Fees/Fines (UXPROD-792)

[UXPROD-2989] Cornell Library - Table-Driven Bursar Item Types for Fees/Fines Created: 18/Mar/21  Updated: 03/May/22  Resolved: 03/May/22

Status: Closed
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: None
Parent: Fees/Fines

Type: New Feature Priority: P3
Reporter: Philip Robinson Assignee: Holly Mistlebauer
Resolution: Done Votes: 0
Labels: feesfines, resourceaccess, transfer
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft Word New Bursar Library Item Types Table pr52.xlsx     PNG File Screen Shot 2021-03-11 at 17.37.21.png    
Issue links:
Defines
defines MODEXPS-10 Enhance fees/fines bursar report sett... Closed
defines MODEXPW-6 Enhance fees/fines bursar report sett... Closed
defines MODEXPW-7 Do not use setting for service point;... Closed
is defined by UIPBEX-9 Bursar Item Types for Fees/Fines Closed
is defined by UIPBEX-10 Rename Bursar export to Transfer crit... Closed
is defined by UITEN-169 Move Tenant/Bursar exports to Users/T... Closed
is defined by UIU-2098 Move Tenant/Bursar exports to Users/T... Closed
Relates
relates to UXPROD-2862 Cornell Library's go-live requirement... Closed
Epic Link: Fees/Fines
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: U of AL (MVP Oct 2020): R5

 Description   

Current situation or problem

Cornell Library needs a table-driven way to manage Cornell Bursar Item Types and Item Descriptions, including a UI to manage these values. This feature is a follow-on to https://folio-org.atlassian.net/browse/UXPROD-2862 , which relies on hard-coded item types and descriptions.

In scope

  1. Create table to store the fields: bursar item type, bursar description, bursar item code (having only the values "Charge" or "Payment"), fee/fine owner, fee/fine type. These are all varchar (variable-length text) fields. The specific values are listed in the attached spreadsheet file, "New Bursar Library Item Types Table pr52.xlsx". The table should also track who updated the values and when, using standard FOLIO field names / types for that.
  2. Create a user interface to manage all values in the table. The proper location of the form is uncertain at the moment, but in the form, bursar item type and bursar description should be free-text fields. Bursar item code, fee/fine owner, and fee/fine type should be pull-down lists. The fee/fine owner pull-down list would be populated by the existing fee/fine owner list managed in Settings > Users > Fee/Fine: Owners. Users should have a way to modify the values fee/fine type as well, perhaps adding that to Settings > Users > Fee/Fine.
  3. Permissions: The table-driven UI should be usable only by users who have access to the other bursar-related features.

 

 

 



 Comments   
Comment by Philip Robinson [ 18/Mar/21 ]

Mikita Siadykh and Debra Howell - created this UXPROD to capture Bursar table-driven values per our discussion.

Comment by Erin Nettifee [ 18/Mar/21 ]

I would not put the UI for this in Settings --> Tenant. Bursar exports are a circulation function, they should live in Circulation Settings. Or, Export Manager needs its own settings section.

I also think the UI discussion should come to the RA SIG for input if this is going to be part of the core FOLIO system - I assume that's the case since an app is being built for it that is visible on Snapshot.

Comment by Philip Robinson [ 18/Mar/21 ]

Erin Nettifee this is Cornell-specific for now, and the Cornell project team decided to put some of the interfaces in Settings > Tenant. The dev team has been using Snapshot for the other Cornell-specific work for now, but there will be further discussions about transitioning these features to the broader FOLIO Bursar work later.

Comment by Erin Nettifee [ 18/Mar/21 ]

Hey Philip Robinson - I understand Cornell is paying for this and directing development, but even for something only Cornell will ever use, I strongly believe Settings --> Tenant is the wrong place to put a circulation-specific setting. It was confusing to people that that is where Service Points lives, since Service Points are essentially a circulation function (though I think people have gotten over that.) Having the location tree in Settings --> Tenant makes more sense, but also makes it unclear to people that the location tree is actually in mod-inventory-storage.

I don't know if Joanne Leary or others have been in the loop on the decision making process - and recognize they may have and disagree with my comment, and if your circ staff disagree, than mea culpa. But having the discussion with the RA SIG about placement while you're developing would do one of two things - it would either help you get community buy-in to your decision-making (and be clear that my thought process is wrong, since I'm only one person in the discussion,) or at least help see that if expansion to other schools does happen (say Core: Functional adds work to it, or a school contributes to developers to add features,) that the SIG may really advocate at that point that the settings be moved.

Comment by Philip Robinson [ 18/Mar/21 ]

Thanks for your input on this, Erin Nettifee - we will look into various options to move it to a better place, we're not terribly wedded to the current location. We are meeting with Holly, Khalilah, and Stephanie next week to talk about eventually moving this FOLIO-wide, so perhaps they can make the decision where to put it.

Comment by Mikita Siadykh [ 19/Mar/21 ]

hi Philip Robinson

can we update Feature description a bit? after discussion with Roman Leshchenko we have several hardcoded entities:

  1. service point (associated with fee/fine owner) - required for transfer
  2. fee/fine transfer account - required for transfer
  3. fee/fine types mapping to bursar items

 

what we propose:
1. fee/fine owner field - dropdown, select one owner from all possible (https://folio-testing.dev.folio.org/settings/users/owners)

2. service point field - dropdown,  select one service point from points that are associated with selected in #1 owner

3. fee/fine transfer account field - dropdown, selected in #1 owner accounts (https://folio-testing.dev.folio.org/settings/users/transfers)

4. from table (aka repeatable field) to build a map fee/fine types (based on selected owner) - bursar item. It displays rows equal to fee/fine types count (e.g. owner1 has 3 types, owner2 has 2 types; when we select owner 1 - table shows all 3 types, when owner2 - 2 types). Columns/fields for this mapper

  • Fee/fine type - disabled field, as it's already preselected based on owner type
  • Item type - text field - any length restrictions?
  • Item description - test field -  any length restrictions?
  • Item code - select with 2 options ("Charge", "Payment")

 

wireframe with new controls, what do you think?

Comment by Philip Robinson [ 24/Mar/21 ]

Hi Mikita Siadykh, the wireframe looks great. As mentioned, we can drop the "Folder" field.

Comment by Khalilah Gambrell [ 12/May/21 ]

Debra Howell and Philip Robinson is this feature still needed for Juniper?

Comment by Debra Howell [ 14/May/21 ]

Khalilah Gambrell Yes, it is still needed.

Comment by Holly Mistlebauer [ 02/Jun/21 ]

Khalilah Gambrell:  The 3 remaining stories are IN REVIEW/IN CODE REVIEW, but the there is more worked to be done.  The work that has been done is not totally correct.  We didn't get this work done for Juniper partly because the feature wasn't assigned to me (so it slipped my mind) and partly because it isn't critical.  I need to re-evaluate this work and determine what changes are needed.  For now I will change the Status to BLOCKED.  Thanks...

Comment by Holly Mistlebauer [ 03/May/22 ]

Was completed several releases ago.

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