Fees/Fines
(UXPROD-792)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | Fees/Fines |
| Affects versions: | None |
| Fix versions: | Morning Glory (R2 2022) | Parent: | Fees/Fines |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Holly Mistlebauer | Assignee: | Holly Mistlebauer |
| Resolution: | Done | Votes: | 0 |
| Labels: | UNAM, cap-mvp, feesfines, po-mvp, q4-2019-at-risk, q4-2019-spillover, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 15 minutes | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | Holly: I believe this is a cross-app issue of importance. Fees/fines will need to change if Inventory does. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Fees/Fines | ||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||||||||||||||||||||||||||||||||||
| Front End Estimator: | Holly Mistlebauer | ||||||||||||||||||||||||||||||||||||||||||||||||
| Front-End Confidence factor: | Medium | ||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||||||||||||||||||||||||||
| Back End Estimator: | Holly Mistlebauer | ||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | UNAM | ||||||||||||||||||||||||||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| PO Rank: | 93 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R3 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Grand Valley (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: Leipzig (ERM Aut 2019): | R5 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R2 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
SIG needs to see a call number field that includes more than just the call number. They want to see the year, volume number, copy number, etc. (see examples on attached mock-up). We will need a component that creates the call number field. This component will then be used by any app that needs to present a more descriptive call number. Notes from previous discussions:
|
| Comments |
| Comment by Holly Mistlebauer [ 22/Mar/18 ] |
|
Cate added an item on the RA SIG Parking Lot called "Normalize Call Number." The description says... Need a normalized call number stored and used for sorting on Loans page. We are currently displaying a concatenated call number on the Loans page to save on real-estate. But sorting by this concatenated string isn't going to work. FOLIO needs to store a "normalized"call # and use that for sorting on Loans and elsewhere. From experience, this data really needs to be stored as opposed to generated on-the-fly. This is a must-have for v1. |
| Comment by Charlotte Whitt [ 06/Apr/18 ] |
|
Hi Holly Mistlebauer - this story links to the wikipage with the list started by Kathryn Harnish, but there is a more updated master spreadsheet for all Metadata elements implemented in Inventory (Instance, Holdings, Item records) covering both the implemented elements (alpha), and already identified 'missing elements' which we are working on to be implemented (beta) - see: https://docs.google.com/spreadsheets/d/1kdYx63J0KoqR3-LUHuPAzERgj8WE0OQ08rzuCaJaHWs/edit#gid=952741439 Following elements related to Call Numbers have been implemented/identified for the Holdings record
|
| Comment by Charlotte Whitt [ 02/Oct/18 ] |
|
Hi Holly Mistlebauer - I have added some update info to this UXPROD feature:
|
| Comment by Holly Mistlebauer [ 17/Jan/19 ] |
|
The fields that make up the displayed call number are... Call number prefix Enumeration |
| Comment by Holly Mistlebauer [ 18/Jan/19 ] |
|
At the 1/17 RA SIG meeting it was decided that each tenet should be able to build the call number in the format they want for the call slips. Despite this, we are going to attempt to build a shared format for display within fees/fines and loans. Adding a setting for doing this would be a lot of extra work. Another related issue is the sorting of the call number. The call number needs to be sorted on both Fees/Fines History and Loans History. Holly will meet with the CUL IT expert on this topic to gather some info on this. |
| Comment by Anya [ 29/Mar/19 ] |
|
Comment from the March Meeting : call number sort needs to work |
| Comment by Holly Mistlebauer [ 14/Oct/19 ] |
|
Per Laura Wright... <prefix> <call number> <suffix> <enumeration> <chronology> <volume> <copy number> Using real field names (note that there is a space between each field)... All data is available via the ITEM RECORD (see attached file ItemRecord.png)... ITEM DATA ENUMERATION |
| Comment by Cate Boerema (Inactive) [ 24/Oct/19 ] |
|
Hi Holly. I cleaned up the links between features a bit:
Finally, when
|
| Comment by Holly Mistlebauer [ 04/Nov/19 ] |
|
Hi Cate Boerema. Thanks. I need to take a closer look at this to make sure I understand what is going on. |
| Comment by Cate Boerema (Inactive) [ 21/Nov/19 ] |
|
Hi Holly Mistlebauer. I'm trying to get a handle on requirements readiness and this one is marked Analysis complete. I think this should probably be marked Draft again until we have worked out what exactly needs to be done here. You are close, but we need to make sure your stories are making use of the Effective call number components we are storing as part of
I know this isn't one of your top Fee/fine features, given you are focusing on features that require more testing and training so I don't think this is urgent. I just want to get the feature statuses lined up with reality in terms of readiness. Does that make sense to you? |
| Comment by Holly Mistlebauer [ 27/Nov/19 ] |
|
Hi Cate Boerema. I wasn't aware of the new "effective call number", but it is a great idea. I have changed the Status of this Feature back to "Draft" and will make sure that devs don't start working on the User Stories. In your comment on 24/Oct/19, you say "It may not be necessary to create a shared module for display of call number." Is this because we may have a "display effective call number" available on the item record? Thanks! |
| Comment by Holly Mistlebauer [ 21/Feb/20 ] |
|
Notes for Circ PO discussion... |
| Comment by Holly Mistlebauer [ 04/Mar/20 ] |
|
Per CIRC PO meeting on 2/28/2020, Holly needs to change the user stories to format the display call number format to... <Effective Call Number Prefix> <Effective Call Number> <Effective Call Number Suffix> <Volume> <Enumeration> <Chronology> <Effective Copy Number> (Full notes available at https://docs.google.com/document/d/1y4DjshPNS7SevPGVw2ptdg_Cv52qNfONW1jWhyDL_-w/edit?usp=sharing) |
| Comment by Cate Boerema (Inactive) [ 27/Aug/20 ] |
|
Hi Holly Mistlebauer, I think this feature needs to be broken down into two parts:
The latter is blocked by
Bohdan Suprun, if this feature was only about displaying "Effective call number string" on:
Thanks! |
| Comment by Bohdan Suprun (Inactive) [ 27/Aug/20 ] |
|
Hi Cate Boerema, Holly Mistlebauer, For the part #1.
For the part #2. |
| Comment by Holly Mistlebauer [ 14/Sep/20 ] |
|
Cate Boerema: Sorting of call number is already a separate feature. It's
|
| Comment by Cate Boerema (Inactive) [ 15/Sep/20 ] |
Holly Mistlebauer, there are a couple reasons why I thought sorting was in scope for this feature:
As I said, I think the sorting functionality ought to be broken out into that separate feature and removed from the stories here, but it isn't urgent. I was originally hoping this feature would be ui-only which would mean we could get it done now (minus the sort bits) but it sounds like there is back end needed just to display the call number. |
| Comment by Khalilah Gambrell [ 11/Jul/22 ] |
|
Hey Holly Mistlebauer. Can we move this feature to Closed? Or should this feature be moved to Nolana? |