Presentation is loading. Please wait.

Presentation is loading. Please wait.

RDA Designed for current and future environments Chris Oliver McGill University May 11, 2011.

Similar presentations


Presentation on theme: "RDA Designed for current and future environments Chris Oliver McGill University May 11, 2011."— Presentation transcript:

1 RDA Designed for current and future environments Chris Oliver McGill University chris.oliver@mcgill.ca May 11, 2011

2 RDA = Resource Description and Access new metadata standard replaces AACR2 designed for the web environment better metadata to support better resource discovery

3 Designed for now and the future Now designed to work in the current environment compatible with AACR2 records can encode in MARC 21 and store in current databasesFuture designed to work in future environments new database structures data on the web linked data in the semantic web environment library data visible in the web alongside other types of metadata

4 Plan for the webinar 1. What is RDA? 2. What makes RDA different?  RDA as a content standard  RDA’s underlying framework - data model - data elements Questions, comments 3. Bibliographic and authority data in new environments  RDA data beyond MARC records  RDA data beyond the current catalog  RDA data on the web Questions, comments

5 What is RDA? What is RDA? relationship to AACR2 a content standard

6 AACR2 RDA continue to record title continue to record edition continue to record date of publication But … new vocabulary new way of thinking about how we do these steps

7 Relationship to AACR2 RDA 0.2 reworked” “ instructions derived from AACR have been reworked” many instructions originate from AACR2 instructions are reworded and organized differently within a new theoretical framework every word has changedmany instructions show visible continuity with AACR2

8 AACR2 RDA AACR2 deconstructed new concepts new structure new vocabulary some new instructions some changed instructions

9 What makes RDA different? some continuity with AACR2 But … RDA as a content standard ◦ flexibility ◦ adaptability theoretical framework bibliographic and authority information as “data”

10 RDA = content standard RDA RDA not an encoding standard not a presentation standard RDA RDAwhat data do I record? RDA RDA 0.4.2Objectives 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.

11 RDA = content standard RDA data can be encoded using: MARC 21 encoding schema such as Dublin Core, MODS, and others web friendly encoding schema based on XML RDA data can be presented using : ISBD conventions labelled display newly developed display conventions display conventions used in other metadata communities

12 Examples in RDA examples show what the data should be: RDA 2.4.1.4 Recording Statements of Responsibility Transcribe a statement of responsibility in the form in which it appears on the source of information. EXAMPLE by Walter de la Mare Fats Waller by Dr. Johnson by Sir Richard Acland by Alfred, Lord Tennyson by a Lady of Quality par Charles M. Schultz directed and produced by the Beatles

13 Examples in RDA AACR2 2.1F1. Transcribe statements of responsibility relating to persons or bodies as instructed in 1.1F 1.1F Shut up in Paris / by Nathan Sheppard Great Britain : handbook for travellers / by Karl Baedecker Vas-y, Charlie Brown / par Charles M. Schulz MARC 21 manual 245 $c statement of responsibility … 245 04 $a The plays of Oscar Wilde /$c Alan Bird. 245 10 $a How to play chess /$c Kevin Wicker ; with a foreword by David Pritchard ; illustrated by Karel Feuerstein.

14 RDA as a content standard record reliable data how to encode data – not part of the standard RDA says: record person’s date of birth 1978 Many possibilities for encoding: $d 1978- MARC 21 1978-. MARCXML 1978- 1978 1978

15 RDA as a content standard record reliable data how to display data – not part of the standard RDA says: record person’s date of birth 1978 Many possibilities for display: born 1978 b. 1978 1978- date of birth: 1978

16 RDA as a content standard designed for use by libraries designed to be flexible and adaptable to many environments not tied to library-specific encoding not tied to library-specific display of data data that can interact and co-exist with metadata of other cultural heritage communities data that can be used in the web environment

17 Day 1 of implementation most – in MARC 21 environment most – in conventional library databases – bibliographic records, authority records + holdings records RDA records in MARC 21 Library of Congress catalog US RDA Test documentation OCLC WorldCat Libraries that participated in the US Test

18 Example: RDA in MARC 21 020 $a 9780521440080 100 1 $a Adrian, R. J. $q (Ronald J.), $e author 245 10$a Particle image velocimetry / $c Ronald J. Adrian, Jerry Westerweel. 260$a New York : $b Cambridge University Press, $c 2011, ©2011. 300$a xxvi, 558 pages : $b illustrations ; $c 26 cm. 336$a text $2 rdacontent 337$a unmediated $2 rdamedia 338$a volume $2 rdacarrier 490 1$a Cambridge Aerospace series ; $v 30 700 1 $a Westerweel, J., $e author 830 0$a Cambridge Aerospace series ; $v 30

19 Example: RDA in MARC 21 020 $a 9780521440080 100 1 $a Adrian, R. J. $q (Ronald J.), $e author 245 10$a Particle image velocimetry / $c Ronald J. Adrian, Jerry Westerweel. 260$a New York : $b Cambridge University Press, $c 2011, ©2011. 300$a xxvi, 558 pages : $b illustrations ; $c 26 cm. 336$a text $2 rdacontent 337$a unmediated $2 rdamedia 338$a volume $2 rdacarrier 490 1$a Cambridge Aerospace series ; $v 30 700 1 $a Westerweel, J., $e author 830 0$a Cambridge Aerospace series ; $v 30

20 Example: RDA in MARC 21 110 2 $a Indian Map Service. 245 00$a Assam tourist road atlas & state distance guide / $c designed, cartographed, printed & published by Indian Map Service ; editors, R.P. Arya [and three others]. 246 3$a Assam tourist road atlas and state distance guide 255 $a Scales differ. 260$a Jodhpur, India : $b Indian Map Service, $c 2010, ©2010. 300$a 1 atlas (40 pages) : $b color illustrations, color maps ; $c 25 cm. 336$a cartographic image $2 rdacontent 337$a unmediated $2 rdamedia 338$a volume $2 rdacarrier 700 1$a Arya, R. P.

21 Example: RDA in MARC 21 110 2 $a Indian Map Service. 245 00$a Assam tourist road atlas & state distance guide / $c designed, cartographed, printed & published by Indian Map Service ; editors, R.P. Arya [and three others]. 246 3$a Assam tourist road atlas and state distance guide 255 $a Scales differ. 260$a Jodhpur, India : $b Indian Map Service, $c 2010, ©2010. 300$a 1 atlas (40 pages) : $b color illustrations, color maps ; $c 25 cm. 336$a cartographic image $2 rdacontent 337$a unmediated $2 rdamedia 338$a volume $2 rdacarrier 700 1$a Arya, R. P.

22 Look beyond day 1 day 1 implementation ≠ task is completed day 1 beginning on a new track making the point of transition as smooth as possible emphasizing continuity

23 Us and our legacy data

24 RDA … takes us from where we are moves us to a new track allows us to change direction start travelling along a new track

25 RDA’s framework the data model the data elements

26 RDA’s framework the data model

27 Explicit RDA data model ERD = entity relationship diagram in RDA Toolkit or available at: http://www.rdatoolkit.org/backgroundhttp://www.rdatoolkit.org/background

28

29 Aligned with IFLA conceptual models FRBRFunctional Requirements for Bibliographic Records 1998 FRADFunctional Requirements for Authority Data 2009 (FRSADFunctional Requirements for Subject Authority Data approved 2010) FRAD and FRSAD are extensions of the FRBR model

30 FRBR + FRAD based on the analysis of bibliographic and authority records entity-relationship models IFLA task forces world-wide consultation international consensus

31 Why are the models important? internationally shared conceptual model broad international support for the explanatory power of the models common international language and conceptual understanding of the bibliographic universe entity-relationship model widely used data modeling technique understood by other metadata and data modeling communities e.g. software engineers, information systems and database designers

32 Why are the models important? as the foundation for a standard: provides a logically consistent underlying framework makes it easier for other metadata communities to understand the structure of our data makes it easier to apply in an international context makes it easier for our data to interoperate with data modeled similarly other data that aligns with a FRBR/FRAD model other data that conforms to a similar entity- relationship model

33 Entities - attributes - relationships new vocabulary entity = the object of a user’s interest entities that are of interest to someone who uses bibliographic and authority data RDA focuses on: bibliographic entities entities specific to authority control

34 Bibliographic entities (FRBR/FRAD) work expression manifestation item person family corporate body concept object event place FRBR Group 1 products of intellectual or artistic endeavor FRBR Group 2 responsible for group 1 entities FRBR Group 3 subjects (includes group 1 & 2)

35 Authority entities (FRAD) bibliographic entities name identifier controlled access point rules agency entities on which authority data is focused entities for authority control entities that determine the content and form of access points

36 Authority entities (FRAD) bibliographic entities name identifier controlled access point rules agency entities on which authority data is focused entities for authority control entities that determine the content and form of access points

37 Attributes characteristics of the entity data to be recorded about the entity examples of attributes: work: title, genre manifestation:publisher, date of publication, extent item: identifier (e.g. barcode), provenance person: name, dates, gender corporate body: place, dates, address object: term

38 Relationships: links between entities link between one entity and another basis for navigation and support collocation explicitly defined primary relationships: between work, expression, manifestation and item 3 other major types of relationships: 1.between a person, family or corporate body and a resource 2.between one resource and another resource 3.between a person, family or corporate body and another person, family or corporate body

39 Relationships: links between entities work created by person itemowned byfamily manifestation produced by corporate body workbased on work manifestation electronic reprod. manifestation personmember offamily familyfoundedcorporate body

40 Organization and Structure of RDA  2 main parts Recording attributessections 1-4 Recording relationshipssections 5-10  Divided into 10 sections sections are organized according to the bibliographic entities

41 Organization and Structure of RDA 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]

42 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 the subject of a work [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]

43 Entities - attributes - relationships new vocabulary new way of thinking about bibliographic and authority information careful separation of content and carrier datathat a human can read and interpret that is machine actionable

44 RDA’s framework the data elements

45 Elements in RDA and AACR2 RDA element = A word, character, or group of words and/or characters representing a distinct unit of bibliographic information. AACR2 element = similar definition plus … and forming part of an area of the description. AACR2 elements are organized and embedded into areas

46 RDA data elements move away from: paragraph style (ISBD areas) data embedded in long character strings data stored in ambiguous elements move towards: independent, separate units of data precisely defined or “parsed” each element contains data about a single attribute or a single relationship increased use of controlled vocabulary

47 RDA data elements distinct and defined elements for each kind of data illustrative content encoding format different element production method for each type of sound content dataapplied material base material reduction ratio

48 Elements in AACR2 AACR2: information embedded in “other physical details” (or a non-specific note) illustrative content encoding format other physical production method detailssound content applied material MARC 300 $bbase material reduction ratio

49 Controlled vocabulary controlled vocabulary recommended for many elements encoding formatDAISY, MP3, Access, XML, JPEG, TIFF, CAD, PDF, Blu-Ray, VCD production methodblueline, blueprint, engraving, etching, lithograph, photocopy, photoengraving, woodcut base materialBristol board, canvas, cardboard, ceramic, glass, leather, paper, parchment, vellum

50 RDA data elements distinct and defined elements for each kind of data = groundwork for the future illustrative content encoding format currently map to production method MARC 300 $b sound content applied material base material reduction ratio day 1 implementation in MARC 21 environment – data will still be ambiguous

51 RDA data elements only one kind of data in an element AACR2: date of publication, distribution, etc. MARC 21: 260 $c RDA: 4 different elements: date of production date of publication date of distribution date of copyright

52 Dates of publication and copyright AACR2: Published: New York : Palgrave Macmillan, 2011. Published: Cambridge, Mass. : Candlewick Press, c2006. RDA: Published: New York : Palgrave Macmillan, 2011, ©2011. Published: Cambridge, Massachusetts : Candlewick Press, [2006], ©2006. day 1 implementation in MARC 21 environment – new proposal for less ambiguity: 2011-DP01

53 RDA data elements remove ambiguity AACR2 AACR2: 1.7B13. Dissertations information embedded in a note note about academic degree, granting institution or faculty and year degree granted RDA: RDA: 7.9.1 Recording Dissertation or Thesis Information separate elements for: academic degree granting institution or faculty year degree granted day 1 implementation in MARC 21 environment – subfields for 502 already implemented

54 Thesis information RDA elements: Academic degreePh.D. Granting institution or facultyMcGill University Year degree granted2009 Already have 2 options in MARC 21: 502 $a Thesis (Ph.D.)—McGill University, 2009. 502 $b Ph.D. $c McGill University $d 2009

55 Thinking “data” even within the MARC environment, we’re thinking about parsing information strings into data elements more granularity for: thesis information place and date of capture dates of pub., dist., man., prod.in progress date of copyrightin progress form of work medium of performance even for display: 260 $a [San Francisco?] : $b [publisher not identified], $c [2009?].

56 Identifiers from FRAD: entities are known by their names and/or are assigned identifiers RDAhas an element defined for recording the identifier of each bibliographic entity:item manifestation expression work person family corporate body RDA has option to use identifiers to reference relationships

57 Identifiers name = more suitable for humans to read and interpret eye-readable data: name, date … Shields, Carol, 1953-2003 identifier = more suitable for machines to make links = scope to use a URI as an identifier = machine actionable data 0101A6635 http://viaf.org/viaf/4944537/#Shields,_Carol

58 Relationship designators specify nature of relationships specify roles e.g.cartographer performer broadcaster former owner specify relationship between resources e.g.adaptation of musical setting of paraphrased as

59 Access points for automated env. AACR2Aesop’s fables. Polyglot. RDAAesop’s fables. Greek Aesop’s fables. Latin Aesop’s fables. English Aesop’s fables. German AACR2Aesop’s fables. English & German RDA Aesop’s fables. English Aesop’s fables. German

60 RDA data elements still recording the same kind of information title edition date of publication record in distinct data elements record with more precision data that a human can use data that is machine actionable each element has the potential to be used: - to search - to navigate - to retrieve - to build meaningful displays of data

61 Questions, comments ? ? ?

62 Bibliographic and authority data in new environments Bibliographic and authority data in new environments RDA data beyond MARC records RDA beyond the current catalog RDA data on the web

63 RDA = “well-formed” metadata instructions on how to record data for each element controlled vocabulary is used as the value recorded in many elements underlying model for the data √ elements defined in the way that other metadata communities expect √ RDA data can interoperate with data modeled similarly √ preparation for use of RDA data on the web, in linked data environment of the future – the next two sessions

64 RDA in XML not an abstract goal for the future US test included testing RDA for descriptions encoded using Dublin Core and MODS RDA Toolkit includes a section on schemas download RDA element sets as XML schema core enhanced specialized universal

65 Part of MODS record - US test data [snip] Edward P. Bailey, Jr. Transcribed from verso [snip] University Archives Photograph Collection [snip] computer online resource still image

66 Part of MODS record - US test data [snip] Inside Poor Monkey's Brown, Luther 1951- Delta State University author [snip] monographic [snip] text file image file video file HTML [snip]

67 Beyond the traditional catalog online catalog = closed database ◦ abundance of metadata ◦ invisible to web search engines“dark data” MARC 21 = library specific record format ◦ developed before concept of relational databases ◦ used in closed databases of the library world ◦ web cannot access and use MARC data ◦ many ILS cannot fully use MARC data ◦ not used in other cultural heritage communities

68 Squeezing into MARC 21 … it can be done … but more comfortable fit elsewhere?

69 RDA data in current databases bibliographic records = description + access points + authority records – linked to access points + holdings records – linked to bib records diagram by Tom Delsey from his presentation to the Deutsche Nationalbibliothek, Frankfurt, Germany, June 2 nd, 2009: http://www.rda-jsc.org/docs/td20090602.pdfhttp://www.rda-jsc.org/docs/td20090602.pdf Bibliographic Authority Holdings

70 RDA data is flexible in new types of database structures e.g. object oriented database database mirroring FRBR/FRAD model cluster of data pertaining to each entity manifestation record + item record + work record + expression record + record for person, family, corporate body + relationships = links between the above entities

71 illustration: from Tom Delsey’s presentation to the Deutsche Nationalbibliothek, Frankfurt, Germany, June 2 nd, 2009: http://www.rda-jsc.org/docs/td20090602.pdfhttp://www.rda-jsc.org/docs/td20090602.pdf

72 AACR2 + MARC 21 for example name of a person ------- title of a resource AACR2 + MARC 21 type of relationship embedded in text of bibliographic description bibliographic record contains name of person and title may have an authority record that also ties together name of person and title of work

73 AACR2 + MARC 21 bibliographic record for the animated film 245 00 $a Alice in Wonderland, or, What's a nice kid like you doing in a place like this? /$cHanna-Barbera Productions. 700 1# $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland. record may or may not include text in a note that explains the relationship between Lewis Carroll and the film

74 RDA + MARC 21 for example name of a person ------- title of book RDA + MARC 21 type of relationship embedded in text of bibliographic description bibliographic record contains name of person and title may have an authority record that also ties together name of person and title of work relationship designators in bibliographic records ($e, 4, i)

75 RDA + MARC 21 bibliographic record 245 00 $a Alice in Wonderland, or, What's a nice kid like you doing in a place like this? /$cHanna-Barbera Productions. 700 1# $i parody of (work) $a Carroll, Lewis, $d 1832-1898. $t Alice's adventures in Wonderland. suggested display of data : (MARC 21 Format for Bibliographic data) 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.

76 RDA + MARC 21 bibliographic record 100 1# $a Verdi, Giuseppe, $d1813-1901. 245 10 $a Otello :$b in full score / $c Giuseppe Verdi. 700 1# $i libretto based on (work) $a Shakespeare, William, $d 1564-1616. $t Othello. 787 08 $i reproduction of (manifestation) $a Verdi, Giuseppe, $d 1813-1901. $t Otello. $d Milan: Ricordi, c1913 day 1 implementation in MARC 21 environment – can record data about many types of relationships

77 RDA + MARC 21 authority record for a work: 100 1# $a Stoppard, Tom. $t Rosencrantz and Guildenstern are dead 500 1# $w r $i based on (work) $a Shakespeare, William, $d 1564-1616. $t Hamlet authority record for a person: 100 1# $a Clemens, Samuel, $d 1835-1910 500 ## $w r $i alternate identity $a Twain, Mark, $d 1835- 1910

78 RDA + post MARC 21 for example name of a person ------- title of a resource RDA + post MARC 21 record environment data about entities: “record” or cluster of data for person, work, expression (as needed), manifestation, item … explicitly defined relationships between entities explicitly defined relationships means that MARC record structure is no longer required

79 RDA data data inside MARC record wrapper data outside MARC record wrapper bibliographic data work data manifestation data person data data of another work manifestation data data about item data of another work

80 Where is the future? data that supports resource discovery data that is visible on the web data that enables machine-actionable processing of data data that can be stored and used in new database structures data that can connect us with other communities

81 RDA moves us forward RDA … takes us from where we are moves us to a new track opens up possibilities for the future

82 Images from Flickr Creative Commons attribution license Dinner train by Slideshow Bruce http://www.flickr.com/photos/springfieldhomer/95614622/ Cross track – iPhone wall paper by CJ Schmit http://www.flickr.com/photos/cjschmit/4623783487/ Behind the big red ball by Christopher Woo http://www.flickr.com/photos/deks/3618803169/ Tracks by eirikref http://www.flickr.com/photos/eirikref/432088535/

83 Thank you Questions, comments ? ? ? contact info: chris.oliver@mcgill.ca


Download ppt "RDA Designed for current and future environments Chris Oliver McGill University May 11, 2011."

Similar presentations


Ads by Google