Over the last couple of years, Backstage created 7 different options for
matching AACR2 access points and RDA access points in special ways. Then
we started whittling that down as certain functionality became outdated
or moot (e.g., 7XX-4 fields being "absorbed" into the authorities as 4XX
fields instead).
As of a month ago, we were down to two options. With RDA Day One already
come and gone (April 1, 2013), we are now down to one option:
1. A bib record's access points will take the best match
regardless of RDA (040 $e rda) or AACR2 status in the authority record.
All of our clients have been "switched" to this new option for matching
authorities, so there is no action required on your part in order to
have this enacted.
As always, please let us know any questions or concerns you may have. It
is through you that we had developed the previous 7 options, as well as
different ways of presenting the reports, and adding new options for RDA
enrichment.
Thanks,
Nate
Nate Cothran
Vice President, Automation Services
25 East 1700 South
Provo, Utah 84606
Phone: +1.800.288.1265, ext. 697
Direct: +1.801.342.5697
nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> *
www.bslw.com <http://www.bslw.com>
Here is another update on the number of RDA authorities received from
the Phase 2 distribution:
NAF = 51,977 total authorities; 45,673 had 040 $e rda - (88%)
Total RDA authorities for Phase 2 (so far):
376,148 name authorities
This should represent the final update for Phase 2 authorities.
Nate Cothran
Vice President, Automation Services
25 East 1700 South
Provo, Utah 84606
Phone: +1.800.288.1265, ext. 697
Direct: +1.801.342.5697
nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Inquiry> *
www.bslw.com <http://www.bslw.com>
