We have put together some initial stats for the Phase 1
<http://ac.bslw.com/community/blog/2012/07/set-phasers-to-stun/>
authorities. Although our default is to not return these authorities,
some of our clients have requested that we do so.
In the table below:
* Auth Master - represents total number of authorities for that
client
* Phase 1 - represents total number of Phase 1 authorities
delivered as part of this week's Notification run
* RDA Total - represents total number of RDA authorities that
client currently has in our master file
* Notif Freq - represents how often Notification is run for that
client
This small portion of stats may be useful for clients interested in
number of Phase 1 authorities being returned based on size of authority
database.
Auth Master
Phase 1
RDA Total
Notif Freq
1,208,000
4,966
18
monthly
1,100,000
4,345
19
weekly
597,000
0
215
monthly
576,000
1,126
1
monthly
353,000
714
3
quarterly
314,000
1,067
2
quarterly
151,000
95
3
quarterly
94,000
143
1
quarterly
Nate Cothran
Vice President, Automation Services
533 East 1860 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
We wanted to let everyone know that Phase 1 of the RDA Implementation
has begun.
In our latest update from LC (this week), we received 29,998 Phase 1
authorities. (Note: Phase 1 officially began on July 30, 2012, though we
did verify that LC did not update any Phase 1 authorities last week).
These specific authorities contain the following note field:
667 $a THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS
BEEN REVIEWED AND/OR UPDATED
As we outlined in our post about Phase 1 RDA authorities on July 10,
2012 (link
<http://ac.bslw.com/community/blog/2012/07/set-phasers-to-stun/> ), we
will not be delivering these authorities to our clients unless otherwise
requested. We have had a few clients request to receive these
authorities and we hope to provide some general statistics (size of
database, number of Phase 1 RDA auths returned) in an upcoming post.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
We have quietly rolled out summaries for our online authority control
clients here:
http://ac.bslw.com/mars
After logging in, using your login & password, when you click on the
"Summary" tab in the AC profile it will list all of the current
processing we are doing based on what you have entered in the online
profile.
Summaries are updated each time you save a step in the profile. Each
step, whether completed or not, will have an explanation associated with
it in the summary. Some steps that are "blank" or haven't been filled
out yet represent our default processing and are reflected as such.
We hope this makes it easier on figuring out exactly what our system is
doing for each step of your profile, especially if you would prefer to
see things at a glance.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
Hello Voyager Users,
I had a question about whether your workflow was set up such that you
have Authority Validation turned on for individual catalogers as you
process your Authority Control with Backstage?
It's my understanding that Validation can be turned on for the system as
a whole as well as for individual catalogers. But if it's for individual
catalogers it may be overwhelming with the kinds of error reports to
either ignore or address?
If you can respond on or off the list that would be much appreciated!
Thank you,
Nate
Nate Cothran
Vice President, Automation Services
533 East 1860 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
Earlier this week, we sent out a couple posts (one brief, and one with
more info) about our RDA AC processing options changing. We realized
that we can work with the programming on our side while still giving our
customers enough time to prepare for the new options.
So our current set of 7 options will be replaced by 5 options starting
August 8, 2012. Again, no action is required on your part if you are
using any of the current 7 options to process both your AACR2 & RDA bib
headings.
The main part to keep in mind is that any use of the 7XX-4 in AACR2
authorities will be going away on August 8, 2012. Once we get closer to
that date, we will send out an updated set of options that we imagine
(hope) will be a little easier to follow.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
Our RDA authority control options, which are useful for matching your
AACR2 & RDA bib headings in unique ways, have undergone several
different changes over the past several months. As you may know,
Backstage has employed 7 different options
<http://ac.bslw.com/community/wiki/index.php5/RDA_7.1> for matching
your bib headings against AACR2 and RDA authority records.
During the testing phase, catalogers were asked to create equivalent RDA
versions of headings based on the access points they were reviewing. If
no AACR2 authority existed, then catalogers were asked to create a new
RDA authority record. If an AACR2 authority did exist, however,
catalogers were asked to add an RDA-compliant heading to the existing
AACR2 authority record, in a 7XX-4 field.
Some 18,000+ 7XX-4 fields were added to existing AACR2 authorities
during this testing phase, 80% of which were 700-4 fields (personal
names). Nearly 66% of the total 7XX-4 fields were, byte for byte,
exactly the same as the AACR2 authorized (1XX) version. Almost 97% of
the remaining unique fields were for personal names.
Our RDA options 3.0
<http://ac.bslw.com/community/wiki/index.php5/RDA_7.1#RDA_OPTION_3.0> &
3.5
<http://ac.bslw.com/community/wiki/index.php5/RDA_7.1#RDA_OPTION_3.5>
included the possibility of matching against these 7XX-4 headings and
flipping/changing to the RDA version. We had 8 large academic
institutions and 1 large public library that have requested we apply
either 3.0 or 3.5.
When the 7XX-4 fields were created, their ultimate fate was debated
within the library community:
1. Move the 7XX-4 fields to their own RDA authority, and remove
from existing AACR2 authorities
2. Remove the 7XX-4 fields entirely and just start over for those
particular test records
Eventually, PCC members decided that the RDA headings created within
AACR2 authorities during the testing phase should be removed entirely by
Day One Implementation of RDA
<http://ac.bslw.com/community/blog/2012/07/set-phasers-to-stun/> .
For a while, Backstage has been maintaining 3 separate authorities
databases:
1. AACR2 authorities
2. AACR2 authorities where 7XX has been moved to 1XX (and existing
1XX was moved to 4XX)
3. RDA authorities
Navigating between the 3 databases has proven to be a little tricky on
our side. But we wanted to have options in place that made sense for our
customers. With the 7XX-4 fields being considered effectively obsolete
by PCC, Backstage will consolidate our existing authority databases back
into one cohesive database.
One other reason why we decided to make this change at this time:
* AACR2 authorities deleted, then replaced by an RDA authority
Our system was struggling to link up the older LCCN of the AACR2
authority, which now existed in the new RDA authority (as 010 $z). By
combining the authority databases on our side, we have ensured that the
system will now return authorities that used to be AACR2, but have now
been replaced by RDA authorities.
Due to our handling of older forms of headings
<http://ac.bslw.com/community/wiki/index.php5/Step_6.4> , the older
AACR2 version of the heading will be included as a 4XX in the new RDA
authority record. This gives you the peace of mind that, even though
your replaced record is RDA, your bib headings will change based on that
older link (4XX) within the RDA authority record.
We will also be removing the possibility of matching against 7XX-4
fields, primarily because PCC will be removing them at some point in the
near future. This change is to ensure that we aren't caught flat-footed
when the 7XX-4 fields are ultimately removed. Not doing so would mean we
could potentially be changing bibliographic headings to authorized forms
which will not exist in the coming weeks, potentially resulting in blind
references.
Due to this announcement, RDA options 4.0
<http://ac.bslw.com/community/wiki/index.php5/RDA_7.1#RDA_OPTION_4.0> ,
4.5
<http://ac.bslw.com/community/wiki/index.php5/RDA_7.1#RDA_OPTION_4.5> ,
and 5.0
<http://ac.bslw.com/community/wiki/index.php5/RDA_7.1#RDA_OPTION_5.0>
are also affected since they treat the 7XX-4 as a 4XX during matching.
We have 11 institutions that currently choose one of these last 3
options. This also means we will be updating our RDA authority control
options soon since some of these will be combined into others.
We fully anticipate creating new options or adjusting our existing
options as we get closer to Day One
<http://ac.bslw.com/community/blog/2012/05/rda-naf-conversion-and-day-on
e-implementation/> , as we are continually seeking to fulfill our
customers' needs.
This change is effective after July 20, 2012.
Please let us know any questions you may have.
As always, your feedback is welcome.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
We have a quick announcement, which will be followed by a much more
in-depth explanation for those that may be interested.
After July 20, 2012, Backstage will no longer be using the 7XX-4 fields
in AACR2 authorities in any manner. Since PCC will eventually have these
fields removed from AACR2 authority records (sometime prior to Day One
Implementation of RDA), Backstage wanted to ensure its processing is in
place ahead of time so we are not scrambling to adjust when it does
happen.
http://ac.bslw.com/community/wiki/index.php5/RDA_7.1
In short, this means that RDA options 3.0, 3.5, 4.0, 4.5, and 5.0 will
undergo some necessary changes
* Options 3.0 & 3.5 included the possibility of matching and
flipping to the 7XX-4 version
* Options 4.0, 4.5, and 5.0 treated the 7XX-4 as a 4XX for
matching purposes
We have 20 institutions that currently choose one of the options listed
above. No action is required on your part, as the processing that
included the 7XX-4 will essentially be excised from each respective RDA
option. We anticipate eventually combining certain of these options as
some will be redundant (e.g., Options 1.0 & 4.0 are now essentially the
same option).
Please see the next listserv post about this subject if you would like
additional information.
As always, your feedback is welcome.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
Day One for RDA Implementation
* March 31, 2013
Phase 1
* Mid-July 2012 (completion estimate)
* 313,000 authorities
* Change: addition of 667 note
* 3-4 week period
Phase 2
* March 31, 2013 (or as close to it as possible)
* 328,000 authorities
* Changes: 1XX, 4XX, 5XX
* 3-4 week period
In Phase 1, 667 fields are being added to 313,000 authorities whose 1XX
fields cannot be used as-is under RDA. These 1XX are also not
susceptible to an automated change.
There are three categories of records which fall under Phase 1:
1. AACR2 whose 1XX contains elements at variance with RDA practice
2. Pre-AACR2 records
3. AACR2 compatible heading records
Since a 667 note to the effect of "THIS 1XX FIELD CANNOT BE USED UNDER
RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND UPDATED" is being added to
the 313,000 authorities, Backstage does not recommend replacing these
particular authorities at this time. At a later date, when these
authorities have been updated in other ways, Backstage can return these
as part of our standard set of updated authorities (new, change, delete)
from the Notification service.
Backstage will default to not delivering these particular updates for
Phase 1, unless otherwise requested by our libraries.
In Phase 2, automated changes that can be made to 1XX, 4XX, and/or 5XX
are done. Most of the changes involve expanding abbreviations, or the
addition/removal of specific fields (link
<http://ac.bslw.com/community/blog/2012/05/rda-naf-conversion-and-day-on
e-implementation/> ).
As Phase 2 is set to be completed as close to Day One as possible (March
31, 2013), we hope this gives our clients enough time to establish
procedures on their end in order to handle the large influx of updates
scheduled to arrive. These updates are planned to cover a 3-4 week time
period, where approximately 328,000 records will be re-issued with the
changes listed above. Backstage does recommend that our libraries
receive these particular updates.
Backstage will default to delivering these particular updates for Phase
2, unless otherwise requested by our libraries.
As always, please let us know any questions you may have about the above
information.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
--
Chad Cluff
Programming/IT Dept. Manager
ccluff(a)bslw.com
800.288.1265 x696
Day One for RDA Implementation
* March 31, 2013
Phase 1
* Mid-July 2012 (completion estimate)
* 313,000 authorities
* Change: addition of 667 note
* 3-4 week period
Phase 2
* March 31, 2013 (or as close to it as possible)
* 328,000 authorities
* Changes: 1XX, 4XX, 5XX
* 3-4 week period
In Phase 1, 667 fields are being added to 313,000 authorities whose 1XX
fields cannot be used as-is under RDA. These 1XX are also not
susceptible to an automated change.
There are three categories of records which fall under Phase 1:
1. AACR2 whose 1XX contains elements at variance with RDA practice
2. Pre-AACR2 records
3. AACR2 compatible heading records
Since a 667 note to the effect of "THIS 1XX FIELD CANNOT BE USED UNDER
RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND UPDATED" is being added to
the 313,000 authorities, Backstage does not recommend replacing these
particular authorities at this time. At a later date, when these
authorities have been updated in other ways, Backstage can return these
as part of our standard set of updated authorities (new, change, delete)
from the Notification service.
Backstage will default to not delivering these particular updates for
Phase 1, unless otherwise requested by our libraries.
In Phase 2, automated changes that can be made to 1XX, 4XX, and/or 5XX
are done. Most of the changes involve expanding abbreviations, or the
addition/removal of specific fields (link
<http://ac.bslw.com/community/blog/2012/05/rda-naf-conversion-and-day-on
e-implementation/> ).
As Phase 2 is set to be completed as close to Day One as possible (March
31, 2013), we hope this gives our clients enough time to establish
procedures on their end in order to handle the large influx of updates
scheduled to arrive. These updates are planned to cover a 3-4 week time
period, where approximately 328,000 records will be re-issued with the
changes listed above. Backstage does recommend that our libraries
receive these particular updates.
Backstage will default to delivering these particular updates for Phase
2, unless otherwise requested by our libraries.
As always, please let us know any questions you may have about the above
information.
Nate Cothran
Vice President, Automation Services
533 East 1860 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
