[RDA-L] AACR2 compatible records

2013-03-26 Thread J. McRee Elrod
Below is our letter to clients announcing SLC's implementing
RDA September 1st, and offering AACR2 compatible export of
RDA records.

So far, most libraries are opting from AACR2 compatible
(because of the GMD), and most e-publishers are opting for
both RDA and AACR2 compatible to give their clients the choice.

Should SLC offer to receive RDA records as a .mrc file to
m...@elrod.ca, and return AACR2 compatible records at $.50 each,
with a minimum batch size of 40 records?  Would many non client
libraries be interested in such a service?

===



Dear SLC Client,   18 March 2013



Executive summary: 

SLC will implement the new cataloguing rules Resource Description and
Access (RDA) September 1st, 2013.  This date was selected because
several of you use ebrary for record distribution; ebrary will accept
not RDA records prior to October, and no AACR2 records after that
time.

Batches of records will be all AACR2 prior to September 1st, all RDA
or RDA exported as AACR2 compatible thereafter.

We need to know whether after September 1st you wish RDA records,
AACR2 compatible records, or both (if you are an aggregator or
publisher' the additional format would be $1.00 per record).

Canadian clients receiving RDA will be sent $4 relator codes following
entries, e.g., $4aut for author, as per Library and Archives Canada
practice.  American clients will be sent $e relator terms following
entries, as per Library of Congress practice, e.g., $eauthor.


We look forward to hearing your choices.


=


RDA changes:

In both RDA and AACR2 compatible records, there will be a difference
in form of entry for the books of the Bible, the Qur'an, and
treaties.*   There will be a difference in the choice of main entry,
e.g., always first author regardless of number.  

In RDA records, most abbreviations will be spelled out; there will be
no General Material Designations (GMD) in 245$h, e.g.. 245
$h[electronic resource] will be lacking.   Instead there are three new
media MARC fields, 336-338, e.g.:

336  $atext$2rdacontent 
337  $aelectronic$2isbdmedia**
338  $aonline resource$2rdacarrier


===

AACR2 compatible records:

If you opt for AACR2 compatible records, the 245$h GMD would be
inserted; relator codes after entries would be removed; words normally
abbreviated would be abbreviated (e.g. 100 pages would be 100 p.);
336-338 media terms would be removed.

===

For library clients, changes to your database and ILS required:

Whether or not you opt to accept unchanged RDA records or AACR2
compatible ones, changes to your Integrated Library System (ILS) will
be required to deal with the changes in form of some entries*.

If you opt for RDA records, you will also need to deal with the
absence of GMD and the new media fields 336-338.   We suggest icons,
or mapping to displaying two of the new MARC media fields [338 : 336]
at end of 245$a title proper, or at head of all data, e.g., [online
resource : text].

A fuller list of RDA/AACR2 differences can be sent if you wish, along
with SLC intended choices among RDA's many options.


===


Aggregators and publishers:

Those of you who distribute MARC records with electronic publications
may wish to consult your clients whether they would prefer AACR2
compatible records, or RDA ones, in deciding whether to offer one, 
the other, or the choice of either.  

The charge for receiving AACR2 compatible versions along with RDA
versions, so you may offer the choice, would be $1.00 per record.  We
can also provide UKMARC versions.


===


Open source (i.e. low cost) ILS for libraries:

Koha: http://koha-community.org/demo/

Evergreen: http://open-ils.org/dokuwiki/doku.php?id=community_servers

If you as a library find having changes made to your ILS to
incorporate RDA too expensive, you might consider one of the two open
source ILS given above.  I'm told one has the ability to translate $4
relator codes into terms.

Using one of these open source ILS would mean you need inhouse IT folk to 
configure it.  With the possibility of MARC being replaced by Bibframe 
(markup coding), this is not a good time to invest in an ILS.

===



Sincerely,  Mac

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




*O.T, and N.T. are removed from between Bible and the name of a
book, spelled out if the 

Re: [RDA-L] AACR2 compatible records--Personal reply

2013-03-26 Thread J. McRee Elrod
Deborah Fritz said:

But Mac, what is the point of offering to change spelled out forms of words
to abbreviations and remove 33X fields to make RDA records backwards
compatible with AACR records when OCLC is intending to run machine
conversions to do the reverse and spell out abbreviations and add 33X fields
to make AACR records compatible with RDA records?

What is in OCLC is irrelevant to many libraries.  What is relevant is
what is in their databases, and what their ILS can accommodate.

This is the worst possible time economically for libraries to have to
incur expense to change their ILSs.  Many lack the inhouse IT skills
to download and use one of the freeware ILSs.

We will of course be loading unchanged RDA records to OCLC, for those
clients who have us load, regardless of what is sent the client.


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


Re: [RDA-L] AACR2 compatible records--Personal reply

2013-03-26 Thread Deborah Fritz
Although many libraries don't use OCLC directly, they do end up copying
records from the catalogs of libraries that do. And if OCLC does what they
say they will, even the national libraries will probably have to follow
suit. So I fear that libraries are just going to have to get used to their
records looking either pure AACR, or pure RDA, or a total hybrid mix.

Believe me, I struggled with this, but I am resigned to making MARC Report
less rigid to accommodate the new reality.

Sigh
Deborah

-  -  -  -  -  -  -  -  
Deborah Fritz
TMQ, Inc.
debo...@marcofquality.com
www.marcofquality.com


-Original Message-
From: J. McRee Elrod [mailto:m...@slc.bc.ca] 
Sent: Tuesday, March 26, 2013 6:16 PM
To: debo...@marcofquality.com
Cc: RDA-L@listserv.lac-bac.gc.ca
Subject: Re: [RDA-L] AACR2 compatible records--Personal reply

Deborah Fritz said:

But Mac, what is the point of offering to change spelled out forms of 
words to abbreviations and remove 33X fields to make RDA records 
backwards compatible with AACR records when OCLC is intending to run 
machine conversions to do the reverse and spell out abbreviations and 
add 33X fields to make AACR records compatible with RDA records?

What is in OCLC is irrelevant to many libraries.  What is relevant is what
is in their databases, and what their ILS can accommodate.

This is the worst possible time economically for libraries to have to incur
expense to change their ILSs.  Many lack the inhouse IT skills to download
and use one of the freeware ILSs.

We will of course be loading unchanged RDA records to OCLC, for those
clients who have us load, regardless of what is sent the client.


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