This is intended to serve as a best-practices guide to those creating new TKR, or tickler, fields in the catalog as well as a tool for using and interpreting many existing ticklers. Ticklers provide an easy means for staff to create and retrieve indexes of related records. TKR that are input on bib records are retrievable in both the public catalog browse search "Cataloging tickler," and in the client in UFU01 using the keyword (WTK) or browse (TKR) searches. TKR that are input on holding records are retrievable in UFU60 using the browse (TKR) search from the Catalog Module. There are several important categories of TKR currently in use, for example, those included automatically with record loads as well as those used to identify specific circulation, acquisitions, binding/preservation, cataloging, and digitization data.
In NOTIS ticklers were recorded in the 035 field (or the 909 field on provisional records) and prefaced with "(FU)" to support index retrieval. These migrated into Aleph TKR fields. The "(FU)" is not used for index retrieval. Ticklers have served us well in many ways over the years. Unfortunately, particular ticklers have often been so cryptic as to only be understood by the few people who use them, and they have often been entered inconsistently. It is hoped that by creating this guide to TKR use we will improve clarity and consistency for future catalog users.
Before designing a TKR, a search should be conducted in the catalog to guarantee that there is not a conflict with an existing usage.
When a new TKR is created, a message should be sent to the Catalog Problems email address describing the exact coding of the field, who it will chiefly be used by, and what it means. It will then be added to the TKR list.
- When it is deemed useful to preface the TKR with the department abbreviation, use the following: cat, acq, pres, dlc, acc, cir for UF or preface these with HC or LL for Health Center or Legal Information Center (i.e., llacq for acquisitions in the Legal Information Center).
Dates that are included in the TKR should be structured in the format: yyyymmdd.
Existing TKR fields should not be deleted without sufficient communication with other catalog users to determine that they are no longer of use. There may be some existing uses that could be terminated, but this should not be decided unilaterally.
- Consideration should be given to whether or not the field will quickly become obsolete on a particular record, and if deletion should be part of a workflow. TKR fields are automatically deleted when a record is overlaid in some loading processes, but in the typical loading of records from CONNEXION they are retained.
TKR List (link to EXCEL spreadsheet list of significant TKR's)
Acquisitions & Licensing Department's tickler page records the ticklers used by the CM Support Unit when creating pre-order records. These ticklers allow the Monographs Unit to retrieve indexes of pre-order records by fund. The department also uses ticklers to identify EOCRs (Electronic Order Confirmation Records) for specific vendors (e.g., YBPEOCR).
FCLA maintains the SUS Digital Library Project Codes webpage. This is a list of codes used in tickler and other fields on PALMM Project digitized resources records which are loaded to Aleph.
Please send questions or suggestions about existing TKR's not found on these lists to the Catalog Problems email address - email@example.com.
Created: February 14, 2006; revised: May 11, 2006.