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 Core Implementation by mp
TITLECitation: Title
CREATORCitation: Originator
If Originator repeats, all are included, space-delimited.
SUBJECTTheme: Theme_Keyword
If Theme_Keyword repeats, all are included, space-delimited. Note that Theme_Keyword_Thesaurus is ignored.
DESCRIPTIONDescription: Abstract
PUBLISHERMetadata_Contact: Contact_Organization
If no Contact_Organization is found, Metadata_Contact: Contact_Person
CONTRIBUTORIdentification_Information: Data_Set_Credit
DATECitation: Publication_Date
TYPEIdentification_Information: Geospatial_Data_Presentation_Form
If Geospatial_Data_Presentation_Form is not found, the value is given as data.structured-text.
FORMATDistribution_Information: Standard_Order_Process: Digital_Form: Format_Name
A separate dc.format element is entered for each Format_Name for each Standard_Order_Process.
IDENTIFIERCitation: Online_Linkage
This will not be unique; only the first occurrence is used.
SOURCEDistribution_Information: Resource_Description
This will not be unique; only the first occurrence is used.
LANGUAGEen
RELATIONCitation: Larger_Work_Citation: Title
COVERAGEThis is not specified directly but is decomposed into the quantitative and qualitative spatial and temporal components below.
COVERAGE.x.minWest_Bounding_Coordinate
COVERAGE.x.maxEast_Bounding_Coordinate
COVERAGE.y.minSouth_Bounding_Coordinate
COVERAGE.y.maxNorth_Bounding_Coordinate
COVERAGE.placeNamePlace: Place_Keyword
If Place_Keyword repeats, all occurrences are included, set apart by spaces. Note that Place_Keyword_Thesaurus is ignored.
COVERAGE.t.minTime_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.maxTime_Period_of_Content: Range_of_Dates/Times: Ending_Date
If Ending_Time is present, it is included, separated from the date by T.
COVERAGE.periodNameTemporal: Temporal_Keyword
If Temporal_Keyword repeats, all occurrences are included, set apart by spaces. Note that Temporal_Keyword_Thesaurus is ignored.
RIGHTSAccess_Constraints and Use_Constraints, tagged simply by name.