Patron Notices
(UXPROD-18)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Patron Notices |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Darcy Branchini | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | notice_tokens, patron_notice, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Epic Link: | Patron Notices | ||||||||||||||||||||||||
| Analysis Estimate: | Medium < 5 days | ||||||||||||||||||||||||
| Analysis Estimator: | Darcy Branchini | ||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||
| Front End Estimator: | Maxim Didenko | ||||||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||
| Back End Estimator: | Alexander Kurash | ||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Includes changes to custom fields module to add new flag for "available to patron notice" and for users only. | ||||||||||||||||||||||||
| Development Team: | Volaris | ||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 5 | ||||||||||||||||||||||||
| PO Rank: | 20 | ||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R1 | ||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R3 | ||||||||||||||||||||||||
| Description |
|
Custom fields are being added to some modules, such as users (
|
| Comments |
| Comment by Brooks Travis [ 20/Feb/20 ] |
|
Re-ranking this in light of user record needs for storing patron preferred name and other non-standard information that needs to be includable in notices. |
| Comment by Cate Boerema (Inactive) [ 07/May/20 ] |
|
Hi Darcy Branchini could you please have estimates added for this feature? Thanks! I'm curious how much more difficult it would be to allow for tokenizing custom fields vs creating a token for a dedicated field. |
| Comment by patty.wanninger [ 16/Sep/20 ] |
|
Darcy Branchini I could contribute a couple of stories for this feature. Let me know. |
| Comment by Darcy Branchini [ 16/Sep/20 ] |
|
Sure, patty.wanninger, please do. My biggest question with this feature is do we add all as tokens by default? Or do we allow the user to select the custom fields that need to be tokens. |
| Comment by patty.wanninger [ 16/Sep/20 ] |
|
I think the custom fields need to be able to be designated if they serve as a token or not, for example, if you have a custom field for honorfics, you would want to be able to make it a token. But other custom fields will be for statistical reporting etc. and wouldn't need to be tokens. |
| Comment by Brooks Travis [ 02/Oct/20 ] |
|
Late to the game, but I agree with Patty about designating custom fields as tokens. |
| Comment by Darcy Branchini [ 02/Oct/20 ] |
|
Thanks Brooks Travis and patty.wanninger. That makes sense to me. |