[UXPROD-4472] Phase 2 ECS authority control investigation Created: 20/Sep/23  Updated: 06/Feb/24

Status: Analysis Complete
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)

Type: New Feature Priority: P3
Reporter: Christine Schultz-Richert Assignee: Christine Schultz-Richert
Resolution: Unresolved Votes: 0
Labels: LC-priority2, ecs, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Requires
requires UIMARCAUTH-266 SPIKE Update Authority control report... Open
requires UIIN-2679 Effective location options not shown ... Closed
Release: Not Scheduled
Back End Estimate: Medium < 5 days
Back-End Confidence factor: 100%
Development Team: Spitfire
PO Rank: 0

 Description   

Current situation or problem: This feature summarizes potential work to consider for phase 2 ECS development, particularly related to authority control and authority records. This feature is intended to capture work concerning investigation and technical design for authority control in an ECS environment.

Proposed solution/stories - Investigate the following: 

  • Ability to promote a local MARC authority record
  • Ability to update a shared MARC authority record via Data import in a member tenant
  • Updates to authority control reporting
  • Propagate shadow authority records to member tenants that are created after authority records are loaded into central tenant

Links to additional info

Questions



 Comments   
Comment by Natalia Zaitseva [ 03/Nov/23 ]

as per the Q Release Planning session, we agreed on the following:

  • in Q release Kalibek Turgumbayev will work on the approach
  • the implementation part will be considered in the R Release

Estimation provided:
Back-End: M (5 days) for review (assumed that review from back-end will not be needed in Q release)
Front-End: to be review after approach defined

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