Checklist for the preparation for the Voyager 9.1.1
Before the update:o Check minimal requirements provided by CARLI
o Research best way to handle the installation process at our library
Decision: We will do a "manual" update checker installation.
This means that we will set all update checkers not to check automatically for
updates. This decision was made due to IT running updates between 2-5am each
morning. Felt like the precaution was worth the extra effort as a preventative
measure. (Will leave a couple non-Voyager computers in the Informatics office
on automatic to see if there would have been issues - for future reference.)
o Update staff client list (list with all library staff and which clients they have installed on their workstations.
o Email staff explaining the upcoming outage time and steps that will take place from a technology/installation standpoint.
o Check with each staff member to ensure that they still want the same clients that are on their list.
o Remove or add clients to workstations based from information from previous step.
o Install Voyager Checker on an computers that do not currently have it but will need it.
o Screenshot preference screens for applicable staff. Remember that the preferences are computer profile specific AND Voyager login specific.
o Communicate with staff about what the Global Data Change client is and that it will not be available immediately.
o Email patrons of outage the day of outage.
o Add announcement outage on website two weeks before outage.
o Email appropriate people in IT about upgrade and how it will affect them.
Decision: GPL office computer has IGLOO deep freeze so we will work
with IT on Tuesday after the upgrade to complete this installation since IT
will have to thaw it for us to work on it.
o Send email to student workers and staff about checkout procedure changes.
Decision: Library will be open on Saturday due to Freshman orientation.
Informatics will follow all of their normal procedures except for the actual
charge/discharge. They will take equipment up to the circulation desk with the
patron and assist the circulation student with any information that may be
needed (like checkout periods).
o Discuss implications of password change settings.
o Inform appropriate IT personnel that XML is now an option besides SIF for patron uploads.
o Backup SQL files from Access file for anyone who uses it.
Decision: We will replace our current mdb files with the new and
improved CARLI file. Then re-import our saved SQLs into their file.
o Save copy of current mdb files.o Comparison of three ini files to the new ini files
o Check with circulation to make sure they have not made any modifications since last installation
Decision: We are an I-Share email alternative so we are going to risk
doing nothing here. We have a backup of the mdb file just in case we need to
make modifications after the fact.
o
Put user guides on shared network drive.
After Completion of upgrade
(Monday, June 13, 7am)
o
Installation test on Informatics Librarian's
computer.o Retrieve new voyager and circ ini files - make changes per earlier research comparison.
o Quick test of functionality.
o Run update checker
o Replace ini files: callslip, voyager, circ
o Set Voyager Checker back to automatic checking
o Check/update client preferences in applicable clients
o Email staff about completion, issues to watch for (especially report changes that may need customization) and changes.
o Relink Oracle to Access Reports
o Import customized SQLs to each desired mdb file
o Check index REGENs schedule.
o Notify Kathy, Trish, Circulation and ILL of evening will we be updated.
No comments:
Post a Comment