Record Contribution: Provide management interface for record contribution jobs in INN-Reach (Current Contribution)

Description

Purpose:

Provide an interface to initiate and mange initial/bulk record contribution jobs for INN-Reach. (Simplified)

Enhanced version of this story has been moved to UIINREACH-55

User story statement(s):

As a user with permission to initiate bulk record contribution for INN-Reach, I want to see if a bulk record contribution job has been started and start one if not.

Scenarios:

  1. Scenario:

    • Given a user with appropriate permissions

    • When the user accesses INN-Reach settings

    • Then a "Manage record contribution jobs" settings item is present in the "Record contribution" settings section

  2. Scenario:

    • Given the "Manage record contribution jobs" settings item

    • When the user selects that settings item

    • Then they are presented with a pane featuring a single-select pull-down menu to select a central server

  3. Secnario

    • Given the menu of central servers

    • When the user selects one

    • Then A "dashboard"-like interface is presented (see attached screenshots)

      • Features segmented button interface with "Current Contribution" and "Contribution history" labels

  4. Scenario

    • Given that no previous record contribution job has been started

    • When the user selects the "Current contribution" (default)

    • Then The following information is displayed

      • The "Initial contribution status" is "not started"

      • Material to item type mapping is either valid or invalid

        • Depends on whether all FOLIO material types are currently mapped to an INN-Reach item type ("real-time" status)

      • FOLIO to INN-Reach locations is valid or invalid

        • Dependent on the presence of, at least, Library mappings and all mapped locations are contributed to the central server

      • Contribution Started (datetime stamp) is empty

      • Started by is empty

      • Contribution complete is empty

      • Total FOLIO instance records is current number of instance records

      • An "Initiate contribution" button is at the bottom of the screenshots

        • If the "Material to item type mapping" and "FOLIO to INN-Reach locations" are valid, then the button is active. Otherwise, the button is inactive

          • Add some kind of tooltip to indicate that valid mappings are required to initiate contribution

  5. Scenario

    • Given that at least one record contribution job has been initiated (and in-progress)

    • When the user selects the "Current contribution" (default)

    • Then The following information is displayed

      • The "Initial contribution status" is "in-progress"

      • Material to item type mapping is either valid or invalid

        • Depends on whether all FOLIO material types are currently mapped to an INN-Reach item type ("real-time" status)

      • FOLIO to INN-Reach locations is valid or invalid

        • Dependent on the presence of, at least, default mappings and all mapped locations are contributed to the central server

      • Contribution Started (datetime stamp) is set to when the contribution was initiated

      • Started by set to the user who initiated the contribution job

      • Contribution complete is empty

      • Total FOLIO instance records is the number of instance records to be evaluated

  6. Scenario

    • Given that a record contribution is in a "in-progress" state

    • When a job completes (all records have been evaluated for contribution and all contributed records have been submitted to the central server)

    • Then the record contribution job complete and the screen is updated to indicate

      • The "Initial contribution status" is "complete"

      • Material to item type mapping is either valid or invalid

        • Depends on whether all FOLIO material types are currently mapped to an INN-Reach item type ("real-time" status)

      • FOLIO to INN-Reach locations is valid or invalid

        • Dependent on the presence of, at least, default mappings and all mapped locations are contributed to the central server

      • Contribution Started (datetime stamp) is set to when the contribution was initiated

      • Started by set to the user who initiated the contribution job

      • Contribution complete is set to the datetime the job completed

      • Total FOLIO instance records is the number of instance records being evaluated

      • Inactive "Initiate contribution" button at the bottom-right of the screen

      • The "Cancel contribution" button is removed

      • "Success" toast is presented indicating that the job has been completed

Additional Information:

Mockup Slides: https://docs.google.com/presentation/d/1GVBJin8Ei3sFZdosLyxZc9OojqcylXZoHG7tOcxJIbU/edit?usp=sharing

Environment

None

Potential Workaround

None

Attachments

5

Checklist

hide

TestRail: Results

Activity

Show:

Igor Godlevskyi August 30, 2021 at 4:49 PM

Oleksandr Oliinyk August 17, 2021 at 3:48 PM

  thanks, we will keep the validation

Brooks Travis August 17, 2021 at 3:22 PM

 I updated that part of the story. I want to hold off on removing it until you have a chance to look at it and let me know if it seems manageable in this part of the work. You should be able to retrieve the list of contributed locations from the central server using the D2IR APIs (API docs, pg. 23), and then compare it to what should be contributed.

Oleksandr Oliinyk August 17, 2021 at 12:05 PM

As discussed on refinement we exclude locations validation from both front and back-end related stories. The validation if further needed will be added as improvement in separate stories.

Oleksandr Oliinyk August 17, 2021 at 8:12 AM

Hello

Could you please clarify FOLIO to INN-Reach locations is valid or invalid requirement and how to properly perform this validation.

1)  presence of, at least, default mappings - what are default mappings? Is it applicable for both type of mappings Library/Location?

2) all mapped locations are contributed to the central server - how to verify if they are contributed?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 27, 2021 at 7:06 AM
Updated September 17, 2021 at 11:20 AM
Resolved August 30, 2021 at 4:47 PM
TestRail: Cases
TestRail: Runs