Why keep the imported files in their original location? I do not understand what you are doing. Do one or the other but not both.
The files are distributed around my server system. Iām not about to disturb them to use them in another program (DEVONthink). If I were to use import, Iād keep the originals where they were, hence two copies.
Well, that makes sense, but I think that clearly an āedge caseā and on the ānot-recommendedā or irrelevant end of the scale when considering the pros and cons of indexing vs. importing, IMHO.
1 Like
I wouldnāt say either an edge case or not recommended. David Sparks in the DEVONthink Field Guide says:
So if youāve got a large corpus of data in your Finder and you just want to work on it through DEVONthink without importing it, you can index it.
Which is exactly what Iām doing.
Yes. Agree with David. I just did not want people to think that with DEVONthink importing means doubling up copies.
I index 1000ās of files by indexing the directories. Never had a problem with it. Never found it hard to understand. Indirect reference/pointer equivalents. But then Iām a programmer. Obviously, if you index something on a different volume from the database holding the index, and you pull that volume out, the database aināt gonna know where to find the files. No mystery to me. Indexing takes up way less space so I can have the databases on one volume and the data on other volumes. I organize the mac file system for management purposes (for example, all photos on one volume, videos on another), but then organize the imported stuff in DT logically (everything to do with gardening, everything to do with photography etc).
2 Likes