LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


MODS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  September 2003

MODS September 2003

Subject:

Re: Mapping from MODS to Dublin Core

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Fri, 12 Sep 2003 08:50:02 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (235 lines)

A MODS to Dublin Core mapping is available from the our Web site:
http://www.loc.gov/standards/mods/dcsimple-mods.html

There is also further information in the MODS guidelines:
http://www.loc.gov/standards/mods/mods-userguide-lite.html

You might compare what you're done with those-- sorry I haven't had a
chance to look at yours yet.

Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^  Rebecca S. Guenther                                   ^^
^^  Senior Networking and Standards Specialist            ^^
^^  Network Development and MARC Standards Office         ^^
^^  1st and Independence Ave. SE                          ^^
^^  Library of Congress                                   ^^
^^  Washington, DC 20540-4402                             ^^
^^  (202) 707-5092 (voice)    (202) 707-0115 (FAX)        ^^
^^  [log in to unmask]                                          ^^
^^                                                        ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^


On Thu, 11 Sep 2003, Paul Fogel wrote:

> Hi.
> I am new to this list and may have missed any previous discussions on this 
> topic, so forgive me if I am rehashing old news.
> 
> We have been developing a MODS to Dublin Core mapping (using XSLT) to 
> process our METS (in XML) records.  We will be using the resultant DC for 
> indexing purposes.
> 
> My question is, has anyone else done a mapping like this?  I looked around 
> and could not find any examples, so I ended up using the DC to MODS mapping 
> as a foundation to build from.
> I have pasted below an overview of the mapping for review.  How does it look?
> 
> Paul Fogel
> California Digital Library
> [log in to unmask]
> 510.987.0680
> 
> 
> MODS to Dublin Core Mapping Documentation
> By Dublin Core Element, from MODS Element
> Title:
> This is mapped from the <titleInfo><title> field.  A conditional IF 
> statement is included to catch <titleInfo><subTitle> and append it to the 
> title, separated by colon space (: ).
> 
> Creator:
> This is mapped from <name><namePart> when <name><role>creator</role>.  A 
> mapping is also made from the <recordInfo><recordContentSource> element
> 
> Subject:
> This is mapped for each occurrence of:
>        <subject><topic>
>        <subject><name>
>        <subject><titleInfo><title>
>        <name><namePart> - A condition is included so that if <name> 
> contains multiple <namePart> elements, they are concatenated using a space 
> ( ) as a separator.
> 
> Description:
> This is mapped for all occurrences from:
>        <abstract>
>        <tableOfContents>
>        <note>
>        <subject><name><description>
> 
> Publisher:
> Mapped from:
>        <originInfo><publisher>
>        <recordInfo><recordContentSource>
>        <publicationInfo><publisher> (to accommodate early UCPEE encoding 
> practices - this usage is outdated)
> 
> Contributor:
> Mapped from <name><namePart> only when <name><role><text>contributor</text>.
> 
> Date:
> Mapped from:
>        <originInfo><dateIssued>
>        <originInfo><dateCreated>
>        <originInfo><dateCaptured>
>        <originInfo><dateOther>
>        <publicationInfo><dateIssued> (as per Publisher above)
> 
> Type:
> Mapped from <typeOfResource> and <genre>.
> 
> Format:
> Mapped from:
>        <physicalDescription><extent>
>        <physicalDescription><form>
>        <physicalDescription><internetMediaType
>        <physicalDescription><digitalOrigin>
>        <physicalDescription><note>
> 
> Identifier:
> Mapped from <identifier>.  If the element has a TYPE attribute equal to 
> "isbn", "issn", "lccn", "doi" or "uri", then this value precedes the data, 
> separated by colon space.  Example:  <identifier>uri: 
> http://www.ucpress.edu/books/pages/6178.html&amp;isbn=0520081994</identifier>
> If there is no TYPE attribute, or if it is not set to one of these values, 
> the data is mapped without qualification.
> 
> Source:
> Mapped from <relatedItem> only when the attribute TYPE is equal to "original".
> 
> Language:
> Mapped from <language>.
> 
> Relation:
> Mapped from <relatedItem> for all occurrences except for those in which the 
> TYPE attribute is equal to "original" (Source, above) or "series" 
> (isPartOf, below).
> 
> Coverage:
> Mapped from:
>        <subject><geographic>
>        <subject><temporal>
>        <subject><hierarchicalGeographic>
>        <subject><cartographic>
>        <classification>
>        <originInfo><place><text>
> The <hierarchicalGeographic> and <cartographic> nodes are flattened so that 
> repeating values as well as sub-elements (and their children) are strung 
> into one element.
> 
> Rights:
> Mapped from <accessCondition>.
> 
> DCTerms:Abstract:
> Mapped from <abstract> - this data is also mapped (see above) into 
> Description so that Unqualified Dublin Core can be extracted without loss.
> 
> DCTerms:Created
> Mapped from <recordInfo><recordCreationDate>.  This is also mapped to Date, 
> so that data is not lost in Unqualified Dublin Core.
> 
> DCTerms:Modified
> Mapped from <recordInfo><recordChangeDate>.  This is also mapped to Date, 
> so that data is not lost in Unqualified Dublin Core.
> 
> DCTerms:isPartOf
> Mapped from <relatedItem> only when the TYPE attribute is equal to 
> "series".  This is also mapped to Relation, so that data is not lost in 
> Unqualified Dublin Core.
> 
> By MODS Element, from Dublin Core Element
> 
> ELEMENT MAPPED TO
> <titleInfo><title>      Title
> <titleInfo><subTitle>   Title, if occurs
> <titleInfo><partNumber> ignored
> <titleInfo><partName>   ignored
> <titleInfo><nonSort>    ignored
> 
> <name><namePart>        Creator, Subject, Contributor
> <name><displayForm>     ignored
> <name><affiliation>     ignored
> <name><role>    Used to assign Creator & Contributor, otherwise ignored.
> <name><description>     Description
> 
> <typeOfResource>        Type
> 
> <genre> Type
> 
> <originInfo><place>     Coverage
> <originInfo><publisher> Publisher
> <originInfo><dateIssued>        Date
> <originInfo><dateCreated>       Date, DCTerms:Created
> <originInfo><dateCaptured>      Date
> <originInfo><dateOther> Date
> <originInfo><edition>   ignored
> <originInfo><issuance>  ignored
> <originInfo><frequency> ignored
> 
> <language>      Language
> 
> <physicalDescription><form>     Format
> <physicalDescription><reformattingQuality>      ignored
> <physicalDescription><internetMediaType>        Format
> <physicalDescription><extent>   Format
> <physicalDescription><digitalOrigin>    Format
> <physicalDescription><note>     Format
> 
> <abstract>      Description, DCTerms:Absctract
> 
> <tableOfContents>       Description
> 
> <targetAudience ignored
> 
> <note>  Description
> 
> <subject><topic>        Subject
> <subject><geographical> Coverage
> <subject><temporal>     Coverage
> <subject><titleInfo><title>     Subject
> (other subelements for titleInfo ignored)
> <subject><name><description>    Subject
> (other subelements for name ignored)
> <subject><hierarchicalGeographic>       Coverage
> (subelements "flattened" to appear in one string)
> <subject><cartographics>        Coverage
> (subelements "flattened" to appear in one string)
> 
> <classification>        Coverage
> 
> <relatedItem>   Source (if type="original")
>          DCTerms:IsPartOf (if type="series")
>          Relation (for all other types)
> (subelements "flattened" to appear in one string)
> 
> <identifier>    Identifier
> (if type is issn, isbn, lccn, uri, or doi, it is applied at beginning of 
> data string; otherwise data is applied as is)
> Ex. <dc:identifier>isbn: 0123456789</dc:identifier>
>       <dc:identifier>12-34567-8901234-5-67</dc:identifier>
> 
> <location>      Ignored
> 
> <accessCondition>       Rights
> 
> <extension>     Ignored
> 
> <recordInfo><recordContentSource>       Creator, Publisher
> <recordInfo><recordCreationDate>        DCTerms:Created
> <recordInfo><recordChangeDate>  DCTerms:Modified
> <recordInfo><recordIdentifier>  Ignored
> <recordInfo><languageOfCataloging>      Ignored
> 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2020
March 2020
February 2020
January 2020
December 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager