Validation module: CSIP17 violation isn't detected when dmdSec is missing

[PhillipAasvangTommerholt]

Running validation (v 2.3.3) up against https://github.com/DILCISBoard/eark-ip-test-corpus/blob/integration/corpora/csip/metadata/dmdsec/CSIP17/IP_18006_CSIP17_1.zip states that the CSIP17 test is passed.

However, Root METS.xml and Representation METS.xml doesn't have a dmdSec. I believe the validator outcome should be 'failed'.

IP_18006_CSIP17_1.zip_validation-report_2023-06-19_1.json.txt

[AntonioG70]

Hi,

The CSIP17 checks for the presence of mets/dmdSec (descriptive metadata section) whenever a SIP contains descriptive metadata. Since your SIP does not include any descriptive metadata, the dmdSec is not mandatory, and the test should pass successfully.

[PhillipAasvangTommerholt]

I read the CSIP17 as: "there SHOULD be descriptive metadata". Therefore I would expect a validator to give a warning if it doesn't exist. However, if there is descriptive metadata content in the package, then it MUST be described in dmdSec - so there are different tests and severity levels located to the same CSIP17 (also described here: #157)

[carlosjepard]

Hello Phillip!
I understand you interpretation, but note that the cardinality starts with 0, so that means that if there is no dmdSec the validation should pass as valid (assuming that there are also no descriptive files).