A Refresher and What’s New(ish) RDA/MARC21 A Refresher and What’s New(ish) Introduce Self I’m going to provide a brief overview of RDA – Resource Description and Access and MARC 21 Format for bibliographic data, and how we use the RDA standards within the format structure of MARC21. Michele (Shelly) Sandstrom Cataloging Librarian Naperville Public Library msandstrom@Naperville-lib.org 630-637-6138

AACR via MARC Before we proceed to talk about RDA and it’s usage with MARC 21 format, I’ll step back a bit to discuss what came before RDA – AACR Anglo-American Cataloguing Rules (AACR) using ISBD punctuation were an international library cataloging standard that provided detailed information on how to record bibliographic information. Librarians followed the rules to compose the bibliographic description of a library item. This "description" is shown in the paragraph sections of a card. It includes the title, statement of responsibility, edition, material specific details, publication information, physical description, series, notes, and standard numbers. In order to use the bibliographic information in a computerized setting, the information from a catalog card couldn’t simply be typed into a computer. The computer needed a means of interpreting the information found on a cataloging record. The MARC record contains a guide to its data, or little "signposts,“ – tags, delimitors, indicators, etc. , before each piece of bibliographic information. MARC format was designed to take the information from a catalog card and make it machine readable, as well as person readable. MARC was developed to “fit” information devised using AACR standards.

RDA History Bibliographic records in RDA aim to be more relevant in an online environment by enabling catalogs to cluster related records. RDA was officially released June 23, 2010 MARC 21 format changed to accommodate Resource Description and Access (RDA) with regular updates to accommodate RDA additions and changes. Over a very long period of time, through many models and meetings and steering committees, RDA was developed. RDA provides a set of guidelines and instructions on recording data that is meant to more easily and flexibly use data in a relational database, linked data – in other words online - setting. Eventually RDA was released in 2010. Libraries had their data being used and shared via MARC format MARC has been updated and changed over time to better accommodate the new RDA standards.

But sometimes it’s felt like this Using a standard intended for an online relational database environment in a format (MARC) intended to be used for individual records modeled after catalog cards (ISBD and AACR2) has proved challenging. Discussion about what formats will be used by libraries in the future is ongoing. Some predict we are heading toward a MARC free format, using more flexible and extensible schemas and formats such as OWL, JASON, MODS or Dublin Core In the meantime MARC21 Format for Bibliographic data is the means we use to identify and access to the materials we provide.

What makes a MARC 21/RDA Record ? What are the differences between an AACR2 and an RDA bibliographic record? How are those differences represented in MARC 21 Format for Bibliographic Data?

Preferred Sources of Information General Guidelines Anywhere on the resource, including housing, containers, accompanying material Can be taken from other sources, usually have it in square brackets include a note in the record RDA 2.2 Covers the preferred sources of information to consult when constructing a bibliographic record. Basically can find the information anywhere on the resource, including housing, containers and accompanying material. However for specific materials, there are preferred sources:

or image of (pdf, microfform) title page, title sheet, or title card Manifestation Preferred Source book, periodical, sheet, or image of (pdf, microfform) title page, title sheet, or title card moving images title frame or frames, or title screen or screens ; alternative, label with a title other manifestations In this order : label, internal source, container or accompanying material no identifying info. on manifestation In this order: accompanying material, other published descriptions, other available source RDA 2.2.2.2- 2.2.2.4 Review slide If taking information from outside the source, need to make a note to that effect, or supply information in brackets. Do this for title, statement of responsibility, edition, production/distribution/publication informationa, series statements, numbering of series.

Transcribed information = "Take what you see" and "accept what you get Represent the resource the way it represents itself. This is a shift away from AACR2's rules on abbreviations, capitalization, punctuation, numerals, and symbols, and on the correction of data that is known to be incorrect, such as typos. General guidelines in 1.7.1 (and appendices A (capitalization) and B (abbreviations) RDA 1.7.1 and appendices A (capitalization) and B (abbreviations) covers transcribing information. Take what you see and accept what you get There are exceptions/elaboration that can be found in the specific examples in 1.7.1 and the appendices

How to Identify/Signify an RDA MARC Record Leader Desc = i - for ISBD punctuation 040 ^^  HHO |b eng |e rda HHO If you are creating or identifying an MARC21 Bibliographic record you supply or look for : The field defines who created and updated the record. A new practice with RDA is recording the language of cataloging and the description conventions. Pipe b is for the language used by the cataloging agency = eng Pipe e is for the cataloging instructions used = rda Both subfields are not required.

Title Differences Institutional choice on how to transcribe AACR2 style (Capitalize first word and proper nouns) Title case as it appears Full caps as it appears Some other variation RDA 1.7 245 14 The story of Venus and Serena Williams 245 14 The Story of Venus and Serena Williams

300 ^^ 265 pages :|b color illustrations ; |c 24 cm Almost Never Use Abbreviations Except When Transcribing From the Source 300 ^^ 265 pages :|b color illustrations ; |c 24 cm Exceptions: (RDA B.2 – B.6) measurements using metric symbols, e.g. cm names of agents and places, e.g. Wm. abbreviations in a title of work that are integral parts RDA 1.7.8 Generally do not use abbreviations, unless the abbreviations are found on the source being cataloged Exceptions: See slide – there are more than listed here

Relationship Designators and Relator terms 1xx/7XX |e relator term Include a relationship designator for all creators, whether they are coded MARC 1XX or MARC 7XX. (PCC) Most commonly used terms are author, composer, narrator, producer, publisher, performer, singer Consult RDA Appendix I for relator terms A relationship designator indicates the nature of a relationship between entities represented by authorized access points, descriptions, and/or identifiers Is mapped to 1XX and 7XX |e – relator term Rather than using a relator code from the MARC list, we know use relator terms that come from RDA Appendix I Most commonly used terms are: author, composer, narrator, producer, publisher, performer, singer,

No ‘Rule of Three’ in Listing Contributors 245 10 |a Around the world /|c by Joe Smith, Rupert Jones, Ellie Morse, Wanda Gregg and Louise Adams. 100 field for first author, and 700 fields for additional authors. Transcribe a statement of responsibility as it appears on the source of information Optional Omission ; can abridge if can be done without loss of information, don’t use mark of omission (…) or et. al. [and 4 others] There is no longer a “rule of three” in listing contributors. RDA 2.4.1.1 All contributors may be included in 245$c and 1xx/7xx fields Optional Omission Abridge a statement of responsibility only if this can be done without loss of essential information. Do not use a mark of omission (…) to indicate such an omission. Always record the first name appearing in the statement. Can use [and 4 others]

Transcribe Exact Edition as found in Source 250 ^^ First edition 250 ^^ Revised and updated edition RDA 2.5.1.4 This is a repeatable field

264 ^4 | Copyright date Use © and Ⓟ symbols Publication, Manufacturing, Distribution, and Copyright statements go in 264 field , distinguished by 2nd indicator 264 ^0   Production             264 ^1   Publication             264 ^2   Distribution            264 ^3   Manufacture 264 ^4   | Copyright date Use © and Ⓟ symbols RDA 2.7 Record first publishing location, even if it is not in the cataloger’s country; optionally include multiple locations. (2.8.2) Transcribe publisher and location as found in source; add state or nation in square brackets if needed for identification. Infer that publication is same as copyright 264 ^0   Production             is for unpublished works 264 ^1   Publication             infer from copyright date 264 ^2   Distribution            date can be based on container artwork date 264 ^3   Manufacture 264 ^4   |c Copyright date   always use if word/symbol on item ; multiple copyright dates may be recorded  

Publisher, Place of Publication, Date of Publication Unknown 264 1^ [United States] :b[Publisher not identified],|c[21??] If the place of publication is uncertain, supply a probable place, if can’t determine a location use Place of publication not identified. If the publisher cannot be identified from the piece itself, and can’t be identified from other sources, use Publisher not identified. If date of publication is not identified, supply an approximate date of publication. If can’t determine an approximate date, record Date of publication not identified. 2.8.4.7 No Publisher Identified Record publisher not identified if: no publisher is named within the manifestation itself and the publisher cannot be identified from other sources 2.8.2.6 Probable Place of Publication If the place of publication is uncertain, supply the name of the probable local place of publication. Include the name of the larger jurisdiction if necessary for identification. If only the local place name is supplied, follow it with a question mark Record Place of publication not identified if neither a known nor a probable local place or country, state, province, etc., of publication can be determined 2.8.6.6 If a date of publication is not identified in a single-part manifestation, supply the date or approximate date of publication If an approximate date of publication for a single-part manifestation cannot reasonably be determined, record date of publication not identified. Indicate that the information was taken from a source outside the manifestation itself

The GMD is No Longer Used 245 |h [videorecording] It has been replaced with: 336 Content type 337 Media type 338 Carrier type The General Material Designation from AACR2 has been replaced by

336 ^^|a text|b txt|2 rdacontent |a Type of content – list of terms in RDA at 6.9.1.3 |b Content type code – list of content terms and codes http://www.loc.gov/standards/valuelist/rdacontent.html |2 Source http://www.loc.gov/standards/sourcelist/genre-form.html |a Record the type of content contained in terms from list in RDA at ( 6.9.1.3) e.g. text, spoken word, two-dimensional moving image. |b Records Content type code - From LC list of content terms and codes http://www.loc.gov/standards/valuelist/rdacontent.html  e.g. txt, spw, tdi |2 Records source rdacontent Find in LC Genre/Form Code and Term Source Codes  http://www.loc.gov/standards/sourcelist/genre-form.html

337 ^^ |a unmediated|b n|2 rdamedia |a Type of media – list of terms in RDA at 3.2.1.3 |b Media type code – list of content terms and codes http://www.loc.gov/standards/valuelist/rdamedia.html |2 Source – LC term source codes http://www.loc.gov/standards/sourcelist/genre-form.html |a Records Media type term Record the type of media contained in terms from list in RDA at (3.2.1.3) e.g. unmediated, audio, video |b Records Media type code – e.g. n, s or v From LC list of content terms and codes http://www.loc.gov/standards/valuelist/rdamedia.html |2 Records source rdamedia Find in LC Genre/Form Code and Term Source Codes  http://www.loc.gov/standards/sourcelist/genre-form.html

338 ^^ |a volume|b nc|2 rdacarrier |a Type of media – list of terms in RDA at 3.2.1.3 |b Media type code – list of content terms and codes http://www.loc.gov/standards/valuelist/rdamedia.html |2 Source – LC term source codes http://www.loc.gov/standards/sourcelist/genre-form.html |a Records Carrier type term Record the type of carrier contained in terms from list in RDA at (3.3.1.3) e.g. volume, audio disc, videodisc |b Records Carrier type code - e.g. nc, sd, vd     From LC list of carrier terms and codes http://www.loc.gov/standards/valuelist/rdacarrier.html |2 Records source rdacarrier Find in LC Genre/Form Code and Term Source Codes  http://www.loc.gov/standards/sourcelist/genre-form.html

344 ^^ Sound characteristics 346 ^^ Video characteristics ? 34x fields are used to describe particular characteristics of some forms of media. 340 ^^ Medium 344 ^^ Sound characteristics 346 ^^ Video characteristics 347 ^^ Digital Characteristics 340 Physical medium |b Dimensions 344 Sound characteristics |a Type of recording (digital) |2 Source code (rdatr) |b Recording medium (optical) |2 Source code (rdrm) |g Configuration of playback channels (stereo)|2 Source code (rdapc) |h Playback characteristics (Dolby) 346 Video characteristics |a format from the list at 3.18.2.3 ; If none of the terms in the list is appropriate or sufficiently specific, use another concise term to indicate a video format.  e.g DVD |b Record a broadcast standard Use term from list at RDA 3.18.3.3  e.g. NTSC 347 Digital characteristics |a Record a file type. Use one or more appropriate terms from list RDA 3.19.2.3 - video file |b Record an encoding format  - RDA 3.19.3.3 e.g. Blu-ray |d Record a resolution if it can be readily ascertained - RDA 3.19.5 e.g. 1080p high definition |e Record a regional encoding using terms from the list at RDA 3.19.6.3 - e.g. region 1 |2 Use source code rdare 344 ^^ digital|boptical|hDolby digital plus 5.1|2 rda

OCLC Bib Formats and Standards newest guideline for the 344 and 347 fields is “Prefer use of a separate field for each unique term.” 344 ^^ digital $2 rdatr 344 ^^ $b optical $2 rdrm 344 ^^ $g stereo $2 rdapc 344 ^^ $h Dolby digital 5.1 |2 Source - under new OCLC guidelines, each unique term  is an individual field, and each requires a |2 Source if one exists at http://www.loc.gov/standards/sourcelist/genre-form.html Each unique term  is an individual field, and each requires a |2 Source if one exists at http://www.loc.gov/standards/sourcelist/genre-form.html

Relationship Information 7XX fields: $i – Relationship information LCPS : First word is capitalized, and the subfield ends with a colon. RDA 24.5.1.1 Relationship information is provided 24.5.1.1 A designator that indicates the nature of a relationship between entities represented by authorized access points, descriptions, and/or identifiers. A relationship designator is recorded with the authorized access point, identifier, and/or description representing the related work, expression, manifestation, or item. This is represented in a 7xx field with a |I indicating the relationship Examples : translations, based on, older editions. 700 1^ $i Translation of: $a Arrupe, Pedro, $d 1907-1991. $t Aqui me tienes, Senor.

|0 – Authority record control number or standard number 710 2^ |aCalifornia Poets in the Schools (Project),|eissuing body|0http://id.loc.gov/authorities/names/n85319780$1http://id.loc.gov/rwo/agents/n85319780 |1 – Real World Object URI 100 1^ |aObama, Michelle,|d1964-|0http://id.loc.gov/authorities/names/n2008054754$1http://viaf.org/viaf/81404344 Subfield $0 contains the system control number of the related authority or classification record, or a standard identifier such as an International Standard Name Identifier (ISNI). These identifiers may be in the form of text or a Uniform Resource Identifier (URI). If the identifier is text, the control number or identifier is preceded by the appropriate MARC Organization code (for a related authority record) or the Standard Identifier source code (for a standard identifier scheme), enclosed in parentheses. When the identifier is given in the form of a Web retrieval protocol, e.g., HTTP URI, no preceding parenthetical is used. Subfield 1 was created in 2017 contains a URI that identifies an entity, sometimes referred to as a Thing, a Real World Object or RWO, whether actual or conceptual.

MARC 21 Fields created for RDA 046 Special coded dates Associated Language Form of Work 382 Medium of Performance

Core elements for Monographs MARC Tag Title 245 |a Statement of Responsibility 245 |c Edition Statement 250 # of Serials 245|n Publication Statement 264 1^ Distribution Statement 264 2^ Manufacture Statement 264 3^ Copyright Date 264 4^ Series Statement 490 Carrier type 338 Extent 300 |a Core elements

RDA Update History (at end of TOC) MARC 21 Updates RDA Update History (at end of TOC) MARC 21 Updates In MARC 21 Format for Bibliographic Data, the date of update in the header of each Field. RDA Updates are listed in RDA Update History at the end of the Table of Contents. Has been updated yearly from 2012-2017. Update No. 26 (April 2018) are displayed in red print. The date located in the header of the full version of each field indicates the last month and year of update. http://www.loc.gov/marc/bibliographic/

RDA Toolkit Beta Site – What’s Next? The Toolkit debuted in 2010 … a site redesign to adjust to changes to the online environment. 3R Project = RDA Toolkit Restructure and Redesign. The beta phase of the new Toolkit will end when RSC and ALA Publishing agree that the revision of content and structure is complete and the RDA Board approves the replacement of the original Tookit with the new version. Work in progress…

Questions???