1 / 13

Implementation of online payments in Aleph

Implementation of online payments in Aleph. Matt Couzens, Library Services Joao Neves, IT Solutions. Session outline. Why online payments? The options considered The technologies used Implementation Demonstration How successful has it been?. Why online payments?.

zan
Download Presentation

Implementation of online payments in Aleph

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementation of online payments in Aleph Matt Couzens, Library Services Joao Neves, IT Solutions

  2. Session outline Why online payments? The options considered The technologies used Implementation Demonstration How successful has it been?

  3. Why online payments? • Manual transactions inefficient use of staff time • Over 30k active Aleph patrons • Annual fines to the value of approx £150k • 85 staff delivering the frontline service across our 6 libraries • Payments previously only taken at the desk, over the phone, by posting a cheque, or at the self-service kiosks • In response to customer feedback • Reductions in risk and cost through less cash handling and less processing of card data onsite

  4. The options considered • We wanted real-time payment, not overnight batch • No readymade solutions so we would have to develop our own • Which interface, Aleph OPAC or Primo? • no strong preference from a business perspective, but for technical reasons the Aleph OPAC was chosen • Create new payment gateway, or reuse an existing gateway? • Decided to integrate with existing print management system, PaperCut

  5. The technologies used • Rely on standard interfaces • Web Services, x-Server, REST-full ALEPH API, SIP2 • OPAC WEB • User session integration • Aleph templates • SIP2 • Client development • PAPERCUT – RESTFUL XML-RPC • Client development • Double checking of transactions • Financial reporting and account conciliation

  6. Implementation • IT/LS joint cooperation • Driven by LS Customer services • Requirements gathering & joint meetings • Acceptance document • Development environment • Papercut test server • Library (ALEPH) test server • UAT • Test done by LS • Development & Documentation and implementation in 3 months

  7. Implementation - issues • Issues • Multiple transaction debits (due to impatient users) • Partial payments (difficult and awkward database transactions) • Fixed amounts in Papercut.

  8. Demonstration…

  9. How successful has it been?

  10. How successful has it been? No serious issues, a few minor issues after go-live were quickly fixed Very successful collaboration between IT and Library Services Contributed to Library Services’ achievement of the UK government’s Customer Service Excellence standard in May 2014

  11. Any Questions? Matt Couzens Service Improvement Manager Library Services 020 7848 2792 Matt.couzens@kcl.ac.uk Joao Neves Senior Application Analyst - Library Systems Information Technology 020 7848 1527 Joao.neves@kcl.ac.uk

More Related