MARC Tags for Authority Records

001 OCLC control no. This was also the local control no. for records exported to the system before the MARCIVE load in May 2002. Some older records in WorkFlows may have the LC control no. in this field and the OCLC number in the 035 field.

003 Record source. Displays for records exported from OCLC.

010 LC control no. This also serves as the local control no. for records exported to the system after the MARCIVE load in May 2002. If there are duplicate authority records in our system, the newest and most reliable will be the records with this type of control number (example: N79021164 for a name record; SH85021262 for a subject authority record).

040 Inputting library. LC authority records will have DLC|cDLC. For records created locally for our database, use MUS|cMUS.

053 LC call number assigned to the heading in the 1xx field. On locally created records (e.g., for series authorities), our local call number is shown in an 090 field.

1xx fields are used for the heading that is being authorized. Indicators for the 1xx fields are the same as those used in the corresponding fields in bibliographic records.

100 Authorized heading-Personal name
110 Authorized heading-Corporate name
111 Authorized heading-Conference name
130 Authorized heading-Title
150 Authorized heading-Topical subject
151 Authorized heading-Geographic name
155 Authorized heading-Genre subject term (not presently used in OCLC or locally)
180 Authorized heading-Topical subject subdivision
185 Authorized heading-Form subject subdivision

4xx fields are cross-references (or "see from" references). They may represent previously valid forms of the heading in the 1xx field, different forms of names used by authors, or, in the case of subjects, other terms that patrons might look under when searching. The 4xx fields for each type of authority correspond to the 1xx tags for that particular type of heading, e.g., 400 fields are references for personal names, 450 for topical subject terms, etc.

5xx fields are "see also" references; they refer catalog users from one valid heading to another, equally valid term that has a relationship to the first heading. Like the 4xx fields, the 5xx tags are consistent with 1xx fields: 500 is a see also reference for a personal name, 530 is a see also reference for a title, etc. In 510 references for corporate bodies, which sometimes change their names, you may notice the subfield $w, which is used to indicate if the heading in the 510 is an earlier ($w a) or later ($w b) form of the heading in the 110 field. For example, on the authority record for USM, "Mississippi Southern College" is shown in the 510 field as an earlier, valid form of the university's name.

260 and 360 fields are "amplified" see and see also references, respectively. They are explanatory references with a "lead-in" statement in $i at the beginning of the field, and can be used to refer catalog users from one type of heading to another, for example:

150 0 Catalogue ...
260 |isubject headings beginning with the word|aCatalog

For an example of a 360 field, see the subject authority record for African Americans.

663 and 664 fields are complex "see also" and "see" references, respectively. They are used for relationships between headings that require explanatory notes, e.g.
664 |aFor this movement included in the composer's unfinished Requiem Mass, search under|bReger, Max, 1873-1916.|tRequiem (Mass)

663 |aWorks by this author are entered under the name used in the item. For a listing of other names used by this author, search also under|bJapp, Alexander H. (Alexander Hay), 1839-1905. 

641 Information on series numbering peculiarities, e.g. 641 Numbering begins with no. 3.

642 Series numbering example. Not used on local series authority records unless numbering is unusually complex.

643 Series place of publication and publisher. 643 New York|bGreenwillow Books

644 Series analysis practice. This indicates whether the library has separate bibliographic records for each title in a series. The code "f" in $a means "fully analyzed." See series authority example for usage of fields 643- 646. The library's holding code is entered in $5.
644 |af|5MUS

645 Series tracing practice. This indicates whether an access point is provided for the series. It is USM's policy to trace all series. The code "t" means "traced." If you are doing series authority work and encounter a record in Validator with code "n" (not traced) in 645 $a, refer it to the authorities librarian.
645 |at|5MUS

646 Series classification practice. The code in $a indicates whether the library classes the volumes in the series together (under a single call number for the entire series) or with a separate call number for each volume. Code c is used for series classed together; use code s if the volumes are classed separately. If the series is classed together, the call number should be entered in the 090 field of the authority record.
646 |ac|5MUS

666 Explanatory reference for names. Provides a note explaining how names having common characteristics are entered in a file.

100 0 De La
666 Names beginning with this prefix may also be entered under La (e.g., La Bretèque, Pierre de) or under the name following the prefix (e.g., Torre, Marie de la).

667 Nonpublic general note. This note is used to provide information for other catalogers who may later use the authority record. It is often used to clarify information about potential confusion between two headings or to instruct catalogers on how to apply the information in the authority record.

667 Give phrase as quoted note.|5DLC
667 Publisher varies.
667 Not same as Smith, Arthur D., 1929-

670 Source data found note. Cites the source of the heading in the 1xx; this is usually the work being cataloged. When creating local authority records, cite the title and date from a record in our database in which the heading appears.
670 The wings of the evening, 1998:|bt.p. (Penelope Morrish)

LC practice calls for the heading as it appears on the work to be given in $b of the 670 field, along with the place in the work where the heading was found (as in the above example). However, when you are creating local authority records based on cataloging records, without the book or other item in hand, omit the $b subfield:

670 Images of the earth, 1998.
If the bibliographic record is for a nonprint item, add the gmd to the 670 in brackets, but do not include the |h:
670 On observance of the Sabbath [microform], 1989.

680 Public general note. Gives information in the OPAC for which a specialized note field has not been defined.
680 Here are entered works on economic relations among nations. Works on foreign economic relations among countries, cities, etc. are entered under headings of the type, [Place]|xForeign economic relations|z[Place].

681 Subject example note. This field contains a note that refers the user to another heading for an example of how the heading is applied in the catalog.
681 |i Example under subdivision|aOfficials and employees.

Bib Services AcquisitionsCatalogingAuthority Control Serials