Free Blogger Templates

Library of Congress to Expand Use of LC Genre/Form Terms (LCGFT) and Implement Subject Heading (LCSH and CYAC—Children & Young Adult) Cataloging Simplification

January 09, 2026

 

Library of Congress to Expand Use of LC Genre/Form Terms (LCGFT) and Implement Subject Heading (LCSH and CYAC—Children & Young Adult)



📌 Library of Congress – Subject Cataloging Update (Effective Feb 2, 2026)

🎯 What’s Changing?

LC will no longer add form subdivisions ($v) to the end of subject heading strings.
➡️ Instead, subject form concepts will be expressed using LC Genre/Form Terms (LCGFT). 

🗓 Effective Date

February 2, 2026 

📘 Why This Change?

✔ Simplify Library of Congress Subject Headings (LCSH & CYAC) cataloging
✔ Support BIBFRAME & linked data environments
✔ Facilitate the use of URIs for subject authority records
✔ Improve clarity and consistency in cataloging practice 

🔍 Key Practice Change

Old method:

  • Use form subdivision ($v) at the end of subject strings

  • Example: Human rights workers $v Diaries 

New method:

  • Keep subject term clean

  • Add separate Genre/Form Term (LCGFT) entry

  • Example:

    • Human rights workers (subject)

    • Diaries (genre/form) (LCGFT) 

📈 Benefits

⭐ Shorter, clearer subject headings
⭐ Better alignment with faceted vocabularies
⭐ Easier linked data integration
⭐ More robust machine processing

🧠 Notes

❗ LC will not retroactively convert records already cataloged using $v. 

❗ Institutions are not required to follow this practice—they can choose based on their workflows. 


LCSH LCGFT FAQ



📌 Library of Congress – Subject Cataloging Change (LCGFT & Form Subdivisions FAQ)

📅 Effective Date
February 2, 2026
(The change in practice begins) 

💡 What’s New?
LC will omit form subdivisions ($v) in Library of Congress Subject Headings (LCSH) and use LC Genre/Form Terms (LCGFT) instead. 

📦 Scope of Change
✔ Applies to new LC records cataloged via the BIBFRAME editor Marva.
✔ Includes rare materials & CYAC subject strings using LCGFT. 

🚫 Not Retroactive
Existing records are not automatically converted. 

🧰 Process
The change will occur via automated updates + human review when cataloging in Marva.

🔍 Impact on Catalogs & OPAC
• Form info will shift to separate genre/form filters.
• OPAC users will need to use genre/form as a filter when searching.

📌 Authority Records & Terms
✔ LC will continue to maintain authority records for $v subdivisions.
✔ No new proposals will be accepted for form subdivisions; proposals will only be for LCGFT. 

🧠 Ongoing Work
LC is reviewing existing $v terms and proposing new LCGFT equivalents to replace them. 

🧩 Audience & Other Data
Audience aspects from old form subdivisions may be recorded via LC Demographic Group Terms (LCDGT) instead of $v. 


Additional guidelines provided by the Library of Congress:

Starting today, Monday, February 2, 2026, we will expand use of LCGFT in LC cataloging while implementing a simplification to subject cataloging by ceasing to use form subdivisions.   This change is to MARC cataloging and BIBFRAME cataloging.

Form subdivisions should no longer be added to subject headings in either format.  In MARC, add an appropriate LCGFT term to 655, and LCDGT term to 385 as needed.  In BIBFRAME, choose an appropriate genre/form from LCGFT and choose an appropriate LCDGT term to indicate Intended Audience as needed.

PTCP has updated related SHM instructions and will continue to address $v subfield information and examples.

Expect to see the following changes in the BIBFRAME/Marva environment:

  1. The form subdivisions will be automatically removed from the ends of subject headings of records imported from FOLIO to Marva and the BIBFRAME database.  PTCP has mapped an existing form subdivision to its appropriate LCGFT, and in some cases also an LCDGT term for Intended Audience.  For example, the form subdivision “Maps for children” will be removed from the end of a subject heading and added as the GenreForm term “Children’s maps” to the BIBFRAME description.  “Children” will be added as the Intended Audience.

Note that this does not mean that the mapping is correct or best. Please evaluate the conversion output according to the LCGFT Manual.

  1. Even if there is no automatically added LCGFT, evaluate your resource to see if LCGFT is needed. 
  2. Some existing form subdivisions may require special consideration when removed from their subject and added as a standalone GenreForm; they will be checked during “Validation.”  A guidance message will be displayed.
  3. The ability to add form subdivisions to subject headings will not be possible.
  4. If a form subdivision isn't established at LCGFT, please put it as literal value in the BIBFRAME Genre/Form element. The system will accept the data and convert it to 655 $a with 2nd indicator 4.

 


See Also:

References:

1. Announcement: LC to Expand use of LCGFT and Implement Subject Heading Cataloging Simplification

2. FAQ on omission of $v subfield in LCSH and expanded use of LCGFT

Tags: