400 likes | 636 Views
Next-Generation Description: FRBR and RDA. University of California, Berkeley School of Information IS 245: Organization of Information In Collections. Overview. Review: Description and AACRII Choice and Form of Headings Next-Generation Description FRBR RDA. Introduction to Description.
E N D
Next-Generation Description:FRBR and RDA University of California, Berkeley School of InformationIS 245: Organization of Information In Collections
Overview • Review: • Description and AACRII • Choice and Form of Headings • Next-Generation Description • FRBR • RDA
Introduction to Description • Description (or descriptive cataloging) is concerned with indentification of an item and recording information about the item so that it may be identified exactly and cannot be confused with another item. (From Wynar/Taylor)
Structure of AACRII • Part I: Description • Chap 1: General • Chap 2: Books, pamphlets and printed sheets • Chap 3: Cartographic Materials • Chap 4: Manuscripts • Chap 5: Music • Chap 6: Sound recordings • Chap 7: Motion Pictures and videorecordings • Chap 8: Graphic Materials • Chap 9: Computer Files • Chap 10: Three-Dimensional Artefacts and Realia • Chap 11: Microforms • Chap 12: Serials • Chap 13: Analysis
Structure of AACRII • Part II: Headings, Uniform Titles, and References • Chap 21: Choice of Access Points • Chap 22: Headings for persons • Chap 23: Geographic Names • Chap 24: Headings for Corporate Bodies • Chap 25: Uniform Titles • Chap 26: References
Organization of the Description • Title and statement of responsibility • Edition • Material specific details • Publication, distribution, etc. • Physical description • Series • Notes • Standard numbers and terms of availability
Choice of Access Points • Chapter 21 of AACRII is concerned with how to choose the elements of a description that will be made searchable – AKA “Access Points” • We will look a bit at the sort of rules that are used to decide what does and doesn’t get made searchable in (conventional) paper and online catalogs (and why)
Choice of Access Points • General Rule • 21.1A -- Personal authorship -- enter works by one or more persons under the heading for personal author. • 21.1B2 -- Corporate Body -- may be chosen as the main entry for an item if it falls into one or more of 6 categories.
21.1B2 Corporate Author Categories • a) The work deals with the body itself, such as a financial report or operations report, staff listing, or a catalog of the body’s resources. • b) Certain legal, governmental, or religious types of works listed in the rule: • laws; decrees of the chief executive that have force of law; administrative regulations; constitutions; court rules; treaties, etc.; court decisions; legislative hearings; religious laws (e.g. canon law); liturgical works
21.1B2 Corporate Author Categories • c) Those that record the collective thought of the body • reports of commissions or committees, official position statements, etc. • d) Those that report the collective activity of a conference (e.g.: proceedings , collected papers), an expedition (e.g.: results of exploration, investigation), or of an event falling within the definition of a corporate body -- provided that the conference, etc. is prominently named in the item
21.1B2 Corporate Author Categories • e) Those that result from the collective activity of a performing group as a whole where the responsibility of the group goes beyond that of mere performance, execution, etc. • Includes sound recordings, films, videorecordings, and written records of performances. • f) Cartographic materials emanating from a corporate body other than a body that is merely responsible for their distribution and publication
21.1B3 • If a work falls outside the categories, treat it as if no corporate body was involved. • Added entries are made for prominently named corporate bodies.
21.1C Entry Under Title • If there is no personal author, personal authorship is diffuse, and the work is not eligible under 21.1B2, when the work is a collection with multiple authorship or produced under editorial direction, or when the work is a text that a religious group accepts as sacred scripture.
Headings for Persons • Once you decide (via the Chapter 21 rules) that entries are to be made for a person or persons, you must then choose the form that the name will appear in.
General Rule • Choose, as the basis of the heading for a person, the name by which he or she is commonly known. This may be a person’s real name, pseudonym, title of nobility, nickname, initials, or other appellation. • Treat a roman numeral associate with a given name (as, for example, in the case of some popes, royalty, and ecclesiastics) as part of the name. • For authors using one or more psuedonyms or a real name and one or more psuedonyms, see 22.2b
Overview • Review: • Description and AACRII • Choice and Form of Headings • Next-Generation Description • FRBR • RDA
FRBR • FRBR stands for “Functional Requirements for Bibliographic Data” (there is also a FRAD for authority data) • It is a conceptual model of HOW bibliographic data should be considered • It is a significant departure from the principles behind AACRII (the Paris Principles) by adopting the Work, instead of the Item as a key element of description
21st century: AACR3 • In 2001, JSC (Joint Steering Committee) decided that FRBR terminology should be incorporated into AACR. Since that time, rule revisions have been proposed to ensure that FRBR terms will be used in AACR. This will require introduction of new terms as well as redefinition of existing usage. • The result is the new RDA (later) This and following slides are adapted from a talk by Don Thornbury (2005)
Development of FRBR • Impetus 1990 • 1) economic realities faced by libraries and the need to reduce the cost of cataloging; 2) importance of meeting user needs; 3) addressing the various types of material and the various contexts within which bibliographic records are used • Aim of the project • produce a framework that would provide a clear, precisely stated, and commonly shared understanding of what it is that the bibliographic record aims to provide information about, and what it is that we expect the record to achieve in terms of answering user needs • Drafting began 1995; published 1998 • http://www.ifla.org/VII/s13/frbr/frbr.htm
FRBR methodology • “The methodology used in this study is based on an entity analysis technique that is used in the development of conceptual models for relational database systems. Although the study is not intended to serve directly as a basis for the design of bibliographic databases, the technique was chosen as the basis for the methodology because it provides a structured approach to the analysis of data requirements that facilitates the processes of definition and delineation that were set out in the terms of reference for the study.” (2.3) Translation: We need to figure out what things we’re talking about in cataloging, what there is to say about them, and how they relate to one another.
FRBR entities: 3 types • Products of intellectual or artistic endeavor that are named or described in bibliographic records: work, expression, manifestation, and item. • Aggregate and Component entities: anthology, series, archival fond … [et al.]; chapter, article … [et al.] • Entities responsible for the intellectual or artistic content, the physical production and dissemination, or the custodianship of such products: person and corporate body. • Subjects of intellectual or artistic endeavour: the above entities, plus concept, object, event, and place.
Work : Expression : Manifestation : Item • A “distinct intellectual or artistic creation.” • An abstract entity: can be hard to define and delineate. • Attributes: title, form, date … [et al.]
Work : Expression : Manifestation : Item • The “intellectual or artistic realization of a work in the form of alpha-numeric, musical, or choreographic notation, sound, image, object, movement, etc., or any combination of such forms.” • Reflects distinctions in intellectual or artistic content between one realization and another of the same work. • Attributes: title, form, date, language, sequencing pattern (serial), type of score (musical notation), medium of performance (musical notation or recorded sound) … [et al.]
Work : Expression : Manifestation : Item • The “physical embodiment of an expression of a work;” “all the physical objects that bear the same characteristics, in respect to both intellectual content and physical form.” • Can be a set of items that result from a single act of production, or unique productions such as manuscripts, original oil paintings, etc. • Attributes: title, statement of responsibility, edition/issue designation, place and date of publication/distribution, publisher/distributor, series statement, foliation (hand-printed book), publication status (serial), playing speed (sound recording), reduction ratio (microform), mode of access (remote access electronic resource) … [et al.]
Work : Expression : Manifestation : Item • A “single exemplar of a manifestation.” • Often a single physical object (e.g., a copy of a one-volume monograph), but can be more than one (e.g., a monograph issued as two separately bound volumes, a recording issued on three separate compact discs, etc.) • Attributes: item identifier, provenance, marks/inscriptions, condition … [et al.]
Entity relationships • Relationships are “the vehicle for depicting links between one entity and another, and thus as the means of assisting the user to ‘navigate’ the universe that is represented in a bibliography, catalogue, or bibliographic database.” • Many kinds of relationships among entities: realization, embodiment, equivalence, whole-to-part, part-to-part … [et al.]
Other entity relationships • Work-to-Work: Successor, Supplement, Adaptation, Whole/Part … [et al.] • Expression-to-Expression: Translation, Abridgement … [et al.] • Manifestation-to-Manifestation: Reprint, Mirror site … [et al.] • Item: Bound with … [et al.]
FRBR and MARC • In LC’s action plan for bibliographic control of web resources (2001): • Enhance MARC 21 to support display of hierarchical relationships among records for a work, its expressions and its manifestations (based on the IFLA Functional Requirements for Bibliographic Records (FRBR)) • MARC to FRBR: 83 pages of element mapping (ca. 2600 data elements in MARC) • FRBR to MARC: 74 pages of element mapping
000 cam a 001 2465968 008 821108 s 1912 gw 0 0 0 0 ger d 035 ‚a (OCoLC)ocm08935092035 040 ‚a ZIH ‚c ZIH ‚d PUL 041 ‚a ger ‚h eng 100 ‚a Shakespeare, William, ‚d 1564-1616. 240 10 ‚a Hamlet. ‚l German 245 10 ‚a Hamlet, Prinz von Dèanemark / ‚c von William Shakespeare ;èubersezt von Heinrich Voss. 260 ‚a [Dèusseldorf : ‚b E. Ohle, ‚c 1912] 300 ‚a 145 p. ; ‚c 28 cm. 500 ‚a Number 141 of an edition of 200 copies.‚5 NjP 563 ‚a Bound by Carl Sonntag jun. in Leipzig. ‚5 NjP 700 1 ‚a Voss, Heinrich, ‚d 1779-1822. 852 8 ‚b ex ‚h 3925.342.11 876 ‚a 32101037428800 MARC
000 cam a 001 2465968 008 821108s 1912gw0 0 00gerd 035 ‚a (OCoLC)ocm08935092035 040 ‚a ZIH ‚c ZIH ‚d PUL 041 1 ‚a ger ‚h eng 100 1 ‚a Shakespeare, William, ‚d 1564-1616. 240 10 ‚a Hamlet. ‚l German 245 10 ‚a Hamlet, Prinz von Dèanemark /‚c von William Shakespeare ;èubersezt von Heinrich Voss. 260 ‚a [Dèusseldorf : ‚b E. Ohle, ‚c 1912] 300 ‚a 145 p. ; ‚c 28 cm. 500 ‚a Number 141 of an edition of 200 copies.‚5 NjP 563 ‚a Bound by Carl Sonntag jun. in Leipzig. ‚5 NjP 700 1 ‚a Voss, Heinrich,‚d 1779-1822. 852 8 ‚b ex ‚h3925.342.11 876 ‚a 32101037428800 Field data:WorkExpressionManifestationItem Record MARC: FRBR mapping
Resources • FRBR: • http://www.ifla.org/VII/s13/frbr/frbr.htm • Tillett: • http://www.loc.gov/catdir/cpso/frbreng.pdf; http://www.loc.gov/cds/downloads/FRBR.PDF • MARC and FRBR: • http://www.loc.gov/marc/marc-functional-analysis/frbr.html
From FRBR to AACR 3? • FRBR has been very influential and has informed the development effort for updating AACRII…
RDA • But, AACRII is on its last legs… • The next generation is Resource Description and Access (RDA) • intended to be released in the third quarter of 2009 • It is a new cataloguing standard to replace AACRII for ALL kinds of materials
RDA Overview • STATEMENT OF PURPOSE FOR RDA • RDA - Resource Description and Access will be a new standard for resource description and access, designed for the digital world. • Built on foundations established by the Anglo-American Cataloguing Rules (AACR), RDA will provide a comprehensive set of guidelines and instructions on resource description and access covering all types of content and media. • RDA will enable users of library catalogues and other systems of information organization to find, identify, select, and obtain resources appropriate to their information needs. From http://www.collectionscanada.gc.ca/jsc/stratplan.html
LONG TERM GOALS FOR RDA • The guidelines and instructions in RDA will be designed to: • Provide a consistent, flexible and extensible framework for both the technical and content description of all types of resources and all types of content. • Be compatible with internationally established principles, models, and standards. • Be usable primarily within the library community, but be capable of adaptation to meet the specific needs of other communities. • Descriptions and access points produced through the application of RDA guidelines and instructions will: • Enable users to find, identify, select, and obtain resources appropriate to their information needs. • Be compatible with those descriptions and access points devised using AACR2, and present in existing catalogues and databases. • Be independent of the format, medium or system used to store or communicate the data. • Be readily adaptable to newly-emerging database structures. • RDA will be developed as a resource description standard that is: • Optimised for use as an online tool (although a print edition will also be published). • Written in plain English, and able to be used in other language communities. • Easy and efficient to use, both as a working tool and for training purposes.
RDA Principles • From proposed standard: • RDA provides a set of guidelines and instructions on formulating data to support resource discovery. • The data created using RDA to describe a resource are designed to assist users performing the following tasks: • find—i.e., to find resources that correspond to the user’s stated search criteria • identify—i.e., to confirm that the resource described corresponds to the resource sought, or to distinguish between two or more resources with similar characteristics • select—i.e., to select a resource that is appropriate to the user’s needs • obtain—i.e., to acquire or access the resource described.
Entity Description • The data created using RDA to describe an entity associated with a resource (a person, family, corporate body, concept, etc.) are designed to assist users performing the following tasks:2 • find—i.e., to find information on that entity and on resources associated with the entity • identify—i.e., to confirm that the entity described corresponds to the entity sought, or to distinguish between two or more entities with similar names, etc. • clarify—i.e., to clarify the relationship between two or more such entities, or to clarify the relationship between the entity described and a name by which that entity is known • understand—i.e., to understand why a particular name or title, or form of name or title, has been chosen as the preferred name or title for the entity.
Relationship to other standards • RDA is built on foundations established by the Anglo-American Cataloguing Rules (AACR) and the cataloguing traditions on which it was based • Instructions derived from AACR have been reworked to produce a standard that will be easier to use, more adaptable, and more cost-efficient in its application. The need to integrate data produced using RDA into existing databases developed using AACR and related standards has been recognized as a key factor in the design of RDA. • Other key standards used in developing RDA include the International Standard Bibliographic Description (ISBD),8 the MARC 21 Format for Bibliographic Data,9 and the MARC 21 Format for Authority Data • The RDA element set is compatible with ISBD, MARC 21, and Dublin Core.11 For mappings of the RDA element set to ISBD, MARC 21, and Dublin Core