Rosetta METS XSD update with reference to several file IDs
Due to an error in one of our input files that creates the METS during a recent batch of deposits, we found that our original METS file did not have unique file IDs in the structMaps for the preservation master and modified master representations (for more details, see case 00477041 from the Getty). It was simply repeating the same file ID from the access file representation.
We validated against the Rosetta XSD both before and after deposit, and for some reason, this did not result in a METS validation mistake. Consequently, however, no files in the METS in Rosetta were listed by the structMaps with the duplicate file IDs. Because the fileIDs in the fileSec were valid, every file was imported properly; however,
Could you tighten the METS XSD to require that the file IDs for each structMap be unique? It would make sense if the XSD enforced the rule that utilizing the same file ID across various representations with the same structMap type is against Rosetta's data model.
dude theft auto,
McKee Elias
shared this idea
-
Sandra J. Brown
commented
Ever have a puzzling validation issue? I once had a METS file where duplicate file IDs were somehow allowed during deposit, but later caused problems listing files. How did I fix it? Ultimately, I had to manually adjust the METS file to ensure all file IDs were unique.
-
Jay AReddick commented
This suggestion makes perfect sense — enforcing unique file IDs per structMap in the Rosetta METS XSD would help catch errors early and prevent missing content in structMaps. A valuable proposal!