1. Integrations, APIs, and the introduction of the Library Data Layer IGeLU: September 2015 - Budapest, Hungary

2. 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

3. Integrations: App Apple, Android, & Microsoft

4. Integrations: Moodle Course reading lists & recommended resources

5. Integrations: Moodle Course reading lists & recommended resources

6. Integrations: Student Portal Loans, Request, Fees

7. Integrations: Staff Portal Loans, Request, Fees

8. Integrations: Discovery Streaming Media

9. Integrations: Discovery Media Repository and Metrics

10. Integrations: Discovery Library Account

11. Working with the APIs Some risks: Availability of relevant data Inconsistency of data Change of delivery (SOAP / REST) Downtime / Loss of connection Speed

12. 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)

14. Stats August 2014 – July 2015 Library APIs Total: 16,022,654 March : 3,083,039

15. Stats August 2014 – July 2015 Primo APIs via Discovery Total: 13,258,269 May : 2,039,553

16. Stats August 2014 – July 2015 Alma APIs - RTA Total: 7,988,690 August: 1,580,239

17. Stats August 2014 – July 2015 Course Readings (Cache) Total From Cache: 829,683 Actual to Primo: 261,886

18. Questions? Thank You Ben.Dalwood@unisa.edu.au