-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: capture PREMIS events for pre-ingest validation tasks #19
Comments
Annotated PREMIS file for multiple objects: |
In the sample PREMIS event, @fiver-watson provided a generic linkingAgentIdentifierValue of |
The structure of the PREMIS file looks good. However, I'm seeing two issues:
Looking at the PREMIS file that's generated, I can see that there are five objects in the package. I can see that there are six format validation events (there should be five, I think - not sure what's going on there). However, all of the objects are linked to just one of those events, rather than each object being linked to a separate event. A similar issue happens with the structure validation and metadata validation events, except in those cases there are only one of each event. There needs to be one event for each object (even though that doesn't make sense, I know!)
Let me know if a mock-up of the premis.xml would be helpful. |
PR ready for CR: #31 |
* Removed redundant PREMIS event for validate file formats * Correct use of improper PREMIS event types * Allowed PREMIS evebt details and PREMIS event outcome detail to be specified rather than generated * Add PREMIS event outcome detail specification to PREMIS events in workflow and validate file formats activity * Generate error when attempting to add a PREMIS event to a non-existent PREMIS object * Fixed issue with validate formats activity * Removed unneeded code in tests of add PREMIS event activity
* Removed redundant PREMIS event for validate file formats * Correct use of improper PREMIS event types * Allowed PREMIS evebt details and PREMIS event outcome detail to be specified rather than generated * Add PREMIS event outcome detail specification to PREMIS events in workflow and validate file formats activity * Generate error when attempting to add a PREMIS event to a non-existent PREMIS object * Fixed issue with validate formats activity * Removed unneeded code in tests of add PREMIS event activity
@mcantelon Archivematica is throwing up the following error - I don't really understand what it means!
|
* Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure * Return subpaths within transfer, instead of absolute paths, in file format validator list of failures
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure * Return subpaths within transfer, instead of absolute paths, in file format validator list of failures
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure * Return subpaths within transfer, instead of absolute paths, in file format validator list of failures
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure * Return subpaths within transfer, instead of absolute paths, in file format validator list of failures
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure * Return subpaths within transfer, instead of absolute paths, in file format validator list of failures
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure * Return subpaths within transfer, instead of absolute paths, in file format validator list of failures
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure
PR to fix issues: #19 |
* Renamed event adding functions * Fixed PREMIS event recording to add one event per file * Updated PREMIS event recording and tests to work with updated transfer structure
Fix merged! 🤞 |
Added support for born digital SIPs to PREMIS event recording.
Added support for born digital SIPs to PREMIS event recording.
Added support for born digital SIPs to PREMIS event recording.
Added support for born digital SIPs to PREMIS event recording. [skip-codecov]
Co-authored-by: José Raddaoui Marín <raddaouimarin@gmail.com>
Is your feature request related to a problem? Please describe.
SFA SIPs will have some custom ingest validation tasks in their workflow that will:
At present, none of these pre-ingest validation tasks are generating PREMIS events. This card aims to change that where possible.
In some cases it would be best to create PREMIS events at the package level (such as for the transfer structure validation) - since AM can't do right now, we will focus only on those events we can add at the file level. For now, we will focus on generating a validation event for each file in a package once it has been checked against the allowed file formats list during the ingest validation phase.
Describe the solution you'd like
Generate file-level PREMIS events where possible, and include them as part of a new well-formed premis.xml file.
The first candidate is file format validation.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Previously, we were generating a premis.xml file by combining individual PREMIS files found within the content directory. This work is being undone by #18.
The text was updated successfully, but these errors were encountered: