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

[UXPROD-2200] Create interactive log-summary of batchload results, next steps Created: 16/Dec/19  Updated: 03/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 1
Labels: Lehigh(round_ii+mvp), bdf-logging, cap-mvp, cornell-priority, data-import, delimited_files, marcimport, po-mvp, q4-2019-spillover
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UIDATIMP-764 Import job summary page - Export UUID... Draft
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
is defined by UIDATIMP-320 Summary screen for an individual impo... Open
is defined by UIDATIMP-321 Details screen for an individual impo... Open
is defined by UIDATIMP-328 Details screen for an individual impo... Open
is defined by UIDATIMP-329 Details screen for an individual impo... Open
is defined by UIDATIMP-615 Add column for Job status and Reseque... Closed
is defined by UIDATIMP-601 Log filter dropdowns by job profile a... Closed
is defined by UIDATIMP-128 UI: Search - DRAFT Draft
is defined by UIDATIMP-129 SPIKE: UI: Search: Filter options - D... Draft
is defined by UIDATIMP-222 Add pagination for viewing logs - DRAFT Draft
is defined by UIDATIMP-322 Errors accordion of the Summary scree... Draft
is defined by UIDATIMP-764 Import job summary page - Export UUID... Draft
is defined by UIDATIMP-308 Search details for individual records... Blocked
Relates
relates to UXPROD-3502 Enhancements to the Data Import log (... Closed
relates to UXPROD-661 Create interactive log-summary of bat... Closed
relates to UIDATIMP-655 Data imports can get stuck at "Runnin... Closed
relates to UXPROD-2753 Data Import Log - "lite version" Closed
relates to UXPROD-2939 Data Import Log - refine error handling Closed
relates to UXPROD-2802 NFR: Handle implicit/explicit actions... Draft
relates to UXPROD-3363 Data Import Log - refine error handli... Draft
relates to UXPROD-3695 Additional Changes to the Data Import... Draft
Release: Not Scheduled
Epic Link: Batch Importer (Bib/Acq)
Analysis Estimate: Medium < 5 days
Analysis Estimator: Niels Erik Nielsen
Front End Estimate: XXL < 30 days
Front End Estimator: Taras Tkachenko
Front-End Confidence factor: Low
Back End Estimate: Small < 3 days
Back End Estimator: Oleksii Kuzminov
Estimation Notes and Assumptions: This issue covers the display of import logs in a UI. By "interactive" I assume the description means that the log report is filterable and sortable? More elaborate configuration options, like choice of display columns or cross tabulating data would obviously have a significant impact on the estimates.

I'm not immediately clear if this issue also covers the writing of logs for display. The estimate assumes that it does but I have no up-front clear view of the complexity of say, error record reports with resolution info. Could potentially be quite involved before all possible error scenarios are covered. Users or developers with experience in this kind of applications might be able to qualify these doubts and assumptions and thus the estimates. Confidence is set to low.
Development Team: Folijet
Kiwi Planning Points (DO NOT CHANGE): 73
PO Rank: 85
Rank: Chalmers (Impl Aut 2019): R3
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R2
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R4
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): 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
  • reliable and stable

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)



 Comments   
Comment by Debra Howell [ 29/Sep/20 ]

Ann-Marie Breaux and Holly Mistlebauer - Requesting an update on this feature. This is a showstopper for Cornell.

Comment by Molly Driscoll [ 23/Jul/21 ]

Ann-Marie Breaux, does this feature cover being able to access the imported record in Inventory from the log screen? If not, is there another feature or story that speaks to that? I have a library interested in creating/ranking that feature if it does not exist. Thanks!

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