Entity Management App. Reporting on "unmatched" headings
Description
Priority
Labels
Fix versions
None
Development Team
None
Assignee
Solution Architect
None
NoneParent Field Value
None
Parent Status
None
Checklist
hideTestRail: Results
Activity
Show:
Reporter

Rank: 5Colleges (Full Jul 2021)
R4
Rank: Cornell (Full Sum 2021)
R2
Rank: GBV (MVP Sum 2020)
R4
Rank: TAMU (MVP Jan 2021)
R2
Rank: Chicago (MVP Sum 2020)
R2
Rank: U of AL (MVP Oct 2020)
R1
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 17, 2020 at 3:29 PM
Updated November 18, 2024 at 4:05 PM
TestRail: Cases
TestRail: Runs
Purpose:
For identified fields in MARC SRS or other datastores, report headings that are not matched to an entity/authoriity stored/cached in FOLIO. Report should include UUID for the source record as well as the unmatched heading, etc.
Use case:
Unmatched heading lists are reviewed to determine if there are errors in bibliographic record headings, when a new authority record is needed, and/or if an authority record needs to be updated.
Notes from the Entity Management Working Group:
TBD: What other sort of reporting features are needed?