Page Comparison

NOTE:  THESE PROCEDURES ARE IN DRAFT STATUS AND ARE SUBJECT TO CHANGE PRIOR TO GO-LIVE.

Procedure Directory

Background

Some CSU libraries export user fine/fee data to campus bursar systems. Creating an automated process allows for greater efficiency and provides the opportunity for integration of online payment through a campus payment processing system.  Alma's existing Bursar integration exports fines and fees data to an ERP system such as PeopleSoft, but upon export, the fines become closed and the user's record becomes active again.  The functionality desired by many campuses would enable fines and fees to be retrieved from Alma, payable by Credit Card through CashNet, with resulting confirmation of payment received by Alma and potentially by email to circulation desk staff.

...

• CashNet Products by Campus

...

Procedure Statement

This policy applies to the implementation considerations and system configuration required for exchanging user fine/fee data with a campus bursar system. 

Three Possible Models

I.  CashNet Portal 

Image Removed

Requirements:  Pay User Fines / Fees API, Export User Blocks, Users API, CashNet "SmartPay"

See:  Ex Libris Tech Blog:  Integrating Alma and PayPal with the Alma REST APIs

Through a CashNet portal, a payment type is set up through a campus' existing CashNet system, enabling users to login, view their balance of library fines, and make payments.   When the user logs into the portal, their username is sent to the Users API to retrieve fine amounts. The user pays the fines and fees through CashNet, and upon payment completion, information about the payment is generated and sent back to a script to be manipulated for import into Alma using the Pay User Fines / Fees API.  The fine is then logged as paid in Alma.

With this option, the only interaction with PeopleSoft would involve placing blocks / holds on the user's PeopleSoft record (for example, if the library places holds on student's registration for unpaid library fees).  Using the Export User Blocks integration with Alma, patrons with blocks such as registration holds can be exported and prepared for ingest to PeopleSoft.  We are still investigating removal of blocks, which may remain manual.  Could also use once-a-day Analytics data export to export fine amounts into PeopleSoft.

Issues/ Questions with this approach:

• Analytics data only available once a day (for export to PeopleSoft).  Ex Libris enhancement request:  Retrieve user accounts from Users API via fine amount?
• Removing Blocks/Holds in PeopleSoft remain manual; fine amount owed not available in PeopleSoft (necessarily) - if using Analytics API export, however, this could be available in PeopleSoft, once a day.
• Need more information about CashNet portal setup (Christian Ward (Sacramento) is researching)
  • Info from Christian:  Requires CashNet add-on called "Smart Pay" used to build a "Storefront" web application.  Sacramento's parking services is using this type of integration with a third party parking tickets application that enables guests and campus users to pay citations through CashNet.   We may be able to work with CashNet to create an interface that all campuses could use but would need the CO to help with that.  It may be more efficient to straight into CashNet without using the unique account page, but that would be worked out with CashNet.  See Information re: Parking Fine Payment @ Sac State
• Need to research any differences in approach for campuses using PayPal (e.g., Pomona) OR whether all CSUs using PayPal could move to CashNet for this integration.

II.  PeopleSoft Integration (San Marcos Approach)

Ian Chan (Unlicensed) at San Marcos is developing a solution that focuses on communication between Alma and PeopleSoft.  In this model, fines and fees data are generated through the Analytics API, as with the CashNet portal, and prepared for ingest into PeopleSoft.  San Marcos Campus IT is working on a script that checks user accounts periodically throughout  the day to check to see if payments have been made.  If a payment is made, that information is sent back to Alma through the Pay User Fines / Fees API.

Problems with this approach:

• Analytics data only available once a day.  Ex Libris enhancement request:  Retrieve user accounts from Users API via fine amount?

III.  Ex Libris Designed Solution

Christian Ward (Sacramento) noted that Ex Libris has created a fines / fees payment integration with a vendor through the UK (see documentation here), who only accepts payments in pounds (see Administration > General Configuration > Integration Profiles > Payment).  It was suggested that we press Ex Libris to develop a solution using CashNet directly, as many universities in the US use this vendor, and it would be benefit to a number of institutions.

Current export of fines and fees information integration closes fines and fees in Alma.  Would like Ex Libris to provide an option to export fines and fees to third party system while keeping the fine information open and active in the user's account.

Ex Libris should also enable the User API to be queried by user fine amount.  Relying on a once-daily acquisitions report to run information about fines and fees is limiting.

Implementation Considerations

...