Tags - Basic
(UXPROD-250)
|
|
| Status: | Analysis Complete |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD | Parent: | Tags - Basic |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Ann-Marie Breaux (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | phase_1, round_iv, tags | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Release: | Not Scheduled | ||||||||||||||||||||||||||||
| Epic Link: | Tags - Basic | ||||||||||||||||||||||||||||
| Analysis Estimate: | Small < 3 days | ||||||||||||||||||||||||||||
| Analysis Estimator: | Ann-Marie Breaux (Inactive) | ||||||||||||||||||||||||||||
| Front End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||
| Front End Estimator: | Michal Kuklis | ||||||||||||||||||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||||||||||||||||||
| Back End Estimate: | Small < 3 days | ||||||||||||||||||||||||||||
| Back End Estimator: | Heikki Levanto | ||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | As it is now, the modules that use tags already have a field called "tags" that contains the tag strings, so they should be easily available for any export and print function. But that is only the tag string, if they want descriptions etc, it is up to each print/export program to expand them. That should not be too hard, but it is up to each module to do their thin. If we change the way tags are stored, storing UUIDs, these bets are off. | ||||||||||||||||||||||||||||
| PO Rank: | 48 | ||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R2 | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R4 | ||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||
| Description |
|
For v1, users should be able to output/export tags data along with all the other data in the individual record, for export and reporting purposes. Those tags should be considered part of the record for output purposes, e.g. printing and exporting. Note: this feature was separated from
Users should also be able to print tags along with the rest of the record that the tags are associated with. 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. Comment 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 Frontend is basically: when a user presses export or print for the individual record, they get tags along with the rest of the record. |
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 17/Sep/18 ] |
|
Heikki LevantoZak Burke Hi guys - this is a portion of the tags work that I split off from a larger feature, since it is less important and is somewhat blocked (no exporting from FOLIO yet). Could you estimate front-end and back-end when you have a chance? |
| Comment by Cate Boerema (Inactive) [ 18/Sep/18 ] |
|
Hi Ann-Marie Breaux, this is not for Q3, correct? I am removing the Q3 fix version. |
| Comment by Ann-Marie Breaux (Inactive) [ 18/Sep/18 ] |
|
Whoops, yes, correct - blame it on copying the previous issue and not removing the Q3 |
| Comment by Cate Boerema (Inactive) [ 05/Dec/18 ] |
|
Removing Q1 2019 fix version due to limited capacity in Q1 2019. |