Making Zotero read only for mult-user access
Hi,
I am new to Zotero but have read many of the posts regarding mult-user access. We also want to keep all of our files (which are now in Zotero) on our network server, but I was wondering if it was possible to change the Zotero files (i.e., sqlite, etc.)to "read-only" for multi-user access without corruption of the database? I would then "uncheck" the files when I wanted to add pdf's to Zotero, then make them read-only again when I finished my modifications. I am not an IT person so I am try to find a very simple solution for local network multi-user access. Thanks.
I am new to Zotero but have read many of the posts regarding mult-user access. We also want to keep all of our files (which are now in Zotero) on our network server, but I was wondering if it was possible to change the Zotero files (i.e., sqlite, etc.)to "read-only" for multi-user access without corruption of the database? I would then "uncheck" the files when I wanted to add pdf's to Zotero, then make them read-only again when I finished my modifications. I am not an IT person so I am try to find a very simple solution for local network multi-user access. Thanks.
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
What's so bad about using Zotero sync?
There's a reason Zotero has an extensive dataserver protocol to allow syncing between computers.
It's open source, so in principal you can host that locally
https://github.com/zotero/dataserver
http://www.zotero.org/support/dev/dataserver_setup
but that requires significant skill and expertise.
Zotero needs write access to the sqlite all the time. It needs write access every time you save an item or make the most tiny change and, I believe, even some more basic operations like remembering your last selected item. It's just not feasible to switch it between "read only" and "read&write". And even if it were - you switch the database to read - someone else accesses it at the same time - and you've got your database corrupted.
Some third parties are working on easier implementation, though.