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  December 2003

MODS December 2003

Subject:

Re: MODS to Dublin Core mapping stylesheet and documentation

From:

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

Reply-To:

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

Date:

Thu, 18 Dec 2003 13:24:47 -0500

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (177 lines)

I've copied your text below and inserted my comments.

Thanks for getting this start-- we will work on developing this into a
mapping that we can put up.

I do think there are other DC qualified elements that MODS elements will
map to. Perhaps for now we should stick to simple DC, since I didn't think
this was complete in terms of qualified, i.e. dcterms:

MODS to Dublin Core Mapping

By Dublin Core Element, from MODS Element

Title:
//mods/titleInfo/title - A conditional IF statement is included to catch
<titleInfo><subTitle> and append it to the title, separated by colon space
(: ).

RG: You need to deal with multiple titles and alternative titles. Karen
has already mentioned this and I agree-they need to be kept in order and
all be strung together in DC.
I would also string together the other pieces (see below).

Creator:
//mods/name/namePart -  when //mods/name/role[. = 'creator']
//mods/recordInfo/recordContentSource

RG: DC does not deal with "metametadata" and the second one is not
appropriate at all; this is creator of the record.

Subject:
//mods/subject/topic
//mods/subject/name
//mods/subject/titleInfo/title

RG: MODS subject can have any number of subelements in any order, so the
DC value should concatenate them all in one string retaining the
order. Punctuation between them is an issue; if the authority is LCSH,
then you can assume double dashes between each subelement.

Description:
//mods/abstract
//mods/tableOfContents
//mods/note
//mods/subject/name<description>

RG: I wouldn't include subject/name<description>.  Description associated
with subject/name cannot really exist on its own. I would probably drop it
(and of course put the subject/name with Subject or just append it to
subject name.

Publisher:
//mods/originInfo/publisher
//mods/publicationInfo/publisher - to accommodate earlier encoding
practices; this usage is outdated

Contributor:
//mods/name/namePart -  when //mods/name/role/text[. = 'contributor']

RG: There are a few ways to do this; it's difficult to map because of the
distinction in DC between Creator and Contributor. There has been much
discussion (especially in the DC-Usage Board) about using only Contributor
and not Creator, but some people got upset, so that was left open. One way
to do this is to to use Contributor for any name/namePart with a role
other than creator specified. The other way is to decide to map all
name/nameParts to Creator and not use contributor. I would think that the
role with value "contributor" would almost never be used, since it doesn't
add anything. If this were done as you suggest, then there would be no
place for anything that doesn't have role=creator or role=contributor in
MODS. And most probably will have something other than these 2 (or
nothing).

Date:
Mapped from:
//mods/originInfo/dateIssued
//mods/originInfo/dateCreated
//mods/originInfo/dateCaptured
//mods/originInfo/dateOther
//mods/publicationInfo/dateIssued - to accommodate earlier encoding
practices; this usage is outdated

Type:
//mods/typeOfResource
//mods/genre

Format:
//mods/physicalDescription/extent
//mods/physicalDescription/form
//mods/physicalDescription/internetMediaType
//mods/physicalDescription/digitalOrigin
//mods/physicalDescription/note

RG: I would put physicalDescription/note in Description. Not sure that
there's a good place for digitalOrigin; could cram it in either here or
note.

Identifier:
//mods/identifier - If @TYPE= '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.

RG: Since MODS 3.0 now makes a distinction between identifier and
location, <location><url> needs to map to DC identifier. URI usually
doesn't precede the data, so I'm not sure that this helps as you specify
above.

Source:
//mods/relatedItem[@TYPE='original']

Language:
//mods/language

Relation:
//mods/relatedItem - except when relatedItem[(@TYPE='original') or
(@TYPE='series')]

Coverage:
Mapped from:
//mods/subject/geographic
//mods/subject/temporal
//mods/subject/hierarchicalGeographic
//mods/subject/cartographic
//mods/classification
        The hierarchicalGeographic and cartographic nodes are flattened so
that repeating values as well as sub-elements (and their children) are
strung into one element.

RG: why classification?? Classification goes under Subject in DC.

Rights:
//mods/accessCondition

DCTerms:Abstract:
//mods/abstract - this data is also mapped (see above) into Description,
so that data is not lost in Unqualified Dublin Core.

DCTerms:Created
//mods/recordInfo/recordCreationDate.  This is also mapped to Date, so
that data is not lost in Unqualified Dublin Core.

RG: no, this is metadata about the record, and dc:created is about the
resource. Same as mods:dateCreated

DCTerms:Modified
//mods/recordInfo/recordChangeDate.  This is also mapped to Date, so that
data is not lost in Unqualified Dublin Core.

RG: same thing; dc:modified is the date the resource was modified, not the
metadata. Same as mods:dateModified (v. 3)

DCTerms:isPartOf
//mods/relatedItem - when //mods/relatedItem[@TYPE='series'].  This is
also mapped to Relation, so that data is not lost in Unqualified Dublin
Core.

RG: Also, mods/relatedItem type=host

There are other DC qualified elements that have mappings (especially
under relation).

By MODS Element, to Dublin Core Element

ELEMENT MAPPED TO
//mods/titleInfo/title                          title
//mods/titleInfo/subTitle                       title
//mods/titleInfo/partNumber                     ignored
RG: I would concatenate with the rest of the title information.
//mods/titleInfo/partName                       ignored
RG: same as above.

(Left off the rest, since already covered above.)

Rebecca

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

July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
May 2021
November 2020
September 2020
August 2020
July 2020
May 2020
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