Uploaded image for project: 'ui-inventory'
  1. ui-inventory
  2. UIIN-1211

Fast add settings: Default instance status and Suppress from discovery

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 5.0.0
    • Labels:
    • Template:
    • Sprint:
      Core: F - Sprint 96, Core: F - Sprint 97
    • Story Points:
      5
    • Development Team:
      Prokopovych

      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 UIPCIR-7)
      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 UIPCIR-7)
      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)

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                SergiySergiyenko Sergiy Sergiyenko
                Reporter:
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases