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