Import full cd-info output into METS files as cartrier-level technical metadata

[bitsgalore]

Related to: https://github.com/KBNLresearch/iromlab/issues/49; may be needed to render ISO images from multisession discs.

[bitsgalore]

Use sourceMD element inamdSec? See e.g.: http://www.loc.gov/standards/mets/docs/mets.v1-9.html#sourceMD and http://www.bl.uk/profiles/sound/METS_profile.pdf.

Minimal example:

https://gist.github.com/bitsgalore/cd903a2479404629346daa955fca112f

Then within sourceMD maybe use PREMIS with xsi:type="premis:representation" + objectCharacteristicsExtension or something along those lines

LoC PREMIS in METS guidelines:

http://www.loc.gov/standards/premis/guidelines-premismets.pdf

Doesn't appear to cover this use case. It does say:

premis:object under techMD or digiProvMD Object metadata for file and bitstream levels should be in techMD if separating between METS sections. Implementations may wish to include information about representations in the object schema under digiProvMD, but this is a local decision which may depend on the processing model used.

But:

• Only covers files/bitstreams
• CD as a whole is a representation (I think)

BUT why not use techMD instead of sourceMD??

ALSO PREMIS 1.5 objectCharacteristics: p. 34 of data dictionary says unit not applicable to intellectual Entity and Representation object types!

[bitsgalore]

Possibly useful:

http://pim.fcla.edu/validate

Takes a METS document containing PREMIS elements and validates it according to the PREMIS in METS Best Practice Guidelines

[bitsgalore]

OK, so PREMIS won't allow this. Other option: directly in METS techMD/mdWap

From METS schema:

http://www.loc.gov/standards/mets/mets.xsd

Such metadata can be in one of two forms: 1) XML-encoded metadata, with the XML-encoding identifying itself as belonging to a namespace other than the METS document namespace. 2) Any arbitrary binary or textual form, PROVIDED that the metadata is Base64 encoded and wrapped in a element within the internal descriptive metadata element.

Form 1 doesn't apply here because iso-info output is not XML. Form 2 IS possible, but having to Base64 encode is a major pain in the ass (mainly from accessibility point of view).

[bitsgalore]

Done: https://github.com/KBNLresearch/omSipCreator/commit/be86657ed49b3f87ee91031ea4f0381e37334ab9