Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Document status

DRAFT (adapted from the Orbis Cascade Alliance documentation)

Area coveredacquisitions, cataloging
Lead Author
Co-authors

Carole Correa-Morris (Unlicensed), @Del Williams, @Kim Valenzuela,@Moon Kim, @Tyler Rogers

Background

Alma supports 10 levels (often referred to as “Encoding Levels”) of brief bibliographic records. This policy, adapted largely from the Orbis Cascade Alliance, articulates recommended Brief Level Rules for records in the IZ* , and the required Brief Level Rule (minimum Encoding Level) for records in the NZ.


 *To be determined by TSWG?

Policy Statement

NZ records will have a minimum Brief Record Encoding Level of 06.  (See Bib Level 06 mapping below.)

Mapping Information

The NZ Brief Record Level Rule is mapped as follows from the Leader byte 17 "Encoding Level" of the MARC record:**

Alma Brief Level

Leader byte 17

Description

10

(blank)

Full level

09

I / L

Full level input by OCLC participants (uppercase “i”) / Full level input added from a batch process (future: use ‘M’ instead)

08

1

Full level, material not examined

07

4

Core level

06

K / M

Less-than-full added from a batch process

05

2 / 7

Less-than-full level, material not examined / Minimal level (OCLC Bib Formats: OCLC participants cataloging online at Minimal level, use ‘K’)

04

8

Pre-publication level

03

3

Abbreviated level

02

5

Partial (preliminary) level (and other codes, e.g., u & z, as encountered and appropriate)

01

J

Deleted record



 **Supplied Orbis' mapping here as a placeholder; final version to be determined by TSWG?

Best practice recommendations

  • Set the NZ’s default Brief Level Rule as your Institution’s default; or
  • If you wish to use different minimum record levels than the consortium, then create a copy of the NZ Brief Level Rule and edit to your suit your needs; set it as your Institution’s default.
    • Consider the minimum Encoding Level of the records you currently accept from OCLC and other MARC record providers.
    • Keep In-Process Brief Bibliographic Records with Minimum Acquisitions Data recommendations in mind in order to ensure that your brief records are in compliance with consortium practice.
    • Recommend institutions use a minimum Brief Record Level of 06.*
  • Run the Identifying Brief Level job after setting the default Brief Level Rule; spot check for accuracy

Note: institutions have the ability to create import profiles that utilize CSU NZ Brief Level Rules. Otherwise, import profiles that load records into an institution's IZ (i.e., have "Use Network Zone = No") will use the local default Brief Level Rule set as the default within that institution's IZ configuration. 


NZ vs. IZ Brief Level settings:

  • If a library loads records to the IZ, it will assign a level based on the institution's brief rule.
  • If a library links an IZ bib to an NZ bib, the NZ bib view will use the brief rule level per NZ settings, and the IZ bib view will maintain its brief level per IZ rules.
  • If a library shares an IZ only bib with NZ, the NZ brief level rules were applied to the NZ record, but the IZ brief level was retained.
  • If a library uses the Copy to Catalog from the NZ, the IZ brief level is retained and the NZ brief level is retained.
  • If you search in Alma Sets in the IZ and NZ, you can successfully search for the records by the corresponding brief level.

 *This is my library's practice; do others agree?

Procedures in Alma

1)      Set the Institution’s default Brief Level Rule

  • Select the NZ Brief Level, or


2)      Create Institution’s Brief Level Rule

  • And set it as the Institution default


3)      Run the Identifying Brief Level Rule job

  • And check that records updated appropriately


Also see: "Working with Brief Record Levels" article in the Knowledge Center

Action log

SectionPoint Person

Expected Completion Date

Last action takenNext action required

Articulate the need for the policy (background)

 



Create a Policy Statement

Wendy Vermeer

 

Drafted policy and input draft in AtalssianTSWG sets minimum brief level; work with ??? to create custom Brief Level Rule in NZ instance (so that others can use the rule in their IZs)

Identify and create best practice recommendations


 



Where applicable, identify and write up procedures in Alma


 




Tasks to be completed

  • TSWG discuss and set minimum brief level; Luiz Mendes
  • ??? Create custom Brief Level rule in NZ  
  • No labels