Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2200

Create interactive log-summary of batchload results, next steps

    XMLWordPrintable

Details

    • Not Scheduled
    • Medium < 5 days
    • XXL < 30 days
    • Low
    • Small < 3 days
    • Hide
      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.
      Show
      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.
    • Folijet
    • 73
    • 85
    • R3
    • R1
    • R1
    • R1
    • R2
    • R1
    • R4
    • R2
    • R4
    • R1
    • R1
    • R1
    • R4
    • R1
    • 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
      • 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)

      TestRail: Results

        Attachments

          Issue Links

            defines

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-764 Import job summary page - Export UUIDs for SRS records - DRAFT

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-47 Batch Importer (Bib/Acq)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Analysis Complete
            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-128 UI: Search - DRAFT

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-129 SPIKE: UI: Search: Filter options - DRAFT

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-222 Add pagination for viewing logs - DRAFT

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-308 Search details for individual records in the "View all" log screen

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Blocked

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-320 Summary screen for an individual import job log

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-321 Details screen for an individual import job log: Pane 1

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-322 Errors accordion of the Summary screen for an individual import job log - DRAFT

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Draft

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-328 Details screen for an individual import job log: Pane 2

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-329 Details screen for an individual import job log: Pane 3

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Bug - A problem which impairs or prevents the functions of the product. UIDATIMP-601 Log filter dropdowns by job profile and user are not in alphabetical order

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-615 Add column for Job status and Resequence columns

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            New Feature - New feature requests UXPROD-661 Create interactive log-summary of batchload results, initial prep

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests UXPROD-3502 Enhancements to the Data Import log (Morning Glory)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. UIDATIMP-655 Data imports can get stuck at "Running" in the UI when they may actually have completed fully, partially, or not at all

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2753 Data Import Log - "lite version"

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2802 NFR: Handle implicit/explicit actions in job profiles

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            New Feature - New feature requests UXPROD-2939 Data Import Log - refine error handling

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-3363 Data Import Log - refine error handling, part 2

            • P2 - normal priority level, must be included in the current development cycle
            • Draft

            New Feature - New feature requests UXPROD-3695 Additional Changes to the Data Import log - DRAFT

            • P2 - normal priority level, must be included in the current development cycle
            • Draft
            mentioned in

            Page Loading...

            Activity

              People

                abreaux Ann-Marie Breaux
                abreaux Ann-Marie Breaux
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Taras Tkachenko Taras Tkachenko
                Oleksii Kuzminov Oleksii Kuzminov
                Votes:
                1 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases