Assign tags to Request Records

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

As a staff person
I want to be able to assign, unassign, view, and output tags in a FOLIO Request 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-requests Request record. Tags have already been deployed in ui-users. See STSMACOM-113 for any additional details that may be needed.

Testing Scenarios
Test the following scenarios to ensure that the Tags smart component was implemented properly:

1. Scenario 1 Fails, but I created a separate bug for this: UITAG-21
   • Given Given Enable tags = Y in Settings > Tags > General per FOLIO-1302
   • When a User displays an Request record in an Requests app search result
   • Then the Tags Icon should display at the top right of the record in the third pane, between the Edit Pencil icon and the Notes icon.
2. Scenario 2
   • Given the Tags Icon
   • When tags are already assigned to a particular record
   • Then the system should display the number of tags to the left of the Tags Icon.
3. Scenario 3
   • Given the Tags Icon
   • When it is clicked
   • Then a fourth pane with tag details (hereafter called the Tags Pane) should open to the right of the existing panes, similar to the Notes pane
4. Scenario 4
   • Given the Tags Pane
   • When it has been opened as the fourth pane
   • Then it should stay defaulted to open, even if a user clicks on a different record in the second pane search results, changing to the tags relevant to that newly-selected record
5. Scenario 5
   • 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
6. Scenario 6
   • Given the Tag Pane 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"
7. Scenario 7
   • Given the Tag Pane text entry box
   • When a user attempts to type an upper-case letter
   • Then convert to lower-case
8. Scenario 8
   • Given the Tag Pane 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
9. Scenario 9
   • Given the Tag Pane 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 fourth pane
     • With a green callout message saying "New tag created" abreaux, this isn't working in Requests or Users. Is it still a priority or did the design change?
10. Scenario 10
    • Given the Tags Pane
    • When a new tag is assigned to a record
    • Then the number of tags in the Sub-header and the number next to the Tags icon should increase by 1
11. Scenario 11
    • Given the Tags Pane
    • When a tag is unassigned from a record (by clicking the "x" for that tag)
    • Then the number of tags in the Sub-header and the number next to the Tags icon should decrease by 1

Note: The Tags component is being refactored in Q1 2019. For questions about what may have changed, please contact dmtkachenko. Also, abreaux (PO for Tags) also suggests that Tag developers join the # entity-tags Slack channel. Thanks!