*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
Scope: LTS staff tabulate nearly all most acquisitions and cataloging functions on a monthly basis, via a special statistics gathering program that extracts data from the 948 field. The first indicator of the 948 field indicates type of transaction, i.e. pre-cataloging, cataloging, and post-catalogingbased on data in the FOLIO Instance Administrative Notes, Instance Status, Cataloged Date, and Instance Statistical Codes. Units and individuals may choose to record other statistics manually (e.g. NACO contributions, etc.)
Contacts: Adam Chandler, Laura Daniels
Date last reviewedupdated: 2021
Date of next review: September 20222026
Activities Codes and Definitions
Acquisitions and Pre-Cataloging
...
...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Individual Processes
A. Administrative
...
note and Statistical codes
Statistics for individual transactions are recorded in the Administrative note (sometimes referred to as a "Transaction data note (Holdings record") and in Statistical codes (Instance record).
in the Instance record. The codes in these elements are very similar to those that were used in the MARC 948, but the format to record them is different.
The transaction data note (recorded in the Administrative note field) is all lower case and is formatted with text labels and colons immediately preceding each code. There are no spaces before or after the colons; there are spaces between each element.
For example,
date:20210803 ttype:c userid:lew235 ploc:lts
This means on August 3, 2021, a user in LTS (ploc=physical location) with netid lew235 copy cataloged the title.
For reference, see Transaction data notes, Statistical codes, and 948s
...
B. Transaction type ("ttype:") codes and definitions
Anchor
1.
...
Pre-Cataloging Transactions
Administrative note Transaction data note (formerly 948, 1st indicator 0). Examples
i Inputting: pre-catalog creation of online bibliographic record
...
mpre Maintenance: pre-catalog update of pre-existing bibliographic record
r Receiving: receipt of new monographs
...
...
2. Cataloging transactions
Transaction data note (formerly 948, 1st indicator 1)Administrative note
c Non-fastcat copy: item with full or core level copy cataloged according to guidelines
in the "the Copy Cataloging (Non-Fastcat – need to update link)" procedure.f Fastcat: item with full or core level copy, cataloged according to guidelines in the "Fastcat" procedure.
k Shelf ready, vendor processed material, to be used during loading of shelf ready bibliographic records (Formerly Batchmatch/Marcadia fast processing: item processed from backlog)
l Added location: location added to existing bibliographic record
o Original cataloging, to include:
Minimal level cataloging, according to guidelines in "MLC Cataloging"PCC core cataloging, according to guidelines in "PCC cataloging" (obsolete--DO NOT USE)
PCC original cataloging, according to guidelines in "PCC cataloging"
s Fastshelve: creation of preliminary record for items that have been pre-assigned
classification or call numbers, including Cornell theses. Items are shelved
and available to the public before a complete bibliographic record is created.u Upgrade to PCC: e.g. copy lacking LC-style call number and/or subject
headings or minimal level copy upgraded locally to PCC core levelz Classification on receipt: to be used for printed monographic materials that, upon receipt, are ineligible for fast or copy cataloging and that are not immediately selected for original cataloging
Note: Count each cataloging transaction when a MFHD Holdings record is created, i.e. make a 948 field create a transaction data note for each transaction. Anchor
3. Post-Cataloging Transactions
Administrative note Transaction data note (formerly 948, 1st indicator 2)
a Added copy: copy added to existing location
b Recataloging: major editing of a bibliographic record for a previously
cataloged title -- for example, a change in format from book to serial, or a
change from a single volume to a multivolume monographmpost Maintenance: minor post-cataloging updates to records.
Includes pieces added (i.e. added volumes, partial transfers), addition of a uniform title field, and minor updates to bibliographic, holdings and item recordsw Withdrawal: of copy, piece or title -- now recorded in the Holdings record, see Withdrawals, Transfers, and Reinstatements
x Retrospective conversion: records input from CUL catalog cards.
Also includes the addition of holdings to an existing online record
from CUL catalog cardsy Reclass or SH assignment: significant changes made to call number,
or subject headings added
Note: Post-cataloging transactions require only one 948 transaction data note to record the transaction. For example, the operator may make multiple changes in a maintenance transaction (code m) but need add only one 948 field note to the record.
Definitions and examples
Copy cataloging
- A record already exists that includes subject headings as appropriate
- You may be
- Assigning LC classification
- Updating or adding notes
- Making other minor modifications (such as adding a variant title or additional contributor name)
- Adding vernacular script
- Correcting transliterations
Original cataloging
- No record exists in OCLC and you create one
- A record exists in OCLC that lacks subject headings (if subjects are appropriate) or has incorrect subject headings that need to be updated
- If you disagree with the subject headings but they are not technically incorrect, they should be left alone
- If the record was acceptable before you touched it, it is not original cataloging
Post-cataloging maintenance
- A cataloged record already exists in FOLIO
- You may be
- Updating contents notes
- Correcting or updating access points
- Overlaying our record with a more complete record from OCLC (without making any of the updates yourself)
- Fixing errors in the original cataloging
If you are fixing an error of your own, there should be no administrative note recorded
4. Statistical Codes
(data formerly recorded in 948 $h (Source of acquisition) and $f (Special format)
These codes are the same codes that were used in Voyager, but are selected from a drop-down menu instead.
...
Add table/list of Special format codes here
Anchor
...
C. Macros
Many macros have been created to make the addition of 948 fields transaction data notes easier for staff.
See the work and web presence of the Technical Services Macro Express Task Force.
, using MacroExpress
Commonly used macros are documented in Transaction data notes, Statistical Codes, and 948s
...
Batch Processes
Batch and automated processes are recorded in a 948 in the MARC bibliographic record. This is documented in Local Fields Tags Used in VoyagerNote: The stats program counts some formats (serials, videorecordings, scores) but not others. Memo from Gary Branch, June 25, 2018: "We’ve discovered our current statistics system does not accurately count microforms. It only counts very sporadically. It would require a complete retooling of the statistics program, testing, and rebuilding of the tables so we will have to live with this reality." [Added to procedure by Sarah Ross, June 28).