Difference between revisions of "Old:Curation Metadata"

From Dryad wiki
Jump to: navigation, search
Line 1: Line 1:
 +
'''STATUS:''' Please also refer to the [[Curation]] and [[Metadata_Profile|Metadata Profile]] pages for information about implementation in the repository.
  
 
*study initiatied to capture "status" of metadata records, when to know they are ready to be published.  Sarah Carrier pursued this work in the metadata class, and ended up establishing the "Dryad" namespace, and then registered the "status" element for the Dryad application profile, following the Singapore Framework recommendation.
 
*study initiatied to capture "status" of metadata records, when to know they are ready to be published.  Sarah Carrier pursued this work in the metadata class, and ended up establishing the "Dryad" namespace, and then registered the "status" element for the Dryad application profile, following the Singapore Framework recommendation.

Revision as of 07:44, 29 July 2010

STATUS: Please also refer to the Curation and Metadata Profile pages for information about implementation in the repository.
  • study initiatied to capture "status" of metadata records, when to know they are ready to be published. Sarah Carrier pursued this work in the metadata class, and ended up establishing the "Dryad" namespace, and then registered the "status" element for the Dryad application profile, following the Singapore Framework recommendation.
  • curation metadata = administrative metadata in many respects.
  • A selected review of standards follows here:
  • National Library of Australia’s Preserving Access to Digital Information (PADI) metadata schema - http://www.nla.gov.au/padi/metadata.html - includes elements that refer to status: 1. record status - status assigned to the resource for administrative purposes (accepted; on hold; rejected; under review); 2. date status - date the status was assigned, 3. reason for status, 4. review category- a category assigned to a record with "on hold" or "review" status that defines the type of review required.
  • METS - The mets header element <metsHdr> captures metadata about the METS document.
  • TEI and EAD - revision history.