List of Integrations

• Regular and ad hoc reporting

• we have a culture of direct database access

• supports daily operational needs and workflows, extends functionality of LMS and allows links to other systems

• daypass and visitor management database (see below)

• shelf reading/inventory database

• shelving accuracy database (QC for student shelvers)

• Reserves pull lists (must join with Ares data)

• e.g. locker rental and faculty rental database rely on direct access to patron information

• ability to define, code, and run custom reports that we define

• To ask other customers: how does the system help with ARL/IPEDS reporting? How do you do it?

• Standards and Integrations with other systems

• EDIFACT  (ordering, invoicing, claiming) 

• APIs for Real-time Acquisitions (e.g. GOBI API) 

• Voucher feed to Comptroller

• ILL & citation managers

• Z39.50

• ILLiad, Relais D2D (runs consortial borrowing programs UBorrow , BorrowDirect), OCLC

• NCIP, Z39.50: four messages that need to be supported: 

• AcceptItem

• PatronLookUp

• CheckOutItem

• CheckInItem

• ILLiad add-on pulls item info from LMS via API

• Mansueto Automated Storage and Retrieval (Dematic) 

• Export records to ASR

• ASR updates item status in LMS

• request items from ASR

• Reserves management integration (Ares)

• must allow the remote system to place an item on reserve and remove from reserve

• may involve changing location, loan period, circulation status in support of this workflow

• Course management integration (Blackboard, Canvas, LTI)

• Ares add-on pulls item info from LMS via API

• Special Collections requisition (Aeon)

• MeeScan (uses SIP2)

• Payment systems for patron charges (or integration w/ 3rd party systems)

• Staff-facing for service desk payments

• Online patron-facing for self-service

• PCI compliant (Moneris preferred vendor)

• Export patron financial info to external systems

• e.g. Bursar, collections agencies

• Integration with campus IdM

• Flow of identities into system

• Maintenance of identities

• Also support identities that are not part of campus IdM

• Day pass database/access control integration

• use LMS patron data to verify eligibility and provide physical access (turnstile system) and credentials for network access (RADIUS, local AD domain)

• Relies on API or direct SQL access

• Integration with Discovery Layer (VuFind)

• circulation and docstore APIs used by VuFind directly.

• our driver for OLE is customized- we query the db directly in many cases. 

• MyAccount feature relies on VuFind to access patron data

• VuFind needs knowledge of both campus and non-campus borrowers in LMS

• How does authentication for MyAccount work so patron can access their data

• Proxy borrower support?

• map lookups, missing items form, report a problem form request data from OLE but exist outside of VuFind. 

• some requests come in for OLE data feeds, like a feed to provide info about techbar item availability. 

• Security review with IT Services

• FERPA requirements for data?

• Hosted? If run locally, how does it sit in the data center? (e.g. is vendor login access required?)

• Can we run test systems for operations, integrations, and upgrades?

• Client distribution (if not web-based): are there local desktop clients that need to be used?

• For hosting, what requirements do we have for performance?

Other Investigations

• how does the system perform authority control?