Keeping attachment cache separate from database
Following setup at the university department where I work: I am in an office with a very slow network connection. To store my data, I can either use a roaming profile, which stores data locally and gets synchronized at login / logoff, or a slow network drive.
The problem is that
- if I store the Zotero data dir on the roaming profile, the synchronization of it times out because of the size of my "storage" directory (I have a lot of multi-megabyte PDF attachments).
- if I store it on the network drive, I get frequent database errors because the SqlLite database is not meant to be stored on a slow network drive.
One solution seems to be to store the database on the roaming profile and the attachment storage on the network drive. However, it seems not possible to separate the storage folder from the data directory, or it is? If not, are there technical reasons why that won't be possible, or could this be a feature request?
The problem is that
- if I store the Zotero data dir on the roaming profile, the synchronization of it times out because of the size of my "storage" directory (I have a lot of multi-megabyte PDF attachments).
- if I store it on the network drive, I get frequent database errors because the SqlLite database is not meant to be stored on a slow network drive.
One solution seems to be to store the database on the roaming profile and the attachment storage on the network drive. However, it seems not possible to separate the storage folder from the data directory, or it is? If not, are there technical reasons why that won't be possible, or could this be a feature request?
I know there's been some talk about restructuring the storage folder, so this isn't out of the question, but having the database and the storage folder in the same location solves the issue of linking files & metadata. Without that, users have to specify the location of the storage folder on every synced computer, which is possible, but error prone.
You're aware that you can use ZotFile to turn attachments into links in any custom location you want to? That does have some downsides, but it should solve your biggest issue.