Entity Management (UXPROD-787)

[UXPROD-2517] Entity Management App. Update cached authorities/entities with external updates 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

Issue links:
Gantt End to Start
has to be done after UXPROD-2516 Entity Management App. Cache external... Open
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): R3
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R2

 Description   

Purpose:
The cached datasets will be updated by the dataset creators; as such, there needs to be a mechanism to update those datasets without losing the various connection points with other types of records (e.g.: bibliographic MARC records, etc.).

Use case:
As a metadata operations staff member, I need to update pref labels (e.g.: LCNAF records where a death date is added to a heading), and also manage merged authorities, split authorities and deleted authorities, for example. Authority and entity datasets are updated with varying frequencies. These external updates may or may not overwrite local updates/enhancements to those records in the local system.

Dependencies/Context:
Reliant on having completed "Cache external authorities/entities" ( UXPROD-2516 Open ). Must account for "Add data points / enhance external authority/entity data" feature".

Notes from the Entity Management Working Group:
The extent of the update workflow should be defined further. I.e.: is there an automated process that goes out and pulls in updates for which authority? Is it all externally mediated? etc.


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