Scope: Minimal-level cataloging (MLC) is an abbreviated form of cataloging that reflects gives limited bibliographic description, subject analysis and (in most cases) authority work. Materials eligible for MLC include low-need and/or low research value titles.
Contact: Sarah RossPam Stansbury / Laura Daniels
Unit: Cataloging
Date last updated: 10/3012/20142023
Date of next review: October 2016 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 in-process record in Voyager to OCLC to bring it up to the LTS minimal level standard, as defined below.
Fixed Field Values
MARC21 Definition | Voyager label | LTS Minimal Level Requirement |
Encoding Level | Encoding level | Enter value "7” |
Descriptive cataloging form | Cataloging form | Should be value “i” (RDA) or "a" (AACR2) |
Cataloging source | Cataloging source | Should be value "d" (default). LC MLC should be left as “blank.” |
Place of publication | Place of publication | Mandatory |
Language | Language | Mandatory |
Type of Date Code | Publication status | Mandatory |
Date 1, Date 2 | Date 1, Date 2 | Mandatory (Date 2 mandatory if applicable) |
All other fixed field positions are optional at minimal level. Catalogers may fill in such fields as Contents or Literary Form at their discretion, as long as they do no not agonize over the choice.
Variable Fields
...
- Focus on the data elements spelled out in this procedure as mandatory or mandatory if applicable.
- Accept what is present on DLC records to the extent possible. Do not delete or change DLC information unless it is clearly inaccurate or egregiously misleading.
- Do not agonize over data elements in a record. Make a quick decision in most cases.
MARC 21 Definition | Tag | LTS Minimal Level Requirement |
Library of Congress Control No. | 010 | Mandatory if applicable. Enter any DLC label mounted on the cover. |
ISBN | 020 | Enter |a if it appears on the item (|z if you know it can’t possibly be valid, for example if it’s not 10 or 13 digits long) |
035
Retain the OCLC control number if present. Do not include an OCLC control number for a different manifestation. Do not include an OCLC control number for a non-English record (that is, 040 |b must be blank or “eng”).
Cataloging Source | 040 |
OCLC automatically supplies |a |
and |d ; |b |
eng and |e rda |
(if applicable) are mandatory | ||
LC Call No. | 050 | |
Authorized access point | 1xx | Mandatory if applicable (includes 100, 110, 111, 130) |
Preferred title | 240 | Enter a preferred title if known or readily inferred from the item; otherwise, omit. See Guidelines for Access Points, section 2, below |
Title area | 245 | Subfield |a is mandatory; |b and |c if applicable |
Varying form of title | 246 | Optional ; use judgment. Record parallel titles. |
Edition area | 250 | Mandatory if applicable |
Imprint | 264: 1: (RDA); 260 (usually AACR2) | Mandatory if applicable; |a, |b and |c should be present |
Physical description | 300 | Subfields |a and |c are mandatory; all other subfields are optional |
Content, Media, Carrier | 336, 337, 338 | Mandatory on RDA records, recommended for all records. Use |
OCLC macro "Add33x" or Essentials macro "Check 33X" | |
Series | 490:0 |
Transcribe series if present. Do not trace the series in an 830. |
FAST subject access | 6xx | Mandatory if applicable; see Guidelines for Subject Access (FAST) |
Added entries | 7xx | All added entries are optional; see Guidelines for Added Entries |
...
Guidelines for LC Call Numbers Anchor B B
...
If you find an actual LC cutter for an individual literary author, artist, geographic area, or subject, use it. Otherwise construct a cutter using Library of Congress practice for cuttering, as described in the LC Shelflisting Manual, available on Cataloger's Desktop.
In crowded places in the schedules, as may happen especially with literary authors, it may be better to keep an author together and a Cutter-Sanborn cutter, rather than splitting an author between the Cutter-Sanborn cutter and the LC cutter. Use discretion.
...
Guidelines for Access Points Anchor C C
For more detailed guidelines on how to choose or construct an access point, see the following document: [link out to Ardeen’s document on how to do authority work].
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 search 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 #2title.
- 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.
...
Starting on December 1, 2014, LTS exclusively uses FAST subject headings on minimal level records. This change applies to minimal level (that is, encoding level 7) cataloging only and not to class-on-receipt (encoding level 3) or full cataloging.
Consult LTS Procedure #127, FAST Headings for Cataloging for guidance on the use of FAST.
...
LTS Statistics Code for Minimal Level Records Anchor F F
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.
...
Historical Background and Policy Anchor G G
...