Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Overall Status
| Status | ||||
|---|---|---|---|---|
|
Major Milestones
| Stage | Complete By | Status | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Meet with CO CMS and Identity Management group to discuss project |
|
| ||||||||
| Meet with vanguard campuses (Fresno, Fullerton, Northridge) to discuss project |
|
| ||||||||
| Vanguard campuses tweak existing process to accommodate Alma |
|
|
| Review survey of libraries' needs regarding parton load |
|
| ||||||||
| Deliver draft requirements document and sample code from vanguard campuses to CMS |
|
| ||||||||
| Create Access Services taskforce to standardize patron types and expiry date |
|
| ||||||||
| Final requirements document |
| delivered to CO CMS |
|
|
|
|
CO CMS |
develops initial |
export process |
|
| ||||||
| Begin testing of CO-developed patron extract with initial test group (= vanguard) campuses |
|
|
| Testing and feedback |
|
| ||||||||
| CMS Development updates |
|
| ||||||
| Campus round 2 testing |
|
| |||||||
| CMS final development |
|
|
| Project delivered in MP 24 |
|
|
Project Team
Why are we doing this?
Staff need to be able to login to Alma and end-users need to be able to login to Primo to perform tasks. Adopting a systemwide approach allows us to streamline the process for setting-up authentication. It also allows us to coordinate this work with the related task of automating the loading of patron data from PeopleSoft to Alma.