Fast add settings: Default instance status and Suppress from discovery

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

Purpose: There needs to be a way to identify fast add records in Inventory so that they can be deleted (if no longer in use) or turned into real records by catalogers. FOLIO will use the existing "Instance status" for this purpose. The purpose of this story is to allow institutions to set at a tenant level, which of their Instance status values should be used as the default for Fast add record.

Some institutions will want their fast add records to be suppressed from discovery by default while others will not. The purpose of this story is to allow institutions to set their preferred default at a tenant level.

User story statement(s):

As a member of the circ staff
I want my fast add records to be automatically flagged with the correct instance status value
so that they can be later found in Inventory and processed

As a member of the circ staff
I want my fast add records to be automatically set with the correct value for "suppressed from discover"
so I don't make mistakes and set it incorrectly

Scenarios:

  1. Scenario:

    • Given Inventory settings

    • When displayed

    • Then the Instance, Holdings and Items section should display a "Fast add" option

  2. Scenario:

    • Given Settings > Inventory > Fast add

    • When displayed

    • Then:

      • Page header: Fast add

      • Controls:

        • Cancel - Close without saving Reverts to last saved values CB: Changing this because (1) it doesn't make sense to close this page and (2) this is how Settings > Inventory > HRID handling works

        • Save & close CB: Removing the close part because it doesn't make sense to close this pane

        • -X - Same as cancel- CB: Removing this because it doesn't make sense to close this pane.

        • Save and Cancel only become active when form is "dirty" (has unsaved changes)

  3. Scenario:

    • Given Settings > Inventory > Fast add

    • When displayed

    • Then "Default instance status" should display:

      • Dropdown menu

      • Values = All instance statuses defined in Settings > Inventory > Instance status types

      • Default = unselected, option should read "Select instance status" (should be possible to re-select this at any time)

      • Note (and this is out-of-scope for this issue), the default here will drive the default for "Instance status term" in the Fast add form (see )

  4. Scenario:

    • Given Settings > Inventory > Fast add

    • When displayed

    • Then "Default suppress from discovery" should display:

      • Dropdown menu

      • Values = Yes, No

      • Default = Yes

      • Note (and this is out-of-scope for this issue), the default here will drive the default for "Suppress from discovery" in the Fast add form (see )

  5. Scenario:

    • Given Settings > Inventory > Fast add form is dirty

    • When I try to navigate away before saving changes

    • Then the standard unsaved changes popup should display

  6. Scenario:

    • Given Save

    • When clicked

    • Then the settings should be saved (assumption: We will store this in configuration)

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

TestRail: Results

Activity

Show:

Cate BoeremaSeptember 14, 2020 at 10:27 AM

Works beautifully. Thanks !

Cate BoeremaSeptember 11, 2020 at 10:58 AM

Done!

Sergiy SergiyenkoSeptember 11, 2020 at 7:57 AM

Thanks for the review, .
Yes, the "Select instance status" option can be made selectable. Could you change the description when you have a chance?

Cate BoeremaSeptember 10, 2020 at 2:31 PM

this works great! The only thing (and I should have added a scenario for this) is that you can't unselect a Default instance status. Can you please make it possible to re-select "Select instance status"? Thanks!

Cate BoeremaSeptember 8, 2020 at 1:08 PM

I just wanted to say that basically we can do without the Cancel button. This is how the ConfigManager component works by default, which is used in places where you do not see this button.

Oh, yes, I agree. My comment above was specifically about the patterns in play for Settings pages that do not contain controlled vocab CRUD.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 17, 2020 at 11:51 AM
Updated October 14, 2020 at 4:51 PM
Resolved September 14, 2020 at 10:27 AM
TestRail: Cases
TestRail: Runs