But I think the main reason for adding it in the first place was for easy conversion of 440 to 830. Changing the order of subfields would negate this.
-----Original Message----- From: bslwac-bounces@mailman.xmission.com [mailto:bslwac-bounces@mailman.xmission.com] On Behalf Of Adam L. Schiff Sent: Thursday, September 24, 2009 1:32 PM To: Backstage Library Works Authority Contol Listserv Subject: Re: [BSLWAC] $x now valid in 8XX series fields - your feedback requested
I believe that if $x is supplied in the 8XX field, it should be put AFTER the series numbering, if there is any. It should not be preceded by a comma, as there is no AACR2 instruction to punctuate in this way. Therefore, it should always follow the period that ends the series added entry.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Adam L. Schiff Principal Cataloger University of Washington Libraries Box 352900 Seattle, WA 98195-2900 (206) 543-8409 (206) 685-8782 fax aschiff@u.washington.edu http://faculty.washington.edu/~aschiff ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On Thu, 24 Sep 2009, Webber, Ruth wrote:
Along with many others I do not believe this change
concerning the $x would be helpful for us.
Ruth Webber
Associate Librarian
Worcester State College
Worcester MA
______________________________________________________________________
______________________________________________
From: bslwac-bounces@mailman.xmission.com [mailto:bslwac-bounces@mailman.xmission.com] On Behalf Of Judy Archer Sent: Thursday, September 10, 2009 5:02 PM To: Chad Cluff; Backstage Library Works Authority Contol Listserv Subject: [BSLWAC] $x now valid in 8XX series fields - your feedback requested
Hello Everyone, we are looking for feedback from our community:
MARC Proposal No. 2008-06 requested that $x ISSN's be allowed in 8XX fields (http://www.loc.gov/marc/marbi/2008/2008-06.html) and the proposal was approved by Library of Congress on October 2, 2008. Just recently OCLC has decided to begin allowing $x too (see their July 2009 Technical Bulletin 257 found at: http://www.oclc.org/support/documentation/worldcat/tb/257/default.htm.
With LC's switch from 440 to 490 and our programming changes to accommodate this, many of you are now getting $x ISSN subfields in your Bibliographic 8XXs. This has been causing some concern and at least in one scenario, it creates a problem situation as follows:
original bib headings: 490_1 $aSTI/PUB ;$v1343 490_1 $aSafety reports series,$x1020-6450 ;$vno. 58 830_0 $aSafety reports series ;$vno. 58.
after processing: 490_1 $aSTI/PUB ;$v1343 490_1 $aSafety reports series,$x1020-6450 ;$vno. 58 830_0 $aSafety reports series ;$vno. 58. 830_0 $aSafety reports series,$x1020-6450 ;$vno. 58.
The resulting 830s happened this way because the 8XXs must link up with 490-1's. The system assumes the first 8XX belongs to the first 490-1 so it retained "Safety report series ;$vno. 58." Since it "thought" there was no 8XX for the second 490-1 an 8XX was created for it. Unfortunately it was the first 490-1 that was missing a linking 8XX.
What is your practice regarding 8XX $x? Since this is now an allowable subfield and we follow LC procedures, what will this do to your system?
Your feedback would be very welcome and much appreciated. Feel free to respond to this e-mail or talk about it on our Forum at: http://ac.bslw.com/community/forum/viewtopic.php?f=10&t=34
Thanks, Judy
--
Judy Archer
MARS Project Manager
Backstage Library Works
1-800-288-1265 ext. 254
jarcher@bslw.com