It has been a couple months since we put out the Near Match Report
(R00), available for all clients as part of our standard reports list.
We updated the threshold to limit near matches to 75% (for the primary
near match at least), in an effort to reduce the size/bulk of the report
itself.
We have received some feedback saying this is a good report and some
saying not so much. We are very interested in whatever you might have to
say in regards to this report: good or bad. We want to make it better or
(more) useful to those of you interested in receiving it.
Our hope is it can be a useful tool especially in regards to generic
name headings (i.e., name headings that lack qualifiers). As LC does not
always include the generic name as a 400 cross-reference in the fuller
form authority record, we hope this Near Match report helps you discover
whether these generic name headings have potentially valid matches.
The intent is to obviate the need to iterate through our Unmatched
Headings report (R07) for these particular generic name headings. R07
lists the unmatched name heading without also attempting to find a
potentially valid (sometimes fuller) form. Anything that reduces the
staff time on your side in researching these types of headings is our
goal here.
Also, if you're planning on coming out to Anaheim for this Summer's ALA,
we will be at Booth #2200 so please feel free to stop by. And come visit
and eat with us at Morton's Steakhouse (1895 S Harbor Boulevard) on
Saturday morning (7:30am to 9:00am).
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
Near Match Report (R00) - Updated Threshold
In an effort to minimize the number of near match headings to sort
through, we have modified our report settings so that it shows only
those headings with a confidence level of 75% or higher:
a9588866
100 1_ $a Akindele, Theophilus O.
99.5%
nb2011002527
100 1_
$a Akindele, Theophilus O. $q (Theophilus Oluwole), $d 1922-
47.8%
n 97070081
100 10
$a Akindele, S. T.
a9595052, a9595718
100 1_ $a Aksoy, M. Ataman.
99.5%
n 82103592
100 10
$a Aksoy, M. Ataman, $d 1945-
76.5%
n 98951697
100 10
$a Aksoy, M. Ata, $d 1947-
a9597948
100 1_ $a Alam, Sanjeer.
78.6%
n 2007073044
100 1_
$a Alam, Sameer
57.1%
no 99022000
100 10
$a Alam, Sameena Bary
Our hope is that this greatly reduces the size of this particular
report. While the default is 75% or higher, this confidence level can be
entirely configurable by our clients. Just let us know if you would
prefer a higher or lower threshold and we will make it happen for you
immediately. This new 75% threshold is now in place for all clients that
have chosen to receive the near match report.
Again, there is no extra cost to receive this report and if you are
interested, please contact your project managers:
Judy Archer
<mailto:jarcher@bslw.com?subject=Near%20Match%20Report%20(R00)> or
Stephanie Hansen <mailto:shansen?subject=Near%20Match%20Report%20(R00)>
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
In a previous post on March 23, 2012, we talked a little about our
efforts to create a more useable report for unmatched headings. We have
added more functionality to the report that we hope helps clarify the
results. Also, we plan to continue to refine the algorithm we use for
the near matches as well as the confidence level we have assigned to
each near match.
Here are a few examples of the report (from its current build):
ocm05472887
100 1_ $a Allen, Junius Mordecai.
99.5%
no 95045186
400 1_
$a Allen, Junius Mordecai, $d 1875-1906.
56.5%
no 00103969
100 1_
$a Allen, Junius, $d 1898-1962
ocm77567496
650 _0 $a Adventure and adventurer $v Fiction.
97.1%
sh 85001072
450 __
$a Adventure and adventurers $v Fiction
70.6%
sh2009113774
150 __
$a Adventure and adventurers $z Europe $v Biography
ocm02224738, ocm02464058, ocm02735261, ocm03462153, ocm04493529
490 0_ $a Old West
99.5%
no 96034673
130 _0
$a Old West (Alexandria, Va.)
99.5%
n 99000801
151 __
$a Old West Lawrence Historic District (Lawrence, Kan.)
Not all near matches will be ranked so high on our "confidence level
percentage", but these three should give you a better idea of the
report's results.
We match as much of the original heading to the near match as possible.
Whatever matches on the unmatched heading is highlighted in BLUE. Parts
of the near match that are potential typos or new additions not
contained in the unmatched heading are offset in RED. Then the second
near match is also highlighted similar to the first near match, but in
GREEN, to help distinguish between the two near matches.
As a next step, we are looking into the possibility of sorting this
report based on percentile. So 90 percentile near matches will be listed
first (and sorted within that group A-Z). This might take some extra
finagling from our programming team to successfully implement, but we
will keep you updated on our progress.
While the higher percentile near matches are useful for letting you know
what may actually be a valid match, we also want to point out that the
lower percentile matches are useful in identifying (or dismissing)
headings where there exists no near match. Every unmatched heading will
have two near matches listed underneath it, even if those near matches
are very low probability (less than 5%). This is due to how our
algorithm is setup to generate these near matches for the report.
This report is called:
R00 - Near Match Report.htm
Please feel free to contact your project managers in order to request
that we start delivering this report with your Current Cataloging
results (at no extra cost):
Judy Archer (email
<mailto:jarcher@bslw.com?subject=R00%20-%20Near%20Match%20Report> )
Stephanie Hansen (email
<mailto:shansen@bslw.com?subject=R00%20-%20Near%20Match%20Report> )
We will still be delivering R07 (Unmatched Headings) and R10 (Multiple
Authority Matches), so this R00 - Near Match Report won't yet replace
those. But since every unmatched heading will have two near matches
listed underneath, we do want to point out that it can be quite large
depending on the size of your Current Cataloging file (and matching
results).
We welcome your feedback!
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
Wikipedia <http://en.wikipedia.org/wiki/Oxymoron> defines an oxymoron
as "a figure of speech that combines contradictory terms." In the title
for this post, this is a turn of phrase that has represented at least
one of the holy grails of research within our dept. We asked the
question many times:
How can we automate what is essentially a manual review of our client's
headings?
We have 2 kinds of standard reports that are of concern here:
* R07 - unmatched primary headings
* R10 - heading matches multiple authority records
With R07 and R10, we have left the burden of researching these headings
up to our clients. For some of you out there, that represents a
tremendous number of headings to manually check on your own each time we
deliver them to you.
Would it be helpful if your unmatched headings report also listed
potentially valid headings? Maybe there was a typo in your original
heading which caused it to not find a match. Or maybe your name heading
is generic and lacking qualifiers. Or perhaps your heading matched two
different authorities-but which two authority headings exactly?
Our team is currently working very hard on a potential near-match report
which we hope to unveil within the next few weeks. We are anticipating
replacing the current R07 and R10 reports with this new near-match
report as part of our standard offering.
Here are a few examples of the report (from our latest build):
bib rec id no
700 1_
$a Miller, Stephen H.
nb2001044979
100 10
$a Miller, Stephen H., $d 1956-
n 83184733
100 1_
$a Miller, Stephen H. $q (Stephen Henry), $d 1943-
bib rec id no
700 1_
$a Cheung, Julian.
no2011144486
400 1_
$a Cheung, Julian Chi Lam, $d 1971-
nb 99009824
100 10
$a Cheung, Juanita
bib rec id no
100 1_
$a Kirk, Erika.
no2003097342
100 1_
$a Kirk, Erica.
no2001034074
100 1_
$a Kirk, Erin.
This revision of our fundamental reports doesn't quite fulfill that
automated manual review goal we still have. But we hope it puts our feet
on the right path and helps to make your workload easier at the same
time. We will have more information about this new report in the near
future.
--
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
Working closely with University of Chicago, we have put together another
option for controlling your AACR2 and RDA headings. We now have a total
of 7 distinct options for libraries to choose from:
http://ac.bslw.com/community/wiki/index.php5/RDA_7.1
To help facilitate understanding for the searching and matching
processes being performed during each option, we have also laid it out
visually in a flowchart. Sometimes it just helps to see the process
plainly to determine whether what we have described matches your
expectations.
Each option now includes a brief summary of the process involved for
either type of heading (AACR2 or RDA), as well as the search order for
the respective headings.
The latest, most recent option is explained here:
http://ac.bslw.com/community/wiki/index.php5/RDA_7.1#RDA_OPTION_5.0
This option follows the PCC/LC standards. Again, with many thanks to
University of Chicago for their valuable input.
Each option listed in the wiki is ready to go at your convenience.
Please just contact your project managers, Judy Archer
<mailto:jarcher@bslw.com?subject=RDA%20Authority%20Control%20Options>
or Stephanie Hansen
<mailto:shansen@bslw.com?subject=RDA%20Authority%20Control%20Options> ,
for more details. We also welcome any feedback you may have about these
options.
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
This post is in regards to our efforts to control the 33X Content,
Media, Carrier Types (hereafter: CMC), sometimes in conjunction with the
245 $h General Material Designator (hereafter: GMD).
GMDs, for the purposes of our discussion, appear in bibliographic 245
$h, and constitute the medium designator used in the title statement (1
<http://www.loc.gov/marc/bibliographic/bd245.html> ). Some examples of
AACR2 standard terms include:
* cartographic material, chart, electronic resource, microform,
music, sound recording, videorecording
MARS 2.0 utilizes an AACR2 Standard Terms
<http://ac.bslw.com/community/wiki/index.php5/Step_2.8#aacr2_standard_te
rms> table that includes 33 separate entries, some of which vary only a
little due to parenthetical qualifiers (e.g., "chart" and "chart (large
print)"). Some libraries use GMDs that are not included in the AACR2
list, which Backstage documentation refers to as the Common Practice
Terms
<http://ac.bslw.com/community/wiki/index.php5/Step_2.8#common_terms> .
There are 75 separate entries in this latter list.
Typically the GMD itself is offset within 245 $h by brackets:
* 245 $h [electronic resource]
MARS 2.0 also adds missing GMDs
<http://ac.bslw.com/community/wiki/index.php5/Step_2.6#245_.24h_added_.2
8medium-aacr2.29> based on specific values in LDR[06] and 008[23] /
008[33], all of which are from the AACR2 Standard Terms list.
When we first visualized adding corresponding (33X) CMC to the
bibliographic records, we approached it from the assumption that a
(245$h) GMD would exist in the same record. Our reasoning was that we
could apply greater granularity to adding the appropriate CMC terms
based on the generous help of the existing GMD.
We also took into consideration the byte values for LDR[06], 007[00],
007[01], 008[23,25,26,33]-when these values were available. For
instance, we devised a series of rules to govern the addition of the 33X
CMC terms based initially on what value the 245 $h GMD was.
As an example, we have 8 separate rules dealing with (GMD) "cartographic
material", from AACR2 Standard Terms list:
* 2 rules examine LDR[06] for 'e' or 'f'
* 6 rules examine 007[00] for 'a' or 'd'
* 5 rules examine 007[01] for 'd', 'j', 'k', 'q', 'u', 'z', '|',
'#'
* 1 rule examines 008[25] for 'd'
Based on the results from each of those separate rules, we generate one
336 Content Type <http://www.loc.gov/marc/bibliographic/bd336.html> :
* cartographic image
* cartographic three-dimensional form
With one 337 Media Type
<http://www.loc.gov/marc/bibliographic/bd337.html> :
* unmediated
And one 338 Carrier Type (RDA)
<http://www.loc.gov/marc/bibliographic/bd338.html> :
* volume, sheet, other unmediated carrier, unspecified, object
So, say our test record had this as the criteria that would help us
determine the data for the 33X (to be added):
007[00] 'a'
007[01] 'q'
245 $h [cartographic material]
Then we would generate a set of 33X like so:
336 $a cartographic three-dimensional form $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a object $2 rdacarrier
>From the first two byte values in 007
<http://www.loc.gov/marc/bibliographic/bd007a.html> , we know we are
dealing with the model (007[01] 'q') of a map (007[00] 'a'). If the
007[01] value had been 'j' (map) or 'k' (profile) instead of 'q'
(model), then our 33X CMC set changes to:
336 $a cartographic three-dimensional form $2 rdacontent
337 $a unmediated $2 rdamedia
338 $a sheet $2 rdacarrier
The above examples only pertain to 8 separate rules for GMD
'cartographic material' in the AACR2 Standard Terms list. In fact, there
are over 300 rules dealing with this particular GMD list. Consequently,
there are nearly 300 separate rules for the Common Practice Terms list
(many terms within this list are shared with AACR2 Standard Terms).
One of the great aspects about our rewritten MARS 2.0 system is that it
gives us the control to easily switch any one of these rules on or off,
as well as modify each one and tailor it for each client. For instance,
we may have some clients that would prefer we treat 007[01] values of
'j', 'k', and 'q' as the same Carrier Type (e.g., "sheet"). Of course
many other options are available as well.
Polonius, in Hamlet, says "... brevity is the soul of wit." (2
<http://www.enotes.com/shakespeare-quotes/brevity-soul-wit> ) Alas, I
still have a ways to go on that front. Suffice to say that this
satisfied our initial desires for how to direct this part of the RDA
services. However, we recently brought up this point: what about records
where there are no GMDs or none can be added based on other fields we
might use (e.g., aforementioned LDR[06], 008[##])?
Our RDA service can make use of the existing GMDs in very precise ways;
again, that is when the GMD already exists in the record. So, currently
we are hard at work on "filling in the blanks", quite literally in this
case. Chiefly, we plan to diverge our rules like so:
1. Add 33X CMC based on initial presence of 245 $h GMD (as well as
other fields listed above)
2. If no 245 $h GMD exists, then utilize other fields in record to
determine best-case 33X CMC set to add
We anticipate that we will have these further rules (item #2 listed
above) in to our programmers late next week. Then, from that point, it
shouldn't be too long before it is officially in place for the CMC
options.
If you have made it this far, we thank you for your diligence!
Incidentally, we have 110 rules to deal specifically with GMD
'electronic resource': 12 separate Content Types, 1 Media Type
(computer), and 9 separate Carrier Types.
(1) http://www.loc.gov/marc/bibliographic/bd245.html
(2) http://www.enotes.com/shakespeare-quotes/brevity-soul-wit
(3) A quick note to point out that Karen Anderson contributed the
exhaustive research into the 600+ rules for this section
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
In a few short weeks, Jeremy Myntti will be leaving Backstage Library
Works to pursue a career at University of Utah. Jeremy has accepted a
position as Head of Cataloging & Metadata Services at the University
Library.
Jeremy has been employed at Backstage for nearly nine years, working his
way through a good collection of depts. For the last three years Jeremy
has been a part of our Automation Services team, specifically lending
his expertise and knowledge as one of our Authority Control project
managers. His strong background in technical services helped us get
creative when it came to deriving solutions for our customers. We will
miss him ... as well as his extreme devotion to all things Disneyland.
As part of his transition out of the company, Jeremy will be helping to
train his replacement. We have selected Stephanie Hansen to step into
the role of serving our Authority Control customers and moving forward
with our dept. Stephanie comes to us with an excellent background in
cataloging at Backstage, with a keen eye towards details. Stephanie was
also part of the original crew that participated in the RDA test back in
late 2010, and we welcome her fresh take on our services.
P.S. I keep promising to send another update about our RDA services,
specifically regarding the 33X field additions (Content, Media,
Carrier)-it's still coming! I had planned to start the dialogue for that
later today, but to keep it separate from this post.
Best regards,
Nate
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
Greetings Everyone,
If I could play some polka through this email, I would do so! It looks
like Punxsutawney Phil
<http://www.washingtonpost.com/national/groundhog-day-2012-punxsutawney-
phil-shadow-means-6-more-weeks-of-winter/2012/02/02/gIQAriw2kQ_story.htm
l> did indeed see his shadow yesterday, which means 6 more weeks of
winter. That is probably good, as Utah hasn't seen much winter this year
anyway.
http://ac.bslw.com/mars/home.php
We have been working on transitioning all of your current AACR2
authority control settings from our older version of the online profile
to our most recent version. So the good news is that you shouldn't have
to update the AACR2 profile unless you wish to make a change, which you
can do so at any time.
We have now made the RDA online profile options available for you to
review at your convenience. As with the AACR2 version, you will notice
that we have tried to make things a little more clearer for everyone.
For instance:
1. Default options are now highlighted. Defaults are intended only
to act as guideposts for you as you fill out the online profiles. Of
course we recommend choosing options which best fit your institution's
needs and desires.
2. There is no longer a wrong answer :D In previous versions we
had 'radio' style buttons which made it difficult to deselect certain
options. Now, everything is a checkbox and every option can be checked
or unchecked as you like. If there is any confusion on our side about
the options you have selected, we will contact you with our questions.
3. Each question has its own '?' box to the right of it. Hovering
your mouse over this provides a quick synopsis of the question, as well
as links within that synopsis to more details in our online wiki.
While filling out the profiles, we ask that you save after each Step
(and there are save options both at the top and bottom of each Step
section). You can switch between Steps without worrying or waiting for
the page to reload each time. You can also save Steps that have only a
few items checked, or even nothing checked (again, no wrong answers for
the profile).
As you look over the RDA profile options, you may have questions or
concerns and we welcome your feedback. Please feel free to contact us
[Nate: nate(a)bslw.com, Jeremy: jmyntti(a)bslw.com, Judy: jarcher(a)bslw.com]
at any time to discuss what's on your mind.
We don't quite have everyone switched over from the previous AACR2
version to the newer version, but we are very close. We hope you enjoy
cruising around the new online profile options.
P.S. Backstage is planning on rolling out a company-wide blog in the
very near future. We will likely post our updates about our RDA services
to the blog, in addition to this listserv. As the blog is company-wide,
it will also include updates from other depts. Or, should that be
departments?
Until next time, best regards.
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
Our RDA Planning Guide and revised Authority Control Planning Guide is
now available for download on our website:
http://ac.bslw.com/mars/guide
We have also revamped the wiki pages:
http://ac.bslw.com/community/wiki/index.php5/Profile_Guide
The RDA Guide clocks in at under 80 pages. The revised Authority Control
Guide is now a svelte 180 pages.
We anticipate needing to make adjustments to the RDA Guide as the weeks
roll by, based on a variety of feedback we receive.
For instance, we are considering expanding our RDA Authority Control
options again, based on recent comments. Currently, we have two separate
RDA authority databases that we maintain:
1. RDA-1: contains authorities where the original 1XX has been
moved to 4XX, and the (rda) 7XX has been moved to 1XX. This facilitates
options for clients interested in flipping to the RDA version of the
heading
2. RDA-2: contains pure RDA authorities, that have been newly
created (040 $e rda); hence, no 7XX
A third option we are working to implement would be to change the (rda)
7XX to 4XX. This would allow clients to match against the RDA heading,
yet still flip the heading to the AACR2 version (1XX) instead. There are
still a few more wrinkles we are trying to iron out with this option.
Of course, in a year's time, once LC starts copying/moving their AACR2
authorities to RDA equivalents (expanding abbreviations, etc), we might
be back to one RDA database to maintain. Or, we could just as easily be
up to 4. So we are also anxiously invested in the directions RDA is
heading.
In the next update, we will outline some of the changes we are planning
to implement for generating the CMC options (33X) in records. The online
profiles for both "regular" authority control and RDA-specific options
should also be ready by the end of next week.
Until then, if you are attending ALA in Dallas, please stop by our booth
(#1229) to discuss RDA. Also, if you can make it, we are having our
dessert reception across the street from the Dallas Convention Center,
held at the Omni (5th floor), from 7:30pm to 9:30pm (Friday).
Thanks!
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
Greetings Everyone,
I just sent out a notice about our new RDA Services, but it has come to
my attention that certain email clients (e.g., Thunderbird) may have
unfortunately blacked out the main body of my text due to the attachment
I had included previously. If this happened, I apologize for the
confusion, and wanted to send this out one more time.
Back in May 2009, Backstage was chosen as one of three vendors to
participate in the national RDA testing phase. Born from that
experience, as well as direct feedback from our clients, we focused our
efforts on providing authority control options for your RDA bib records.
We started with an easy option and assigned it as the default:
1. Treat all incoming bibs, whether encoded as AACR2, RDA, or
something else as AACR2
This option was a starting point and allowed us to stretch our legs, and
discover more solutions for our clients:
2. Ignore all incoming RDA bibs, separating them out for later
runs (if desired)
3. Match AACR2 & RDA bib headings against their respective
databases first; unmatched headings have the option to be searched
against the other respective database next
4. Match AACR2 & RDA bib headings against AACR2 (but include 700
x4 as a matching point), flipping all potential matches to respective
authority's 1XX heading; unmatched headings can then be searched against
the RDA authority database only
These options, in an early form, were made available in late October
2010, with an official announcement from us in January 2011. Since that
time, there have been a few modifications made, especially in regards to
simplifying the language used to describe each option. Also, we sought
to make option #3 match the PCC standard for RDA authority control as
closely as possible. Still, we continue to have minor variations on each
of these for certain customers and fully anticipate needing to make
additional adjustments in the months ahead.
For the last several months, our team has been hard at work putting
together options to process & validate your AACR2 or RDA bib records
using new RDA standards. We are trying to tackle this from multiple
angles:
1. Full RDA cataloging, utilizing the expertise of our experienced
cataloging staff
2. Convert entire collection of (pre)AACR2 bib records to RDA
formatting
3. Upgrade ongoing (pre)AACR2 bib records to RDA formatting
4. Upgrade / Validate existing RDA records as part of current
cataloging efforts
5. Provide options for hybridizing your records (e.g., both AACR2
& RDA elements co-existing within same record)
6. Applying the same type of customized options you are used to
with our Authority Control service
7. Providing opportunities to test the waters before taking the
plunge
Over the next several weeks & months, we plan to roll out this service
and make all parts of it available for your perusal. We are still making
changes based on feedback from a beta-test partner, as well as our own
quality assurance checks.
By the end of January, we will have available a new online profile
dedicated to RDA processing options. Our customers will be able to
choose to view either the existing Authority Control profile (which we
have also revamped) or the new RDA profile and make changes as
necessary. In addition, we have created an accompanying 70-page profile
guide (pdf, printed, wiki) to assist you with your RDA processing
options.
Please stop by our booth (#1229) to ask us about our RDA Services, and
address any questions you may have.
More information will be forthcoming, so please stay tuned!
Nate Cothran - nate(a)bslw.com
<mailto:nate@bslw.com?subject=Automation%20Services%20-%20Query>
Product Manager, Automation
Backstage Library Works
533 E 1860 S, Provo UT 84606
(p) 801.342.5697 - (f) 801.356.8220
www.ac.bslw.com/community/blog <http://ac.bslw.com/community/blog/>
