Music Library Association Best Practices for category of work

Routinely record the element in authority records if giving category of work as a component of an access point, that is, if the preferred title consists of the name of one or more types of composition. Record the element for other works if readily ascertainable. Do not record types of composition terms that are:

• terms indicating a number of performers (e.g., Duets)
• tempo markings (e.g., Allegros)
• other generic terms that do not convey formal characteristics (e.g., Pieces, Music)

For bibliographic records, consider a genre heading to record category of work.

In MARC: In authority records: Record as a structured description using field 380 subfield $a. If no appropriate controlled term is available an unstructured description may be used instead.

In bibliographic records: Generally do not use field 380 unless directed by local policy. Prefer recording genre terms in field 655 instead.

See examples in MARC format: category of work

Generally do not apply the option in authority records unless no appropriate controlled term is available and it is deemed necessary for description or access. For uncontrolled terms, follow the formatting guidelines in Descriptive Cataloging Manual, Z1. Name and Series Authority Records (also available through Cataloger's Desktop), that is, record uncontrolled terms in the singular form and capitalize the first word of the term.

Prefer terms from the Library of Congress Genre/Form Terms thesaurus. Do not use terms that describe only the characteristics of an expression (e.g., Expression: format of notated music). Refer to Best Practices for Using LCGFT for Music Resources for detailed guidance.

In MARC: If recording a term from the recommended vocabulary encoding scheme, indicate the source of information using the $2 code lcgft.

In MARC: In bibliographic records: Generally do not apply the option using field 008 bytes 18-19, field 006 bytes 01-02, or field 047 in new cataloging unless directed by local policy. In existing records, generally do not update field 008 bytes 18-19 or 006 bytes 01-02 unless directed by local policy.