Patron Notices
(UXPROD-18)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Patron Notices |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Darcy Branchini | Assignee: | Darcy Branchini |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | notices, resourceaccess | ||
| 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 Estimator: | Michal Kuklis | ||||||||
| Back End Estimate: | XL < 15 days | ||||||||
| Back End Estimator: | Jakub Skoczen | ||||||||
| Estimation Notes and Assumptions: | BE: Assumes templating and emailing functionality is built specifically for this feature rather than provided through |
||||||||
| Development Team: | Prokopovych | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R1 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R1 | ||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||
| Description |
|
Need the ability to define email, sms (text) and/or print templates depending on the institution/organization. For example, some organizations are required to send print notices for a fee/fine notice; whereas, some organizations have a no paper policy. For email, a subject, body (or multiple body parts) and signature are required. For sms, just a body of text is required. For print, they'll need to be able to include a patron name and address (for mailing) and body as well as signature. It was suggested that contact information (and logo) being defined with location settings instead of in the notice itself. If it changes, then it is edited once, and it'll fix all notices. Template requirements include:
Also, the idea of consolidating notices came up. The use case that came up is over items from multiple library locations. For some institutions, it's simple, one notice with all items overdue with one statement about fee/fine policies and/or contact information. For some, it's more complicated, they might each have their own policies and/or generated fees, so it look something like this: Library 1 Library 2 ... Also see
Not sure what templating language will be selected but some early ideas include Mustache. Mustache seems to be popular because of it's simplicity and it's ability to integrate with several languages as described by this comparison chart - (https://en.wikipedia.org/wiki/Comparison_of_web_template_engines). I'd suggest it's biggest drawback is that it won't handle the conditionals outlined above. It will do a simple if exists/not empty test, but that's it. For what it's worth, a few developers at Cornell have researched the topic of rich-text editors combined with templating languages for an email notification system, and their solution eventually became a combination of Quill (https://quilljs.com/) because it stores the template as JSON (and got them out of some earlier trouble with tags and/or elements being stripped out) and Liquid Droplets (https://github.com/Shopify/liquid/wiki/Introduction-to-Drops) for field tokens and/or code snippets. Or at least I think I'm explaining that correctly! Here's a ticket that goes into some details about their research - https://github.com/cul-it/studentsite/issues/862#issuecomment-349994330. |
| Comments |
| Comment by Cate Boerema (Inactive) [ 27/Aug/18 ] |
|
Hi Darcy Branchini. How do you see this distinguished from
|
| Comment by Cate Boerema (Inactive) [ 06/Sep/18 ] |
|
Darcy Branchini I see this is still targeted for the Q3 2018 release. Is there still a chance this will make it? Can you follow up with the devs to make sure they are working on it? |
| Comment by Darcy Branchini [ 06/Sep/18 ] |
|
Cate Boerema I must have misunderstood you, or maybe I'm thinking back to my first staff slip story, but I remember a conversation where you suggested splitting the editor/template from the CRUD portion. |
| Comment by Cate Boerema (Inactive) [ 14/Sep/18 ] |
|
Closing as a duplicate of
|