Tags - Basic (UXPROD-250)

[UITAG-18] Tags permissions: Enabling tag app in general Created: 09/Apr/18  Updated: 04/Oct/21  Resolved: 02/Aug/18

Status: Closed
Project: ui-tags
Components: None
Affects versions: None
Fix versions: None
Parent: Tags - Basic

Type: Story Priority: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Michal Kuklis
Resolution: Done Votes: 0
Labels: demo43, phase_1, sprint42, sprint43, tags, ui-core
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File 21-Tags Setting Option.JPG     JPEG File 22-Enable Tags Setting - Not Checked.JPG     JPEG File 23-Enable Tags Setting - Checked.JPG     JPEG File 24-Unsaved changes message.JPG    
Issue links:
Relates
relates to UITAG-8 Change "Enable Tags" default Closed
relates to UITAG-21 Enable Tags Checkbox in Settings Not ... Closed
relates to STSMACOM-113 Tags on individual records: Assign, U... Closed
relates to UXPROD-489 Tag permissions-individual records Analysis Complete
Sprint:
Development Team: Prokopovych
Tester Assignee: Ann-Marie Breaux (Inactive)
Epic Link: Tags - Basic

 Description   

Purpose: To be able to enable the tags "helper app" across an individual FOLIO tenant

As a systems librarian or department manager
I want to be able to enable the tags helper app across FOLIO
So that users can assign tags to records within individual main apps of FOLIO.

Scenarios

  1. Scenario
    • Given FOLIO Settings
    • When displayed
    • Then a new section called "Tags" should display in alphabetical order along with the other sections (Calendar, Circulation etc) as shown in the attached mockup
  2. Scenario
    • Given Settings > Tags
    • When Displayed
    • Then a "General" section should display in the second pane as shown in the attached mockup
  3. Scenario
    • Given Settings > Tags > General
    • When displayed
    • Then and "Enable tags" checkbox should display (checked by default )
  4. Scenario
    • Given Settings > Tags > General
    • When the page isn't "dirty" (i.e. there ARE NOT unsaved changes)
    • Then the save button should be disabled
  5. Scenario
    • Given Settings > Tags > General
    • When the page is "dirty" (i.e. there ARE unsaved changes)
    • Then the save button should be enabled
  6. Scenario
    • Given Settings > Tags > General has unsaved changes
    • When user attempts to navigate away to another part of FOLIO (within the same browser tab)
    • Then the unsaved changes modal should display
  7. Scenario
    • Given Settings > Tags > General
    • When a change is successfully saved
    • Then the "Setting was successfully updated" save confirmation is displayed as shown in the attached mock-up

See attached screenshots
21. New "tags" section in settings
22. Only 1 general setting - allow tags or not
23. If checkbox is checked, enable the save and show the standard save success message
24. If checkbox if changed, and save is not pressed, display standard unsaved changes message if user attempts to navigate away from the page.

Note that the Tags app will not appear as an app with a UI icon until Phase 2 of the Tags app work. For Phase 1, tags will only be visible on individual records within FOLIO. There will be a central list of tags assigned across a FOLIO tenant in Phase 1, but it will not have a UI.



 Comments   
Comment by Cate Boerema (Inactive) [ 09/Apr/18 ]

This is great, Ann-Marie Breaux! I would split this story, as it includes some fairly distinct functionality. I'd create one story for the setting to enable/disable tags on a tenant basis (let's mention the expectation that this would turn tags on/off in every app where tags have been integrated (at least I think that's the idea)). It would be great if you could include a wireframe showing where and how that should be done in Settings.

Then, I'd then create a number of additional stories for the user tag management permissions. For the user permission stories, it would be great if you could add a tab to the permissions google sheet for tags to summarize all the Tag permissions. Then you create one story for each permissions similar to LIBAPP-147 Closed , LIBAPP-148 Closed and LIBAPP-149 Closed .

I think you have some time to get these details together, as the first step on Tags will be to get the basics going ( STSMACOM-113 Closed ). I'd mark this story DRAFT in the meantime. You can also move it to the development project (user stories don't belong in UXPROD). I believe Tags stories should be filed in the STCOM or STSMACOM projects. Jakub Skoczen, which is the correct one?

Thanks!

Comment by Jakub Skoczen [ 09/Apr/18 ]

Cate Boerema Ann-Marie Breaux Agree, we need to start with the basics and build backend and UI component prerequisites for STSMACOM-113 Closed first. As far as STSMACOM-113 Closed is concerned – it mentions a standalone Tags app, if that's the case then we will need a new Jira project for it (e.g UITAGS) we will also most likely need a new backend module for tag "management" and new Jira project for that (MODTAGS). As far as the UI component is concerned – I am not sure the assignment control will be a smart component, like say the one for Notes. If we keep tags as strings on the records (which seems like the likely option) it depends on the level of validations we would like to enable.

Comment by Ann-Marie Breaux (Inactive) [ 09/Apr/18 ]

Thanks, Jakub Skoczen and Cate Boerema I'll work on making these changes today. Could someone build UITAGS? I don't think I'm allowed. Once it's built, I'll rename these stories over to it. A-M

Comment by Ann-Marie Breaux (Inactive) [ 09/Apr/18 ]

Thanks, Cate Boerema I'll break this into multiple stories. I clearly don't understand what all goes in one user story versus being broken into separate stories!

Comment by Cate Boerema (Inactive) [ 10/Jul/18 ]

Hi Ann-Marie Breaux, scenario 1 of this story is a bit confusing. I suggest we take it out. Also, I think we really need to pull the requirements out of the mockup and put them as scenarios in the story. You don't need to change the mockups, but it would be good to add these requirements in text. So, I am thinking we replace your current scenario 1 with something like the following. Your current scenario 2 is fine and can stay at the end.

  1. Scenario
    • Given Folio Settings
    • When displayed
    • Then a new section called "Tags" should display in alphabetical order along with the other sections (Calendar, Circulation etc) as shown in the attached mockup
  2. Scenario
    • Given Settings > Tags
    • When Displayed
    • Then a "General" section should display in the second pane as shown in the attached mocks
  3. Scenario
    • Given Settings > Tags > General
    • When displayed
    • Then and "Enable tags" checkbox should display (unchecked by default )
  4. Scenario
    • Given Settings > Tags > General
    • When the page isn't "dirty" (i.e. there are no unsaved changes)
    • Then the save button should be disabled
  5. Scenario
    • Given Settings > Tags > General
    • When the page is "dirty" (i.e. there ARE unsaved changes)
    • Then the save button should be enabled
  6. Scenario
    • Given Settings > Tags > General has unsaved changes
    • When user attempts to navigate away to another part of FOLIO (within the same browser tab)
    • Then the unsaved changes modal should display
  7. Scenario
    • Given Settings > Tags > General
    • When a change is successfully saved
    • Then the "Setting was successfully updated" save confirmation is displayed as shown in the attached mock-up
Comment by Ann-Marie Breaux (Inactive) [ 11/Jul/18 ]

Cate Boerema Thank you for writing the user stories for me! I've updated as you noted. Clearly I didn't pick up on the level of detail needed in the user stories! A-M

Comment by Michal Kuklis [ 13/Jul/18 ]

The work for this story has been done. We now have a new ui-tags module: https://github.com/folio-org/ui-tags

Jakub Skoczen we need to add it to our CI. I'm not sure what the correct procedure for registering it is. Is this something John Malconian could help with?
Also the mod-tags have to be turned on on the vagrant box. I talked to Wayne Schneider and he is on top of that already.

Comment by John Malconian [ 13/Jul/18 ]

Michal Kuklis Looks like you or someone else added the Jenkinsfile so that automatically adds it to CI. I've also added @folio.tags to 'platform-core'. Next step would be for Wayne Schneider and I to coordinate getting the module into the nightly builds.

Comment by Michal Kuklis [ 23/Jul/18 ]

Thank you John Malconian!

Wayne Schneider I added the @folio/tags to package.json and stripes.config.js in folio-testing-platform:

https://github.com/folio-org/folio-testing-platform/blob/master/package.json#L25
https://github.com/folio-org/folio-testing-platform/blob/master/stripes.config.js#L22

but I wonder if there is anything else which has to happen in order for the nightly build to pick tags up.

Comment by Wayne Schneider [ 23/Jul/18 ]

Michal Kuklis – adding it to folio-testing-platform should do it for now. Thanks!

Comment by Ann-Marie Breaux (Inactive) [ 30/Jul/18 ]

Michal Kuklis Hi Michal - I can't test this in folio-snapshot-stable yet, but checked it in folio-testing and folio-snapshot. I can't get past scenario 3 for testing. The third pane with general settings never opens. Switching back to In Progress. Once corrected, I'll keep it In Review until folio-snapshot-stable is available for final testing.

Comment by Michal Kuklis [ 31/Jul/18 ]

Thanks Ann-Marie Breaux. Yes this is very strange. This works fine on my local env so something must be off in those environments. I will look around to see if I can spot what is going on.

Comment by Michal Kuklis [ 31/Jul/18 ]

Ann-Marie Breaux it looks like the third pane is showing up now at least in folio-testing

Comment by Ann-Marie Breaux (Inactive) [ 02/Aug/18 ]

Good job Michal Kuklis all looks good in folio-snapshot-stable. Thank you!!

Comment by Ann-Marie Breaux (Inactive) [ 25/Sep/18 ]

I realized the default setting is unchecked, so created a bug ( UITAG-8 Closed ) to switch teh default to checked (enabled), as it should be, per scenario 3 above. Otherwise, every time there's an update of a tenant, a library's tags disappear (though they are still attached to records and in the central tag list, just disabled)

Generated at Thu Feb 08 23:12:20 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.