Page History

...

Contact:  Pam Stansbury / Laura WrightDaniels

Unit: Cataloging

Date last updated: 10/9/2019

Date of next review: October 2020

OCLC review: compatible

2024

...

Inputting
Guidelines for LC Call Numbers
Guidelines for Access Points
Guidelines for Subject Access (FAST)
Guidelines for Added Entries
LTS Statistics Code for Minimal Level Records
Historical Background and Policy
Eligibility for MLC
Exclusions from MLC
Definitions
Interpreting the Minimal Level Standards

...

Any record input by LTS should be described according to RDA.  If the record is based on AACR2 copy input as MLC (Encoding level not blank) by LC, it is acceptable to leave the record as AACR2.  Modify the record in OCLC to to bring it up to the LTS minimal level standard, as defined below.

...

...

Access points should be consistent with the structure of the Voyager catalog.  NoteLC Name Authority File. Note: it is not necessary for every MLC access point to be represented by an authority record in the national file. 

...

• If you find an authority record, use that form, which is the authorized access point, and control the heading.
• If you don't find an authority record, search Voyager FOLIO (the public catalog search may be more effective) and use a form from a Voyager an existing bibliographic record. If several forms of the name or uniform title occur in Voyager, select a heading form in this order of preference: a full RDA or AACR2 record; another MLC minimal level record; an LC in-process (Encoding level 5) record. Use judgment to select one of them; make a quick decision in most cases.
• If the heading is new to Voyagerus, do a quick search of OCLC. If a form is found in other bibliographic records, use that form. Otherwise, formulate the heading using RDA, information from the item, and information you've discovered by searching Voyager.
• If the heading conflicts with a heading that already occurs in Voyagerour catalog, resolve the conflict by making additions to the MLC heading in your record.
  
• If the conflict cannot be resolved in this manner, create an RDA NACO authority record.

Note, the only instance in which you would make a NACO authority record is when the chosen access point conflicts with an access point that is already in Voyager our catalog and you cannot resolve the conflict without further research. 

   2.  Titles (130, 240).  If the item is a translation and the original title is known, supply the preferred title for the original + |l Language.  Follow the procedure in (1) above to find the preferred title or name/title combination.  Remember that RDA requires what we used to call “uniform titles” in two more situations:

• If the work is a complete compilation with one creator, RDA requires a conventional collective such as “Works. |k Selections” or “Short stories. |k Selections.”  NB: As of August 2013, CUL does not follow this rule. See Chart #2.title.
  
• If the work is a compilation with more than one creator, you may need to devise a 130 if the title proper is in conflict with another title in the database. 
• Supply these titles if the choice is easy and quick.  You should check for an authority record for any name/title 100/240, but you do not need to create NARs in these situations.
  
  

...

Add a 948 field an instance administrative note for statistics tracking. Use first indicator 1 for cataloging transaction and subfield b o for This is considered original cataloging. Minimal level cataloging statistics are defined by the o (original cataloging) from the 948 structured note field and 7 from the encoding level field of the MARC Leader.

...

...