Tags - Basic (UXPROD-250)

[UXPROD-251] Be able to create, delete, display, output tags to individual records within apps Created: 22/Feb/18  Updated: 16/Sep/20  Resolved: 17/Sep/18

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2018
Parent: Tags - Basic

Type: New Feature Priority: P3
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ann-Marie Breaux (Inactive)
Resolution: Done Votes: 0
Labels: phase_1, tags
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-250 Tags - Basic In Progress
Relates
relates to STSMACOM-113 Tags on individual records: Assign, U... Closed
relates to UIU-660 Number of tags should update simultan... Closed
relates to UXPROD-1115 Be able to output tags from individua... Analysis Complete
Epic Link: Tags - Basic
Analysis Estimate: Small < 3 days
Analysis Estimator: Ann-Marie Breaux (Inactive)
Front End Estimate: XL < 15 days
Front End Estimator: Jakub Skoczen
Back End Estimate: XL < 15 days
Back End Estimator: Jakub Skoczen
Estimation Notes and Assumptions: Assumes this include the back end for initial implementation
Development Team: Prokopovych
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R5
Rank: GBV (MVP Sum 2020): R2
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

For v1, users should be able to create new tags, assign pre-existing tags, or delete tags from a record in an app. Allow for autosuggest/type ahead when a user is assigning a tag to a record. Behind the scenes, tags would be tracked in only one master tag list across an entire FOLIO implementation, not separate tag lists per app.

A few comments from Jakub: do tags live in the individual records or in a central list?
o If stored in each record, then might not need a central list
o Central list built from what’s in the individual tags; mostly used for autocomplete.
o Store in record for v1 perhaps, vs store/manage centrally.
o Biggest implications are reporting and faceting.

Include tags as data elements available from all FOLIO apps that allow them, so that they can be output for reporting purposes (would this happen by default?) Be part of the data that the records send to the data lake.

A few comments from Jakub: with regards to outputting for reporting: talk to Vince, since he’s doing data lake est; reporting system needs to get the tag values, not just the IDs, so needs a translation fxn



 Comments   
Comment by Ann-Marie Breaux (Inactive) [ 28/Feb/18 ]

Dev T-shirt estimate from Jakub: Front-end: XL, Back-end: XL

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

Holly Mistlebauer Hi Holly - I see that all of these tags features were downgraded in priority. Keep in mind these are critical for acquisitions, if libraries expect to be able to assign any reporting categories. We are expecting to support those reporting categories/codes via tags, and are not building a different field into the order, invoice, vendor, fund, etc records. Adding Dennis Bridges in case he wants to weigh in.

Comment by Cate Boerema (Inactive) [ 17/Sep/18 ]

Ann-Marie Breaux, there is only one story in this feature and it has the status of "In Review". This means the feature itself should also be "In Review". I will update the status for you now, as I am trying to get an accurate picture of what is happening for Q3.

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

All the remaining problems with STSMACOM-113 Closed were completed or moved to separate Jira stories or bugs. Closed STSMACOM-113 Closed , so this feature is DONE!

Comment by Cate Boerema (Inactive) [ 18/Sep/18 ]

Congrats!!

Comment by Cate Boerema (Inactive) [ 18/Sep/18 ]

Congrats!!

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

Hooray!!

Generated at Fri Feb 09 00:06:48 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.