NFR: R2 2022 Morning Glory: Implement flow control for Data Import

Description

Implement flow control as a way to ensure that Inventory Single Record Import jobs do not get stuck behind large import jobs.

For additional details, see ARCH-14 and https://folio-org.atlassian.net/wiki/display/FOLIJET/ARCH-14%3A+Investigate+opportunity+to+not+take+extended+time+for+OCLC+single+record+import+while+large+file+is+importing. Architectural review in Lotus, but implementation will not be until Morning Glory

NOTE Description of the Inventory Single Record Import process drafted in the scope of MODCPCT-38: https://docs.google.com/document/d/1LI3THKLH1C5ovrzvqzt3V6isP0Q1xTxwN0KKTh-hj8k/edit?usp=sharing

NOTE Spitfire implementing Delete MARC Authorities via UI in Morning Glory UXPROD-3517 - those import jobs should also take priority over large import jobs

Priority

Development Team

Folijet

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux April 1, 2022 at 12:24 AM

Good to know - thanks, .

Do we need to add a story to account for MARC Authority deletes? These are individual record deletes, triggered from the MARC Authority app UI, and we need to make sure that they do not get stuck behind long-processing import jobs. These were not taken into account when the feature was first scoped, but may be necessary to provide a decent UX. See for more details. Or maybe Spitfire should add a testing/review task to their UXPROD-3517?

cc:

Vladimir Shalaev March 23, 2022 at 12:08 PM

IMO this ticket is solving not the general performance of OCLC import issues, but parallel jobs - big data import and OCLC

Ann-Marie Breaux March 23, 2022 at 10:25 AM

Hi and Please see 's comments on MODSOURMAN-716. Is this feature still needed if the Inventory Single Record Import "creates" are faster now? I'm thinking probably yes, but I'm not sure. To make this feature unnecessary means that
1. We need to ensure that Inventory Single Record Imports (creates or updates) do not get stuck behind long-processing import jobs
2. We need to ensure that MARC Authority deletes (which are individual record deletes, triggered from the MARC Authority app UI) do not get stuck behind long-processing import jobs. These were not taken into account when the feature was first scoped, but may be necessary to provide a decent UX. See .

Kateryna Senchenko February 11, 2022 at 2:40 PM

Hi , I don't think we'll need additional Karate tests, checking the main functionality with existing tests should suffice. Thank you!

Ann-Marie Breaux February 11, 2022 at 6:02 AM

Hi One more question about this feature - will we need any new or adjusted Karate tests?

Done

Details

Reporter

PO Rank

125

Front End Estimate

Out of scope

Front-End Confidence factor

High

Back End Estimate

XL < 15 days

Back End Estimator

Release

Morning Glory (R2 2022)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 4, 2022 at 2:10 PM
Updated June 29, 2022 at 2:23 PM
Resolved June 14, 2022 at 6:11 PM
TestRail: Cases
TestRail: Runs