In an earlier blog post, we discussed the structure of OneSearch’s metadata, aka PNX. (See: Behind OneSearch: Part 1 – Internal Records (PNX).)
If you’ve wondered exactly which MARC fields are being used to create each of those PNX fields, we’ve got good news for you! We extracted the data and are making it available for your review. The resulting spreadsheet (CUNY-ALEPH-Norm-Rules-2015-12.xlsx) contains a list of all fields used by the OneSearch normalization process which creates the PNX records. The data was retrieved at the beginning of December 2015.
Now you’ll know that the 856 field, for example, is being used in the following PNX sections:
- delivery/delcategory
- links/addlink
- links/linktoreview
- links/linktorsrc
- links/linktotoc
The first tab in the spreadsheet, MARC, contains all the MARC fields in use. The second tab, non-MARC, contains fields which do not use Aleph MARC as the source. The Non-MARC tab includes fields containing static text as well as fields generated from system data or other PNX fields.
Each column of spreadsheet data has a filter applied, so, for example, you can click on the drop-down box in the “MARC” column of the MARC tab and select ‘008’ only. This will display only those PNX fields which use the MARC 008 field. The other columns in the MARC tab are:
- Ind1 (1st indicator)
- Ind2 (2nd indicator)
- MARC Subfields
- PNX Section
- PNX Subsection
A minus (“-“) in the Ind1, Ind2, or MARC Subfields columns indicates that these values are omitted from use. You can think of it as the “NOT” Boolean operator. For example, the 500 field is used in the PNX display section but its “5” and “6” subfields ($$5, $$6) are omitted (MARC Subfields = “-56”).
If a number appears in the Ind1 or Ind2 field, only that specific indicator is used. If no number appears in these fields, all indicators are included.
An asterisk in the MARC Subfields column indicates that all subfields are used.
Download the spreadsheet here: CUNY-ALEPH-Norm-Rules-2015-12.xlsx
