Source: PCC Series Bridge Training

Series Treatment: 4 Types of Resources

Module 1, Slide 11

Under RDA, we will continue to transcribe series statements and create series authority records for these four different types of resources. 

Monograph series and analyzed serials have serial comprehensive descriptions.

Multipart monographs have monographic comprehensive descriptions.

Series-like phrases have no comprehensive descriptions; records for series-like phrases are created to save time for the cataloger. Although they are not mentioned in AACR2 or RDA, they are described in the LCRIs and the LC-PCC PS’s (2.12, 2.3.2.13, and 6.27.4), and they are valid in MARC21. Since they have proved useful, their place in the current metadata environment will need to be discussed.

• Monograph series (008/12 = a)
• Multipart monograph (008 = b)
• Series-like phrase (008 = c)
• Other (serials with issues that have analyzable titles) (008 = z)

Source: PCC Bridge Training Module 3b Slide 3, RDA 6.4, 6.10

New field: 046: Special Coded Dates (R)

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.

• 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.

Source: PCC Series Bridge Training, Module 3b, Slide 3

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.  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.

Source: PCC Series Bridge Training, Module 3b, Slides 20-23, RDA 6.6

New Field: 381: Other Distinguishing Characteristics of Work or Expression

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.

• 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.

Justifying the 381

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.

• 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 [1]

• Multiple characteristics from the same source vocabulary may be recorded in the same field in separate occurrences of ‡a

Under current YUL policy, a SAR for the Shakespeare example should not be made, since it requires a conventional collective titles and LC PCC policy has not been clarified for CCTs. If an AAP is needed, use Selections without further qualification.

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.

YUL: Since a CCT is not needed, a SAR of this type is OK to make.

Source: PCC Series Bridge Training, Slides 12-14

Presenter Notes. When the title is not unique, we add one or more qualifiers, to form the authorized access point .  The rules for making this addition to form a serial’s or a series’ access point are substantially the same as before, so we have in these examples a Place of Origin Attribute, and an issuing body and publisher, both Other Distinguishing Characteristic Attributes.

Additions to Generic Titles

Presenter Notes. In other words—as before, there are several attributes that can be used as qualifiers; the choice depends on whether the title is generic, and on other factors. Here is an example of when we qualify with Place of Origin and/or Publisher or Issuing Body (one of the Other Distinguishing Characteristics, at the Expression level), and use Form of Work or Date of Work when needed.

Unnumbered vs Numbered, Corporate Name as Numbered Series

As before, if the best way to distinguish between two otherwise-identical series authorized access points is to add “(Unnumbered)” to one of them, then that is what we do.

Also as before, when numbering is present on our item in conjunction with a corporate body name, we consider that name to be the series title and distinguish the series authorized access point from the corporate body’s authorized access point by adding the Form of Work:

LCPS 6.27.1.9:

"Unnumbered/numbered titles from the same body. If one body issues both an unnumbered series and a numbered series/serial with the same title, add the qualifier "(Unnumbered)" for the unnumbered series in all cases of such a conflict. (For example, if the new title is numbered and the existing title is unnumbered, change the authorized access point for the existing unnumbered series to add "(Unnumbered)".) Do not apply this technique when some issues of a series lack numbering."

Source: PCC Series Bridge Training, Module 6b

YUL: until PCC comes to agreement on handling of series expressions, make the series AAPs as follows, and do not make SARs. For the series AAP for the original language, do not include the original language. Do not add ‡s to the AAPs.