2017-04-07 Meeting notes

Owned by Lauren Magnuson (Unlicensed)
Last updated: Apr 13, 2017 by Ian Chan (Unlicensed)
2 min read

Date

Attendees

Goals

  • Determine next steps for helping institutions with their Fine/Fee integration

Discussion items

TimeItemWhoNotes
20min

Information from CashNet

  • See March Status Update #2
  • Need decision:
    • should we pursue a CSU-wide solution given complexity of required eMarket?
    • What other information do we need?


Lauren Magnuson (Unlicensed) / All
10min 

 Form / define work plan for eMarket / PS Integration (San Marcos) / Bursar Integration subgroups/leads

  • Scope of each group
    • Gather / create documentation on each integration
    • Plan and host Zoom call describing steps for integration. Use Q&A format, gather questions in advance
 Lauren Magnuson (Unlicensed)

 San Marcos vs. Bursar Integration:

  • Ultimately San Marcos doesn't want to be accepting payments in the library
  • Benefit of San Marcos model: fine/fee is in Alma, can be used to continue to block user privileges if TOU is configured to
  • San Marcos uses Analytics output report (available as of 5PM previous day)
    • Alternate method to identify users for fines/fees -export user accounts that have changed in 24 hours
      • Used in production w/DCB
      • Could leverage and do additional queries to use this
  • 2 additional phases for San Marcos model to be completed
    • Will need separate eMarket as a backup for same day fine/fee transactions
      • e.g., someone incurs fee at noon, wants to pay immediately, can't be done w/existing PeopleSoft integration model
      • If borrowing privileges are not affected by fines/fees, no eMarket backup essential
    • How to handle community borrowers?
      • At Stanislaus, borrowing privileges are suspended
      • Paper form w/PeopleSoft details (user details, fine amount, and PeopleSoft account), send borrower to bursar's office
      • At San Marcos, separate eMarket for non-campus people, posts to library account in PeopleSoft in student financial services
        • Library itself does not manage transactions
  • Native bursar is much less work
    • Library has no involvement in fines/fees
    • Alma dumps data to PeopleSoft, no payment info gets sent back to Alma, fines/fees are closed in Alma

San Marcos PeopleSoft model update:

  • Not yet in production
  • Successfully uploaded data from Alma to PeopleSoft, including line item charge
  • Road block when working with PeopleSoft side
  • Difficult to automate ingestion of file from Alma to PeopleSoft
  • Haven't yet developed query for PeopleSoft to find payments and pay back into Alma (not road black, just hasn't been developed yet)

San Marcos use of eMarket:

  • Currently in production, user enters any amount owed manually, funds get paid directly to library account
  • To look at Alma > CashNet integration as a backup

Sacramento use of CashNet/T2:

  • T2 contains payment portal - payment protocol gets sent to CashNet via SmartPay - may be written into the Sacramento CashNet

  • Still would need a shopping cart system outside of Primo/Alma intermediary between Primo (analogous to eCommerce model from Millennium)

Action items