Technical Services Report: February 2010

System news and work completed

1. Switched SSL certificate providers and installed new certificates for all of the EZproxies.
2. Installed and tested the version 19 service pack released in December on the development server. Will be installing it on production on February 14, 2010.
3. Turned on the ue_08 process on production to automatically flip Bib headings that have been updated by LC Authority. Started loading the backlog of Authority updates on production. We will be loading approximately four weeks of files each week until we are caught up on the weekly Authority record updates. This will take approximately eight weeks.
4. Ran p_manage_15 to delete unlinked Bib headings on production over the MLK holiday weekend. This took approximately 4.5 days to complete. Will be setting up a regular schedule to run this service on production.
5. Performed global changes on the Bib records we identified that had the 150 field with subdivisions of $$v, $$x, or $$z incorrectly updated during the time ue_08 was turned on in August 2009. Discovered this also occurs in the 151 fields in the Subject file and the 100, 110, 111, 130 subdivision of $$v in the Name file and fixed these records also. Changed the fix routine to also set these Authority records to UPD=N.
   
6. Installed new licenses for version 19 on development and production that are good until 2015---for version 19.
7. Upgraded CUFTS/GODOT on development and production. This fixed the Gale database linking problem in PALSconnect Linker and the A-Z Resource list in PALSconnect ERM.
8. Installed a number of fixes and enhancements to MnPALS Plus on production.
9. Set up SVN access for MnPALS Plus for ODIN.

Work in progress

1. Working on enhancing the monitoring and reporting of system services from Nagios. (email, SMS, and Web interfaces)
2. After the backlog of the weekly Authority record updates have been loaded, we will run p_manage_103 over a series of weekends to flip any remaining records in the Bib database. There are approximately 3 million Bib records that will get analyzed. We have learned by running it on development that most of the Bib records that were identified as candidates for updates will not get flipped, and it was just the difference in punctuation between the Bib and Authority headings (ending period) that caused them to be selected. However, it will still re-index nearly half of the Bib database by the time it has been completed even though there will be no change in most of the Bib records.
3. We will be writing a script to create z305 tables for approximately 900 Rasmussen patrons before their data can be removed on production. This will be done as time permits. Once this is done, then p-cir-77 can be run to delete these patrons on development. After everything has been removed on development for Rasmussen, we will be removing their records on production.
4. Tested and implemented Web Self Check services on development. Will install on production after find out interest level from the libraries.