# Presentation: 695964

## CONSER Standard Record   Quick Review

- By:

## Current resources www.loc.gov/acq/conser

- Complete Power Point Presentation
- Cataloger’s Cheat Sheet
- Documentation
- Metadata Application Profile (MAP)
- Appendices
- Decision-making guidance
- Working with copy/record maintenance

**Notes:**
The CONSER standard record documentation consists of:
  -- an introduction that summarizes the development, purpose, and structure of the guidelines
  -- a discussion of general principles
  -- field-by-field instructions (the Metadata Application Profile, or MAP)
  -- Appendix A, which discusses such difficult questions as how to create a corporate name heading; and how to decide if a word in a title is a “resource type” (in order to determine if a title change is minor)
 -- Appendix B, which shows examples of serial bib records created according to the MAP; and examples of numbering complexities

##  General principles

- Metadata Application Profile (MAP) identifies mandatory data elements
- Additional data elements *may* be added
- Specialized resources = specialized treatment
- Existing copy **not** changed unless incorrect or information outdated
- New records maintained to new standard
- Records may contain a mix of old and new practices (as always)

**Notes:**
Let’s talk about some of the general principles of the CONSER standard record:
There are certain data elements that are required in the CONSER standard record. They are identified and explained in the Metadata Application Profile (MAP). The MAP also explains how to apply all other optional data elements, which can also be added if required by the resource or the institution. For example, specialized materials (for example, newspapers or vernacular-language serials) may require additional data elements. Cataloging communities for specialized materials have already begun to discuss “best practices” for how to adequately provide access for these special kinds of resources.
Existing cataloging copy should not be changed to reflect the new standard. Only errors and outdated information should be changed. New records, however, should be edited according to the guidelines for the CONSER standard record.

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.

[Helpful hint for Instructor: In anticipation of any questions re: editing pre-AACR2 records, see CCM Modules 21 and 22 and CEG Section B, Policies for guidance in editing pre-AACR2 records. For example, from CEG B.4.2.4: “With the exception of updating headings to currently valid forms, changes to pre-AACR2 records should be made only in the context of the cataloging code under which the record was created.”]

##  If in doubt ...

- Follow the general principles
- Do what makes the most sense
- Do what you’ve always done (unless guidelines instruct otherwise)
- Exercise your cataloger’s judgment!

**Notes:**
Here are some wonderful words of wisdom from Regina Reynolds, the co-Chair of the CONSER Working Group that developed this new standard. Follow these simple steps whenever you find yourself wondering what to do next, and remember that one of things particularly emphasized by the CONSER standard record is the use of common sense and judgment in applying cataloging guidelines.

##  What’s the same?

- Main entry
- Title proper
- Edition statement
- Place of publication
- Publisher

- Current frequency
- Numbering area (unformatted)
- Subject headings
- Most added entries
- Most linking fields

**Notes:**
Let’s take a look at what’s the same in the CONSER standard record.
As we can see from this checklist, the CONSER standard record, in essentials, contains the elements that users have come to expect in a CONSER record. 
Before we go on to talk about what’s different, remember that elements that are not required in the CONSER standard record can still be added depending upon the needs of the particular resource or the cataloging institution.

##  What’s different?

- Simplification
- Fixed field, 006, 007, other MARC fields
- Coding of indicators for 246 field
- Authorized access points vs. transcription and/or notes
- Limited use of differentiating uniform titles

**Notes:**
The CONSER standard record simplifies the coding of some rather esoteric elements in the MARC 21 format, including selected parts of the fixed field, the 006 and the 007. Coding for variant titles in the 246 is also simplified.
The CONSER standard record emphasizes controlled access rather than extensive, and sometimes redundant, transcription of descriptive elements. For example, as long as the added entries for corporate bodies are backed by name authority records in the LC/NACO Authority File, statements of responsibility and issuing body notes are not required. 
Without name authority work, however, a cataloger can’t take advantage of some of the simplification, and therefore must transcribe statements of responsibility or add issuing body notes. In this way, transcription takes the place of an authority record, and so ensures that the catalog record, either alone or in combination with an authority record, will still contain what users need.
Guidelines for the CONSER standard record also simplify the situations in which differentiating uniform titles will need to be applied.
[Note: LCRI for 25.5B has been revised – this is the RI that established the usage of the differentiating uniform title for serials.]

##  What’s different?

- Numbering
- Numbering statement in note format (362)
- Always a “Description based on” note
- Always a source of title note (even if t.p.)
- Standard abbreviations not required

**Notes:**
CONSER standard record guidelines recommend that whenever the cataloger has information regarding the first and/or last issue of a serial, it is entered in a 362 unformatted note (first indicator “1”). Because another cataloger interpreting the record will not know whether the original cataloger had the first issue in hand, a “description based on” note is always required. In effect, the formulation of cataloger’s notes is no longer dependent on having the first and/or last issue in hand. The source of title note is also always required, even if the title is taken from a title page.
The CONSER standard record will always have the same types of notes regardless of the issue being cataloged and the chief source of information used on that issue.
In addition, the cataloging guidelines for the CONSER standard record allow the cataloger the option to transcribe all numbering statements just as they appear on the piece.

##  Why change numbering?

- Clarity
- Consistency
- Efficiency
- Ease of training

**Notes:**
OK, I know I said earlier I wasn’t here to argue the merits of the CONSER standard record, but ...
Here are some good reasons to simplify the transcription of numbering, and these reasons reflect the Working Group’s analysis (within the FRBR context) of this area of the description, together with anecdotal evidence and feedback from both catalogers and reviewers. The redesign of the numbering area also reflects the basic objective of the CONSER standard record, which is to save time and trouble for serials catalogers and other users of serial records.
Depending on how the formatted 362 is displayed in various OPACs, users can often confuse it with a holdings statement about what the library actually owns.
Always providing the catalogers’ notes in the same way eliminates steps in the cataloging decision tree and contributes to a more uniform-looking serial record. Other catalogers editing a record for changes don’t have to wonder things like “was there truly a title page or did they just forget to put the source of title note?” Consistency of notes in turn allows for easier training of new serials catalogers, who no longer need to learn “the secret handshake” of first-issue-in-hand vs. other-issues-available. *
Looking up standard abbreviations for dates and numbers was reported by catalogers as one of the most time-consuming activities that resulted in one of the least useful results.

(* Special thanks to Steve Shadle of the University of Washington for this most excellent analogy.)

## “CSR” and “AACR2” 

- CONSER standard record cataloging is an application of AACR2 cataloging
- Examples labeled “CSR” show CONSER standard record application of AACR2
- Examples labeled “AACR2” show elements beyond the requirements of “CSR”

**Notes:**
Trainer’s Note: Please make sure that everybody understands that CSR is an application of AACR2. It is the minimum set of requirements for a CONSER-authenticated record, but catalogers can go beyond basic CSR requirements when needed. In this workshop, for shorthand purposes, we have labeled the examples either as “AACR2" or “CSR" to distinguish the full range of AACR2 elements that could be added to a record and the elements that meet basic CSR requirements. 
The CONSER standard record is fully supported by LCRIs, just as with other LC and PCC policies and practices.

##  Fixed field

**Notes:**
Here we see the fixed field for a CONSER Standard Record. Do you notice anything that looks different to you? 
The bytes for Conference Publication, Frequency, and Regularity have default values of “fill character.” Catalogers are no longer required to code these elements. [OCLC has updated the record validation profile to allow these characters to validate. The bolded data elements continue to be required. 
Note that “Form of Original Item” (Orig) is italicized. That is because this element is mandatory only for serials originally published as microforms. [However, fill character not yet in OCLC – so code e-only resources as “blank” for now!]One last point: The content elements “EntW” (Nature of the entire work) and “Cont” (Nature of contents) are NOT bolded; that’s because they are now optional.

##  006 and 007 fields

- Mandatory: only first byte of 006
- Form of material
- Mandatory: only first two bytes of 007
- Category of material
- Specific material designation

- 006    [m                        ]
- 007   $a c $b r

**Notes:**
Coding for the 006 and 007 fields has been simplified. In this example, coding for a remote-access electronic serial would only have to contain the following:
 006 code “m” computer file/electronic resource (=first byte)
   007 $a “c” for electronic resource and $b r for remote access

Notes: 
Additional subfields may be required for preservation microforms (as of May 2007, subfield $e “Dimensions” is needed for microforms to pass OCLC record validation).
As of Sept. 2008, OCLC validation required code in 006/09 (usually ‘d’)

## AACR2 – Basis of description

**AACR2 – Basis of description**

- If first issue:
**Do**  362 0-  Formatted numbering statement
-  	362 0-  No. 1 (June 1936)-
**No  **500 “Description based on” note
- If not first issue:
**No  **362 0-  Formatted numbering statement
**Do**  500 “Description based on” note
- If not first issue, **but*** *have information:
**Do****	**** **362 1-  Unformatted numbering statement (note)
**Do**  500 “Description based on” note
- 500 --  $a Description based on v. 14, no. 3 (Dec. 1998).

**Notes:**
If you are strictly following AACR2, the existence of certain notes and MARC tags for serials cataloging depend on the issues available.

In AACR2 cataloging, if you have the first issue in hand, your 362 is in what is called a “formatted” style: first indicator = “0” and the volume/date designations (no note). (AACR2 cataloging also uses the unformatted 362, but only in certain circumstances.)

In AACR2 cataloging, you only need to state the source of description if it is not the first issue. (The existence of the 362 formatted field implies that the first issue was in hand.)

## CSR – Basis of description

**CSR – Basis of description**

- 	The first issue, but if that’s not available the earliest issue in hand:
**	****Do**  362 1-  Unformatted numbering statement
- 		362 1- $a Began with v. 1, no. 1 (May 2002).
**	****Do**  500 “Description based on” note
- 		500 --  $a Description based on: Vol. 14, no. 3
- 		(Dec. 1998).
- 		500 --  $a Description based on: Vol. 1, no. 1 (May
- 		2002).

**Notes:**
Developers of the CONSER Standard Record recommended exclusive use of the 362 unformatted style note, because it is less likely to be mistaken for a statement of the library’s holdings.

## Noting chief source 

**Noting chief source**** **

**CSR**
- 	Note chief source, even if title page, and  combine with “Description based on” note:
- 500 -- Description based on: Vol. 1, no. 1 (Jan. 2001); title from cover.
- 500 -- Description based on: Jan. 2003; title from t.p.
- 500 -- $a Description based on first and only issue; title from caption.
**AACR2**
- 	Note chief source only if it’s **not **title page
- 500 -- Description based on: Jan. 2003; title from cover.

**Notes:**
As with the “Description based on” note, CSR guidelines direct that catalogers always note the chief source used for the title, even if it is the title page. For AACR2 cataloging, a source of title note is only required if the chief source is not the title page.
Compare the differences in the notes between CSR and AACR2 practice:
First example: First issue in hand, so no DBO note needed for AACR2
Second example: Title is from title page, so no source of title note needed for AACR2
Although there are more required notes for the CSR, the requirements are consistent from record to record, which makes it easier to train new catalogers. In effect, the inclusion of cataloger-type notes regarding the issue(s) consulted and the source of the title is no longer dependent on what the cataloger has in hand.

## Other title information

- Transcribe if considered useful:
- To clarify the title proper
- 	245  00  $a Focus : $b a journal of legal studies.
- 				*or*
- 	245  00  $a Focus.
- 	500  --    $a “A journal of legal studies.”
- To “explain” the title proper (LCRI 12.1E1)
- 	245  00  $a Nature Conservancy : $b [newsletter].

**Notes:**
Generally, other title information is not included in serial records unless it helps to clarify or in some way support the title proper. The subtitle is usually omitted because it can change frequently; however, when the title proper is very general, catalogers have a choice of including it. Transcribe the subtitle as other title information (245 $b) or as a quoted note (500). Decision is cataloger’s judgment.
Supplied other title information may be needed to explain the title proper, as in the case here where the title consists only of a name of a corporate body.
There is no preferred way to handle other title information, although the guidelines for the CONSER standard record limit the cases where such information is necessary in the catalog record. This is an example of one of the areas where cataloger’s judgment comes into play.

## On title page:

- 245 00  $a Rain clouds.
- 245 00  $a Rain clouds : $b journal of poetry and pessimism.     245 00 $a Rain clouds.
- 246 13 $a Journal of poetry and pessimism
- 245 00 $a Rain clouds.
- 500 --  $a “Journal of poetry and pessimism.”

- Rain Clouds
- Journal of Poetry and Pessimism

**Notes:**
In the case of “Rain Clouds” which options would be valid within the guidelines of the CONSER standard record?
[Answer: all four options are correct.]
That’s correct -- all might be valid ways to treat this other title information.

## Variant titles - 246

- Record all variant titles as usual
- Parallel titles/acronyms = “variant titles”

| Parallel titles from chief source |  246 11 |
| --- | --- |
| Other variant titles
(including initialisms/acronyms) |  246 13 |
| Minor title changes
(including parallel titles found on later issues) |  246 1_ $i ... : $a |

**Notes:**
This slide summarizes the 246 coding for variant titles. Record parallel titles with indicators 11 and initialisms/acronyms not chosen as the title proper with indicators 13. Record minor title changes as 246 1_ with a subfield $i Issues for [dates] have title: $a [minor title change]. (Also use this convention whenever you need to generate a note regarding the variant title.) All other variant titles may be coded 246 13.
Record variant titles that appear prominently in the resource being cataloged, and which a user might reasonably consider to be the title. Do not spend a lot of time looking for information buried in the text of the item that could possibly be considered a variant. 
For online serials, generally consider recording as variant titles only those titles appearing in readily accessible sources (for example, those that can be accessed within one or two pages from the earliest issue’s title page or title screen by clicking on a prominently displayed icon or menu choice on a home page or a main menu page). [Instructor’s note: Many e-serials catalogers have already been following this practice; the guidelines affirm it as a best practice.]

## Variant titles: CSR vs. AACR2

- Initialisms/acronyms:
- 	245 00 Cataloging world.
- 	246 13 CW			**CSR**
- 	245 00 Cataloging world : $b CW.
- 	246 30 CW			**AACR2**
- Parallel titles:
-    245 00 Annual review.
- 	246 11 Rapport annuel	**CSR**
- 	245 00 Annual review = $b rapport annuel.
- 	246 31 Rapport annuel	**AACR2**

**Notes:**
According to guidelines for the CONSER standard record, record initialisms/acronyms not chosen as the title proper in 246 13 (AACR2: would be coded in 245 $b). Record parallel titles as 246 11 (AACR2: would be coded in 245 $b).

## CSR on variant titles - 246

**CSR on variant titles - 246**

- Titles that appear elsewhere on issue:
- 245  04  $a The miner & workman's advocate.
- 246  13  $a Advocate                     [cover title]
- Other forms of the title:
- 245  04  $a The miner & workman's advocate.
- 246  13  $a Miner and workman's advocate
- Parallel titles:
- 245  00  $a Japan report.
- 246  11  $a Nihon

**Notes:**
Title added entries are generally made for other titles that the publication might bear (cover title, fluctuating titles, parallel titles, running titles, etc.) or for portions of titles and any variations of titles (initialisms, titles with ampersands, etc.) when these might reasonably be taken by a user as the true title. Variant titles also include minor title changes.
The guidelines for the CONSER standard record simplify the coding for the 246 field. For any variant titles found on the piece, including initialisms/acronyms not chosen as the title proper, use indicators 13 as shown in the first two bullets.
For parallel titles found on the chief source of the item described, used 246 11.

## CSR & AACR2 on variant titles - 246

**CSR & AACR2 on variant titles - 246**

- Variant titles:
- 245  00  $a Freeport daily journal.
- 246  1-   $i  Alternate issues published with title:
- 	        $a Chicago daily telegraph
- 245  00  $a Los Angeles design world.
- 246  1-   $i  Issues for Nov. 2006- have title:
- 	        $a LA design world
- Titles that do not appear on any pieces:
- 245  00  $a Tennessee ancestors.
- 246  1-   $i  Popularly known as: $a Tenn an

**Notes:**
For any other title for which you wish to generate a note, use 246 1_ and input the text of the note in $i. This is commonly used for alternating titles and for minor title changes, as shown in the examples under the first bullet.
Title added entries may also be made for works commonly known by titles that do not appear on any pieces (LCRI 12.7B4).
For example, if Tennessee ancestors were popularly known as Tenn an, a 246 could be added to the record.
The use of the first indicator 1 combined with the subfield $i is the same for both CSR and AACR2 cataloging.

## Statement of Responsibility

**Statement of Responsibility**

- 	A corporate body appearing prominently in conjunction with the title:
- 			News and events
- 		      Art Institute of Chicago
**CSR**
- Statement of responsibility _not_ transcribed _if _national name authority record exists
- If no name authority record, follow AACR2 and transcribe in 245 $b or $c
- 	245  00  $a News and events / $c Art Institute of                  Chicago.

**Notes:**
AACR2: Record corporate bodies appearing prominently (i.e., in a source used for Areas 1 or 2) in a statement of responsibility, and made an added entry for the body. According to the guidelines for the CONSER standard record, as long as an added entry is backed by a national name authority record (i.e., in the LC/NACO Authority File), the statement of responsibility is not required.
However, if there is no LC/NACO authority record, the corporate body must be transcribed so that usage can be traced for future authority work, as seen in our example here.
Generally, personal editors are not included in statements of responsibility, as they change over time. If the editor is considered of historical significance and  important for access, he/she may be given in a note and an added entry made.
In the example shown here, the statement of responsibility is included either because:
1) The cataloger is strictly following AACR2
2) The cataloged is following the CSR guidelines but no name authority record exists for the body

## There is a name authority record in national authority file, so...

- 		    245 00 $a Horizons.

- On cover:
- Horizons
- ** The Agency for International Development **
- Published in Washington, D.C. by the Agency for International Development...

**Notes:**
We’ve covered several important points related to the CONSER standard record. Here’s an example to help summarize these points.
Horizons is a magazine published by the Agency for International Development, along with a traditional AACR2 description. Assume that the LC/NACO Authority File has an authority record for the Agency for International Development. Based on the information covered and what you know of the CONSER standard record, which data elements are OPTIONAL?
[Answer: 130 field, 245 $c, also 260 $c (which we haven’t gotten to yet)]

[Instructor’s note:
There are over 160 OCLC records for serials with the title “Horizon.” In some library settings, where entries in the indexes already include clarifying information (e.g., publisher and dates), then the option of NOT having a uniform title with a qualifier consisting of place of publication may be welcome. In other situations, catalogers entering an original record may decide to apply the option of continuing to create a distinguishing uniform title.]

##  Publication information

- Place
- First-named place required (LCRI 12.4C)
- Online resources: [S.l.] if not readily available
- If country known (or reasonably guessed):
- 		[United States] or [United States?]
- Dates - 260 $c
**CSR**  Optional
**AACR2**  Only if first and/or last piece in hand

**Notes:**
The guidelines require catalogers to supply the first-named place of publication as found on the item (LCRI for 12.4C). However, catalogers are not required to supply any additional places, regardless of the home country of the cataloging agency. For e-serial catalogers, the principle is “don’t agonize.” If the place of publication is readily available (for example, found by scrolling within a few pages of the home page or first issue page), record that place in 260 $a. Otherwise, supply [S.l.] in field 260 $a. Code the fixed field country code as appropriately as possible. For example, a U.S. Web site lacking location could be coded 260 $a [United States] and the FF element “Ctry” could be coded “xxu.”
Catalogers may omit date of publication from the publication area (260 $c); however, if you are editing existing copy for a ceased title and you elect to close off a formatted 362, also close off the 260 $c to be consistent with the cataloging practices you have chosen to apply. (I will explain this in more detail when I talk about editing the 362 field in existing catalog records.)

##  Physical description

- Required only for tangible, non-print resources.
- 300 -- $a CD-ROMs
- 300 -- $a 12 microfilm reels
- 300 -- $a sound discs

**Notes:**
Physical description, coded in the 300 field, is generally not required in the CONSER standard record. The exception is for tangible non-print resources, and the subfield $a (extent of item) is the only element required, as shown in the examples on this slide.

##  Frequency

- Required: Current frequency if known (310)
- Fixed field = fill characters
- Optional: Former frequency (321)
- Maintenance (existing records):
- Update 310 with current frequency
- Move previous frequency to 321 field
- Leave all existing 321 fields

**Notes:**
We also have some new options in the guidelines regarding frequency notes.
As discussed earlier, frequency need not be coded in the fixed field; instead, the cataloger may leave the default fill characters for both Frequency and Regularity.
Original cataloging: When entering an original record according to the guidelines, ALWAYS record the current publication frequency in the 310 field if known. This is required.
Original cataloging: Former frequency notes (that is, 321 fields) are optional in original cataloging. 
Maintenance: To update a record created earlier under AACR2 that has an existing 310 field, move the former frequency to a 321 field and enter the current frequency in the 310 field (this is already established practice). Do NOT delete former frequencies just to conform to the new standard.
[Instructor’s note: the guidelines do NOT recommend the option of converting Freq/Regl and deleting the former frequency]

## If creating an original record - CSR

- 310 -- $a Quarterly

- If editing existing copy – **AACR2**
- 310 -- $a Quarterly, $b 2004-
- 321 -- $a Monthly, $b 1999-2000
- 321 -- $a Three times a year, $b 2000-
- 	       2003

- Item(s) described:
- Monthly, 1999-2000; three times a year, 2000-2003;
- quarterly, 2004-

- And the fixed field coding?

**Notes:**
Notice the difference between what you would do if creating an original record and what you would do if maintaining an existing record.
When editing an existing record, move previous frequencies to 321 fields. The order of the 321 fields is chronological.
Do NOT remove former frequencies to conform to the new standard.

##  Numbering

- Unformatted 362 note
- 362 1- $a Began with neue Folge, Nummer 1 (1997); ceased with neue Folge, Nr. 11, published 2006.
- 362 1- $a Began with número 1 (abril 2001); first series ceased with número 12 (marzo 2003); nuevo serie began with número 1 (abril 2003).
- Optional
- Abbreviations
- Capitalization
- Arabic numerals (for spelled out numbers)

**Notes:**
As noted earlier, numbering (and related notes) is one area which represents a very visible change from previous practice. The next few slides will go into more detail and give examples for the general points shown here on this first slide.
For new records entered according to the guidelines:
  -- Prefer to code information in an unformatted note whenever the information is available, regardless of whether the first or last issue is actually in hand.
-- The cataloger may transcribe captions and dates as found (including abbreviations and capitalization) or use standard AACR2 abbreviations. Numbers (including ordinal numbers) may be transcribed as found or they may be recorded using Arabic numerals, whichever is easiest.
Later, we’ll cover the options for maintenance of numbering data. For now, let’s go into more detail about each of the points listed on this slide ...

##  Numbering

- Optional: Abbreviations, capitalization, Arabic numerals (for spelled out numbers)
- 	Volume 1, number 1  *or:  *Vol. 1, no. 1
- 	Vol. IV, no. 4  *or:  *Vol. 4, no. 4
- 	Second series  *or:  *2nd ser.
- 	Nouvelle série  *or:  *Nouv. sér.

**Notes:**
As mentioned earlier, the cataloger may transcribe captions and dates as found (including abbreviations and capitalization) or use standard AACR2 abbreviations. Numbers (including ordinal numbers) may be transcribed as found or they may be recorded using Arabic numerals, whichever is easiest.
Here are some examples of how numbering and dates may be recorded in the CONSER standard record, either in the 362, 500, 515 or any other note where the numbering is used.

## On title page of first issue, called February 2006:

- 260 -- $a Amsterdam ; $a New York : $b Harwood, $c 2006-
- 362 0- $a Feb. 2006-
**CSR:**
- 260 -- $a Amsterdam : $b Harwood
- 362 1- $a Began with February 2006.
-                *OR:* Began with Feb. 2006.
- 500 -- $a Description based on first issue; title from t.p.

- Harwood
- Amsterdam, Beijing, Canberra, New York
- 2006

**Notes:**
Let’s return to our serial from Amsterdam. 
If you were entering a new record for this serial according to the guidelines for the CONSER standard record, how would the 362 and 500 “Description based on” notes look? (I’ve already supplied the simplified 260, which we covered earlier.) Is this what you would have done?
Remember that the cataloger has the option to transcribe the months as found or to use the abbreviations found in AACR2 (i.e., Feb. 2006).
Also, re: 500 field: In the spirit of the relaxed guidelines for abbreviations, the cataloger can either spell out “title page” or use the standard abbreviation of “t.p.” It is the long-term goal that all cataloger’s notes will be recorded in a separate 5xx field that can be suppressed from public display.

Any questions? Comments?

##  Numbering (maintenance)

- Ceased title (have last issue)
- Add to existing 362 0-
- 				**or**
- Add a separate unformatted note (362 1-)
- New series
- Add to existing 362 0-
- 				**or**
- Convert to unformatted note (362 1-)

**Notes:**
Turning to maintenance of existing records (cataloged prior to implementation of the CONSER standard record), let’s look at two common situations:
Ceased title: To add an ending designation, the cataloger can add to an existing formatted 362 according to previous practice or add a separate unformatted 362.
New series: To indicate new series, changes in numbering, etc., the cataloger may add to an existing formatted 362 according to the previous practice. Or, the cataloger may convert the information into an unformatted note that includes new series information.
Let’s see how this might work in practice ...

[Instructor’s note: This information is in Appendix A “Working with Copy and Record Maintenance”]

## CSR:

- 362 0- $a Vol. 1, no. 1-v. 4, no. 4.
**   ****OR*** *
- 362 0- $a Vol. 1, no. 1-
- 362 1- $a Ceased with v. 4, no. 4, published in 2005.
- 500 --  $a Final issue consulted.

- In OCLC record:
- 362 0- $a Vol. 1, no. 1-
- 500 --  $a Latest issue consulted: Vol. 4, no. 3.
- Ceased with: Volume 4, number 4, with publication date of 2005 (last issue in hand).

**Notes:**
Situation: You receive the last issue of a journal. The numbering information is volume 4, number 4. The issue lacks a coverage date, but has a publication date of 2005. In OCLC, you find a CONSER record with a formatted 362 entered under previous AACR2 conventions.
Which of these options could you use to update the record? 
That’s right! Both options are correct.
NOTE: If you choose the first option, that is, to close off a formatted 362, there are a few more points to make about that ...

## How would you update the catalog record for the 3rd series?

- a. Add to formatted 362
- b. Convert formatted 362 to unformatted note &
- 	add new information
- c. Leave existing 362; add separate unformatted 362

- In catalog record:
- 362 0- $a No. 1-no. 6 ; [new ser.], no. 1-
- You have two issues:
- -- No. 3, published in 2004 (last issue of “new ser.”)
- -- 3rd series, No. 1, published in 2006

**Notes:**
This situation is somewhat more complex. In this case, you have TWO issues: one issue represents the last issue of the “new series”; the other issue represents the first issue of the subsequent series, series 3. All three of these options are valid under the guidelines:
  -- You could add to the existing formatted 362 (following AACR2)
  -- You could convert the existing 362 to unformatted note and add the new information
  -- You could leave the existing note and add an unformatted note
Which option do you prefer? Which option may require edits to other parts of the existing catalog record? Why or why not?
[Instructor’s notes: Participants may wish to explain their preference or may not. Amount of time for discussion may vary.]
Having considered our options, let’s see how one of the options would actually look ...

## 362 0- $a No. 1-no. 6 ; [new ser.], no. 1-

- 362 1- $a [New series] ended with No. 3, published in            2004; 3rd series began with No. 1, published in 2006.
- 500 -- $a Latest issue consulted: 3rd series, No. 1, published in 2006.

- In catalog record:
- You have two issues:
- -- No. 3, published in 2004 (last issue of “new ser.”)
- -- 3rd series, No. 1, published in 2006

**Notes:**
This illustrates one of the options a cataloger could follow when maintaining an existing record. In this case, the cataloger chose to leave the existing formatted 362 and enter a separate unformatted note to describe the two newer issues. 

[Reminder: The cataloger may transcribe captions and dates as found (including abbreviations and capitalization) or use standard AACR2 abbreviations. Numbers (including ordinal numbers) may be transcribed as found or they may be recorded using Arabic numerals, whichever is easiest.]

## CSR required notes

**CSR required notes**

- DBO
- Source of title
- Numbering
- Latest issue consulted note:
- 500 --  $a Latest issue consulted: 2001.
- 500 --  $a Final issue consulted.
- Even when cataloging based on one issue:
- 500 -- $a Description based on: 1918; title from t.p.
- 500 -- $a Latest issue consulted: 1918.

**Notes:**
CSR: 
Always supply a note about the latest issue consulted note.
Supply an LIC note even when cataloging based on only one issue.
3. Do not combine the DBO and LIC notes into one 500 note.
Always enter a “Description based on” note to make clear which issue was used as the basis for description. Also always enter a “Source of title” note even if the title is taken from the title page. Always enter a “Latest issue consulted” note if later issues are available. 

AACR2:
Supply a note about the latest issue consulted when cataloging based on more than one issue.
When a serial is closed off and the last issue is given in field 362/0, the “Latest issue consulted” note is removed.

## Uniform title

- Distinguishing uniform title only to resolve conflicts (LCRI 25.5B) for:
- Monographic series
- Serial title = Generic term
- 		**or**
- 	Serial title = Generic term plus frequency word
- Create uniform titles as required for legal materials and other cases for collocation purposes

**Notes:**
According to the new RI for 25.5B, catalogers are not required to create or add a uniform title in order to resolve conflicts. This is true both for title main entry and for titles entered under personal or corporate main entry. The two exceptions are:
1)  Continue to create distinguishing uniform titles when cataloging a monographic series as a serial
2)  Also create a distinguishing uniform title when a serial consists of a generic term (i.e., resource type, e.g., bulletin) or a generic term plus a frequency word (e.g., monthly newsletter)

NOTE: Continue to create uniform titles as required for legal materials and other cases of collocating (as opposed to distinguishing) uniform titles that are not translations or language editions.

## Translations/language editions

- No uniform title
- Collocating title added entry
- Linking entry field

-  245 00  $a Analyse des politiques éducatives.
-  730 0- $a Education policy analysis. $l French.
-  775 08 $i Issued also in English: $t Education policy
- 	   analysis $x [ISSN] $w (DLC) ... $w (OCoLC) ...

**Notes:**
According to the guidelines, catalogers are not required to create or add uniform titles for translations or language editions. (This is true both for serials entered under title and those entered under personal or corporate main entry.) 
Instead, create a linking entry field as usual (765/767 for translations; 775 for language editions). Then also create a title added entry to collocate the serial in hand with the original language edition. Put a subfield $l in the 730 title added entry field to indicate the language of the resource being cataloged.
Note: This is an exception to the general policy which states that title added entries (730s and 740s) are not required if they duplicate linking fields.

##  Series (traced)

- Series statement (4xx):
- If authority record  Not required
- No authority record  **Required**
- Series added entry (8xx):
- Record authorized form here instead of 4xx

**Notes:**
For traced series:
It is not required to transcribe a series statement appearing on the piece as long as a series authority record exists or is being established. Record instead the authorized form of the series using the 8xx field. (If you need to record ISSN information about the series, however, you will need to do that in a 490 field because currently the 830 cannot accommodate it.)
In cases where no series authority record exists or will be created, the cataloger must transcribe the series statement so that usage can be documented.
The following slides show examples of the new series treatment ...

## On item described:

-     	Reports of the Mono Lake Committee
- In LC authority record:
- 	130 -0 $a Report (Mono Lake Committee)

- In catalog record:
- 245 00 $a This month at Mono Lake.
- 260  --  $a Lee Vining, CA : $b Mono Lake Committee
- 830  -0 $a Report (Mono Lake Committee)

**Notes:**
In this example, there is a series authority record in the LC/NACO Authority File for the Reports of the Mono Lake Committee. No 4xx is required; only the authorized form (830) is recorded in the bibliographic record.

## On item described:

-      National parks occasional news brief
- 	(No LC/NACO authority record)

- In catalog record:
- 245 00 $a Yosemite this month.
- 260 --  $a Lee Vining, CA : $b Eastern Sierra Mountain Climbers Association
- 440 0- $a National parks occasional news brief

**Notes:**
In this example, there is no LC series authority record for the National parks occasional news brief, and none is being created. The cataloger is therefore required to transcribe the series statement as found to record usage.
The cataloger would record the series either in a 440 or 490/830 combination, depending on how the entry for the series would be established in accordance with AACR2 and relevant LCRI’s. (In other words, follow existing practice as currently defined by the MARC 21 tags for these fields.)
[Note: One of the recent MARBI changes is the re-definition of the indicator “1” in the 490, from the currently defined “Series traced differently” to: “Series traced in 8xx” (or something like that) – this would allow all series to be transcribed in 490 fields, whether traced or not traced (first indicator “0”), and whether they are in the series entry form or not, and the elimination of 440]

## Issuing body notes(LCRI 12.7B7.1)

- Optional, **if** authority record exists
- Required
- If authority work does not exist and will not be created
- If issuing responsibility for the work changes

**Notes:**
Catalogers are not required to use 550 or other notes simply to justify added entries providing that a heading for the body has been established in the LC/NACO Authority File.
If a corporate body’s name has changed over time, update the authority record in the LC/NACO Authority File to reflect these changes. In addition, if a corporate body changes its name, or a new body becomes responsible for the work, add an appropriate 550 note and a make access points on the bibliographic record as necessary.
[Reminder: A CONSER standard record is one in which all headings are represented by authority records in the LC/NACO Authority File. For all other records (both non-CONSER records and CONSER records), the issuing body note should always be transcribed if no authority records exist nor will be created.]
[Note: At some future time, if a MARBI proposal is approved to add date ranges to 7xx fields, the 550 note for changes in responsibility will no longer be required.]

## In catalog record:

- 245 00 $a Behavior therapy.
- 260 --  $a New York : $b Elsevier
- 710 2- $a Association for Advancement of Behavior Therapy.

-  On item described:
-   Behavior Therapy
- Official journal of the Association for Advancement of Behavior Therapy
- Published by Elsevier.
- LC/NACO authority record exists for the Association.

**Notes:**
In this example, the 550 field is not required, because the issuing body is represented by a national level name authority record. The 710, an authorized access point, is the “justification” for the body.

## In catalog record:

- 260 -- $a New York : $b Elsevier
- 550 -- $a Issued by: Association for Behavioral and
-             Cognitive Therapies, <2006->
- 710 2- $a Association for Advancement of Behavior
- 	     Therapy.
- 710 2- $a Association for Behavioral and Cognitive
-            Therapies.

-  On (later) issue for Jan. 2006:
- Official journal of the Association for Behavioral and Cognitive Therapies
- Authority record exists for later name of the Association.

**Notes:**
In this example, the 550 field is required, because the issuing body has changed and an additional 710 has been added to the catalog record.

##  Miscellaneous ...

- Prefer linking fields where feasible:
- 776 08 $i vs. 530
- note generation from 7xx vs. 580
- 730, 740 not required if linking field exists
- Optional fields/subfields:
- 041 0- use only $a (record details in 546)
- 538 not required except ...
- Refer to MAP and Cataloger’s Cheat Sheet

**Notes:**
This is a summary slide for some miscellaneous areas of the cataloging record that differ under the CONSER standard record guidelines. 
Where feasible, prefer to use linking fields and their existing note-generating capabilities (this will not always be possible depending on your local system). For example:
530: Prefer to use a 776 $i rather than a 530 note to describe any additional formats available.
580: Prefer to use the note-generating capabilities in indicators and subfields of 7xx fields.
041: If the main content of the serial is in more than one language, record all those languages in repeatable $a’s in field 041. It is not required to code the other subfields; instead, record all information about languages in an eye-readable 546 note. This includes multiple languages, translations, different languages of summaries, tables of contents, or accompanying material.
538: For direct access electronic resources, catalogers are not required to make a 538 note except in cases when it is necessary to indicate the type of operating system or the make and model of the computer(s) on which the resource is designed to run. For remote access electronic resources, make a note on the mode of access only if the resource is accessed other than through the World Wide Web.
Unless instructed otherwise, record all other MARC 21 fields as usual.
[Instructor’s note: MARBI changes are needed to increase use of note generation in linking fields.]

## Questions?