Migration Tips & Tricks

Editor's Notes

• #3: SirsiDynix customer since 1990’sHorizon 7.4.2, HIP 3.09Running 8 on-site serversHorizon Production ServerHIP ServerWeb Reporter ServerWeb ServerExchange ServerNetwork Storage ServerPrint Management ServerScreen Door (network security) Server
• #4: Reduce number of on-site servers Lower utilitiesLess hands-on upkeep5 year TCO savings would equal approx. the cost of replacing three servers (HIP, Horizon, WR)Makes us portable – can access Horizon at off-site locations, outreachTemporary renovation/re-location being planned post-migration
• #5: A LOT, hence this program!
• #7: Complete one before you migrate – why bring all those old items over if you aren’t going to need them?
• #8: If you have a test database, run the upgrade there first.Put it through its paces. (SaaS was an all or nothing process, but the upgrade could have been tested)Plan at least a week to experiment with the changesHave a “test collection” you can useSet up test parametersShort circ period to go to overduesShort expiration dates
• #9: Negotiate for one in your next contractGet the Test database included in any system migration/upgrade plans and costsUntil then – Network with colleagues in similar situations – listserv, in person, etc.Have they upgraded?What did they notice was different?What did they wish they’d trained harder on?Ask SD (or your company) for a list of references/other libraries you can contact
• #10: Make lists/take screenshotsTables you rely on for reportsCustom Views (or other database customizations)Reports you may have created Reports you rely on for statistics
• #11: WR creates reports, Narrowcast delivers them by email or on the flyRegardless of the report software/command language:Make a record of the statement(s) that drove the report if you created it or edited itALWAYS save a copy of the original before editingSpecial note of any joins or nested functionsKeep track of tables and attributes that were involved in the reportMonitor any subscriptions to reports
• #12: Don’t forget that partners like the collection agency need to know when you’re migrating or upgrading, so they can be sure your software is still working afterwards.Colleagues around the area might be able to offer suggestions or suspend ILL requestsOCLC needs to know so you don’t get ILL Requests while your system is offlineSchools might be able to spread the word that the resources are unavailable for reports, etc
• #13: Did it run correctly last month?When do you need it again?What will you lose?Can you capture it another way?
• #14: Make sure the software is currentCheck your settingsDownload your patron database and trap your blocks prior to going offlineBack up any transactions to a secure folder OFTENHave alternate plans for lack of powerTest laptops with barcode readers, remember which one worked with which!
• #15: Try running a day in Circ to see how it goes – are there transactions you can’t complete?If possible, run “live” client on one Circ computer, Offline on the otherTest uploads to the “live” server Watch for barcode errors, human errorDocument the common errors and their work-arounds
• #16: IP AddressesServersWorkstationsLaptopsSelf-checkPrintersDatabase IP rangesUser Names AND PASSWORDSUsers – WindowsUsers – Library softwareSys Admin for both network and ILSHIP (OPAC) adminDatabase admin (EBSCO, AllData, etc)Reporting SoftwarePC/Print Management Software Installs
• #17: Outlook contacts are the easiest – if you have the softwareSpace for notesPre-fab fields for youAvailable from any computer with access to your email Otherwise, minimum info needed:NameCompanyDirect Line or Phone # with ExtensionEmailPrimary Responsibility for your upgrade projectNice to haveNotes of dates/times of callsEmail conversations – keep them all until project is completed
• #18: Make sure you gather stats before going offlineDouble check everything.Print a copy and put it in a folderSave it on your network folder or flash driveEmail it to yourself offsite as well as at work if possible
• #19: On the webIn the paperOn the radioOn cable TVIn the newsletterOn the front doorPrint up business cardsPrint up bookmarksOn screen saversOn due date receiptsPost it in letters a MILE HIGHIn the language(s) your users needUsing clear languageAsk for feedback from people who don’t know about the projectDo they understand what you’re doingDo they know when you’ll be downDo they know what they can do in the mean timeWrite to your audienceBe prepared for questions from people looking RIGHT AT the sign you just posted
• #20: Have a backup plan to your backup planNothing ever goes as plannedPrepare forTechnology problemsIf the internet connection dies, then whatWeather problemsStorms, snow, etcElectrical/Utility problemsCan you keep the doors open without powerPersonnel problemsWhat if someone’s sickWho can cover that duty while you’re tied up with the upgrade
• #21: Network loginDo you use a generic circulation network login or does each person use their ownWho uses which computer for what, how oftenHorizon loginWhich network logins use which Horizon loginsWhich Horizon logins need to have which permissions
• #22: What access will you have to reporting structures?Will you have direct access to query your database?Will you have user access or sys admin access to change data from a command line?Will you have web access to WR or is the Desktop software available too?
• #23: What functions will you need customer support to run (mass indexer, phantom deletion) and what can you do on your own? Make sure you know how to get in touch with the folks who need to do those functions and that they know when you’re open! You don’t want them running some jobs when you need access to the system.
• #24: Will you lose statistics from before the migration or will they be there in the history?Will you be able to maintain the same statistics if you change platforms?Do the primary views (customer, item) look similar enough or are there new fields to consider?
• #25: Will any modules lose functionality?In our case, Sybase to MSSQL conversion caused errors in reports that have to be fixed manuallyHow will things like printing be affected? – in our case, we had to work for weeks to get overdues to print again. Even regular reports through HP (daily money reports) wouldn’t format correctly because of the Citrix interface. Had to tweak settings on the SaaS Server and home printer/computer to communicate across the internet. And it only works with that printer!
• #26: How long do you have to discover the glitchesHow long can you just call the tech support team for the same problem vs. logging the issueWhen does it become a billable service/new client care ticket?
• #27: Will be Laura England-Biggs after October 30!The picture is my cat, Cotton Malone, when she was just a baby. It has nothing to do with the slide, just thought it looked like she was asking a question!