- Article Type: General
- Product: Aleph
- Product Version: 18.01
Can more information be provided on the changes in the lc_call_no filing routine (version 18 rep_change 478)? How does lc_call_no_2 differ?
The changes to the lc_call_no filing routine affect *only* call numbers which begin with numbers. Of course, *most* call numbers going through the lc_call_no routine are actual LC call numbers -- which begin with letters, rather than numbers. So these rep_changes apply only to call number indexes containing a mixture of LC numbers and non-LC numbers where the lc_call_no routine is specified as a filing routine.
Prior to version 18 rep_change 30 [16.02 rc 1582, 17.01 rc 651] call numbers beginning with numbers which went through the lc_call_no filing routine had special filing characters (# ! ") inserted (just as the first number part of regular LC numbers have special characters inserted) so that the digits preceding any letter, space, or decimal were treated as whole numbers.
With version 18 rep_change 30 [16.02 rc 1582; 17.01 rc 651] call numbers beginning with numbers which went through the lc_call_no filing routine did not have special filing characters (# ! ") inserted. (This was done because the special characters at the beginning of the number caused problems in linking.) This meant that they were filed as decimals.
With version 18 rep_change 478 [16.02 rc 1844; 17.01 rc 879], the lc_call_no routine reverts to its pre-rc 30 [16.02, pre-1582; 17.01, pre-651] state in which call numbers beginning with numbers which go through the lc_call_no filing routine have special filing characters inserted.
And the version of lc_call_no with special characters omitted for call#s beginning with numbers becomes lc_call_no_2.
faq, lc call number, tab_filing
- Article last edited: 10/8/2013