Assign tags to Inventory Holdings

Purpose: To display, assign, unassign, and output tags associated with individual HOLDINGS records within the FOLIO Inventory app.

As a staff person
I want to be able to assign, unassign, view, and output tags in a FOLIO Inventory Holdings record
So that I can categorize records for filtering and reporting purposes.

Tags are meant to be labels that can be assigned to individual data records in various FOLIO apps. Tags will be used as a visual indicator in the record, to gather records in some way, and to facilitate reporting. This is a cross-app “helper app,” similar to how the Notes app is envisioned. However, unlike notes, the tags need to be easily accessible as part of the record for filtering and output purposes. [Filtering and output are separate, future stories.]

Scenario
Use Tags smart component to introduce Tag CRUD in the ui-inventory *Holdings*record. Tags have already been deployed in ui-users. See STSMACOM-113 for any additional details that may be needed.

Testing Scenarios
Test scenarios 2-7 ensure that the Tags smart component was implemented properly:

1. Scenario 1
   • Given the Inventory Holdings view details screen (full-screen view)
   • When viewing the data in the Holdings record
   • Then insert a new Accordion for Tags
     • Below the Holdings Detail accordion and above the Holdings notes accordion
     • And make the Tags accordion closed if no tags are assigned, but open if tags are assigned
     • And include a count of the assigned tags in the header pane when the Tags accordion is closed.
     • See examples from Data Import Field Mapping profile, attached
2. Scenario 2
   • Given the Tag Pane text entry box
   • When a user starts typing
   • Then FOLIO should auto-suggest existing options from the FOLIO central tag list, as follows:
     • Start suggesting as soon as the user starts typing
     • Auto-suggest looks for the typed string no matter where it appears in the existing tag
     • Any existing tags that start with the string should be presented at the top of the list in alphabetical order, followed by existing tags that have the string embedded in them, also in alphabetical order
3. Scenario 3
   • Given the Tags text entry box
   • When a user types a space or pipe character
   • Ignore that character when creating the tag (e.g. "do this" would become tag "dothis"
4. Scenario 4
   • Given the Tags text entry box
   • When a user attempts to type an upper-case letter
   • Then convert to lower-case
5. Scenario 5
   • Given the Tags text entry box
   • When the user sees an appropriate tag in the auto-suggest list
   • Then they should be able to select it by clicking on it or scrolling down to it and pressing Enter, thereby completing the text in the text entry box with the auto-suggestion
6. Scenario 6
   • Given the Tags text entry box
   • When the user enters text, presses "Enter," and the Tag does not already exist in the Library's central tag list.
   • Then the tag should be created as follows
     • Add to the record's tag list in the Tags accordion
     • With a green callout message saying "New tag created"
7. Scenario 7
   • Given the Tags text entry box
   • When a user clicks the x next to a specific tag
   • Then the tag should be removed from that record's list
   • And the number of tags in the Tags accordion header should decrease by 1