(Disclosure: Zotero dev)
There was a forum entry that self-hosting the database is a topic being worked on. That's my number one gripe with Zotero, it just seems weird: if using multiple clients, users have to sync to the Zotero servers, yet the storage space for attachments there is minimal (which is okay; Zotero pricing looks reasonable but of course, own storage via e.g. Nextclodu is much, much cheaper). This basically forces a hybrid solution, with bring-your-own-storage. If all of Zotero's data could be self-hosted, now that would be a streamlined, great experience.
Then again, I am anal about my entries' metadata and often correct faulty data found online. Syncing that to Zotero servers is kind of like giving back? I always thought that data might help improve Zotero's own auto-fill functionalities, which I'd like helping with.
> Syncing that to Zotero servers is kind of like giving back? I always thought that data might help improve Zotero's own auto-fill functionalities, which I'd like helping with.
No, we don't expose your data to anyone else. (And tools that try to do that usually just end up filling people's libraries with junk data.)
You should sync Zotero if you want to 1) access your library on other devices, 2) collaborate with others, and/or 3) have a real-time backup of your Zotero data.
Zotero is great! :)
- Offline ensures that you do not suffer an externally caused downtime just before a deadline
- Offline ensures that you have a path for keeping your database throughout your research career, and to do system updates when _you_ want to.
- Offline ensures that if you leave academia, you will always have access to local copies of the academic papers you have referenced.
My favorite offline/local reference manager is `jabRef` [0] which stores all metadata directly in a bibtex-file. The GUI has an excellent pdf-integration, and everything is local and super fast.
Case in point: after a decade in industry, I am looking to get back into my academic fief. All the papers I ever read are in my Dropbox, and all I had to do to pick up where I left was download a current version jabRef and point it to my database which it read without any issues.
[0]: https://www.jabref.org/