Meet with CO CMS and Identity Management group to discuss project
Status
colour
Green
title
Completed
Meet with vanguard campuses (Fresno, Fullerton, Northridge) to discuss project
Status
colour
Green
title
Completed
Vanguard campuses tweak existing process to accommodate Alma
Status
colour
Green
title
Completed
Review survey of libraries' needs regarding parton load
Status
colour
Green
title
Completed
Deliver draft requirements document and sample code from vanguard campuses to CMS
Status
colour
Green
title
Completed
Create Access Services taskforce to standardize patron types and expiry date
Status
colour
Green
title
Completed
Final requirements document delivered to CO CMS
Status
colour
Green
title
Completed
CO CMS develops initial export process
Status
colour
Blue
title
In-Progress
Begin testing of CO-developed patron extract with initial test group (= vanguard) campuses
Status
colour
Blue
title
In-Progress
Testing and feedback
Status
colour
Red
title
Not started
CMS Development updates
Status
colour
Red
title
Not started
Campus round 2 testing
Status
colour
Red
title
Not started
CMS final development
Status
colour
Red
title
Not started
Project delivered in MP 24
Status
colour
Red
title
Not started
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.
The Chancellor's Office CMS group has developed an app engine (read: batch script) that campus PeopleSoft groups can enable to automate the extract of user data from PeopleSoft to Alma.