Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Project Owner: Ian Chan (Unlicensed)

Overall Status

IN-PROGRESS 

Meeting Notes

2016-04-18 Meeting notes

NameLocationNotes
Systems integration surveyGoogle Forms Survey

Determine current configurations and workflow specifics.

CSU-ULMS/User-Data-via-Alma-API Github 
User Data via New Alma APIBitbucketLogin and team membership required
ILLiad Login Bitbucket

Login and team membership required

Uses deprecated SOAP API. CSUSM will udate to new REST API and post to Github

Major Milestones

StageComplete ByStatus
Meet to define overall project goals
 
COMPLETED
Send systems integration survey
(in collaboration with other TF) 

  

COMPLETED

Upgrade CSUSM code to utilize Alma REST-based API
 

COMPLETED

Review survey findings and discuss deliverables

  

NOT STARTED

Finalize requirements for version 1 of ILLiad-Alma integration
 
NOT STARTED
ILLiad-Alma integration - version 1 ready for campus testing
 
NOT STARTED
ILLiad-Alma integration - version 1 production-ready
 
NOT STARTED

Project Team

RoleName
Project Lead
Team Members
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

Scope

  • Computer sign-on scripts (San Francisco, San Diego, Long Beach)
    • Envisionware (may consider SIP2)
    • SIP2 - Cybrarian (Sacramento)
  • EZProxy 
  • ILLiad
  • Hoopla (CSUSB)

Requirements / Risks

ILLiad-Alma User Data Integration version 1

EZproxy-Alma User Data Integration version 1

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

 

  • No labels