Score Cataloging Checklist
I. Connexion
· Fixed Field Elements
o ELvl: For new records or when upgrading to RDA, use [blank].
o Srce: New record: use d. When upgrading to RDA, accept what is present.
o Rules: New record: use i. Ensure that variable fields have appropriate ending punctuation (a period in most cases).
o FMus
§ For RDA record, use l (lower case L) for score, score with part(s), and music for a solo instrument.
§ Use code b (miniature or study score) or c (accompaniment reduced for keyboard) as appropriate.
§ Use code z for a set of parts.
§ See full list of codes in Bib. Formats and Standards.
o DtSt and Dates
§ t = Publication date and copyright date. Okay to enter same date in Date 1 and Date 2 when publication date and copyright date are the same (e.g., 2021,2021).
Check to make sure both dates are present in 264 fields.
§ See Bib. Formats and Standards for full list of codes and order of precedence.
028: For both publisher's numbers and plate numbers, put 2 in 2nd indicator. No 500 note is necessary.
· 040: Add ǂe rda if upgrading to RDA. Also make sure $b eng is present.
· 050: If field is present, accept as is.
When entering the field:
o 1st indicator = blank; 2nd indicator = 0
o If using only one cutter, enter cutter in ǂb.
M25 ǂb .B415 no. 1 1979
M1001 ǂb .B813 op. 98 2004
M1010 ǂb .M939 K.525 1960
If using two cutters, the first will go in $a, the second in $b.
M312.H415 ǂb E9 1950
· 100: For creator of work.
o For a compilation of works by different composers, do not give a 100 field.
o For collaborative work, generally, either the person with principal responsibility or the first named person will be given in the 100.
o Control the access point.
· 240: Uniform title of a single work; or a collective title for two or more works by the same composer (e.g., Sonatas, piano. $k Selections). Field does not end with a period.
· 245: Ensure correct subfield coding and ISBD punctuation.
· 264, Publication statement: If field ends with a closing square bracket, ending period is not given.
· 300: No period after cm, unless a series statement in field 490 is given.
· 490: Give series statement(s) as needed. Use 1st indicator 1 if the series is traced (8XX is present).
· Fields 336, 337, and 338:
336 notated music ǂb ntm ǂ2 rdacontent
337 unmediated ǂb n ǂ2 rdamedia
338 volume ǂb nc ǂ2 rdacarrier
· Field 348 $a: Choose appropriate term(s) from the following list. When giving 2 or more terms, enter in separate 348 fields.
choir book
chorus score
condensed score
part
piano conductor part
piano score
score
study score
table book
violin conductor part
vocal score
· 348 $c: Give appropriate term for form of musical notation.
348 $c staff notation $2 rdafmn
Note: The 348 field can also be added with the Music Toolkit. See the 655 section below.
· 382: Add appropriate terms from LCMPT. Ensure correct subfield coding.
Note: These can be added with the Music Toolkit, after you have added LCSH terms. See the 655 entry below. Always verify that the MoP terms are correct. Make revisions as needed.
· 6XX: Give appropriate subject headings. Be sure to control the headings.
o Once subject headings are added, run the Music Toolkit macro to add form/genre headings (655s) and 382 fields.
Note: If you are enhancing a record, and deleting or making a change to one or more subject headings, be sure to remove any FAST headings. These will be in field 655, with a $2 subfield containing the code fast. Also look for any 648 fields that contain a date or time period. These should also be removed.
· 655: Add appropriate form/genre terms. These can be added automatically with the Music Toolkit macro. Ensure terms are correct and appropriate. Control all terms.
· 7XX fields: Add appropriate access points for editors, arrangers, works and/or expressions, etc. Be sure to control headings/access points.
· 800: Add heading for series, as appropriate.
· Validate the record, make any corrections, then validate again.
· Replace the record.
Prior to exporting
If the record contains non-LCSH terms, delete them locally (do not remove them from the OCLC master record).
· Non-LCSH terms will be in 6XX fields, with 2nd indicator values other than 0.
· If the 2nd indicator is set to 7, the field will also have a subfield $2 containing a code that indicates the source vocabulary (e.g., fast, att).
· Export the record.
II. Alma
· Holdings Record
o Select the appropriate Sublocation and Shelving location codes.
§ You can select these from dropdown menus: Place the cursor in the 852 field, then press <Ctrl> + <F>.
o 852 field: 1st indicator should always be 0 (zero), so that the number files in the LC index.
o Call number formatting
1 cutter: Enter class number in $$h, and the remainder of the call number in $$i:
$$h M25 $$i .B415 no. 1 1979
$$h M1001 $$i .B813 op. 98 2004
$$h M1010 $$i .M939 K.525 1960
2 cutters: Enter class number and 1st cutter in $$h, and the remainder of the call number in $$i:
$$h M312.H415 $$i E9 1950
See the Sibley Cataloging Wiki for additional examples and marking procedures.
Note: After creating holdings record with LC-based call number, do a call number browse in Alma to ensure that it indexes correctly (i.e., has 0 in 852 1st indicator)
· Item record
o Material type: Music Score
o Always add a Copy ID, even if there is only one copy.
o Set temporary location:
§ Select the Yes radio button.
§ Most scores should be sent to Sib Music Bindery.
§ Use Sib Music Brittle Books for brittle scores.
o Write call number on title page (or first page of music, if there is no title page).
§ For brittle scores, also write call number in lower left corner of cover.
o Fasten barcode with paperclip next to call number.
· Place scores going to bindery in the wooden bookcase in the main hallway of the cat. department.
· Place brittle scores on the Brittle Books shelves on the wall of the cat. department.