...
Page Properties | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
NOTE: THESE PROCEDURES ARE IN DRAFT STATUS AND ARE SUBJECT TO CHANGE PRIOR TO GO-LIVE.
Procedure Directory
Child pages (Children Display) |
---|
Background
Some campuses 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.
User fine and fee data is available to 3rd party systems through Alma's External Systems Integration Profile, the User API, and the Analytics API. The first option utilizes Alma's built-in export functionality to extract patron fine/fee data and S/FTP to a campus locationserver. Fines and fees exported via this method are considered closed in Alma, since they are handled by the campus bursar system.
...
Each method exports data in XML.
Import of user fine/fee payments payment updates to Alma is available only via the User API method. This However, any export method may be used with either the User API or Analytics API export methodthe payment update import process. Updates to user accounts are made on a per user basis. With PeopleSoft it is possible to utilize a reporting query or a query by an external script to retrieve fine/fee payment data for specific users.
...
Supporting Documents:
Procedure Statement
This policy applies to the setup required for importing records into the Network Zone via Connexion. This policy also outlines the system-wide settings for match, merge, normalization, and management tag settings used when importing and overlaying records from Connexion into the Alma Network Zone.
Best Practice Considerations
implementation considerations and system configuration required for exchanging user fine/fee data with a campus bursar system.
Implementation Considerations
Fines & Fees Export
How often should the library export user fine/fee data from Alma?
...
Will the Library retain over-the-counter payment methods and how will the bursar system receive those payment updates?
User API
Does the Library want real-time fines/fees output and payments sent between Alma & CASHNet or PayPal?
Availability to pay fines/fees for both Alma external and internal accounts.
Campuses may have already existing integrations between CASHNet and bursar system/PeopleSoft which may make the updating holds easier.
Procedures
Ex Libris Documentation:
...
Section | Point Person | Expected Completion Date | Last action taken | Next action required | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Provide documentation on potential integration methods and create list of best practice and procedural considerations. |
| |||||||||||
Tasks to be completed
- Working group provides feedback on initial documentation.
- San Marcos provides additional details on integration project.