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

SIP2 validation checks against wrong profile #161

Closed
prettybits opened this issue Jun 26, 2023 · 2 comments · Fixed by #167
Closed

SIP2 validation checks against wrong profile #161

prettybits opened this issue Jun 26, 2023 · 2 comments · Fixed by #167
Assignees
Labels
Milestone

Comments

@prettybits
Copy link

When validating an E-ARK SIP with mets/@PROFILE set to https://earksip.dilcis.eu/profile/E-ARK-SIP.xml as specified in SIP2 I get a validation failure for the requirement:

{
    "specification" : "SIP-2.0.4",
    "id" : "SIP2",
    "name" : "METS Profile",
    "location" : "mets/@PROFILE",
    "description" : "The value is set to “https://earksip.dilcis.eu/profile/E-ARK-SIP.xml”.",
    "cardinality" : "1..1",
    "level" : "MUST",
    "testing" : {
      "outcome" : "FAILED",
      "issues" : [ "mets/@PROFILE value isn't https://earkcsip.dilcis.eu/profile/E-ARK-CSIP.xml /home/prettybits/SIPs/SIP2/representations/master/METS.xml" ],
      "warnings" : [ ],
      "notes" : [ ]
}

Also, it looks like only errors for the representation METS are reported, even though the package METS has the same profile set?

@AntonioG70
Copy link
Contributor

Hello,

Could you please send the SIP you used?

@prettybits
Copy link
Author

Sure, find a minimal SIP to reproduce the issue here

@AntonioG70 AntonioG70 linked a pull request Jun 27, 2023 that will close this issue
@AntonioG70 AntonioG70 self-assigned this Jul 28, 2023
@hmiguim hmiguim added this to the 2.3.4 milestone Aug 4, 2023
@hmiguim hmiguim added the bug label Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants