This includes two strands:
1) Retaining original datetime stamps on files stored/transferred to Rosetta (e.g. using commands like "rsync")
2) Extracting datetime stamps from files to store with the digital object in its technical metadata.9 votes
There are actually 2 ideas here. We’re happy to let you know that we’ve implemented the first idea as part of Rosetta version 5.2. Please open another idea for the second one and we’ll evaluate it separately.
The BagIt format (https://en.wikipedia.org/wiki/BagIt) is “designed to support disk-based storage and network transfer of arbitrary digital content”. Rosetta should support ingests via BagIt to standardize various ingest workflows and make use of the existing BagIt software ecosystem.4 votes
Deposit of BagIt content was implemented as part of Rosetta version 5.2.
We have a few workflows where we are adding derivative copies either manually or automatically.
We hold our derivative / access copies to a different standard than the preservation master files - as such, we are willing to ignore most techMD extraction errors, etc. at this stage.
However, looking at the MD extraction error handling rules, ignore reasons can only be filtered on the producer / format / extension / mime type etc. level.
We therefore propose to add Preservation Type as an input criterion for submission rules such as metadata extraction error.4 votes
Provide XSD and/or examples of the raw XML for places in which Rosetta provides the option of editing the XSLT.3 votes
- Don't see your idea?