Entity Management (UXPROD-787)

[UXPROD-2523] Entity Management App. Reporting on "unmatched" headings Created: 17/Jun/20  Updated: 09/Dec/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Entity Management

Type: New Feature Priority: P3
Reporter: Jason Kovari Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Entity Management
Development Team: None
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R1

 Description   

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?


Generated at Fri Feb 09 00:24:40 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.