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 - Creating a 2.1.0 E-ARK SIP results in wrong value for mets/@PROFILE #294

Closed
spacid opened this issue Sep 13, 2024 · 1 comment
Closed
Assignees

Comments

@spacid
Copy link

spacid commented Sep 13, 2024

When creating a 2.1.0 E-ARK SIP with commons-ip version 2.8.0 , the value of mets/@PROFILE is "https://earksip.dilcis.eu/profile/E-ARK-SIP-v2-1-0.xml". According to the 2.1.0 spec it should be: "https://earksip.dilcis.eu/profile/E-ARK-SIP.xml":

image

Also, validating a 2.1.0 SIP via commons-ip with the value "https://earksip.dilcis.eu/profile/E-ARK-SIP.xml" results in the following ambiguous error:

{
    "specification" : "SIP-2.1.0",
    "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://earksip.dilcis.eu/profile/E-ARK-SIP.xml Root METS.xml" ],
      "warnings" : [ ],
      "notes" : [ ]
    }
@hmiguim
Copy link
Member

hmiguim commented Mar 27, 2025

Hi @spacid,

Commons-ip uses the latest specification version, in this case, 2.2.0, as the default.

To validate the SIP against 2.1.0 version, please use the option --specification-version=2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants