Skip to content
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

PREMIS schematron is expecting PREMIS 2 and so won't validate PREMIS 3 #4

Open
ross-spencer opened this issue Apr 16, 2019 · 0 comments

Comments

@ross-spencer
Copy link

Archivematica points users at the web interface for this tool so that users can validate their METS output before storing AIPs. Having recently updated to include PREMIS 3 in the output, we are now seeing this error:

image

I have traced it to the best of my abilities to this assert in the schematron:

<rule context="mets:mets">
<assert test="count(//mets:xmlData/pre:object) +
count(//mets:xmlData/pre:agent) +
count(//mets:xmlData/pre:rights) +
count(//mets:xmlData/pre:event) > 0 or
count(//mets:xmlData/pre:premis) = 1" see="bp-1a bp-1b">
There must be PREMIS elements inside the METS container.
</assert>
</rule>

And I can get past this error if I modify the namespace to expect PREMIS 3 but then I start to see additional assertion errors, so a more expert view on how the schematron could be modified would be appreciated. For example, understanding the basis for other assertions such as PREMIS bitstream and file objects must be contained in a METS techMD

Happy to submit a PR if it helps. This is an incredibly useful tool.

Cheers,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant