Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

  • Bursar integration: library "washes its hands" - money is owed to the university
  • eMarkets model
    • $3500/yr (unless unlimited eMarket license - no cost if your campus has unlimited licenses.  See this document for a list.)
    • Pros:  Somewhat easy to set up, minimal custom programming required (unless you want to automate email notifications > fine and fee payment API in Alma), enables payment by community users
    • Cons:  When you go into the CashNet portal, the amount user needs to pay is not specified. Shows as $0 balance due.  User must manually enter the amount they wish to pay.  When payment received, email is sent to circ inbox, and someone has to apply the payment to Alma and release payment in PeopleSoft.  Could potentially automate with script (needs development) to pull data out of email and send data to Alma Fines/Fees API.  Script could likely be ready by go-live.  Blocks / holds in PeopleSoft would have to be removed manually.  Possible cost to the library (up to $3500 / year)
    • Campus could purchase / take advantage of eMarket for year 1, while custom interface (see below) is developed
    • Note:  we are still seeking out more information to the following questions:  
      • More information needed: Accounting / reconciliation fines/fees and payment trails
        • When Sacramento used eCommerce model, daily totals sent to campus financials - entered into CashNet / automatically pushed into PeopleSoft in nightly job (at Sacramento for parking, no longer need receipts as they are sent to PeopleSoft automatically) -
        • Lauren Magnuson (Unlicensed) to ask CashNet rep how this works / gets reconciled w/campus financial systems;
        • Lauren Magnuson (Unlicensed) to ask about consortial deal on cheaper eMarket licenses
      • More information needed: Fines to go general fund, replacement costs are kept by the library - Can CashNet understand which fines go to which fund?
        • With parking T2 - there's an identifier for the type of transaction
        • bill by type of charge - fine/fee vs. replacement
        • Lauren Magnuson (Unlicensed) ask CashNet: Alma differentiates between transaction type (fine vs. replacement) - would CashNet be able to communicate the charge type that was paid back to Alma?
        • Lauren Magnuson (Unlicensed) reach out to Delfin at Stanislaus - student financial services
  • Library-specific custom payment portal:
    • This would be a custom interface developed by a working group across the CSU.  It would not be ready by go live, but would enable automation of fine/fee payment through the alma API, while Cashnet securely handles credit card transactions.  Users would see a fine/fee payment link in Primo, would login, and upon login, fine/fees would be pulled immediately from Alma, so amount owed would always be up-to-date.  Then they would be directed to a CashNet payment form.  Upon payment, data could be sent to Alma fine/fee payment API.  It is likely that removal of blocks / holds would still be manually removed, at least in early iterations of the app.
    • Pros:  Totally customizable with regard to notifications, enables fine/fee payment from community users, automatically updates fine/fees paid via Alma API
    • Cons:  Would not be complete by go-live.  Estimated timeline looks to Fall 2017 for completion.  Could either purchase 1-year eMarket license in the meantime, or handle fine/fee payment manually.
  • PeopleSoft Integration (San Marcos Model):
    • Enables fines/fees to be paid directly in PeopleSoft.  Requires a daily export of fines and fees (can be automated using Alma Analytics API) be sent to PeopleSoft and ingested.  Your campus IT would implement a script (San Marcos can provide an example of their working script) to check for payments made in PeopleSoft every x number of minutes, which can be sent to Alma via the fine/fee payment API.
    • Pros:  Takes advantage of existing PeopleSoft payment integration.  Working example available from Ian Chan (Unlicensed) at San Marcos.
    • Cons:  Single daily export of fines/fees owed may not be accurate if you also allow fine/fee payment at the desk, or you waive the fines at some point during the day due to daily analytics extract.  Guest users (non-campus affiliates) cannot use this integration.  Requires campus IT buy-in.
  • No labels