Update to get sharedDirectory from Storage Service
|Status:||In progress||Start date:|
|Target version:||Release 1.7.0|
|Google Code Legacy ID:||Requires documentation:|
Currently, the sharedDirectory path is defined in /etc/archivematica/MCPServer/serverConfig.conf, as well as assumptions about it scattered around the codebase.
The Storage Service assigns each pipeline a Currently Processing Space.
Archivematica should get it's sharedDirectory path from the storage service. Also, the shared directory structure (watched directories, currently processing, etc) should be created dynamically from entries in the database (eg watched directories) and known paths (eg. failed, rejected).
#1 Updated by Holly Becker almost 8 years ago
- Status changed from New to In progress
Updated all hardcoded references to /var/archivematica/ to refer to the serverConfig.conf file. On boot, the MCPServer queries the storage service for the currently processing location, and creates the shared directory structure at that path. The currently processing space can be changed by updating it in the storage service and restarting Archivematica twice.Existing problems:
- To change the currently processing location, Archivematica must be restarted twice.
This is because the MCPServer and dashboard start at the same time and read the config file once on boot. The MCPServer updates its config by querying the SS and writing the new value to the config file, but has no way of updating the dashboard's cached value. The second restart updates the value in the dashboard.
A possible solution is to not cache the config values, but then any change to the config would be immediately reflected in the runtime behaviour - possibly not a good thing.
- SIP arrangement JS uses hardcoded /var/archivematica/
This was commented out in the 1.0 branch and is under active development currently. Will need to be fixed when these branches are merged.