Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Project Owner: Ian Chan (Unlicensed)

Overall Status

Status
colourYellowGreen
titleNot Started
 

Meeting Notes

  • e.g., in Google Drive

 

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

NameLocationNotes
CSU-ULMS/EZProxy-Alma-AuthenticationGitHubPublic
GithubPublic

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

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!):

CSULB_ILLiad_Logon_Process.pdf

Major Milestones

01 Jun
StageComplete ByStatus
 
Meet to define overall project goals
 
Status
colour
Yellow
Green
title
Not started 01 Jun
Completed
Send systems integration survey
(in collaboration with other TF) 

  

Status
colour

Yellow 

Green
title

Not started

Completed

Upgrade CSUSM code to utilize Alma REST-based API
 

Status
colour

Yellow 

Green
title

Not started

Completed

Release sample EZProxy script

 

Status
colour

Yellow

Green
title

Not started 

Completed

Review survey findings and discuss deliverables

  

Status
colour

Yellow 

Green
title

Not started

COMPLETED

Finalize requirements for version 1 of ILLiad-Alma integration
 

Status
colour

Yellow 

Green
title

Not started

COMPLETED

ILLiad-Alma integration - version 1 ready for campus testing
 

Status
colour

Yellow

Green
title

Not started            

COMPLETED

ILLiad-Alma integration - version 1 production-ready
 

Status
colourGreen
titleCOMPLETED

Project Team

RoleName
Project Lead
Team Members
Guillermo Meraz
Vendor Contacts

 

Informed / Other Stakeholders
 


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)
  • EZProxy 
  • ILLiad
  • Hoopla (CSUSB)

Must Have

Should Have

Nice to Have

Out of Scope

TBD

Top 5 Risks

  •  

    • 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 surveyGoogle 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