Archive for the ‘Authority Control’ Category

Authority Control Interest Group (ACIG)

Monday, October 19th, 2009

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

Your New Automation Services Department

Friday, October 9th, 2009

John Reese, the former Product Manager for Authority Control, has been promoted to Chief Operating Officer within our company. John is still available to all of us and we welcome his input whenever we get a chance to hear it (jreese@bslw.com).

Nate Cothran has been promoted to Vice President of Automation Services and continues to look for innovative ways to serve you better. Nate has chosen Jeremy Myntti (jmyntti@bslw.com) as the new Project Manager for Authority Control services, which also includes Judy Archer (jarcher@bslw.com).  All of us look forward to working with you on your future projects and welcome any questions, concerns or suggestions.

Backstage Library Works Automated Services

Monday, August 31st, 2009

You may have noticed that we’ve recently changed the name of this blog from MARS Authority Control to MARS Automation Services. Why the change? I’ve asked our Chief Operations Officer of the Utah location, John Reese, to explain why. Here is what he had to say.

***

Before the purchase of MARS from OCLC, Backstage Library Works ran several bibliographic automated products.  These services include Non-MARC or Brief MARC Record Upgrades (Machine Matching), Deduplication and Consolidation of bibliographic data, Union Database creation, Marcadia and Custom Programming.  Prior to this week, these services were run independent of the MARS 2.0 Automated Authority Control Service.  Backstage is happy to announce the consolidation of all of the above mentioned services and MARS 2.0 Automated Authority Control under one division to be called, “Backstage Library Works Automated Services.”

We found that there was a lot of overlapping in client needs involving authority control with the above mentioned automated bibliographic services.  All of these services require technical knowledge of the automated process.  At Backstage we are now sharing this valuable resource under one umbrella, Automated Services.  We look forward to having one department work with your sales representative in offering the most efficient automated solution for you.  Below is a list of all of the services under our newly formed Automated Services department.  If you have question about this change please contact John Reese, jreese@bslw.com.

MARS 2.0 Automated Authority Control:

MARS 2.0 service is one of the oldest and most reliable automated authority control offerings on the market. With our new system upgrade introduced in 2008, managing your authority records has never been easier.  MARS 2.0 offers name and subject authority control based on the Library of Congress name and subject authority databases (and other available National databases like MeSH, NLC, etc.).  The authority control process standardizes name, subject, series and Uniform title headings.

Automated Machine Matching:

This service offers several options to upgrade non-MARC or brief MARC records to full MARC bibliographic records.  This process searches electronic records against Backstage Library Works database and the Library of Congress Bibliographic Database to return a full standard MARC record.  There are over twenty million records to match against in this database.

Automated Deduplication:

Backstage Library Works offers a deduplication process that consolidates bibliographic or authority records in a library’s database(s).  This process is performed according to the profile specifications of the library and is often used when a library or a library consortia is forming or adding new libraries.

Union Database Creation:

Library consortia or library districts often require a central database for their consortia to work from. Backstage helps libraries create Union Bibliographic as well as Union Authority databases.

Marcadia:

Marcadia is an automated batch copy cataloging service offered jointly by OCLC and Backstage Library Works.  This product finds, evaluates and delivers catalog records from OCLC WorldCat.  It is based on search records you supply from your local system and a selection criterion you provide.  Marcadia selects matching records from WorldCat and delivers them to you.

Custom Programming:

It has been a long standing Backstage Library Works’ tradition to customize our services to the needs of our libraries.  Many libraries require special programming to accommodate either earlier cataloging practices that no longer meet current standards and need to be changed or special programming to create unique processes for their library.  Backstage takes pride in its ability to accommodate these special needs.

Anatomy of an Authority Record

Tuesday, August 18th, 2009

Those of us in the Authority side of library sciences (the dark side?) talk a lot about Authority records, but while most librarians understand bibliographic records, understanding authority records requires a whole different understanding. To help cover that, we had one of our Project Managers explain exactly what an authority record is, and whats in it.

One of the reasons Authority Control was developed was to keep headings consistent.  Just think how much fun it would be trying to sort out whose published work was whose, if there wasn’t some way to consistently clarify each author or subject or series.  For example, if you have 5 books written by 5 John Smiths, unless there is a standard for each John Smith (one is Smith, John, Jr., one is Smith, John,$d1957- , one is Smith, John$q(Johnathan), etc.) it could get crazy.

For all libraries who participate (and that’s most of them) a standard is established for every single heading created (called the “authorized form”).  Whenever a heading is used on a bib record, that authorized form should be the one a library uses.  That’s why you may enter a heading on a bib record but if we do authority control on it you might see it flipped to something else.  Currently the Library of Congress gives final approval for that standard and an authority record is created for every single heading.  What we do in the Authority Control department is help libraries manage their authority data.

All headings fall under 4 categories:  (1) NAMES; (2) NAME/TITLE COMBOS; (3) UNIFORM TITLES/SERIES; and (4) SUBJECTS.  There are also genre authorities and these come from different databases.

In the bibliographic record you have 1XX’s, 4XX’s, 6XX’s, 7XX’s and 8XX’s as the tags under authority control.  On an authority record, the authorized headings are in the 1XX of the authority record.  The “see-references” and “see-also” references are found in the 4XX and 5XX of the authority record.  Here’s an example of how the headings sync up:

Your Bib: 100 1_ $aRowling, J. K.

Authority Record: 100 1_ $aRowling, J. K.

Your Bib: 100 1_ $aRowling, J. K.

240 10 $aHarry Potter and the prisoner of Azkaban

Authority Record: 100 1_ $aRowling, J. K.$tHarry Potter and the prisoner of Azkaban

Your Bib:  440_0 $aHarry Potter and the prisoner of Azkaban (Motion picture)

Authority Record: 130_0 $aHarry Potter and the prisoner of Azkaban (Motion picture)

(ditto if this were an 830)

Your Bib:  650 _0 $aPotter, Harry (Fictitious character)

Authority Record150 _0 $aPotter, Harry (Fictitious character)

Your Bib: 651 _0 $aLondon (England)

Authority Record: 151 _0 $aLondon (England)

Your Bib:  710 2_ $aWarner Bros.

Authority Record: 110 2_ $aWarner Bros.

So …what are the parts of an Authority Record?  They are:

0XX =  These are standard numbers, classification numbers, codes, etc.  (Mostly you’ll see 001, 003, 005, 008, 010, 035, 040, 043).  A few comments about the usual ones:

001 =  In bib records this is a bib ID number (wln, oclc, etc.) – in authorities it’s the owning agency, typically the Library of Congress’, control number.  On a bib record this LCCN is found in the 010.  On the LC authority record it is the 001.

005 =  This is a date/time stamp – it will show the last time an authority record was updated.  Example:  20030808053519.0.  2003 is the year, 08 is the month, 08 is the day, and then the rest of the numbers equate down to the minute and second.

008 =  A fixed field – this field is very similar to a bib record in that it provides info on how an authority can and cannot be used (example:  it can be used as a name and/or subject heading, it can’t be used as a serial).

010 =  This is a repeat of the 001 control number.  Past control numbers appear here too:

010  $an  79065753 $zno 92031869

1XX =  Your main heading (whoo-hoo!) = see above explanation for how they match up with bib headings.  You will see:  100, 110, 111, 130, 150, 151, 155 and 185.  The 155 is for genres (which show up on bibs as 655_0 or 655_7 with a $2) and the 185 is for subject subfields (for instance, the $x in a 650 tag).

2XX =  Complex see-references.

3XX =  Complex see-also references.

4XX =  See-from references = These lead a user from an older, not authorized heading to the current valid heading (1XX).  In the authority record the tag structure typically reflects that of the 1XX:  400, 410, 411, 430, 450, 451, 455, 485.

5XX =  See-also references = These lead a user from one valid heading to another related valid heading.  In the authority record the tag structure typically reflects that of the 1XX:  500, 510, 511, 530, 550, 551, etc.

When a patron wants to look something up in an authority file on their ILS system, their findings will reflect what is found on an authority record.  For example, The authority Record below:

100 1_ $aTwain, Mark,$d1835-1910

400 1_ $aConte, Louis de,$d1835-1910

500 1_ $aClemens, Samuel Langhorne,$d1835-1910

Would Display as follows on your typical ILS System:

Twain, Mark, 1835-1910

See also:          Clements, Samuel Langhorne, 1835-1910

Clements, Samuel Langhorne, 1835-1910

See also:          Twain, Mark, 1835-1910

Conte, Louis de, 1835-1910

See:                 Twain, Mark, 1835-1910

6XX =  Notes.  These are used to explain various aspects of the authority record or to justify the heading.  The most common ones you see are 667 and 670.

7XX =  Heading Linking entries.  The most common one is the 781 field, which may show you how a geographic subdivision should be used.  Example:  781 $zIreland$zDublin.

8XX =  Alternative graphics.

9XX =  Library of Congress local tags.

By Judy Archer

Basic Authority Control Terms for Novices

Tuesday, July 7th, 2009

Authority Control is a specialized subset of library science and has it’s own unique vocabulary. To help librarians and administrators who may be dealing with authority control for the first time we’ve created, and are continuing to create, resources for both authority novices and experts. Today, we’ve asked our resident Authority Librarian to give us a brief and basic overview of Authority Control. We hope it helps.

Some basic authority control terms:

Authority control

The term used in library and information science to refer to the practice of consistent use and maintenance of the forms of names, subjects, uniform titles, etc. used as headings in a catalog. Authority control fulfills two important functions.

1)  It enables catalogers to disambiguate items with similar or identical headings.

2)  It is used by catalogers to collocate materials that logically belong together, although they present themselves differently.

Authority control can provide the underlying structure of the catalog when this process is used to create links between bibliographic records and the authority file.

Authority work

The process of determining the form of a name, title, or subject concept that will be used as a heading on a bibliographic record; determining cross references needed to that form; and determining relationships of this heading to other authoritative headings.

Authorized Heading

The form of an entry, i.e., the word(s) or phrase(s) chosen to provide an access point to the bibliographic record in the catalog or database.

Cross-reference

An alternate heading which directs the user to either the established form of a heading or to related headings Through the use of see and see also references, authority control creates a syndetic structure that guides the user to the materials sought.  This structure forms the pillar of authority control and makes possible efficient access to resources

See Reference – variant forms from the chosen, or authorized form of the heading.  They are used to lead the searcher to the proper form of the heading.

See Also Reference – Related form of a heading that is also an authorized heading.

Authority record

A record which shows a heading in the form established for use in the catalog; lists the cross-references to be made to and from the heading, cites the sources consulted in establishing the heading, and includes any other information that would be pertinent to the heading and its use.

Authority file

A set of authority records listing the chosen form of a heading and its appropriate cross-references. Types of authority files include name authority, series, and subject authority files

Library of Congress file are widely used.  They have separate name and subject files, but they are indexed together for searching at http://authorities.loc.gov/ In addition to using a national authority file, individual institutions may have local authority files.

Global change

The ability to change every occurrence of a specified string of characters in a catalog, usually by using one command to change all representations of a heading from one form to another form.  This is facilitated by actually linking the authority headings to the bibliographic records.

We have even more resources, including an extensive and growing terminology page on our Wiki.

RDA Test Site

Friday, June 19th, 2009

Backstage Library Works chosen to test RDA

The Library of Congress announced the selected RDA test partners and Backstage Library Works is one of only two vendors accepted to test the RDA cataloging structure.  Authority Control Librarian, Karen Anderson will lead the testing group at Backstage Library Works.  The complete testing list as well as background on the test process can be found at the Website for Testing Resource Description and Access (RDA): http://www.loc.gov/bibliographic-future/rda/test-partners.html