[FOLIO-3862] Spike | Investigate if Data import task force development will impact ECS development Created: 25/Jul/23  Updated: 06/Nov/23  Resolved: 06/Nov/23

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Khalilah Gambrell Assignee: Taras Spashchenko
Resolution: Done Votes: 0
Labels: SolutionArchitecture, data-import, ecs
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-4141 Import and create/update a shared ins... Closed
relates to UXPROD-4259 DI processing updates for matching an... Closed
relates to UXPROD-4278 Sharing & Linking MARC authority records Closed
Sprint: DITF - Sprint 170
Development Team: Data Import Task Force
Release: Poppy (R2 2023)

 Description   

DoD: 6. Analyze and document impact on Consortium functionality

Context

For Enhanced Consortia Support (ECS) development, there will be updates for importing MARC bib and MARC authority records. 

  • Consortia (aka Central) tenant will have the ability to import records that can be shared to other libraries or local to the tenant.
  • Local tenant will have the ability to import records that are local to the tenant or shared to other tenants based on permissions. 

Spike needs to 

  • Review consortia technical design(s) for data import 
  • Document findings > if the planned data import task force development will impact consortia development
  • Present findings to data import task force and Folijet/Spitfire dev leads to determine next steps

Documentation



 Comments   
Comment by Taras Spashchenko [ 21/Aug/23 ]

Based on the analysis of git branches and PRs created in data-import-raml-storage mod-source-record-manager mod-data-import ui-data-import modules by DI Task Force team and UXPROD features UXPROD-4141 Closed UXPROD-4259 Closed UXPROD-4278 Closed , these changes do not affect or intersect with changes needed for Enhanced Consortial Support (ECS) in these modules.

Generated at Thu Feb 08 23:31:21 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.