Patron Notices
(UXPROD-18)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Patron Notices |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Darcy Branchini | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | appreport, error_handling, notice_error, patron_notice, resourceaccess, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Potential Workaround: | EBSCO hosting configured their libraries email service (AWS SES) to notify select staff via email for each bounced email | ||||||||
| Epic Link: | Patron Notices | ||||||||
| Analysis Estimate: | Medium < 5 days | ||||||||
| Analysis Estimator: | Darcy Branchini | ||||||||
| Front End Estimate: | XL < 15 days | ||||||||
| Front End Estimator: | Darcy Branchini | ||||||||
| Back End Estimate: | XL < 15 days | ||||||||
| Back End Estimator: | Jakub Skoczen | ||||||||
| Development Team: | Volaris | ||||||||
| Report ID (pre-May 2019): | ID449 | ||||||||
| Report Contact(s): |
Cheryl Malmborg, David Bottorff, Joanne Leary
|
||||||||
| Report Functional Area(s): |
Resource Access
|
||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 11 | ||||||||
| PO Rank: | 30 | ||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R4 | ||||||||
| Rank: Grand Valley (Full Sum 2021): | R1 | ||||||||
| Rank: hbz (TBD): | R4 | ||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||
| Description |
|
Problem/Purpose: Knowing which user records don't have an email address would also be useful as a proactive measure to prevent errors in sending. Implementation Thoughts:
|
| Comments |
| Comment by Theodor Tolstoy (One-Group.se) [ 19/Sep/18 ] |
|
If bouncing emails could be routed to a central inbox, that would be enough at the moment. |
| Comment by Sharon Beltaine [ 30/Oct/18 ] |
|
Please let me know if this needs to become a data warehouse report so we can get it developed in time. Thanks. |
| Comment by Darcy Branchini [ 30/Oct/18 ] |
|
Sharon Beltaine - I believe it will be data warehouse report. |
| Comment by Khalilah Gambrell [ 29/Mar/19 ] |
|
Darcy Branchini - is there a way to address this comment "If bouncing emails could be routed to a central inbox, that would be enough at the moment." currently? |
| Comment by Darcy Branchini [ 29/Mar/19 ] |
|
Khalilah Gambrell, I don't know, I can ask Vega, but I also want to be careful that we're not spending time on a quick fix, which means we have to circle back and rethink it later. I'm planning to more thoroughly analyze this feature beginning in mid-April. |
| Comment by Martina.Schildt [ 13/May/19 ] |
|
In any case, as a system user I need to be able to view all the letters and e-mails I have created, even retrospectively. This issue only seems to generate a list of the generated notes. |
| Comment by David Bottorff [ 01/Jul/19 ] |
|
Chicago could wait up to 1 year for this |
| Comment by Holly Mistlebauer [ 17/Jun/20 ] |
|
Cornell comment from Round IV Outliers spreadsheet: This outlier is a showstopper for Cornell |