[DCRM-L] BSC response to OCLC merge proposal

Valerie Buck valerie_buck at byu.edu
Fri Nov 15 10:03:34 MST 2013


Thanks for writing the letter, Nina!

From: dcrm-l-bounces at lib.byu.edu [mailto:dcrm-l-bounces at lib.byu.edu] On Behalf Of Schneider, Nina
Sent: Friday, November 15, 2013 9:57 AM
To: DCRM Revision Group List (dcrm-l at lib.byu.edu)
Subject: [DCRM-L] FW: BSC response to OCLC merge proposal

FYI. Below is an email I sent on behalf of BSC in response to a proposal by OCLC to merge records based on place of publication. If you feel strongly about this issue, I would encourage you to contact Cynthia Whitacre directly. Her email is below.

Please let me know if you have any questions.


+---------------
Nina M. Schneider
Chair, RBMS Bibliographic Standards Committee

Head Cataloger
William Andrews Clark Memorial Library
2520 Cimarron Street
Los Angeles, CA  90018
(323) 731-8529

nschneider at humnet.ucla.edu<mailto:nschneider at humnet.ucla.edu>
http://www.humnet.ucla.edu/humnet/clarklib/



From: Whitacre,Cynthia [mailto:whitacrc at oclc.org]
Sent: Friday, November 15, 2013 8:44 AM
To: Schneider, Nina
Subject: RE: BSC response to OCLC merge proposal

Thank you!

From: Schneider, Nina [mailto:nschneider at humnet.ucla.edu]
Sent: Friday, November 15, 2013 11:38 AM
To: Whitacre,Cynthia
Cc: 'bsc at rbms.info' (bsc at rbms.info<mailto:bsc at rbms.info>)
Subject: BSC response to OCLC merge proposal

Dear Cynthia,

On behalf of the RBMS Bibliographic Standards Committee, I thank you for the opportunity to comment on OCLC's proposed options for place of publication. The majority opinion is that Option A is the most desirable.

Requiring different WorldCat records for different places of publication is one way to avoid conflation of different editions or issues. As one of our colleagues pointed out, "Editions published in different places really can be different editions. They may have many textual differences that are not indicated at all on the title page. The difference in imprint may be the only clue in the catalog record that they are not the same text." There are also many special collections/rare materials records that haven't been coded bdrb or dcrb or dcrm[x] and fall outside of the 1830 cut-off date. These copies, if published in different places, may  have significant differences that can prove valuable to a scholar, whether or not these differences are obvious from the title page.

Although OCLC may believe that "[e]nd users really don't care about these distinctions when it comes to obtaining the content and find the multiple records confusing," we have found the opposite to be true for scholars who use the catalog as a tool to determine the holdings of a particular institution. In contrast to the general user who is satisfied with the content of a work or expression, scholars increasingly want information about distinct manifestations, even when very similar. Conflating and confusing places of publication may remove redundant multiple records, but it will also remove distinctions between manifestations. End users (both researchers and staff) in academic libraries, particularly those conducting research in rare materials repositories, value more information, not less. Creating or retaining separate records for different places of publication must continue.

We would like to note that Option A is preferred over Option C, for much the same reason. As another colleague has pointed out, “If it is inappropriate to merge records for two paper books whose records only differ in place of publication because they are in fact separate manifestations, it is exactly as inappropriate to merge records for the digital copies of those two books. If the two paper books are indeed separate manifestations, so are digital copies of those two books.”

Thank you for your consideration.

Nina

+---------------
Nina M. Schneider
Chair, RBMS Bibliographic Standards Committee

Head Cataloger
William Andrews Clark Memorial Library
2520 Cimarron Street
Los Angeles, CA  90018
(323) 731-8529

nschneider at humnet.ucla.edu<mailto:nschneider at humnet.ucla.edu>
http://www.humnet.ucla.edu/humnet/clarklib/



From: Program for Cooperative Cataloging [mailto:BIBCO at LISTSERV.LOC.GOV] On Behalf Of Whitacre,Cynthia
Sent: Tuesday, October 29, 2013 9:57 AM
To: BIBCO at LISTSERV.LOC.GOV<mailto:BIBCO at LISTSERV.LOC.GOV>
Subject: [BIBCO] OCLC matching/merging question for BIBCO: place of publication

Hello BIBCO Colleagues:

This is an admittedly long message, but please read all of it, as your opinion and thoughts are requested.
OCLC is contemplating making a change in our “when to input a new record” standards as published in Bibliographic Formats and Standards Chapter 4, as well as in our internal merging standards for what is considered a duplicate.  We’d like your help in reaching a decision.  The element in question is the place of publication.

Currently in Chapter 4 of BFAS (http://www.oclc.org/bibformats/en/input.html) under 260 subfield a (we know we need to add 264 to this) we list some instances where minor differences in place are acceptable for considering the records to be the same.  However, the basic statement says that “differences in the place of publication justify a new record.”

One of the reasons we have traditionally NOT merged “duplicate” records when everything else is the same is when place of publication differs.  Here is what our current internal merge instructions say:
260
Subfield $a guidelines
•         Records may be considered duplicates for merge even with the absence or presence of the subfield a.
•         Always match 1st place of publication.
Examples:
•         New York matches New York, Toronto
•         London, Orlando matches London, Toronto
•         New York does not match Toronto, New York
•         New York, Bombay does not match Bombay, New York
Note:  Places of publication within the same country are considered a match and justify a merge.
•         New York, Chicago matches Chicago, New York
+++++++++++++++++++++++++++++
For example, look at these 3 publication statements from 3 WorldCat records for the same title:
264 1 Cheltenham, UK : ǂb Edward Elgar, ǂc [2013]
260    Cheltenham : ǂb Edward Elgar, ǂc 2013.
260    Northampton, Mass. : ǂb E. Elgar Pub., ǂc 2013.
Under our current OCLC criteria for place, we would merge the first two but not the third (assuming everything else matched).

Looking at the cataloging codes, here’s what AACR2 says:
1.4C5. If two or more places in which a publisher, distributor, etc., has offices are named in the item, give the first named place. Give any subsequently named place that is given prominence by the layout or typography of the source of information. If the first named place and any place given prominence are not in the home country of the cataloguing agency, give also the first of any subsequently named places that is in the home country. Omit all other places.

[cid:image001.jpg at 01CED0C8.CB70D890]

And, RDA says:
2.8.2.4
More Than One Place of Publication
If more than one place of publication is named on the source of information, record the place names in the order indicated by the sequence, layout, or typography of the names on the source of information.
+++++++++++++++++++++++++++++++++
Our thinking, in random order:

•         It has always seemed that cataloger’s judgment is at play regarding what gets recorded, no matter which code is in use.

•         RDA gives a bit more leeway than AACR2.  In our discussions, we are of two minds regarding this.

•         In the past, when the same content was published in two countries (UK publication and US publication for example), it often came out at different times and may have had bibliographic significance.  We are not so certain that is the case today.

•         Many reported duplicates and perceived duplicates exist in WorldCat because of the policy of not matching places of publication in different countries when everything else matches.

•         End users really don’t care about these distinctions when it comes to obtaining the content and find the multiple records confusing

•         Records for remote electronic resources, are often created by content providers through automated means, and careful checking of the actual publication is often not done; thus the accuracy of place of publication may be meaningless in many records for electronic resources.

•         Distinctions like this will continue to matter for rare books.

So, we are left with some choices:
A) Continue with the current policy, and require different WorldCat records for different places of publication
B) Modify the current policy to allow the merging of records (and matching of records) with different places of publication for non-rare materials if everything else matches.
C) Stick with the current policy for tangible resources, but allow matching/merging of records for different places of publication for records for remotely-accessed resources only.
D) Another alternative entirely; suggestions welcome!

We would welcome discussion and input on this matter.  Which of the choices, A, B, or C do you prefer?  If you prefer D, please suggest the alternative that you have in mind.  We have asked BIBCO colleagues, since we believe this is a larger issue with records for monographic materials rather than with records for continuing resources.  Please share your thoughts on the BIBCO list.  If you prefer to send a message directly to OCLC, send it to askqc at oclc.org<mailto:askqc at oclc.org>, as that will go to the appropriate people.  We welcome comments through November 15, as we will be discussing this again at OCLC the week of November 18 to try to reach a decision.

Thank you!

Cynthia M. Whitacre
Manager, WorldCat Quality & Partner Content Dept.
OCLC
800-848-5878, ext. 6183
whitacrc at oclc.org<mailto:whitacrc at oclc.org>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20131115/6d8ffd03/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 39814 bytes
Desc: image001.jpg
URL: <http://listserver.lib.byu.edu/pipermail/dcrm-l/attachments/20131115/6d8ffd03/attachment-0001.jpg>


More information about the DCRM-L mailing list