...
Datastream | Set | Item | Child of atomistic object |
---|---|---|---|
identityMetadata | Has <objectType>set</objectType> | Has <objectType>item</objectType> | Minimal, to record objectType objectLabel and uuid |
descMetadata | EAD to MODS mapping, with <mods:typeOfResource collection="yes"/> | EAD to MODS mapping | n/a |
sourceMetadata | n/a | optional | n/a |
provenanceMetadata | n/a | Defer | n/a |
technicalMetadata | n/a | Defer; part of object creation, validation and preservation workflows. | possible during object assembly until integrated into parent item record; not part of final Hypatia objects |
contentMetadata | n/a; "content" is defined by the set's membership | Using Stanford schema | possible during object assembly until integrated into parent item record; not part of final Hypatia objects |
rightsMetadata | Public template | Public template | n/a |
RELS-EXT | hydra:hasModel=implicitSet | fedora:hasModel=hydra:genericParent | fedora:hasModel=hydra:genericContent ... or ... |
content | n/a | n/a, that is to say, Hypatia fully embraces the atomistic model, separating the parent metadata-bearing object from child content-bearing object(s), even in cases off single-file content. This is not a given across Hydra in general, but a simplifying assumption for early Hypatia. | For Hypatia we can use both the simple genericContent model where each child object bears a single file, or the compoundContent model where multiple content files in the child are in content01, content02, etc. |
...
- Stanford identityMetadata datastream
- Stanford-specific extensions to contentMetadata, e.g., shelve, publish and preserve directives
- Stanford has all content in its externally managed "Digital Stacks"
- Child objects have no content datastreams (and in some cases may be obviated)
- contentMetadata <location> URLs will point to stacks delivery services
- Shared demo Hypatia objects need to be locally managed and self-sufficient, without reliance on Stanford environment
Sharing
Method of contributing/sharing of objects to be determined by the practitioners along the lines of whatever works. Current thinking is that FOXML is the best lowest common denominator, or perhaps working directly with a dev hypatia repository where possible.
identityMetadata
Stanford-specific. Will appear in Stanford produced fixtures and demo objects; not required otherwise.
...
First round has publicly accessible objects only, using the following rightsMetadata:
Panel |
---|
<rightsMetadata> |
...