College Data Store (CDS), Lead - Theresa Hilding
Members: Mark, Jim H, KC, JoshMarch 2, 2006
The SAS pilot will go live on March 18th as 22 student workers in the EC will begin using it to record their hours. The CDS is currently loading data (Faculty and students) from SIS only.Ê We are now looking at adding employee data to the CDS.Some CDS and Network File System team members have started conversations this week regarding the candidate file systems andÊ "new" Genesis' role in provisioning accounts and group memberships.
Our shortterm objectives are:
- to have a successful rollout of the SAS pilot and use the feedback to prepare the system for production.
- to work closely with the Network File System team to develop requirements for the new Genesis.
- to make a decision on the format on our local logon id for GCC specific systems. District is changing policy regarding publicizing the Enterprise ID and we are not sure where they are going to end up and whether we will be able to use it. We will be discussing the state of the Enterprise ID and Audree Thurman's All Colleges Repository with Audree tomorrow.
February 16, 2006
We've moved the test CDS instance to our production Oracle 10g server and have loaded real student and course data from SIS. SAS code is being modified to point to the new database and should be up and running shortly.We understand that at some point in the future, when NSS goes live, we will most likely have to make some modifications to the CDS schema in order to coexist more peacefully with EIMS and other District data sources. In order to make this transition as painless as possible we are examining what we can do now to "futureproof" CDS tables, views and code. This includes lively discussions on what to use as a primary key for bio/demo data - sid, SA emplid, EIMS global id or a gcc created key. Since we don't have access to EIMS we are looking at what timely data we can get from the district ADAM server.
SAS on the VAX currently assigns unique barcodes to students and staff when an id card is issued. We are discussing how to move that functionality to the new id card system.
February 9, 2006
The test Oracle 9i instance is in the process of being migrated to a more permanent and secure 10g server. The SAS group will be meeting next week for the first time since last Fall to see where we are at and to plan for the pilot deployment of SAS. Access to id card photos for online SAS photo rosters will be available as soon as the new access control and badging system goes production which should be within the next few days. Access to RDS and query analyzer has been requested from the District so that some progress can be made on CDS table definitions while we wait for access to the EIMS delta views.February 2, 2006
The good news is that the first application to utilitize the data in the CDS should be ready for an initial pilot test this month. That application is the SAS replacement. The bad news is that the CDS schema is not yet well defined as it is partially reliant on having access to the EIMS delta views. Access to these views has not yet been given to us from the District Office and I do not know when access will be granted. The delay in being given access is tied up with the go-live postponement of NSS.SAS will eventually offer photo rosters to replace the rosters currently provided by Genesis. With the pending deployment of the new ID card system the new SAS will shortly have access to current id photos to start development on these rosters.
