Fees/Fines
(UXPROD-792)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | Fees/Fines |
| Affects versions: | None |
| Fix versions: | R1 2021 | Parent: | Fees/Fines |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Holly Mistlebauer |
| Resolution: | Done | Votes: | 0 |
| Labels: | PMP, delegate_candidate, feesfines, resourceaccess, round_iv, ui-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Potential Workaround: | Holly: This is important for debugging fee/fine issues. The data warehouse should be able to provide this information. | ||||||||||||||||||||||||||||||||
| Epic Link: | Fees/Fines | ||||||||||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||
| Front End Estimator: | Matt Connolly | ||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||||||||||||||
| Back End Estimator: | frances.webb@cornell.edu | ||||||||||||||||||||||||||||||||
| Estimation Notes and Assumptions: | Matt's estimated was Small < 3 days, but Holly changed this to Medium < 5 days when |
||||||||||||||||||||||||||||||||
| Development Team: | Vega | ||||||||||||||||||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||||||||||||||||||
| Rank: BNCF (MVP Feb 2020): | R1 | ||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R5 | ||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R1 | ||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||||||||||||||
| Description |
|
Merged on July 20, 2020
Attached images contain mock-ups and in-progress requirements for this feature. Important note: Must include normalized call number for sorting purposes! |
| Comments |
| Comment by Sharon Beltaine [ 26/Aug/19 ] |
|
Holly Mistlebauer - The Reporting SIG can help provide exports like this with the data warehouse, but it needs to be entered as an REP issue in JIRA in order for us to keep track of it. A data analyst will need to be assigned to write the query to generate the export. |
| Comment by Cate Boerema (Inactive) [ 18/Sep/20 ] |
|
Hi Holly Mistlebauer. This looks like 3 features, not one. Am I missing something? I think some of these might be ui-only and, as you know, we are sometimes able to slip those in where we have extra FE capacity. If you could break this down and flesh out the feature descriptions a bit, we could get them individually ranked and estimated (and, in the process, find out if any are ui-only). Thoughts? |
| Comment by Debra Howell [ 29/Sep/20 ] |
|
Holly Mistlebauer - Requesting an update to this feature as it is needed. Please see Cate's comment above also. And, you reference the LDP in the Workaround field - some piece of this probably needs to be assigned to that PO. |
| Comment by Holly Mistlebauer [ 05/Oct/20 ] |
|
Cate Boerema: I stopped working on this feature when it wasn't selected to be part of the MVP. Originally there were other places were we were going to have this 3-part Export option where you could download a spreadsheet, create a printer-friendly file or email something to a patron. I'm not sure what happened with the other options. I think we should start by just having an Export button that will let the user download a spreadsheet of all fee/fine activity for a patron. The user can then slice-and-dice the results how they see fit. That would be easy to do and could be developed quickly. The RA SIG asked for this primarily for resolving complicated fee/fine issues and a spreadsheet of all fee/fine activity would do it. I can knock out the user story for this relatively fast... |
| Comment by Holly Mistlebauer [ 05/Oct/20 ] |
|
Sharon Beltaine: This was made in-app because the users want the very latest data. LDP could be a backup solution. |
| Comment by Holly Mistlebauer [ 20/Oct/20 ] |
|
UPDATE: I am working on a thin-thread version of this that would create just an spreadsheet of fee/fine details for a single user. Hoping for an R1 2021 or R2 2021 release. Will be presenting this to the RA SIG next week (hopefully). |
| Comment by Tom Wilson [ 20/Oct/20 ] |
|
Couple of things: Why would we want to do an export of one record at a time? Once the code is in place to export one users fee/fine info, it isn't another full development activity to export all that have a non-null amount in the fee/fine field. |
| Comment by Holly Mistlebauer [ 06/Nov/20 ] |
|
Tom Wilson: Many highly ranked features did not make it into the MVP. The export is for all fee/fine data for one user, not one record at a time. The RA SIG has approved this in-app approach for researching a fee/fine issue when you need up to date data for a patron. If a library wants to do more exporting for multiple patrons, select fee/fine types, etc. they should use the LDP (data warehouse). |
| Comment by Holly Mistlebauer [ 06/Nov/20 ] |
|
To 'watchers' of issue UXPROD-100: The mock-ups have been created for this feature. If you look at the user stories linked as 'Defined by' you can take a look at the mock-ups. I will work on the actual user story text today or next week. These stories are labelled 'ui-only', which means they are likely to be picked up by a team with front-end capacity in R1 2021. |
| Comment by Holly Mistlebauer [ 19/Nov/20 ] |
|
Update: The user stories have been created. Just wanting for this to be picked up... |
| Comment by Holly Mistlebauer [ 19/Nov/20 ] |
|
Cate Boerema:
|
| Comment by Cate Boerema (Inactive) [ 23/Nov/20 ] |
|
Thanks Holly Mistlebauer! FYI Stephanie Buck and Dennis Bridges in case your teams are looking for ui-only work. Holly Mistlebauer - BTW, we have a green toast message we are displaying now when potentially large exports are generating (check out the Requests CSV and the Overdue Loans report in Users for example). I don't know if this export would every be large enough to warrant that toast displaying, I just thought I'd let you know in case you wanted to add it to your stories. |