Batch Importer (Bib/Acq) (UXPROD-47)

[UXPROD-4257] Data Import Architecture Refinements (Quesnelia) Created: 02/May/23  Updated: 06/Feb/24

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: LC-priority2, SolutionArchitecture, data-import, di-swat, epam-folijet, loc, needs-t-shirt-size-BE, needs-t-shirt-size-FE, possible-quesnelia
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Continues
is continued by UXPROD-4469 Data Import Architecture Refinements ... Open
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
is defined by MODDATAIMP-743 2 SPIKE: Design approach for DI to re... Open
is defined by MODDATAIMP-922 [SPIKE] Report User Friendly Errors Closed
is defined by MODDICORE-251 1 SPIKE: Investigate support of multi... Closed
is defined by MODSOURMAN-1042 Delete All Source Records Belonging T... Closed
Relates
relates to UXPROD-3145 Remove SRS and Data Import Debris Draft
relates to UXPROD-4471 Remove step of initial saving of inco... In Progress
Release: Quesnelia (R1 2024)
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Small < 3 days
Front End Estimator: Olamide Kolawole
Front-End Confidence factor: 90%
Back End Estimate: XL < 15 days
Back End Estimator: Ryan Taylor
Back-End Confidence factor: 90%
Development Team: Folijet
PO Rank: 120

 Description   

Next steps:

  • POs/Olamide/Kate review this feature
  • categorize the types of changes
  • split into Q and post-Q
  • for post-Q, can we organize into a multi-release roadmap

Status

  • 14 Sept 2023: 1st high-level review done, next: move the post-Q out and then re-review/refine the possible Q issues

Current situation or problem: Various infrastructure changes to improve the performance of source record storage

Possible changes

  • Delete old, unused versions of MARC records
  • reformat SRS data schema

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 02/May/23 ]

Hi Kateryna Senchenko I created this feature per our conversation from last week. There ma be other issues in the Poppy Misc feature that we should re-link to it. Should we mark this feature as Poppy?

Comment by Ryan Taylor [ 10/Oct/23 ]

Discussed with Olamide, Kate, & Ann-Marie and we decided to only commit to the top 3 stories initially prioritized for this feature. Stories 4-10 will be moved to Ramsons' Architecture feature and can be pulled into Quesnelia as Stretch work if capacity allows. Based on these changes, we've lowered the Back End estimate from XXXL to XL.

The following stories moved to UXPROD-4469 Data Import Architecture Refinements (Ramsons) and given Folijet-Quesnelia-Stretch tag

    4.) MODSOURCE-631: 4 SPIKE: figure out a way to clean up records created by a cancelled job
    5.) MODINV-844: 5 Discard Duplicate Data Import Events
    6.) MODDATAIMP-923 Open 6 Expose Incoming Record Journey Through The System (5)
    7.) MODSOURMAN-1028 Open 7 Save Journal Records in Batches (3)
    8.) MODSOURCE-678 Open 8 Optimize events process query (3)
    9.) MODDATAIMP-789 Open 9 SPIKE: Design solution to clean up temp data (5)
    10.) MODSOURCE-623 Open 10 SPIKE: Reduce Connection Pool Size When Connections Are Idle (2)

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