Metadata Genres Core Element Discussion 8 July 2009
Present:
- Patsy
- Tom
- Rob
Notetaker: Rob
What are Metadata Genres:
- Preservation
- Rights
- Structural
- Provenance
Objective of this Discussion:
A core set of elements for each genre.
Structural Metadata
Purposes of structural metadata
- File management
- Content Management or Collection Management
- Domain Modeling
Structural Metadata Requirements
- Identification of the Atomic Unit(AU) of a domain. The atomic unit is a standalone entity. The structural metadata may need to indicate the standalone status of any entity it describes.
- Reference to the metadata for an AU
- Reference to all files that comprise AU
Possible Structural Metadata Requirements
- Relation of Atomic Unit to other things in the domain
Different methods of recording Structural Metadata
- In the metadata for the AU (via relation metadata)
- In a separate map (e.g. METS)
Brainstorm kinds of relationships
One way to categorize relationships
- part --> whole (hierarchical)
- whole --> part (hierarchical)
- part --> part (peer)
- networks
kinds of peer relationships
- version
- sequence
- other peer relationships?
kinds of hierarchical relationships
- book --> chapter --> page
- FRBR
- courseware
- other chains of aggregation levels in different domains (from largest to smallest)?
kinds of network relationships
- websites
- relationships between agents
- other web like structures?
Hierarchical Metadata Requirements
- Define Atomic Unit (Smallest Describable Unit)
- smallest needs to know largest
- largest needs to know about all the smallest
- In between relationships not core
Peer Metadata Requirements
- Atomic Unit must have one peer relationships
rwolfe todo
- Look up types of peer, hierarchical, and network relationships that we might encounter