Presentation is loading. Please wait.

Presentation is loading. Please wait.

RDA Training Day MOBIUS Conference, Columbia, Missouri Wednesday, June 4, 2014 Presenters: Charles Croissant, Senior Catalog Librarian Pius XII Memorial.

Similar presentations


Presentation on theme: "RDA Training Day MOBIUS Conference, Columbia, Missouri Wednesday, June 4, 2014 Presenters: Charles Croissant, Senior Catalog Librarian Pius XII Memorial."— Presentation transcript:

1 RDA Training Day MOBIUS Conference, Columbia, Missouri Wednesday, June 4, 2014 Presenters: Charles Croissant, Senior Catalog Librarian Pius XII Memorial Library, Saint Louis University Felicity Dykas, Head, Digital Services Department MU Libraries, University of Missouri-Columbia

2 2 “Why Do We Catalog?” People with information needs Catalog records Library resources

3 It’s all about access! Providing access via any piece of information a user might know:  An author’s name  A title  An editor’s name  A subject  Keywords 3

4 How?  Create bibliographic records  Bibliographic records in catalogs  Catalogs with features and function Indexing rules Display rules Navigation

5 Metadata  Metadata: “data about data”  Catalog records are metadata Library resource = Data Catalog record = Data about the resource = Metadata  Important: Consistency Standardization Using controlled vocabularies (thesauri)

6 6 “Why RDA?”  Evolving cataloging environment  RDA an improvement over AACR2 “Why don’t we just revise AACR2?”

7 7 The Cataloging Environment -- Internet  Catalogs are no longer in isolation Global access to data “linked data systems”  Integrate bibliographic data with wider Internet environment Share data beyond institutions Any user – any place – any time

8 8 Web front end Services VIAF Databases, Repositories LCSH The Cataloging Environment

9 RDA has a philosophical foundation: FRBR Functional Requirements for Bibliographic Records International collaboration Produced by IFLA Issued in 1997 Pushes us to a higher intellectual rigor 9

10 10 What do we really mean when we say “book”? “Book” Door prop (item) “publication” at bookstore any copy (manifestation) Cited from Patrick LeBoeuf, former chair of the IFLA FRBR Review Group

11 11 What do we really mean when we say “book”? “Book” – Who illustrated this? (expression) – Who wrote this? (work) Cited from Patrick LeBoeuf, former chair of the IFLA FRBR Review Group

12 The FRBR user tasks Find (a resource that meets certain criteria) Identify (make sure the resource is the one you want and not some other, similar resource) Select (from a number of possible resources, select the one that is most useful to you in your particular situation) Obtain (get it from its current location to a place where you can use it – gaining access to the resource) (navigate) (being able to make your way through a catalog, a search engine, a Web site to find what you want)

13 The FRBR Model An “entity-relationship” model – STEP 1: identify all the possible entities in the process you are analyzing. – STEP 2: Identify all the attributes that can be possessed by a particular entity. – STEP 3: Identify all the possible relationships that can exist between any two of your entities. Step 1 of the process identified 3 groups of entities.

14 Group 1, the Bibliographic Entities: the bibliographic “Great Chain of Being”  Work (the most abstract level) is realized through Expression is embodied in  Manifestation is exemplified by Item (the most concrete level)

15 WEMI (“work, expression, manifestation, item”) Work = a distinct creation Expression = the intellectual or artistic realization of a work Manifestation = physical embodiment of an expression of a work (i.e., the publication of a particular expression in book form) Item = a single exemplar of a manifestation (i.e., a single copy of a book)

16 The other groups of entities: Group 2: The “agent” entities – individual persons, corporate bodies. Group 3: The “subject” entities – concepts, events, places, etc., plus any of the Group 1 and Group 2 entities. Each entity is described by recording its attributes. Entities are linked to each other by relationships.

17 Leo Tolstoy in FRBR (the “linked data” model)

18 PERSON Tolstoy, Leo Russian novelist WORK Anna Karenina Novel WORK Voi ̆ na i mir Novel Created/Created By EXPRESSION War and peace (English translation) Created/Created by Is realized through PERSON Constance Garnett Role: literary translator Translated MANIFESTATION 1904 English edition of War and peace Is embodied in CORPORATE BODY William Heinemann Ltd. English publishing house Publishes ITEM Copy of Heinemann’s 1904 edition held by Harvard Library Is exemplified by

19 RDA – an overview What RDA is: a set of instructions on how to record bibliographic data What RDA is not: a display standard (RDA says nothing about how a record should be displayed on your screen; it says nothing about what data format to use)

20 RDA’s “world view” Bibliographic resources = carriers of content Content → intellectual Carrier → physical

21 Content maps to Work and Expression level Carrier maps to Manifestation and Item level

22 Moving from MARC to RDA MARC record structure is “flat” RDA envisions Linked Data Systems

23 AuthorTolstoy, Leo, graf, Uniform TitleVoĭna i mir. English Title War and peace / Leo Tolstoy ; translated from the Russian by Richard Pevear and Larissa Volokhonsky. Edition 1st ed. Published New York : Alfred A. Knopf, Description xviii, 1273 p. ; 25 cm. Bibliography Includes bibliographical references (p. [1223]-1247) and index. Subjects Russia -- History -- Alexander I, Fiction. Napoleonic Wars, Campaigns -- Russia -- Fiction. Related AuthorPevear, Richard, Volokhonsky, Larissa. ISBN

24 A new emphasis in RDA  Relationship designators  Identifiers 24

25 Relationship Designators (remember relator terms and codes?)  author  editor  translator  compiler  conductor  composer  performer 25

26 Relationship Designators in MARC: subfield $e  100 1_ Brown, Dan, $e author.  100 1_ Smith, Edward, $d $e compiler.  700 1_ Lee, Sandra, $d $e editor.  700 1_ Bernstein, Leornard, $d , $e conductor. in a Linked Data System:  the Designator is a data element of its own  could be expressed as a URL 26

27 Identifiers  definition: a character string uniquely associated with an entity (e.g. work, expression, person, corporate body, etc.) 27

28 RDA – Pathway to the Semantic Web in a Linked Data System: relationship designators + identifiers = more data manipulation by machines 28

29 In bib record for BBC video of Pride and Prejudice: conventional note: 500 __ Based on the novel by Jane Austen. (Humans can understand this, machines cannot)

30  In a linked data system: machines are able to interpret this. Record for BBC video. Identifier: 2abc15x Record for the work, Pride and prejudice by Jane Austen. Identifier: z345x1bc defined link: Is Adaptation Of

31 RDA is granular -- Data elements -- each element contains just one piece of data, of just one type. RDA’s structure is based on FRBR (no more Areas of Description as in AACR2) (go to RDA toolkit)

32 Helpful tools: RDA mappings Especially MARC Bibliographic to RDA, but also RDA to MARC Bibliographic Advanced search (icon: magnifying glass) AACR2 rule number search

33 Group exercise 1

34 THE CASE FR RDA Free Our Data! BY Bret Dee University of Versailles Tom D. Knot College of the Plains Cora Lee Sims Tia Smart IFLA Liberating Library Series PLAINS, MISSOURI The College of the Plains All Rights Reserved c2012 The College of the Plains ISBN: Printed on acid-free paper (Additional information: Title on cover: The case for RDA Pagination: xiv, 345 pages Illustrations: Screen shots in color, charts, 2 photographs Size: 23 1/2 x 16 cm Bibliography at the end of each chapter Index on pages )

35 Login to Connexion Browser

36

37 Group exercise 2, Emily Dickinson’s approving God (small groups)

38 38

39 Page facing title page (“series title page”) 19 th century American poets A series edited by Paul Everett Hanson University of Missouri, Columbia Volume 21 ISSN:

40 Title page verso First published in 1998 Second corrected edition, 2006 prepared by Jane Hutchinson ©1998, ©2006 ISBN:

41

42 RDA “pure”

43 43 RDA and Access Points for Names  Group 2 entities Persons (RDA Chapter 9) (Families) (RDA Chapter 10) Corporate bodies (RDA Chapter 11)  Group 3 entity Place names (RDA Chapter 16)

44 RDA – Authority records vs. Identity Records  Recording attributes “Core” = always record if available “non-Core” = not required, but a good idea to record if available  Identifying the “preferred name”  Establishing the authorized access point  Documenting the decision 44

45 RDA’s workflow for creating identity records  First, record all the available attributes For persons, see Chapter 9.2 through 9.18 (go to RDA Toolkit)  Then, determine which attributes are needed for establishing an “authorized access point” (“AAP”) AAP = “Preferred name” + additional attributes as instructed, see Chapter

46 “Identity records” and MARC  To accommodate RDA, the MARC format has added new fields: 370 (associated place) 371 (address) 372 (field of activity) 373 (associated group) 374 (occupation) 375 (gender) 377 (language) 46

47 47

48 AACR2 style 48

49 RDA style 49

50  For establishing a personal name, the important chapters are:  9.2. Name of the person  Constructing access points to represent persons  And chapters for any attributes we need for 1xx. Dates, fuller form of name, titles, etc. 50

51 What is the preferred name of the person?  The preferred name is the name by which the person is commonly known ( )  Names can be taken from any source ( ) BUT: There is an order of preference ( ): Preferred source of information (in AACR2, the “chief source of information,” i.e. title page) Other formal statements Reference sources 51

52 What is the name by which a person is commonly known? Possibilities:  Real name  Pseudonym  Title of nobility  Nickname  Initials  Other appellation 52

53 53

54 54

55 55 NAXOS

56 Other details 56

57  8.5 General guidelines on recording names: capitalization, numbers expressed as numerals or words, accents, hyphens, spacing of initials, abbreviations 57

58 Different forms of the same name ( ) – see special instructions  If it is known that the person prefers a name that is different from usage (i.e. form found on title pages), follow that preference.  Names in specific categories (e.g., Burmese): See additional instructions.  Name varies in fullness: choose the form most commonly found -- if no form predominates, use the latest form.  Language: Choose the form that is used in most resources. 58

59 – words, etc., indicating relationship  In Portuguese names, the words Filho, Junior, Neto, Netto, or Sobrinho are part of the surname.  Designations like Jr., Sr., II, III, are recorded as part of the preferred name (compare AACR2) They follow the given name and are preceded by a comma: Saur, Karl-Otto, Jr. 59

60 Step 3: Construct the authorized access point (AAP) (9.19)  Use the preferred name as the basis of the AAP.  Make additions as instructed in

61  If the name does not convey the idea of a person, add information even if not needed for differentiation ( ) Term that indicates profession or occupation: Stone Mountain (Writer) Term that indicates a fictitious or legendary character: Wolverine (Fictitious character) Term that indicates type, species or breed for non-human entities: Battleship (Race horse) 61

62 Title or other designation associated with the person ( ) Royalty (always): Charles, ǂ c Prince of Wales, ǂ d Nobility (always): Religious rank (if given name is first element and commonly appears with name): Mary Francis, ǂ c Mother, ǂ d Saint (add unless pope, emperor, empress, king, or queen): Hildegard, ǂ c Saint, ǂ d Spirit (always): Presley, Elvis, ǂ d ǂ c (Spirit) Other (if needed): Moses ǂ c (Biblical leader) 62

63 Date of Birth and/or Death ( )  Add if known (LC-PCC PS)  Use hyphens (LC-PCC PS) 63

64 Fuller Form of Name ( )  Add if needed to differentiate  If part of the forename or surname used is represented by an initial, add if important for differentiation (LC-PCC PS) Eliot, T. S. ǂ q (Thomas Stearns), ǂ d [today might not add the fuller form of name]  Add unused forenames or surnames only if needed for differentiation (LC-PCC PS) Richardson, Alan ǂ q (Alan John) 64

65 Period of activity of person and/or profession or occupation ( )  Add if needed for differentiation  Allen, Charles, ǂ d active 18th century-19th century  Butler, Jean ǂ c (Composer) 65

66 Other term of rank, honour, or office ( )  Add if needed to differentiate  Must have appeared with name  Wood, John ǂ c (Captain) 66

67 Other designation ( )  Add if needed to differentiate  Nichols, Chris ǂ c (Officer of the North Oxford Association) 67

68 PN summary (for typical names)  Preferred name  Always add dates when known  Add the following as needed, in this order of preference Fuller form of name Period of activity or Profession or occupation Other designation 68

69 Corporate names (11)  Same sources of information  Same process 69

70 Conventional names ( )  A conventional name is a name, other than the real or official name, by which a corporate body has come to be known. If a body is frequently identified by a conventional name in reference sources in its own language, choose this conventional name as the preferred name. 70

71  Governments. The conventional name of a government is the name of the area exercises jurisdiction. This can be a country, province, state, county, municipality, etc. 71


Download ppt "RDA Training Day MOBIUS Conference, Columbia, Missouri Wednesday, June 4, 2014 Presenters: Charles Croissant, Senior Catalog Librarian Pius XII Memorial."

Similar presentations


Ads by Google