[UICIRC-70] Settings for patron notice templates Created: 08/Jun/18 Updated: 28/Mar/19 Resolved: 11/Dec/18 |
|
| Status: | Closed |
| Project: | ui-circulation |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 1.4.0 |
| Type: | Story | Priority: | P2 |
| Reporter: | Darcy Branchini | Assignee: | Matt Connolly |
| Resolution: | Done | Votes: | 0 |
| Labels: | demo53, sprint43, sprint44, sprint45, sprint48, sprint49, sprint50, sprint51, sprint52 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Purpose: Configuration/Settings for patron notices Context/Stories: As an administrator, I want to setup patron notices, including name, description, active/inactive status and email templates. Generally, notices include availability, courtesy, overdue and/or fee/fine notices as well as notices specific to other workflows, such as claims returned. All notices will be sent via email initially. SMS and Print are OUT OF SCOPE for this release, but these will be developed in a future release. This issue covers just create, edit and clone for notices, and not full CRUD or the triggering events, conditions and/or scheduling, which will be addressed through patron notice policies and circulation rules. All notice mockups are available here - https://drive.google.com/drive/folders/1zNDRmeBiK6m1VU6OEU0STPlL7hN-YFxA. Attached mockups are relevant to this story. Note: wherever an accepted UI pattern already exists, such as the Save button at top right, that should be implemented. Scenario 1:
Mockup(s): 1 Patron notices - settings |
| Comments |
| Comment by Cate Boerema (Inactive) [ 19/Jul/18 ] |
|
Great to see this story come in! It's a big one. I vote for putting all the pre-formatted notices requirements into
It would be helpful if you could number the scenarios so people could reference them in comments. Thanks! |
| Comment by Khalilah Gambrell [ 23/Jul/18 ] |
|
This implementation could be leveraged to support sending a user a Create/Reset/change password. |
| Comment by Matt Connolly [ 30/Jul/18 ] |
|
Cate Boerema Darcy Branchini I have some time available, so I can pick this one up if it's ready to go. |
| Comment by Darcy Branchini [ 30/Jul/18 ] |
|
Matt Connolly - yes, they're ready! I'm happy to see someone pick this up. Please let me know if you have any questions. Also, you might want to connect with Michal Kuklis about his work with the rich text editor for staff slips. He used Quill JS and Mustache. Thank you! |
| Comment by Cate Boerema (Inactive) [ 06/Nov/18 ] |
|
Matt Connolly and Jakub Skoczen, just checking in on this. It's been in progress for quite some time and this entire feature (not just this story but all of
|
| Comment by Darcy Branchini [ 06/Nov/18 ] |
|
Cate Boerema, Matt Connolly and I were just discussing this. I made a few UI changes to be more inline with Filip's UX patterns. Matt thinks he can have this done within a week or two. |
| Comment by Cate Boerema (Inactive) [ 07/Nov/18 ] |
|
Thanks for the update, Darcy Branchini and Matt Connolly. The entire feature (
I think we should really strive to get the settings described in this story plus a basic patron notice CRU(D) workflow complete (similar to the Staff slips CRUD). |
| Comment by Marc Johnson [ 07/Nov/18 ] |
|
(I'm not sure if this is the right place to ask this, but wasn't sure of a better place) Matt Connolly Is my understanding correct that this work is to use interfaces implemented by mod-template-engine and not mod-circulation-storage? If so, should we
|
| Comment by Matt Connolly [ 07/Nov/18 ] |
|
Hi, Cate Boerema ... I appreciate that the time remaining is limited. I'd like to see how far I can get with the code this week. That will put us in a good position to figure out who can do what at the beginning of next week. Marc Johnson, you're right; this is based now on mod-template engine, and so
|
| Comment by Jakub Skoczen [ 29/Nov/18 ] |
|
John Malconian this will require mod-template-engine (template-engine 1.0 interface) included in the snapshot and snapshot-core to operate. Can we get it in? |
| Comment by Darcy Branchini [ 30/Nov/18 ] |
|
I removed general configuration from this story. It's just a list of defined templates. We'll address formats (such as email, sms and print) allowed and footer in a separate story. Footer will be more generic and instead we'll have templates and template snippets (such as footer, header, and/or signature). |
| Comment by Darcy Branchini [ 30/Nov/18 ] |
|
Matt Connolly, please use the term "Patron notice templates" as label in settings. We'll also have "Patron notice policies," so I just want it to be clear. |