When I index files, if some have moved and i update items, thos ecome back as failed rather than no longer being in the index list. it used to be different - but now everytime i move something, i have to have it register as failed forever. i am not sure what to change but this is new behaviorl.
I took a look at DEVONthink “Help” to remind me of some of the pitfalls with indexing which may apply to you.
The “Help” says:
Moving Indexed Items: DEVONthink stores individually indexed items by its absolute path in the filesystem. If you move an individually indexed file or folder, it will disappear when the database updates or be reported as missing. This is because the item no longer exists in the indexed location, so the absolute path points to nothing. If you move a file or subfolder inside an indexed parent group, the change should be reflected in the database or the Finder. The parent folder still exists in the same location and DEVONthink can adjust for the changed relative paths within it.
Is there a specific reason why you are indexing rather than importing? Indexing adds complexity and I only do it for very specific–and rare for me–reasons.
1 Like
I would take a bet this situation has been answered 50 - 100+ times in this forum, because of the same errors and misunderstanding. Which is why Search is your friend. Try it sometime. Indexing is actually very easy to understand and very easy to break if you don’t follow the rules:
- In Finder, don’t move files in folders you are indexing in DEVONthink to folders that are not children of the indexed folder
- Don’t rename folders you are indexing.
- Don’t let any app move your indexed folders or the files indexed inside them.
- Don’t index files – index folders, for safety.Don’t let any app delete indexed files.
- Don’t index at all unless there’s another app that has a legitimate need to access the same folder hierarchy you want to index, not you know how that app manages files, and not until you have thought about all the consequences.
When it comes to indexing, there are no “dos”, just “don’ts”.
4 Likes
this is insane attitude for someone who doesn’t even understand what i’m saying. are you okay? to answer your questions - i AM indexing folders, i haven’t let any app move anything, i haven’t renamed anything, i’m using the same indexed folder i’ve used for nearly 5 years and haven’t moved it once. i’ve been using DEVONthink (and indexing files) for many years (you even helped me w/ a script once!), and as i said, this is new behavior. typically if a file has moved out of the folder, when you update items from the file menu the index recalibrates and reassesses what is in your folder. meaning its no longer visible in DT3 as missing or otherwise. ymmv on how effective updating items is at recognizing a moved sub-folders, but with files in an indexed folder it has worked consistently for a decade or so. its worked for this specific folder for five years. now its not. and for the record i DID search. as i said, this is a bug and new behavior.
my message wasn’t particularly clear, i know, but i really do find it fascinating how DT is my absolute favorite tool and yet the loudest voices in the community can be so profoundly unwelcoming! i now remember why i stopped coming to this forum years ago lol. unnecessary hostility towards someone who has come to the DEVONthink bug-report forum to report a bug in DEVONthink.
i index because i like having access to the files outside of DT if need be - i find the indexing capabilities to be one of the best things about DT. I have a folder with my primary project documents, which don’t change often - every few years or so - and then I’ll create a new database for each sub-project documents. i can work with them in DT and delete the database when I’m done. it works great for me, usually! up until recently.
You’re not indexing a parent folder in one database then indexing subfolders into other databases, are you?
no, i’m not - all indexed folders live in different databases separate from each other.
In DEVONthink, hold the Option key and select Help > Report Bug to start a support ticket.