a metadata application profile for the driade project n.
Skip this Video
Download Presentation
A Metadata Application Profile for the DRIADE Project

Loading in 2 Seconds...

play fullscreen
1 / 10

A Metadata Application Profile for the DRIADE Project - PowerPoint PPT Presentation

  • Uploaded on

A Metadata Application Profile for the DRIADE Project. Sarah Carrier, Jed Dube, Jane Greenberg March 13, 2007 _____________________. What is a Metadata Application Profile?.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'A Metadata Application Profile for the DRIADE Project' - josiah-ward

Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
a metadata application profile for the driade project

A Metadata Application Profile for the DRIADE Project

Sarah Carrier, Jed Dube, Jane Greenberg

March 13, 2007


what is a metadata application profile
What is a Metadata Application Profile?
  • “Application profiles consist of data elements drawn from one or more namespace schemas combined together by implementors and optimised for a particular local application.” (Heery and Patel, 2000)
    • Data Elements: Title, Name, Coverage, Identifier, etc.
    • Namespace schemas: Dublin Core, Data Documentation Initiative (DDI), Darwin Core, PREMIS, Ecological Metadata Language (EML), etc.
why create an application profile
Why create an Application Profile?
  • Single existing schemes are often not sufficient
    • Dublin Core, DDI, other element sets alone do not cover DRIADE needs
  • We look to supplement Dublin Core with others
    • But we may not need all elements (e.g. in DDI or PREMIS)
  • We look to other schemes because we don't want to re-invent the wheel
Object Types:

The publication

The published piece of data in the publication

The dataset behind the published data (supplemental)

An initial data source

Newly created data

(Heterogeneous) Data Types:

Structured labeled data

Structured unlabeled data

Unstructured textual data

Unstructured non-textual data

DRIADE’s application profile – combining a range of metadata to effectively support evolutionary biology data and digital repository functions:

  • Information life cycle:
  • Creation
  • Collection
  • Identification/Organization
  • Rights management
  • Archiving/Preservation
  • Access/Distribution
  • Usage
driade application profile development 1
DRIADE Application Profile Development (1)

A multi-methods approach:

  • Requirement assessment: Identified initial goals and functional requirements based on Dec. 5 meeting, plus amalgam of DRIADE team efforts-to-date. Initial questions included: How many elements are needed? What functions will the scheme support?
  • Content analysis: Examined various metadata schemes and employed the content analysis methodology to identify relevant elements.
    • Which schema is being analyzed and what elements are included?
    • How is the schema defined?
    • In what context was the schema designed, and how is it currently applied?
    • How does the context relate to DRIADE?
  • Crosswalk analysis: Mapped selected elements on spreadsheet for a comparison and selection for the DRIADE application profile. Included examples of element use.
driade application profile development 2
DRIADE Application Profile Development (2)


  • Considered Dec.5th meeting, DRIADE goals, Todd’s demo, data type extraction, keyword sampling,etc.
  • Considered information life-cycle, data object types, data types, metadata life cycle
  • Researched use of standards and recommendations for best practices, case studies
  • Identified potential metadata schemes/elements
  • Developed list of required metadata
  • Mapped required metadata to elements (spreadsheet)
  • Chose elements (Dublin Core where possible--mandatory and required elements from each scheme were considered a priority)
  • Completed Level 1
  • Work ongoing for Level 2
driade application profile
DRIADE Application Profile
  • Level 1 – initial repository implementation
    • metadata support for preservation, access, and basic usage of data
  • Level 2 – full repository implementation
    • (Level 1 plus) support for expanded usage, interoperability, preservation, administration, etc.
  • Level 3 – “next generation” implementation
    • May consider Web 2.0 functionalities
level 1 application profile
Name (DC:Creator)

Title (DC:Title)

Identifier (DC: Identifier)

Fixity? (PREMIS)

Relation (or Project, or Study)

Contributor (DC:Contributor)

Contact (DDI <contact>)

“Rights” (DC: Rights)

Date (DC: Date)

Description (DC: Description)

“Keyword” (DC: Subject)

Data Type (DC: Type)

Format (DC: Format)

Size? (DC: Format, PREMIS)

Software (DDI <software>)

“Locality” (DC: Coverage)

“Date Range” (DC:Coverage)

Species, or ScientificName (Darwin Core)

Level 1 Application Profile
level 2 application profile
Level 2 Application Profile
  • All Level 1 elements, PLUS:
  • Expanded information for preservation
  • More granularity for data description
  • More information about methodology
  • More about known linkages (to publications etc.)
  • Etc.
  • Application Profile Spreadsheet:


  • Application Profile Bibliography/References: