U.S. Geological Survey

USGS NSDI Tools for creation of formal metadata
Dublin Core tags in mp's HTML output

This note is intended to explain how mp maps FGDC CSDGM elements to Dublin Core elements in the META tags of the HEAD section of its HTML output. If you are in doubt about what is explained here, the best information is always going to be found in the source code of mp, in the file html.c at this writing.

The Dublin Core tags are identified using a LINK tag in the HEAD element, placed before the META elements containing the element values. The LINK tag is written as follows:

<link rel=schema.dc href="http://purl.org/metadata/dublin_core">

Other META tags are written in the following form:

<meta name="dc.element" content="stuff">
where element is replaced with the Dublin Core element name and stuff is replaced with the element's value as indicated below.

Dublin CoreImplementation by mp
TITLE Citation: Title
CREATOR Citation: Originator

If Originator repeats, all are included, space-delimited.

SUBJECT Theme: Theme_Keyword

If Theme_Keyword repeats, all are included, space-delimited. Note that Theme_Keyword_Thesaurus is ignored.

DESCRIPTION Description: Abstract
PUBLISHER Metadata_Contact: Contact_Organization

If no Contact_Organization is found,

Metadata_Contact: Contact_Person

CONTRIBUTOR Identification_Information: Data_Set_Credit
DATE Citation: Publication_Date
TYPE Identification_Information: Geospatial_Data_Presentation_Form

If Geospatial_Data_Presentation_Form is not found, the value is given as data.structured-text.

FORMAT Distribution_Information: Standard_Order_Process: Digital_Form: Format_Name

A separate dc.format element is entered for each Format_Name for each Standard_Order_Process.

IDENTIFIER Citation: Online_Linkage

This will not be unique; only the first occurrence is used.

SOURCE Distribution_Information: Resource_Description

This will not be unique; only the first occurrence is used.

LANGUAGE en

RELATION Citation: Larger_Work_Citation: Title
COVERAGE This is not specified directly but is decomposed into the quantitative and qualitative spatial and temporal components below.
COVERAGE.x.min West_Bounding_Coordinate
COVERAGE.x.max East_Bounding_Coordinate
COVERAGE.y.min South_Bounding_Coordinate
COVERAGE.y.max North_Bounding_Coordinate
COVERAGE.placeName Place: Place_Keyword

If Place_Keyword repeats, all occurrences are included, set apart by spaces. Note that Place_Keyword_Thesaurus is ignored.

COVERAGE.t.min Time_Period_of_Content: Range_of_Dates/Times: Beginning_Date

If Beginning_Time is present, it is included, separated from the date by T.

COVERAGE.t.max Time_Period_of_Content: Range_of_Dates/Times: Ending_Date

If Ending_Time is present, it is included, separated from the date by T.

COVERAGE.periodName Temporal: Temporal_Keyword

If Temporal_Keyword repeats, all occurrences are included, set apart by spaces. Note that Temporal_Keyword_Thesaurus is ignored.

RIGHTS Access_Constraints and Use_Constraints, tagged simply by name.


This file is <http://geology.usgs.gov/tools/metadata/tools/doc/dublin.html>
Maintained by Peter Schweitzer
Last updated 21-Nov-1997