Agenda for HOLLIS Liaisons Meeting #66
Notes from the May Meeting
indicates that messages 17, 18, and 19 are on a second screen. To see the second and subsequent screens, use the FWD (forward) command. To move backward through screens, use the BWD (backward) command. To redisplay the top of the list (on the first screen) use the TOP command.
OSPR is concerned that staff unfamiliar with EMS functions may miss messages listed on the second screen of the bulletin board. The best solution to this problem appears to be a combination of
While library staff are welcome to use the bulletin board for business-related messages, they are responsible for deleting a message promptly when its usefulness has passed. OSPR reserves the right to delete any common message at any time.
The HOLLIS Reference Manual Appendix R describes the EMS system and provides a full list of valid commands. In addition, OSPR offers periodic training in basic EMS functions. If you have any questions, please contact Julie Wetherill at OSPR (495-3724).
HOLLIS reference questions on the dial assistance line. OSPR has received an increasing number of reference calls coming in over the HOLLIS dial assistance line (495-0490). The dial assistance line provides technical assistance to those having trouble dialing into the HOLLIS system. OSPR always refers any reference questions to an appropriate library reference desk. Public service liaisons confirmed that OSPR referral of reference questions is appropriate and desirable. Telephone reference is a service provided by most Harvard libraries.
Status of Internet access. OSPR continues to perform testing of the Internet connections to the RLIN and EPIC systems. We anticipate that problems will be resolved and both systems will be available on the OIT application menu in mid-June. OSPR is also considering adding a generic Telnet facility option and the HUBS service to the menu for staff terminals. (HUBS is currently accessible from all staff terminals despite the fact that it does not display as an option.) There will be more on these projects as development continues.
Summary of the Spring 1991 HOLLIS managers meeting. The spring meeting of HOLLIS managers was devoted to discussion of a HOLLIS "business resumption" plan. Harvard libraries are heavily dependent on online systems when performing work-related tasks and it is clear that there should be a provision for restoring system functions in the event of a disaster. (Responses to Tracey's recent informal HOLLIS use survey indicate that 60 percent of library staff use HOLLIS at least 5 hours each day.) Managers have been asked to identify the essential HOLLIS system components that should be available after a disaster and the time frame in which recovery should take place. Library system business resumption planning is part of a larger effort by the OIT (Office for Information Technology) Data Center to develop a business resumption plan for their major customers. The next step is for managers to meet in smaller discussion groups to define recovery plans in detail.
Managers also spent some time discussing recent HOLLIS developments and enhancements (which were described in detail in the May 1991 HOLLIS Newsletter).
Update on the location display project. Priscilla Caplan, Head of OSPR's Systems Development Division, presented a progress report on a project to allow users to request location information while within a citation database. Consult the article "New Location Display Feature" in the Feature Articles section of this newsletter.
Review of enhancements list, part 2. Liaisons completed a review of the HOLLIS enhancement list, which began at the April liaisons meeting. Tracey reminded liaisons that the enhancements list includes both true enhancements and bugs because the same programming staff work on both. Some liaisons were concerned about OSPR's focus - - do bugs or enhancements have priority. Tracey noted that in some cases, OSPR programming staff must devote immediate attention to bugs which corrupt data or in some way interfere with the performance of HOLLIS or HULPR. All other "non-critical" bugs and enhancements inevitably end up on the enhancement list. Tracey suggested that the distinction between "bugs" and enhancements is not a particularly significant one. Input from liaisons is critical to OSPR in determining the priority of items on the list, regardless of whether the item qualifies as a "bug" or as a true "enhancement".
Tracey announced that the top vote-getters in the "my favorite enhancement" survey were the following:
online vendor indexes (4 votes)
sort LOC fields in catalog display (3 votes)
O/P/R display enhancements (3)
page through bibliographic and order records (3)
interface with outside binding services (3)
explicit truncation in string indexes (3)
microcomputer-based reporting (3)
The small number of votes reflects a low response to this survey.
In response to the review of the list and the survey results, liaisons have set up the following groups to review specific enhancements:
Interface with outside binding services:
We need a few more volunteers for the binding services group. Please contact Tracey Robinson if you are interested in participating.
LOC field sequence and sorting:
In addition, we would like to establish the following groups. If you would like to volunteer, please contact Tracey Robinson.
Tracey also announced a few new additions to the enhancements list:
This new location display feature will proceed in the following manner:
From the location display a user can enter Cn or Hn commands to see circulation and holdings information just as he/she would from the long or short display of an HU bibliographic record. The user is still in the AI database, but is now looking through a "window" into the HU database.
OSPR is designing the new location display feature to work in any database where it is suitable. In the AI and LR databases, the link between a citation record and the host item in the HU database will be the ISSN (international standard serial number). In later HOLLIS citation databases, the link between the analytic record and the HU record may be data other than ISSN, such as ISBN (international standard book number).
Regardless of what the linking information turns out to be, how will the system handle the case where the analytic record does not contain the linking information, or the case where the analytic record links up with more than one HU record? In the former case, OSPR is confident that as the use of linking numbers (such as ISSNs and ISBNs) becomes more common, database producers will be more diligent in including these numbers on their citation records. When the system encounters an analytic record that does not contain linking information, it will display a message warning the user to search the HU database directly before assuming the host item is not held locally.
There are currently 50 records in the AI database that do not contain ISSN's. Information Access Company, who owns this data, has assured OSPR that they will add ISSN's to records lacking them.
In the latter case (multiple HU records retrieved) the University should strive to reduce the amount of duplication in the HU database, which will in turn reduce the likelihood that the LOC command would retrieve more than one HU record. This effort includes reducing the number of HU records containing duplicate ISBNs and investigating a change to serial cataloging practices related to multiple version information. The HOLLIS Administrative Advisory Committee (HAAC) is currently considering changes prescribing that multiple versions (microform and paper, CD and laser disk, etc.) of a serial be described on the same bibliographic record. OSPR is also designing an algorithm that will select a single record from a group of potential matching records.
What will be the system's response when no HU record is found? In the event that the link to HU fails, a message will display instructing the user to search the HU database directly. OSPR is still designing the exact text of this message and an accompanying help screen.
Because of this project, won't there be a need to improve the current library location display in catalog mode? Currently, LOCs appear in the order they were added to the bibliographic record. Liaisons are unanimous that all occurrences of a library's LOC display together, but they do not agree on the order in which LOCs should display (strictly alphabetically or Harvard libraries first). Tracey agreed to set up a group to discuss this topic.
The overall design of the LOC command and location display is in place -- OSPR distributed a functional specification describing this new feature in April. Before all programming is complete, we hope library staff will review this specification and contact OSPR with any questions and comments. Contact Eric Young at 495-3724 if you need a copy of this specification. The location display feature is scheduled to become available in catalog mode in time for the fall semester. OSPR will notify staff through this newsletter and via electronic mail as development proceeds.
How NOT to use the DERI Command. With the advent of the DERI (derive) command, library staff can now create new bibliographic records using an existing record as a template. (See the February and March HOLLIS Newsletters for details about this new command.) However, it appears that some library staff members are creating bibliographic records in the HU database just for the purpose of templating. For example, the following record,
is designed to be a template for bibliographic records describing individual monographs in the Emory University law and economics working paper series. There are at least two problems with this practice:
OSPR strongly discourages this practice of creating template records in the HU database that do not represent real items held by Harvard libraries. These records are indexed along with real bibliographic data and will interfere with online searching activities. Please derive only from real bibliographic data or create these templates in the training file (TR) and then derive from them into HU. If you have any questions, please contact Julie Wetherill or Robin Wendler at OSPR (495-3724).
Notes and Reminders
Index display enhancements. OSPR has recently completed a number of index display enhancements at the request of library staff. These include:
As part of this project, all HOLLIS indexes must be regenerated in order to incorporate these changes. As this newsletter goes to print, only the call number indexes (CL, CW, and CO) have not yet been regenerated -- and these should be finished by the end of May. If you have any questions about these changes please contact MacKenzie Smith at OSPR (495-3724).
Extra copies of "Displaying Harvard Locations" available. Additional copies of the "Display Harvard Location" paper that Priscilla Caplan discussed at the May Liaisons meeting are available in OSPR. (An article summarizing Cilla's presentation appears in this newsletter.) Call Eric at 495-3724 to request a copy if you did not already receive one.
ACU reports every Friday. From now until the end of the fiscal year (June 30) the "HOLLIS Accounting Unit Status Report" (ACU reports) will be produced every Friday (except 06/28) for Monday distribution. Please note that this schedule SUPERSEDES the regular schedule of production (that is, the 15th and the 31st of each month). On July 1st we will go back to producing ACU reports twice a month.
Pre-1977 Widener record load. On May 3rd, OSPR loaded 14,841 OCLC records representing Widener materials cataloged prior to 1977. Since some of these records contain old Widener subject headings and miscoded Library of Congress call numbers, Widener is planning a summer cleanup project. Cataloging notification reports (accompanied by a cover letter indicating that this was a special load of records) have been distributed. During this cleanup effort, library staff do not need to notify Widener cataloging if they come across errors in these records.
Billing for cataloging notifies. At the May liaisons meeting, Tracey misstated that library units were charged for the cataloging notification reports that are printed after each utility tape cycle. As it turns out, there are currently no charges to libraries for these reports. Sorry for the confusion.
Change to HULPR catalog mode password. Since catalog mode became available in mid-1988, we have been using the same "secret command" to exit from catalog mode in the HULPR system. In order to keep in step with our obligations to improve system security, OSPR will change this command at the beginning of the 1991-1992 fiscal year (that is, 1 July). OSPR will announce the new command to all HOLLIS primary liaisons in early June. Liaisons should make sure that all library staff are aware of this change before the new fiscal year begins. In the future, we plan on changing this password at the beginning of the each fiscal year. If you have any questions, contact Julie Wetherill at OSPR (495-3724).
Response time tests. Response time tests are scheduled for the first Tuesday of each month. Upcoming tests are scheduled for: 4 June, 2 July, 6 August, and 3 September. Volunteers should mark their calendars appropriately.
Response times recorded during the May test are consistent with previous months. About 84% of the transactions took less than 2 seconds. Keyword transactions continue to take somewhat longer than other types of searches and transactions. The average response time for test keyword searches was just over 3 seconds; the average response time for all other test transactions was about three-quarters (.75) of one second.
HOLLIS Hints: Default subfield coding.
HOLLIS supplies default subfield coding based on the likely order of subfields within each field. If you need to add subfields that deviate from the likely default order -- such as adding only subfields a (title proper) and c (statement of responsibility) to field 924 -- HOLLIS will supply incorrect subfield coding. This feature can be useful in cutting down keying time. It will work with all bibliographic formats as well as the holdings and authority formats. In some cases, such as in the holdings format, variable fields often contain a sequence of subfields that deviate from the default order and therefore this technique will not always work. For more information, consult section 188.8.131.52.3. in the HOLLIS Reference Manual.
Inserting fields containing repeat numbers. There has been much discussion about ways of inserting fields or data into an existing record display. There is a special method of inserting repeatable fields into a specific sequence within the record display. To insert a repeatable field into a group of existing fields of the same type, assign to the new field the appropriate repeat number. The existing field with that repeat number, as well as fields below it, will be renumbered when the new field is inserted into its proper place. For example, given the existing display:
you want to add a new 500 note that will be the first in the group. You move the cursor to the first free line below the data on the screen and type the following:
After you press enter to reformat, the resulting display will be:
Of course, if the field you want to insert is not repeatable, this technique will not work. Consult section 184.108.40.206. in the HOLLIS Reference Manual for more information.
Vendor File Changes in May