Integrations, APIs, and the introduction of the Library Data Layer IGeLU: September Budapest, Hungary
Integrations Library Catalogue Research Outputs Catalogue Object Repository Alumni CatalogueMedia Repository Streaming media (AV) Document Delivery Research Object Repository myLibrary Course Readings lists User Account info Document Delivery requests** Single Sign-On (EZProxy / Moodle) Library APIs Corporate LMS (moodle) Reading lists Research outputs metadata self-serve to Alma Mobile App Users account info Course Readings lists ** Corporate Portals (staff / student) Users account info Users research outputs
Integrations: App Apple, Android, & Microsoft
Integrations: Moodle Course reading lists & recommended resources
Integrations: Moodle Course reading lists & recommended resources
Integrations: Student Portal Loans, Request, Fees
Integrations: Staff Portal Loans, Request, Fees
Integrations: Discovery Streaming Media
Integrations: Discovery Media Repository and Metrics
Integrations: Discovery Library Account
Working with the APIs Some risks: Availability of relevant data Inconsistency of data Change of delivery (SOAP / REST) Downtime / Loss of connection Speed
The “Data Layer” Vendor / Data custodian: e.g. ExLibris, Syndetics, Serials Solutions, In-House Data stores, Altmetrics Data Layer: Common, simplified communication interface to end user systems End user / User Interfaces: The clients (via discovery) Integrated systems (via APIs)
Stats August 2014 – July 2015 Library APIs Total: 16,022,654 March : 3,083,039
Stats August 2014 – July 2015 Primo APIs via Discovery Total: 13,258,269 May : 2,039,553
Stats August 2014 – July 2015 Alma APIs - RTA Total: 7,988,690 August: 1,580,239
Stats August 2014 – July 2015 Course Readings (Cache) Total From Cache: 829,683 Actual to Primo: 261,886
Questions? Thank You