imported>admsys: +key scheme fixed

2023-10-20T08:45:59Z

+key scheme fixed

New page

We're considering [https://www.zotero.org Zotero] as literature management system for the group.

Points to know:

* Local usage of the software is free.
* Registering at [https://www.zotero.org Zotero] provides a cloud service for syncing the database and its attachments, up to 300 MiB it's free. For {2 GiB, 6 Gib, ∞} it's [https://www.zotero.org/support/individual_storage {$20, $60, $120} per year].
* The database itself is small, but the attachments (typically the actual papers) will quickly grow beyond 300 MiB.
* For the users ''own'' library, syncing can be split: The database can be synced to Zotero, the attachments can be synced to any WebDAV server (like our [https://nxcl.e-services.physik.uni-due.de NextCloud]).
* Registered users can create a group and invite others, this yields a ''group'' library (upon next sync).
* For the ''group'' library, syncing ''cannot'' be split, it has to use the Zotero server.
* The scheme for generating the unique item keys ''cannot'' be changed.
* Zotero allows for ''linking'' to attachments inside a designated folder. For this, only relative paths within this folder are stored in the database.
* We could share the "linking folder" (or rather a sub-folder therein) via [https://nxcl.e-services.physik.uni-due.de NextCloud]. But it should be pre-structured well, because once a contained file is referenced in the database, it shouldn't be renamed nor moved.

Zotero - Revision history

imported>admsys: +key scheme fixed