![]() |
Introduction to FCLA Aleph Reindexing Project Aleph v.19 OCLC Reclamation ILS Futures Discovery Tools Futures FCLA Website Redesign Aleph v18 Service Packs Aleph v18 Circulation Aleph v18 Acquisitions and Serials Aleph v18 Cataloging Mango/Endeca Metalib SFX Aleph DLU01 Library Reports and Statistics Data Warehouse and Reporting |
LMS News: 2 December 2008Today, December 2nd, the October service pack (up to rc 1871) will be installed on the Report server. The same service pack will go into Production on Sunday, December 7th. The system will be unavailable during the installs and after it has been brought up again and we have given the OK new files will be available for updating your existing clients through version check. If all goes well the Rept server install should be unavailable for 1 1/2 hours starting at 1:00 p.m. The Production server upgrade is expected to last from 7:00 a.m. until 8:30 a.m. Sunday morning.Here is a little more information on what should happen with this process: With the implementation of each service pack will come the need to update clients installed on all staff workstations at your institution. In order to update the staff clients we will push out the various update files by "Version Check" (mainly .exe files that must be updated to insure correct client behavior and configuration files, i.e., .dat or .ini). After the service pack is installed the update files to be pushed to the clients will be placed in the special "Version Check" directories in preparation for staff to pull the files over to their PCs. There are two ways of handling version check in the Aleph client (1) automatic check when the client application is opened, staff accepts the files when prompted (2) manually launching version check from the "Aleph/Version Check" menu option of any client and accepting the detected files. In order to successfully detect and retrieve the update files the Version check "Type" setting must correspond to the special directory where the files are located on the server. All test clients currently posted at http://www.fcla.edu/libraryservices/aleph/clientsv18.html were packaged with the version check type setting following this pattern: xx_updates Where xx is the institution code for your university: am (FAMU), cf (UCF), fa (FAU), fi (FIU), fs (FSU), gc (FGCU), nc (New College), nf (UNF), sf (USF), wf (UWF), uf (UF) e.g., for FAMU the Type would equal am_updates Last modified 2 December 2008 at 12:47 pm by jeanp | |||||||||||||||||||||||||||||||||||||||||||||||||||