Alma User API Integration

Project Owner: @Ian Chan (Unlicensed)

Overall Status

Complete

Ongoing support available for institutions working with the Alma User API. Contact members of this Task Force with questions.

Meeting Notes / Update Report

2016-04-18 Meeting notes

February 3, 2017 Alma User API TF Status Update

Project Links

Name	Location	Notes

Name	Location	Notes
CSU-ULMS/EZProxy-Alma-Authentication	GitHub	Public
CSU-ULMS/User-Data-via-Alma-API	Github	Public
User Data via New Alma API Alma-ILLiad-User-Data-Integration	Bitbucket Github	Login and team membership required Public
ILLiad Login ILLiad-Login-with-External-User-Data-Source Installation and Configuration Instructions	Bitbucket Github	Login and team membership required. Public
ILLiad Login (ASP)	BitBucket	Login required - contact @Lauren Magnuson (Unlicensed) for access This set of scripts generally follows the logon process that Jeanie Tan at Long Beach has described in this document (thanks Jeanie!):

Major Milestones

Stage	Complete By	Status

Stage	Complete By	Status
Meet to define overall project goals	Apr 18, 2016	Completed
Send systems integration survey (in collaboration with other TF)	May 16, 2016	Completed
Upgrade CSUSM code to utilize Alma REST-based API	May 20, 2016	Completed
Release sample EZProxy script	Mar 1, 2017	Completed
Review survey findings and discuss deliverables	Jun 17, 2016	COMPLETED
Finalize requirements for version 1 of ILLiad-Alma integration	Jun 20, 2016	COMPLETED
ILLiad-Alma integration - version 1 ready for campus testing	Sep 5, 2016	COMPLETED
ILLiad-Alma integration - version 1 production-ready	Dec 5, 2016	COMPLETED

Project Team

Role	Name

Role	Name
Project Lead	@Ian Chan (Unlicensed), San Marcos
Team Members	@Lauren Magnuson (Unlicensed), Northridge @Elizabeth Altman (Unlicensed), Northridge @G (Unlicensed), Stanislaus @Renaldo Gjoshe (Unlicensed), Fresno
Vendor Contacts
Informed / Other Stakeholders	@David Walker, @brandon dudley (Unlicensed)

Why are we doing this?

To ensure that patron information from the ILS (Alma), such as patron types or blocks, that are required for authorization into certain 3rd party library systems can be used in authentication.

Goals

EZProxy sample script
ILLiad sample script

Out of Scope

Computer sign-on scripts (San Francisco, San Diego, Long Beach)
- Envisionware (may consider SIP2)
- SIP2 - Cybrarian (Sacramento)
- Note: contact the task force if you need Alma User API support for these integrations.

Requirements / Risks

ILLiad-Alma User Data Integration version 1

EZproxy-Alma User Data Integration version 1

Systems integration survey

Google Forms Survey

Determine current configurations and workflow specifics.

Related Activities

ILLiad - Alma Integration Task Force

Resources

Creating a Student Portal with the New Alma APIs

Ex Libris Student Portal Sample App - My Rails Library

Alma User API Documentation