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

Create interactive log-summary of batchload results, initial prep

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      Small < 3 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      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.
    • Development Team:
      Folijet
    • Calculated Total Rank:
      98
    • PO Rank:
      87.9
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • 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: 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: 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

      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

            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. MODSOURMAN-160 Sequence of records in the log does not match the sequence in the imported file

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

            Bug - A problem which impairs or prevents the functions of the product. MODSOURMAN-212 Backend requests for View All Logs screen ignore query params

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSOURMAN-215 Remove logDto and jobExecuitonDto entities

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

            Umbrella - MODSOURMAN-219 Design and implement journal service for job executions and data import process

            • 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. MODSOURMAN-222 Create API for getting logs with sort functionality

            • 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. MODSOURMAN-227 Implement journal service rest api

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UIDATIMP-285 Create "view all" log screen

            • 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-286 Search details for the "view all" log screen

            • 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-287 Filter details for the "view all" log screen

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

            Task - A task that needs to be done. UIDATIMP-301 Support ordering when retrieving logs

            • 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-304 Update BE calls for retrieving logs and jobExecutions

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

            Task - A task that needs to be done. UIDATIMP-310 Update query for sorting by numeric field

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

            New Feature - New feature requests UXPROD-2200 Create interactive log-summary of batchload results, next steps

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

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Analysis Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Front End Estimator:
                Taras Tkachenko Taras Tkachenko
                Back End Estimator:
                Oleksii Kuzminov Oleksii Kuzminov
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases