Versions Compared

Old Version 13

changes.mady.by.user rwolfe@mit.edu

Saved on

compared with

New Version Current

changes.mady.by.user Patricia Baudoin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

...

  • 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

...

kinds of hierarchical relationships

  • book --> chapter --> page
  • FRBR
  • courseware
  • other chains of aggregation levels in different domains (from largest to smallest)?

...

  • Look up types of peer, hierarchical, and network relationships that we might encounter

CORE structural Elements

Type element: aggregation, atom (smallest deliverbale unit) agent (person or organization)

Policy: each atom must belong to an aggregation, the outermost aggregation; relationship may be nul in the case where the atom is free-standing.

Sept 2, 2009

Present:

  • Patsy
  • Tom
  • Rob
  • Ann Marie

...

  • PREMIS (event)
  • ABC HArmony

Oct. 1, 2009

Techincal and provenance are seperate metadata, but policies are not in place for migration. It is difficult to decide what we need to capture about provenance events.

Look at provenance metadata schema-- PREMIS has a provenance "event" entity.

Copyright metadata

2 kinds of rights

1. DRM (or access managemnt) -- ODRL, MPEG -- these are policy metadata schemas. Spell out who can perform what.

2. descriptive meatdaat schemes

PREMIS rights

METS rights

LoC rights MD -- See LoC A/V prototype project: http://www.loc.gov/rr/mopic/avprot/metsmenu2.html

http://www.loc.gov/rr/mopic/avprot/DD_RMD.html

They all provide for:

-- rights holder

-- rights basis (based on contract, license, a coipyright statement, or stutute like fair use, public domain.

--content (a URI/CC license; or text of the rights)

-- context -- who, when and sometimes where (which means in DSPace for us, so less important). Human-readable, not coputer-actionable. Must be inclusive of the needed oinformation. (i.e. a notes field)