SLC Directors (Mac, Gary, Rich, Matt, with Norma absent) met March
18th to determine SLC RDA practices.

1.  SLC will adopt RDA beginning September 1st, 2013.  This date was
influenced by ebrary accepting no RDA records before October, and no
AACR2 records October or later.

2.  In view of that, SLC will produce only AACR2 records before
September 1st, and only RDA records thereafter, regardless of whether
the derived record is AACR2 or RDA.  No mixed batches will be sent to
clients.  Batches will be all AACR2, RDA, or RDA exported as AACR2
compatible.  Aggregators may receive both RDA and AACR2 compatible if
they wish.  AACR2 compatible (with GMD and abbreviations) will still
have RDA choice of main entry, LDR/18 i, with 040$erda and 33X
removed.

If editing from an SLC record, retain the 001 RSN (so that it will
overwrite), and code LDR/05 c.
  
3.  Most of the changes to create AACR from RDA, or RDA from AACR2,
will be machine generated.  Cataloguers will need to be observant
concerning resources with more than three authors.  The main entry,
Cutter and title 1st indicator will require manual change.  The RDA
100 may become the first AACR2 700.  The AACR2 1st 700 may become RDA
100.
  
Additional authors in 245/$c need not be removed for RDA to AACR2.  
Additional authors in 245/$c and 700s should be added for AACR2 to
RDA.  Transcribe only the first 10 authors, adding [et # al.] for the
remainder.

4.  Try to avoid inclusions by guessing place, publisher, and date; if
required, use ISBD Latin abbreviation inclusions, due to the several
languages of the catalogue among SLC clients.

5.  Add $4 relationship codes to entries, following final mark of 
punctuation.

Codes will be exported to Canadian clients who opt for RDA, and loaded
to OCLC and ebrary for Canadian clients.  Terms coded $e (all lower
case) will be exported to US clients, and loaded to OCLC and ebrary
for US clients.  We will follow British Library practice in exporting
to UK clients, once we know what that practice is.

The $4 codes follow the final mark of punctuation of entries.  Matt
will attempt to replace periods with commas when exporting terms coded
$e, retaining periods after initials and a select list of
abbreviations, e.g., Inc., Ltd.

6.  Do not transcribe affiliations in statement of responsibility, and
remove if present.  This was felt to be less labour intensive than
upgrading punctuation to replace commas with no space semicolons
between information related to different persons.  Also, affiliations
could be mistaken for corporate bodies responsible for content.  Some
corporate body affiliations are multi level, e.g., with departments of
a larger bodies.

7,  Enter 264  4 copyright only if different year from 264  1, even if
264  1 is bracketed.  There would never be 008 t with dates one and
two, unless the two dates are different.  This may require editing.

8.  Use exact unit names as per the RDA Procedures for each client,
e.g., PDF, DVD, Blu-ray.

9.  Use RDA 336-338 media terms, with the exception of 337  
$aelectronic$2isbdmedia.  These are given in Procedures. While ISBD
Area 0 content and media terms are superior to RDA's, it was felt wise
to conform to RDA with the single exception of the misleading
"computer" as a media type, for material more often accessed via
electronic readers.

10.  SLC will not assign  344, 345, 346, 347 or 256; 007 will be coded
instead, and 043 if relevant.
   
11.  SLC will not purchase the Toolkit, but may purchase two print
copies, one for the Rich head cataloguer and one for Gary the quality
control cataloguer.  Cataloguers may ask them for guidance.  
Cataloguers are encouraged to use the MRIs, the Procedures, and this
cheat sheet:

http://special-cataloguing.com/node/1397


   __       __   J. McRee (Mac) Elrod (m...@slc.bc.ca)
  {__  |   /     Special Libraries Cataloguing   HTTP://www.slc.bc.ca/
  ___} |__ \__________________________________________________________

Reply via email to