Print

Print


Hi,

Thank you all for replies! I got some ideas and I think we will be able to somehow solve it now.

Ray, it´s good to hear that it will be probably recommended to create separate originInfos  for separate 264s in the future, so we wouldn´t go against the official MODS documentation if we decide to implement it in our system this way.

Have a great day,
Miroslava

Mgr. Miroslava Beňačková
Metadatová specialistka  |  Metadata Specialist
Odbor digitálních fondů | Digital Collections Division
Národní knihovna České republiky | The National Library of the Czech Republic
Klementinum 190, Praha 1
[log in to unmask]<mailto:[log in to unmask]> | www.nkp.cz<http://www.nkp.cz/>
+420 221 663 574
Budova: Hostivař
Místnost: 421

[cid:[log in to unmask]]

TENTO E-MAIL NEMÁ POVAHU OBCHODNÍ NABÍDKY, PŘIJETÍ NABÍDKY S DODATKEM NEBO ODCHYLKOU SE VYLUČUJE. TENTO MAIL NEMÁ POVAHU PŘEDSMLUVNÍ INFORMACE. VEŠKERÁ KOMUNIKACE MEZI STRANAMI MUSÍ BÝT PROVEDENA PÍSEMNĚ S TÍM, ŽE DOKUD NENÍ JAKÝKOLIV ÚKON A JEHO OBSAH POTVRZEN DRUHOU STRANOU, NELZE JEJ POVAŽOVAT ZA JEDNÁNÍ, KTERÉ BY OSOBĚ, KTERÁ JEJ UČINILA, ZAKLÁDALO JAKÉKOLIV NÁROKY VŮČI DRUHÉ STRANĚ.

From: Metadata Object Description Schema List [mailto:[log in to unmask]] On Behalf Of Denenberg, Ray
Sent: Tuesday, February 19, 2019 4:17 PM
To: [log in to unmask]
Subject: Re: [MODS] questions about marc21 to mods mapping

Hi Miroslava,
On your second question – the current MODS documentation is silent on whether there should be one or separate originInfo elements for separate 264s. However the documentation is currently being updated and (tentatively) will recommend separate originInfo elements for each 264. (This wouldn’t be mandated because that would invalidate current MODS records.)

On the first question … when all this information is crammed into a single originInfo, it’s easy to get confused.  But if there are separate originInfo elements, and each has a date, couldn’t that information (earliest, intervening, latest, etc.) be derivable from those dates?

Ray

From: Metadata Object Description Schema List <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Ashton, Jan
Sent: Tuesday, February 19, 2019 6:18 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [MODS] questions about marc21 to mods mapping

Hi Miroslava,

For your first question if you mean that 264 First Indicator = 3 (Current/Latest) you could possibly use <dateOther type=”current/latest”> or some similar ‘type’ attribute value that you think would work best for you.

Apologies if I have misunderstood.

Best wishes,

Jan

________________________________
[http://www.bl.uk/email/logo100.gif]



Jan Ashton
Collection Metadata Analyst
Metadata Standards

The British Library
Boston Spa
Wetherby
West Yorkshire
LS23 7BQ

www.bl.uk<http://www.bl.uk/>



[http://www.bl.uk/email/imageright.gif]<http://www.bl.uk/email/banner.htm>

T +44 (0) 1937 546603
[log in to unmask]<mailto:[log in to unmask]>

________________________________

From: Metadata Object Description Schema List <[log in to unmask]<mailto:[log in to unmask]>> On Behalf Of Benacková Miroslava
Sent: 19 February 2019 07:34
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: [MODS] questions about marc21 to mods mapping

Dear MODS Listserv community,

I am turning to you to ask for your thoughts on two problems we at our department are currently struggling with.


1.       One of our data suppliers asked us how could they display the temporal information from MARC21 field 264 subfield 3 in MODS. According to mappings and stylesheets available at http://www.loc.gov/standards/mods/mods-conversions.html , there is no designated way how to get 264$3 to MODS. We feel like putting it simply to dateIssued would be a simplification and the information could lose some of its value. Do you map this subfield to MODS? If yes, where to?

2.       This may be a  matter of our stylesheet template, however: when you have a multiple 264 field in the catalogue, does all the information map to one mods:originInfo or are separate mods:originInfos created for each field? In our case, it merges into one originInfo and lists first all the publishers, then all the places and then all the dateIssued, which can be quite confusing. We are looking into how to solve the problem and how to eventually designate what  kind of information is inside said originInfo. Any recommendations?

Thank you in advance for you help and have a great day!

Mgr. Miroslava Beňačková
Metadatová specialistka  |  Metadata Specialist
Odbor digitálních fondů | Digital Collections Division
Národní knihovna České republiky | The National Library of the Czech Republic
Klementinum 190, Praha 1
[log in to unmask]<mailto:[log in to unmask]> | www.nkp.cz<http://www.nkp.cz/>
+420 221 663 574
Budova: Hostivař
Místnost: 421

[cid:[log in to unmask]]

TENTO E-MAIL NEMÁ POVAHU OBCHODNÍ NABÍDKY, PŘIJETÍ NABÍDKY S DODATKEM NEBO ODCHYLKOU SE VYLUČUJE. TENTO MAIL NEMÁ POVAHU PŘEDSMLUVNÍ INFORMACE. VEŠKERÁ KOMUNIKACE MEZI STRANAMI MUSÍ BÝT PROVEDENA PÍSEMNĚ S TÍM, ŽE DOKUD NENÍ JAKÝKOLIV ÚKON A JEHO OBSAH POTVRZEN DRUHOU STRANOU, NELZE JEJ POVAŽOVAT ZA JEDNÁNÍ, KTERÉ BY OSOBĚ, KTERÁ JEJ UČINILA, ZAKLÁDALO JAKÉKOLIV NÁROKY VŮČI DRUHÉ STRANĚ.



******************************************************************************************************************
Experience the British Library online at www.bl.uk<http://www.bl.uk/>
The British Library’s latest Annual Report and Accounts : www.bl.uk/aboutus/annrep/index.html<http://www.bl.uk/aboutus/annrep/index.html>
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook<http://www.bl.uk/adoptabook>
The Library's St Pancras site is WiFi - enabled
*****************************************************************************************************************
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask]<mailto:[log in to unmask]> : The contents of this e-mail must not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.
*****************************************************************************************************************
Think before you print