Versions Compared

Key

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

Project Owner: Ian Chan (Unlicensed)

Overall Status

Status
colourYellow
titleNot Started
 

Meeting Notes

  • e.g., in Google Drive
NameLocationNotes
CSU-ULMS/User-Data-via-Alma-API 
(
Github
) (Bitbucket, login
BitbucketLogin and team membership required
)(
Bitbucket
, login

Login and team membership required

) - uses

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

Github 

Github

Major Milestones

 
StageComplete ByStatus
Define scope and requirements 
Status
colourYellow
titleNot started
TBD dependent on scope and requirements  
   
   
  
   

Project Team

RoleName
Project LeadIan 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 

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)

Must Have

Should Have

Nice to Have

Out of Scope

TBD

Top 5 Risks

  •  

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