Fees/Fines (UXPROD-792)

[UXPROD-393] Finalize display format of Call Number within Fees/Fines Created: 22/Mar/18  Updated: 12/Jul/22  Resolved: 12/Jul/22

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: JPEG File CallNumberExamples.jpg     JPEG File Display-call-number-notes.JPG     PNG File ItemRecord.png     PNG File Skärmavbild 2018-10-02 kl. 13.15.18.png     PNG File Skärmavbild 2018-10-02 kl. 13.19.33.png    
Issue links:
Blocks
blocks UXPROD-2128 Future Fees/Fines: Address Call Numbe... Draft
is blocked by UXPROD-2170 Store Effective Copy Number Open
is blocked by UXPROD-1626 Store Effective Call Number Prefix, C... Closed
Defines
is defined by MODFEE-99 BE Display call number: Update Fees/... Closed
is defined by UIU-1307 Display call number: Update Fees/Fin... Closed
is defined by UIU-1308 Display call number: Update Fee/Fine ... Closed
is defined by UIU-1309 Display/save call number: Update New ... Closed
is defined by UIU-1171 Display call number: Create shared m... Closed
Relates
relates to UXPROD-2002 Implement Normalized Call Number for ... Closed
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

  • Call Number (implemented - alpha)
  • Call Number Prefix (identified)
  • Call Number Type (identified)
Comment by Charlotte Whitt [ 02/Oct/18 ]

Hi Holly Mistlebauer - I have added some update info to this UXPROD feature:

  • link to the Inventory Beta Metadata element spreadsheet - in the description
  • and spec of call numbers (holdings record, and item record) - see: attachments
Comment by Holly Mistlebauer [ 17/Jan/19 ]

The fields that make up the displayed call number are...

Call number prefix
Call number
Call number suffix
Copy number

Enumeration
Volume
Chronology
Year, Caption (although there were questions about this field being a combined field… perhaps it should just be labeled Caption and that might include year data, if desired?)

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)...
<Call number prefix> <Call number> <Call number suffix> <Enumeration> <Chronology> <Volume> <Copy number>

All data is available via the ITEM RECORD (see attached file ItemRecord.png)...

ITEM DATA
Call number prefix
Call number
Call number suffix
Copy number

ENUMERATION
Volume
Enumeration
Chronology

Comment by Cate Boerema (Inactive) [ 24/Oct/19 ]

Hi Holly. I cleaned up the links between features a bit:

  • Since this is about call number display, the feature that blocks it is actually Implementing effective call number: UXPROD-1626 Closed (not Implementing normalized call number for sorting UXPROD-2002 Closed )
  • To that point, I think it's really important that, when your stories refer to the data elements to include when building the call number, they need to refer to <Effective Call Number Prefix> <Effective Call Number> <Effective Call Number Suffix> <Enumeration> <Chronology> <Volume> <Effective Copy Number> all from the item record
  • The feature of yours that is blocked by the call number normalization ( UXPROD-2002 Closed ) is UXPROD-2128 Draft . I linked those up accordingly.

Finally, when UXPROD-1626 Closed is complete, let's discuss before you implement UIU-1171 Closed . It may not be necessary to create a shared module for display of call number.

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 UXPROD-1626 Closed

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:

  1. Display "Effective call number string" throughout Fee/fines pages
  2. Support sorting by call number in Fees and Fines

The latter is blocked by UXPROD-2002 Closed . The stories here also reference both display and sorting. We need to remove the sorting bit from the display stories.

Bohdan Suprun, if this feature was only about displaying "Effective call number string" on:

  • New fee/fine form (after barcode has been added)
  • Fee fine details
  • Fee fine history
    Would there still be backend work needed? I'm looking to identify front-end only features.

Thanks!

Comment by Bohdan Suprun (Inactive) [ 27/Aug/20 ]

Hi Cate Boerema, Holly Mistlebauer,

For the part #1.

  • New fee/fine form (after barcode has been added) - it is UI only.
  • Fee fine details/history - potentially it can be UI only stories, but it means that we're moving business logic to UI side, what we currently trying to get rid of. So, I'd prefer to have it on BE side. On BE, when we return fee(s)/fine(s) by query, we have to additionally fetch call number components from inventory. (~10 days)

For the part #2.
Can be solved as duplication the call number components (or just sortable call number) on fee/fine record. What requires cascade changes in circulation, to populate new property where we create automatic fees. It also means that the call number on the fee/fine vs the call number in inventory can be out of sync. If we need keep them sync, then we need to decide how to implement it.

Comment by Holly Mistlebauer [ 14/Sep/20 ]

Cate Boerema: Sorting of call number is already a separate feature. It's UXPROD-2128 Draft . The three stories for this are already written. See the 'is defined by' links.

Comment by Cate Boerema (Inactive) [ 15/Sep/20 ]

Cate Boerema: Sorting of call number is already a separate feature. It's UXPROD-2128 Draft . The three stories for this are already written. See the 'is defined by' links.

Holly Mistlebauer, there are a couple reasons why I thought sorting was in scope for this feature:

  1. The feature description mentions sorting
  2. There are stories linked to this feature as "is defined by" which have scenarios in them around sorting ( UIU-1307 Closed scenario 5)

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?

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