Management of persistent MCP metadata needed for statistical reports
|Assignee:||Mike Cantelon||% Done:|
|Category:||Data management||Estimated time:||24.00 hours|
|Google Code Legacy ID:||archivematica-882||Pull Request:|
e.g. AIP & DIP locations info. This info will need to be backed up and maintained across release upgrades.
Likely strategy: ensure all this metadata is in one place, i.e. the MCP dbase, include cron script that does MySQL dumps and then document procedures/recommendations for getting backups off MCP server (e.g. on AIP storage?)
[g] Legacy categories: Data management
#3 Updated by Evelyn McLellan almost 9 years ago
The data that should be preserved is:
For AIPs and DIPs:
AIP storage location
Date placed in storage
Date updated (when we have AIP versioning)
DIP storage location
Date DIP uploaded
For transfer backups:
Transfer storage location
Date placed in storage
Courtney to do mock-ups so I'm making her the owner.
[g] Labels added: Component-DataManagement
[g] Labels removed: Component-Backup
[g] New owner: Courtney Mumma
#5 Updated by Courtney Mumma almost 9 years ago
Joseph - I think that one DB per storage location would work best, with minimal MD available for overview in the Administration tab of the Archivematica Dashboard.
See mockup of the Admin tab here: http://archivematica.org/wiki/index.php?title=Transfer_Backup_Requirements#Administration_Tab_in_Dashboard
#6 Updated by Joseph Perry almost 9 years ago
As the order of storing an AIP/uploading a DIP can vary. This information should be held in the es index for archivematica 0.9. Inserted as part of the processing chain, or microservice, for uploading or storing.
In future revisions, this information should be included in the upload/store or updated through an API. === DO NOT CLOSE THIS ISSUE TILL THIS IS DONE === (bump to 1.0 once 0.9 requirements are met)
[g] New owner: Mike Cantelon
#14 Updated by Evelyn McLellan about 8 years ago
- Assignee changed from Evelyn McLellan to Courtney Mumma
Here is the list of data to be saved with the current location in METS identified where applicable:
For AIPs: -AIP name - In METS structMap: <div TYPE="directory" LABEL="[AIPname]-[UUID]"> -AIP UUID - In METS structMap: <div TYPE="directory" LABEL="[AIPname]-[UUID]"> -AIP storage location - Not in METS file -Date placed in storage - Not in METS file -Date updated (when we have AIP versioning) - will be in METS header <metsHdr CREATEDATE="2013-05-09T15:00:00" LASTMODDATE=”2014-02-09T21:00:00> -AIP size - Not in METS file -Related DIP - Not in METS file -DIP storage location - Not in METS file -DIP size - Not in METS file -Date DIP uploaded - Not in METS file For transfer backups: -Transfer name <div TYPE="directory" LABEL="[Transfername]-[UUID]"> -Transfer UUID <div TYPE="directory" LABEL="[Transfername]-[UUID]"> -Transfer size - Not in METS file -Transfer storage location - Not in METS file -Date placed in storage - Not in METS file
#15 Updated by Evelyn McLellan about 8 years ago
Other fields to include:
-Logged-in user (should be captured as PREMIS agent)
-UUID of the Archivematica instance (should be captured as PREMIS agent)
-Possibly also environment data: what machines did Archivematica live on, what versions of all the tools were installed (already in PREMIS events), what version of Archivematica was used (already in software agent).
#16 Updated by Courtney Mumma about 8 years ago
A request for metrics has been sent out to the Archivematica and digital curation discussion groups.
A wiki page has been added for this feature / set of features: https://www.archivematica.org/wiki/Metrics_requirements