...
Statistics are recorded in the Transaction data note (Holdings record) and in Statistical codes (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 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:i userid:lew235 ploc:lts
For reference, see See 948 field definitions. (A revised version of this will be created/linked to)
...
B. Activities Codes and DefinitionsTransaction type ("ttype:") codes and definitionsAnchor B B
Anchor B1 B1
We no longer have the equivalent of 1st indicators that we had in Voyager (explicitly differentiating between Pre-cataloging, Cataloging, and Post-cataloging). We do have the same codes that we used in the 948 $c to indicate the specific transaction. The type of transaction can be inferred from the code.
1. Pre-Cataloging Transactions 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
...
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 | ||||
|---|---|---|---|---|
|
...
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.
4. Statistical Codes (data formerly recorded in 948 $h (Source of acquisition) and $f (Special format)
...
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.
...