INN-Reach Record Contribution: Configure Item Contribution Options

Description

Purpose:

Due to variance items states between FOLIO and those supported by INN-Reach , some affordance needs to be made to allow a FOLIO system administrator to indicate what item status should be indicated on a contributed item record.

User story statement(s):

As a FOLIO administrator,
I want configure item contribution options
so that FOLIO can properly indicate item status for contributed items

Scenarios:

  1. Scenario:

    • Given an "Item contribution options" item under the "Record contribution" collection in INN-Reach settings

    • When the user selects the item

    • Then a pane with a menu to select a configured central server is presented

  2. Scenario:

    • Given the pane with the central server selection menu

    • When the user selects a central server

    • Then a form with the following multi-select fields are presented (and any existing configuration retrieved and displayed) along with an inactive "Save" button:

      • "Not available" statuses:

        • A list of FOLIO item states/statuses that does not include: "Available", "Checked out", "Paged", "In transit", "Declared lost", "Withdrawn", "Awaiting pickup",  and "Aged to lost"

      • "Non-lendable" loan types:

        • A list of all FOLIO loan types

      • "Non-lendable" locations:

        • A list of all FOLIO shelving locations

      • "Non-lendable" material types:

        • A list of all FOLIO material types

  3. Scenario:

    • Given the form

    • When the user fills in/changes one or more form field

    • Then the "Save" button becomes active

  4. Scenario:

    • Given the form has been changed

    • When the user attempts to navigate away from the form

    • Then a standard "are you sure" modal is presented

  5. Scenario:

    • Given the form has been changed and the "Save" button is active

    • When the user activates the save button

    • Then the configuration is saved to the backend and a success toast is presented

  6. Scenario:

    • Given an attempt to save the form

    • When the there is an error returned by the backend or some other error

    • Then an error toast is presented in the user is returned to the in-progress form

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Tim AugerDecember 18, 2023 at 7:37 PM

I asked Brooks if I could take a stab and the language here. will do.

Oleksii PetrenkoJuly 6, 2021 at 8:49 AM

Demoed. Closing.

Separate story will be added to backlog for verification with backend

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Volaris

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created June 14, 2021 at 6:43 AM
Updated December 18, 2023 at 7:37 PM
Resolved July 6, 2021 at 8:49 AM
TestRail: Cases
TestRail: Runs