The metadata team is a forum for discussing metadata-related discovery topics for the catalog requiring shared policy or infrastructure. The team will investigate use cases, issues, and approaches, interface with stakeholders, and ultimately propose recommendations for the development team to respond to. Additionally, this team facilitates knowledge sharing among its members – setting up a communication/support structure where members can grow their knowledge of the data components (which Marc fields are extracted, how data gets mapped to shared data model, what gets indexed, what’s used for display, etc) of the shared catalog infrastructure.
Contact email@example.com with any questions for the team.
- Lynn Whittenberger, (co-lead) North Carolina State University Associate Head, Acquisitions and Discovery (Monographs)
- Kelly Farrell, (co-lead) TRLN Program Officer
- Dennis Christman, Duke University Metadata Transformation Librarian
- Cory Lown, Duke University Application Development Project Lead
- Anna Goslen, University of North Carolina at Chapel Hill Metadata Librarian
- Michelle Cronquist, University of North Carolina at Chapel Hill Special Collections Cataloger
- Genia Kazymova, TRLN Applications Developer
- Gabriel Israel, North Carolina State University, University Library Specialist
Subject Heading Remapping
In an effort to improve the subject terms used in TRLN’s discovery layer to better represent diverse populations, and to change existing subject terms that may be exclusionary or divisive, the Metadata Team is collecting suggestions to overlay existing problematic subject headings with alternative vocabulary terms.
Contact firstname.lastname@example.org with any questions about this program.
About the Process
The TRLN Discovery Metadata Team reviews, researches, and documents decisions made for each suggested term. A public list of requests and the status of review by the team is available at https://bit.ly/trlnsubjects. Some terms have been extensively discussed in broader communities and we can point to this work when making our recommendations, but some suggestions may require collaboration with the TRLN Metadata Interest Group, subject matter experts, and other stakeholders to determine whether a term should be remapped as part of this program and what is the preferred term.
Ultimately, the TRLN Discovery product owners review the recommended terms to remap and if they approve, the terms are added to the configuration file and visible to end users.
New, In Progress, and Completed Requests
- Submit a new request.
- Review requests the Metadata Team is currently processing.
- Access the full list of remapped subject headings.
How does subject remapping work?
Remapping a subject heading does not change the MARC record data or search results, but rather changes subject data that displays to the end user. Additionally, remapped headings must be specified at the whole subdivision level. This requires some repetition in the configuration file, but this also accommodates nuance in the remappings. If a user searches for “illegal aliens”, they will return results using this term; however the subject facet and the item record’s subject will display “Undocumented immigrants”. The remapping only applies to subject headings. If “Illegal aliens” displays elsewhere, such as title, then this information will not be overlaid with “Undocumented immigrants”.
Presentations about subject remapping
- OCLC Cataloging Community Meeting, Second Session (recording)
- Remapping LC Subject Headings in TRLN Discovery (slides) for RUSA Decolonizing the Catalog: Anti-Racist Description Practices from Authority Records to Discovery Layers