Project Owner: Ian Chan (Unlicensed)
Overall Status
IN-PROGRESS
Meeting Notes
Project Links
| Name | Location | Notes |
|---|---|---|
| /User-Data-via-Alma-API | Github | |
| User Data via New Alma API | Bitbucket | Login 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
| Stage | Complete By | Status |
|---|---|---|
| Meet to define overall project goals | COMPLETED | |
| Upgrade CSUSM code to utilize Alma REST-based API | IN-PROGRESS | |
| 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
| 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
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