Patron Notices
(UXPROD-18)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q4 2018 | Parent: | Patron Notices |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Darcy Branchini | Assignee: | Darcy Branchini |
| Resolution: | Done | Votes: | 0 |
| Labels: | notices, resourceaccess, split | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Patron Notices | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Analysis Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Analysis Estimator: | Darcy Branchini | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | XL < 15 days | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Michal Kuklis | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Very Small (VS) < 1day | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Jakub Skoczen | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | CB: Per slack chat with Matt Connolly, "I think that the back-end work is being handled by the mod-template-engine team (Folijet), so the Core team work should be minimal either way." Given that, I have reduced the BE estimate from XXL to Large (30 to 10 days). I'd like the developers to adjust further, as-needed, but I needed to make an initial adjustment now for planning.
CB: Per Jakub, this can be further reduced to 1 day for BE. Jakub also thinks we should increase the front end from 5 to 15. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 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 |
|
Basic create, read, update and delete functionality (as well as clone or duplicate) for patron notice templates. They'll need to be configurable from settings > circulation > patron notices and a patron notice will have the following fields name, description, active/inactive toggle and templates. Notes:
Details on Templates (
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 ... 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) [ 06/Sep/18 ] |
|
Darcy Branchini I see this is still targeted for Q3 2018. Is there still a chance this can get into the release? |
| Comment by Cate Boerema (Inactive) [ 14/Sep/18 ] |
|
This is blocked on endpoint for patron notice templates (
|
| Comment by Cate Boerema (Inactive) [ 14/Sep/18 ] |
|
Per agreement with Darcy, I am merging this with
|
| Comment by Cate Boerema (Inactive) [ 26/Sep/18 ] |
|
Darcy Branchini, this seems to be missing its frontend estimate. |
| Comment by Cate Boerema (Inactive) [ 28/Sep/18 ] |
|
Michal Kuklis can you please estimate the front end work needed for this? Thanks much! |
| Comment by Michal Kuklis [ 28/Sep/18 ] |
|
Cate Boerema done. |
| Comment by Darcy Branchini [ 28/Sep/18 ] |
|
Jakub Skoczen - can you take another look at the back end estimate for this feature? Will it really be an XXL for just CRUD? The logic (scheduling, triggers - both event and conditions) is a separate issue. |
| Comment by Cate Boerema (Inactive) [ 18/Oct/18 ] |
|
Matt Connolly, this feature has a 30 day backend estimate. I am pretty sure you said that the backend work was taken care of by Folijet so there is little to no BE work remaining for the Core team. Is that right? If so, can you please modify the backend estimate accordingly? |
| Comment by Cate Boerema (Inactive) [ 08/Nov/18 ] |
|
Moving this from Blocked to InProgress because, as I understand it,
|
| Comment by Cate Boerema (Inactive) [ 11/Jan/19 ] |
|
Hi Darcy Branchini. It is end of quarter and this feature is incomplete. It will need to be split:
|