Optimal Setup for Discovery of Forms following LC move from use of $v subdivisions with preference for lcgft
See Best Practices for Decision Pages and Tags for groups
Legend: not started IN PROGRESS STALLED decided
Status | IN PROGRESS |
|---|---|
Description | Review effect of LC lack of $v subdivisions with preference for lcgft in discovery; determine if recommendation from RM for discovery configuration is needed |
Decision summary |
|
Owning group | RM-OST (SILS-RM-L@listserv.ucop.edu) |
Approver | RM-OST |
Consulted | CDL Sysops |
Informed | Discovery |
Decision-making process |
|
Priority | High |
Target decision date | [type // to add Date] |
Date decided | [type // to add Date] |
Recommendation
Impact
Stakeholder group | Impact |
|---|---|
CDL Sysops | Setup in configuration; best to align with reindexing schedule (starts in May/November) |
Campus discovery administrators | Setup in configuration; best to align with reindexing schedule (starts in May/November) |
Reasoning
As of January 2026, the Library of Congress discontinued the use of 6XX subfield v to indicate form of resource in lieu of using 655 lcgft terms. We have and will continue to have records that will forms in 6XX $v, 655 lcgft (or other terms) or a combination of both. We would like to make recommendations that will optimize discovery of these materials given this mixed MARC21 coding.
Background
Options Considered
Description | Turn on index_5xx_authority_fields | Utilize Primo VE default normalization rules for Subject and Genre display | Display only 655 in Genre | Set up advanced genre search index | Add 655 to advanced subject search index and rename as Subject/Genre | Enable Genre facet in Primo VE |
|---|---|---|---|---|---|---|
| Option 1 | Option 2 | Option 3 | Option 4 | Option 5 | Option 6 |
Documentation/information | Primo would index terms in authority record 5XX fields Needs to be done on the NZ level? | Moves subject $v to Genre https://docs.google.com/document/d/1n0Ddq0ijeSbipEd7-bQXd_8Hw8F5qaqN6HihRD2_r4E/edit?usp=sharing | Keep full strings in Subject; display only 655 in Genre. UCLA example: https://docs.google.com/document/d/1M19_wcTdFXNoVh4M6TdcSz7ZnLBIH7h_AQ7_ez1T1Gg/edit?usp=sharing |
|
|
|
Campuses that have implemented |
|
| UCLA | UCSD, UCLA |
| UCSD, UCLA |
Examples |
| Example on UCSB PSB Default, so easy to configure and troubleshoot |
|
|
|
|
Pros | Users searching on a form subdivision such as “fiction” will retrieve the record if the term is a broader term in an authority record. | Attempts to collocate all genre terms together | Metadata is displayed as intended |
|
| Allows users to filter results based on genre PrimoVE Genre facet includes 6XX subfield v terms, as well as 655 subfield a terms |
Cons | Related terms that are not necessarily equivalents
Could defeat the purpose of having narrower terms | If setup as links in record to allow for advanced searching, subject searching does not input the genre term, and therefore increases recall Form subdivisions and genre/form terms often use different terminology. | Genre is disproportionately available for newer records and not for older records. |
|
| Cannot remove foreign-language terms from facet list. |
Dependencies
Reindex of the NZ is needed for some of these options. We would ideally want to align with the semi-annual reindexing rather than requesting an off-cycle reindex.
Questions to consider
How are results/recall impacted?
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|
Talk to colleagues who have implemented any of these at ELUNA/C. Busselen | May 1, 2026 |
| NOT STARTED |
|
|
|
|