WIP: Add PREMIS Object XML to file model and template to make characterization tool output visible #180
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently this is the metsrw tuple representation of the output, which isn't the most user-friendly output. It might be better to skip metsrw and just store a blob from the original METS XML or try to turn it into key-value pairs.
tw4l
force-pushed
the
dev/add-technical-metadata
branch
from
75c77b2
to
ab1635c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the PREMIS Object XML for files that have a
premis:objectCharacteristicsExtension. This allows for users to see characterization tool output in its XML form within AIPscan.This currently doesn't work due to artefactual-labs/mets-reader-writer#94. First, artefactual-labs/mets-reader-writer#96 will need to be merged and then a
0.3.22release ofmetsrwuploaded to PyPI.Commit c3a098d is left here for now to show what is possible without serializing the PREMISObject to XML - the result is that the tuple representation of the characteristics extension is stored in the database, which is harder for users to read.