Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-763

Import job summary page - Values for record and error columns

    XMLWordPrintable

Details

    • Folijet Sprint 104, Folijet Sprint 105, Folijet Sprint 106, Folijet Sprint 107
    • 3
    • Folijet

    Description

      Purpose: To provide the values used in the import job summary screen for various record types and the error column

      As a staff person viewing the summary screen for an imported job
      I want to see which records were created or updated, and if there were errors
      So that I can be aware of successful imports and errors

      Scenarios

      1. Scenario 1
        • Given the individual import job summary page
        • When viewing the columns for the various record types (SRS MARC Bib, Instance, Holdings, Item, Order, Invoice)
        • Then display one of the following values for each row (record in the incoming file) and column (FOLIO record type)
          • Created (if that record type was created)
          • Updated (if that record type was updated; for MARC records, this includes both the Modify and Update actions)
          • Multiple (if that record type was both created and updated, e.g. 1 existing holdings record being updated by an incoming record and 1 new holdings record being created by that same incoming record)
          • Discarded (1) if the import job has some actions for that record type, but for that particular title, there was no action for that record type, e.g. if matched, update an item record; if no match, take no action. "Take no action" would trigger the Discarded status, or 2) if the job stopped before creating/updating that record type due to an error)
          • - (hyphen) If that record type was not supposed to be affected by the job. For now the Order and Invoice columns will always specify "-"
      2. Scenario 2
        • Given the Individual import job summary page
        • When viewing the Error column
        • Then leave it blank if there was no error
        • And use value Error if there was an error
        • No need for more details here. The errors will be more specific on subsequent log detail pages
      3. Scenario 3
        • Ensure this story passes Accessibility testing
      4. Scenario 4
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Mariia_Aloshyna Mariia Aloshyna
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases