Purpose:

User story statement(s):

As a FOLIO system administrator with appropriate permissions, I want to configure criteria for determining what records should be contributed to the central server so that the system can properly limit the records that are contributed.

Scenarios:

1. Scenario:

   • Given the Record Contribution Settings Group (UIINREACH-18)

   • When the user selects "Contribution Criteria"

   • Then a new pane appears with a form containing a pull-down menu to select a configured central server for which to create a new contribution criteria configuration, along with an inactive "Save & close" button

2. Scenario:

   • Given the previous scenario

   • When the user selects a central server from the list

   • Then the following additional form fields appear:

     • Multi-select field of FOLIO locations to always exclude from contribution

     • Single-select field of FOLIO statistical codes with Statistical Code Type of "INN-Reach" (this code type will be created as part of initial setup of mod-inn-reach, out of scope for this story) to indicate that a record should be contributed but suppressed from central discovery (INN-Reach contribution code "l") (Display as <statistical code type name>: <statistical code code> - <statistical code names>)

     • Single-select field of FOLIO statistical codes with Statistical Code Type of "INN-Reach" to indicate that a record should not be contributed (INN-Reach contribution code "z") (Display as <statistical code type name>: <statistical code code> - <statistical code names>)

     • Single-select field of FOLIO statistical codes with Statistical Code Type of "INN-Reach" to indicate that a record should be contributed as a "provided by the consortium" (INN-Reach contribution code "g") (Display as <statistical code type name>: <statistical code code> - <statistical code names>)

3. Scenario:

   • Given an existing contribution criteria configuration exists for any selected central server

   • When the user selects the central server

   • Then the form fields that appear should be pre-populated according to that configuration

4. Scenario:

   • Given the previous scenarios

   • When the user configures one or more of the option fields

   • Then the "Save & close" button should become active

5. Scenario:

   • Given that an optional field has been modified

   • When the user attempts to navigate away from the modified form

   • Then a standard "are you sure" modal should be presented with options to "keep editing" or "close without saving" should be presented

6. Scenario:

   • Given the "are you sure" modal

   • When the user selects "keep editing"

   • Then they are returned to the in-progress form

7. Scenario:

   • Given the "are you sure" modal

   • When the user selects "close without saving"

   • Then they continue navigating to wherever they were attempting to navigate

8. Scenario:

   • Given a modified form

   • When the user selects "Save & close"

   • Then the configuration for the selected central server is saved