We send our current cataloging files to Backstage on the first of every month.  Our October file has already been processed and returned to us, and I know there were rda records in that file.   This set of options was announced in the blog on October 29, and not distributed to this list until October 31.  This did not give us time to consider them prior to this file being processed.  I am still not certain which option I prefer, but knowing that our October records were processed according to option 1 makes it likely that I will stay with that one for consistency’s sake for the duration of the test period.  I would be very interested in hearing from other libraries as to which option they have chosen and their reasons for doing so.   What are the implications for the test period and thereafter?  What if rda is adopted?  What if it isn’t?  What in-house review procedures are you performing, if any?

Darla Carras
Head, Catalog Management Unit
University Library System
University of Pittsburgh
412-244-7541
dcarras@pitt.edu

From: bslwac-bounces@mailman.xmission.com [mailto:bslwac-bounces@mailman.xmission.com] On Behalf Of Nate Cothran
Sent: Monday, November 01, 2010 5:06 PM
To: 'Backstage Library Works Authority Contol Listserv'
Subject: Re: [BSLWAC] Backstage Plans for RDA Bibliographic Record Handling

An excellent question as to what is considered the default for RDA bib processing.

Here are the list of options (with #1 being the default unless our clients tell us otherwise):

1. Match RDA bibs as if they are AACR2 bibs, so RDA headings are matched against AACR2 authmaster (default)

2. Ignore RDA bibs when our system encounters them as part of mixed file of AACR2 bibs & RDA bibs

3. Match AACR2 headings against AACR2 authmaster, RDA headings against RDA authmaster

4. If no match in #3 above, match AACR2 headings against RDA authmaster, RDA headings against AACR2 authmaster

We have already had a couple requests for option #2 (ignore RDA bibs), though there has been interest for all options.  For #2, we will need to manually separate out the files prior to processing, otherwise option #1 (match RDA as AACR2) will take precedence; however, by late next week our system should be able to ignore these bibs as it runs across them (obviating the need to manually separate the records).

Up to this point, we were undecided as to how to process the RDA bibs and AACR2 bibs.  So some of our clients may have received RDA authorities since our system would attempt to find a suitable match either on an RDA authority or AACR2 authority.  On November 2 (tomorrow), the two authority databases will be maintained separately within our system.  This ensures that your headings are searched only against the authorities you specify, even during the testing phase.

Of course if an RDA authority is available and your processing is setup to match against the RDA authmaster, and there is a match, that matching RDA authority will be returned to your institution.  Starting tomorrow, the only time you should receive new RDA authority records is if you instruct us to match against the RDA authmaster.

We hope to have more concrete numbers as to the number of RDA authorities later this week to give you an idea of how many have been distributed by Library of Congress to Backstage.

Nate Cothran

Backstage Library Works