/
ContentMD discussions
ContentMD discussions
Resolutions:
- document Stanford contentMD schema (LTM)
- document decision that Hydra compliant objects reply to contentMD method and return contentMD xml (RG)
- document the fact that there are multipe options for satisfying this. show the most common ways you might satisfy this (RG -> MZ):
- explicit contentMetadata datastream,
- explicit structInfo & fileInfo datastreams in parent that also rely on part objects' fileInfo datastreams…
- start a comprehensive JIRA ticket (RG)
NOTE: assembling the contentMetadata on the fly is actually an example of a pattern
examples:
- Assembling full EAD for a collection,
- Assembling METS on the fly,
- TechMD on the fly,
- BagIt manifest files, OAI-ORE, etc.
, multiple selections available,
Related content
Object cModels and datastreams
Object cModels and datastreams
More like this
Samvera objects, content models (cModels) and disseminators
Samvera objects, content models (cModels) and disseminators
More like this
Hydra content models and disseminators
Hydra content models and disseminators
More like this
Community Content Modelling
Community Content Modelling
More like this
Hydra:Works @ Code4Lib Notes
Hydra:Works @ Code4Lib Notes
More like this
Don't call it a 'content model'!
Don't call it a 'content model'!
More like this