Update mappings for facet and single item display fields for subjects
Opened this issue · 0 comments
Is your feature request related to new functionality not yet included in the product? Please describe.
CATACOM would like only the following to display in single record display and as facets. All other vocabularies should be suppressed from display. It is important for CATACOM that the workflow for suppressing and making different vocabularies visible is easy and flexible, because Emory users’ needs could change and other vocabularies could become relevant.
6xx second indicator
0 – LC
2 - Medical Subject Headings
7 $2 lcgft LC genre and form headings
7 $2 homoit – homosaurus
7 $2 aat – art and architecture thesaurus
7 $2 rbbin
Binding terms: a thesaurus for use in rare book and special collections cataloguing
7 $2 rbgenr
Genre terms: a thesaurus for use in rare book and special collections cataloguing
7 $2 rbpap
Paper terms: a thesaurus for use in rare book and special collections cataloging
7 $2 rbpri
Printing & publishing evidence: a thesaurus for use in rare book and special collections cataloging
7 $2 rbprov
Provenance evidence: a thesaurus for use in rare book and special collections cataloging
7 $2 rbpub
Printing and publishing evidence: a thesaurus for use in rare book and special collections cataloging
7 $2 rbtyp
Type evidence: a thesaurus for use in rare book and special collections cataloging
Is your feature request related to a problem or a change to existing functionality? Please describe.
CATACOM believes it is important to suppress fields in subject headings and facets that could be considered offensive or not in line with the primary subject heading.
Describe the solution you'd like
See above
Describe alternatives you've considered
There is possibly a larger project that could look at cleaning up catalog data and replacing offensive subject heading terms.
How will this impact users?
This could benefit all users who might find certain terms offensive or confusing.
Additional context
Add any other context or screenshots about the feature request here.