2.-3. Updating & Importing New SARS

2. Updating Existing SARs

2A. Where to Update SARs
 
OCLC
  • Updating  a SAR in OCLC if making national-level changes.
  • National-level changes include such things as: changing fixed fields, headings, and cross references adding new cross references, and adding new 640, 641, 642, 643, 645, 667, and 670 fields.
ORBIS
  • Update a SAR in ORBIS if making local changes.
  • Local changes include such things as: adding 090 fields, recording Yale analysis and classification decisions in 644 and 646 fields, and recording local notes in 690 fields. It might be necessary to import the SAR from OCLC into ORBIS before making the update.
2B. 090 Field (update in ORBIS)
 
Class together
Add an 090 field to the ORBIS record to record the call number of a series or MPM that will be classed together, even if the number is exactly the same as the one recorded in the 050 field. Preface the call number with the Yale location to which it pertains. Example:
Before After
050   4 BX3201 ‡b .S78 ‡5 CtY-D 050   4 BX3201 ‡b .S78 ‡5 CtY-D
  090     DIV: BX3201 .S78
Before After
050   0 BX3301 ‡b .A52 050   0 BX3301 ‡b .A52
  090     SML: BX3301 .A52 (LC)

If you discover existing bib records in ORBIS (for the same location) that have been classed separately, use judgment in deciding whether to 1) reclass them, 2) add a note to the SAR specifying a change in practice after a certain date, or 3) continue to class separately. The third option is discouraged.

Encoding Level 7 Analytics
Add text in square brackets to the end of the call number in the 090 field to record a decision to create encoding level 7 analytics (EL7) for a monographic series or MPM. Example:
Before After
  090 SML: HB5 D58 (LC)+ Oversize [EL7 ANALYTICS ONLY]
Classed Separately

Decision to class separately may be highlight in 090 fields but the practice should generally be limited to the following situation:

  • changes in Yale classification practice (see example below)
  • complex situations involving especially voluminous numbered series
  • different practices for different Yale locations (especially locations that use the same MARC institutional code)
Before After
 

090 SML: 20- [CLASSED SEPARATELY]

090 SMLY: J525 St94 1-19 090 SMLY: J525 St94 1-19
Not Analyzed

Decision not to analyze may be highlighted in 090 fields but the practice is not required. Example:

Before After
  090 DIV: DO NOT ANALYZE
644 f ‡5 DLC 644 f ‡5 DLC
  644 n ‡5 CtY-D
2C. 642 Field (update in OCLC)
  • Do not retrospectively add a ‡5DPCC code to an exiting 642 field.
2D. 645 Field (update in OCLC)
  • If the existing SAR contains a DPCC or LC "traced" decision, follow it. If the existing SAR contains only an "untraced" decision, follow it.
  • Do not add new 645 fields
  • Do not retrospectively add a ‡5 DPCC code to an existing 645 field.
2E. 644 and 646 Fields (update in ORBBIS)

For monographic series and MPMs that are new to Yale, generally follow analysis and classification decisions recorded by LC and other PCC libraries. If necessary, update SARs to record Yale decisions by adding new 644 and 646 fields or by modifying existing ones according to the guidelines below.

Adding New 644 and 646 Fields

Add Yale analysis and classification decisions in new 644 and 646 fields in the ORBIS record in the following situations:

Yale decisions differ from the decisions already recorded in the SAR. Example:

Before After
646 s ‡5 CoU 646 s ‡5 CoU
  646 c ‡5 CtY

SAR lacks 644 and 646 fields. Example:

Before After
  644 f ‡5 CtY-BR
645 t ‡5 DPCC 645 t ‡5 DPCC
  646 s ‡5 CtY-BR

Modifying Existing 644 and 646 Fields

Do not delete decisions already in the SAR for LC and other PCC institutions.

Modify existing 644 or 646 fields in the ORBIS record whenever a Yale decision of "do not analyze" or "class together" duplicates an existing decision. Example:

Before After
646 c ‡5 DLC 646 c ‡5 DLC ‡5 CtY-BA

Do not generally record a Yale decision to "analyze" or "class separately" when it duplicates an existing decision unless you want to differentiate it from a decision for another Yale location. Examples:

Before After
646 s ‡5 DLC 646 s ‡5 DLC
Before After
646 s ‡5 DLC 646 s ‡5 DLC ‡5 CtY-M
646 c ‡5 CtY 646 c ‡5 CtY

Recording Changes of Practice

Use ‡d to record a change in practice for a location, placing the ‡5 code at the end of the field:

Before After
646 s ‡5 CtY-D 646 s ‡d vols. cat. before Oct. 1, 2003 ‡5 CtY-D
  646 c ‡d vols. cat. after Sept. 30, 2003 ‡5 CtY-D
2F. 690 Field (update in ORBIS)

Use 690 fields to record lengthy explanations of local analysis and classification decisions, if necessary. Do not add 690 fields as a matter of course.

3. Importing SARs

3A. When to Import SARs

As a general rule, do not import SARs into ORBIS from OCLC. MARS will send us the SARs as a result of weekly bib record processing.

Exceptions: You may import a SAR if:

  • you need to update the SAR in ORBIS with local information
  • you are cataloging the first volume of a standing order
  • the SAR is for a series-like phrase (008 Type of series=c)
Note: MARS does not usually send us SARs for series-like phrases because the phrases tend to be recorded in bibliographic records in note fields, which are not examined during MARS processing.
3B. How to Import SARs

Authority records are imported from OCLC in the same way that bib records are imported (although authority records will rarely need to be imported; see 3A).


Document issued by the NACO Coordinating Committee.

Contact: Rick Sarcia