Page Comparison

Overall Status

Status

colour	Blue
title	In-Progress

Major Milestones

StageComplete ByStatusMeet with CO CMS and Identity Management group to discuss project

08 Oct 2015

StatuscolourGreentitleCompletedMeet with vanguard campuses (Fresno, Fullerton, Northridge) to discuss project

30 Nov 2015

StatuscolourGreentitleCompletedVanguard campuses tweak existing process to accommodate Alma

15 Jan 2016

StatuscolourGreentitleCompletedReview survey of libraries' needs regarding parton load

29 Jan 2016

StatuscolourGreentitleCompletedDeliver draft requirements document and sample code from vanguard campuses to CMS

01 Feb 2016

StatuscolourGreentitleCompletedCreate Access Services taskforce to standardize patron types and expiry date

22 Mar 2016

StatuscolourGreentitleCompletedFinal requirements document delivered to CO CMS

02 May 2016

StatuscolourGreentitleCompleted

CO CMS develops initial export process

29 Jul 2016

Status

colour	Blue
title	In-Progress

Begin testing of CO-developed patron extract with initial test group (= vanguard) campuses

01 Aug 2016

Status

colour	Blue
title	In-Progress

Testing and feedback

30 Sep 2016

Status

colour	Red
title	Not started

CMS Development updates30 Nov 2016

Status

colour	Red
title	Not started

Campus round 2 testing

31 Jan 2017

Status

colour	Red
title	Not started

CMS final development

28 Feb 2017

Status

colour	Red
title	Not started

Project delivered in MP 24

31 Mar 2017

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

About

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.