WGC Minutes - November 14, 2001
Present: David Banush, Nancy Holcomb (recorder), Jim LeBlanc, Rachel Maines, Linda Miller, Margaret Nichols (chair), Jean Pajerek, Lois Purcell, Adam Smith (guest), Pam Stansbury, Barbara Tarbox, Marijo Wilson, Iris Wolley.
1. MyContents--Iris Wolley and Adam Smith
Iris Wolley, a member of the MyLibrary team, invited Adam Smith, the functional leader for MyContents, to come and describe this service.
MyLibrary is a personal library space online, similar to a study carrel for print resources. MyUpdates and MyLinks are currently available within MyLibrary. MyContents, a current awareness service for tables of contents of serials, is being developed for release to the general Cornell community during spring semester 2002.
Vendors send tables of contents of journals to MyContents; subscribers select journals and have tables of contents automatically routed to them via e-mail. Currently, the journals of Mann and Vet libraries are in the MyContents service, including some library-related journals. Geneva and Engineering are also in the service; their journals will be available soon. Adam is working with selectors across campus to gather wider subject coverage for MyContents. He is also negotiating contracts with additional vendors.
2. RLIN delete workflow--Jim LeBlanc:
In NOTIS, we did implicit deletes by putting a "d" in the Leader/05 byte for Record Status. The "d" records could be called up only by NOTIS i.d., but would be exported to RLIN and deleted there. The "d" in Leader/05 does nothing in Voyager. But in RLIN, the "d" is necessary to do programmatic deletes. In order to do this deleting from RLIN, we need to set the "d" in Voyager, allow the record to be exported to and deleted from RLIN, and then go back in Voyager and manually delete the record.
Jim proposes a workflow that would allow automatic deleting of bibliographic records from RLIN and Voyager. It involves a program that would be run weekly, getting records that fit the delete profile and sending them to RLIN. Then, they would be loaded back into Voyager with bulk import, and deleted. The steps:
- Step 1: Done manually by staff: Set Leader/05 to d. Leave record unsuppressed from OPAC. On Mfhd, add a delimiter "z" note showing that the record is scheduled for deletion. Delete attached item records. (Records having attached purchase orders cannot be deleted from Voyager.)
- Step 2: Done automatically by the program: Extract records for ftp to RLIN. Report bibs with "d" in Leader/05. Send records to RLIN. (RLIN will delete these records.) Extract copies of bib "d" records from Voyager. Reload bib "d"s as deletes.
How useful would this delete program be for processing centers other than CTS? Representatives from Mann, Law, and ILR said they had relatively few deletes, and could handle them manually as they do currently. Could it be used in the case of withdrawals? Not if there are purchase orders or bills attached to the records. One potential use for the program is aggregator records that we may want to later delete as a group. Jim will consult with Barbara Tarbox to determine the usefulness of this program in TSSU, and delineate which types of records could be handled this way.
Lois Purcell asked about deleting our holdings from OCLC. Jim indicated that nothing has been done with OCLC deletes as yet.
3. The Digital Library Assistant shelf reader and enum/chron fields--Rachel Maines.
Rachel described the Digital Library Assistant shelf reader being used at the Hotel library. In order for the reader to work reliably for serial volumes, the enum/chron fields on item records need to be completely consistent. Rachel wishes to clean up Hotel serial records so that the volume caption for the enumeration will be always "v." and never "vol." She also wants to put the date in the chronology field, not have it included with the enumeration as has sometimes been done. WGC gave its blessing to these changes at Hotel, and wish Rachel and Hotel well in using the Digital Library Assistant. A suggestion was made that a committee be organized at some point to look into database management issues associated with any possible CUL conversion to the 3M tagging/shelf reading system.
4. GMD for electronic resources, changing from [computer file] to [electronic resource]--Jean Pajerek.
On December 1, LC will implement the change of GMD from [computer file] to [electronic resource]. Cornell will follow suit. Jean asked if we could retrospectively change records using [computer file] to [electronic resource] for consistency. Jim said this would be tricky in Voyager. We might not be able to find all of them. Should catalogers change those we come upon in the database? Yes, if we have to make other changes to the records. Nancy plans to send out a message to catalogers about this change as well as others in the AACR2 2001 Amendments. She will also send CU-LIB a message about this particular GMD change because Public Services uses this GMD as a limiting strategy in searching.
Minutes: Nancy Holcomb