2016-04-18 Meeting notes
Date | Â 1pm - 2pm |
---|---|
Attendees | Elizabeth Altman (Unlicensed), G (Unlicensed), Ian Chan (Unlicensed), Lauren Magnuson (Unlicensed), Renaldo Gjoshe (Unlicensed) |
Goals
- Define scope and requirements for how to best leverage the capabilities of the Alma User API.
- Discuss specific applications where Alma user data will be required.
- Discuss specific applications where Alma user data will be useful.
- Draft timeline and milestones, and determine point person for tasks and applications.
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
5min | Introductions | Ian Chan (Unlicensed) | Â |
25min | Applications that require Alma user data Applications where Alma user data might be useful | Ian Chan (Unlicensed) | EZproxy integration with Alma user data to restrict access to authorized users.
Populating ILLiad with Alma user data is a desirable outcome
Create requirements list for the end product - what fields are needed. How are usertypes in Alma translated to ILLiad?
Currently use LDAP for auth and III for patron data. Â Shib connection to Primo and Alma Look into use of Shiboleth for ILLiad across the system, as a follow-up project. Focus on the patron data scripts first. Issues with campus LDAP not indicating that a user is no longer part of campus community. How to check Alma for user expiration info for EZproxy? Hoopla - ebooks, video database (CSUSB) PC reservation - Envsionware can use SIP2. See what Self-check TF would like to do with this. - Lauren Magnuson (Unlicensed) Scholarworks - groups in ScholarWorks are dynamically assigned based on user types. Use LDAP data to differentiate user types for ScholarWorks
Follow-up with CSUS on who they are facilitating authentication for ILLiad-Alma plugin  |
10min | Potential timeline and milestones | Ian Chan (Unlicensed) | See above |
10min | Who does what | Ian Chan (Unlicensed) | See above |
Action items
See aboveÂ
ILLiad-Alma User Data Integration version 1
EZproxy-Alma User Data Integration version 1
Â
Â
Â