hello rda, goodbye aacr2/67531/metadc86157/m2/1/high_res_d/rda...hello rda pre-conference, tla...

Hello RDA, Goodbye

AACR2! Pre-conference April 15, 2008

Texas Library Association

Annual Conference Dallas, Texas

Agenda

7:30-8am Check-in 8-8:15am Introductions and Overview 8:15-10 Role of Functional Requirements for Bibliographic Records

(FRBR) and Functional Requirements for Authority Data (FRAD), 10-10:15 Break 10:15-noon RDA : structure, key changes from AACR2, discussion on how it

will affect what we do, etc. Noon -1pm Lunch on your own (see handout for restaurants) 1:15-2 RDA continued: examples, affect on catalogs 2-2:45 Vendor issues, Carol Seiler from AMIGOS 2:45-3 Break 3- 3:45 Pre-implementation strategies, learning resources, what we need to

do to keep informed 3:45-4pm Wrap-up, Survey

Hello RDA! Goodbye AACR2!

Pre-conference

Presenter Shawne D. Miksa, Ph.D.

Assistant Professor School of Library and Information Sciences

University of North Texas

Tuesday, April 15, 2008

Selected Readings

Texas Library Association Annual Conference

Texas Catalogers and Classifiers Round Table

Hello RDA, Goodbye AACR2!

The selected reading packet distributed to participants included the following documents: Tillett, B. (2004). What is FRBR? Washington, D.C. : Library of Congress. Available at http://www.loc.gov/cds/downloads/FRBR.PDF Documents available from the website of the Joint Steering Committee for the Development of Resource Description and Access

• RDA Scope and Structure (December 2007) [PDF format]. • RDA Element Analysis (December 2007) [PDF format]. • RDA to FRBR mapping (December 2007) [PDF format]. • RDA to FRAD mapping (December 2007) [PDF format]. • Draft RDA Objectives and Principles (December 2007) [PDF format] • Prospectus

Texas Library Association (TLA) Annual Conference April 15, 2008

http://www.loc.gov/cds/downloads/FRBR.PDF

http://www.collectionscanada.gc.ca/jsc/docs/5rda-scoperev2.pdf

http://www.collectionscanada.gc.ca/jsc/docs/5rda-elementanalysisrev.pdf

http://www.collectionscanada.gc.ca/jsc/docs/5rda-frbrmappingrev.pdf

http://www.collectionscanada.gc.ca/jsc/docs/5rda-fradmapping.pdf

http://www.collectionscanada.gc.ca/jsc/docs/5rda-objectivesrev.pdf

http://www.collectionscanada.gc.ca/jsc/rdaprospectus.html

Hello RDA pre-conference, TLA Annual Conference, April 15, 2008, Dallas, TX

1

Hello RDA, Goodbye AACR2!Sponsored by:

Texas Regional Group of Catalogers and Classifiers

AMIGOS

School of Library and Information Sciences, UNT

Texas Library AssociationAnnual Conference

Dallas, TXApril 15, 2008


2

Introduction and Overview

Welcome!IntroductionsAgenda and materialsBreaks and Lunch

Breaks: 10 and 2:30Lunch: noon-1pm (on your own)

Survey


3

Crowded room with 135 attendees!


4

AACR2—1978 to current

AACR2Parts I

Part I addresses descriptive cataloging based on division by format.

Chapter 1 GeneralChapters 2-12 based on

formatChapter 13 Analytical

AACR2Part 2Addresses choice and formation of personal corporate body, title access points

http://www.collectionscanada.ca/jsc/history.html


5

RDA is….

“RDA is a content standard, not a display standard and not a metadata schema. RDA is a set of guidelines that indicates how to describe a resource, focusing on the pieces of information (or attributes) that a user is most likely to need to know. It also encourages the description of relationshipsbetween related resources and between resources and persons or bodies that contributed to creation of that resource.”(Oliver, 2007, Changing to RDA)


6

Intention of RDA

Broaden the statement of principles (Paris Principles)All types of resources (not just books)Bibliographic relationships, descriptive cataloging, not Subject Cataloging at this timeAccess (not just choice and form of entry, but all access for bibliographic and authority records)

Builds onGreat cataloguing traditions of the worldFRBR and FRAR and future FR-Subjects


7

StakeholdersJoint Steering Committee for Development of Resource Descriptionand AccessAmerican Library Association (ALA)

Association for Library Collections and Technical Services (ALCTS)Cataloging and Classification Section

RDA Implementation Task ForceAustralian Committee on Cataloguing (ACOC)The British LibraryCanadian Committee on Cataloguing (CCC)CILIP: Chartered Institute of Library and Information ProfessionalsThe Library of CongressInternational Federation of Library Associations and Institutions (IFLA) Dublin Core Metadata Initiative (DCMI) RDA/MARC Working Group You………………………………………..to name a few…..

http://www.collectionscanada.ca/jsc/index.html

http://www.collectionscanada.ca/jsc/index.html

http://www.ala.org/

http://www.ala.org/ALCTSTemplate.cfm?Section=alcts

http://www.ala.org/ALCTSTemplate.cfm?Section=alctssectionscont&Template=/TaggedPage/TaggedPageDisplay.cfm&TPLID=16&ContentID=7991

http://www.nla.gov.au/lis/stndrds/grps/acoc/acoc.html

http://www.bl.uk/

http://www.collectionscanada.ca/ccc/ccc-e.htm

http://www.cilip.org.uk/default.cilip

http://www.loc.gov/

http://www.ifla.org/index.htm

http://dublincore.org/


8

Resource

—a resource is an identifiable information object, either tangible or intangible in nature

…. anything that has identity. Familiar examples include an electronic document, an image, a service (e.g., "today's weather report for Los Angeles"), and a collection of other resources.

http://dublincore.org/documents/abstract-model/

http://dublincore.org/documents/abstract-model/


9

Functionality is IN…FRBR and FRAD are conceptual models resulting from the international cataloguing community’s effort to address…

a constantly changing information environment, emergence of new forms of information resourcesincreasing density of networked information systems

Most importantly, broader range of user expectations and needs..

FindIdentifySelectObtain

Functional Requirements for Bibliographic Records (FRBR)http://www.ifla.org/VII/s13/frbr/frbr.htm

Functional Requirements for Authority Data (FRAD)http://www.ifla.org/VII/d4/FRANAR-ConceptualModel-2ndReview.pdf

http://www.ifla.org/VII/s13/frbr/frbr.htm

http://www.ifla.org/VII/d4/FRANAR-ConceptualModel-2ndReview.pdf


10

Why do we need a conceptual framework?

FRBR Attributes and relationships associated with work, expression, manifestation, and item

Four user tasks: find, identify, select, obtainGood resource: What is FRBR?--Tillett, B.

FRAD attributes and relationships associated with entities person, corporate body, place, work, expression, manifestation, and item

Beyond these fundamentals, (RDA will not yet address those additional attributes and relationships associated with these entities named above)



11

User Tasks, objectivesUser tasks...their expectations and needs..

FindIdentifySelectObtain

Svenonius (2000) addsNavigate

To find entities in a file or database; to identifyentities (to confirm); to select entities that are appropriate to the user’s needs; to obtain the entities (to access it); to navigate a bibliographic databaseFinding, collocating, choice, acquisition, and navigation objectives (Svenonius, 2000, p.20)


12

FRBR Entity Groups and Levels (chart borrowed from http://www.frbr.org/files/entity-relationships.png, at the FRBR Blog at http://www.frbr.org/ )

http://www.frbr.org/files/entity-relationships.png

http://www.frbr.org/


13

Bibliographic Relationships and WEMI

How we envision relationships between information resources of all types, formats, etc equivalent, derivatives, descriptive, whole-part, part-to-part, sequential—a necessary framework for relating resources within a library catalog (see Tillett’s What is FRBR?)work, manifestation, expression, item—much discussion on what these actually mean



14

Work

From FRBR:“A work is an abstract entity; there is no single material object one can point to as the work. We recognize the work through individual realizations or expressions of the work, but the work itself exists only in the commonality of content between and among the various expressions of the work. When we speak of Homer's Iliad as a work, our point of reference is not a particular recitation or text of the work, but the intellectual creation that lies behind all the various expressions of the work.”


15

ExpressionFrom FRBR:“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. An expression is the specific intellectual or artistic form that a work takes each time it is "realized." Expressionencompasses, for example, the specific words, sentences, paragraphs, etc. that result from the realization of a work in the form of a text, or the particular notes, phrasing, etc. resulting from the realization of a musical work. The boundaries of the entity expression are defined, however, so as to exclude aspects of physical form, such as typeface and page layout, thatare not integral to the intellectual or artistic realization of the work as such. any change in intellectual or artistic content constitutes a change in expression


16

ManifestationFrom FRBR:“the physical embodiment of an expression of a work. The entity defined as manifestation encompasses a wide range of materials, including manuscripts, books, periodicals, maps, posters, sound recordings, films, video recordings, CD-ROMs, multimedia kits, etc. As an entity, manifestation represents all the physical objects that bear the same characteristics, in respect to both intellectual content and physical form.”The boundaries between one manifestation and another are drawn on the basis of both intellectual content and physical form. When the production process involves changes in physical form the resulting product is considered a new manifestation.


17

ItemFrom FRBR:a single exemplar of a manifestation. The entity defined as itemis a concrete entity. It is in many instances a single physical object (e.g., a copy of a one-volume monograph, a single audio cassette, etc.). There are instances, however, where the entity defined as item comprises more than one physical object (e.g., a monograph issued as two separately bound volumes, a recording issued on three separate compact discs, etc.). Defining item as an entity enables us to separately identify individual copies of a manifestation, and to describe those characteristics that are unique to that particular copy and thatpertain to transactions such as circulation, etc. involving thatcopy. Defining the entity called item also enables us to draw relationships between individual copies of manifestations.


18

How does WEMI work?Example: Wizard of OzExample: Harry Potter seriesSeven original books, as written by J.K. Rowling (see

http://www.frbr.org/2006/06/13/eg-1 for a good illustration of this example)

What is the “work”?What is an “expression”?What is a “manifestation”?What is an “item”?(here we listed our understanding of the entity levels as

per WEMI)

http://www.frbr.org/2006/06/13/eg-1


19

Snapshot of whiteboard during discussion (please note that Ed O’Neill, from OCLC, is not the Wizard. Earlier, we referred to his analysis of Humphrey Clinker records.)


20

AACR2 vs RDA: difference in proportions

(See comparison chart included in handouts)AACR2

Description of information entities—13 chapters (Part 1)Weak on access points; talks of main and added (MAP, AAP), have to look all over Part II for access point provisions (e.g., title access points are discussed in chapter 21 only and then only as a default provision, not much direction)Is not really based on the idea of a “work”, rather it is very much based on the unit record system.


21

AACR2 vs RDA, continuedRDA

Description is covered in 4 chapters, everything else is about access pointsForm is no longer the first decision; chapters are not based on form (e.g., no longer have chapters 2-12 as in AACR2)Does not focus on the unit record system—it can be, but it doesn’t need to do so—rather it operates on the idea of a “work”Does not put the cataloger in the decision of having to decide Main and Added Access points; we don’t need those distinctions any longer although it does use the idea of a “preferred access point”Lots of discussion ensued about the difference in “proportions”and the move away from main access point designation to “Preferred access points” and the differences that would make in the cataloging process (e.g., affect on using Cutter numbers)


22

Structure of RDA (see booklet)Recording attributes

Section 1. Recording attributes of manifestation and itemSection 2. Recording attributes of work and expressionSection 3. Recording attributes of person, family, and corporate bodySection 4. Recording attributes of concept, object, event, and place

Recording relationshipsSection 5. Recording primary relationships between work, expression, manifestation, and itemSection 6. Recording relationships to persons, families, and corporate bodiesSection 7. Recording relationships to concepts, objects, events, and places associated with a workSection 8. Recording relationships between works, expressions, manifestations, and itemsSection 9. Recording relationships between persons, families, and corporate bodiesSection 10. Recording relationships between concepts, objects, events, and places

As described by the Joint Steering Committee for Development of RDA, Nov 2007)

http://www.collectionscanada.ca/jsc/rda-new-org.html




23

Structure of RDA (continued)“Each section will contain a chapter of general guidelines and chapters for the entities. Each chapter will be associated with one of the FRBR user tasks and one or more FRBR entities; for example, chapter 2 in section 1 will cover elements primarily used to identify a manifestation or item and chapter 19 in section 6 will cover elements primarily used to find a work. The chapters on recording attributes and relationships for the FRBR group 3 entities (concept, object, event, and place) will be placeholders, provided to allow a complete mapping to FRBR and FRAD and as a template for possible future development of RDA to cover these entities. Instructions on recording the attributes and relationships for places have been included, but will not initially go beyond the scope of AACR2 chapter 23.”

“In addition to these sections, there will be a General Introduction, Glossary, and various appendices, including those on capitalization, abbreviations, initial articles, and data presentation included in the current RDA Prospectus.”

(Joint Steering Committee for Development of RDA, Nov 2007)



24

One of the many questions that came up at the workshop concerned GMDs: Will there be a more comprehensive list of GMDs (general material designation) and SMDs (specific material designation) in RDA? (question and answer taken from the FAQ on the RDA website)

Representatives from the publishing community, ONIX, and the JSChave looked specifically at the types of content and carriers covered in RDA. Information about type and form of content and type and form of carrier will still be recorded, but the terms used will likely change. Aspects of the resource being described that relate to the type of content, such as cartographic, textual, or numeric will be declared or recorded separately from aspects relating to the type of carrier(microform, electronic resource, etc.). There will still be the possibility to give users an "early warning" regarding the type (content type, carrier type, or mixture) of material described in the record, but that will be determined in relation to the display or presentation of the data rather than the recording of the data.The SMDs will likely continue to be a mixture of established terms and common usage terms.At the JSC website there are is very useful FAQ that addresses many of cataloging community’s questions. See http://www.collectionscanada.gc.ca/jsc/rdafaq.html#1

http://www.collectionscanada.gc.ca/jsc/rdafaq.html#1


25

How much of FRBR is covered in RDA?

FRBR Attributes and relationships associated with work, expression, manifestation, and item

Four user tasks: find, identify, select, obtainGood resource: What is FRBR?--Tillett, B.

FRAD attributes and relationships associated with entities person, corporate body, place, work, expression, manifestation, and item

Beyond these fundamentals, RDA does not yet address those additional attributes and relationships associated with these entities named above



26

How much will I have to re-learn?RDA now outlines the first step in creating a catalog record as deciding on the type of description to be represented, and not deciding on format, although format is still integralTypes of description (rules 1.2)

Comprehensive, analytical, or multi-level descriptionSee flowchart on decision process

More emphasis on showing bibliographic relationships (e.g., taxonomy of bibliographic relationships) in order to better allow clustering of records

Read--works by B. Tillett, R. Smiraglia; M. Yee, S. Vellucci, E. O’Neill, D. Vizine-Goetz, just to name a few…

http://www.collectionscanada.ca/jsc/docs/5rda-part1.pdf


27

Preparation

Cataloging community must study the conceptual model offered by FRBR and FRADRead and study drafts of RDA as releasedProvide feedback to JSC

Vendors must consider re-design of their systems in order to incorporate new functionality of bibliographic and authority data


28

When is RDA to be released?

RDA timeline (subject to change):July-September 2007: Review of revised chapters 6-7December 2007-March 2008: Review of part BJuly-September 2008: Review of complete draft of RDA1st quarter of 2009: Release of RDA

http://www.collectionscanada.gc.ca/jsc/rda.html

http://www.collectionscanada.gc.ca/jsc/rda.html


29

Implementation StrategiesRDA Implementation Task Force (CCS/ALCTS)

Charged to develop a plan for the implementation of RDA: Resource Description and Access in the United States.

Training/continuing education activities Communication with OCLC and the Library of Congress Consultation with colleagues involved in the implementation of AACR2 The Task Force will develop an integrated timetable for the above activities, identify persons or organizations that will take the lead for each activity, and provide coordination as necessary through CCS/ALCTS in collaboration with LC, PCC, OCLC, and other appropriate bodies

http://www.ala.org/ala/alctscontent/catalogingsection/rdaimplement/rda.htm


30

Debates and Issues about RDA

Plenty of debate and criticism, as well as support of RDA

Listservs (e.g., AUTOCAT, RDA-L)Journals (e.g., LRTS, CCQ, LJ, D-Lib)Working groups, task forces

Investigate the library associations and institutions

Conferences (e.g., ALA, ASIST, MLA, AALL)Research past conference proceedings, and look for future conference announcements


31

Working Group for the Future of Bibliographic Control at the Library of Congress

Formed 2006 and charged to:Present findings on how bibliographic control and other descriptive practices can effectively support management of and access to library materials in the evolving information and technology environment Recommend ways in which the library community can collectively move toward achieving this vision Advise the Library of Congress on its role and priorities

(taken from the WG website, linked above)

http://www.loc.gov/bibliographic-future/




32

WG Recommendation 4.2Presented their preliminary recommendations Nov. 13, 2007 at

the Library of Congress, recommendation 4.2 directed at RDA. The working group expressed their concerns about the new guidelines:

RDA is being written on a framework that is not yet tested--FRBR concepts need to be tested on real cataloging data "Temporarily suspend all further new work on RDA" need thorough exploration of FRBR and implications on bibliographic control WG needs assurance that RDA is based on practical reality as well as on theoretical construct, that this would improve the support for the new code need more info on cost of implementation need identification of the real benefits of implementation need info on hospitality of systems to be able to handle the newrules urge the JSC to go back and address these outstanding issues, as well as language issues, organization, and usability



33

Does this mean RDA development will cease?

The WG’s recommendation is just that…a recommendationThe JSC has already taken action to restructure RDA to more fully address the FRBR conceptual frameworkThere are many studies and tests on how to operationalize the concepts outlined in FRBR

FRBR Bibliography--available from IFLA FRBR Display Tool--Library of Congress OCLC research on FRBR--list of projects and publications

http://www.collectionscanada.ca/jsc/news.html

http://www.ifla.org/VII/s13/wgfrbr/bibliography.htm

http://www.loc.gov/marc/marc-functional-analysis/tool.html

http://www.oclc.org/research/projects/frbr/


34

But, I have more questions, such as…

What about vendors—what are they doing about RDA?

This is still an unknown variable, but all indicators say that vendors are asking the same thing about the cataloging community. (Carol Seiler, AMIGOS, presented some info on her conversations with several vendors)Obviously, we need more dialog and more research on the impact that RDA will have on our practice and processesNeed to submit “Requests for Enhancements” to your vendor. Tell them what you need!


35

What about MARC? How will RDA change this standard?

We don’t have complete answers about how MARC will change with the adoption of RDA. The RDA/MARC Working Group has formed to address these questions:

Under the auspices of the British Library, the Library and Archives Canada, and the Library of Congress, an RDA/MARC Working Group has been established to collaborate on the development of proposals for changes to the MARC 21 formats to accommodate the encoding of RDA data. With the implementation of RDA anticipated for late 2009, the Working Group will be drafting proposals for review and discussion by the MARC community in June 2008.Although the MARC 21 formats support the encoding of descriptions created according to a wide range of content standards, the close relationship between AACR and MARC 21 has contributed to the efficient exchange of information among libraries for decades. The RDA/MARC Working Group will identify what changes are required to MARC 21 to support compatibility with RDA and ensure effective data exchange into the future.

(Taken from an email posted by Marjorie Bloss to RDA-L on April 13, 2008. See accompanying word file with complete announcement and roster of members)


36

What do I need to do?Read and study! Ask questions!

For example, there is a ton of literature out there on how the transition to AACR2 was handled. Start with a search in the mid-1970s and continue to the mid-1980s. Just to start you out….

The Making of a Code: Issues Underlying AACR2. Papers given at the International Conference on AACR2 held March 11-14, 1979, Tallahassee, Florida. Edited by Doris Hargrett Clack. Sponsored by the School of Library Science, Florida State University. Chicago: ALA, 1980.

Includes a select bibliography for papers between 1974-1980

A Brief History of AACR2, Joint Steering Committee for Development of RDA…and many more…

http://www.collectionscanada.ca/jsc/history.html


37

Too much change?!

“In cataloging, all changes cost money. The larger the catalog in which the changes are introduced, the more they cost. That is why there is always a powerful conservative lobby among administrators of the largest and richest libraries when the revision of cataloging rules is under consideration.”

Lewis, P.R. (1980). “The Politics of Catalog Code Revision and Future Considerations.” In The Making of a Code: the Issues Underlying AACR2. held March 11-14, 1979, Tallahassee, Florida. Edited by Doris Hargrett Clack. Sponsored by the School of Library Science, Florida State University. Chicago: ALA


38

Consider this past observation…“…failure to keep cataloging practice in line with changes in the characteristics in the documents in our libraries, and with the expectation and needs of document users in those libraries, leads to increasing inefficiencies; and so long-term costs of avoiding catalog changes may be as high as those of accepting them, although this is not easy to demonstrate in library budgets. Either way, the longer the changes are deferred, the more they cost...the proper method is to carry out revisions promptly.”

Lewis. P.R. (1980)


39

About this presentation:

These slides were used as talking points only and do not represent the whole of the content of the workshop.This April 2008 presentation was based on an earlier lecture, entitled “Are You Ready? given at UNT SLIS on November 16, 2007.

http://courses.unt.edu/smiksa/documents/Miksa_RDA_SLIS_16Nov2007.pdf

Slides were modified on April 20 to include pictures and additional comments and resources




Resource Description & Access (RDA) Resources Joint Steering Committee for the Development of RDA website - http://www.collectionscanada.gc.ca/jsc/ RDA-L Discussion list - http://www.collectionscanada.gc.ca/jsc/rdadiscuss.html RDA Cataloger Scenarios - http://www.dublincore.org/dcmirdataskgroup/Scenarios Coyle, Karen & Diane Hillmann (Jan./Feb. 2007) Resource Description & Access (RDA) : Cataloging Rules for the 20th century. D-Lib Magazine 13(1/2) - http://www.dlib.org/dlib/january07/coyle/01coyle.html Oliver, Chris (2007) Changing to RDA. Feliciter 53(5) - http://www.collectionscanada.gc.ca/jsc/rdadiscuss.html Howarth, Lynne C. & Jean Weihs (2007) Making the link : AACR to RDA : Part 1 : Setting the stage. Cataloging & Classification Quarterly 45(2), p. 3-18.

TLA Annual Conference April 15, 2008 1

http://www.collectionscanada.gc.ca/jsc/

http://www.collectionscanada.gc.ca/jsc/rdadiscuss.html

http://www.dublincore.org/dcmirdataskgroup/Scenarios

http://www.dlib.org/dlib/january07/coyle/01coyle.html

http://www.collectionscanada.gc.ca/jsc/rdadiscuss.html


Functional Requirements for Bibliographic Records (FRBR) Resources FRBR Final Report & Amendments - http://www.ifla.org/VII/s13/frbr/ FRBR Blog - http://www.frbr.org/ FRBR Discussion List - http://www.ifla.org/VII/s13/wgfrbr/listserv.htm Carlyle, Allyson (October 2006) Understanding FRBR as a conceptual model: FRBR and the bibliographic universe. Library Resources & Technical Services 50(4), p. 264-273. (An abridgement of this article can be found here: http://www.asis.org/Bulletin/Aug-07/Carlyle_Fusco.pdf) Le Boeuf, Patrick, ed. (2005) Functional Requirements for Bibliographic Records (FRBR): Hype, or Cure-All? Binghamton, NY: Haworth Press, p. 15-37. Published simultaneously as Cataloging & Classification Quarterly, v. 39, no. 3/4 (2005). Maxwell, Robert (2008) FRBR : A guide for the perplexed. American Library Associaion. ISBN 0-8389-0950-7 Miksa, Shawne (Aug./Sept. 2007) Understanding support of FRBR’s four user tasks in MARC-encoded bibliographic records. of the American Society for Information Science and Technology 33(6), p. 24-26 - http://www.asis.org/Bulletin/Aug-07/Miksa.pdf Riva, Pat (Aug./Sept. 2007) Introducing the Functional Requirements for Bibliographic Records and Related IFLA Developments. Bulletin of the American Society for Information Science and Technology 33(6), p. 7-11 - http://www.asis.org/Bulletin/Aug-07/Riva.pdf Shadle, Steve (2006) FRBR and Serials: An Overview and Analysis. Serials Librarian 50(1/2), p. 83-103. Taylor, Arlene, ed. (2007) Understanding FRBR: What It Is and How It Will Affect Our Retrieval Tools. Libraries Unlimited. ISBN 1-5915-8509-0 Tillett, Barbara (2003) What is FRBR? A Conceptual Model for the Bibliographic Universe. Washington: Library of Congress, Cataloging Distribution Service - http://www.loc.gov/catdir/cpso/whatfrbr.html

TLA Annual Conference April 15, 2008 2

http://www.ifla.org/VII/s13/frbr/


http://www.ifla.org/VII/s13/wgfrbr/listserv.htm

http://www.asis.org/Bulletin/Aug-07/Carlyle_Fusco.pdf

http://www.asis.org/Bulletin/Aug-07/Carlyle_Fusco.pdf

http://www.asis.org/Bulletin/Aug-07/Miksa.pdf

http://www.asis.org/Bulletin/Aug-07/Riva.pdf

http://www.loc.gov/catdir/cpso/whatfrbr.html

Entity-Relationship chart (borrowed from http://www.frbr.org/files/entity-relationships.png, at the FRBR Blog at http://www.frbr.org/ )

http://www.frbr.org/files/entity-relationships.png


Johann Sebastian Bach

Partita No.1 in B minor

Person

WorkImagined

a

a

Original ArrangementExpression a

expressed in

wrote

Some Sheet Music

Manifestation

a

manifest in

pieces of paper on a shelf

Item

a

in

Jeffry Hamilton Steele

a

wrote

Arrangement for Classical Guitar

expressed in

wouldneverhave

approvedof

F. Tárrega

a

some other arrangement

wrote

is based on

a

Classical Guitar Arrangements of Bach

manifest in

a

A book on a shelf

in

a

expressed in

a

a live performance on a date in a place

John Holloway

a

manifest in

a

Bach: The Sonatas and Partitas for Violin Solo /

Holloway

a

manifest in

recorded at

performed

AACR2 (CHIEFLY PART II) RDA (CHIEFLYSECTIONS 2-10) COMPARED

1

AACR2 RDA

Pt 1 DESCRIPTION S 1 DESCRIBING MANIFESTATIONS & ITEMS ch. 1 General rules applicable to all kinds of IOsch 2-12

Additional special rules applicable to particular kinds of IOs

ch. 13

Analytical descriptions

c. 1-4 Same kinds of rules as AACR2, chs. 1-13, & in approx. the same order (ISBD) but integrates notes with each kind of descriptive data about which notes are made.

Pt. 2

HEADINGS, UNIFORM TITLES & REFERENCES

S2-S10 IDENTIFYING WORKS, EXPRESSIONS, MANIFESTATIONS & ITEMS IN TERMS OF THEIR ATTRIBUTES, DETERMINING APs FOR THEM, & RECORDING RELATIONSHIPS AMONG THEM

ch 20 General rules and definitions—Assumes idea of a work, though the idea is not integrated w\ Pt I & functions in the background of Part II

S 2 ch 5-7

Identifying Works & Expressions by means of their attributes (i.e., titles, sometimes preceded by names)—Essentially focuses on establishing the ideas of work and expression. See also S5 below.

ch. 21

Choice of Access Pts, in terms of MAP & AAPs

.1-.3 General rules & definitions .4-.7 Main rules for determining Main

APs (& some APs See chapter 19 below

.8-.27 MAP (& some AAPs) for works of mixed responsibility

See chapter 20 below

.28 MAP for related works See chapters 19 & 20 below? or chapters .29-

.30 AAPs—summary & specific rules See chapters 19 & 20 below

.31-.39

MAPs (& some AAPs) for special legal & religious works

See chapter 19 below

S 3 Recording Attributes of Persons, Families & Corporate Bodies—i.e., HOW TO FORMULATE THEM

ch 8 General rules ch. 22

How to formulate personal name APs ch 9 Persons

ch 10 Families ch 23 How to formulate geographical name APs (See below, ch 16) ch. 24

How to formulate corporate body name APs

ch 11 Corporate bodies

NOT IN AACR2 except for formulating names of places

S4* Recording Attributes of Concept, Object, Event, & Place—i.e., HOW TO FORMULATE THEM.

Not in AACR2 ch 12* General Not in AACR2 ch 13* Identifying Concepts Not in AACR2 ch 14* Identifying Objects Not in AACR2 ch 15* Identifying Events See ch. 23 above ch 16 Identifying Places S5 Recording Primary Relationships between [among]

Work, Expression, Manifestation, & Item [Accomplished chiefly by use of Identifiers, Names (titles+names) & full descriptions] See Section 2 above for Identifying

ch 17 General guidelines S6 Recording Relationships to Persons, Families, and

Corporate Bodies Associated with a Resource—i.e, CREATING APs.

ch 18 General Guidelines See ch. 21 above ch 19 Persons, Families, & Corp. Bodies

associated w\ a work—creating APs for original creators, originating CBs, attributed Persons, Families, & Corp. Bodies, and other. [REQUIRED]

AACR2 (CHIEFLY PART II) RDA (CHIEFLYSECTIONS 2-10) COMPARED

2

See ch 21 above ch 20 Persons, Families, Corp. Bodies associated w\ an Expression—creating APs for Contributors = editors, compilers, commentator writers, composers of added accompaniments, illustrators, translators, music arrangers, transcribers, &c, performers, other)—[OPTIONAL]

See ch 21 above ch 21 Persons, Families, Corp. Bodies associated w\ a Manifestation—creating APs for Producers, Publishers, Distributors [OPTIONAL]

See ch 21 above ch 22 Persons, Families, & Corp. Bodies associated w\ an Item—creating APs for Owners, Custodians, Finders [OPTIONAL]

ch 25 How to formulate uniform titles See chs 5-7 above ch 26 How to formulate cross-references ??????? S7 Recording Subject Relationships ch 23* General guidelines on recording the subject

of a work See above 21.28 plus occasional notes S8 Recording Relationships between Works,

Expressions, Manifestations, and Items—Greatly expands AACR2 21.28 plus many notes that speak of relationships

ch 24 General guidelines ch 25 Related works ch.26 Related expressions ch.27 Related manifestations ch 28 Related items Mostly not in AACR2 except in occasional

notes S9 Recording Relationships between Persons, Families,

and Corporate Bodies—Not in AACR2 except in occasional notes

ch 29 General guidelines ch. 30 Related persons ch. 31 Related families ch. 32 Related corporate bodies NOT IN AACR2 S10* Recording Relationships between Concepts, Objects,

Events, and Places—Not in AACR2 except in occasional notes.

ch 33* General Guidelines ch 34* Related concepts ch 35* Related objects ch 36* Related events ch 37* Related places IO = Information Object * sections not yet completed AP = Access Point MAP = Main Access Point AAP = Additional Access Point

What Type of Description does the record represent?

New Description required?

1.3

1.4Mandatory Elements

1.2

As a whole?

ComprehensiveLevel1.2.1

Part of whole? Whole and its parts?

Yes

No No

AnalyticalLevel1.2.2

MultilevelLevel1.2.3

Yes

Decision on Level of Description affects

consequent rule choices

Go to

Yes

Serials

2.3.1.11b

D.1.4

Yes

Title

responsibility

=

Title 2.3 rules

Edition Statement 2.5 rules

Date of publication 2.7, 2.8, 2.9

rules

Resource Identifier2.13 rules

Statement of Responsibility

2.4 rules

Earlier/LaterVariations in

Titles 2.3.5 rules

Numbering 2.6 rules(serials)

Publisher, distribution, etc.

2.7, 2.8, 2.9 rules

Title proper of series

2.10, 2.3 rules

Numbering within series 2.10.6 rules

Form of CarrierChapter 3

ExtentRule 3.4

Scale of cartographic

contentrule 4.16

Coordinates of cartographic

content rule 4.18

Minimal Description of the information resource should include the following

elements

Additional elements added as needed

Information Resource

Any Resource

+

2.1 rules—basis for identification, source of

information, etc

S.Miksa, work-in-progress, April 2008

Preliminary decision

RDA/MARC Working Group Established

Under the auspices of the British Library, the Library and Archives Canada, and the Library of Congress, an RDA/MARC Working Group has been established to collaborate on the development of proposals for changes to the MARC 21 formats to accommodate the encoding of RDA data. With the implementation of RDA anticipated for late 2009, the Working Group will be drafting proposals for review and discussion by the MARC community in June 2008.

Although the MARC 21 formats support the encoding of descriptions created according to a wide range of content standards, the close relationship between AACR and MARC 21 has contributed to the efficient exchange of information among libraries for decades. The RDA/MARC Working Group will identify what changes are required to MARC 21 to support compatibility with RDA and ensure effective data exchange into the future.

RDA/MARC Working Group Roster (3/27-1/08)

Everett Allgood, ALA ALCTS CCS CC:DA New York University Libraries Bobst Library - B-Level70 Washington Square South New York, NY 10012 work: (212) 998-2488 fax: (212) 995-4366 E-mail: [email protected] Corine Deliot, BL Operations & Services The British Library Boston Spa WetherbyWest Yorkshire LS23 7BQ United Kingdom work: +44 (0)1937 54666 fax: +44 (0)1937 546979 E-mail: [email protected] John Espley, VTLS VTLS, Inc. 1701 Kraft Drive Blacksburg, VA 24060-6351 work: (800) 468-8857 fax: (540) 557-1210 E-mail: [email protected] Richard O. Greene, OCLC OCLC, Inc. 6565 Kilgour Place Dublin, OH 43017-3395 work: (800) 848-5878, ext. 6154 fax: (614) 718-7275 E-mail: [email protected]

Rebecca S. Guenther, LC Library of Congress Network Development and MARC Standards Office Washington, DC 20540-4402 work: (202) 707-5092 fax: (202) 707-0115 E-mail: [email protected] Bill Leonard, LAC Library and Archives Canada Standards 395 Wellington Street Ottawa, Ontario K1A 0N4 CANADA work: (819) 994-6936 fax: (819) 934-4388 E-mail: [email protected] Sally H. McCallum, LC Library of Congress Network Development and MARC Standards Office Washington, DC 20540-4402 work: (202) 707-5119 fax: (202) 707-0115 E-mail: [email protected] Bill Moen, UNT University of North Texas School of Library and Information Sciences ISB Building, Rm. 205 205 Chestnut St. P.O. Box 311068 Denton, Texas 76203-1068 work: ( 940)565-3563 fax: (940) 565-3101 Email: [email protected]

Margaret Stewart, LAC Library and Archives Canada Standards 395 Wellington Street Ottawa, Ontario K1A 0N4 CANADA work: (819) 994-6900 fax: (819) 953-0291 E-mail: [email protected] Martha Yee, UCLA UCLA Film & Television Archive 1015 N. Cahuenga Blvd. Los Angeles, Calif. 90038 work: 323-462-4921 x27 fax 323-469-9055 E-mail: [email protected]