Skip to content
This repository has been archived by the owner on Mar 14, 2022. It is now read-only.

TACO Data Modeling & MAPs

Jump to bottom
Christina Harlow edited this page Apr 2, 2018 · 16 revisions

Generated from the design work done by the Phase 1 Team.

THIS IS ACTIVELY BEING REDESIGNED AND SHOULD NOT BE CONSIDERED VALID

Table of Contents

SDR3 Data Model Overview

SDR3 Data Model Diagram

SDR3 Metadata Application Profiles

MAP Keys

Expectation key

Code Description
M Mandatory
M+ Mandatory if applicable
R Recommended
R+ Recommended if applicable

Source key

Code Description
U User supplied only
U+ User supplied if provided, System derived otherwise
S System derived only

Broken out according to resource type (Collection, Object, Fileset, File).

Digital Repository Object (DROs, aka Object)

Definition: Domain-defined abstraction of a “work”. Digital Repository Objects’ abstraction is describable for our domain’s purposes, i.e. for management needs within our system. Maps to PCDM:Object. More information on SDR3 Digital Repository Objects.

Structural Expectations:

  • Can contain zero or more FileSets(s).
  • Can have zero or more component (member) Digital Repository Objects.
  • Can have ordered members (component DROs) but it is optional.
  • Can not contain Files or Collections.

Scope of the abstraction for an DRO within our domain:

  • Delineates a discoverable entity;
  • Delineates a unit of ownership;
  • Delineates a unit of preservation;
  • Delineates (along with Digital Repository Collections) a unit of what our domain versions.

Object Subclasses / Content Types:

  • 3d
  • Agreement
  • Book
  • Dataset
  • Document
  • Geo
  • Image
  • Page
  • Photograph
  • Manuscript
  • Map
  • Media
  • Track
  • Web archive binary
  • Web archive seed

Profile:

  • See the JSONschema specified MAP here.
  • TBD: RDF specified MAP for @context node.
  • See our DRO MAP CSV

Digital Resource Collection (DRC, aka Collection)

Definition: A group of Digital Repository Objects that indicate some type of conceptual grouping within the domain that is worth reusing across the system. Maps to PCDM:Collection. More information on SDR3 Digital Repository Collections.

Structural Expectations:

  • Can have zero or more member DRO(s) or DRC(s).
  • Can not contain File(s).
  • Can be Ordered or Non-Ordered (i.e. it's member resources can have an order but it is optional).
  • Allows Multiple Membership (i.e. a Digital Repository Object can belong to multiple collections).

Scope of the abstraction for an DRC within our domain:

  • Delineates a discoverable entity;
  • Delineates a unit of ownership;
  • Delineates a unit of preservation;
  • Delineates (along with Digital Repository Collections) a unit of what our domain versions.

Collection Subclasses / Content Types:

  • Curated collections
  • User Collection
  • Exhibit
  • Series

Profile:

  • See the JSONschema specified MAP here.
  • TBD: RDF specified MAP for @context node.
  • See our DRO MAP CSV

File Grouping (Fileset)

Definition: Relevant groupings of Files. Maps to HydraWorks:Fileset.

Structural Expectations:

  • Can only contain File(s). Must have at least one File (do not create a File Grouping without a file).
  • All Files must be contained by a File Grouping.
  • All File Groupings must be contained by a DRO (they cannot exist alone).
  • Members cannot be ordered.
  • Does not allow Multiple Membership (i.e. it belongs to one DRO).

Scope of the abstraction for an DRC within our domain:

  • Delineates a grouping of Files that are from the same processing & represent the same DRO.

File Grouping Subclasses / Content Types:

  • n/a (TBD)

Profile:

  • See the JSONschema specified MAP here.
  • TBD: RDF specified MAP for @context node.
  • See our File Grouping MAP CSV

File

Definition: Binaries that are the basis of what our domain manages. Binaries here do not include metadata files generated for the domain's own management purposes. Maps to PCDM:File.

Structural Expectations:

  • Files cannot contain anything.
  • All Files must be contained by a File Grouping, which in turn must be contained by a DRO.
  • Files cannot be ordered.

Scope of the abstraction for an DRC within our domain:

  • File metadata resource within TACO delineates describing 1 & only 1 binary within TACO.
  • TACO is binary & asset type neutral;
  • Stores or points to fuller technical metadata having been generated;
  • Delineates a unit of downloading;
  • Can be “deliverable”, but not required;
  • Delineates a unit of ownership;
  • Delineates a unit of preservation;
  • Delineates a unit of what our domain versions.

File Format Types:

File Usage Types:

Profile:

  • See the JSONschema specified MAP here.
  • TBD: RDF specified MAP for @context node.
  • See our File Grouping MAP CSV

Agents

Definition: An Agent - Person, Group, Organization, or other Acting body.

Profile:

  • See the JSONschema specified MAP here.
  • TBD: RDF specified MAP for @context node.
  • See our File Grouping MAP CSV

Operational Annotations

Flexible metadata annotations for emerging or not formalized within our domain administrative functions. Can be applied to any Domain resource.

Reuse the Web Annotation Model.

TACO Docs

TACO Wiki Homepage

Design & Process

Selection

Legacy

Clone this wiki locally