Fees/Fines (UXPROD-792)

[UXPROD-2862] Cornell Library's go-live requirements to transfer fees/fines to the Cornell bursar system Created: 06/Jan/21  Updated: 01/Nov/21  Resolved: 22/Apr/21

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

Type: New Feature Priority: TBD
Reporter: Holly Mistlebauer Assignee: Debra Howell
Resolution: Done Votes: 0
Labels: Showstopper-Cornell, mandatory
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Microsoft Word Cornell FOLIO Bursar export specs.docx    
Issue links:
Defines
is defined by MODEXPS-4 Enable scheduling of modules to run a... Closed
is defined by MODEXPW-2 Create module to generate machine rea... Closed
is defined by MODFEE-155 Stop scheduled patron notices from be... Closed
is defined by UIEXPMGR-2 Export manager layout Closed
is defined by UIEXPMGR-3 Export manager - export jobs view (re... Closed
is defined by UIEXPMGR-4 Export manager - export jobs search a... Closed
is defined by UIEXPMGR-5 Export manager - export job details Closed
is defined by UIEXPMGR-10 Show export job real data Closed
is defined by UIPBEX-1 Project setup Closed
is defined by UIPBEX-2 Enable FOLIO to define FTP file desti... Closed
is defined by UIPBEX-3 Run bursar export manually Closed
is defined by UIPBEX-5 Bursar exports configuration form (UI) Closed
is defined by UITEN-153 Display list of completed file extrac... Closed
is defined by UITEN-159 Bursar exports settings page Closed
is defined by MODFEE-154 Verify that Circulation Log includes... Closed
is defined by MODBUREXP-1 Identify CUL fees/fines to be transfe... Completed
Relates
relates to MODEXPW-31 Bursar transfer form cannot specify d... Closed
relates to UXPROD-105 Future Fees/Fines: Update current aut... Closed
relates to UIPBEX-27 Rename the label "Max. days outstandi... Closed
relates to UXPROD-2989 Cornell Library - Table-Driven Bursar... Closed
Requires
requires FOLIO-2986 Create mod-bursar-export github repos... Closed
Release: R1 2021
Epic Link: Fees/Fines
Development Team: Scout
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem: Cornell Library needs to be able to transfer fees/fines to the bursar when they go live with FOLIO in Summer 2021. UXPROD-105 Closed (Automated Transfer of fees/fines to bursar or other account) will not be completed on time, so Cornell is paying EPAM developers to develop what they need at go-live. Most of what is being developed will be reusable by UXPROD-105 Closed .

In scope

  1. Create module to identify fees/fines meeting Cornell’s criteria (which is any active student fees/fines that have been outstanding for more than 9 days) and create fee/fine ‘action’ record for each transfer (see the manual Transfer fee/fine process for more information--this is needed to document that the patron’s fee/fine has been transferred and so that Cornell is able to balance fees/fines)
  2. Create module to generate machine readable extract in format Cornell’s Bursar system needs.
  3. Facilitate scheduling of modules to run daily (or at other interval) at a set time.
  4. Facilitate production of list of previous extracts and ability to download selected file.
  5. Verify that Circulation Log includes Transfer ‘actions’ (it does for manual transfers, and should automatically pick up automated transfers).
  6. Stop scheduled patron notices from being sent after the fees/fines have been transferred to the bursar.

Out of scope

  1. Incorporating the manually transferred fees/fines into the extract. Cornell does not need to be able to transfer individual fees/fines manually. Only the daily bulk extract is needed.
  2. Generating of patron notices is not included because Cornell does not currently send notices for transfers and doesn't plan to do so after migrating to FOLIO.
  3. Creating a log of transferred fees/fines--the Circulation Log will meet this need, plus we will have a copy of each extract to refer back to.
  4. Processing of rejected transfers--this will be handled manually by Cornell Library staff.
  5. Notifying the Bursar of refunded fees/fines—this will be handled manually via the refund report initially (separate UXPROD feature is UXPROD-1879 Open ).

Questions for Michelle Hubbell (answered January 12, 2020)

  1. Is criteria correct: Students with open fee/fine created more than 9 days ago? Yes. Students must be Active.
  2. Which patron groups make up 'students'? Undergraduate, Graduate, CU Undergraduate, CU Graduate (the last two may not be migrated to FOLIO; not sure yet; there aren't many).
  3. If sending notices is not included in the API, is it enough to add a note at the bottom of all 'charge' notices indicating that any student fees/fines not paid within 9 days will be transferred to the bursar? This is what CUL already does. They do not send a notice when fees/fines are transferred. We will continue with this approach.
  4. Does Cornell need to be able to send single transfers? No, have never done that and don't plan on doing that in FOLIO.


 Comments   
Comment by Philip Robinson [ 07/Jan/21 ]

I notified the Cornell Office of the Bursar and Cornell Information Technologies (CIT) that this change is coming. Voyager sends Bursar files to CIT today. Their Production Control office and PeopleSoft team peoplesoft-incid @ cornell.edu will work with us on the transition.

Comment by Philip Robinson [ 07/Jan/21 ]

The "Cornell FOLIO Bursar export specs.docx" attachment summarizes the Bursar file and data format used today. We should adopt the same format for FOLIO.

Comment by Holly Mistlebauer [ 12/Jan/21 ]

Holly is responsible for In scope items 1 and 5. Phil is responsible for 2, 3 and 4.

Comment by Mikita Siadykh [ 14/Jan/21 ]

hi Holly Mistlebauer Philip Robinson
from the stories I see that we'll have UI changes here: list of exports, some config forms etc and I have few questions and notes

1. will it be totally new module?
2. for UI stories usually UI* project is used and MOD* for BE, I think we'll update them after discussion
3. will we have mockups? for now I couldn't find anything

cc Debra Howell

Comment by Holly Mistlebauer [ 19/Jan/21 ]

Mikita Siadykh: Hi! I am responsible for user stories MODBUREXP-1 Completed and MODFEE-154 Closed only. There isn't any UI work for these two stories, so they should remain in the MOD* project. They won't have any mock-ups. For MODBUREXP-1 Completed , the module will be new, but it uses an existing API. MODFEE-154 Closed should just be checking that the transfer 'actions' appear on the Circulation Log. This should happen automatically, but if it doesn't there will be some BE work needed to an existing module. Please let me know if you have any other questions about these 2 user stories. The other user stories (see 'is defined by' links, are being handled by Phil. Thanks, Holly

Comment by Marc Johnson [ 28/Jan/21 ]

Is this work specific only to Cornell or is it intended to be a general process for other FOLIO implementors?

Comment by Debra Howell [ 28/Jan/21 ]

Marc Johnson This work is specific to Cornell, however, the work is being completed with an eye towards contributing it to the community.

Comment by Marc Johnson [ 28/Jan/21 ]

Debra Howell Thanks

Comment by Erin Nettifee [ 01/Feb/21 ]

Hi - the comments on UXPROD-105 Closed suggest that there was discussion about using the LDP to generate the extract for the fee/fine transfer, but am I correct in reading this that that's not the path that's being taken? That there's a module being written to extract the fee/fine data somehow?

Comment by Debra Howell [ 01/Feb/21 ]

Erin Nettifee UXPROD-105 Closed was a showstopper for Cornell that will not be ready for inclusion in Iris. After discussions with @holly and some other folks, Cornell decided to hire developers to build an export for us. Holly broke off this piece from UXPROD-105 Closed , so that we can track the work.

Comment by Erin Nettifee [ 01/Feb/21 ]

Right Debra Howell I understand this is specific to Cornell, but I'd also understand that the work done here could / would be repurposed into the general functionality to eventually support UXPROD-105 Closed . I'm mainly wondering if Cornell is still pursuing the LDP based approach that was outlined in the comments on that Jira, since this Jira implies that you're not... that a module is actually being built?

Comment by Debra Howell [ 01/Feb/21 ]

Erin NettifeeAh! No, we are not pursuing the LDP-based approach. It doesn't work for our needs.

Comment by Nick Cappadona [ 24/Feb/21 ]

I have shared the Amazon Resource Name (ARN) for each of the following Cornell AWS resources with Aleksei Prokhorov via Slack:

  • S3 bucket
  • IAM role

 

I am waiting to hear back from him with the ARN for the AWS account Scout will be using to test this during development. Once I have that I will update the trust relationship on the IAM role so that it can be assumed by this account to gain appropriate access to the S3 bucket.

 

Hongwei Ji & Mark Veksler : Heads up that I have also included the ARN for the AWS account we used when setting up the logs shipper via Lambda in the trust relationship for this new IAM role. We can always adjust these as needed once this feature is included in a release.

Comment by Debra Howell [ 22/Apr/21 ]

In Iris and tested.

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