Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
Folijet
-
-
101
-
R1
-
R1
-
R1
-
R1
-
R1
-
R3
-
R2
-
R1
-
R1
-
R2
Description
When a data import is taking too long (and may have died without an indication), user should have the ability to manually stop that data import job.
TBD: when a job is stopped, what should happen?
- Retain as much as had created/updated properly, and add to log as Completed with errors?
- Roll back everything that may have created/updated, and add to log as Failed?
- Any indication needed that a user stopped the job (and if so, who)?
- What else?
Question - what about existing jobs that are stuck (see EBSCO demo account for examples). Can they be retroactively updated so that they can be stopped?
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-47
Batch Importer (Bib/Acq)
-
- Analysis Complete
-
- is defined by
-
MODSOURMAN-361
Add capability to remove jobs that are stuck in "Running" area of Data Import landing page first pane
-
- Closed
-
-
UIDATIMP-651
Add capability to remove jobs that are stuck in "Running" area of Data Import landing page first pane
-
- Closed
-
-
UIDATIMP-655 Data imports can get stuck at "Running" in the UI when they may actually have completed fully, partially, or not at all
-
- Closed
-
- mentioned in
-
Page Loading...