#1036 closed enhancement (fixed)
Migrate storage directory folders to secondary keys
| Reported by: | dstillman | Owned by: | dstillman |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.5 Sync Preview 1 |
| Component: | data layer | Version: | 1.5 |
| Keywords: | Cc: |
Description
Change History (3)
comment:1 Changed 8 years ago by stakats
- Version changed from 1.0 to 1.5
comment:2 Changed 8 years ago by dstillman
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 8 years ago by stakats
How do we deal with the scenario of a user upgrading a Zotero library copied onto multiple machines? Since the new randomly-generated attachment directory names will be different on both machines, do we simply discourage this practice? Or do we need to do something different to prevent this problem?
Note: See
TracTickets for help on using
tickets.
(In [2942]) Closes #1036, Migrate storage directory folders to secondary keys
Also moves orphaned directories into orphaned-files folder in data dir
Safety first: Keeps track of moved files, moving them back if there's an error before the end of the upgrade process (since the keys are generated randomly and would be different if recreated), and creates a zotero.moved-files.36.bak file with a list of id/key pairs