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/>
