CCS News
MAY 16, 2008
FROM THE COMPUTER ROOM:
Trees – effective June 1 we will no longer print any month end reports – we suspended the daily reports a long time ago but a few libraries were still using the monthly reports. Let Linda (847-666-3213) know if there are any concerns about this at all. Many of you have emailed us to say it’s time to stop sending these too.
Local Notice Printing – we are still printing notices but will “graduate” the first batch of libraries to print their own notices during the first week of June. As you know, we will no longer be able to ship notices via the van after August.
iBistro – we continue to monitor response time – but our summer Sundays do not see as much traffic as our Sunday’s during the colder weather. Our response time has been well within acceptable limits for several weeks now. But it is still very important that you tell us when response time seems unduly slow.
Memorial Day Weekend – the computer room will be staffed during normal hours on Friday, Saturday and Sunday, May 23-25. We will be closed on Monday May 26 to observe Memorial Day.
DID YOU KNOW?
Did you know that last week’s CCS News item about an error message that pops up when using function keys resulted in several people asking about where function keys are defined? There are actually two places where you can map functions keys and both are found under the Preferences menu on the main WorkFlows screen. If you follow the path: Preferences > Desktop > Current Toolbar > Function Key Mapping, a window will open that’s associated with whichever module you happen to be using at the time you start mapping. (i.e. Acquisitions, Cataloging, Circulation, etc.) Depending on the module, the Function Key Mapping window will have a number of keys already assigned and some of them will be grayed-out (can’t be used for another function). The existing mapped keys can be replaced with a new key, or you can map a new function to one of the available blank fields. Select the F#-key you want to map, click on the dropdown arrow to display all possible wizards, and select the one you want to add (or re-map). The mapped function keys apply to all windows in a module, so if you change an existing key in circulation, it will be changed for all wizards in circulation (on your workstation, under your login). If you want to map a key using the Shift+F# key or Alt+F# key, check the appropriate box at the top of the screen. You’ll notice that the functions mapped with Shift or Alt are completely different from the plain vanilla function keys you’ll see in the default mapping window.
The second place to map function keys is also found on the path: Preferences > Desktop > Current Toolbar >, but instead of selecting the Function Key Mapping option, you select the Local Toolbar Management option. Under Local Toolbar Files, right-click on the module for which you want to map a function key. (Of course, you need to have already copied the module from the Delivery Toolbar Files to Local Toolbar Files to do this.) The dropdown menu that displays will have an option called Function Key Mapping and if you select it you’ll see the same mapping window that appeared in the above procedure. The rest of the procedure is the same as above. – Ken Victorson
CCS MEETINGS NEXT WEEK:
Tues., 5/20, noon, Jameson’s: Technical
Group Chairs lunch
Wes., 5/21, 10:00, Schaumburg: ILUUG
(You must be registered!)
Thur., 5/22, 9:30, CCS: SCRAP
