ALATechSource, profile picture
Uploaded byALATechSource
PPTX, PDF9,536 views

Introducing RDA

RDA is a new metadata standard that replaces AACR2. RDA is built on FRBR and FRAD conceptual models which analyze bibliographic data in terms of entities, attributes, and relationships. RDA focuses on the user and aims to provide data that helps users find, identify, select, and obtain resources. Key differences from AACR2 include taking data as it appears, recording relationships explicitly, and avoiding abbreviations to make data easier for users to understand.

Embed presentation

Downloaded 187 times
1 Introducing RDA October 17th, 2012 Chris Oliver McGill University chris.oliver@mcgill.ca
2 What is RDA? RDA = Resource Description and Access • new metadata standard replaces AACR2 • set of practical instructions built on the foundation of a theoretical framework/data model • record better metadata to support better resource discovery • designed for the web environment
3 Plan 1. moving towards RDA and its implementation 2. key concepts in RDA • theoretical framework • objectives and principles • focus on the user • content standard • bibliographic information as data • internationalization and their visible impact on RDA
4 1. Moving towards RDA
5 AACR2  successful standard  adopted by many countries  in use for many years but problems with AACR2 for example: • written for card catalogues • inadequate rules to describe new types of resources • inconsistencies • library specific
6 Roots of RDA 1997 problems identified: International Conference on the Principles & Future Development of AACR, Toronto, Ontario 1998-2004 revisions to AACR2; revise within the existing structure 2004 AACR3 2005 decision to develop a new standard: Resource Description and Access 2005-2009 development of content for the new standard
7 Moving towards RDA 2009 text of RDA completed software designed ... but >>> still a set of static documents that need to be transformed into a web tool 2010 first release of the RDA Toolkit (RDA plus) 2010 US testing (US RDA Test Coordinating Committee) 2011 US national libraries and the Program for Cooperative Cataloging: intention to implement if certain conditions are met implementation not before 2013
8 Moving towards RDA 2011 some of the libraries who tested RDA decide to continue producing RDA records 2011-2012 preparations for implementation - work on recommendations - community involvement 2012 announcement from the Library of Congress: target date for implementation: March 31, 2013 Long-Range RDA Training Plan http://www.loc.gov/aba/rda/pdf/RDA_Long-Range_Training_Plan.pdf
9 Moving towards RDA 2012 other national libraries are also planning to target the 1st quarter of 2013 as their RDA implementation date: National Agricultural Library National Library of Medicine British Library Library and Archives Canada National Library of Australia Deutsche Nationalbibliothek (mid 2013)
10 Is there a day 1? Yes and No 1) day 1 is important for a sharing data environment: PCC: declares day 1 for contributing to NACO authorities LC: declares day 1 for its own cataloguing operations 2) some institutions never switched back after the test 3) each institution decides on day 1 for bibliographic data
11 March 31, 2013 • all new authority records contributed to LC/NACO authority file = RDA • all records coded pcc = all RDA access points all records coded pcc whether: • RDA description or • AACR2 description • LC will have completed training all its cataloging staff and all LC records will be RDA records
12 by March 31, 2013 • rapid rise in number of RDA bibliographic records • changes in LC/NACO authority file • distinction between RDA acceptable and not acceptable • global changes in individual databases implications for authority work implications for copy cataloging
13 Implementation arriving quickly ...
14 Phase 1 of implementation emphasis on continuity RDA data in MARC 21 in current catalogues still creating bibliographic and authority records some new fields some changed instructions some new instructions BUT >>> thinking about bibliographic information differently
15 Phase 1 = starting down new track RDA • continuity and change • moves us to a new track • starts us on a promising track for the future use of our metadata • useful to understand some of the key RDA concepts and see the long view
16 2. Key concepts in RDA
17 AACR2 RDA • continue to record the title • continue to record the statement of responsibility • continue to record the date of publication But … • new vocabulary • new way of thinking about how we do these steps
18 Similar, but ... AACR2 1.2B1. Transcribe the edition statement as found on the item. Use abbreviations as instructed in appendix B and numerals as instructed in appendix C. RDA 2.5.1.4. Transcribe an edition statement as it appears on the source of information. No instruction to abbreviate or to convert to arabic numerals.
19 Similar, but ... • serious adherence to the principle of representation “take what you see” t.p. data recorded 3rd ed. 3rd ed. Second edition Second edition
20 On the surface … similar instructions but different framework new vocabulary but also new concepts
21 2. Key concepts in RDA Theoretical framework
22 RDA’s theoretical framework • explicit conceptual framework • aligned with the FRBR and FRAD conceptual models FRBR Functional Requirements for Bibliographic Records 1998 FRAD Functional Requirements for Authority Data 2009 FRAD is an extension of the FRBR model • both models developed under the auspices of IFLA • broad base of international consensus and support
23 The two models • widely used data modeling technique: entity relationship model • entities • attributes • relationships • analyze bibliographic and authority data from the point of view of how that data is used
24 RDA vocabulary from FRBR + FRAD • user tasks • meaning and scope of the 11 bibliographic entities work person concept expression family object manifestation corporate body event item place • entities – attributes – relationships
25 Organization and Structure of RDA RDA table of contents reflects alignment with FRBR Section 1-4 = Recording attributes Section 1. Recording attributes of manifestation and item Section 2. Recording attributes of work and expression Section 3. Recording attributes of person, family, and corporate body Section 4. Recording attributes of concept, object, event, and place [placeholder]
26 Organization and Structure of RDA Sections 5-10 = Recording Relationships Section 5. Recording primary relationships between work, expression, manifestation, and item Section 6. Recording relationships to persons, families, and corporate bodies associated with a resource Section 7. Recording subject relationships [placeholder] Section 8. Recording relationships between works, expressions, manifestations, and items Section 9. Recording relationships between persons, families, and corporate bodies Section 10. Recording relationships between concepts, objects, events, and places [placeholder]
27 User tasks from FRBR + FRAD Bibliographic data Authority data • find • find • identify • identify • select • contextualize (clarify) • obtain • justify (understand)
28 Attributes • how to record the attributes of entities (characteristics) for example, entity = a manifestation attributes we record: title proper statement of responsibility edition statement place of publication etc.
29 Relationships: links between entities work created by person item owned by family manifestation produced by corporate body work based on work manifestation electronic reprod. manifestation person member of family family founded corporate body
30 Relationships in RDA 1. record relationship 2. specify exact nature of the relationship for example AACR2 name of a person ------- title of book • type of relationship may be embedded in text of description • bibliographic record contains name of person and title RDA name of a person --- type of relationship --- work • make the relationship explicit and clear • relationship designators = controlled vocabulary
31 Relationship designators • specify roles for example cartographer performer broadcaster former owner issuing body • specify the nature of the relationship for example adaptation of paraphrased as electronic reproduction of
32 Relationships in RDA examples with MARC 21 coding: 245 10 $a British Atlantic, American frontier : $b spaces of power in early modern British America / $c Stephen J. Hornsby ; with cartography by Michael J. Hermann. 700 1# $a Herman, Michael J., $e cartographer 245 00 $a Alice in Wonderland, or, What's a nice kid like you doing in a place like this? /$c Hanna-Barbera Productions. 700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland. authority record 500 3# $w r $i Descendant family: $a Adams (Family)
33 Theoretical framework • alignment with the FRBR and FRAD conceptual models • bibliographic and authority data >>> in terms of entities, attributes + relationships • identify what is important --- how is data used • systematic and coherent framework >>> conceptual clarity >>> logical consistency >>> reference point for further development
34 Underlying data model >>> practical set of cataloguing instructions ● built on a theoretical framework ● built on a robust data model • widely used data modeling technique • understood by other metadata and data modeling communities e.g. software engineers, information systems and database designers
35 2. Key concepts in RDA Objectives and principles
36 RDA Objectives & Principles • important part of RDA • shaped many of the instructions that are different from AACR2 • concur with the International Cataloguing Principles (ICP)
37 RDA Objectives & Principles Objectives RDA 0.4.2 Principles RDA 0.4.3 • responsiveness to user • differentiation needs • sufficiency • cost efficiency • relationships • flexibility • representation • continuity • accuracy • attribution • common usage or practice • uniformity
38 Principle of representation for example RDA 0.4.3.4 principle = representation The data describing a resource should reflect the resource’s representation of itself. result = simplify transcription “Take what you see”
39 RDA = Take what you see source = Kemptville, Ontario AACR2 = Kemptville, Ont. RDA = Kemptville, Ontario 264 1 $a Kemptville, Ontario ____________________________________________________________________________________________________________________ source = Band LXXXVIII (series numbering) AACR2 = Bd. 88 RDA = Band LXXXVIII 490 $a ... ; $v Band LXXXVIII
40 RDA = Take what you see source = Third revised edition AACR2 = 3rd rev. ed. RDA = Third revised edition _____________________________________________ source = 2nd enlarged ed., revised AACR2 = 2nd enl. ed., rev. RDA = 2nd enlarged ed., revised
41 Different instructions AACR2 1.0F. Inaccuracies In an area where transcription from the item is required, transcribe an inaccuracy or a misspelled word as it appears in the item. Follow such an inaccuracy either by [sic] or by i.e. and the correction within square brackets. Supply a missing letter or letters in square brackets. RDA 1.7.9 Inaccuracies When instructed to transcribe an element as it appears on the source of information, transcribe an inaccuracy or a misspelled word as it appears on the source, except where instructed otherwise.
42 Inaccuracy in RDA 1.7.9 continued Make a note correcting the inaccuracy if it is considered to be important for identification or access (see 2.20 ). If the inaccuracy appears in a title, record a corrected form of the title as a variant title (see 2.3.6 ) if it is considered to be important for identification or access. Exception: 2.3.1.4 Inaccuracies. When transcribing the title proper of a serial or integrating resource, correct obvious typographic errors, and make a note giving the title as it appears on the source of information (see 2.20.2.4 ) ...
43 RDA = Take what you see title page = Melallization of polymers AACR2 = Melallization [sic] of polymers or Melallization [i.e. Metallization] of polymers RDA = Melallization of polymers 245 14 $a Melallization of polymers 246 1 $i Corrected title: $a Metallization of polymers
44 2. Key concepts in RDA Focus on the user
45 RDA Objectives & Principles Objectives RDA 0.4.2 Principles RDA 0.4.3 • responsiveness to user • differentiation needs • sufficiency • cost efficiency • relationships • flexibility • representation • continuity • accuracy • attribution • common usage or practice • uniformity
46 Focus on the user • record data that is important to the user why is it important? helps the user to find identify select obtain
47 Resource discovery = user tasks Bibliographic data Authority data • find • find • identify • identify • select • clarify • obtain • understand Why record the data? To help user achieve these tasks.
48 Consistent focus on the user • RDA divided into 10 sections • each section begins with general guidelines • functional objectives and principles specific to the section Functional objectives = relationship between data and user tasks the data (recorded or formulated according to the instructions in that section) the user tasks
49 Example from Section 1 Section 1= Recording attributes of manifestations & items 1.2 Functional Objectives and Principles The data describing a manifestation or item should enable the user to: a) find manifestations and items that correspond to the user’s stated search criteria b) identify the resource described … c) select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and encoding of information stored on the carrier d) obtain a resource …
50 Basis for Cataloguer Judgment • instructions encourage cataloguer judgment --- based on relationship to user tasks for example, from 3.7 Applied material Record the applied material used in the resource if it is considered important for identification or selection …
51 Easier for user to identify • no abbreviations 300 $a 398 pages :$b illustrations ; $c 25 cm AACR2: 300 $a 398 p. :$b ill. ; $c 25 cm. • no square brackets 300 $a 48 unnumbered pages, 256 pages AACR2: 300 $a [48], 256 p. • replace Latin abbreviations 300 $a 48, that is, 96 pages AACR2: 300 $a 48 [i.e. 96] p. • avoid cryptic information 300 $a xiv, 179 pages (incomplete) AACR2: 300 $a xiv, 179 + p.
52 Easier for user to find, identify RDA: no more: rule of three no more … [et al.] in description if statement of responsibility names more than one person >>> record all RDA 2.4.1.5 optional omission: record first named and summarize the omission [and six others] access points for first named or principal core or all or cataloger judgment or institutional policy
53 Easier for user to find, identify RDA: record all authors; access points for all authors; define relationships with designators 100 1 $a Berry, John W., $e author. 245 10 $a Cross-cultural psychology : $b research and applications / $c John W. Berry, Ype H. Poortinga, Seger M. Breugelmans, Athanasios Chasiotis, David L. Sam. 250 $a Third edition. 260 $a Cambridge : $b Cambridge University Press, $c 2011. 300 $a xxii, 626 pages ; $c 25 cm 700 1 $a Poortinga, Ype H., $d 1939- $e author. 700 1 $a Breugelmans, Seger M., $e author. 700 1 $a Chasiotis, Athanasios, $e author. 700 1 $a Sam, David L., $e author.
54 Easier for user to understand RDA optional omission (2.4.1.5): more than three, omit and summarize core relationship = access point for first-named 100 1 $a Berry, John W. 245 10 $a Cross-cultural psychology : $b research and applications / $c John W. Berry [and four others]. 250 $a Third edition. 260 $a Cambridge : $b Cambridge University Press, $c 2011. 300 $a xxii, 626 pages ; $c 25 cm
55 Easier for user to find AACR2 Aesop’s fables. Polyglot. RDA Aesop’s fables. Greek Aesop’s fables. Latin Aesop’s fables. English Aesop’s fables. German AACR2 Aesop’s fables. English & German RDA Aesop’s fables. English Aesop’s fables. German
56 2. Key concepts in RDA Content standard
57 RDA as a content standard AACR2: MARC encoding + ISBD display RDA = what data should the cataloguer record? • possible to encode using many encoding systems • can be encoded using MARC • does not have to be encoded using MARC encoding • can be used with web friendly XML based encoding schema, such as Dublin Core, MODS • possible to display the data in many ways
58 RDA as a content standard not an encoding standard not a display standard • for example, take the data and create displays that suit your user group: RDA says: record person’s date of death= 2003 Display? died 2003 d. 2003 - 2003 date of death: 2003
59 Possible display Issuing body: Whitney Museum of American Art 710 2# $a Whitney Museum of American Art, $e issuing body. Photographer: Burger, Hillel 700 1# $a Burger, Hillel, $e photographer. Author: Gaines, Isabel 100 1# $a Gaines, Isabel, $e author. Alice in Wonderland, or, What's a nice kid like you doing in a place like this? / Hanna-Barbera Productions. Parody of: Carroll, Lewis, 1832-1898. Alice's adventures in Wonderland. 700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland
60 Identifying the entity either eye-readable data: name date of birth and death Shields, Carol, 1953-2003 and/or machine actionable data: identifier 0101A6635 http://viaf.org/viaf/4944537/#Shields,_Carol
61 RDA as a content standard • not locked into library encoding practices • not locked into library display practices • get out of the library silo >>> data visible on the web >>> data interacting with the data of other metadata communities
62 2. Key concepts in RDA Bibliographic information as data
63 Data Elements element = A word, character, or group of words and/or characters representing a distinct unit of bibliographic information. appears similar to AACR2 definition minus “forming part of an area” effect is quite different from AACR2 each element is ≈ discrete ≈ precisely defined ≈ single attribute / single relationship
64 AACR2 for example AACR2: information embedded in non-specific places notes digital file characteristics physical description file type MARC 538 encoding format 516 file size 500 resolution 300 regional encoding transmission speed
65 RDA RDA: precise elements and element sub-types digital file characteristics RDA 3.19 file type encoding format file size resolution regional encoding transmission speed
66 347 Digital File Characteristics new MARC field 347 subfield codes $a - File type (R) $b - Encoding format (R) $c - File size (R) $d - Resolution (R) $e - Regional encoding (R) $f - Transmission speed (R)
67 AACR2 Information AACR2: ambiguity --- assume human will decipher AACR2: date of publication, distribution, etc. date of copyright date of manufacture MARC 21: 260 $c 260 $g
68 RDA Data Elements RDA: precise elements – only one kind of data in an element RDA: 5 different elements: RDA 2.7-2.11 date of production date of publication date of distribution date of manufacture date of copyright MARC 21: 264 $c 5 different indicators
69 Controlled vocabulary • controlled vocabulary recommended for many elements encoding format DAISY, MP3, Access, XML, JPEG, TIFF, CAD, PDF, Blu-ray, VCD production method blueline, blueprint, engraving, etching, lithograph, photocopy, photoengraving, woodcut base material Bristol board, canvas, cardboard, ceramic, glass, leather, paper, parchment, vellum
70 RDA data = precise + usable data RDA • each element is distinct and precisely defined • each element contains only one kind of data • controlled vocabulary in many elements  each element has the potential to be usable: to index to search to build meaningful displays of data  data in any element can be used: by humans by computers
71 Many new elements many new elements but do not have to use them all core elements • not a level of description • core elements are a minimum “a floor, not a ceiling” • must include any additional elements required to differentiate the resource or entity from a similar one • inclusion of other elements --- cataloguer judgment
72 2. Key concepts in RDA Internationalization
73 Beyond “Anglo-American” RDA 0.11.1: RDA is designed for use in an international context. options for use of • other languages • other scripts • other calendars • other numeric systems • other units of measurement
74 RDA • when not transcribing: some instructions say – ... record in the language preferred by the agency creating the data ... record in the preferred script of the agency creating the data 6.4.1.3 Recording Date of Work Record the date of the work in terms of the calendar preferred by the agency creating the data.
75 RDA April 2012 update • change at 6.2.1.7 for the international cataloguing community (proposed by the German National Library and approved by all constituencies) Basic instructions on recording titles of works RDA 6.2.1.7 Initial articles When recording the title, include an initial article, if present. Alternative Omit an initial article … original text at RDA 6.2.1.7 was: Omit an initial article …
76 FRBR + FRAD as point of reference broad international support for the explanatory power of the models common international language and conceptual understanding of the bibliographic universe as the foundation for a standard: • easier to apply in international context • easier for our data to interoperate with other data generated on the basis of a FRBR/FRAD understanding of the bibliographic universe
77 On the international scene 2005-2009 comments on RDA drafts: from libraries beyond Australia, Canada, Great Britain and the United States 2011 formal launch of European RDA Interest (began in 2009) Group (EURIG) members from: Austria, Croatia, Denmark, Finland, France, Germany, Great Britain, Italy, Latvia, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, the Vatican >>> interest of countries who use AACR2 >>> interest of countries that have never used AACR
78 On the international scene Translation projects: German Germany, Austria French Canada, France, Belgium Spanish licensing for: Argentina, Bolivia, Chile, Colombia, Costa Rica, Dominican Republic, Ecuador, El Salvador, Equatorial Guinea, Guatemala, Honduras, Mexico, Nicaragua, Panama, Paraguay, Peru, Spain, Uruguay, Venezuela Chinese (Mandarin) and expressions of interest from others
79 Key concepts Key concepts shape RDA: • theoretical framework • objectives and principles • focus on the user • content standard • bibliographic information as data • internationalization >>> visible impact on RDA and the content of instructions >>> many changes in RDA trace back to concepts
80 Familiarity with key RDA concepts • a useful way to grab hold of RDA • a useful way to approach RDA implementation
81 Flickr credits: creative commons attribution Tour de Toona by Team Traveller http://www.flickr.com/photos/teamtraveller/5928422950/ Cross track – iPhone wall paper by CJ Schmit http://www.flickr.com/photos/cjschmit/4623783487/ The roof continues by Martin Pettitt http://www.flickr.com/photos/mdpettitt/2521374167/ Oregon silo by TooFarNorth http://www.flickr.com/photos/toofarnorth/4597980984/ Rock climbing is fun by mariachily http://www.flickr.com/photos/mariachily/3382799213/
82 Questions … ? chris.oliver@mcgill.ca

More Related Content

PPT
Subject cataloguing
bySarika Sawant
 
PPTX
Intro to rda
byAnna Enos
 
PPT
Fundamentals of RDA: Resource Description & Access
byGLA: Technical Services Interest Group (TSIG)
 
PPT
RDA (Resource Description & Access)
byJennifer Joyner
 
PPT
Descriptive cataloging: Overview
byJohan Koren
 
PPT
Cataloging basics
byrobin fay
 
PDF
Functional Requirements For Bibliographic Records - FRBR
byIslamic University of Lebanon
 
PPT
AACR2 8 Areas of Bibliographic Description
byIme Amor Mortel
 
Subject cataloguing
bySarika Sawant
 
Intro to rda
byAnna Enos
 
Fundamentals of RDA: Resource Description & Access
byGLA: Technical Services Interest Group (TSIG)
 
RDA (Resource Description & Access)
byJennifer Joyner
 
Descriptive cataloging: Overview
byJohan Koren
 
Cataloging basics
byrobin fay
 
Functional Requirements For Bibliographic Records - FRBR
byIslamic University of Lebanon
 
AACR2 8 Areas of Bibliographic Description
byIme Amor Mortel
 

What's hot

PPT
Marc format
byIme Amor Mortel
 
PPTX
Customer service in the library
bySeti Keshmiripour
 
PPT
FRBR model by Gaurav Boudh
byLibrary and Information Science Blog
 
PPTX
RDA Presentation
byjendibbern
 
PPTX
What is a school library media center
byJohan Koren
 
PPTX
International Standard Bibliographic Description: background and recent devel...
byScottish Library & Information Council (SLIC), CILIP in Scotland (CILIPS)
 
PPT
Descriptive cataloging areas of description
byIme Amor Mortel
 
ODP
DDC Number Building for shelf arrangement
bySreeja Ramachandran
 
PPT
Interoperability Protocols and Standards in LIS
byADINET Ahmedabad
 
PPT
Lirary Classification-Need and Purpose.ppt
byDr. Anjaiah Mothukuri
 
PDF
Resource description and Access
byUDAYA VARADARAJAN
 
PPTX
Ppt.marketing of library and information services
bypardeeprattan
 
PPTX
Collection development
byAli Hassan Maken
 
PPTX
RDA: Resource Description and Access
byRieta Drinkwine
 
PPT
Catalog entries of nonbook materials
byIme Amor Mortel
 
PPTX
MARC -21.pptx
byRbalasubramani
 
PPTX
ISBD
byHarsimran Singh Bhatia
 
PPTX
Collection Development policies
bySarah Wilkie
 
PPTX
DIGITAL LIBRARY ARCHITECTURE
bysarika meher
 
PDF
History and Development of Special Librarianship
byFrancheska Vonne Gali
 
Marc format
byIme Amor Mortel
 
Customer service in the library
bySeti Keshmiripour
 
FRBR model by Gaurav Boudh
byLibrary and Information Science Blog
 
RDA Presentation
byjendibbern
 
What is a school library media center
byJohan Koren
 
International Standard Bibliographic Description: background and recent devel...
byScottish Library & Information Council (SLIC), CILIP in Scotland (CILIPS)
 
Descriptive cataloging areas of description
byIme Amor Mortel
 
DDC Number Building for shelf arrangement
bySreeja Ramachandran
 
Interoperability Protocols and Standards in LIS
byADINET Ahmedabad
 
Lirary Classification-Need and Purpose.ppt
byDr. Anjaiah Mothukuri
 
Resource description and Access
byUDAYA VARADARAJAN
 
Ppt.marketing of library and information services
bypardeeprattan
 
Collection development
byAli Hassan Maken
 
RDA: Resource Description and Access
byRieta Drinkwine
 
Catalog entries of nonbook materials
byIme Amor Mortel
 
MARC -21.pptx
byRbalasubramani
 
ISBD
byHarsimran Singh Bhatia
 
Collection Development policies
bySarah Wilkie
 
DIGITAL LIBRARY ARCHITECTURE
bysarika meher
 
History and Development of Special Librarianship
byFrancheska Vonne Gali
 

Viewers also liked

PPTX
Open Access and Your Publications: What's Copyright Got to Do with It?
byALATechSource
 
PDF
Resources
byALATechSource
 
PPTX
Supporting Early Literacy through Language Rich Library Environments
byALATechSource
 
PPTX
Libraries, Copyright and the World
byALATechSource
 
PPTX
Supervising Library Shelvers
byALATechSource
 
PPTX
Crews on Copyright: E-Reserves and Fair Use
byALATechSource
 
PPTX
Hiring, Training and Supervising Library Shelvers: Part 2
byALATechSource
 
PPTX
How to Improve Library Instruction: Assessment in Five Minutes
byALATechSource
 
PPSX
RDA como novo código de catalogação
byMarcelo Votto
 
PPTX
Interviewing Library Shelvers
byALATechSource
 
PPTX
Introducing RDA: June 2013
byALATechSource
 
PDF
Resource description and access
byNational Library of Australia
 
PPTX
Cataloging Video Resources with RDA Workshop: Pt. 2
byALATechSource
 
PPTX
Cataloging Video Resources with RDA Workshop: Pt. 1
byALATechSource
 
PPT
Resource Description & Access (RDA)
byBuzz Haughton
 
PDF
Rda
byVilma Souza
 
PDF
RDA
byUNESP
 
PPTX
RDA: Dando um passo à frente
byFabrício Silva Assumpção
 
PPTX
Minicurso Introdução ao FRBR e ao RDA (SNBU 2014, Belo Horizonte)
byFabrício Silva Assumpção
 
PPTX
Mudanças e desafios na utilização do RDA
byFabrício Silva Assumpção
 
Open Access and Your Publications: What's Copyright Got to Do with It?
byALATechSource
 
Resources
byALATechSource
 
Supporting Early Literacy through Language Rich Library Environments
byALATechSource
 
Libraries, Copyright and the World
byALATechSource
 
Supervising Library Shelvers
byALATechSource
 
Crews on Copyright: E-Reserves and Fair Use
byALATechSource
 
Hiring, Training and Supervising Library Shelvers: Part 2
byALATechSource
 
How to Improve Library Instruction: Assessment in Five Minutes
byALATechSource
 
RDA como novo código de catalogação
byMarcelo Votto
 
Interviewing Library Shelvers
byALATechSource
 
Introducing RDA: June 2013
byALATechSource
 
Resource description and access
byNational Library of Australia
 
Cataloging Video Resources with RDA Workshop: Pt. 2
byALATechSource
 
Cataloging Video Resources with RDA Workshop: Pt. 1
byALATechSource
 
Resource Description & Access (RDA)
byBuzz Haughton
 
Rda
byVilma Souza
 
RDA
byUNESP
 
RDA: Dando um passo à frente
byFabrício Silva Assumpção
 
Minicurso Introdução ao FRBR e ao RDA (SNBU 2014, Belo Horizonte)
byFabrício Silva Assumpção
 
Mudanças e desafios na utilização do RDA
byFabrício Silva Assumpção
 

Similar to Introducing RDA

PPTX
Introducing RDA
byALATechSource
 
PPTX
Oliver: Introducing RDA
byALATechSource
 
PDF
Clara RDA Training 1
byClaraLiao
 
PDF
Resource Description
byNational Library of Australia
 
PDF
Karen Coyle Keynote - R&D: Can Resource Description become Rigorous Data?
byeby
 
PPTX
Resource Description and Access at University of Zimbabwe
byPeter Kativhu
 
PDF
Resource Description and Acess
byNational Library of Australia
 
PPTX
NCompass Live: RDA: Are We There Yet?
byNebraska Library Commission
 
PPTX
RDA for Original Catalogers
byShana McDanold
 
PPTX
Library LicExamination Review Class 2016
bySuJunMEjDaEnchu
 
PPTX
RDA: Are We There Yet? Carterette Webinar S
byEmily Nimsakont
 
PPTX
RDA from Scratch for Catalogers
byShana McDanold
 
PPTX
RDA Intro - AACR2 / MARC> RDA / FRBR / Semantic Web
byrobin fay
 
PPTX
RDA and serials: Theoretical and practical applications. Preconference
byNASIG
 
DOC
Rda seminar syllabus
byRichard.Sapon-White
 
PPT
Tools Of Our Trade
byFarrukhshahzad
 
PPT
The tools of our trade: AACR2/RDA and MARC
byAnn Chapman
 
PPT
Tools of our Trade (RDA, MARC21) 2010-03-15
byAnn Chapman
 
PPTX
RDA, FRBR, and FRAD: Connecting the dots
byLouise Spiteri
 
PPTX
Introduction to RDA Part 1
byNebraska Library Commission
 
Introducing RDA
byALATechSource
 
Oliver: Introducing RDA
byALATechSource
 
Clara RDA Training 1
byClaraLiao
 
Resource Description
byNational Library of Australia
 
Karen Coyle Keynote - R&D: Can Resource Description become Rigorous Data?
byeby
 
Resource Description and Access at University of Zimbabwe
byPeter Kativhu
 
Resource Description and Acess
byNational Library of Australia
 
NCompass Live: RDA: Are We There Yet?
byNebraska Library Commission
 
RDA for Original Catalogers
byShana McDanold
 
Library LicExamination Review Class 2016
bySuJunMEjDaEnchu
 
RDA: Are We There Yet? Carterette Webinar S
byEmily Nimsakont
 
RDA from Scratch for Catalogers
byShana McDanold
 
RDA Intro - AACR2 / MARC> RDA / FRBR / Semantic Web
byrobin fay
 
RDA and serials: Theoretical and practical applications. Preconference
byNASIG
 
Rda seminar syllabus
byRichard.Sapon-White
 
Tools Of Our Trade
byFarrukhshahzad
 
The tools of our trade: AACR2/RDA and MARC
byAnn Chapman
 
Tools of our Trade (RDA, MARC21) 2010-03-15
byAnn Chapman
 
RDA, FRBR, and FRAD: Connecting the dots
byLouise Spiteri
 
Introduction to RDA Part 1
byNebraska Library Commission
 

More from ALATechSource

PPT
Liven Up Baby and Toddler Storytimes with Sign Language (March 2019)
byALATechSource
 
PPTX
Dealing with Mental Health on the Front Lines: Part 1
byALATechSource
 
PPT
Serving Children with Autism Spectrum Disorder: Part 2 (Feb. 2019)
byALATechSource
 
PDF
Using Visual Arts in Early Childhood Programming
byALATechSource
 
PPTX
Serving Children with Autism Spectrum Disorder (Feb. 2019)
byALATechSource
 
PPTX
Library Website Rehab: Promotional Webinar
byALATechSource
 
PPTX
Taking STEAM Programs to the Next Level
byALATechSource
 
PPTX
Creating a Digital Media Space for Today's Teens: Part 2 (Jan. 2019)
byALATechSource
 
PPT
Creating a Social Media Policy for Your Library (January 2019)
byALATechSource
 
PPTX
Creating a Digital Media Space for Today's Teens: Part 1 (Jan. 2019)
byALATechSource
 
PPTX
Working with Individuals Affected by Homelessness: An Empathy-Driven Approach...
byALATechSource
 
PPTX
Fake News, Real Concerns: Developing Information-Literate Students (December ...
byALATechSource
 
PPTX
Offering Service and Support to the LGBTQIA Community and Allies (Nov. 2018)
byALATechSource
 
PPTX
Library Director Bootcamp: Getting the Skills You Need, Part 3 (Nov. 2018)
byALATechSource
 
PPTX
Engaging Learners through Active Instruction and Assessment
byALATechSource
 
PPTX
Library Director Bootcamp: Getting the Skills You Need, Part 2 (Nov. 2018)
byALATechSource
 
PPTX
AL Live: What Do the Midterms Mean for Your Library? (November 2018)
byALATechSource
 
PPTX
Library Director Bootcamp: Getting the Skills You Need, Part 1 (Nov. 2018)
byALATechSource
 
PDF
Prepare for the Future: Tech Strategies You Need to Know (November 2018)
byALATechSource
 
PPTX
Write and Cite “Chicago Style”: Helping Students and Patrons Understand The C...
byALATechSource
 
Liven Up Baby and Toddler Storytimes with Sign Language (March 2019)
byALATechSource
 
Dealing with Mental Health on the Front Lines: Part 1
byALATechSource
 
Serving Children with Autism Spectrum Disorder: Part 2 (Feb. 2019)
byALATechSource
 
Using Visual Arts in Early Childhood Programming
byALATechSource
 
Serving Children with Autism Spectrum Disorder (Feb. 2019)
byALATechSource
 
Library Website Rehab: Promotional Webinar
byALATechSource
 
Taking STEAM Programs to the Next Level
byALATechSource
 
Creating a Digital Media Space for Today's Teens: Part 2 (Jan. 2019)
byALATechSource
 
Creating a Social Media Policy for Your Library (January 2019)
byALATechSource
 
Creating a Digital Media Space for Today's Teens: Part 1 (Jan. 2019)
byALATechSource
 
Working with Individuals Affected by Homelessness: An Empathy-Driven Approach...
byALATechSource
 
Fake News, Real Concerns: Developing Information-Literate Students (December ...
byALATechSource
 
Offering Service and Support to the LGBTQIA Community and Allies (Nov. 2018)
byALATechSource
 
Library Director Bootcamp: Getting the Skills You Need, Part 3 (Nov. 2018)
byALATechSource
 
Engaging Learners through Active Instruction and Assessment
byALATechSource
 
Library Director Bootcamp: Getting the Skills You Need, Part 2 (Nov. 2018)
byALATechSource
 
AL Live: What Do the Midterms Mean for Your Library? (November 2018)
byALATechSource
 
Library Director Bootcamp: Getting the Skills You Need, Part 1 (Nov. 2018)
byALATechSource
 
Prepare for the Future: Tech Strategies You Need to Know (November 2018)
byALATechSource
 
Write and Cite “Chicago Style”: Helping Students and Patrons Understand The C...
byALATechSource
 
In this document
Powered by AI

Introduction to Resource Description and Access (RDA) and its significance in modern metadata.

Discussion of the shift from AACR2 to RDA, including historical context and the timeline leading to its implementation.

Overview of RDA authority records and expected changes in bibliographic records by March 31, 2013.

Insights into Phase 1 of RDA implementation, focusing on continuity and changes required in data handling.

Key concepts that differentiate RDA from AACR2, focusing on vocabulary and thought processes in cataloging.

RDA's theoretical framework aligned with FRBR and FRAD models; user tasks and relationships in bibliographic data.

RDA objectives focusing on user needs, highlighting direct impacts on data recording and user tasks.

Defining RDA as a content standard that supports multiple encoding possibilities beyond libraries.

Introduction of precise bibliographic elements in RDA, emphasizing clarity and usability in metadata.

RDA's commitment to internationalization, accommodating diverse languages and practices in the cataloging community.Summary of key concepts informing RDA's structure and implementation, reinforcing the necessity for understanding.

Open floor for questions regarding the RDA presentation, inviting further discussion on its details.

Introducing RDA

  • 1.
    1 Introducing RDA October 17th,2012 Chris Oliver McGill University [email protected]
  • 2.
    2 What is RDA? RDA= Resource Description and Access • new metadata standard replaces AACR2 • set of practical instructions built on the foundation of a theoretical framework/data model • record better metadata to support better resource discovery • designed for the web environment
  • 3.
    3 Plan 1. moving towardsRDA and its implementation 2. key concepts in RDA • theoretical framework • objectives and principles • focus on the user • content standard • bibliographic information as data • internationalization and their visible impact on RDA
  • 4.
  • 5.
    5 AACR2  successful standard  adopted by many countries  in use for many years but problems with AACR2 for example: • written for card catalogues • inadequate rules to describe new types of resources • inconsistencies • library specific
  • 6.
    6 Roots of RDA 1997 problems identified: International Conference on the Principles & Future Development of AACR, Toronto, Ontario 1998-2004 revisions to AACR2; revise within the existing structure 2004 AACR3 2005 decision to develop a new standard: Resource Description and Access 2005-2009 development of content for the new standard
  • 7.
    7 Moving towards RDA 2009 text of RDA completed software designed ... but >>> still a set of static documents that need to be transformed into a web tool 2010 first release of the RDA Toolkit (RDA plus) 2010 US testing (US RDA Test Coordinating Committee) 2011 US national libraries and the Program for Cooperative Cataloging: intention to implement if certain conditions are met implementation not before 2013
  • 8.
    8 Moving towards RDA 2011 some of the libraries who tested RDA decide to continue producing RDA records 2011-2012 preparations for implementation - work on recommendations - community involvement 2012 announcement from the Library of Congress: target date for implementation: March 31, 2013 Long-Range RDA Training Plan http://www.loc.gov/aba/rda/pdf/RDA_Long-Range_Training_Plan.pdf
  • 9.
    9 Moving towards RDA 2012 other national libraries are also planning to target the 1st quarter of 2013 as their RDA implementation date: National Agricultural Library National Library of Medicine British Library Library and Archives Canada National Library of Australia Deutsche Nationalbibliothek (mid 2013)
  • 10.
    10 Is there aday 1? Yes and No 1) day 1 is important for a sharing data environment: PCC: declares day 1 for contributing to NACO authorities LC: declares day 1 for its own cataloguing operations 2) some institutions never switched back after the test 3) each institution decides on day 1 for bibliographic data
  • 11.
    11 March 31, 2013 •all new authority records contributed to LC/NACO authority file = RDA • all records coded pcc = all RDA access points all records coded pcc whether: • RDA description or • AACR2 description • LC will have completed training all its cataloging staff and all LC records will be RDA records
  • 12.
    12 by March 31,2013 • rapid rise in number of RDA bibliographic records • changes in LC/NACO authority file • distinction between RDA acceptable and not acceptable • global changes in individual databases implications for authority work implications for copy cataloging
  • 13.
  • 14.
    14 Phase 1 ofimplementation emphasis on continuity RDA data in MARC 21 in current catalogues still creating bibliographic and authority records some new fields some changed instructions some new instructions BUT >>> thinking about bibliographic information differently
  • 15.
    15 Phase 1 =starting down new track RDA • continuity and change • moves us to a new track • starts us on a promising track for the future use of our metadata • useful to understand some of the key RDA concepts and see the long view
  • 16.
  • 17.
    17 AACR2 RDA • continue to record the title • continue to record the statement of responsibility • continue to record the date of publication But … • new vocabulary • new way of thinking about how we do these steps
  • 18.
    18 Similar, but ... AACR2 1.2B1.Transcribe the edition statement as found on the item. Use abbreviations as instructed in appendix B and numerals as instructed in appendix C. RDA 2.5.1.4. Transcribe an edition statement as it appears on the source of information. No instruction to abbreviate or to convert to arabic numerals.
  • 19.
    19 Similar, but ... • serious adherence to the principle of representation “take what you see” t.p. data recorded 3rd ed. 3rd ed. Second edition Second edition
  • 20.
    20 On the surface… similar instructions but different framework new vocabulary but also new concepts
  • 21.
    21 2. Key conceptsin RDA Theoretical framework
  • 22.
    22 RDA’s theoreticalframework • explicit conceptual framework • aligned with the FRBR and FRAD conceptual models FRBR Functional Requirements for Bibliographic Records 1998 FRAD Functional Requirements for Authority Data 2009 FRAD is an extension of the FRBR model • both models developed under the auspices of IFLA • broad base of international consensus and support
  • 23.
    23 The two models •widely used data modeling technique: entity relationship model • entities • attributes • relationships • analyze bibliographic and authority data from the point of view of how that data is used
  • 24.
    24 RDA vocabulary fromFRBR + FRAD • user tasks • meaning and scope of the 11 bibliographic entities work person concept expression family object manifestation corporate body event item place • entities – attributes – relationships
  • 25.
    25 Organization and Structureof RDA RDA table of contents reflects alignment with FRBR Section 1-4 = Recording attributes Section 1. Recording attributes of manifestation and item Section 2. Recording attributes of work and expression Section 3. Recording attributes of person, family, and corporate body Section 4. Recording attributes of concept, object, event, and place [placeholder]
  • 26.
    26 Organization and Structureof RDA Sections 5-10 = Recording Relationships Section 5. Recording primary relationships between work, expression, manifestation, and item Section 6. Recording relationships to persons, families, and corporate bodies associated with a resource Section 7. Recording subject relationships [placeholder] Section 8. Recording relationships between works, expressions, manifestations, and items Section 9. Recording relationships between persons, families, and corporate bodies Section 10. Recording relationships between concepts, objects, events, and places [placeholder]
  • 27.
    27 User tasks fromFRBR + FRAD Bibliographic data Authority data • find • find • identify • identify • select • contextualize (clarify) • obtain • justify (understand)
  • 28.
    28 Attributes • how torecord the attributes of entities (characteristics) for example, entity = a manifestation attributes we record: title proper statement of responsibility edition statement place of publication etc.
  • 29.
    29 Relationships: links betweenentities work created by person item owned by family manifestation produced by corporate body work based on work manifestation electronic reprod. manifestation person member of family family founded corporate body
  • 30.
    30 Relationships in RDA 1. record relationship 2. specify exact nature of the relationship for example AACR2 name of a person ------- title of book • type of relationship may be embedded in text of description • bibliographic record contains name of person and title RDA name of a person --- type of relationship --- work • make the relationship explicit and clear • relationship designators = controlled vocabulary
  • 31.
    31 Relationship designators • specifyroles for example cartographer performer broadcaster former owner issuing body • specify the nature of the relationship for example adaptation of paraphrased as electronic reproduction of
  • 32.
    32 Relationships in RDA exampleswith MARC 21 coding: 245 10 $a British Atlantic, American frontier : $b spaces of power in early modern British America / $c Stephen J. Hornsby ; with cartography by Michael J. Hermann. 700 1# $a Herman, Michael J., $e cartographer 245 00 $a Alice in Wonderland, or, What's a nice kid like you doing in a place like this? /$c Hanna-Barbera Productions. 700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland. authority record 500 3# $w r $i Descendant family: $a Adams (Family)
  • 33.
    33 Theoretical framework • alignmentwith the FRBR and FRAD conceptual models • bibliographic and authority data >>> in terms of entities, attributes + relationships • identify what is important --- how is data used • systematic and coherent framework >>> conceptual clarity >>> logical consistency >>> reference point for further development
  • 34.
    34 Underlying data model >>>practical set of cataloguing instructions ● built on a theoretical framework ● built on a robust data model • widely used data modeling technique • understood by other metadata and data modeling communities e.g. software engineers, information systems and database designers
  • 35.
    35 2. Key conceptsin RDA Objectives and principles
  • 36.
    36 RDA Objectives &Principles • important part of RDA • shaped many of the instructions that are different from AACR2 • concur with the International Cataloguing Principles (ICP)
  • 37.
    37 RDA Objectives &Principles Objectives RDA 0.4.2 Principles RDA 0.4.3 • responsiveness to user • differentiation needs • sufficiency • cost efficiency • relationships • flexibility • representation • continuity • accuracy • attribution • common usage or practice • uniformity
  • 38.
    38 Principle of representation forexample RDA 0.4.3.4 principle = representation The data describing a resource should reflect the resource’s representation of itself. result = simplify transcription “Take what you see”
  • 39.
    39 RDA = Takewhat you see source = Kemptville, Ontario AACR2 = Kemptville, Ont. RDA = Kemptville, Ontario 264 1 $a Kemptville, Ontario ____________________________________________________________________________________________________________________ source = Band LXXXVIII (series numbering) AACR2 = Bd. 88 RDA = Band LXXXVIII 490 $a ... ; $v Band LXXXVIII
  • 40.
    40 RDA = Takewhat you see source = Third revised edition AACR2 = 3rd rev. ed. RDA = Third revised edition _____________________________________________ source = 2nd enlarged ed., revised AACR2 = 2nd enl. ed., rev. RDA = 2nd enlarged ed., revised
  • 41.
    41 Different instructions AACR2 1.0F. Inaccuracies In an area where transcription from the item is required, transcribe an inaccuracy or a misspelled word as it appears in the item. Follow such an inaccuracy either by [sic] or by i.e. and the correction within square brackets. Supply a missing letter or letters in square brackets. RDA 1.7.9 Inaccuracies When instructed to transcribe an element as it appears on the source of information, transcribe an inaccuracy or a misspelled word as it appears on the source, except where instructed otherwise.
  • 42.
    42 Inaccuracy in RDA 1.7.9continued Make a note correcting the inaccuracy if it is considered to be important for identification or access (see 2.20 ). If the inaccuracy appears in a title, record a corrected form of the title as a variant title (see 2.3.6 ) if it is considered to be important for identification or access. Exception: 2.3.1.4 Inaccuracies. When transcribing the title proper of a serial or integrating resource, correct obvious typographic errors, and make a note giving the title as it appears on the source of information (see 2.20.2.4 ) ...
  • 43.
    43 RDA = Takewhat you see title page = Melallization of polymers AACR2 = Melallization [sic] of polymers or Melallization [i.e. Metallization] of polymers RDA = Melallization of polymers 245 14 $a Melallization of polymers 246 1 $i Corrected title: $a Metallization of polymers
  • 44.
    44 2. Key conceptsin RDA Focus on the user
  • 45.
    45 RDA Objectives &Principles Objectives RDA 0.4.2 Principles RDA 0.4.3 • responsiveness to user • differentiation needs • sufficiency • cost efficiency • relationships • flexibility • representation • continuity • accuracy • attribution • common usage or practice • uniformity
  • 46.
    46 Focus on theuser • record data that is important to the user why is it important? helps the user to find identify select obtain
  • 47.
    47 Resource discovery =user tasks Bibliographic data Authority data • find • find • identify • identify • select • clarify • obtain • understand Why record the data? To help user achieve these tasks.
  • 48.
    48 Consistent focus onthe user • RDA divided into 10 sections • each section begins with general guidelines • functional objectives and principles specific to the section Functional objectives = relationship between data and user tasks the data (recorded or formulated according to the instructions in that section) the user tasks
  • 49.
    49 Examplefrom Section 1 Section 1= Recording attributes of manifestations & items 1.2 Functional Objectives and Principles The data describing a manifestation or item should enable the user to: a) find manifestations and items that correspond to the user’s stated search criteria b) identify the resource described … c) select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and encoding of information stored on the carrier d) obtain a resource …
  • 50.
    50 Basis for CataloguerJudgment • instructions encourage cataloguer judgment --- based on relationship to user tasks for example, from 3.7 Applied material Record the applied material used in the resource if it is considered important for identification or selection …
  • 51.
    51 Easier for userto identify • no abbreviations 300 $a 398 pages :$b illustrations ; $c 25 cm AACR2: 300 $a 398 p. :$b ill. ; $c 25 cm. • no square brackets 300 $a 48 unnumbered pages, 256 pages AACR2: 300 $a [48], 256 p. • replace Latin abbreviations 300 $a 48, that is, 96 pages AACR2: 300 $a 48 [i.e. 96] p. • avoid cryptic information 300 $a xiv, 179 pages (incomplete) AACR2: 300 $a xiv, 179 + p.
  • 52.
    52 Easier for userto find, identify RDA: no more: rule of three no more … [et al.] in description if statement of responsibility names more than one person >>> record all RDA 2.4.1.5 optional omission: record first named and summarize the omission [and six others] access points for first named or principal core or all or cataloger judgment or institutional policy
  • 53.
    53 Easier for userto find, identify RDA: record all authors; access points for all authors; define relationships with designators 100 1 $a Berry, John W., $e author. 245 10 $a Cross-cultural psychology : $b research and applications / $c John W. Berry, Ype H. Poortinga, Seger M. Breugelmans, Athanasios Chasiotis, David L. Sam. 250 $a Third edition. 260 $a Cambridge : $b Cambridge University Press, $c 2011. 300 $a xxii, 626 pages ; $c 25 cm 700 1 $a Poortinga, Ype H., $d 1939- $e author. 700 1 $a Breugelmans, Seger M., $e author. 700 1 $a Chasiotis, Athanasios, $e author. 700 1 $a Sam, David L., $e author.
  • 54.
    54 Easier for userto understand RDA optional omission (2.4.1.5): more than three, omit and summarize core relationship = access point for first-named 100 1 $a Berry, John W. 245 10 $a Cross-cultural psychology : $b research and applications / $c John W. Berry [and four others]. 250 $a Third edition. 260 $a Cambridge : $b Cambridge University Press, $c 2011. 300 $a xxii, 626 pages ; $c 25 cm
  • 55.
    55 Easier for userto find AACR2 Aesop’s fables. Polyglot. RDA Aesop’s fables. Greek Aesop’s fables. Latin Aesop’s fables. English Aesop’s fables. German AACR2 Aesop’s fables. English & German RDA Aesop’s fables. English Aesop’s fables. German
  • 56.
    56 2. Key conceptsin RDA Content standard
  • 57.
    57 RDA as acontent standard AACR2: MARC encoding + ISBD display RDA = what data should the cataloguer record? • possible to encode using many encoding systems • can be encoded using MARC • does not have to be encoded using MARC encoding • can be used with web friendly XML based encoding schema, such as Dublin Core, MODS • possible to display the data in many ways
  • 58.
    58 RDA as acontent standard not an encoding standard not a display standard • for example, take the data and create displays that suit your user group: RDA says: record person’s date of death= 2003 Display? died 2003 d. 2003 - 2003 date of death: 2003
  • 59.
    59 Possible display Issuing body:Whitney Museum of American Art 710 2# $a Whitney Museum of American Art, $e issuing body. Photographer: Burger, Hillel 700 1# $a Burger, Hillel, $e photographer. Author: Gaines, Isabel 100 1# $a Gaines, Isabel, $e author. Alice in Wonderland, or, What's a nice kid like you doing in a place like this? / Hanna-Barbera Productions. Parody of: Carroll, Lewis, 1832-1898. Alice's adventures in Wonderland. 700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland
  • 60.
    60 Identifying the entity either eye-readable data: name date of birth and death Shields, Carol, 1953-2003 and/or machine actionable data: identifier 0101A6635 http://viaf.org/viaf/4944537/#Shields,_Carol
  • 61.
    61 RDA as acontent standard • not locked into library encoding practices • not locked into library display practices • get out of the library silo >>> data visible on the web >>> data interacting with the data of other metadata communities
  • 62.
    62 2. Key conceptsin RDA Bibliographic information as data
  • 63.
    63 Data Elements element =A word, character, or group of words and/or characters representing a distinct unit of bibliographic information. appears similar to AACR2 definition minus “forming part of an area” effect is quite different from AACR2 each element is ≈ discrete ≈ precisely defined ≈ single attribute / single relationship
  • 64.
    64 AACR2 for example AACR2: informationembedded in non-specific places notes digital file characteristics physical description file type MARC 538 encoding format 516 file size 500 resolution 300 regional encoding transmission speed
  • 65.
    65 RDA RDA: precise elementsand element sub-types digital file characteristics RDA 3.19 file type encoding format file size resolution regional encoding transmission speed
  • 66.
    66 347 Digital FileCharacteristics new MARC field 347 subfield codes $a - File type (R) $b - Encoding format (R) $c - File size (R) $d - Resolution (R) $e - Regional encoding (R) $f - Transmission speed (R)
  • 67.
    67 AACR2 Information AACR2:ambiguity --- assume human will decipher AACR2: date of publication, distribution, etc. date of copyright date of manufacture MARC 21: 260 $c 260 $g
  • 68.
    68 RDA DataElements RDA: precise elements – only one kind of data in an element RDA: 5 different elements: RDA 2.7-2.11 date of production date of publication date of distribution date of manufacture date of copyright MARC 21: 264 $c 5 different indicators
  • 69.
    69 Controlled vocabulary • controlledvocabulary recommended for many elements encoding format DAISY, MP3, Access, XML, JPEG, TIFF, CAD, PDF, Blu-ray, VCD production method blueline, blueprint, engraving, etching, lithograph, photocopy, photoengraving, woodcut base material Bristol board, canvas, cardboard, ceramic, glass, leather, paper, parchment, vellum
  • 70.
    70 RDA data =precise + usable data RDA • each element is distinct and precisely defined • each element contains only one kind of data • controlled vocabulary in many elements  each element has the potential to be usable: to index to search to build meaningful displays of data  data in any element can be used: by humans by computers
  • 71.
    71 Many new elements many new elements but do not have to use them all core elements • not a level of description • core elements are a minimum “a floor, not a ceiling” • must include any additional elements required to differentiate the resource or entity from a similar one • inclusion of other elements --- cataloguer judgment
  • 72.
    72 2. Key conceptsin RDA Internationalization
  • 73.
    73 Beyond “Anglo-American” RDA 0.11.1: RDAis designed for use in an international context. options for use of • other languages • other scripts • other calendars • other numeric systems • other units of measurement
  • 74.
    74 RDA • when nottranscribing: some instructions say – ... record in the language preferred by the agency creating the data ... record in the preferred script of the agency creating the data 6.4.1.3 Recording Date of Work Record the date of the work in terms of the calendar preferred by the agency creating the data.
  • 75.
    75 RDA April 2012update • change at 6.2.1.7 for the international cataloguing community (proposed by the German National Library and approved by all constituencies) Basic instructions on recording titles of works RDA 6.2.1.7 Initial articles When recording the title, include an initial article, if present. Alternative Omit an initial article … original text at RDA 6.2.1.7 was: Omit an initial article …
  • 76.
    76 FRBR + FRADas point of reference broad international support for the explanatory power of the models common international language and conceptual understanding of the bibliographic universe as the foundation for a standard: • easier to apply in international context • easier for our data to interoperate with other data generated on the basis of a FRBR/FRAD understanding of the bibliographic universe
  • 77.
    77 On the internationalscene 2005-2009 comments on RDA drafts: from libraries beyond Australia, Canada, Great Britain and the United States 2011 formal launch of European RDA Interest (began in 2009) Group (EURIG) members from: Austria, Croatia, Denmark, Finland, France, Germany, Great Britain, Italy, Latvia, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, the Vatican >>> interest of countries who use AACR2 >>> interest of countries that have never used AACR
  • 78.
    78 On the internationalscene Translation projects: German Germany, Austria French Canada, France, Belgium Spanish licensing for: Argentina, Bolivia, Chile, Colombia, Costa Rica, Dominican Republic, Ecuador, El Salvador, Equatorial Guinea, Guatemala, Honduras, Mexico, Nicaragua, Panama, Paraguay, Peru, Spain, Uruguay, Venezuela Chinese (Mandarin) and expressions of interest from others
  • 79.
    79 Key concepts Key conceptsshape RDA: • theoretical framework • objectives and principles • focus on the user • content standard • bibliographic information as data • internationalization >>> visible impact on RDA and the content of instructions >>> many changes in RDA trace back to concepts
  • 80.
    80 Familiarity with keyRDA concepts • a useful way to grab hold of RDA • a useful way to approach RDA implementation
  • 81.
    81 Flickr credits: creativecommons attribution Tour de Toona by Team Traveller http://www.flickr.com/photos/teamtraveller/5928422950/ Cross track – iPhone wall paper by CJ Schmit http://www.flickr.com/photos/cjschmit/4623783487/ The roof continues by Martin Pettitt http://www.flickr.com/photos/mdpettitt/2521374167/ Oregon silo by TooFarNorth http://www.flickr.com/photos/toofarnorth/4597980984/ Rock climbing is fun by mariachily http://www.flickr.com/photos/mariachily/3382799213/
  • 82.

Editor's Notes

  • #38 Objectives 0.4.2.1Responsiveness to User NeedsThe data should enable the user to:find resources that correspond to the user's stated search criteriafind all resources that embody a particular work or a particular expression of that workfind all resources associated with a particular person, family, or corporate bodyfind all resources on a given subjectfind works, expressions, manifestations, and items that are related to those retrieved in response to the user's searchfind persons, families, and corporate bodies that correspond to the user's stated search criteriafind persons, families, or corporate bodies that are related to the person, family, or corporate body represented by the data retrieved in response to the user’s searchidentify the resource described (i.e., confirm that the resource described corresponds to the resource sought, or distinguish between two or more resources with the same or similar characteristics)identify the person, family, or corporate body represented by the data (i.e., confirm that the entity described corresponds to the entity sought, or distinguish between two or more entities with the same or similar names, etc.)select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and encoding of information stored on the carrierselect a resource appropriate to the user's requirements with respect to form, intended audience, language, etc. obtain a resource (i.e., acquire a resource through purchase, loan, etc., or access a resource electronically through an online connection to a remote computer)understand  the relationship between two or more entitiesunderstand  the relationship between the entity described and a name by which that entity is known (e.g., a different language form of the name)understand why a particular name or title has been chosen as the preferred name or title for the entity.0.4.2.2Cost EfficiencyThe data should meet functional requirements for the support of user tasks in a cost-efficient manner.0.4.2.3Flexibility The data should function independently of the format, medium, or system used to store or communicate the data. They should be amenable to use in a variety of environments.0.4.2.4Continuity The data should be amenable to integration into existing databases (particularly those developed using AACR and related standards).Differentiation The data describing a resource should differentiate that resource from other resources.The data describing an entity associated with a resource should differentiate that entity from other entities, and from other identities used by the same entity.0.4.3.2Sufficiency The data describing a resource should be sufficient to meet the needs of the user with respect to selection of an appropriate resource.0.4.3.3Relationships The data describing a resource should indicate significant relationships between the resource described and other resources.The data describing an entity associated with a resource should reflect all significant bibliographic relationships between that entity and other such entities.0.4.3.4Representation The data describing a resource should reflect the resource’s representation of itself.The name or form of name designated as the preferred name for a person, family, or corporate body should be the name or form of name most commonly found in resources associated with that person, family, or corporate body, or a well-accepted name or form of name in the language and script preferred by the agency creating the data. Other names and other forms of the name that are found in resources associated with the person, family, or corporate body or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant names.The title designated as the preferred title for a work should be the title most frequently found in resources embodying the work in its original language, the title as found in reference sources, or the title most frequently found in resources embodying the work. Other titles found in resources embodying the work or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant titles.0.4.3.5Accuracy The data describing a resource should provide supplementary information to correct or clarify ambiguous, unintelligible, or misleading representations made on sources of information forming part of the resource itself.0.4.3.6Attribution The data recording relationships between a resource and a person, family, or corporate body associated with that resource should reflect attributions of responsibility made either in the resource itself or in reference sources, irrespective of whether the attribution of responsibility is accurate.0.4.3.7Common Usage or PracticeData that is not transcribed from the resource itself should reflect common usage in the language and script preferred by the agency creating the data.The part of the name of a person or family used as the first element in recording the preferred name for that person or family should reflect conventions used in the country and language most closely associated with that person or family.0.4.3.8Uniformity The appendices on capitalization, abbreviations, order of elements, punctuation, etc., should serve to promote uniformity in the presentation of data describing a resource or an entity associated with a resource.
  • #46 Objectives 0.4.2.1Responsiveness to User NeedsThe data should enable the user to:find resources that correspond to the user's stated search criteriafind all resources that embody a particular work or a particular expression of that workfind all resources associated with a particular person, family, or corporate bodyfind all resources on a given subjectfind works, expressions, manifestations, and items that are related to those retrieved in response to the user's searchfind persons, families, and corporate bodies that correspond to the user's stated search criteriafind persons, families, or corporate bodies that are related to the person, family, or corporate body represented by the data retrieved in response to the user’s searchidentify the resource described (i.e., confirm that the resource described corresponds to the resource sought, or distinguish between two or more resources with the same or similar characteristics)identify the person, family, or corporate body represented by the data (i.e., confirm that the entity described corresponds to the entity sought, or distinguish between two or more entities with the same or similar names, etc.)select a resource that is appropriate to the user’s requirements with respect to the physical characteristics of the carrier and the formatting and encoding of information stored on the carrierselect a resource appropriate to the user's requirements with respect to form, intended audience, language, etc. obtain a resource (i.e., acquire a resource through purchase, loan, etc., or access a resource electronically through an online connection to a remote computer)understand  the relationship between two or more entitiesunderstand  the relationship between the entity described and a name by which that entity is known (e.g., a different language form of the name)understand why a particular name or title has been chosen as the preferred name or title for the entity.0.4.2.2Cost EfficiencyThe data should meet functional requirements for the support of user tasks in a cost-efficient manner.0.4.2.3Flexibility The data should function independently of the format, medium, or system used to store or communicate the data. They should be amenable to use in a variety of environments.0.4.2.4Continuity The data should be amenable to integration into existing databases (particularly those developed using AACR and related standards).Differentiation The data describing a resource should differentiate that resource from other resources.The data describing an entity associated with a resource should differentiate that entity from other entities, and from other identities used by the same entity.0.4.3.2Sufficiency The data describing a resource should be sufficient to meet the needs of the user with respect to selection of an appropriate resource.0.4.3.3Relationships The data describing a resource should indicate significant relationships between the resource described and other resources.The data describing an entity associated with a resource should reflect all significant bibliographic relationships between that entity and other such entities.0.4.3.4Representation The data describing a resource should reflect the resource’s representation of itself.The name or form of name designated as the preferred name for a person, family, or corporate body should be the name or form of name most commonly found in resources associated with that person, family, or corporate body, or a well-accepted name or form of name in the language and script preferred by the agency creating the data. Other names and other forms of the name that are found in resources associated with the person, family, or corporate body or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant names.The title designated as the preferred title for a work should be the title most frequently found in resources embodying the work in its original language, the title as found in reference sources, or the title most frequently found in resources embodying the work. Other titles found in resources embodying the work or in reference sources, or that the user might be expected to use when conducting a search, should be recorded as variant titles.0.4.3.5Accuracy The data describing a resource should provide supplementary information to correct or clarify ambiguous, unintelligible, or misleading representations made on sources of information forming part of the resource itself.0.4.3.6Attribution The data recording relationships between a resource and a person, family, or corporate body associated with that resource should reflect attributions of responsibility made either in the resource itself or in reference sources, irrespective of whether the attribution of responsibility is accurate.0.4.3.7Common Usage or PracticeData that is not transcribed from the resource itself should reflect common usage in the language and script preferred by the agency creating the data.The part of the name of a person or family used as the first element in recording the preferred name for that person or family should reflect conventions used in the country and language most closely associated with that person or family.0.4.3.8Uniformity The appendices on capitalization, abbreviations, order of elements, punctuation, etc., should serve to promote uniformity in the presentation of data describing a resource or an entity associated with a resource.