1 / 102

RDA Special Topics: RDA Elements in Name Authority Records (NARs): MARC 21 fields

Ana Lupe Cristán Policy and Standards Division Library of Congress Revised August 2015. RDA Special Topics: RDA Elements in Name Authority Records (NARs): MARC 21 fields. 1. Overview. Context for expanding MARC to support RDA Parameters for adding new MARC fields

sarthurs
Download Presentation

RDA Special Topics: RDA Elements in Name Authority Records (NARs): MARC 21 fields

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. Ana Lupe CristánPolicy and Standards Division Library of Congress Revised August 2015 RDA Special Topics: RDA Elements in Name Authority Records (NARs):MARC 21 fields 1

  2. Overview • Context for expanding MARC to support RDA • Parameters for adding new MARC fields • Walk through the new MARC fields with emphasis on guidelines and best practices • Document updated with new MARC fields added as of April, 2015 • Note that at this time not all fields or subfields are active for use in name authority records contributed to the LC/NACO Authority File • Cataloger’s should check the latest Descriptive Cataloging Manual section Z1 and/or the LC Supplement to the MARC 21 Format for Authority Data 2

  3. Official documentation for MARC 21 fields http://www.loc.gov/marc/authority/

  4. LC/PCC documentation for exchange of MARC 21 fields – LC supplement to the MARC 21 Format …

  5. LC/PCC “best practices” documentation for use of MARC 21 fields – DCM Z1

  6. MARC 21 Format for Authority Data Enhanced in support of FRBR/FRAD attributes for use in RDA Future scenarios: Semantic Web Linked data New MARC 21 fields may be added to RDA coded name authority records (008/10=z). When recoding NARs from the previous rules these fields may be added at that time.

  7. Name Authority Records Name Authority Record (NAR) – Overview 7

  8. Name Authority Record MARC 21 Fields *001 – Control number *010 – Library of Congress control number (LCCN) 024 – Other standard number (ISNI, etc.) 034 – Coded cartographic mathematical data (Coordinates) *040 – Cataloging Source 046 - Dates *1XX - Name 336: Content type 368: Other corp. attributes; 370: Associated place; 371: Address; 372: Field of activity; 373: Associated group; 374: Occupation; 375: Gender; 376: Family information; 377: Language; 378: Fuller form of name; 380: Form of work; 381: Other characteristics; 382: Medium of performance; 383: Numeric designation; 384: Key; 385: Audience characteristics; 386: Creator/Contributor characteristics; 388: Time period of creation 8

  9. Name Authority Record MARC 21 Fields 4XX – See-From tracings (Name variants) 5XX – See-Also from tracings (Related authorized access point) 663 – Complex see-also reference 667 – Nonpublic general note 670 – Source data found 672 – Title Related to the entity 673 – Title Not related to the entity 675 – Source data not found 678 – Biographical or historical data 781 – Geographic subdivision 9

  10. 008/10 = z value "z" (Other) for use in 008/10 rules for RDA. 040 (Cataloging source) subfield $e = rda Must be used in combination with 008/10 to convey an eye readable notification of an RDA formulated name authority record. 4XX-5XX – “r” relationship designation in $i or $4 value used in control subfield $w position 0 Subfield $i – Relationship information – Use phrase or term from Appendix J or K of RDA Changes or new codes/subfields for use in NARs activated in 2010 10

  11. Name Authority Record Fixed Fields (008)

  12. 024 Other Standard Identifier (R) 046 Special Coded dates (R) 336 Type of Content [used only for expressions] (R) 368 Other Attributes of Person or Corporate Body (R) 370 Associated place (R) 371 Address (R) 372 Field of Activity (R) 373 Associated Group (R) 374 Occupation (R) 375 Gender (R) 376 Family Information (R) 377 Associated Language (R) 378 Fuller Form of Personal Name (NR) MARC 21 fields – in support of FRBR/FRAD and RDA 12

  13. 380 Form of Work (R) 381 Other Distinguishing Characteristics of Work or Expression (R) 382 Medium of Performance (R) 383 Numeric Designation of Musical Work (R) 384 Key (NR)386 - Creator/Contributor Characteristics (R) 388 - Time Period of Creation (R) 672 - Title Related to the Entity (R) 673 - Title Not Related to the Entity (R) 13

  14. New MARC 21 fields – Factoids Only 3 fields have defined indicators – in all of the other fields the indicators are undefined (blank) (024, 382, 388) All except for 046 and 378 have subfield $a All except for 024 have subfield $b defined Most have subfield $2 (Source) defined. Most have subfields $0 (Record control number) and $4 (Relator code) defined but these are not routinely used Most have subfields $6 (Linkage) and $8 (Field link and sequence number) defined but these are not used in the LC/NAF 14

  15. MARC 21 fields – LC/NAF Parameters All these fields are OPTIONAL The required fields for a name authority record are: 010, 040, 1XX, and a 670 subfield $a Use information that is readily available, research is not required beyond that needed for the name itself These fields are not regularly reviewed; however, if errors are noted LC may correct or remove the field(s) As with all NARs catalogers may update the existing fields or add additional fields as appropriate 15

  16. Name Authority Records MARC 21 fields – Best Practices 16

  17. Provide in numerical order by MARC 21 field Repeatable subfields may be repeated in the same field Repeat the field if a different source subfield $2 or different date parameters ($s or $t) apply to separate bits of information. Justify the information in the 046 and 3XX fields in one or more of the following fields: 670 – Source Found information Subfield $u - URI (electronic address of source of information) Subfield $v - Source of information MARC 21 fields – LC/NAF Best Practices 17

  18. 670 – Source Found information [RDA 26.9] Used to provide source data to enable matching with bibliographic record – used to justify 1XX, 5XX & 4XX Subfield $u – URI (Universal Resource Identifier) When citing information in a 670 found in an online site Added to the new MARC fields to link to source of information found in an online site in conjunction with $u Subfield $v - Source of information Add to new MARC fields when citing a resource that may or may not have a URI May be used in lieu of providing additional information in 670 MARC 21 fields – LC/NAF Best Practices - justification for 1XX, etc. - Sources 18

  19. NAR with only a 670 as justification for 1XX and additional information 040 ## $a DLC $b eng $e rda $c DLC 100 1# $a Deitz, Milissa 670 ## $a Watch this space, 2010:$b t.p. (Milissa Deitz) back cover (Dr. Deitz worked as a journalist for fifteen years before moving into academia full-time, she is a lecturer in Communication and Media Studies in the School of Communication Arts; PhD in Communication (2006) from the University of Sydney, a Master of Arts in Cultural Studies (1998) from Macquarie University and a Bachelor of Communication (1993) from the University of Newcastle) Examples: Sources 19

  20. Examples: Sources With 670 and new MARC fields added with information repeated: 040 ## $a DLC $b eng $e rda $c DLC 100 1# $a Deitz, Milissa • 370 ## $c Australia $e Sydney (N.S.W.) $e Newcastle (N.S.W.) $2 naf • 373 ## $a University of Sydney $2 naf $t 2006 • 374 ## $a Journalists $a Lecturers $2 lcsh • 670 ## $a Watch this space, 2010:$b t.p. (Milissa Deitz) flap (Dr Deitz worked as a journalist for fifteen years before moving into academia full-time, she is a lecturer in Communication and Media Studies in the School of Communication Arts; PhD in Communication (2006) from the University of Sydney, a Master of Arts in Cultural Studies (1998) from Macquarie University and a Bachelor of Communication (1993) from the University of Newcastle.) 20

  21. 040 ## $a DLC $b eng $e rda $c DLC 100 1# $a Deitz, Milissa 370 ## $c Australia $e Sydney (N.S.W.) $e Newcastle (N.S.W.)$2naf $v Watch this space, 2010 373 ## $a University of Sydney $2naf $t 2006 $v Watch this space, 2010 374 ## $a Journalists $a Lecturers $2 lcsh $v Watch this space, 2010 670 ## $a Watch this space, 2010:$b t.p. (Milissa Deitz) Example of using subfield $v to show additional information in 37X fields instead of in $b of 670 21

  22. 040 ## $a DLC $b eng $e rda $c DLC 100 1# $a Deitz, Milissa 370 ## $c Australia $e Sydney (N.S.W.) $e Newcastle (N.S.W.) $2 naf $v University of Western Sydney, June 18, 2012 $uhttp://www.uws.edu.au/hca/school_of_humanities_and_communication_arts/key_people/academic_staff_directory/doctor_milissa_deitz 374 ## $a Journalists $a Lecturers$2 lcsh $v University of Western Sydney, June 18, 2012 $u http://www.uws.edu.au/hca/school_of_humanities_and_communication_arts/key_people/academic_staff_directory/doctor_milissa_deitz 670 ## $a Watch this space, 2010:$b t.p. (Milissa Deitz) Example of using subfield $u to show information in 37X fields instead of adding another 670 Information found at the University of Western Sydney’s web site – $v and $u with URI added; not necessary to also add as 670. 22

  23. Source of the information – Things to remember There are 3 mechanisms to provide source citations in NARs: 670 Sources found $u Uniform Resource Identifier (in 670 or 3XXs) $v Source of information (in 3XXs only) LC/PCC requires the use of a 670 with subfield $a [title proper, date of publication] and $b [location where the information was found (form of the name of the 1XX or 4XX as found in source)] to justify information in 1XX, 5XX, etc. Subfield $u may be added to a 670 if the source being cited has a URI 23

  24. Source of the information – Things to remember Catalogers may provide information in a 670 and also provide the information in the 046 and 3XX fields When providing information in the 046 or 3XX field taken from the 670 it is not necessary to add a $u or $v to these fields Use subfield $u for the URI to cite an electronic resource in combination with the subfield $v for the title of the source Some 3XX fields do not require justification for information supplied (e.g., 375, 377, 380) 24

  25. Source of the information – Things to remember Use subfield $v when citing the title of a source that is not electronic or in conjunction with the $u Attributes about the entity generally cited in the 670 can be supplied in the 046 and 3XX fields and justified by a subfield $v. It is not necessary to repeat information in the 670 Previous example repeated to show 670 $v citation: 100 1# $a Deitz, Milissa370 ## $c Australia $e Newcastle (N.S.W.) $2 naf $v Watch this space, 2010373 ## $a University of Sydney $2 naf $t 2006 $v Watch this space, 2010374 ## $a Journalists $a Lecturers $2 lcsh $v Watch this space, 2010 375 ## $a female377 ## $a eng 670 ## $a Watch this space, 2010:$b t.p. (Milissa Deitz) 25

  26. 046 – Special coded dates (R) - MARC Indicators: Not defined Subfields $f Birth date (NR) $g Death date (NR) $k Beginning or single date created (Work) (NR) $l Ending date created (Work) (NR) $q Establishment date (NR) $r Termination date (NR) $s Start period (NR) $t End period (NR) $u URI (R ) $v Source of information (R) $2 Source of date scheme (NR)

  27. 046 – RDA Element – RDA Number $f Birth date 9.3.2 $g Death date 9.3.3 $k Beginning or single date created (Work) 6.4 $k Beginning or single date created (Expression) 6.10 $l Ending date created (Work) 6.4 $l Ending date created (Expression) 6.10 $q Establishment date 11.4 $r Termination date 11.4 $s Start date for period of activity 9.3.4 $s Start date for Date associated with family 10.4 $s Start date for Date associated with corporate body 11.4 $t End date for Period of activity 9.3.4 $t End date for Date associated with family 10.4 $t End date for Date associated with corporate body 11.4

  28. 046 – Form of date (edtf) As of August 2015 LC/PCC will adopt using the Extended Date/Time Format (edtf) for dates as appropriate 28

  29. Examples 046 – Dates – edtf 046 ## $f 1931 $2 edtf 100 1# $a Munro, Alice, $d 1931- 046 ## $f 1899 $g 1961 $2 edtf 100 1# $a Hemingway, Ernest, $d 1899-1961 046 ## $f 1936-05-05 $2 edtf 100 1# $a Smith, John, $d 1936 May 5- 046 ## $f 1936-10-05 $g 2011-12-18 $2 edtf 100 1# $a Havel, Václav 046 ## $f 1936-10 $2 edtf 100 1# $a Cooper, John, $d 1936- 29

  30. Examples 046 – Dates – edtf 046 ## $s 1977 $2 edtf 110 2# $a Double Image (Musical group : 1977-) 046 ## $s 1989 $2 edtf 110 2# $a Double Image (Musical group : 1989-) 046 ## $s 1980 $t 2011 $2 edtf 110 2# R.E.M. (Musical Group) 046 ## $s 1925 $t 1979 $2 edtf 100 3# $a Pahlavi (Dynasty : $d 1925-1979) 30

  31. 046 – EDTF date scheme Provide ‘edtf’ in 046 subfield $2 31

  32. 336 – Content Type (R) Indicators: Not defined Subfields $a Content type term (R) $b Content type code (R) $2 Source [of term or code] (NR) $3Materials specified (NR) 32

  33. 336 – RDA Element - RDA Number Content type 6.9 Example: 336 ## $a performed music $2 rdacontent 33

  34. 336 – Content Type Use content type terms from RDA 6.9 Use subfield $2 to note the source of term ($2 rdacontent) Do not repeat $a – repeat 336 field Used only for expressions (not works) This field can be applied to AACR2 NARs but: You do have to know the difference between a work and an expression as defined by FRBR - You must have access to the RDA Toolkit or RDA print in order to find the right term – or use list on the MARC website at: http://www.loc.gov/standards/valuelist/rdacontent.html 34

  35. 368 – Other Corporate Body Attribute (R) Indicators: Not defined Subfields $a – Type of corporate body (R) $b – Type of jurisdiction (R) $c – Other designation (R) $d – Title of person (R) $d – Start period (NR) $s – End period (NR) $2 – Source [of term] (NR) 35

  36. 368 – RDA Element – RDA Number Other Designation Associated with the Corporate Body 11.7

  37. 368 – Other corporate body attribute Record the attribute in English Use a general (suitable or appropriate) designation for a corporate body. LC/PCC prefer a term from an authorized vocabulary Record the type of jurisdiction for a place name in English unless there is not an equivalent term (e.g., Duchy, Regierungsbezirk, Voivodeship)

  38. 368 – Other Corporate Body Attribute Examples: 110 2# $a I.M. Pei & Associates 368 ## $a Architectural firms $2 lcsh 110 2# $a McGuire, Woods, Battle & Boothe 368 ## $a Law firms $2 lcsh 110 2# $a Barenaked Ladies 368 ## $a Musical groups $2 lcsh 151 ## $a Buenos Aires (Argentina : Province) 368 ## $b Province 151 ## $a Nayarit (Mexico) 368 ## $b State

  39. 370 – Associated Place (R) Indicators: Not defined Subfields $a - Place of birth (NR) $b - Place of death (NR) $c - Associated country (R) $e - Place of residence or headquarters (R) $f - Other associated place (R) $g - Place of origin of work (R) $s - Start period (NR) $t - End period (NR) $u - URI (R) $v – Source (R) $2 – Source of term (NR)

  40. 370 – RDA element – RDA number $a - Place of birth 9.8 $b - Place of death 9.9 $c – Place associated with the person (country) 9.10 $c – Place associated with the family (country) 10.5 $c – Location of headquarters (country) 11.3.3 $e – Place of residence (city, state, country) 9.11 $e – Place associated with the family (city, state, country) 10.5 $e – Location of conference (city, state, country) 11.3.2 $e – Location of headquarters (city, state, country) 11.3.3 $f – Other place associated with a family 10.5 $f – Other place associated with a corporate body 11.3.3 $g - Place of origin of work 6.5 40

  41. 370 – Associated Place The name is recorded in the authorized access form if found in the LC/NAF with subfield $2 added Example: 151 Paris (France) [name established in the LC/NAF] 370 ## $a Paris (France) $2 naf 151 Santana (São Paulo, Brazil) [name established in the LC/NAF] 370 ## $a Santana (São Paulo, Brazil) $2 naf It is not necessary to create a NAR if the place name is not already established, but you must record it in the form that would be used to establish it. Example: 370 ## $a Waelder (Tex.) 370 ## $b Flatonia (Tex.) $2 naf [Place of birth for a person is Waelder, Texas – the name is not found in the LC/NAF; place of death is Flatonia, Texas – name found in LC/NAF]

  42. Example 370 – Associated Place Example: 100 1# $a McCain, John, $d 1936- 370 ## $a Coco Solo Naval Air Station (Canal Zone) 370 ## $c United States $2 naf [U.S. Senator from Arizona born in Panama Canal Zone; associated country: U.S. – not Panama] Example: 100 1# $a Díaz, Porfirio, $d 1830-1915 370 ## $a Oaxaca de Juárez (Mexico)$b Paris (France) $c Mexico $2 naf [Ex-President of Mexico; born in Mexico; died in France; associated country: Mexico]

  43. 371 – Address (R) Indicators: Not defined Subfields $a - Address (R) $b - City (NR) $c – Intermediate jurisdiction (NR) $d - Country (NR) $e – Postal code (NR) $m – Electronic mail address (R) $s - Start period (NR) $t - End period (NR) $u - URI (R) $v - Source (R) $z – Public note (R)

  44. 371 – RDA Element – RDA Number Address of the Person 9.12 Address of the corporate body 11.9

  45. 371 - Address Each address is recorded in a separate 371 field For a person: the address of a person's place of residence, business, or employer and/or an e-mail or Internet address. For a corporate body: the address of the corporate body's headquarters or offices, or an e-mail or Internet address for the body. Distinction between field 371 (Address) and field 370 (Associated place): Field 370 (Associated place) includes information about places associated with a person or a corporate body at the level of the country, the town, etc. Field 371 (Address) contains information relating to the specific address of a corporate body. The place at which the business office can be found or reached (e.g., mailing address, e-mail, etc.).

  46. 372 – Field of Activity (R) Indicators: Not defined Subfields $a - Field of activity (R) $s - Start period (NR) $t - End period (NR) $u - URI (R) $v - Source of information (R) $0 - Record control number (R) $2 - Source of term (NR)

  47. 372 – RDA Element - RDA number $a - Field of activity of the person 9.12 $a – Field of activity of the corporate body 11.9

  48. 372 – Field of Activity Term represents a discipline not an occupation Term in English First letter of term capitalized Examples: 100 1# $a Frost, Robert, $d 1874-1963 372 $a Poetry $2 lcsh 100 1# $a Will, George F. 372 $a History $a Politics $2 lcsh

  49. 373 – Associated Group (R) Indicators: Not defined Subfields $a - Associated group (R) $s - Start period (NR) $t - End period (NR) $u - URI (R) $v - Source of information (R) $0 - Record control number (R) $2 - Source of term (NR) In RDA this attribute is called Affiliation (9.13) or Associated Institution (11.5) Started out as only used to show association between a person and an affiliated body. Redefined to show information about a group, institution, association, etc., that is associated with the entity in the 1XX.

  50. 373 – RDA Element – RDA number $a – Affiliation 9.13 Associated Institution 11.5

More Related