1 / 26

Gordon Dunsire Depute Director, Centre for Digital Library Research

RDA ( Resource Description and Access ) and its application to rare books, manuscripts, and their digital surrogates. Gordon Dunsire Depute Director, Centre for Digital Library Research University of Strathclyde, Glasgow, Scotland Presented to Summer School in the Study of Old Books

hoang
Download Presentation

Gordon Dunsire Depute Director, Centre for Digital Library Research

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. RDA (Resource Description and Access) and its application to rare books, manuscripts, and their digital surrogates Gordon Dunsire Depute Director, Centre for Digital Library Research University of Strathclyde, Glasgow, Scotland Presented to Summer School in the Study of Old Books Zadar, Croatia, 28 Sep - 2 Oct 2009

  2. Overview • RDA • FRBR • Principles • Application

  3. RDA Resource Description and Access A new standard for creating bibliographic metadata Based on the Anglo-American Cataloguing Rules In development since 1841 (Panizzi’s rules for the British Museum) And Functional Requirements for Bibliographic Records (FRBR) and other more modern stuff FRBR published 1998

  4. User-centred features of RDA (1) • Covers all types of user • Those who need to find, identify, select, obtain and use information, and manage and organize information bibliographically • Covers all media • Print-based, digital; textual, visual, etc. • Equal, even treatment gives more control to the user in finding and choosing the most appropriate resources

  5. User-centred features of RDA (2) • Clearly distinguishes content from carrier • E.g. Moving pictures on DVD; text on CD-ROM • Helpful for users with special needs • E.g. restrict search to non-visual resources • Multinational • Anglo-centricity (and cataloguer-eccentricity) removed • Abbreviations and acronyms avoided • Latinisms removed • Farewell s.n., s.l., et al. • [Still arguing about square brackets!]

  6. User-centred features of RDA (3) • Independent of technical metadata formats • Can be used with MARC, DC (Dublin Core) • And a whole bunch of other acronyms • Gives user familiar metadata regardless of what system is used • Designed for the digital environment • RDA will be published as an online product • So could be incorporated in user help facilities • E.g. How a “preferred title for the work” (uniform title) is derived • Improves the FRBRizability of catalogues

  7. FRBR • Presents a common understanding of the aims and purpose of bibliographic metadata • With a framework and model to support that understanding • Developed for International Federation of Library Associations and Institutions (IFLA) from 1992 to 1997 • User-centric

  8. FRBR user tasks • Aims and purpose of bibliographic metadata • Find an information resource • Matching the user’s search criteria • Identify a resource • Confirming the user’s criteria; distinguishing similar resources • Select a resource • Meeting the user’s needs • Obtain a resource • Accessing the information in the resource

  9. FRBR model • Identifies 3 groups of entities • Group 1 represents the different aspects of user interests in the products of intellectual or artistic endeavour • Group 2 represents what is responsible for the content, production and custodianship of Group 1 entities • Group 3 represents the subjects of one of the Group 1 entities

  10. Group 1 entities • Work • A distinct intellectual or artistic creation • Expression • Intellectual or artistic realisation of a Work • Manifestation • Physical embodiment of an Expression • Item • Single exemplar of a Manifestation

  11. FRBRization Work Symphony no.1 Is realised through Expression 1 Expression 2 LSO performance Is embodied in Manifestation 1.1 Manifestation 2.1 Manifestation 2.2 DVD-A Is exemplified by Item 1.1.1 Item 2.1.1 Item 2.2.1 Item 2.2.2 Copy on shelf

  12. Cataloguer-centred features of RDA • More emphasis on cataloguer’s judgment • Guidelines rather than “rules” • Rules grouped by bibliographic element rather than format • Bibliographic elements related to FRBR entities (related to user tasks) • Why am I recording this information? • Authority control included • Generally compatible with AACR

  13. RDA Objectives and principles • Objectives • Comprehensiveness; Consistency; Clarity; Rationality; Currency; Compatibility; Adaptability; Ease and efficiency of use; Format • Principles • Generalization; Specificity; Non-redundancy; Terminology; Reference structure • “The IME-ICC draft Statement of International Cataloguing Principles informs the cataloguing principles used throughout RDA.” • Statement ... now published (2009)

  14. Content vs Carrier • Distinguishes content from carrier • Using the RDA/ONIX framework for resource categorization • Being augmented by Vocabulary Mapping Framework • “High level” category labels (controlled terms) • Content type < FRBR Expression • E.g. “text”; “still image” • Carrier type < FRBR Manifestation • E.g. “volume”; “online resource” • Different users = different emphasis • The carrier is the content (after McLuhan)

  15. Core and communities • RDA elements mapped to FRBR Group 1 entities • E.g. Preferred [uniform] title < Work • Some elements designated “core” • not mandatory! • Special communities (e.g. Rare books) expected to designate additional core elements • Minimum input standard • And use of options (few, but some) • Preferred language of cataloguing agency, etc.

  16. RDA for specific types of resource (1) • RDA 2.8.4.1 “For early printed resources, printers and booksellers are treated as publishers.” • 2: Identifying Manifestations and Items > 2.8 Publication statement > 2.8.4 Publisher’s name > 2.8.4.1 Scope • Rule hierarchy aids logical layout of RDA, but can be transparent in a digital environment • “Early printed resources” is controlled terminology • Clarity and ease of use of rules • (ISBD: “older monographic publications”)

  17. RDA for specific types of resource (2) • RDA 3.9.2.3 Recording Production Method for Manuscripts “If the resource is a manuscript, record one of the following terms as appropriate.” • holograph (written by the work creator) • manuscript (written by other than the creator) • printout • typescript • More controlled terminology • Consistency for user

  18. RDA for specific types of resource (3) • RDA 6.2 Title of the Work • RDA 6.2.2.5 Works Created Before 1501 “... choose the title or form of title in the original language by which the work is identified in modern sources as the preferred title.” • RDA 6.2.2.8 Incunabula “Choose as the preferred title for a work contained in an incunabulum the title found in standard reference sources for incunabula.” • RDA 0.4.3.4 Representation • “... 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.”

  19. Focus and metadata density • Items readily available (multiple, identical copies) => Less need for distinct item metadata • Nearest available copy is function of collection-level and patron transaction metadata • User focus is on expression and manifestation • E.g. My gadget can’t handle PDF documents • Rare (but not unique) items => More need for distinct item metadata • E.g. Numeration in limited edition • E.g. Provenance

  20. FRBR: rare vs digital Often unique: 1 item, 1 manifestation, 1 expression Digital copy (image) is a new manifestation (Different file type = new manifestation) Work Expression 1 Manifestation 1.1 Manifestation 1.2 (PDF) Manifestation 1.3 (DOC) Item 1.1.1 Item 1.2.1 Item 1.2.2 Item 1.3.1 Item 1.3.2

  21. Relating manifestations Work Expression 1 Manifestation 1.1 Manifestation 1.2 (PDF) ? Item 1.1.1 Item 1.2.1 Item 1.2.2 Manifestations 1.1 and 1.2 related implicitly via Expression 1 Specific nature of relationship needs explicit metadata RDA Appendix J: “electronic reproduction”; “digital transfer”

  22. Organising metadata Original Surrogate Translated Expression Derived Work Contained Work SILOS W1 E1 M1 I1 W1 E1 M2 I2 W1 E2 M3 I3 W2 E3 M4 I4 W3 E4 M5 I5 W1 W2 W3 Relators: Structural Semantic WEB E1 E2 E3 E4 M1 M2 M3 M4 M5 I1 I2 I3 I4 5

  23. Thank you • g.dunsire@strath.ac.uk

  24. Workshop. 1: Entities and elements • Why am I recording this information? • What is a Work? • Owner inscriptions, annotations, addenda? • What is an Item element? (or are these Works?) • Owner bookplates, stamps, bindings • Library bookplates, stamps, bindings • Other indications of provenance

  25. Workshop. 2: Relationships • RDA Appendix J: “electronic reproduction”; “digital transfer” • Item-Item or Manifestation-Manifestation? • Other FRBR Group 1 relators in Appendix J • Derivation; part/whole (contains); etc. • RDA Appendix I: Relators between Group 1 and Group 2 entities • “book designer”, “engraver”, “platemaker”, “printer”, etc. • “current owner”, “previous owner” • “autographer”

  26. Workshop. 3: Metadata organisation • FRBR de-duplication • Avoid repetition of Work, Expression ... • Need for record (instance) identifiers • But how to achieve globally? • Semantic web • FRBR and RDA element and role/relator registration • Beyond bibliographic description • Modelling provenance, publisher/printer histories, etc.

More Related