9: Identifying Appropriate Copy

9: Identifying Appropriate Copy
How do I identify the "most appropriate" serial record? Is it the same publication? Is it for the appropriate physical format? Do the dates fit? Is the record RDA or pre-RDA? How authoritative is the record? References The trainer may want to review the following sources: CONSER Editing Guide, Field 042 CONSER Cataloging Manual, Modules 22 and 31 Questions for the Session: The objectives of this session are to help the participants recognize the distinctive elements of serial cataloging records, define the “most appropriate” serial copy, and select appropriate serial copy based on information from the piece(s) in hand. To that end the material in the session is focused on answering these questions: - Does the record describe this publication, in general? How does the format match; for example, if the publication is a CD-ROM, is the record also for a CD-ROM? Does the issue in hand fit with the dates in the record? - Can the record be interpreted & edited by anyone familiar with the current RDA rules? Or, is knowledge of earlier rules needed? - What assumptions can the cataloger make, based on the quality of the record? [Trainers Note: Records in any utility or catalog will reflect several generations of cataloging. For that reason, many of the pre-RDA records on these slides reflect non-CONSER standard record cataloging practices.] SCCTP Basic Serials Cataloging Workshop

Is the publication the same?
What to look for: Description ISSN Title statement Publisher Date of publication Issuing bodies Subject headings Links MARC 21 Tag $a, $n, $p, and $c 264 $b (or 260 $b) 264 $c, 362, 008 dates 550, 11X, 71X 6XX 780/785, other 77X What to look for Evaluating Serial Copy [Trainers: please note that the records used for examples in this session may not conform to current practices in coding, tagging, formatting notes, etc. The emphasis in this session is on selecting the best or most appropriate copy available, not on how it should or could be edited. The session on working with copy will cover the editing of serial copy.] The first question to ask is, Does this record describe the same publication as the one in hand? - What you need to know - Many serials have the same title. - What may at first seem to be the appropriate record may not be - What to look for in the record: - Does the ISSN on the issue match the record? 2- How well do the descriptive elements match--the title proper ($a, $n, $p), edition, and publisher? [NOTE: 245 $c is not required for CONSER standard records, but will still be found in other RDA and pre-RDA records] - Does the date of coverage on the issue in hand match the range given in the 362 field (and 008 Date elements)? - Is the publication in hand issued by the same body as that represented in the record? SCCTP Basic Serials Cataloging Workshop

Example CRITIQUE studies in contemporary fiction Cover:
Volume 40, No Spring 1999 Verso of cover: CRITIQUE: Studies in Contemporary Fiction (ISSN ) is published quarterly by Heldref Publications, 1319 Eighteenth Street, N.W. Washington, D.C … Critique is a fairly common title. What other clues could the cataloger use to match this issue to records in the database? Note that there is an ISSN and that it is published in Washington. Note also that what we are looking at is volume 40, published 1999. Setup: A search of the utility retrieves three records. The question is, which (if any) matches this issue? SCCTP Basic Serials Cataloging Workshop

Record 1 Type a ELvl Srce c GPub Ctrl Lang eng BLvl s Form Conf 0 Freq b MRec Ctry nyu S/L 0 Orig EntW Regl r Alph a Desc a SrTp p Cont DtSt d Dates 1946, ## $a //r # $a $ ## $a (OCoLC) ## $a DLC $c DNGA $d InU $d DLC $d NSDP $d m/c 042 ## $a pcc $a nsdp $a N1 $b .C ## $a 709/.04 $ # $a Critique (New York, N.Y.) 210 0# $a Critique $b (New York, N.Y.) $a Critique $b (New York, N.Y.) $a Critique. This is the first record that has been found. What do we see from this screen? - The title is the same. - Qualifier in 130 and 222, 210 is New York; fixed field place is New York - It was only published from - The ISSN doesn’t match. SCCTP Basic Serials Cataloging Workshop

Record 1 (continued) 260 00 $a New York : $b [s.n.], $c 1946-1947.
300 ## $a 1 v. : $b ill. ; $c 24 cm. 310 ## $a Bimonthly, $b Jan.-Feb. 1947 321 ## $a Monthly, $b Oct.-Nov. 1946 362 0# $a Vol. 1, no. 1 (Oct. 1946)-v. 1, no (Jan./Feb. 1947). 500 ## $a A review of contemporary art. 500 ## $a Title from cover. 500 ## $a Editor: Oct D. Loshak and others. 650 #0 $a Art $v Periodicals. 650 #0 $a Art, Modern $y 20th century $v Periodicals. 7001# $a Loshak, David. Points to mention from this screen: The imprint (260) information does not match. The dates (362 and fixed field Dates) are clearly outside the range of the piece in hand. There is no issuing body given in a note or in an added entry. The subjects (65X) do not match. SCCTP Basic Serials Cataloging Workshop

Record 2 Type a ELvl Srce c GPub Ctrl Lang eng BLvl s Form Conf 0 Freq f MRec Ctry stk S/L 0 Orig EntW Regl r Alph Desc SrTp p Cont b DtSt c Dates 1973, ## $a //r ## $a $2 z 035 ## $a (OCoLC) ## $a DLC $c DLC $d OCoLC $d NST $d AIP $d NST $d MH 042 ## $a lc 043 ## $a ee----- $a e-ur $a DK246 $b .C ## $a 320.9/47/ # $a Critique $b (Glasg.) 222 #0 $a Critique $b (Glasgow) $a Critique. This is the second record found. What matches and what doesn’t? The ISSN (022) does not match. The title (245) does match. SCCTP Basic Serials Cataloging Workshop

Record 2 (continued) 260 ## $a [Glasgow] 300 ## $a v. $c 21 cm.
362 0# $a v. 1- spring 1973- 500 ## $a "A new journal of Soviet studies and Socialist theory." 651 ## $a Soviet Union $x Politics and government $v Periodicals. 651 ## $a Europe, Eastern $x Politics and government $v Periodicals. 650 #0 $a Socialism $v Periodicals. Points to mention: The imprint (260) information does not match. The dates (362 and fixed field Dates) could include the piece in hand. There is no issuing body (550 or 710) mentioned on this record. The subjects (65X) do not match. SCCTP Basic Serials Cataloging Workshop

Record 3 Type a ELvl Srce d GPub Ctrl Lang eng BLvl s Form Conf 0 Freq q MRec Ctry dcu S/L 0 Orig EntW Regl r Alph a Desc i SrTp p Cont DtSt c Dates 1956, ## $a # $a $ ## $a MUL $b eng $e rda $c MUL … 042 ## $a pcc $a PN3503 $b .C # $a # $a Critique (Bolingbroke Society) 210 0# $a Critique - Bolingbroke Soc. 222 #0 $a Critique - Bolingbroke Society In record 3 what matches? The ISSN (022) matches. What else do you notice about the record? 040 $e rda and Desc = i This is an RDA record. SCCTP Basic Serials Cataloging Workshop

Record 3 (continued) 245 10 $a Critique.
264 #1 $3 <summer 1957-> $a [Minneapolis, Minnesota] : $b Bolingbroke Society $3 fall : $a Washington, D.C. : $b Heldref Publications 300 ## $a volumes ; $c cm 310 ## $a Quarterly, $b fall 1982- 321 ## $a Three times a year, $b winter 1956-spring 1982 336 ## $a text $b txt $2 rdacontent 337 ## $a unmediated $b n $2 rdamedia ## $a volume $b nc $2 rdacarrier 362 1# $a Began with: Vol. 1, no. 1 (winter 1956). Points to mention: The title (245) matches. The first imprint 264 information does not match, but the second 264 current publishing information makes it clear that the publication information has changed and the new information does match. The dates (362 and fixed field Dates) could include the piece in hand. A society is associated with this publication (see also 710 on next slide). SCCTP Basic Serials Cataloging Workshop

Record 3 (continued) 500 ## $a Some vols. have also special titles.
588 ## $a Description based on: Vol. 1, no. 2 (summer 1957); title from cover. 588 ## $a Latest issue consulted: Vol. 30, no. 1 (fall 1988). 515 ## $a Lacks date designation, <volume 3, no. 16>-volume 23, no. 1. 650 #0 $a Fiction $y 20th century $x History and criticism $v Periodicals. 710 2# $a Bolingbroke Society. $t Faulkner studies $w (OCoLC) Points to mention: The subject (65X) does match the scope of the serial being searched. Note that as a serial changes over time, some information (e.g., Bolingbroke Society) that appears on early issues may no longer appear on later issues. SCCTP Basic Serials Cataloging Workshop

Is the Record for the Same Format?
What to look for: Description MARC Tag Fixed fields form coding , 006, and 007 General Material Designation (GMD) $h (if AACR2) Physical description Content, media, carrier type 336, 337, 338 Other physical format note Reproduction note Electronic access Is the record for the same physical format? - What you need to know: - Many serials are issued in multiple formats: print, electronic (CD, online), microform (microfilm, microfiche) - Often they have the same title - You will often find many records for the microform version (use the search mechanism in your utility to eliminate these if you are hunting only for the print title) Online versions may have their own record or they may be noted on the print record (if you are cataloging the print title, you can use this record). With RDA the general material designation was abolished in favor of providing specific terms for content, media and carrier types in the 336, 337, 338 fields. According to PCC and OCLC guidelines these fields may appear in AACR2 and pre-AACR2 records without the GMD having been removed. A future project will likely remove the GMD from these OCLC records, but for the time being the GMD remains even if 336, 337 and 338 have been added. - What to look for in the record: (discuss list above) SCCTP Basic Serials Cataloging Workshop

Example March 1999 VANITY FAIR Cover: Table of contents p. 24:
March No 463 Masthead page: Vanity Fair is published by The Condé Nast Publications, Inc. Condé Nast Building, 350 Madison Avenue, New York, New York 10017 In this case, we are looking for the appropriate record for Vanity Fair. We have the serial in print. SCCTP Basic Serials Cataloging Workshop

Record 1 Type a ELvl I Srce d GPub Ctrl Lang eng
BLvl s Form a Conf Freq m MRec Ctry nyu S/L Orig EntW Regl r Alph a Desc a SrTp p Cont DtSt c Dates 1914,9999 007 ## $a h $b b $d b $e d 010 ## $a $z sn $z sn 040 ## $a BHP $b eng $c BHP 022 0# $a 130 0# $a Vanity fair (New York, N.Y.) 222 #0 $a Vanity fair $b (New York, N.Y.) $a Vanity fair $h [microform]. 260 ## $a [New York : $b Vanity Fair Pub. Co., $c 1913- 300 ## $a v. : $b ill. ; $c cm. Points to mention: There are lots of clues as to physical format in this record! The fixed field Form is coded for a microfilm version (code a). The 007 field makes it clear that this record is for a microfilm version. The GMD in the 245 field also makes it clear that this is for a microfilm version. Form “a” = 008/23 Form of item is coded required “a” for microfilm Note that the record is coded AACR2 in Desc “a” SCCTP Basic Serials Cataloging Workshop

Record 1 (continued) 336 ## $a text $b txt $2 rdacontent
337 ## $a microform $b h $2 rdamedia 338 ## $a microfilm cartridge $b hb $2 rdacarrier 362 0# $a [Vol. 1, no. 5 (Jan. 1914)]- 500 ## $a Imprint varies: New York, NY : Condé Nast Publications, 515 ## $a Issues for Jan Feb called also v. 1, no. 9-v. 45, no. 6. 580 ## $a Absorbed by: Vogue, Mar. 1936; resumed publication Mar with v. 46, no. 1. 580 ## $a Issued also in an Italian ed. (with different textual content) under title: Vanity fair Italia, June 1990- 533 ## $a Microfilm. $b Foster City, CA : $c Information Access Co., $e cartridges : negative ; 16 mm. $f (Magazine collection) # $t Vanity fair Italia $w (DLC) $w (OCoLC) Points to mention: Even though this is an AACR2 record that has a GMD in the 245 $h, note that the 336, 337 and 338 field have optionally been added to this record The 533 notes also makes it clear that this is a reproduction microform record. Note: the rest of the record, the following fields are not included in the example just to save space: $t Dress & vanity fair $w (OCoLC) $w (DLC)sf $t Vogue $x $g Mar Feb $w (DLC) $w (OCoLC) $a Magazine collection SCCTP Basic Serials Cataloging Workshop

Record 2 Type a ELvl Srce d GPub Ctrl Lang eng
BLvl s Form Conf Freq m MRec Ctry nyu S/L Orig EntW Regl r Alph a Desc a SrTp p Cont DtSt c Dates 1914,9999 010 ## $a //r912 $z sn $z sn 022 0# $a $2 1 040 ## $a ViU $c ViU … 042 ## $a nsdp $a pcc $a AP2 $b .V # $a Vanity fair (New York, N.Y.) 210 0# $a Vanity fair $b (N. Y. N. Y.) 222 #0 $a Vanity fair $b (New York, N.Y.) $a Vanity fair. This is an AACR2 record for the print version. Note the following: Form of item in fixed field is blank There is no GMD in the 245 For a CONSER standard record: FF: Conf, Freq, Regl are not required SCCTP Basic Serials Cataloging Workshop

Record 2 (continued) 260 ## $a [New York : $b Vanity Fair Pub. Co., $c 1913- 300 ## $a v. : $b ill. ; $c cm. 310 ## $a Monthly 336 ## $a text $b txt $2 rdacontent 337 ## $a unmediated $b n $2 rdamedia 338 ## $a volume $b nc $2 rdacarrier 362 0# $a [Vol. 1, no. 5 (Jan. 1914)] ## $a Imprint varies: N.Y., N.Y. : Condé Nast Publications 515 ## $a Issues for Jan Feb called also v. 1, no. 9-v. 45, no. 6. 515 ## $a Issues for Mar July 1995 called v. 46, no. 1-v. 58, no. 7; for Aug called no. 420- Further indications: 300 field has v. This is the appropriate record. SCCTP Basic Serials Cataloging Workshop

Record 2 (continued) 580 ## $a Absorbed by: Vogue, Mar. 1936; resumed publication Mar with v. 46, no. 1. 580 ## $a Issued also in an Italian ed. (with different textual content) under title: Vanity fair Italia, June 1990- 775 1# $t Vanity fair Italia $w (DLC) $w (OCoLC) $t Dress & vanity fair $w (OCoLC) $w (DLC)sf $t Vogue $x $g Mar Feb $w (DLC) $w (OCoLC) For a CONSER standard record: 775: now would prefer even if have 580 785: now would prefer even if have 580 SCCTP Basic Serials Cataloging Workshop

Do the dates fit? What to look for: Description Dates of coverage Publication dates Designation(s) Description based on note Latest issue consulted note Other notes MARC Tag Fixed field dates (008) 264 $c (or 260 $c) or 588 5XX Does the date of the issue(s) in hand fit within the scope of the record? - What you need to know: - Because serials are issued over time they can change their titles and sometimes change back to an original title - Just because the title and the publisher are the same does not necessarily mean that the record is appropriate. - What to look for in the record: First, look at the fixed field (Dates) and 362 field. In AACR2 and some early RDA records, publication dates may also be found in the 260 subfield $c. (Note that 264 subfield $c is only required in CONSER RDA records when the first or last issue is in hand. - However, because the description may not be based on the first issue, also look at notes in the record, especially the Description based on note. SCCTP Basic Serials Cataloging Workshop

Issue in hand for March 1999:
Type a ELvl Srce d GPub Ctrl Lang eng BLvl s Form Conf Freq m MRec Ctry nyu S/L Orig EntW Regl r Alph a Desc a SrTp p Cont DtSt c Dates 1914,9999 010 ## $a //r912 $z sn $z sn 022 0# $a $2 1 040 ## $a ViU $c ViU … 042 ## $a nsdp $a lc $a AP2 $b .V3 130 0# $a Vanity fair (New York, N.Y.) 210 0# $a Vanity fair $b (N. Y. N. Y.) 222 #0 $a Vanity fair $b (New York, N.Y.) $a Vanity fair. Example: issue in hand is for March Note that the fixed field dates are open (9999 in last position). For a CONSER standard record: FF elements Conf, Freq, and Regl could be fill characters SCCTP Basic Serials Cataloging Workshop

Example (continued) 260 ## $a [New York : $b Vanity Fair Pub. Co., $c 1913- 300 ## $a v. : $b ill. ; $c cm. 310 ## $a Monthly 362 0# $a [Vol. 1, no. 5 (Jan. 1914)]- 500 ## $a Imprint varies: N.Y., N.Y. : Condé Nast Publications 515 ## $a Issues for Jan Feb called also v. 1, no v. 45, no. 6. 515 ## $a Issues for Mar July 1995 called v. 46, no. 1-v. 58, no. 7; for Aug called no. 420- If this were an RDA CONSER standard record: 260 $c: Record the publication date(s) of first and/or last issue if the dates are known and the first and/or last issues are in hand. 300 not required for ongoing print serial (RDA alternative + LC PCC PS: only require extent for ceased print serials--where extent is known) 362 1#could be phrased: Began with vol. 1, no. 5 (Jan. 1914). SCCTP Basic Serials Cataloging Workshop

Example (continued) 580 ## $a Absorbed by: Vogue, Mar. 1936; resumed publication Mar with v. 46, no. 1. 580 ## $a Issued also in an Italian ed. (with different textual content) under title: Vanity fair Italia, June 1990- 775 1# $t Vanity fair Italia $w (DLC) $w (OCoLC) $t Dress & vanity fair $w (OCoLC) $w (DLC)sf $t Vogue $x $g Mar Feb $w (DLC) $w (OCoLC) This screen shows that the title was absorbed by Vogue for a certain period, which is explained by the 580 and 785 fields. However, the title resumed and thus, this is still an active record. The reason why there is no new record is because the absorption was temporary and the resumed serial continued the numbering. If this were a CONSER standard record: 775 would be coded $i Issued… $t Vanity fair Italia [even with 580] SCCTP Basic Serials Cataloging Workshop

Is the record RDA? What to look for:
MARC coding for RDA bibliographic records: 040 ## $a ____ $b eng $e rda $c ____ PCC practice: Code for (and use) ISBD punctuation: Leader/18: value “i” Is the record RDA? - What you need to know: - Many records you will find were created prior to RDA. They might be coded as AACR2 or pre-AACR2 records. - In most cases, these are perfectly good records and need not be changed to RDA. In some cases, however, they may need to be changed. (This will be discussed in the next session). RDA records are identified by $e rda in the 040 field. The PCC preferred best practice is to enter the $e rda immediately after the subfield $b. This element says: “RDA was used as the content standard in this record.” Historically in WorldCat the absence of subfield $b has indicated that English is the language of cataloging. OCLC now recommends always coding this element. ( Additionally, PCC has decided that members will code Leader/18 as “i” since PCC libraries use ISBD punctuation in the bibliographic records created. SCCTP Basic Serials Cataloging Workshop

How authoritative is the record?
CONSER authentication codes (042 field): Specific agencies: pcc Program for Cooperative Cataloging nlc Library and Archives of Canada (formerly National Library of Canada) nsdp National Serials Data Program (US ISSN Center) isds/c ISSN Canada Name heading status: msc Descriptive elements verified, but one or more headings not in the LC Name Authority File How authoritative is the record? What you need to know: - The CONSER program has created or authenticated many serial records. LC serial records are all CONSER records. - The 042 field of a serial record identifies a CONSER-authenticated record. The specific code indicates the level of authentication; it may also show the authenticating agency. This slide and the next show some of the most common codes found in CONSER records. - Headings in CONSER standard records and (for records created before June 2007) CONSER Full records are all included in the Name Authority File; and descriptive and subject elements have been verified as of the date given in field 936 or 500 “Latest issue consulted” note. - However, not all CONSER records have headings fully-backed by authority records. CONSER records coded with 042 msc may contain headings NOT backed by records in the Name Authority File. - Also: Just because a record is CONSER authenticated does not mean that the record might not need some editing; later changes may have occurred to the serial. - Finally, OCLC also uses the 042 field for programs other than CONSER. Beware that codes such as “dlr” and “anuc” do not indicate PCC authentication Trainer’s Note: The PCC Working Group on Authentication Codes and Encoding Levels recommended in fall 2006 that 042 codes “lc” and “lcd” be replaced by “pcc.” This change was implemented May 1, 2009; and OCLC completed replacement of these codes by “pcc” in [See: SCCTP Basic Serials Cataloging Workshop

CONSER authentication codes (042 field): Other: lccopycat Library of Congress copy cataloging premarc Library of Congress recon record x Codes that begin with an "x” mean the title is not considered to be a serial or the institution has not treated it as a serial You may find a code, such as “xlc” on a record for a monographic series or a conference publication. In this case, the code means that LC does not treat this title as a serial. It does not mean that it isn’t a serial and that another CONSER cataloger might want to create a serial record for it. SCCTP Basic Serials Cataloging Workshop

What to look for: LCCN (010 field): Unprefixed LC (or CONSER after 2000) 010 ## $a sn- prefix US ISSN Center or other CONSER member (prior to 2000) 010 ## $a sn c-- National Library of Canada 010 ## $a ce How authoritative is the record? In addition to an 042 authentication code, each CONSER record will have a Library of Congress Control Number (LCCN) in an 010 field. This slide shows some aspects of coding the LCCN. SCCTP Basic Serials Cataloging Workshop

What else? What to look for: Description MARC Tag
Call numbers , 082, 090, etc. Subject headings XX Earlier and/or later titles and/or 785 Related titles Other 76X-78X linking fields What else should the cataloger consider? - What you need to know: -- Not all serial or CONSER records will contain a call number and subject headings. Many CONSER records are those created by the ISSN center. You may need to add subject elements, as appropriate. -- Serial records often contain links to earlier or later titles and your span of issues may include one of these titles. -- Serial records also often have links to other related records, such as supplements, translations, language editions, and other physical formats. Do you also have one of these titles in your collection? Would you need to edit these records as well? - What to look for in the record: In considering whether a record can be used as-is or whether it will need enhancement, check for subject analysis (call numbers, subject headings) and relationships (earlier, later, and related titles) SCCTP Basic Serials Cataloging Workshop

Example Type a ELvl 8 Srce d Pub Ctrl Lang eng
BLvl s Form o Conf ■ Freq q MRec Ctry nju S/L Orig EntW Regl r Alph a Desc i SrTp p Cont DtSt c Dates 2015,9999 006 m o d 007 ## $a c $b r 010 ## $a 040 ## $a DLC $b eng $e rda $c DLC 012 ## $l 1 022 0# $a $2 1 042 ## $a msc $a ISSN RECORD $a IEEE transactions on big data. Example: U.S. ISSN Center prepublication record. What codes do you notice, in this record? The Fixed Field Elvl code is ‘8’ for a pre-publication record and that the 040 has the code “DLC.” Also: Pre-publication records still reflect Freq/Regl codes. Examples: OCLC# , Those familiar with monograph cataloging could compare ISSN pre-publication records with “Cataloging in Publication” records for books. 042: Code msc is used by the U.S. ISSN Center in all prepub records because headings are not checked in these records. Trainer’s note: The U.S. ISSN Center assigns ISSNs for serials and other continuing resources published in the U.S. For many years since its beginning it was known as the National Serials Data Program (NSDP) and records created by it were coded 040 $a NSD $c NSD. SCCTP Basic Serials Cataloging Workshop

Example (continued) 246 1# $a Transactions on big data.
264 #1 $a Piscataway, NJ : $b Institute of Electrical and Electronics Engineers, Inc. $c 2019- 310 ## $a Quarterly 336 ## $a text $b txt $2 rdacontent 337 ## $a computer $b c $2 rdamedia 338 ## $a online resource $b cr $2 rdacarrier 710 2# $a Institute of Electrical and Electronics Engineers. 936 ## $a PREPUB: publication expected: Jan. 2015 The note in field 936 (CONSER note field) explains that this is a record created prior to publication for the purposes of assigning the ISSN. Field 263 contains the expected date of publication. Note: This pre-publication record is an example of a CONSER record that is NOT a CONSER standard record. (It is not a CONSER Standard Record because the access points are not necessarily backed by authority records.) However, it does follow the CSR coding for the fixed field. SCCTP Basic Serials Cataloging Workshop

Pre-AACR2 caveats Truncated titles: Transcription: Initialisms:
On piece: Annual report. Quarterly statistics of the Finance Department. Transcription: Report. Statistics. Initialisms: $a GQ, Gentleman’s quarterly. Pre-AACR2 and Latest Entry Records - If the copy you find is coded as pre-AACR2, note that the rules for choice of entry, descriptive cataloging (including title transcription), punctuation, capitalization and bracketing were quite different. - Some typical differences: Titles were often truncated to omit frequency statements and corporate body names when the same body was also the main entry. For example, On piece: Transcription: Annual report  Report. Quarterly statistics of the Finance Dept.  Statistics. Note that this affects search strategies in both the local OPAC and in a utility such as OCLC. After 1975, if a piece contained both an initialism and a full form of the title, both were included in the title proper. The initialism appeared first separated from the full title by a comma. For example, $a GQ, Gentleman’s quarterly. [Trainer’s note: For more information, see: CONSER Cataloging Manual 22.4.e] SCCTP Basic Serials Cataloging Workshop

More pre-AACR2 caveats Use of the 247 for slight title variations:
$a Bulletin - Council on Library Resources. $a Bulletin of the Council on Library Resources 500 ## $a Title varies slightly. Rarely, some AACR successive entry records may contain a 247 field (former title or title variations) for slight variations in the title proper. For example, $a Bulletin – Council on Library Resources. $a Bulletin of the Council on Library Resources $a Title varies slightly. - In the history of online serials cataloging there are two main sets of rules that have been employed to describe and maintain the bibliographic histories of serial titles. They are: latest entry cataloging (coded in fixed field 008 S/L as “l”) and successive entry cataloging (coded in fixed field 008 S/L as “0”) - There are MARC records in most utilities and systems created according to both of these conventions. SCCTP Basic Serials Cataloging Workshop

Latest entry records Description is based on latest issue
Earlier title changes are included in 247 fields Earlier issuing bodies in 550 note New records created for mergers and splits Latest entry records: Latest entry records describe the bibliographic history of a serial in fewer records since the occasions when a new record was called for were far more limited. When a title changed, the record was revised so that entry was under the latest title with earlier titles accounted for in 247 fields. Records for serials entered under corporate bodies likewise were revised to reflect the latest corporate body when the body changed. A new record was created to handle title mergers and splits. The next slide is an example of a latest entry record (some tags omitted). SCCTP Basic Serials Cataloging Workshop

Latest Entry Record Type a Elvl Srce d GPub Ctrl Lang eng Blvl s Form Conf 0 Freq m MRec Ctry nyu S/L 1 Orig EntW Regl n Alph Desc SrTp p Cont DtSt d Dates 1926, ## $a //r ## $a ## $a Arts magazine. 247 ## $a Art digest $f Nov July ## $a Arts digest $f Aug Sept ## $a Arts $f Oct May/June ## $a [New York, etc. $b Art Digest Inc.] 362 0# $a v. 1-66, no. 7; Nov Mar 1992. If you use pre-AACR2 copy, consult your local standards for editing copy. [At this point, depending on audience interest, the instructor may wish to also show optional slides : Related to OCLC: parallel language record; Institutional Record Related to E-Serials] SCCTP Basic Serials Cataloging Workshop

Summary When selecting copy, look for: In comparing records, look for:
Physical format RDA descriptive conventions Successive entry cataloging In comparing records, look for: ISSN Title proper and dates Publication information CONSER-authenticated copy Summary Select serial copy based on: - physical format - RDA descriptive conventions, - successive entry cataloging, including linking entries for earlier/later titles - ISSN - title proper & numeric and/or chronological designations - publication information, as well as statement of responsibility and/or issuing body notes - publication dates CONSER authenticated copy is often the best choice. Be aware of the major pre-AACR2 serials cataloging conventions and your local policies for adapting/editing records created using them. [For those cataloging e-serials: Be aware of the various ways of handling electronic journals well as your local policies] SCCTP Basic Serials Cataloging Workshop

Additional slides (related to OCLC)
SCCTP Basic Serials Cataloging Workshop

OCLC: Parallel Language Record
(Optional: after slide 34) If you are an OCLC user, then be aware of OCLC’s partnerships with vendors and others who catalog in other languages. In the case of “Today’s cinema,” the serial is in English. But the language of cataloging is Dutch. Look for: 040 #b for the language code. Other Clues: FF codes may be unexpected, e.g., according to this record, the serial has ceased. That is consistent with the 260 field. But do not be surprised if the issues in hand contradict this information. When you find parallel language records, continue searching—you may also find English-language records. If this is the only record, then either create an original record or derive a record. Link your record to the non-English record with a 936 field. In the future, OCLC plans to migrate these records to Institutional Records based in part on the 936 fields. That will make these records easier to distinguish from other records. SCCTP Basic Serials Cataloging Workshop

OCLC: Institutional Records
(Optional:after slide 34) Beginning in 2006, two large databases of records merged: OCLC and RLIN. As part of that merger, OCLC was restructured. In the past, OCLC strove to include one record to represent each work. This was termed the “Master Record” concept. Now, libraries may retain the individual view of their own bibliographic records. These institution-specific records are called “Institutional Records.” Points: You may find additional information on these Institutional Records; however, you will need to evaluate the information against the master record and other records in OCLC. For example, the master record may show that a serial has ceased; the Institutional Record may still be open. SCCTP Basic Serials Cataloging Workshop

Basic Serial Cataloging Workshop
10: Working with Copy Change over time Criteria for editing copy Some guidelines to keep in mind Categories of maintenance This module was revised Sept. 10, 2014 Welcome to the final module of the SCCTP Basic Serials Cataloging Workshop. In this module, we will be discussing ways in which serials change over time, general principles and guidelines for editing records, and a few of the most common categories of maintenance. May 2014

Change over time How to maintain existing records?
How do we accommodate change? Using existing copy How to edit? RDA & AACR2/CSR records Pre-AACR2 successive entry records When to consider re-describing to RDA? In Module 10, we’ll explore the questions: --How to maintain existing records? --What kinds of change can be accommodated in the existing RDA description? --How can we modify our legacy AACR2 records using RDA? ** Note that we will not be covering pre-AACR2 successive entry records in this workshop. ** --When should we consider re-describing pre-RDA records? (brief mention only) SCCTP Basic Serials Cataloging Workshop

Criteria for editing copy
Local policies & CEG B.4 Added value for end users and processing staff Other fields may need editing: Input standards for local system and utility Reports derived from your system General thoughts about maintaining CONSER records: --Within this module, our focus is: identifying those corrections and/or additions that add value for end users and processing staff while meeting basic standards --The extent to which copy should be edited is dependent on local policies and also CONSER guidelines (CEG B4) --Some changes may need to be completed with the help of OCLC (e.g., dup reporting); (consolidation of CONSER records); CONSER colleagues (use the CONSER website’s Contacts list!); and US ISSN (report through the portal those serials that need ISSNs, for US publications that change title) --Other records may need to be edited as well in your local system depending on: 1. The needs of your local system 2. The types of reports you expect to pull from your automated system (e.g., locally defined fields, other data elements in the fixed fields, etc.). Original trainers notes: Criteria for Editing Serial Copy -The extent to which the copy you have selected should be edited is a local decision. - However, major changes that affect the record’s accuracy (title changes, cessations, incorrectly closed records, etc.) can be reported to your utility to help improve the records available for other institutions. - In addition, editing may be important since serials change over time; and so may cataloging practices (e.g., the use of subfield v for form divisions such as Congresses, Directories, and Periodicals) and the CONSER standard record guidelines. - The suggestions outlined below are based on a single consideration; namely, identifying those corrections and/or additions to existing copy that add value to the final record for end users and processing staff while meeting basic standards. - Such streamlining focuses copy cataloging work on the truly critical elements most valued by all users. - Other fields may need to be edited as well depending on: 1. The input standards of your utility, local systems, etc. SCCTP Basic Serials Cataloging Workshop

Keep in mind … Do not edit records to conform to new standard
Do not delete data unless incorrect Maintain changes that affect access to the record Records may contain a mix of old and new practices (as always) Existing records created before implementation of RDA and the CONSER Standard Record do not need to be edited just to conform to the new standard. Catalogers are urged not to remove any fields from existing records unless the data in those fields are determined to be incorrect or are already outdated and would not be maintained because the information is no longer required under the new guidelines. As a general guideline, consider any change that affects access to the record or the performance of other serials functions (such as receiving, claiming, or binding) as a candidate for maintenance. If new information needs to be supplied, supply it according to CSR guidelines. If in a particular situation it is more difficult to supply information according to RDA CSR guidelines, and if the cataloger can easily supply the information according to code of the original record, it is fine to do so. SCCTP Basic Serials Cataloging Workshop

Categories of maintenance
ISSN Access points: Variant titles Issuing bodies Series Place of publication/publisher Numbering Frequency Other changes Hybrid records Pre-AACR2 maintenance Here are eight types of serial record maintenance. Seven will be covered in this session. We will be covering the first five topics in some detail; and the next two topics in passing. As mentioned before, we will leave pre-AACR2 maintenance for another time Trainers notes: You may wish to add an empty slide before this and ask participants for the types of changes they’ve encountered when working with serials Trainers notes (Online): Have participants use the chat function/box to share types of changes they’ve encountered when working with serials. SCCTP Basic Serials Cataloging Workshop

ISSN (022 field) 022 ## $a $ l $y $y $2 1 $a = valid ISSN $ l = ISSN-l $m = canceled ISSN-l $y = incorrect ISSN $z = canceled ISSN $2 = ISSN Center ISSN (022 field): International Standard Serial Number The ISSN can be especially helpful for serial orders and check-in staff if the 022 field is indexed in your system and is used by Acquisitions Staff for ordering and check-in activity. The ISSN is also used by many publishers to construct a link to online versions. Note that in this example, US ISSN catalogers would enter first indicator 0; the rest of us enter first indicator blank. - Add the ISSN appearing on a piece in hand to the record if it is not already there. - Enter a valid ISSN in the 022 field, subfield $a. For non-US ISSNs, assume that an ISSN is valid unless you have evidence that it is invalid or inappropriate for the publication in hand. For US ISSNs, use the ISSN Portal to verify the ISSN. - Note that the ISSN is sometimes printed incorrectly on pieces and it is worthwhile to verify it. In many cases, an ISSN may refer to a portion of a serial that appeared under an earlier title. If the publisher or printer has printed an incorrect ISSN on the serial, enter it in subfield y. - [Verification tools: The definitive tool is the ISSN Portal, for those with subscriptions. For open access e-serials, a free resource is the ISSN ROAD service. If you are working in a system that does validation such as OCLC, a structurally incorrect ISSN will be automatically recoded to subfield $y. Other subfields: $z represents a canceled ISSN. $ℓ [el] contains the linking ISSN, which collocates ISSNs across media types. $m represents a canceled linking ISSN. $2 shows the code for the ISSN Center. The title represented here is: Library Journal SCCTP Basic Serials Cataloging Workshop

Variant titles Coding for CONSER Standard Record: 245 00 $a Title.
246 1# $i Issues for … have title: $a [later title] 246 1# $i Issues for … have English title: $a [later parallel title] 246 1# $a [variant title] $f <Nov > Example Note: Session 8 covered major/minor changes in titles of serials more fully. Minor title changes ( , ) , parallel ( ), and variant titles ( ) But just as a reminder, this slide shows the general pattern for coding minor changes of title, changes to parallel titles, and title variants appearing on later issues. $a Géologie de la France. 246 1# $i Issues for have title: $a Géol. Fr. 246 1# $i Issues for have also English title: $a Geology of France and surrounding areas 246 1# $a GFSA $f <1995> -1999 SCCTP Basic Serials Cataloging Workshop

Variant titles, examples
$a Annual report. 246 1# $a NAVISTAR annual report $f 1990- “Minor” variations in title proper $a Openhouse. 246 1# $i Issues for have title: $a Open house SCCTP Basic Serials Cataloging Workshop

Parallel titles Parallel titles (CSR): 245 00 $a Groundwater series.
$a Grondwaterreeks 500 ## $a Order of titles varies with language of text. $a Electric power in Canada. 246 1# $i Issues for have also French title: $a Energie électrique au Canada If the order of parallel titles changes but the title proper still appears on the piece, this is not a major title change You may, however, want to make a 246 title added entry for parallel titles not already accounted for or for any new ones that appear. - The first example on this slide shows fields from a CONSER standard record where the title has always appeared both in English and Dutch. The language of the text alternates between English for one issue, Dutch for the next; and the order of titles switches accordingly. - In the second example, the chief source of the serial showed the title in English: Electric power in Canada. Then, beginning in 1969, the chief source included the title in both English and French. SCCTP Basic Serials Cataloging Workshop

Fluctuating titles $a Knitting times # $i Some volumes, have title: $a Knitting times newsweekly 246 1# $i One issue each month, Mar. 24, has title: $a Apparel world $a TIMS/ORSA bulletin # $i Alternating issues called: $a ORSA/TIMS bulletin Fluctuating titles are a special type of title variation. Such titles are commonly encountered with newspapers, which tend to use special terms for weekend issues, e.g., “The Sunday Times” - These are not major title changes, but you will want to account for the variations by making a 246 title added entry (see LCRI 21.2C). Such added titles help processing staff and patrons find and identify publications. [This slide shows spelled-out form in recorded note: Some volumes… The cataloger could also use the abbreviation from RDA Appendix B7: “v”] - Note that it is often difficult to recognize a fluctuating title as opposed to a major title change unless you have evidence from more than a single piece in hand or the publisher explicitly states that, for example, alternating numbers will have different titles. SCCTP Basic Serials Cataloging Workshop

Pop Quiz! $a Publicaciones del Observatorio del Ebro. Beginning with volume 47, published in 2012, a parallel title also appears in English: Publications of the Ebro Observatory How could you edit the record to include this title? SCCTP Basic Serials Cataloging Workshop

Possible response 245 00 $a Publicaciones del Observatorio del Ebro.
246 1# $i Volumes for have also English title: $a Publications of the Ebro Observatory Note that even though this is a parallel English-language title, it did not appear on the issue used as the basis for description. Therefore, the 246 indicators are “1#” rather than “11” SCCTP Basic Serials Cataloging Workshop

Issuing body ( ) CONSER practice: [introductory word(s)]: [information], [dates] Example 550 ## $a Issued by: Bureau of Vital Statistics, 1964–1977; by: Bureau of Vital Records, 1978– CCM promotes a preferred style that makes it easier for future record maintainers to extend the note. While this preference was developed prior to RDA, the examples in RDA also illustrate this model. SCCTP Basic Serials Cataloging Workshop

Issuing body ( ) 550 ## $a Issued by: Bureau of Vital Statistics, 1964–1977; by: Bureau of Vital Records, 1978– 710 1# $a Alaska. $b Bureau of Vital Statistics. 710 1# $a Alaska. $b Bureau of Vital Records.

Series $a Cool stars, stellar systems and the sun. 264 #1 $a [Cambridge, Mass.] : $b Smithsonian Astrophysical Observatory 310 ## $a Biennial 362 1# $a Began with Jan. 31, # $ : $a SAO special report 490 1# $ : $a Lecture notes in physics 490 1# $ : $a Astronomical Society of the Pacific conference series 830 #0 $ : $a SAO special report. $x #0 $ : $a Lecture notes in physics. $x #0 $ : $a Astronomical Society of the Pacific conference series. $x Similarly, changes to series should include information about the dates that each series appeared on the publication. - If a serial is issued in a series and ceases to be issued in that series, note this in a 490 field. (Per RDA 2.12, Series statements are Core.) Giving series access points [i.e., added entries] or not is a local policy decision. - If the serial appears in a succession of series, note this in multiple 490 fields along with the inclusive dates. Trainers note: Since 2008, the 440 field for series has been obsolete. In addition, MARC21 8XX fields now include a subfield $3 that may be used to indicate volume coverage (the equivalent to “ $a :” in the slide above); and include a subfield $x for ISSN. In the rare case where a series entry would include volume numbering, give the volume and then the ISSN, e.g.: -0 $ : $a SAO special report ; $v no. 3. $x [per CONSRLST discussion, Aug. 2009] Redundancy of dates in $3 490 and 830 on slides: may not be necessary to add dates in both the 490 and the 830. Since 490 series statement is required, it probably only needs to be entered in 490. SCCTP Basic Serials Cataloging Workshop

Publisher change (2.8, 2.17.7) Reminder: Existing:
260 ## (if 260 is present, leave tag as-is) OR 264 #1 (for RDA record created after August 2011) Add: $3 Coverage New: (intermediate) (most recent) $3 Coverage [recorded] $a Place : $b Publisher [transcribed] $c Date (if ceased) [transcribed] Publisher/distributor/manufacturer/copyright: Beginning in September 2011, CONSER catalogers have been using the 264 field to code publisher, distributor, and manufacturer data If the data coded in the 260 field has changed, and if the role of the body named is known AND if the cataloger knows that the RDA rules for transcription have been followed, the cataloger may choose to recode the 260 field to a 264 field. If the role is not known, then the cataloger would leave the tag as 260. Also: For simplicity, the current screen shows coding just for the publisher statement. Distributor data would be coded in a 264 field with second indicator 2; manufacturer data would be coded in a 264 field with second indicator 3. There is also a second indicator 4 for copyright data; but for serials, copyright data is less commonly coded. Let’s try this out. Additional note: RDA 2.11 LC-PCC PS: LC Practice for core element: It is not required to record copyright dates for multipart monographs, serials, and integrating resources. SCCTP Basic Serials Cataloging Workshop

Place/Publisher Country of publication: mdu $a Camera obscura. 264 #1 $ : $a Berkeley, Calif. : $b Camera Obscura Collective $3 <May 1990-> : $a Baltimore, MD : $b Johns Hopkins University Press 362 1# $a Began in 1976. Edits Important for Serials Control - Country of Publication Code (fixed field) -- If the piece in hand contains a later place of publication on it than appears in the cataloging copy, do not change the 264 subfield “a” place of publication. Instead enter a $3 to the 264 field with the date/numbering range and add a second 264 field with first indicator 3 (latest imprint), if it is considered important. -- Additionally, change the country of publication code in the fixed field to correspond to the current country of publication even though that means that it does not match the 264 subfield “a” information. -- In the example, the place of publication changed to Bloomington, Indiana in This change is noted in a second 264 note and the Country of Publication fixed field is updated. How would you change the record for Camera obscura based on this information? Note that the first indicator for intermediate 264 fields is “2” and that the order of fields is earliest to most recent. Trainer’s note: On Sept. 1, 2009, CONSER implemented repeatable 260 fields. First indicators: “Blank” = Not applicable, no information provided, or earliest available publisher; no information provided; earliest available publisher 2 = Intervening publisher 3 = Current/latest publisher New subfield $3 = Materials specified Multiple 260 fields are listed in chronological order, earliest to most recent The last issue of Camera obscura published in MD was: Sept Beginning Jan. 1992, it was published in Bloomington, IN by Indiana University Press. SCCTP Basic Serials Cataloging Workshop

Place/Publisher Country of publication: inu $a Camera obscura. 264 #1 $ : $a Berkeley, Calif. : $b Camera Obscura Collective $3 <May 1990> -Sept. 1991: $a Baltimore, MD : $b Johns Hopkins University Press $3 Jan : $a Bloomington, IN : $b Indiana University Press 362 1# $a Began in 1976. In this case, a 264 field is added to record the change in place and publisher. Note that the publisher information is important to record so long as it appears to be important to identification of the publication. If the place/publisher change very frequently, the cataloger may decide that this data is less likely to be useful in identification. In that case, a note may be used: Imprint varies. However, the fixed field should still be coded for the most current place of publication. SCCTP Basic Serials Cataloging Workshop

Exercise: Publisher Fixed field: 008/15-17 (Ctry): nyu The journal Cognitive dissidents began in 1987, but the first issue received by the library was for Volume 1, number 5 Nov 15, Note that “Nov” appeared that way on the issue. Later, the library received more issues, though not a complete run. The earliest issue showing a move of the publisher to Tonawanda was “February 1990”; and the earliest issue showing that the publisher moved to Las Vegas had a coverage date of February The last issue received by the library was for Volume 7, issue #1 with coverage date May 15, 1993. After this record was created, the cataloger received some additional issues (though not a complete run). Here are some changes discovered: --By the “February 1990” issue, the place of publication moved to: Tonawanda, NY --By the “February 1991” issue, the place of publication moved to: Las Vegas, NV The Raving Lunatic Society remained the publisher throughout the life of the serial. The latest issue received was: Volume 7, issue #1 (May 15, 1993). How would you show this information? --By the “February 1990” issue, the place of publication moved to: Tonawanda, NY --By the “February 1991” issue, the place of publication moved to: Las Vegas, NV The Raving Lunatic Society remained the publisher throughout the life of the serial. The latest issue received was: Volume 7, issue #1 (May 15, 1993). SCCTP Basic Serials Cataloging Workshop

Exercise: Publisher change (2)
Fixed field: 008/15-17 (Ctry): nvu Possible answer. Recording the change to Tonawanda is cataloger judgment, since the state did not change from New York. But the change to Las Vegas should be recorded since it involves a different state. Note that currently, there is no requirement to change a 260 if the original record has data coded in a 260 field. In any case, a subfield $3 materials specified note would be added to the beginning of the field. Then additional 264 fields would be added. SCCTP Basic Serials Cataloging Workshop

Numbering (2.6.1, 2.17.5) Coding: Partially transcribed
Reminder: If numbering starts over without series designation, supply [new series] Options: 362 1# $a If have first/last in range 515 ## $a In all situations Example 1 362 1# $a Began with: No 7 (année judiciaire 1998/1999); ceased with no 13 (année judiciaire 2004/2005). Example 2 362 1# $a Began with December 1971. 515 ## $a Issues for <May 2010-> called: <2nd series, volume 1, issue 5-> The RDA instructions for when to record numbering changes follow the previous CONSER practice. How to record the numbers themselves has changed, as we saw in an earlier module (Module 4). The first example illustrates a cessation. (introduced in Module 8) The second example illustrates a new series, where the cataloger lacked the first issue of the series. The issue in hand is shown in angle brackets. Note that spacing conventions for angle brackets have changed somewhat. See LC/PCC PS 1.7.1 [If a further review is needed: The change is that numbering, even in a note field, is given in a modified transcribed form. That is, captions such as “volume” and dates such as “February” are spelled out if found that way on the issue. However, as was also mentioned in session 4, numbers themselves are given in numerals if they appear as spelled out; and ordinal numbers for European language serials may appear with a numeral plus period (e.g., 2. for segundo)] For Trainers: see: RDA 2.6.1, 1.7, 1.8 and LC/PCC PS RDA : If a new sequence with the same system as before is not accompanied by wording such as new series, supply new series or another appropriate term. Indicate that the information was taken from a source outside the resource itself as instructed under SCCTP Basic Serials Cataloging Workshop

Numbering changes = Minor!
Use 362 or 515, whichever is clearer Example 1: 362 1# $a Began with: volume 1, number 1 (Jan. 1960); ceased with volume 5, number 6 (June 1964). New series began with volume 1, number 1 (July 1964). Example 2: 362 0# $a Vol. 1, no. 1 (Jan )-v. 5, no. 6 (June 1964) ; [new ser.], v. 1, no. 1 (July 1964)- If new numbering scheme: Example 3: # $a Began with: no. 1; original numbering ended with no. 15. New numbering began with v. 1, no. 1, published in 1964. Changes in numbering and numbering schemes can be accounted for in either a 362 or in a 515 note, whichever is clearer. The 1st example represents CSR practice and the 2nd example conforms to AACR2 practice- the record was not converted to RDA. Here is a good side-by-side comparison of RDA CSR v. AACR2 practice. The CSR example should be more understandable and less likely to be confused with a library’s holdings. In the 3rd example, the serials starts a new numbering scheme. When numbering system (field 362) repeats and the serial does not use “new series,” “second series,” etc. supply such wording according to RDA Guidelines. SCCTP Basic Serials Cataloging Workshop

Frequency ( , ) Coding: Recorded; CONSER practice: keep all 310 ## $a Frequency, $b coverage [current] 321 ## $a Frequency, $b coverage [oldest] 321 ## $a Frequency, $b coverage [next] CONSER practices for recording changes to frequency have not changed since the CONSER Standard Record guidelines were first issued in Catalogers still code current content in the 310 field and earlier frequency (from earliest to most recent) in sequential 321 fields. In contrast to CONSER practice when creating original records, CONSER practice for maintenance is still to keep all historic data unless it is inaccurate. SCCTP Basic Serials Cataloging Workshop

Frequency Move re-tagged note to position as last 321 note
310 ## $a Weekly, $b Mar 321 ## $a Biweekly, $b 1989-Feb. 2007 Retag existing frequency note from 310 to 321 Move re-tagged note to position as last 321 note -- Enter current frequency in 310 field, with $b to show dates -- Add subfield $b to both 310 & 321 to show dates. Frequency field: --Serials often change publishing frequency. When maintaining a record, the cataloger should move the out-of-date frequency from the 310 field to the last 321 field and add “…, $b [date range for frequency]”. Then code the new frequency in the 310 field. Note that there is no limit to the number of 321 fields allowed. (Before July 2007, cataloging practice limited the number of 321 fields in a bib record. The 2010 CSR guidelines removed the limit.) --Fixed field: If the fixed field elements Frequency and Regularity are fill characters, the cataloger may leave them. Otherwise (i.e., if the elements were coded according to past practice), either maintain the fixed field characters according to the code for the current frequency (310) or change them to fill characters during record maintenance. Do NOT leave obsolete coding in these fixed field elements. [The next shows these two options] [Trainer’s note: In contrast with record maintenance, when creating a record, the cataloger has TWO options. First, the cataloger may record the history of frequencies. Second, the cataloger may choose to record only the latest frequency. If following the second option, prefer to record the date range (310 $b) when the 310 frequency does not represent the whole range of issues. (Note: This is a change from pre-2007 practice and has not yet been included in CONSER documentation as of 1/7/2008.) E.g.: 310 ## $a Weekly, $b Mar ] SCCTP Basic Serials Cataloging Workshop

Frequency (continued)
Fixed field: Freq w OR Freq ■ Regl r Regl ■ 310 ## $a Weekly, $b Mar ## $a Biweekly, $b 1989-Feb. 2007 (Change, 2/2010: NSDP now US ISSN) This slide displays the fixed field options, for a record that originally had Fixed Field elements Frequency and Regularity coded. How does this work in practice? Let’s see… Trainer’s note: Records created by US ISSN catalogers include Fixed Field elements Frequency and Regularity; CONSER participants will maintain these elements. The Fixed Field codes affect record movement from OCLC to the ISSN database. SCCTP Basic Serials Cataloging Workshop

Frequency: What are the options?
Bibliographic record has: Fixed field Frequency: ■ Fixed field Regularity: ■ ## $a Semiannual 362 1# $a Began in 1990. Publication history: Semiannual through Dec Quarterly, Jan to Dec Monthly, Jan to June Bimonthly, July/Aug to Nov./Dec Annually, since 2003. Is this an AACR2 record or a CONSER standard record? What are your options in completing maintenance for this record? SCCTP Basic Serials Cataloging Workshop

Frequency: CSR Fixed field Frequency: ■ Fixed field Regularity: ■
310 ## $a Annual, $b 2003- 321 ## $a Semiannual, $b 321 ## $a Quarterly, $b 321 ## $a Monthly, $b 2000-June 2001 321 ## $a Bimonthly, $b July/Aug Catalogers following the CONSER standard record guidelines should record all frequencies. Reminder 1: Catalogers no longer need to delete frequency history and use “321 Imprint varies” when recording more than three frequency notes. Reminder 2: Since the original record had Frequency & Regularity coded as fill characters, there is no need to edit these elements. SCCTP Basic Serials Cataloging Workshop

Related manifestations (27.1)
Prefer: $i Issued also on CD-ROM: $t APIS $w (DLC) $w (OCoLC) Use as appropriate: 530 ## $a Issued also on CD-ROM. When enhancing an AACR2 record or a CONSER standard record to show other formats (e.g., CD-ROM), prefer to include the note in the 7XX linking field. If no 7XX linking field is possible, the cataloger may use a 530 note. In some cases, the cataloger may know that an alternate format exists, but may not know the title. (Do not assume that the title will be the same in all formats. In the case of the CD-ROM serial APIS, the print version has the title: Annual poverty indicators survey.) SCCTP Basic Serials Cataloging Workshop

Other considerations CEG B4 588 ## $a Latest issue consulted: … .
FF Dates: If most recent issue (or known issue) is older than 3 years: 008/06 (Status): u 008/11-14 (Date2): uuuu Basis of identification: If have later issue than was previously been entered: 588 ## $a Latest issue consulted: … . 588 ## $a Latest issue consulted: … (publisher’s website, viewed …). When maintaining records, the CONSER practices regarding maintenance of Fixed Field elements and entry of a Latest issue consulted note still apply. We have completed our consideration of RDA changes at the manifestation level. Now let’s turn our attention to Expression-level change… SCCTP Basic Serials Cataloging Workshop

Expression-level change (7.29.2.3)
So far, ALL changes can be accommodated Types of change common to serials: Language Script Examples: 546 ## $a Volumes 1-3 in French, volumes 4-7 in German. 546 ## $a In Azerbaijani (Cyrillic), <1999->; (Latin), < > While OCLC CONSER records in MARC have always included expression-level data, RDA considers this data explicitly. So far, RDA instructions related to serials and integrating resources only address expression-level changes that can be accommodated in the existing description. Please keep in mind that this situation, where the title is constant but the language (or script) of the content changes, is different than the more common situation where a serial undergoes a major change of title at the same time that the language changes. A major change of title requires a new description for a serial per (with ). Additional note: For the benefit of the trainer, here is the text of Multipart Monographs and Serials: If a content characteristic is changed in a subsequent issue or part, make a note if the change is considered important for identification or selection. If the changes have been numerous, a general statement may be made. Integrating resources: Make notes on content characteristics no longer present on the current iteration if the change is considered important for identification or selection. If the changes have been numerous, a general statement may be made. SCCTP Basic Serials Cataloging Workshop

Work-level change (Chapter 6)
Parallel language titles appearing on later issues ( ) Variant titles that differ significantly from the preferred title and might reasonably be sought ( ) Nature of the content ( ) Work-level records may also accommodate change. In our current environment, catalogers may not be aware of the elements of the record that contribute to enhancing the work-level description. The most common work-level enhancement that catalogers will be making is to record minor changes to the title proper, parallel language titles, and variant titles that appear on later issues. SCCTP Basic Serials Cataloging Workshop

Hybrid: Editing AACR2/CSR records
Documentation: Post RDA Implementation Guidelines and Standards : May follow RDA conventions to maintain AACR2/CSR records May add (or add to) fields Should create RDA NARs if additional name headings are needed (e.g., issuing body) Many changes can be made without re-describing serial using RDA These bullet points reflect guidelines for editing AACR2/CSR records. Final report of the PCC Post-Implementation Hybrid Bibliographic Records Guidelines Task Group (chair, Gene Dickerson): The final report of the Post-Implementation Hybrid Records Task Group was approved February 2013. (Pre-RDA records edited may reflect pre-Implementation Guidelines reflected in the interim report, available from the same website) In addition to changes in issues, without removing the General Material Designator (245 $h), catalogers may add fields. Finally, a word about re-description. In most cases, as has been noted, catalogers should be able to build on the existing record. However, there are a few cases where re-description may be warranted. If the cataloger would need to cease the record and begin a new description solely due to pre-RDA cataloging rules, then consider re-describing the serial. The most common case of this is where a legacy record has a 110 field with a corporate body, but under RDA would have a work authorized access point based on title. As always, local institutional policies may also come into play. SCCTP Basic Serials Cataloging Workshop

Exercise: CSR record maintenance
FF: LDR/18 (Desc) = a 008/18-19 (Freq/Regl) =q/x /15-17 (Ctry) = nju Take a few minutes to consider this exercise. What enhancements could/should be made to reflect this issue? This AACR2 record is coded 042=pcc FF: Ctry: pau 264 #1 $ : $a [if the College is considered to be acting as a publisher] $3 <2012-> : $a Philadelphia, PA : $b Taylor and Francis 310 ## $a Five times a year, $b <2012-> 321 … 321 # # $a Four no. a year, $b 1970- 588 ## $a LIC: Volume 87, issue 4 (2012). Could also add Issue : Volume 87, issue Philadelphia, PA * Taylor and Francis * Published 5 times a year SCCTP Basic Serials Cataloging Workshop

FF: LDR/18 (Desc) = a 008/18-19 (Freq/Regl) =q/x 008/15-17 (Ctry) = pau
Here is one possibility. Note that the FF: Ctry: pau 260 ## $ : $a [if the College is considered to be acting as a publisher, cataloger could also re-code to 264] $3 <2012-> : $a Philadelphia, PA : $b Taylor and Francis 310 ## $a Five times a year, $b <2012-> 321 … 321 # # $a Four no. a year, $b 1970- 588 ## $a LIC: Volume 87, issue 4 (2012). Could also add NOTE: Participants may wish to discuss whether CONSER should establish some sort of practice regarding the 500 Published: note (recognizing that some of these notes lack adequate information to convert.) SCCTP Basic Serials Cataloging Workshop

Summary All PCC records may be maintained using RDA and CONSER RDA practices Enhancements for accuracy and current data add value for end users and staff Valued enhancements include ISSN Variant titles, issuing bodies, subjects Cessations --CONSER no longer requires catalogers to maintain records using the code under which they were created. Catalogers may use RDA to maintain all successive entry records. (Latest Entry records are excluded) --In many cases, records can be used as-is. Unless local policies require it, there is no need to edit records just to “modernize” the style, e.g., punctuation. However, in those cases where discovery (find) or identification would be enhanced, catalogers should consider enhancing records. --Some of the most common reasons catalogers enhance records (in addition to correcting typos) include the addition of identifiers, recording data elements that change during the life of the serial; and serial cessation. The CONSER Editing Guide and CONSER Cataloging Manual (CCM) are excellent sources of information on how to edit serial records. SCCTP Basic Serials Cataloging Workshop

9: Identifying Appropriate Copy

Similar presentations

Presentation on theme: "9: Identifying Appropriate Copy"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

9: Identifying Appropriate Copy

Similar presentations

Presentation on theme: "9: Identifying Appropriate Copy"— Presentation transcript:

Similar presentations

About project

Feedback