Recording the Attributes of Series MARC21 in NACO RDA Series Authority Records Welcome back. Module 3b

Remember the new fields list? Fields in green can be used for Series 375 376 377 (Series) 378 380 (Series) 381 (Series) 382 383 384 046 (series) 336 (series) 368 370 (series) 372 373 374 Next we are going to highlight most likely uses of new MARC fields for series authority records. These new fields will be used to record the other work and expression level attributes covered in Chapter 6 of RDA.

New field: 046: Special Coded Dates (R) RDA 6.4 and 6.10 No indicators Subfields $k – Beginning or single date created (NR) For a work, earliest date (normally the year) associated with a work; that date may be the date the work was created or first published or released. $l – Ending date created (NR) Ending date of the date range for which the beginning date is recorded in $k. The 046 field is used to record the Attributes Date of Work and Date of Expression found in RDA 6.4 and 6.10. As you remember from using this field in NARs, there are no indicators to code. The subfields k and l (el) can be used to record the beginning and ending dates of a series. Dates like this might also be recorded in the 640 field – Series Dates of Publication and/or Sequential Designation. Remember the Dates of Publication are what we will most often use to infer the dates of the work.

046 Justification – PCC practice! 670 field $u Uniform Resource Identifier (R) $v Source of information (R) See DCM Z1 046 PCC practice for recording sources $2 Source of date scheme (NR) - There is no need to use $2 if you are using the default ISO 8601 YYYYMMDD format. - $2 edtf is used for questionable dates (Extended Date/Time Format) Justification (source is core, remember) follows the pattern you learned about in the training with Paul and Melanie. The 670 may be the source, in which case you don’t have to code anything special in the 046 field. DCM Z1 for the 046 has the PCC practice for using the delimiter u and the delimiter v for all fields where they are defined. Here are the points: 1.  670s must be used to support information used as part of a heading in 1XX and 4XX. 2.  For 046, 37X, 381: a. use of delimiter v is optional if the same information/source is already cited in the 670  b. use delimiter v if the information/source is not cited in a 670 c. use of delimiter u is optional, and should always be preceded by delimiter v. The YYYY part of the ISO 8601 standard will be most often used. If the dates are questionable, remember to use the Extended Date/Time Format code edtf in the $2.

046: Special Coded Dates: Example _0 Masculin-féminin dans l'Europe moderne. $p Série XVIIe siècle 642 1 $5 DPCC $5 GU Madame de Murat et la "défense des dames," 2012: $b series title page (Masculin/féminin dans l'Europe moderne. Série XVIIe siècle) 046 _ _ $k 2012 Here is an example showing the Authorized Access Point for a series which began with number 1 in the year 2012. So we would use the $k to record that beginning date in the 046. And we wouldn’t need a justification other than what’s already provided in the 642 and 670 fields.

046: Special Coded Dates: Examples Series with volume 1 published as the May 31, 2012 issue of a quarterly publication 046 _ _ $k 20120531 Questionable? 2010? = 046 _ _ $k 2010? $2 edtf Remember oddities of ISO standard If you have year and month only 046 _ _ $k 2012-05 Here are a few other less common examples. The use of month and day along with the year, (PAUSE) a questionable date with the $2 edtf, (PAUSE) and a reminder about ISO standard peculiarities.

New Field: 336: Content Type (R) (Do not supply at this time – Pending) No indicators Subfields $a Content type term (R) $b Content type code (R) $2 Source (NR) – identifies the source of the term or code - Always use $2rdacontent $3 Materials specified (NR) – part of the described materials to which the field applies RDA 6.9 Let’s look at the 336 field even though DCM Z1 currently instructs us not to supply this data pending the outcome of a report and/or recommendations from the PCC Access Point for Expressions Task Group. From RDA instructions we know that Content Type reflects the fundamental form of communication in which the content is expressed and the human sense through which it is intended to be perceived. The field 336 is used and a term, a code, or both can be recorded. The terms and codes come from a formal list, and you should always use the $2 rdacontent to justify the $a and $b information.

Term and Code List for RDA Content Types http://www. loc Terms and codes can be found in the Term and Code List for RDA Content Types list. Note that the first column is the content term and would be used in the 336 $a. And the matching codes are in the second column for the 336 $b. The third column helps you recognize appropriate usage by referencing the bibliographic leader.

Definitions in RDA table 6.1 (see 6.9.1.3 Recording Content Type RDA has a table at 6.9.1.3 of the terms and definitions of those terms. There are also examples to help illumine when each term can be used. For instance, cartographic image has the examples maps, views, and remote-sensing images.

336: Content Type: Example 100 1_ Beethoven, Ludwig van, $d 1770-1827. $t Sonatas, $m piano (Unicorn Records (Firm)) _ _ Beethoven, L. van. Piano sonata no. 3, op. 2, no. 3 [SR] p1969: $b container (Beethoven sonatas; The complete Beethoven sonatas) 336 _ _ $a performed music $b prm $2rdacontent Here is an example of a series with sound recordings of Beethoven sonatas. The 336 is given a $a for performed music and a $b prm from the Term and Code List for RDA Content Types list. And the $2 is coded as well.

336: Content Type: Example 110 1_ $a Indiana. $b Geological Survey. $t Petroleum exploration map 336 _ _ $a cartographic image $b cri $2 rdacontent Here is another example. Remember that you must always note the source as rdacontent.

New Field: 370: Associated Place (R) RDA 6.5 No indicators Subfields $g Place of origin of work (R) – country or other territorial designation from which a work originated $s Start period (NR) $t End period (NR) The 370 field is used to record the Attribute: Place of Origin. RDA 6.5.1.1 tells us the Scope: Place of origin of the work is the country or other territorial jurisdiction from which a work originated. MARC 21 tells us the Field definition and scope: A town, city, province, state and/or country associated with persons, corporate bodies, families, works, and expressions. For a work or expression: The country or other territorial jurisdiction from which a work or expression originated. $g is used to record the jurisdictional information. $s and $t can be used to indicate start and end dates. Of course, this is usually recorded in the 643 field too.

370 Justification 670 Subfields $u Uniform Resource Identifier (R) $v Source of information (R) $2 Source of term (NR) – source of codes for associated country or place We have the familiar justification/source options. Remember the PCC instructions concerning the 670, delimiter u, and delimiter v.

Subject Heading and Term Source Codes http://www. loc There is a list called Subject Heading and Term Source Codes so that you can indicate the source of the information you input. By convention, the information in 370 is expected to come from NAF, so it’s not required to tell the source unless it comes from another thesaurus.

370: Associated Place: Example $a Chicago $b Windy City Pub. $d 2002- 643 $a Omaha $b Heartland Press $d 1989- 2001 370 _ _ $g Chicago, Ill. $s 2002 370 _ _ $g Omaha, Neb. $s 1989 $t 2001 The Place of origin in this series example has changed. Since the 370 is repeatable, you can list each associated place with the dates separately for clarity. Remember from the NAR training, that the authorized form of the place is used with the form modified to remove the parentheses. If the place has not been established, you do not need to establish it. But do input in the way the heading would likely be established.

New Field: 377: Associated Language (R) RDA 6.11 2nd indicator 7 specifies that an alternate source of code is indicated in $2 Subfields $a Language code (R) – identifies the language used for publication or in which a work is expressed $l Language term (R) $2 Source of code (NR) - If using the MARC Code List, $2 is left blank The 377 field is for the Attribute: Language of Expression. Note that we will use a 7 in the second indicator to indicate that the source of the language code is in the $2. But, if you are using a code from the MARC Code List for Languages which is the default source, the second indicator and $2 should be left blank.

377: Associated Language: Example 100 1_ DiTerlizzi, Tony. $t Beyond the Spiderwick chronicles 643 _ _ New York $b Simon & Schuster Books for Young Readers _____________________________________ 100 1_ DiTerlizzi, Tony. $t Beyond the Spiderwick chronicles (Simon & Schuster Audio (Firm)) 377 _ _ $a eng $l English Here is an example where we could use the 377 field. The second series is a Simon & Schuster audio book expression of the Simon & Schuster series originally appearing in print. The language of expression could be coded even though it isn’t a translation.

377: Associated Language: Example 130 _ _ $a Trudy Matematicheskogo instituta imeni V.A. Steklova. ǂl English 430 _ _ $a Proceedings of the Steklov Institute of Mathematics 377 _ _ $a eng $l English Here the entire Russian series is translated and published, volume by volume, so the authorized access point and the authority record as a whole represents an expression.

New Field: 380: Form of Work RDA 6.3 No indicators Subfields $a Form of work (R) – a term expressing the class or genre of the work Examples: 380 _ _ Series 380 _ _ Subseries? 380 _ _ Multipart item? 380 _ _ Series-like phrase? The 380 field is used to record the Attribute: Form of Work. Series is the term that shows up in RDA examples. But perhaps other Form of Work attributes could be used as well. Other forms might be Subseries, and terms from the coded 008/12, Multipart item and Series-like phrase. We will have to wait for the PCC to develop a best practice for this area. Bye the way, series-like phrase records are not defined in AACR2 or RDA. However, PCC policy is unchanged (LC-PCC PS 2.12), and PCC catalogers should continue to create series authority records for series-like phrases.

New Field: 381: Other Distinguishing Characteristics of Work or Expression No indicators Subfields $a Other distinguishing characteristic (R) – Any characteristic that is not accommodated in a special field that serves to characterize a work or expression. Examples are an issuing body, arranged statement of music, version, or a geographic term. May be used to differentiate a work from another work with the same title. RDA 6.6 The 381 field is used to record the Attribute: Other distinguishing characteristic of work. Remember that RDA instructs us that this attribute is a characteristic other than form of work, date of work, or place of origin of the work that serves to differentiate a work from another work. As is true with all of these attributes, you can look in the MARC 21 Authority Format and in RDA by instruction number to find examples for each of these fields/attributes.

Justifying the 381 670 Subfields $u Uniform Resource Identifier (R) $v Source of information (R) $2 Source of term (NR) – Code from the Subject Heading and Term Source Codes www.loc.gov/standards/sourcelist/subject.html Multiple characteristics from the same source vocabulary may be recorded in the same field in separate occurrences of $a Here are the usual source options. Multiple instances of this attribute can go in the same 381 field as long as they share the same source. And, once again, follow the PCC practice for 670s, delimiter u, and delimiter v.

381: Other Distinguishing Characteristics: Example 100 1_ $a Shakespeare, William, $d 1564-1616. $t Plays. $k Selections (Stratford-upon- Avon, England) 400 1_ $a Shakespeare, William, $d 1564-1616. $t Shakespeare Memorial Theatre series 381 _ _ $a Selections 381 _ _ $a Royal Shakespeare Theatre (Stratford-upon-Avon, England) $2 naf Here is an example. The authorized access point for the Shakespeare Memorial Theater is Royal Shakespeare Theatre (Stratford-upon-Avon, England). You could use the natural language appearing on the source, or the authorized form.

381: Other Distinguishing Characteristics: Example 130 _0 $a Formules (Unnumbered) 381 _ _ $a Unnumbered