Child pages
  • Data Model Options
Skip to end of metadata
Go to start of metadata

Heidi's Notes, later on 8/10/2016:

Based on the Preservation Metadata meeting, we landed on this as the most viable option for the data model:

Heidi's Notes, 8/10/2016:

Refining data model options:

Option 1: Nested works in CurationConcerns makes it easier to store multiple works, would allow us to separate the physical and digital object in terms of metadata. The issue is that this would require the depositor to create two separate works within HD2.

               In this case, if a physical object needs to be redigitized it could be stored again as a separate nested work? That way the digitization process metadata from both the first digitization and the second could be accessible. Useful if there's like a problem in the digitization process, etc.

Option 2: Physical A/V objects behavior could be turned off at the developer level if only handling born digital materials. However, if this behavior is implemented, the physical object metadata fields are displayed on the same work. No differentiating between physical object and digital work.

Daniel's Notes, 7/18/2016:

Some questions that need to be answered regarding how the HydraDAM data model handles different work flows.

See for diagrams of some modeling options.

  1. How should data about the physical object that was digitized be stored?
    1. As a simplified object that is a member of the top-level Work? 
    2. As it's own Work, distinct from the currently implemented Work, but has a stored relationship?
    3. As a set of metadata that can be optionally included in the top-level work?
  2. If a Work is redigitized for some reason, how is that stored, respecting the above options?
    1. As a fully separate Work, duplicating data about the original object?
    2. As a new Work that adds a relationship to an existing PhysicalObject?
  3. Where is data about the digitization process(es) and preservation actions stored?



  • No labels