Patron Notices (UXPROD-18)

[UXPROD-676] CRUD Patron Notice Policies - Loan-related notices only (part 1) Created: 25/May/18  Updated: 16/Sep/20  Resolved: 13/Mar/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Patron Notices

Type: New Feature Priority: P3
Reporter: Darcy Branchini Assignee: Darcy Branchini
Resolution: Done Votes: 0
Labels: notices, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Screen Shot 2018-05-25 at 10.25.17 AM.png     PNG File fee fine lost.png     PNG File fee fine overdue options.png     PNG File fee fine overdue.png     PNG File loan policy - notice 1.png     PNG File loan policy - notice 2.png     PNG File receipts.png     PNG File request - recall.png     PNG File request available options.png     PNG File request available.png    
Issue links:
Relates
relates to UXPROD-1386 Send patron notices via email for use... Closed
relates to UXPROD-1387 Add Request-Related Notice Settings t... Closed
relates to UXPROD-1585 Send patron notices for user initiate... Closed
relates to UXPROD-1589 Send patron notices for item status c... Closed
relates to MODSENDER-4 SPIKE: Determine Technical approach f... Closed
relates to UICIRC-110 SPIKE: CRUD patron notice policies Closed
relates to UXPROD-1587 Send patron notices for time based re... Closed
relates to UICIRC-181 Permission Set for Notice Policy CRUD Closed
relates to UXPROD-1217 Extending Loan Rules Editor to target... Closed
relates to UICIRC-98 New/edit notice policy Closed
relates to UICIRC-108 View notice policy Closed
relates to UICIRC-109 Delete notice policy Closed
relates to UICIRC-167 Settings - list of notice policies Closed
relates to UICIRC-198 Add toggle for user initiated v. time... Closed
relates to UXPROD-1392 Extend patron notices to print Draft
relates to UXPROD-1393 Extend patron notices to SMS Draft
Epic Link: Patron Notices
Analysis Estimate: Large < 10 days
Analysis Estimator: Darcy Branchini
Front End Estimate: XL < 15 days
Front End Estimator: Jakub Skoczen
Back End Estimate: XXL < 30 days
Back End Estimator: Jakub Skoczen
Estimation Notes and Assumptions: Modified issue - logic in notice policies instead of workflow or other policies (loan, fee/fine, request). Need new estimates. BE estimates assumes the scheduling, event triggers/listener logic is built specifically for PN rather than relies on existing functionality provided though UXPROD-594 and UXPROD-729

Jakub: XXL for the backend since this may include coding internal scheduling logic. XL for the UI, the assumption is all logic lives on the server and UI is merely a configuration interface.
Development Team: Vega
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   

IMPORTANT NOTE: As a first pass, this feature has been modified for notices sent via email related to loan activities only. There are new features created for request-related notices and fee/fine-related notices as well as SMS and print notices.

Needs to allow for scheduling, event triggers/listeners, and other conditions. This function will be configured using in policies, including loan, request and fee/fine policies, and general configuration for notices. Early hand-drawn mockups are attached.

See UXPROD-110 for earlier reference to patron notices, as well as UXPROD-675 Closed and UXPROD-723 Closed for setting up the name, description and templates.


Initially thought Workflow would be the right solution. Here's the original thinking on that:
A visual representation of one use case is attached. It assumes a UI will be developed for the workflow engine. The attached visual shows two different notices sent at different points in time, overdue notice #1 is sent at Day 1 (maybe immediately is more appropriate here), and then overdue notice #2 is sent at Day 3. Additional criteria might include loan type, patron type (group), and/or loan policy.



 Comments   
Comment by Cate Boerema (Inactive) [ 14/Sep/18 ]

Darcy Branchini, it seems like the summary and description of this feature probably need to be updated now that the plan is to leverage loan rules for the logic (by tying notices to policies).

Comment by Cate Boerema (Inactive) [ 14/Sep/18 ]

Just looking at the number of blockers on this and the fact that no stories have yet been written, I would say this is at risk for Q4. You will probably need to phase this out, first allowing patron notices to be tied to loan policies (which exist already) and later adding to fee/fine policies and request policies (neither of which exist or are currently targeted for Q4).

Comment by Cate Boerema (Inactive) [ 14/Sep/18 ]

When the description for this has been updated to reflect your current thinking, you should probably clear out the estimates and ask the devs to re-estimate.

Comment by Darcy Branchini [ 14/Sep/18 ]

Jakub Skoczen - please provide updated estimates or assign someone to provide updated estimates - since we are now doing this with policies - loan, request and fee/fine policies - as well as some general configuration (most likely in notices) for patron notices of that are receipts (check-in, check-out and/or fee/fine payment). Our earlier estimate was for workflow to handle the logic.

Comment by Darcy Branchini [ 28/Sep/18 ]

Another modification to this feature. After the SIG reviewed the mocks for adding patron notice to loan, fee/fine and request policies, it was decided to instead separate out notice logic into notice policies. Circulation rules (currently called loan rules) is where loan, notice, request and fee/fine policies will be tied together using combinations of patron type, material type, loan type (and eventually location).
Jakub Skoczen Can you please update the front end and back end estimates if they need to be?

Comment by Cate Boerema (Inactive) [ 16/Oct/18 ]

Darcy Branchini, per our Slack, this is assigned to the Vega team for Q4. We need to target sprint 50 - 51 for having the backlog in place.

Also, I added "Patron notice policies" to the summary of this feature, as the current thinking is that is where much of the logic will go (aside from the logic that says which transactions this applies to which falls into "Extending Loan Rules Editor to target additional policy types" ( UXPROD-1217 Closed ). Thanks!

Comment by Cate Boerema (Inactive) [ 09/Nov/18 ]

Darcy Branchini, are you still targeting sprint 51 for getting some stories to Vega?

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Changed the title of this feature, as per Kostyantyn Khodarev, the expectation is that the CRUD aspects of this will get done before the end of the Q4 development period while. Making these policies effective will need to be done in Q1 2019 (see UXPROD-1386 Closed ).

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Per discussion with Kostyantyn Khodarev, if we change the scope of this to just CRUD patron notice, Vega will finish this prior to the start of the Q1 development period. However, since it didn't get completed prior to Feature freeze for Q4, we do need to change the fix version to Q1 2019. I will also tag it with Q4-2018pFF (for Q4 post-feature freeze).

I will make sure the cap plan is not drawing time for this feature in Q1.

Let me know if this doesn't make sense!

Oh, and Darcy, since this is moving out of the Q4 release, could you please make a note in the Weekly Status Report? Thank you!

Comment by Khalilah Gambrell [ 06/Dec/18 ]

Cate Boerema, what is the start date of the Q1 development period?

Comment by Cate Boerema (Inactive) [ 08/Dec/18 ]

Hi Khalilah Gambrell, while the Q1 develoment period doesn't start until January 14th, I need to tag any work that is targeted for release in Q1 as fixversion = Q1 2019. Per Kostyantyn Khodarev, this work is in progress and will be completed before the Q1 development period begins so we are not factoring in additional time for it in Q1. I have tagged this with "Q4-2018pFF" to indicate it's being worked on in Q4 but after Feature Freeze.

Comment by Cate Boerema (Inactive) [ 04/Jan/19 ]

Per Khalilah and Kostya, this is no longer planned to be completed by the end of Q4. I am removing the Q4-2018pFF tag and pulling down the full estimates for this work from the Vega capacity in the cap plan.

Comment by Cate Boerema (Inactive) [ 10/Mar/19 ]

@darcy it looks like all the stories in this feature are complete. Can we close the feature?

Comment by Cate Boerema (Inactive) [ 13/Mar/19 ]

Marking this done as all the stories it contains are completed.

Generated at Fri Feb 09 00:09:34 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.