Staff Slips
(UXPROD-19)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Sunflower (R3 2024) | Parent: | Staff Slips |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Darcy Branchini | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | Folijet-UI-candiate, acs, lc-priority4, loc, round_iv, staff_slips, staff_slips_tokens | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Staff Slips | ||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | 30% | ||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Khalilah Gambrell | ||||||||||||||||||||||||||||||||||||||||||||
| Back-End Confidence factor: | 30% | ||||||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Scope should be limited to Large (BE and FE estimates) | ||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Vega | ||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 9 | ||||||||||||||||||||||||||||||||||||||||||||
| PO Ranking Note: | Additional fields not yet available on user record. | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R1 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Purpose/Problem: As of 7/19/21, the RA SIG identified the following user tokens that should be added:
Since almost all of these fields/tokens are all on the user record, except current date/time, I'm capturing these as one feature and will close
|
| Comments |
| Comment by David Bottorff [ 09/Jul/19 ] |
|
Chicago can wait up to a year. |
| Comment by Erin Nettifee [ 06/Aug/19 ] |
|
Darcy Branchini - question about this one. I looked at the tokens Google sheet https://docs.google.com/spreadsheets/d/13Xnb7j-xt0CZrgD9zRuH3OBX_bxR8FNl94F52Lom9gM/edit?usp=sharing Duke is very interested in having preferred name as a token, and I can see that it's captured in the spreadsheet. We would like that for go-live once preferred name is implemented. (
We'd also like to see proxy tokens, which don't appear to be captured in the Google Sheet. It's worth convo with RA probably, but I think we'd want to have available proxy first name, last name, preferred name, and sponsor first name, last name, preferred name. There was also a question about whether patron address is captured as a notice token - which could be important for any institutions that want to mail slips to patrons as opposed to using email. |
| Comment by Darcy Branchini [ 07/Aug/19 ] |
|
Erin Nettifee, I think we might need to clarify what these are – staff slips are intended for staff-use only. Patron notices, which right now is email only but print and SMS are planned for later, are intended for patron use. Right now we have a hold and transit slip, and we're planning for a paging request slip too. Does that change your need for preferred name on these? |
| Comment by Erin Nettifee [ 07/Aug/19 ] |
|
Hi Darcy, I guess I got confused since I was looking at the token list which appears to be a global token list (or at least it's labeled as patron tokens.) I think these are needed for patron-facing notices, but you're right that that it's not as much of a need for staff slips. Is there another UXPROD tracking potential future tokens for patron-facing notices? |
| Comment by Darcy Branchini [ 07/Aug/19 ] |
|
Thanks for the clarification Erin Nettifee. And for future reference, there's a separate Google Doc for staff slip tokens - https://docs.google.com/spreadsheets/d/1kP3jrlG4jxIAR-hRYCAGId6F875KC_-YZ7svxlRItU0/edit?usp=sharing. Also, to answer your question, there is a different UXPROD for future (user) tokens for patron facing notices –
|
| Comment by Erin Nettifee [ 07/Aug/19 ] |
|
Thanks Darcy - appreciate your patience with me. |
| Comment by Anya [ 29/Oct/21 ] |
|
julie.bickle - do you know when this will be added to FOLIO - Okanagan would like to add this to their notices.
CC Ross Tyner |
| Comment by Molly Driscoll [ 30/Nov/21 ] |
|
julie.bickle do we have a timeline for development of this feature? It's being requested by more and more libraries that would like to leverage the preferred first name token on records where it is present. For reference, both Lafayette College and Okanagan College have asked about this feature recently. |
| Comment by patty.wanninger [ 30/Nov/21 ] |
|
Ann-Marie Breaux Could Folijet look at this as a follow-on to creating the "preferred name" for display and perhaps also create it as a token? |
| Comment by Ann-Marie Breaux (Inactive) [ 30/Nov/21 ] |
|
Hi patty.wanninger I'm not sure. There's no stories defined n the feature, and no mockups. If you can confirm that there's no backend work, and add story(s) with mockups, we'll take a look at it. No promises though |
| Comment by julie.bickle [ 01/Dec/21 ] |
|
Molly Driscoll I aim to have my features around tokens groomed before my Xmas break. |
| Comment by Molly Driscoll [ 01/Dec/21 ] |
|
Thank you julie.bickle! |
| Comment by Ann-Marie Breaux (Inactive) [ 01/Dec/21 ] |
|
julie.bickle and patty.wanninger Should the Assignee on this Feature be changed to julie.bickle? |
| Comment by julie.bickle [ 22/Feb/22 ] |
|
Hello Molly Driscoll,
2) Are these fields (for staff slips) the same as you'd like to have added to patron notices (
|
| Comment by julie.bickle [ 22/Feb/22 ] |
|
Molly Driscoll "Anonymized ID token - Needs to be configured for tenant by FOLIO admins, but something like, first three characters or last name and first character or first name." Is this a request to have BOTH the option of showing the full names AND an anonymised version (so 2 tokens, requester.firstName and e.g. requester.firstNameAnon OR is this about a tenant setting, that means that the token requester.firstName will, e.g. only show the first 3 letters ? |
| Comment by Molly Driscoll [ 22/Feb/22 ] |
|
julie.bickle happy to provide screenshots for you! (from Bugfest Kiwi)
Department: Proxy/Sponsor |
| Comment by Molly Driscoll [ 22/Feb/22 ] |
|
To follow up on your other questions, I haven't received any direct feedback about those aspects of this feature - only preferred first name, which libraries I work with would like to see in both notices and staff slips. It may be worth following up with the RA SIG to clarify requirements around the inclusion of departments and proxy/sponsors in notices and about the anonymized token. For what it's worth, as a librarian, I would want botha first and last name token and an anonymized version of each of those tokens to customize according to my library's needs and privacy requirements. |
| Comment by julie.bickle [ 23/Feb/22 ] |
|
Brilliant, thank you Molly Driscoll! |
| Comment by Erin Nettifee [ 26/Jul/22 ] |
|
julie.bickle Duke is very much wanting patron group to be on hold and pick slips - we rely on it for workflows and will be pretty hard to figure out a workaround without it. Any sense as to when this might be worked on? |
| Comment by julie.bickle [ 02/Aug/22 ] |
|
Erin Nettifee I've fully scoped this feature to the best of my knowledge:
|
| Comment by Marie Widigson [ 15/Dec/22 ] |
|
Changing Chalmers' ranking from R5 to R2 (could very well be R1) since we need Anonymized ID token. |
| Comment by Tim Auger [ 02/Jan/23 ] |
|
julie.bickle Happy New Year! Am I correct in my understanding that the stories do not reflect everything desired by the RA SIG? I may be missing these in the stories but should the following be included in this feature?
Thanks! |
| Comment by julie.bickle [ 09/Jan/23 ] |
|
Hi Tim Auger, happy new year! Correct, I haven't written features or stories for those two yet. |
| Comment by Tara Barnett [ 12/Jul/23 ] |
|
Hello julie.bickle! My friends at CU Boulder required the "Anonymized ID token" listed above for their open hold shelves. I can see above you have not yet written features or stories for that one as of January 9th 2023, so I'll just follow this issue, but I wanted to add their interest to this ticket. Thanks! |
| Comment by Khalilah Gambrell [ 08/Sep/23 ] |
|
Hey Anne Ekblad and Stephanie Buck is this issue still a LC priority 3? |
| Comment by Stephanie Buck [ 08/Sep/23 ] |
|
Yes. I'm working on consolidating staff slip needs for LC and at the moment this is the best representation of them. |