MARS Authority Control

Any time we process a file for your institution, we generate a Statistical Summary report.  Within this report, we list match-rates, types of records processed, as well as the number of fields changed during processing.  While this is all well and good, as soon as that report is sent out to you, those statistics have been forgotten.

We thought it would be a good idea to keep you informed of some of those statistics on a regular basis, all completely tailored to when you send us files for processing.  And we wanted to do this in a graphical way so that you’re not just looking at lists of numbers and confused as to their relevancy to your records.

As we started planning on what to do with the statistics, we realized early on that not everyone goes through our website to process their files.  Some of our clients use external FTP servers, while some use the website.  We never want our customers to feel left out on any functionality we have implemented.

Whenever a file is submitted to Backstage for processing, we keep track of certain statistics within our tables.  We have to keep track because this is how we generate that Statistical Summary report that we deliver for base files, ongoing current cataloging, and samples.  It doesn’t matter how the file reaches us (website, ftp, email, etc)—once we process it, we keep track of the data.

This statistical tracking helps us determine the busiest times of the year and how we should structure the time on our side to meet the expectations on your side.  We also realized that this could be a useful tool for you and your staff to track the trends in your own processing.  Throughout the year, how often do you send in files for processing?  What kinds of match-rates or types of records do you usually see?

We have created two sections for you:

1. Record Statistics
2. Match Statistics

For Record Statistics, we’ll show you how many books, serials, and other types of records were processed:

Of those records, how many were changed vs unchanged?

We’ll also plot how many records you sent throughout the year:

We think it makes sense to only include months where you send us bib files to process.  Each part of every graph has parts that can be clicked to determine more information, or isolate that part of the process for you.

With Match Statistics, we go a step further than our Statistical Summary report and tell you about the kinds of matches you’ve received on your records:

Finally, we wanted to also show you how many of your headings (1xx, 6xx, 7xx) found full or partial matches, as well as the number of unmatched headings:

Over the next few weeks, we plan on putting this information in place for all of our clients.  Whenever you log into our website to view your profile or current jobs, you can also view your stats.  Again, it doesn’t matter whether you send us your bibs through the website, ftp server, or email—once we process them, those stats will be added to your stats page.

As a bonus to those clients that do send us their files through the website, each one of those website bibliographic jobs will have its own set of graphic statistics as well.

We hope this information gives you the edge you may need for your staff.  As always, feel free to let us know if you would like to see other statistics.

New Optional Report – R08 Generic Names

Backstage has a new optional report that can be generated during Current Cataloging or Basefile processing.  The new report lists all generic name headings.  Below is a brief description of the report as well as a few examples of how headings on this report appear.

The fields in this report contain a primary name heading which is considered generic (i.e. names without qualifiers such as a date or fuller form of the name). Choosing to flip on generic name headings will give you a greater match rate, but it can cause mismatched headings. The MARS 2.0 software allows for the flip of all name authority headings including the generic heading if there is a match to a See reference (400) in the LC authority record.

Sometimes a national authority record just lacks some of the key information that your library needs. Maybe it’s an important cross-reference, a note, or some sort of field identifier. If you just receive the latest Library of Congress authority, for example, you could lose all that hard work that you and your staff have gone through to find the information and add it to your authorities.

Thanks to our project manager for writing that up. Preserving fields is one of the services many of our libraries find most useful, and we have even more options than listed above when it comes to preserving your data for cases where adding a $5 would be unreasonable or impossible. so feel free to talk to on of our project managers about how we can help you with your situation.

With all the excitement surrounding RDA at ALA Annual (and we’ll have an update about that up soon), we realized we didn’t have a quick recap of events from my point of view in DC.  I would like to fill you in on details from an operational point of view as concerns Backstage, letting Karen Anderson let you know about the RDA updates later.

On June 24, a few of us flew into Bethlehem, PA to visit our new offices out there.  As some of you may know, we acquired the preservation services (Digitization, Microfilm) from OCLC back in August 2009.  So it was an opportunity to get out and visit with our team, meeting Joan DaShiell and Joe Konrath, both of whom are widely respected in that business.

That next Friday we drove up to DC to take part in the sweltering outside heat and air-conditioned halls of the conference center.  The traffic going into DC made the trip an all-day affair, though the upside was it gave us a chance to catch up on our emails and plan out our schedules.

On Saturday, we had a great turnout for the Authority Control users breakfast as Clyde’s.  I mentioned a couple announcements (i.e., online stats to track your processing throughout the year, and our ability to process & return records in MARCXML now).  But the real star of the show was with Karen’s updates regarding RDA.  As Backstage is part of the ongoing testing effort with RDA, it was great to have Karen with us to field your questions.  She has written up a detailed response and we will post that very soon.

Much of the remainder of my time was occupied with chances to meet up with existing and potential clients.  It’s a great feeling to work with people all throughout the years and finally meet each one in person.

We think we have a fair number of lurkers on this blog and would encourage you to leave comments whenever you like.  We are always on the lookout to make the service easier and more efficient for you and your workflow, so please feel free to let us know how we can make things better.  Tell us what you want and we will see what we can do to make it happen.

Our RDA librarian, Karen, sent me this helpful blog entry with a lot of detail about RDA, without further ado, I present it to you.

Now that RDA has been published, there are lots of questions about when we will start seeing RDA records.  LC and OCLC have both asked that no RDA records, or records using RDA elements be sent out until October 1^st, 2010 when the National RDA Test participants will start producing records officially.  Here are some links to policy statements and other information that may help you figure out what to expect.

http://www.loc.gov/catdir/pcc/RDA-Testing-PCC.pdf – This is the policy statement for PCC (NACO, BIBCO, CONSER) participants.

http://www.oclc.org/us/en/rda/policy.htm – this is OCLC’s policy statement about the RDA test.  It gives their protocols.  If you use OCLC, I highly recommend that you take a look at this.

http://www.oclc.org/us/en/rda/about.htm – OCLC’s main page about RDA where you can find the above link as well as a host of other information

http://www.loc.gov/catdir/cpso/RDAtest/rda_lcps.html – here are the LC Policy Statements (LCPSs) for the RDA rules.  These are the equivalent of the LCRI’s for AACR2.  The LCPSs are for the testers to use.  They will be reviewed after the evaluation of the test.

http://www.rda-jsc.org/workingnew.html – for complete examples of RDA bibliographic and authority records.  This is where the JSC (the group responsible for RDA) puts their working documents.  Be sure to make note of the note at the top.

http://www.loc.gov/catdir/cpso/RDAtest/rdaexamples.html – LC has also posted some examples that demonstrate some of the differences between RDA and AACR 2

LChelp4RDA@loc.gov - where anyone (whether participating or not) can ask questions about the national RDA test.

I hope these links will be helpful. Please feel free to comment or ask questions here (best), or email our listserv, and I’ll do my best to find an answer.   bslwac@mailman.xmission.com

Although the major international library communities who are planning on implementing RDA have agreed to the Oct. 1^st starting date, there is certainly no guarantee that RDA records won’t start showing up.  But they shouldn’t cause problems as long as your system can recognize all the fields.  They should be able to exist alongside AACR2 records.  (We’re only talking MARC here.)  As an official test partner, Backstage will have our policies and processes to deal with RDA records (bibliographic and authority) in place by Oct. 1^st.

So, here again (see RDA Changes in MARC Records) is the list of all the changes made to the MARC Bibliographic and Authority formats from 2008 through March 2010.  It includes changes approved at ALA Midwinter 2010.  Unfortunately, it does not include the changes approved at the ALA Annual meetings.  I haven’t been able to find those yet, but I’ll post them as soon as I do.

The changes are listed by tag, with the Bibliographic format changes first, then the Authority format changes following.  I have included the link to the tag description in the MARC21 Standards.  Also, after each change I’ve given the link to the MARBI proposal for that change in case you would like to see the reasoning behind it.  These will have the word “marbi” in the link and directly follow the actual change

Fields with changes made to directly or indirectly accommodate RDA are marked with an *.  For more information on how RDA is affecting MARC21 see the document “RDA in MARC” found on the MARC21 Standards home page:  http://www.loc.gov/marc/RDAinMARC29.html

Bibliographic format changes by field as of Mar. 2010

*Leader/18 – Descriptive cataloging form   http://www.loc.gov/marc/bibliographic/bdleader.html

Note: will be coded i with RDA

http://www.loc.gov/marc/RDAinMARC29.html

*007/01 – Electronic Resource (007/00=c)  http://www.loc.gov/marc/bibliographic/bd007g.html

New codes defined [2009]

d – disc, type unspecified

e – disc cartridge, type unspecified

k – computer card

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Projected Graphic (007/00=g)  http://www.loc.gov/marc/bibliographic/bd007g.html

Redefined code: [2009]

f – other or unspecified type of filmstrip (changed from Other type of filmstrip)

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Microform (007/00=h)  http://www.loc.gov/marc/bibliographic/bd007h.html

New codes defined: [2009]

j – microfilm roll

http://www.loc.gov/marc/marbi/2009/2009-06-3.html

h – microfilm slip

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Nonprojected Graphic (007/00=k)  http://www.loc.gov/marc/bibliographic/bd007k.html

New codes defined: [2009]

a – activity card

k – poster

p – postcard

q – icon

r – radiograph

s – study print

v – photograph, type unspecified

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*007/01 – Motion Picture (007/00=m)  http://www.loc.gov/marc/bibliographic/bd007m.html

New code defined: [2009]

o – film roll

http://www.loc.gov/marc/marbi/2009/2009-06-3.html

*007/04 – Map (007/00=a)  http://www.loc.gov/marc/bibliographic/bd007a.html

*007/04 – Globe (007/00=d)  http://www.loc.gov/marc/bibliographic/bd007d.html

*007/04 – Nonprojected Graphic (007/00=k)  http://www.loc.gov/marc/bibliographic/bd007k.html

New codes defined: [2009]

i – plastic

l – vinyl

n – vellum

v – leather

w – parchment

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

007/04 – Videorecording (007/00=v)  http://www.loc.gov/marc/bibliographic/bd007v.html

New code defined: [2008]

s – Blu-ray disc

http://www.loc.gov/marc/marbi/2008/2008-09.html

*007/05 – Nonprojected Graphic (007/00=k)  http://www.loc.gov/marc/bibliographic/bd007k.html

New codes defined: [2009]

i – Plastic

l – Vinyl

n – Vellum

v – Leather

w – Parchment

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

008/18-19 & 006/01-02 – Music – Form of Composition (also valid in field 047 – Form of Musical Composition Code)  http://www.loc.gov/marc/bibliographic/bd008m.html

New codes defined: [2009]

za – Zarzuelas

fl – Flamenco

vi – Villancicos

tl – teatro lirico

http://www.loc.gov/marc/marbi/2009/2009-09.html

*008/20 & 006/03 – Music – Format of Music http://www.loc.gov/marc/bibliographic/bd008m.html

New codes defined: [2009]

h – chorus score

i – condensed score

j – performer-conductor part

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

008/23 & 006/06 – Books – Form of item  http://www.loc.gov/marc/bibliographic/bd008b.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/22 & 006/05 – Continuing Resources – Form of original item http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/23 & 006/06 – Continuing Resources – Form of item  http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/23 & 006/06 – Computer File – Form of item http://www.loc.gov/marc/bibliographic/bd008c.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/22-23 & 006/05-06 – Maps format – Projection  http://www.loc.gov/marc/bibliographic/bd008p.html

New codes defined: [2009]

bk – Krovak

bl – Cassini-Soldner

http://www.loc.gov/marc/marbi/2009/2009-04.html

008/23 & 006/06 – Music – Form of item  http://www.loc.gov/marc/bibliographic/bd008m.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

00823 & 006/06 – Mixed Materials – Form of item  http://www.loc.gov/marc/bibliographic/bd008x.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/24-27 & 006/07-10 – Books – Nature of content  http://www.loc.gov/marc/bibliographic/bd008b.html

New codes defined: [2008]

y – Yearbooks.  -  made obsolete in 1988, but is now being redefined

2 – Offprints

5 – Calendars

6 – Comics/graphic novels  – this replaces 008/33 and 006/16 code c (comic strip)

http://www.loc.gov/marc/marbi/2008/2008-04.html

008/24 & 006/07 – Continuing Resources – Nature of Entire Work  http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2008]

y – Yearbooks – this code was made obsolete in 1988, but is now being redefined

5 – Calendars

6 – Comics/graphic

http://www.loc.gov/marc/marbi/2008/2008-04.html

008/25-27 & 006/08-10 – Continuing Resources – Nature of contents  http://www.loc.gov/marc/bibliographic/bd008s.html

New codes defined: [2008]

y – Yearbooks

5 – Calendars

6 – Comics/graphic novels

http://www.loc.gov/marc/marbi/2008/2008-04.html

008/29 & 006/12 – Map – Form of item  http://www.loc.gov/marc/bibliographic/bd008p.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/29 & 006/12 – Visual Materials – Form of item http://www.loc.gov/marc/bibliographic/bd008v.html

New codes defined: [2010]

o – Online

q – Direct electronic

http://www.loc.gov/marc/marbi/2010/2010-01.html

008/33 & 006/16 – Books format – Literary Form   http://www.loc.gov/marc/bibliographic/bd008b.html

Obsolete code: [2008]

c – Comic strips – made obsolete (replaced by a code 6 in 008/24-27 or 006/7-10 for Books format.)

http://www.loc.gov/marc/marbi/2008/2008-04.html .

017 – Copyright or Legal Deposit Number   http://www.loc.gov/marc/bibliographic/bd017.html

New subfield: [2008]

$z – Canceled/invalid copyright or legal deposit number (R)  [2008]

http://www.loc.gov/marc/marbi/2008/2008-08.html

*033 – Date/Time and Place of an Event   http://www.loc.gov/marc/bibliographic/bd033.html

New subfields defined: [2010]

$p – Place of event

$0 – Record control number

$2 – Source of term

http://www.loc.gov/marc/marbi/2010/2010-03.html

034 – Coded Cartographic Mathematical Data http://www.loc.gov/marc/bibliographic/bd034.html

New subfield: [2010]

$3 – Materials specified

http://www.loc.gov/marc/marbi/2010/2010-05.html

*040 – Cataloging Source http://www.loc.gov/marc/bibliographic/bd040.html

Subfield made repeatable [2010]

$e – Description conventions

code “rda” added to the MARC code list for Descriptive Conventions to indicate the use of the RDA rules for description. Leader/18 will be coded i with RDA.

041 – Language Code   http://www.loc.gov/marc/bibliographic/bd041.html

New first indicator [2008]

# – No information provided – Formerly undefined

http://www.loc.gov/marc/marbi/2008/2008-03.html

080 – Universal Decimal Classification Number http://www.loc.gov/marc/bibliographic/bd080.html

Redefined Indicator 1 – Type of edition – Prior to 2009 undefined
# – No information provided
0 – Full
1 – Abridged

http://www.loc.gov/marc/marbi/2009/2009-03.html

082 – Dewey Decimal Classification Number   http://www.loc.gov/marc/bibliographic/bd082.html

New subfields defined:  [2008]

$m – Standard or optional designation (NR)  code values:

a  – Standard

b – Optional

$q – Assigning agency (NR)

http://www.loc.gov/marc/marbi/2008/2008-01.html

083 – Additional Dewey Decimal Classification Number  http://www.loc.gov/marc/bibliographic/bd083.html

New field: [2008]

http://www.loc.gov/marc/marbi/2008/2008-01.html

http://www.loc.gov/marc/marbi/2008/2008-01.html#proposal01-5

085 – Synthesized Classification Number Components   http://www.loc.gov/marc/bibliographic/bd085.html

New field: [2008]

http://www.loc.gov/marc/marbi/2008/2008-01.html

http://www.loc.gov/marc/marbi/2008/2008-01.html#proposal01-6

257 – Country of Producing Entity   http://www.loc.gov/marc/bibliographic/bd257.html

Removed ‘for Archival Films’ from title.  Made tag repeatable.

Subfield redefined: [2009]

$a – Country of producing entity – subfield renamed & made repeatable

New subfield defined: [2009]

$2 –  Source

http://www.loc.gov/marc/marbi/2009/2009-08.html

*336 – Content Type   http://www.loc.gov/marc/bibliographic/bd336.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*337 – Media Type   http://www.loc.gov/marc/bibliographic/bd337.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

*338 – Carrier Type   http://www.loc.gov/marc/bibliographic/bd338.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html

New code under $b

ur – object

http://www.loc.gov/marc/marbi/2009/2009-06-3.html

*380 – Form of Work  http://www.loc.gov/marc/bibliographic/bd380.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*381 – Other Distinguishing Characteristics of Work or Expression   http://www.loc.gov/marc/bibliographic/bd381.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*382 – Medium of Performance   http://www.loc.gov/marc/bibliographic/bd382.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*383 – Numeric Designation of a Musical Work  http://www.loc.gov/marc/bibliographic/bd383.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*384 – Key    http://www.loc.gov/marc/bibliographic/bd384.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

440 – Series Statement/Added Entry – Title

Field made obsolete  http://www.loc.gov/marc/bibliographic/bd440.htm – this link contains instructions for conversion to appropriate 490/830 fields.

http://www.loc.gov/marc/marbi/2008/2008-07.html

490 – Series Statement   http://www.loc.gov/marc/bibliographic/bd490.html

1^st indicator redefined – Series traced, formerly Series traced differently

http://www.loc.gov/marc/marbi/2008/2008-07.html

Subfield redefined:

$x – made repeatable

http://www.loc.gov/marc/marbi/2009/2009-06-2.html

New subfield defined:

$3 – Materials specified

http://www.loc.gov/marc/marbi/2008/2008-06.html

502 – Dissertation Note   http://www.loc.gov/marc/bibliographic/bd502.html

New subfields defined: [2008]

$b – Degree type

$c – Name of granting institution

$c – Year degree granted

$g – Miscellaneous information

$o – Dissertation identifier

http://www.loc.gov/marc/marbi/2008/2008-05-4.html

510 – Citation/References Note   http://www.loc.gov/marc/bibliographic/bd510.html

New subfield defined:

$u – Uniform Resource Identifier (R)

http://www.loc.gov/marc/marbi/2009/2009-05.html

*518 – Date/Time and Place of an Event Note http://www.loc.gov/marc/bibliographic/bd518.html

New subfields defined: [2010]

$d – Date of event

$o – Other event information

$p – Place of event

$0 – Record control number

$2 – Source of term

http://www.loc.gov/marc/marbi/2010/2010-03.html

534 – Original Version Note   http://www.loc.gov/marc/bibliographic/bd534.html

New subfields:

$o – Other resource identifier (R) [2008]

http://www.loc.gov/marc/marbi/2008/2008-10.html

$3 – Materials specified [2009]

http://www.loc.gov/marc/marbi/2009/2009-10.html

542 – Information Relating to Copyright Status   http://www.loc.gov/marc/bibliographic/bd542.html

New field: [2008]

http://www.loc.gov/marc/marbi/2008/2008-02.html

588 – Source of Description Note   http://www.loc.gov/marc/bibliographic/bd588.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-07.html

*700, 710, 711, 730 –    http://www.loc.gov/marc/bibliographic/bd70x75x.html

New subfield: [2009] (see X00, X10, X11 sections for description)

$i – Relationship information

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

*760, 762, 765, 767, 770, 772, 773, 774, 775, 776, 777, 780, 785, 786, 787 – Linking Entries   http://www.loc.gov/marc/bibliographic/bd76x78x.html

Subfields redefined [2009]

$g – Related parts (R) – renamed from Relationship information text

$i – Relationship information (R) - renamed from Display text and made repeatable

New subfield defined [2009]

$4 – Relationship code (added for RDA Appendix J)

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

*787 – Other Relationship Entry   http://www.loc.gov/marc/bibliographic/bd787.html

Renamed from Nonspecific Relationship Entry [2009]

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

800, 810, 811, 830 – Series Added Entries   http://www.loc.gov/marc/bibliographic/bd80x83x.html

New subfields defined: [2008]

$x – International Standard Serial Number

$3 – Materials specified

http://www.loc.gov/marc/marbi/2008/2008-06.html

$5 – Institution to which field applies [2010]

http://www.loc.gov/marc/marbi/2010/2010-02.html

*New Subfield – $0 – Authority Record Control Number

Added to the following fields

100, 110, 111, 130, 240, 600, 610, 611, 630, 648, 650, 651, 654, 655, 656, 657, 662, 700,                                     710, 711, 730, 752, 754, 800, 810, 811, 830

http://www.loc.gov/marc/marbi/2007/2007-06.html#p1

Authority format changes by field as of Mar. 2010

034 – Coded Cartographic Mathematical Data   http://www.loc.gov/marc/authority/ad034.html

New subfield codes: [2010]

$3 – Materials specified

http://www.loc.gov/marc/marbi/2010/2010-05.html

*040 – Cataloging Source http://www.loc.gov/marc/authority/ad040.html

$e – Description conventions – made repeatable [2010]

code “rda” added to http://www.loc.gov/marc/relators/reladesc.html

see http://www.loc.gov/marc/RDAinMARC29.html

*046 – Special Coded Dates  http://www.loc.gov/marc/authority/ad046.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

New subfield codes [2010]

$k – Beginning or single date created

$l – Ending date created

http://www.loc.gov/marc/marbi/2010/2010-04.html

080 – Universal Decimal Classification Number http://www.loc.gov/marc/authority/ad080.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-03.html

083 – Dewey Decimal Classification Number   http://www.loc.gov/marc/authority/ad083.html

New subfield: [2008]

$y – Table sequence number for internal subarrangement or add table

http://www.loc.gov/marc/marbi/2008/2008-01.html#proposal01-1

*336 – Content Type  http://www.loc.gov/marc/authority/ad336.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-2.html – proposal

*370 – Associated Place   http://www.loc.gov/marc/authority/ad370.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*371 – Address   http://www.loc.gov/marc/authority/ad371.html

New field [2009] (see Marc standards for description)

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*372 – Field of Activity   http://www.loc.gov/marc/authority/ad370.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*373 – Affiliation   http://www.loc.gov/marc/authority/ad373.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*374 – Occupation   http://www.loc.gov/marc/authority/ad374.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*375 – Gender   http://www.loc.gov/marc/authority/ad375.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*376 – Family Information   http://www.loc.gov/marc/authority/ad376.html

New field: ([2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*377 – Associated Language   http://www.loc.gov/marc/authority/ad377.html

New field: [2009]

http://www.loc.gov/marc/marbi/2009/2009-01-1.html

*380 – Form of Work http://www.loc.gov/marc/authority/ad380.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*381 – Other Distinguishing Characteristics of Work or Expression http://www.loc.gov/marc/authority/ad381.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*382 – Medium of Performance http://www.loc.gov/marc/authority/ad382.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*383 – Numeric Designation of Musical Work http://www.loc.gov/marc/authority/ad383.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*384 – Key http://www.loc.gov/marc/authority/ad384.html

New field: [2010]

http://www.loc.gov/marc/marbi/2010/2010-04.html

*4XX, 5XX –

Subfield redefined (adjusted) [2009]

$i – Relationship information (done to accommodate RDA app. K and J)

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

New subfield

$4 – Relationship code [2009]

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

New subfield codes

$w/0 – r – Relationship designation in $i or $4 [2009]

http://www.loc.gov/marc/marbi/2009/2009-06-1.html

See Tracings and References–General Information -http://www.loc.gov/marc/authority/adtracing.html for instructions on using these subfields.

Why is Authority Control Important?

A basic definition of Authority Control is the process used to maintain consistency in access points and the process of showing the relationships among names, subjects, and works.

Some basic goals of authority control go back to Charles Cutter’s goals for a library catalog:

• To enable a person to find a book
• To show what a library has in its collection
• To assist patrons in their choice of a book

Using Cutter’s goals for a catalog, we can go further by saying that the purposes of authority control are to help patrons:

• find an item from known information
• identify an item with limited information
• collocate items using a controlled vocabulary
• evaluate and select an item
• locate synonyms to aid subject searching

To achieve these goals, authority records need to bring together related terms for the specific name, subject, or work.   Many times, the name of a person, place, or thing is constantly changing.  For example, the artist currently known as “Diddy” has had several name changes over the years.  Without a current authority record, a patron may not be able to find all of the items by this artist if they are searching on his former name of Sean Combs.  With the following authority record, the patron would be able to search for any of the artist’s former names and find all relevant items.

010 $a no 97057848

100 $a Diddy, $d 1969-

400 $a Puff Daddy, $d 1969-

400 $a P. Diddy, $d 1969-

400 $a Combs, Sean, $d 1969-

400 $a Combs, Puffy, $d 1969-

400 $a Puffy, $d 1969-

400 $a Diddy, P., $d 1969-

400 $a Combs, $d 1969-

400 $a Combs, Diddy, $d 1969-

Authority control is also important when a well-known name has been translated into several different languages.  For instance, the authority record for William Shakespeare has ninety-seven alternate forms of his name translated into multiple languages.

In order to increase access for the library’s patrons, it is important to use authority control to standardize the forms of search terms and increase the likelihood that the search will return the items that the patron desires.

Reference:

Taylor, A. G., & Joudrey, D. N. (2009). The Organization of Information (3rd ed.). Westport, Conn.: Libraries Unlimited.

Karen, our librarian and resident RDA expert let me know about a little update on the RDA front. I think it’s well worth your time to take a look, especially if you’re feeling a little stressed about RDA.

The last I heard, RDA is still scheduled to be published this month, and I know many are anxiously awaiting it.  (Either in excitement or trepidation!)  I saw this link to slides from an update about RDA given to the California Library Association Annual Conference on November 2.  It not only gives a good overview of RDA and its underlying models, but goes over the new data elements in RDA and some basic differences between RDA and AACR2 with examples to illustrate them.  There are also helpful links.  I really love the title:   “Help!  The new Cataloging Code is Coming!”  This presentation will surely help.

http://alcts.ala.org/crgwiki/images/1/10/RDA_CLA_Presentation.pdf

Many people know what the Library of Congress Authority Record Database is and how it can help their library. But what do you know about the other large authority collections? Nate Cothran, Product Manager of MARS Automation Services and expert on the Art and Architecture Thesaurus (AAT) sheds a little light on it for us:

The Art & Architecture Thesaurus (AAT) is a collection of 131,000 authority records about the visual arts and architecture maintained by the Getty Institute. Though the AAT is updated every month, the licensed version—which Backstage uses—is sent out once annually.

Within the authority record itself, the AAT entry lists the main heading in the 155 tag:

001 __ 300015529

155 __ $abird's-eye views$B(<views by vantage point or orientation>, views,
<visual works by form: image form>, <visual works by form>, <visual works>,
Visual Works, Visual and Verbal Communication, Objects
Facet)$I1000015529$TDescriptor$GN/A$HCurrent$VUndetermined$L70052/American
English$AN/A$ON/A$8300015529.1

The 155 $a is the part of the heading that will be reflected in your updated bib heading:

 655 __ $abird's-eye views

I can see what you’re thinking on this: How is it that the authority’s 155 above contains so much more information than the bib’s 655 field? Sometime in the last year, the AAT authority records began including an incredible amount of reference points & additional information encoded into capital-letter & numbered subfields. Unless your system is able to incorporate this extra data, the pertinent information you likely prefer to retain resides in the main (lower-cased) subfields.

In order to bring the authority records received from AAT back into a more manageable structure, Backstage can remove all of the capital-letter subfields as well as the numbered [0-9] subfields. This makes the loading into your system error-free in case your system balks at the extra subfields it has to somehow categorize on the fly.

So this revised authority heading:

001 __ 300015529

155 __ $abird's-eye views

Now matches cleanly and updates easily within your ILS system.

At least now you’ll know what to look AAT in your Art & Architecture Thesaurus authorities.

http://www.getty.edu/research/conducting_research/vocabularies/aat/about.html

Authority Control Interest Group (ACIG)

About twenty years ago I attended my first American Library Association Conference.  I was relatively new to the library world and really looking forward to the ALA experience.  I had heard so much about the great meeting being held about all topics known to “Library” Mankind.  It was a long time ago, and I don’t remember the details of any of the meetings I attended with the exception of one.  It is as clear today as it was some twenty years ago.  I stepped into a rather large conference room, standing room only, as I recall.  There was a panel of experts placed at the very front of the conference room on a stage with microphones for each and pitchers of water placed strategically on the table for all to share.  There was a standing microphone placed in the middle of the isle and as the panel completed their discussion, an anxious group of librarians lined up behind the microphone to say their piece.  Soon an angry tirade of heart felt opinions emerged.  I don’t remember the exact discussion, but I do remember it had something to do with the creation of an authority control record for “nuns”.* I was amazed at the passion and at times anger expressed in the varying opinions.  I remember thinking to myself, “What is wrong with these people!”

That, ladies and gentlemen, was my first introduction to what we know today as the ALA Annual Session of the Authority Control Interest Group.  Oh yes, there is great passion in authority control.

So, you may ask: what is the Authority Control Interest Group (ACIG), and why should I care?    We will start with the group’s history and mission.  The ACIG was established in 1984 by Barbara Tillett.  Its original name, “Authority Control in the Online Environment Interest Group” highlights the original purpose of the group, which was to bring about awareness to technical service librarians who were moving to the online environment. At that time most of the existing ILS systems had not configured authority control into their ILS systems.  In 2006 the name was shortened to, “Authority Control Interest Group”.   The goal of the group was to provide a forum for discussion of issues related to authority control for online cataloging.  The forum is used to raise the level of awareness on authority control issues and to encourage ideas for new approaches to authority control.  Each year officers are elected to coordinate overall activities of the interest group.  The group is co-sponsored by the LITA and ALCTS divisions of the American Library Association.  A program is presented at each ALA conference.  The programs typically address what is new in the world of controlled vocabulary.  A representative for the Library of Congress typically gives an update of what is going on with authority control within their organization.  OCLC usually sends a presenter to update the library world on OCLC involvement with authority control.   The rest of the panel usually consists of people who are either experts in an area the group is focusing on for that particular meeting, or people who have done research in the area that the group is focusing on for that meeting.  The sessions are usually well attended.  You can expect several hundred for the summer session.

Upon completion of the presentations, the ACIG group gathers to have a business meeting.  All who are interested are invited to attend.  In this meeting officers are elected and the next conference presentation is discussed.  Over the next six months, the Vice-Chair works with the library community and the ACIG committee to put together a presentation for next conference.

I have been involved with the Authority Control Interest Group for the last four years.  I found it a very good vehicle for keeping a pulse on the authority control world.  The group is always looking for volunteers and welcomes new members.  For more information on the ACIG please visit their wiki site at http://wikis.ala.org/lita/index.php/Authority_Control_IG

*Out of curiosity, I looked to see if there was a heading for nuns and there is.  It is listed below.  For the life of me, I don’t remember what the debate was about!

LDR                   00385cz   2200145n  4500

001                     sh 85093287

003                     DLC

005                     19961001105801.6

008                     860211i| anannbab|          |a ana |||

010                     $ash 85093287

040                     $aDLC$cDLC$dDLC

150         0         $aNuns

450         0         $aSisters (in religious orders, congregations, etc.)

550         0         $wg$aChristians

550         0         $aMonasticism and religious orders for women

Record Info

Ctrl No: sh 85093287

Record Date: 10/1/1996 10:58:01 AM

Last Updated/Loaded: 3/4/2009 1:56:25 AM

Usages: Subject

Rec Status:

**Post by John Reese, Chief Operating Officer of the Utah dept. of Backstage Library Works

Judy, one of the project managers would like opinions from multiple librarians on a question we are facing right now. Here’s what she had to say.

Hello Everyone, we are looking for feedback from our community:

MARC Proposal No. 2008-06 requested that $x ISSN’s be allowed in 8XX fields (http://www.loc.gov/marc/marbi/2008/2008-06.html) and the proposal was approved by Library of Congress on October 2, 2008.  Just recently OCLC has decided to begin allowing $x too (see their July 2009 Technical Bulletin 257 found at:  http://www.oclc.org/support/documentation/worldcat/tb/257/default.htm.

With LC’s switch from 440 to 490 and our programming changes to accommodate this, many of you are now getting $x ISSN subfields in your Bibliographic 8XXs.  This has been causing some concern and at least in one scenario, it creates a problem situation as follows:

original bib headings:
490_1 $aSTI/PUB ;$v1343
490_1 $aSafety reports series,$x1020-6450 ;$vno. 58
830_0 $aSafety reports series ;$vno. 58.

after processing:
490_1 $aSTI/PUB ;$v1343
490_1 $aSafety reports series,$x1020-6450 ;$vno. 58
830_0 $aSafety reports series ;$vno. 58.
830_0 $aSafety reports series,$x1020-6450 ;$vno. 58.

The resulting 830s happened this way because the 8XXs must link up with 490-1′s.  The system assumes the first 8XX belongs to the first 490-1 so it retained “Safety report series ;$vno. 58.”  Since it “thought” there was no 8XX for the second 490-1 an 8XX was created for it.  Unfortunately it was the first 490-1 that was missing a linking 8XX.

What is your practice regarding 8XX $x?  Since this is now an allowable subfield and we follow LC procedures, what will this do to your system?

Your feedback would be very welcome and much appreciated. Feel free to comment on this blog or talk about it on our Forum at:  http://ac.bslw.com/community/forum/viewtopic.php?t=34

Thanks,
Judy