Voyager Client Installations: Update Information
Desktop Services - Cornell University Library
Last updated: 9/12/2000. Amy Blumenthal <ab18@cornell.edu>

Date
(Recent at top)

Software affected
(Subject)

 Message (from Amy unless otherwise noted)
12 Sept 2000 megapatch instructions Here are complete (I hope) instructions for obtaining and installing the megapatch! Below the instructions is some further information/trivia.

1) Using FTP software, download the megapatch from digilib. It's in the CUL Voyager Installer folder, and it should be downloaded as a binary file. You can't run the installer yet (don't bother trying - it's password-protected), but if you download it now you'll have it ready for tomorrow.

2) By 8:00 Wednesday morning you'll receive a message from me saying that it's OK to start installing the patch. (Or you might hear that the upgrade was postponed...but judging from testing, I think we can be optimistic.) The message I send out will have the password for unlocking the installer.

3) Double-click on megapatch.exe, and type in the password. You'll see the usual installer stuff. READ THE INFORMATION SCREEN, since it will tell you exactly what's in the patch. A Typical install will install all the software included in the patch. A Compact install will only install the circ components. A Custom install will allow you to pick and choose. Be sure to install the software to the same place where your Voyager clients already are. The default is d:\voyager, but you can change that, depending on your particular computer's setup. The megapatch is an updater to what's already there - it's not a complete Voyager installer.

4) The installer will install the Voyager clients, tag tables, etc. Then it will invoke another installer, this time to install the Voyager system files. You may be prompted to reboot afterwards - do so if prompted.

5) If you have multiple Voyager folders (such as one for production and one for testing), they'll all need to be updated. You can copy and paste updated files into your second Voyager folder. These would be the tagtable folder, circ.exe, acq.exe, circ.exe, and 91300patch.txt.

What files are in this patch?
Endeavor has supplied us with new acquisitions (build1520), circulation (build 1503), and cataloging (build 1501) clients, as well as with a new system files set. (Some circ desks may already be running build 1503 of the circ client - this megapatch will ensure that all circ desks have it.)
This megapatch will not install shortcuts in the Start menu, since it's assumed your shortcuts are already in place.
Marty Kurth has included an updated set of tag tables, with a date file of 20000912. Due to the fact that the megapatch is not deleting files, only overwriting them, the previous date file of 20000614 will also be there. If you're neurotic you can delete it. :-)
Scott Wicks has asked for a settings change in acq.ini, so this file is included.
I've included a date file called 91300patch.txt.

Why is 91300patch.txt included?
You'll still be able to connect to Voyager if you don't run megapatch to update your software. However, we don't know what the functionality will be, or what problems you'll run into. For troubleshooting purposes we must insist that you update your software, and the presence of the 91300patch.txt file shows us that you did. (And of course we can check what build your circ, cat, and acq clients are, too - but the txt file is easier to spot.)

What about Reporter and Sysadmin?
Endeavor hasn't supplied us with new clients for Reporter and Sysadmin, so apparently they aren't affected by this upgrade. I did a test run of Reporter and it seemed fine.

If you run into any problems, or see anything weird, please contact Desktop Services ASAP! Email us at ltd-l, or call us at 5-8530.

Have fun!
Amy

18 Aug 2000 Circulation Macros from Jesse Koennecke:
A file of 15 Circulation macros has been added to the digilib server. This can be downloaded and imported to your existing Macro Express file. The file is in the macro files folder inside the Macro Express folder.
Important: These are set to function with Windows NT. If you want to use them on Win 95 or 98, you MUST change the SCOPE from ntvdm.exe to Circ.exe.
The macros include:
- Item Searching (by title, author, barcode, keyword, builder, and call number)
- Patron Searching
- Circulation Logon - needs to be modified to fit your location (change userID to your desk logon, and enter the password into the encrypted text field)
- Charge and Discharge
- And several others that may require modification to be used in your location

If you have created macros that may be useful for other circ departments, please send them to me (Jesse Koennecke) and I will update the file from time to time.

10 Aug 2000 new Reporter files for custom notices from Lydia Pettis:
Two new circ Reporter files have been placed on the DIGILIB server for retrieval by circ staff or net admins. These contain the approved systemwide textual changes to the paper and e-mail notices.
1)crcnotes.mdb: Access database with local text modifications to the circ notices
2)NoticeEmail.cfg: text file with local text modifications for e-mail messages

Circ staff or net admins will need to:

  • rename existing files for backup purposes
  • ftp the new files to each circ Reporter machine
  • verify they ftp'd correctly
  • move them to the correct location (if not done as part of ftp)
Performing these steps assume you are familiar with FTP, and using Explorer. The files should be retrieved at your earliest convenience, but not later than the 'live' e-mail date of 8/23.

Rename existing files:
1)In Explorer, open your Voyager / Reporter folder
2)Rename the existing versions of these files:
crcnotes.mdb --> crcnotes ORIG.mdb
NoticeEmail.cfg --> NoticeEmail ORIG.cfg

FTP files to your machine:
1)From each machine running the circ Reporter client, ftp to digilib.library.cornell.edu (user name Voyager; call 5-8530 if you need the password)
2)Open the Reporter folder on digilib
3)Select crcnotes.mdb, click the BINARY radio button and hit the left arrow to transfer to your machine
4)Select NoticeEmail.cfg, click the ASCII radio button and transfer to your machine
5)Make a note of where the files were placed on your machine (the default directory is the Bear Access ftp folder... unless you have modified your setup). The files need to go in the Voyager/Reporter folder. You can do this as part of the ftp process, or as a later step using Explorer, depending on your knowledge level.

Test that the files transferred correctly:
1)Open Explorer, and open the folder where the files were placed
2)Double-click NoticeEmail.cfg. This should open WordPad (if you're prompted to select a program to open choose WordPad). You should see a text file, and if you scroll down you should see the lines scroll off the page to the right. THIS IS NORMAL. Close the file without saving
3)Double-click crcnotes.mdb. It should open the MS Access database which contains all the notice report formats. If you click on one of the reports listed on the Reports tab, you should see the text of the notice display.
4)If anything looks strange, redo your ftp, making sure to get the radio button selections right. If it continues to look strange, contact ltd-l.

Move the files to the correct location on your hard disk:
1)Use Explorer to copy the files from the directory they were placed in when ftp'd, and place them in the Voyager / Reporter directory.

Please get these files at your earliest convenience. Ask your netadmin for assistance if needed. Send requests for additional assistance to ltd-l, NOT to me personally (I'm getting ready to go on vacation).

1 Aug 2000 Cataloging: updated tag tables On digilib.library.cornell.edu, in the CUL Voyager installer folder, is a folder called TagTables. It includes many changes from the previous set. You'll need to replace your current TagTable folder with this new one. The new timestamp file, inside the TagTable folder, says 20000726.

How to proceed:
1) Delete your current TagTable folder:
On your desktop computer, go to the Voyager folder. Now go into the Catalog folder, and you'll see two folders there - TagTable, and Template. Delete the entire TagTable folder.
2) FTP to digilib.library.cornell.edu. Open the CUL Voyager installer folder.
3) Download the new TagTable folder into your Catalog folder:
On the left pane of the FTP server, navigate around so that anything you FTP will go into your Catalog folder in Voyager. Now select the TagTable folder from the right pane and download that into the Catalog folder.

You're done! Quit out of FTP.
Remember that if you have more than one Voyager folder (alternating between live and testing, for example), you'll need to replace the TagTable folder in both folders. If you simply copy the TagTable folder to Catalog, rather than deleting it, you'll need to go in and delete the old timestamp file.

Amy

1 Aug 2000 preparing for Circ email notices from Lydia Pettis:
To all circ supervisors,
In preparation for going live with circ e-mail notices later this month, I'd like each of you to verify your system set-up to ensure you will be ready for this next phase of the Voyager reporting process.
Please go through this check list (action items in bold), and then write back to me to confirm that your are a-ok or to let me know if you have any questions. You may want to consult with your network administrator when performing these tasks.

1 - All e-mail related to library business MUST be sent out 'from' the e-mail address of the appropriate library unit, NOT the name of an invidual associated with that unit.
--- confirm that your circ desk has a registered e-mail address
--- confirm that the machine(s) on which you run Reporter has one and only one version of Eudora installed, and that the fields on the Eudora TOOLS menu/Options/Personal Info tab contain the e-mail address and name for the library unit.
*** Experimentation with e-mail on machines with multiple instances of Eudora, configured for different users, indicate you cannot reliably call one copy of Eudora over another. Therefore, it is a requirement that the circ reporter client run on a machine with one and only one instance of Eudora.

2 - Eudora settings:
-- REQUIRED: From the TOOLS menu, select OPTIONS and scroll down to the MAPI option, near the bottom of the list. Set the 'Use Eudora MAPI Server' option to ALWAYS. This should be done NOW. It is a one-time setting, and will not interfere with normal e-mail tasks.
-- OPTIONAL: The Eudora default for sending e-mail notices is to 'send immediately'. If this option is used in conjunction with the Voyager Reporter, as soon as you click the button to Run Reports, the e-mail messages will be sent to users. If you wish to delay the sending of e-mail notices until you can review them, you will need to change the default setting:
Tools / Options / Sending Mail: Look in the middle of the screen for 2 checkboxes: Immediate send / Send on Check. To review e-mail before sending make sure both these boxes are NOT checked. If they are, simply click the box to make the check go away. When you do this, the SEND button you click to send e-mail will change to a QUEUE button. All outgoing e-mail will be held in your OUT mailbox until you go to the FILE menu and select 'Send queued messages'. This affects all e-mail being sent from the computer.
Please contact me this week if you have any questions or problems. Due to my upcoming vacation beginning the week of August 14th, I want to make sure everyone is in good shape before I leave.

Lydia

2 Jul 2000 prepackaged reports for the production database On the digilib FTP site, in the folder called Access Reports, is now an Access database called VoyProd Reports.mdb. This is the prepackaged reports' set of links to the Voyager production database. You can download the Access Reports folder and place it inside your Voyager folder, or just download the VoyProd Reports database. If you need help doing this, check with your net admin.
Some of you may have downloaded a .mdb file called VoyCUt1 a month or two ago. This actually points to the production database now. You might want to rename it to VoyProd Reports.mdb, so it'll be clearer to you what data you're looking at; and then you don't have to download anything from the FTP server.
20 Jun 2000 Updated CUL Voyager Web pages At the bottom of the CUL Voyager Client Installations page (www.library.cornell.edu/dlit/ds/vc/) are two links you may find useful. One chronicles updates and changes to our Voyager setup (mostly taken from email I've sent to you), and the other describes what's on the FTP server. I'm going to TRY to keep these sites as up-to-date as possible.
On the FTP server page (www.library.cornell.edu/dlit/ds/vc/ftpserver.htm) I've included some things that are or will be obsolete. For example, the mini-installer was removed last week, but I've left a blurb (along with a note: REMOVED) on the page. This is so you won't go to the FTP site, not be able to find something, and think to yourself "I KNOW I saw this last week. What's going on?". The headings on this page pretty much correspond with the directories (folders) you see on the FTP site.
The updates and changes page (www.library.cornell.edu/dlit/ds/vc/status.htm) is mostly excerpts of email. It will be especially useful for new net admins. When I send out email I'll try to remember to remind you of the CUL Voyager Client Installations page, since it has links to both of the others.
16 Jun 2000 installer updated, new Circ executable, other FTP site changes Hi - some clean-up messages, and a NEW THING.
1) I've updated VoyagerSetup.exe to include yesterday's TagTables and country and language files.
2) I've removed the mini-installer from the FTP site. Its purpose was to help catalogers start off on the same foot on Day 1. If anyone feels we still need it, I can update it and put it back.
3) I've added a folder on digilib called Voyager Circ client. In it I've put a new Circ.exe client file. This fixes a bug Endeavor found with proxy patrons. My guess is that this mostly applies to the Voyager install at circulation desks. ILR and Hotel and anyone else who already has their circ desk computers ought to download this.
4) I've updated the zip file containing Cornell modifications. It's called 06162000 Cornell Modifications. New in this file are the TagTable folder and the Circ client.
15 Jun 2000 tag tables modified I added a TagTable folder, containing modified tag table files, to the CUL Voyager Installer folder on digilib.library.cornell.edu. The folder also contains modified copies of the files which list countries and languages (they were alphabetized for easier use). The tag table and country and language files are essential for catalogers.
The TagTable folder lives inside Voyager/Catalog. Delete the old folder, then copy the new folder in. By deleting the old folder you'll get rid of older files that might not be in the new TagTable folder, such as the datestamp file.
The Voyager installer has not yet been updated to include these changes.
10 Jun 2000 Iniswitcher - small modification Date: Sat, 10 Jun 2000 11:52:29 -0400
From: Amy Blumenthal <ab18@cornell.edu>
To: <CUL-NETADMIN-L@cornell.edu>
Subject: Iniswitcher - small modification

I've fixed a small annoyance in the Iniswitcher. Switchtoprod and switchtotrain run in a DOS window (black text-based thing), and on Win95/98 the window didn't close when the program finished running. It didn't "break" anything - it was just ugly.
I figured out how to make the window close, and I've put the fixed version of Iniswitcher on digilib (in the CUL Voyager Installer folder).
Note that this was only a problem in Win95/98. If you used it in NT, the DOS window closed just fine.
The fixed version works fine on 95/98 and NT.

Amy


>A lot of catalogers are finding that they want to switch back and forth
>between production and test Voyager, until everything goes live.
>You can make a copy of your Voyager folder, name it something else, and
>change the ini in it. So one folder is training and one's the real thing.
>Another alternative is to have a little program which will switch your inis
>for you. Then you don't need two folders.
>Hot off the presses is... Iniswitcher! You can download it from digilib -
>it lives in the CUL Voyager Installer folder.
>Iniswitcher should be installed into your Voyager folder. It includes the
>production and training inis. Shortcuts will be placed in your Voyager
>folder in the start menu. Switchtoprod switches the Voyager ini file to the
>production database. Swichtotrain will switch it to the training database.
07 Jun 2000

Mini-installer vs. regular installer

 Date: Wed, 07 Jun 2000 15:25:23 -0400
From: Amy Blumenthal <ab18@cornell.edu>
To: <CUL-NETADMIN-L@cornell.edu>
Subject: installer confusion?

I sent out two messages a little while ago, about a mini-installer and about a regular installer. One person tells me he's confused - so in case anyone else is, let me try to clear things up.

Who should use the mini-installer:
a) Anyone going live tomorrow who already has Voyager clients on their computer.
The mini-installer will update various files and point the Voyager clients to the production database. Anyone going live tomorrow will be ready to go once they run this. Most likely they will choose the "typical install" option.
b) If you're not going live, you can use it too. Choose the "custom install" option and uncheck the Voyager Production Ini file. This will update your tag tables, templates, etc. but leave your clients pointing to the training database.

Who should use the full Voyager installer:
Anyone who doesn't have Voyager installed at all (whether you'll be live tomorrow or not). This is the most recent version of the installer. It includes all the pieces in the mini-installer, but it doesn't point to the production database (the ini file is there but needs to be renamed).

Who should use the Cornell customizations zip file:
Those who only want to update a piece or two of their Voyager install and who prefer to do it manually.

I hope this helps! Please let me know if you're still confused... Sorry I wasn't clearer the first time.

Amy