Print

Print


How about:

<originInfo>
  <place><placeTerm>Haarlem</placeTerm></place>
  <publisher>Nederlands B©¦belgenootschap</publisher>
  <dateIssued>1993</dateIssued>
  <copyrightDate>1993</copyrightDate>
</originInfo>
<originInfo>
  <place><placeTerm>Brussel</placeTerm></place>
  <publisher>Belgisch B©¦belgenootschap</publisher>
  <dateIssued>1993</dateIssued>
</originInfo>

Only need copyrightDate in one, I think.  It's not part of the "event" of publication.

Laura


-----Original Message-----
From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Catherine H. Phan
Sent: Monday, April 02, 2012 11:33 AM
To: [log in to unmask]
Subject: Re: [MODS] MARC to MODS mapping: originInfo

Where would you put the date in this? In both instances of <originInfo>?

Thanks,
Cat

On 3/30/2012 2:31 PM, Ray Denenberg, Library of Congress wrote:
> From: Lian Wintermans
>
> ....
>
>  > I would like to preserve the place-publisher pairs in the MODS
> output. How can
>
>  > this be done? I do not like to rely on the order of the <place> and
> <publisher>
>
>  > elements, since that is not the way to couple related elements in XML.
>
> Use separate instances of originInfo
>
> Thus:
>
> <mods:originInfo>
>
> <mods:place>
>
> <mods:placeTerm>Haarlem</mods:placeTerm>
>
> </mods:place>
>
> <mods:publisher>Nederlands B©¦belgenootschap</mods:publisher>
>
> </mods:originInfo>
>
> <mods:originInfo>
>
> <mods:place>
>
> <mods:placeTerm>Brussel</mods:placeTerm>
>
> </mods:place>
>
> <mods:publisher>Belgisch B©¦belgenootschap</mods:publisher>
>
> </mods:originInfo>
>
> That in fact is the reason why originInfo is defined to be repeatable.
>
> --Ray
>
> *From:*Metadata Object Description Schema List
> [mailto:[log in to unmask]] *On Behalf Of *Lian Wintermans
> *Sent:* Friday, March 30, 2012 12:04 PM
> *To:* [log in to unmask]
> *Subject:* [MODS] MARC to MODS mapping: originInfo
>
> Dear all,
>
> I have some questions regarding the MARC to MODS mapping for the
> <originInfo> element.
>
> According to the MARC-MODS mapping and the MODS Guidelines each 260$a
> goes into separate <place><placeTerm> elements, and each 260$b goes
> into separate <publisher> elements. But what should one do when the
> MARC record has multiple place-publisher pairs? E.g.
>
> <datafieldtag="260"ind1=" "ind2=" ">
>
> <subfieldcode="a">Haarlem :</subfield>
>
> <subfieldcode="b">Nederlands B©¦belgenootschap ;</subfield>
>
> <subfieldcode="a">Brussel :</subfield>
>
> <subfieldcode="b">Belgisch B©¦belgenootschap,</subfield>
>
> <subfieldcode="c">cop. 1993.</subfield>
>
> </datafield>
>
> I assumed the corresponding MODS would be
>
> <mods:originInfo>
>
> <mods:place>
>
> <mods:placeTerm>Haarlem</mods:placeTerm>
>
> </mods:place>
>
> <mods:publisher>Nederlands B©¦belgenootschap</mods:publisher>
>
> <mods:place>
>
> <mods:placeTerm>Brussel</mods:placeTerm>
>
> </mods:place>
>
> <mods:publisher>Belgisch B©¦belgenootschap</mods:publisher>
>
> <mods:copyrightDate>1993</mods:copyrightDate>
>
> [...]
>
> </mods:originInfo>
>
> But the MARCXML to MODS (version 3.4) stylesheet produced the following:
>
> <originInfo>
>
> <place>
>
> <placeTermtype="code"authority="marccountry">ne</placeTerm>
>
> </place>
>
> <place>
>
> <placeTermtype="text">Haarlem</placeTerm>
>
> </place>
>
> <place>
>
> <placeTermtype="text">Brussel</placeTerm>
>
> </place>
>
> <publisher>Nederlands B©¦belgenootschap</publisher>
>
> <publisher>Belgisch B©¦belgenootschap</publisher>
>
> <dateIssued>cop. 1993</dateIssued>
>
> <dateIssuedencoding="marc">1993</dateIssued>
>
> [...]
>
> </originInfo>
>
> I would like to preserve the place-publisher pairs in the MODS output.
> How can this be done? I do not like to rely on the order of the
> <place> and <publisher> elements, since that is not the way to couple
> related elements in XML.
>
> Besides this, I would like to ask about the mapping and transformation
> of publisher statements that include square brackets for place and/or
> publisher.
>
> Should I include square brackets in the MODS output, or should I
> remove them and use the ˇ°suppliedˇ± (yes) attribute? Anyway, the MARC
> to MODS stylesheet seems to transform this incorrectly (removing the
> opening square bracket, but retaining the end square bracket).
>
> E.g. the following input:
>
> <marc:datafieldtag="260"ind1=" "ind2=" ">
>
> <marc:subfieldcode="a">[Schiedam] :</marc:subfield>
>
> <marc:subfieldcode="b">MainPress ;</marc:subfield>
>
> <marc:subfieldcode="a">[Den Haag] :</marc:subfield>
>
> <marc:subfieldcode="b">Academic Service,</marc:subfield>
>
> <marc:subfieldcode="c">cop. 2009.</marc:subfield>
>
> </marc:datafield>
>
> is transformed into:
>
> <originInfo>
>
> <place>
>
> <placeTermtype="code"authority="marccountry">ne</placeTerm>
>
> </place>
>
> <place>
>
> <placeTermtype="text">Schiedam]</placeTerm>
>
> </place>
>
> <place>
>
> <placeTermtype="text">Den Haag]</placeTerm>
>
> </place>
>
> <publisher>MainPress</publisher>
>
> <publisher>Academic Service</publisher>
>
> <dateIssued>cop. 2009</dateIssued>
>
> <dateIssuedencoding="marc">2009</dateIssued>
>
> <issuance>monographic</issuance>
>
> </originInfo>
>
> I am really interested in your treatment of these <originInfo> elements.
> I hope you can give me some practical advice to solve these problems,
> both in the mapping and in the stylesheet.
>
> With kind regards, Lian.
>
> Lian Wintermans
> Metadata Specialist
>
> E [log in to unmask] <mailto:[log in to unmask]> T (+31) 70
> 3140978
>
>
>
> Koninklijke Bibliotheek, National Library of the Netherlands
> <http://www.kb.nl>
>
>
>
>
>
> Prins Willem-Alexanderhof 5 |2595 BE Den Haag Postbus 90407 |2509 LK
> Den Haag |(070) 314 09 11 |www.kb.nl <http://www.kb.nl/>
>
>
>
>
>
>
>
>
>
> English version <http://www.kb.nl/red/email.html> |Disclaimer
> <http://www.kb.nl/red/disclaimer.html>
>
>
>

--
Catherine H. Phan
Digital Services and Metadata Librarian
UW Digital Collections Center
431 Memorial Library
728 State St.
Madison, WI 53706
608-262-2738
http://uwdc.library.wisc.edu/

________________________________

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).