Details
-
New Feature
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
customfield_11200 17546
-
Medium < 5 days
-
XXL < 30 days
-
Small < 3 days
-
Low
-
-
Folijet
-
-
87.9
-
R4
-
R1
-
R1
-
R1
-
R2
-
R1
-
R4
-
R4
-
R1
-
R1
-
R1
-
R4
-
R1
-
R1
Description
After batch load is completed, create an interactive results log/dashboard/report, with data such as:
- load stats (date, time, # actions)
- new records created
- existing records merged or overlaid with new data
- deleted record, or records marked for deletion
- problem/error records that were set aside during the load, with info about the problem to allow the user to resolve
Comments from Jon Miller/Chicago in the context of Data Migration, July 2019:
I added support for the Source Record Storage module to my general purpose file loader app https://github.com/jemiller0/Folio. For loading using the API it uses the batch API. It is the first test case that I have that makes use of an API that accepts and array of objects. It's a work in progress. It doesn't do much with regard to handling the HTTP response at this point (for example, parsing out the error messages)
Comments from Lisa McColl/Lehigh
I know we've had conversations on what constitutes an error. A "success" could be successful from the computer's point of view, but not what you intended. An "error" could mean the system failed or that intended consequences were recognized. I definitely think errors should be reported, so I don't think this is an interface issue, but I would like to be clear for system behavior as to what constitutes an error. Do we have this worked out? If not, do we need to work it out now? Thank you! (edited)
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-47 Batch Importer (Bib/Acq)
-
- Analysis Complete
-
- is defined by
-
MODSOURMAN-160 Sequence of records in the log does not match the sequence in the imported file
-
- Closed
-
-
MODSOURMAN-212 Backend requests for View All Logs screen ignore query params
-
- Closed
-
-
MODSOURMAN-215 Remove logDto and jobExecuitonDto entities
-
- Closed
-
-
MODSOURMAN-219 Design and implement journal service for job executions and data import process
-
- Closed
-
-
MODSOURMAN-222 Create API for getting logs with sort functionality
-
- Closed
-
-
MODSOURMAN-227 Implement journal service rest api
-
- Closed
-
-
UIDATIMP-285 Create "view all" log screen
-
- Closed
-
-
UIDATIMP-286 Search details for the "view all" log screen
-
- Closed
-
-
UIDATIMP-287 Filter details for the "view all" log screen
-
- Closed
-
-
UIDATIMP-301 Support ordering when retrieving logs
-
- Closed
-
-
UIDATIMP-304 Update BE calls for retrieving logs and jobExecutions
-
- Closed
-
-
UIDATIMP-310 Update query for sorting by numeric field
-
- Closed
-
- relates to
-
UXPROD-2200 Create interactive log-summary of batchload results, next steps
-
- Open
-