Sorting LC call numbers with Cutter sometimes in $$a, sometimes $$b

• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
In the LC call number index (zone 090) we have the following series of call numbers which files correctly according to the tab_filing LC routine :

T805 1931 B1H64
T805 1931 C1C4
T805 1931 C1N53
T805 1931B1M67 2000

However, because sometimes the cutter is in the sub-field b and sometimes it is in the sub-field a we would like the data in the call number indexes to be treated as character strings with the spaces ignored.

So that the above series should file like this :

T805 1931 B1H64
T805 1931B1M67 2000
T805 1931 C1C4
T805 1931 C1N53


When testing with util F/1/3, we get this:

Enter Filing Procedure (Q to quit)
Enter values as defined in Col. 1 of tab_filing: 24
Enter values D/N/F or Space: f
Enter text (Q to quit) : T805 1931 B1H64
IN -T805 1931 B1H64 -
Load: /tmp/utf_files/exlibris/aleph/u20_2/uqm01/tab/tab_filing
Load: /exlibris/aleph/u20_2/alephe/unicode/unicode_case
OUT -t8051931b1h64

Enter text (Q to quit) : T805 1931 C1C4
IN -T805 1931 C1C4 -
OUT -t8051931c1c4 -
-
Enter text (Q to quit) : T805 1931 C1N53
IN -T805 1931 C1N53 -
OUT -t8051931c1n53 -

Enter text (Q to quit) : T805 1931B1M67 2000
IN -T805 1931B1M67 2000 -
OUT -t8051931b1m672000 -

Enter text (Q to quit) :

Subsequent sorting on the OUT values provided gives us, correctly, this:

t8051931b1h64
t8051931b1m672000
t8051931c1c4
t8051931c1n53

And yet this is not represented in the display in the GUI. How can we get the call numbers to sort the way we want in the GUI? See attached screenshot.

Is there a routine in tab_filing or some other file that must be modified that would do the job?

Resolution:
The following entry in tab_filing worked:

24 del_subfield
24 lc_call_no
24 to_lower
24 compress_blank

I suggest that you:

* change the tab_filing "24" to the above form,
* change the tab00.eng for the relevant indexes (LCC and LCCx?) to 24,
* test it with util f/1/3, and, if OK, then
* restart ue_01 and the pc_server.

Then resend records in a particular call number range to the server so they are reindexed and see if the order is satisfactory.

If so and if there are fewer than, say, 100,000 records with such numbers, you could use p_ret_01 to create a file with the Aleph document numbers for these records, which you could use as input to p_manage_40, which will create a z07 record for each, which will be processed by ue_01.

If there are more than 100,000 records with such a number, then you would need to rerun the Headings sequence of jobs.

• Article last edited: 10/8/2013