Info on complementary .zotero library files
To whom it may regard,
what information do the .zotero-ft-cache files contain?
Are the annotation over there as well?
Can all
.zotero-pdf-state
.zotero-reader-state
.zotero-ft-info
be deleted without any issue while Zotero is not running?
what information do the .zotero-ft-cache files contain?
Are the annotation over there as well?
Can all
.zotero-pdf-state
.zotero-reader-state
.zotero-ft-info
be deleted without any issue while Zotero is not running?
Upgrade Storage
The ft files contain indexing for full text (hence ft) search. Disabling them will remove The pdf and reader state files contain the current state of the Zotero reader so it opens the same docs in the same position next time.
Why do you want to delete those files?
https://github.com/MuiseDestiny/zotero-attanger
attanger is doing most of the re-organization for me
For the most part it worked pretty well. The advantage of this is the logical structuring (replacing random words with clearly understandable folder names, from stored files to linked files).
I wanted to then delete unnecessary folder in a post-moving clean-up process.
I have a local storage+onedrive synce setup, so the change in folder organization is advantageous in a vacuum, but maybe I am missing something. Any comment?
If it didn't, I assume the effect would just be that, on the destination volume, Zotero would recreate these files when the application is opened the first time? I'd rather have an exact copy (and I'm assuming that CCC has given me that), but it would be nice to know what the ill effects (if any) would be if these particular files weren't copied to the destination volume.
I would assume CCC includes hidden files on copy, but you'd want to check to make sure and it's conceivable there'd be a setting for that.
(and it wouldn't be a huge issue if you deleted them -- you'd lose the indexing status, indexing information, and current position of the reader, respectively and they can all be regenerated if need be, but still, they're meant to be included in a full library back-up)
Looking further, I've noticed that CCC has a "Don't preserve extended attributes" option within its backup settings. To my understanding, "extended attributes" mostly applies to Finder in macOS, but I guess there are other applications, including third-party ones like Zotero, to which this might be applicable. Because I haven't got this option selected, I can't be certain what it would do the particular files mentioned above. But it's good to know that, regardless, Zotero would regenerate them if, for some reason, they weren't copied.