Sync and Storage#
EpiLib keeps library data locally and can synchronize it with a configured metadata backend. Attachment file storage is configured separately.
| What you sync | Custom deployment | Upstream service option |
|---|---|---|
| Library metadata: items, collections, notes, and related records | PostgreSQL sync server | zotero.org, when selected in the client |
| Stored attachment files | WebDAV using global settings or library-specific profiles | Zotero Storage, when selected and supported for that library/backend |
Configure your deployment#
- Ask your administrator which metadata backend and file-storage service to use.
- For a custom server, follow PostgreSQL Metadata Sync.
- Configure and verify WebDAV Profiles for attachment storage.
- Check each library’s file-storage assignment under Libraries.
- Test with a small item and attachment, then confirm both arrive on another configured client.
A successful metadata sync does not prove that attachment uploads succeeded. Check both layers when troubleshooting.
Backend-specific behavior#
A zotero.org account belongs to the upstream service. A PostgreSQL server account belongs to that deployment; the credentials are not interchangeable. Switching backends is a migration decision. Back up first and follow your administrator’s migration procedure.
Upstream claims about free storage quotas, group WebDAV restrictions, online libraries, or service policies do not automatically describe EpiLib’s custom server. Consult Project and Group Libraries for the custom workflow.
Backups#
Keep separate backups of local library data, the PostgreSQL database when you administer it, and WebDAV attachments. Sync is not a historical backup: it can propagate edits and deletions.