We are gearing up our RDA Testing as one of the official Test Partners with LC and we wanted to share with you what we are doing. There will be more to come in the coming days and weeks, but our wonderful RDA Librarian Karen has put together what to expect right away. (more…)
Posts Tagged ‘Authority Records’
RDA Testing and Policies
Tuesday, September 7th, 2010Tags:Authority Records, RDA
Posted in Automated Authority Control, RDA | 1 Comment »
Adding to Authorities
Monday, August 16th, 2010Sometimes 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. (more…)
Tags:Authority Control, Authority Records, Automation
Posted in Authority Control, Authority Records, Automated Authority Control | Comments Closed
RDA Questions and Answers
Tuesday, July 20th, 2010Our 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 1st, 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. (more…)
Tags:Authority Control, Authority Records, Bibliographic Records, RDA
Posted in RDA | Comments Closed
What is Series Authority Control
Monday, March 29th, 2010Last week we talked a little bit about the history of how series have been handled, but what is series authority control? Of all the types of Authority Control (Names, Subjects, Series) series is likely the most complex aspect and can be quite overwhelming for both newcomers and veterans of Authority Control. Our Authority Librarian, Karen, has once again come to our aid to help explain what a series is, and how Authority Control works with series.
A series is defined by AACR2 as a group of separate items related to one another by the fact that each bears, in addition to its own title proper, a collective title applying to the group as a whole. A series under authority control uses a controlled or unique chosen access point for the collective title of a series in the analytic bibliographic records.
Series authority work is the process of controlling those collective titles through the use of authority records. Series authority work is done for the same reasons as name authority work; that is first, to create a single form of the series title which will collocate records so that the user can find all the records related to that resource; and second to create a unique form of the series title which will distinguish records for one resource from those for a different resource. Uniqueness is especially important since many series have the same or similar titles.
There are several decisions that need to be made to control a series. These decisions should be based on a standard such as AACR2.
The first decision is to decide which form of the series title will be used as the authorized form. A single, unique form of the title needs to be chosen often from among several variant forms. Then that decision needs to be recorded. Three possibilities for this include:
- Use the bibliographic record for the resource used for the series data to record the authorized form.
- Create an alphabetic listing of series in the library.
- Use a Series Authority Record (SAR)
The SAR provides the best method for access, and can also contain a lot of other valuable information about the series. The authority record can be on a card, or most commonly now, a machine-readable record. More on SAR’s below.
The second decision to make is how the series will be treated. How will you handle the parts of the series that come in to your institution? A couple of points to consider are:
- Analyze or not
- Class together or separately
The third decision is whether to trace the title or not. This means deciding whether to use the access point in your database or catalog.
It is important that these decisions be recorded because not all series will be handled in the same way. Actions taken for subsequent acquisitions need to be consistent. The most common way to record series authority records is a MARC 21 record format. Since MARC21 is a machine-readable format, the records can be updated at any stage in the workflow. They are based on standards and can be easily shared with the greater library community.
A Series Authority Record (SAR) is the means to generate consistency in any database (or catalog) and allow the retrieval of all the series in a logical display. The SAR should serve three functions:
- Provide a unique and authoritative heading. The record reflects the chosen form that will be used as an access point for the series for all bibliographic records containing references to the series. Uniqueness promotes consistency in the database and allows the retrieval of all analytics in a predictable display. Several fields in a MARC format SAR provide the required information. The 1xx field is used to record the chosen form of the series title. This is the authorized heading. Related to the function of the 1xx to record the chosen form, the 4xx fields are used to record variant forms of the heading (series title) that were not chosen as the authorized form. The 642 field provides the style of numbering to be used with the series if it is numbered and also provides consistency.
- Provide identification – the record should provide enough information to identify the resource used in doing the authority work for a particular series, and distinguish this series from all others. The 1xx and 4xx fields are also part of this function. Other fields providing identification are:
643 – contains the place and publisher of the series
670 – contains the time period of publication
642 – numbering example taken from the source listed in the first 670 field.
667 – this is a note field that is used to record other information that is valuable, but does not fit into other fields.
- Show the treatment – the SAR should be a record of the decisions regarding analysis, tracing, and classification. It can have both local and other decisions. Fields used for this function are:
050-090 – These fields record the call number chosen for the series if the decision is to class holdings together.
644 – this field records the analysis decision
645 – this field records the tracing decision
646 – this field records the classification decision (see fields 050-090)
One other type of SAR can actually be for something that is not a series. Many resources have phrases or other character strings that will not be considered as a series. Although a SAR is not required to record this conclusion, providing one with the documentation for the decision to not consider it a series will create consistency for questionable cases. It will also save time in the future by avoiding having to make the same decision over and over again as other materials come in.
In a MARC21 bibliographic record the 490 field is used to record the transcription of the series from the item. In this field, the series appears exactly like it does on the item. A 500 note field may also be used for the series. The 8xx fields (800, 810, 811, and 830) are used to provide a tracing for the series when needed. These fields will contain the authorized form of the series title. This demonstrates the need for the authority work to provide consistency. The series on items do not always appear the same way so there could be different headings in the 490 fields for the same series. But by having one authorized form, the 8xx fields for that series will always have the exact same heading. Without this consistency, it could be very difficult to find all the parts of the same series in the catalog or database.
Series authority records can provide effective management for the bibliographic headings and can also provide physical control of series holdings in the library. By creating series authority records and maintaining a database of the records (an authority file) consistency will be maintained. Time and effort will be saved in the future. As new materials come in, the work on the series and the decisions regarding it will not have to be done over and over again.
For a detailed explanation of Series authority work see the excellent power point presentation by Judith A. Kuhagen of the Cataloging Policy & Support Office at the Library of Congress. http://library.ust.hk/info/other/feb2005/series.html Although this presentation is from 2005 and some of the LC policies and MARC tags talked about have changed, the process of making the decisions needed for series authority work in gone into in great detail.
For more information on the changes to series policies and MARC tags see the article “A Brief History of Series Authority Work”
For more information on using the MARC21 standards, see the MARC21 Format for Authority Data http://www.loc.gov/marc/authority/ecadhome.html and the MARC 21 Format for Bibliographic Data http://www.loc.gov/marc/bibliographic/ecbdhome.html
Tags:Authority Records, Bibliographic Records, Series
Posted in Authority Control, Authority Records, Bibliographic Records, MARC | 2 Comments »
Brief History of Series Authority Work
Wednesday, March 24th, 2010Our Authority Librarian, Karen, provided me with this extremely useful and detailed history of the way series entries are handled in both bibliographic records and authority records.
Series description has changed and evolved over time along with other descriptive cataloging practices. Most changes have been realized in LC policies and standards as more libraries chose to follow LC practices.
Prior to Sept 1, 1989, the Library of Congress policy was to trace only some series. They would create series authority records (SARs) for all series cataloged and record the tracing decisions on the SARs.
In the 1960’s LC developed the MARC format for the computerized storage and exchange of bibliographic information. As series policies have changed, the MARC format fields dealing with series have also changed.
Up to 1978 when AACR2 was published (see below), MARC had the following fields defined for the input of series information: (All definitions are from Its Marc http://itsmarc.com/crs/Bib1468.htm)
400 – This field contains an author/title series statement in which the author portion is a personal name or a possessive pronoun that refers back to the name in the 100 main entry field in the record. Field 400 is both a series statement and a series added entry. When a 400 field is present, a corresponding 800 field is not used, since it would duplicate the 400 field
410 – This field contains an author/title series statement in which the author portion is a corporate name or a pronoun representing it that refers back to a 110 field . Field 410 is both a series statement and a series added entry. When a 410 field is present, a corresponding 810 field is not used, since it would duplicate the 410 field.
411 – This field contained an author/title series statement in which the author portion is a conference/meeting name or a pronoun representing it that refers back to a 111 field . Field 411 is both a series statement and a series added entry. When a 411 field is present, a corresponding 811 field is not used, since it would duplicate the 411 field.
The descriptions of the indicator values, subfields and input conventions associated with the 400, 410, 411 fields corresponded to those for the 100, 110, and 111 fields respectively, with the addition of subfields specifically for series:
$x – ISSN #
$v – Volume designation
440 – This field contains a series statement consisting of a series title alone. Used when the series statement and the controlled added entry form of the series title are the same. Field 440 is both a series statement and a series added entry.
490 – This field contains a series statement for which no series added entry is to be made, or for which the series added entry is in a controlled form different from that which appears in the series statement. Field 490 does not serve as a series added entry. When field 490 is used and a series added entry is desired, both the series statement (field 490) and a corresponding series added entry (800-830 fields) are separately recorded in the bibliographic record.
800 – This field contains an author/title series added entry in which the author portion is a personal name. It is used when the added entry form of a series is different from that in the corresponding series statement. An 800 field is usually justified by a series statement (field 490 ) or a general note (field 500 ) relating to the series.
810 – This field contains an author/title series added entry in which the author portion is a corporate name. It is used when the added entry form of a series is different from that in the corresponding series statement. An 810 field is usually justified by a series statement (field 490 ) or a general note (field 500 ) relating to the series.
811 – This field contains an author/title series added entry in which the author portion is a meeting or conference name. It is used when the added entry form of a series is different from that in the corresponding series statement. An 811 field is usually justified by a series statement (field 490 ) or a general note (field 500 ) relating to the series.
830 – This field contains a title series added entry in which the entry of the series is a conventional title. It is used when the added entry form of a series title is different from that in the corresponding series statement.
840 – This field contains a title series added entry in which the entry of the series is under uniform title . It is used when the added entry form of a series title is different from that in the corresponding series statement.
All of the 8XX fields are justified by a series statement (field 490) or a general note (field 500 ) relating to the series. No 8XX series added entry field was used in conjunction with a series statement in the 400-440 fields because each of these fields functions both as part of the bibliographic description and as a series added entry. The indicator and subfield definitions for 8xx fields are the same as the corresponding 1xx fields, except for the addition of the $x (ISSN) and $v (numbering designation) subfields
In 1978 the second edition of the Anglo-American Cataloging Rules was published. Changes in the rules with the largest impact on series were the rules to formulate entries for personal, corporate, and meeting names, which made a separate distinction between the descriptive transcription and the form of entry. So the new rules did not really provide for name/title series statements as part of the transcription. Under these rules, the authorized form of the series (established in the authority file in Series Authority Record) did not always match the form found on the item. So if the series were traced, it would need to be traced differently.
Library of Congress implemented AACR2 in January of 1981. Eventually the MARC tags changed to accommodate the new cataloging rules.
The 440 and 490 fields were revised and used for the transcription of the series statement from the item. Fields 400, 410, and 411 were no longer to be used for the transcription of the series from any type of material.
440 – This field contains a series title statement when the series statement and the controlled added entry form of the series title are the same. Field 440 is both a series statement and a series added entry (title is traced). When a 440 field is present, a corresponding 830 field is not used since it would duplicate the 440 field.
490 – This field contains a series statement for which no series added entry is to be made, or for which the series added entry is in a controlled form different from that which appears in the series statement. Field 490 does not serve as a series added entry. When field 490 is used and a series added entry is desired, both the series statement (field 490) and a corresponding series added entry (800-830 fields ) are separately recorded in the bibliographic record.
The 8XX fields were also revised to better accommodate the new rules. The 800, 810, and 811 fields contain a name/title added entry used as a series added entry in which the entry of the series in under personal name, corporate name, or meeting name respectively, when the series statement is contained in field 490 (Series Statement) or field 500 (General Note) and a series added entry is required for the bibliographic record. No 8XX series added entry field is used in conjunction with a series statement in the 400-440 fields because each field functions both as part of the bibliographic description and as a series added entry. The indicator and subfield definitions for 8xx fields are the same as the corresponding 1xx fields, except for the addition of the $x (ISSN) and $v (numbering designation) subfields:
In 1988 fields 400, 410 and 411 were officially made obsolete in the CAN/MARC format. They can still be used as local fields. This left only the 440 and 490 as transcription fields. Their definitions as well as the 8xx’s remained much the same. Instructions are given to convert to 4xx/8xx as follows
MARC 21 conversion to current fields:
If indicator 2 is 0 in the 400, 410 or 411:
- 4XX indicator 1 and all subfields except subfield $x convert to 8XX with same indicator 1 value and same subfields,
- 4XX $t, $v, $x are also copied to 490 $a, $v, $x, respectively
- 490 indicator 1 is set to 1.
If indicator 2 is 1 in the 400, 410 or 411:
- 4XX indicator 1 and all subfields except subfields $a and $x convert to 8XX with same indicator 1 value and same subfields,
- and all 1XX subfields are copied into the same 8XX, preceeding the subfields from the 4XX field,
- and 4XX $t, $v, $x are also copied to 490 $a, $v, $x, respectively; 490 indicator 1 is set to 1.
On Sept. 1, 1989, Library of Congress implemented a policy to trace all series. New series authority records showed the decision to trace. When they needed to update a series, they would not go back and re-catalog the previous items. The change in tracing decision would be recorded on the SAR using multiple 645 fields.
On June 1, 2006, the Library of Congress implemented its decision not to create/update series authority records and not to provide controlled series access points in its bibliographic records for resources in series. This meant that in newly created bibliographic records for LC original cataloging (040 $a is solely “DLC”), the series statement will be given in a 490 0# field and LC will stop using 8xx fields. This decision from LC was not well received by the cataloging community and even sparked a protest from LC catalogers
The Program for Cooperative Cataloging (PCC) will not follow this policy. Members will continue to provide controlled series access on records and create and maintain series authority records through their BIBCO, NACO, and CONSER programs. More details can be found under the PCC programs NACO, BIBCO, and CONSER, and in the PCC Series Statement http://www.loc.gov/catdir/pcc/seriesPCC.html.
LC will continue to support the PCC by deleting duplicate series records reported, answering questions if no research is needed, and coordinating and conducting series training. In newly created CIP-partnered cataloging, in PCC member copy used for cataloging, and in non-PCC copy cataloging, existing series statements/access points will be accepted as is and “passed through.” This will help prevent LC-issued records without series access points from overlaying records that have them in OCLC.
On June 6, 2008, MARBI (Machine-Readable Bibliographic Information) the interdivisional committee of the American Library Association that deals with MARC standards, approved the proposal to make field 440 (Series Statement/Added Entry-Title) obsolete in the MARC 21 Bibliographic Format. This was done after much debate in the library community. This decision leaves the 490 as the only field to record the transcription of the series statement from the item. The intention of the change is to resolve the long-standing problem of field 440 being both a descriptive field and a controlled access point. The assumption is that separating the two functions will result in a more reliable description and easier maintenance through automated authority control over time.
This led to another change approved by MARBI:
In the 490 tag, the first indicator value ‘1’ has been redefined to:
1 – Series traced in 8XX field
When value “1” is used, the appropriate field 800-830 is included in the bibliographic record to provide the series added entry using the authorized form even if that form matches the transcribed form in the 490 field. It was felt that since there are now few space limitations in online systems, the duplication of the data in 490 and 8xx should not be a problem. An 8XX field can still be justified by a both a series statement in the 490 field or a general note in a 500 note field.
At this same time a second MARC proposal was made and approved. This proposal made two changes:
Added $x subfield (ISSN) to 8XX fields.
Added $3 (Materials specified) added to field 490 and 8xx fields
The Library of Congress approved these proposals on October 2, 2008. They will continue to accept the 440 field in records, and will not be retrospectively changing any records to conform to these changes.
The library community has been somewhat divided on whether to implement these changes, some have, and some have not, or are still deciding. Libraries always have the option to formulate policies to fit their own circumstances.
This is where series description stands as of July 2009.
———————————
References:
Website “Its MARC” The Library Corporation: http://itsmarc.com/crs/Bib1468.htm
MARC21 Format for Bibliographic Data 1999 ed. Library of Congress Network Development and Marc Standards Office: http://www.loc.gov/marc/bibliographic/ecbdhome.html
MARC21 Format for Authority Data 1999 ed. Library of Congress Network Development and Marc Standards Office: http://www.loc.gov/marc/authority/ecadhome.html
Article “Series at the Library of Congress: June 1, 2006” on the Library of Congress website: http://www.loc.gov/catdir/cpso/series.html
Tags:Authority Records, Bibliographic Records, Series
Posted in Authority Records, Bibliographic Records, MARC | Comments Closed
AAT – Art & Architecture Thesaurus
Tuesday, October 27th, 2009Many 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
Tags:AAT, Authority Control, Authority Records
Posted in Authority Control | Comments Closed