The following is taken from the Workflows helpfiles with notes by Nancy Boggess-Korekach in quotes. 9/29/06
Adding Analytics (Subfield z) to Call Numbers
When a new item is created in Unicorn, by either batch load or receiving orders or serial issues, Unicorn examines the call number in the bibliographic record and selected Class Scheme, such as LC, LCPER, DEWEY, and others. Based on Classification (Class Scheme) policy attribute definitions, Unicorn determines whether or not a |z is appended to the call number, and what the structure of the |z will be. Classification Policy Attributes that Affect Analytics
Analytic File Prefix
The Prefix portion of the Classification policy references a special /Unicorn/Custom file outlining the sorting/treatment of dates, volume, issue, and other analytic call number parts for each Classification policy. The name of the file is the prefix name plus.clas. If a prefix is recognized, Unicorn automatically inserts a subfield z in the Unicorn call number. Portions of the call number that follow a |z are considered analytic information, and are fully expanded to enhance sorting of call numbers. Analytic information is not displayed as part of the base call number that appears at the top of a single item view window. A |z can be manually inserted by a cataloger to improve sorting. In printing or displaying call numbers, |z is replaced with a space. Select a valid prefix from the drop-down list.
"Our LC.clas file contains all of the captions that we have added over the years. We use the same file for LC and LCPER class schemes. The prefix “NEW” had not been added to this list and that was what was causing the problem with the New Ser. Not working correctly. If for some reason, the class scheme in the properties were set to ALPHANUM or ASIS when the items are created, the subfield z will not be placed anywhere in the call number."
Preceding Year Part of Analytic
This attribute specifies whether the preceding year will be part of the analytic file prefix. If a Classification policy is defined to include preceding year, then after the analytic term is found by using the prefix file, the preceding call number characters are examined. If a two- or four-digit number or combination is found before the analytic term, the analytic subfield (|z) is inserted before the number. The following patterns are recognized as years.
99
1999
98/99
98-99
2001/2002
2001-2002
2001/02
2001-02
Example: The call number in the bibliographic record is as follows.
PN2312 .N37 2001-2002 PT. 2
When calculating the position in which to insert |z, if a Classification policy that includes preceding years is used, |z will be inserted as follows.
PN2132 .N37 |z2001-2002 PT. 2
If a Classification policy that does not include preceding years is used, |z will be inserted as follows.
PN2132 .N37 2001-2002 |zPT. 2
"Our LC class scheme policy does not include the preceding year as part of the analytic. The LCPER class scheme policy does include it. There is also a sort setting in each class scheme policy that tells it to sort ascending or descending. Our LC policy is set to ascending and the LCPER is set to descending. If you had a list of items with a mix of LC and LCPER classed items, this setting could also account for some of the sorting being incorrect."