Index creating duplicates in DTP 1.1

DEVONthink Tips
1

In another thread, a Devon developer said of v.1.1, “synchronizing won’t create duplicates anymore”. That doesn’t seem to be the case in my testing.

I created a folder structure like this (all of these are folders):

foo

bar
baz
qux

I then indexed foo. Then, in the Finder, I moved qux into baz to get this:

foo

bar
baz

qux

Then I performed a Synchronization. DevonThink ended up with this:

foo

bar
baz

qux
qux

So, now I have two quxi in DevonThink. Is this the correct behavior? I was under the impression, it would sync to match the Finder by adding, deleting, and moving files/folders accordingly. Is is supposed to perform in that manner?

Thanks

2

Some preferences have been simplified in DTPro 1.1. One on these was the choice between import, index, link on drag-and-drop of a pdf in a DTPro window. I’d just like to know what happens whit pdf’s dropped on a DT window in the new version? are they automatically copied in DTPro’s database folder?

Thanks

3

Yes, drag & drop into the Names column, the Dock or the Groups panel copies PDFs into the database Files folder. Same for images and QuickTime media. Also for “unknown” file types if you’ve checked Preferences > Import - Unknown file types. Drag & drop of text file types (including RTF, HTML etc.) copies them into the body of the database.

If you want to leave files externally linked, use File > Index.

Check out the improvements in synchronizing files back to the database after launching them under the parent application, editing and saving.

4

Thanks, Bill

5

Anyone know about the duplicate issue?

6

I’ll check this at the beginning of next week but it looks like a bug (but a minor maintenance release will probably follow in April anyway).

7

Thanks for the info. This is about the only thing keeping me from using DevonThink right now. I’d love to be able to use the import option, but it does bad things to my “Web archives” (not Safari webarchives–Firefox Web archives–Firefox saves as plain html with local links to the images, css, etc.)

Anyway, indexing looks like my best option right now, but I’d rather not have duplicates.

Thanks again

8

The issue will be fixed in V1.1.1 and occurs only if existing & already indexed stuff is moved to another location but not if you’re creating/updating items or removing items from the indexed folders.