You must create two index definitions for a multiple-source collation key index. One index definition is for the bib table, and the other definition is for the auth table. Each index definition controls how the data is stored, what database table column stores the sorted data, the name of the index, and so forth. Once you create each index definition, you assign both of these indexes to one search option that displays in staff searching.
This section includes these topics:
• | Creating the bib Index Definition in the Table Editor |
• | Creating the auth Index Definition in the Table Editor |
Creating the bib Index Definition in the Table Editor
To create the bib index definition in the Table Editor
View: mq_index
Process: Administration\Index Control Menu\Indexes
➢ | In these fields, do the following: |
Field |
Action |
|||||||||
Enter a code for the index. This is the code you assign to a specific search option. (For example, if you are creating an index for a collation key uniform title, you may enter “ckbib.”) |
||||||||||
Description |
Enter a description for the index. For example, if you are creating an index for collation key uniform titles, you may enter “Collation Key (bib)”. |
|||||||||
Enter the name of the index table you created on the database. This is the table that will store the data. This is the index table you created by running the SQL script. (For more information, see Creating Database Objects for the Index .) |
||||||||||
Enter “sort_weight” as the sort column. This is the column in the new table that sorts the data. |
||||||||||
Enter “bib” as source table for the raw data (the data you want to index). |
||||||||||
Enter “text”. This is the column in the bib table where the index finds the raw data. You use the text column because it is the column in the bib table that contains the text of the MARC tags and subfields. |
||||||||||
Enter “bib#” as the column link from the index to the source record that is indexed. |
||||||||||
Leave this field blank. |
||||||||||
N_Keys Col. |
Leave this field blank. |
|||||||||
Do one of these options:
A MARC map “tells” Horizon what subfields to pull from which tags under specific conditions for processing and inserting the data into the index table. |
||||||||||
Mark this box. When you mark this, Horizon extracts and indexes only the result of the first tag in the MARC record. |
||||||||||
Ignore Spacer for Indexing |
Leave this box unmarked. |
|||||||||
Leave this box unmarked. |
||||||||||
Leave this box unmarked. |
||||||||||
Leave this box unmarked. |
||||||||||
Choose the Multi-Source Collation-Key option. The index type controls what algorithm Horizon uses as it indexes. |
||||||||||
Enter the “UcSrtWt” processor. Horizon uses this processor for unicode browse indexes. |
||||||||||
Note: The Staff-Only option is useful only if your library has public-only indexes defined. This is because both staff-only and combined indexes contain staff-only records. Only public-only entries filter out the staff-only records. |
||||||||||
Enter a “0” (zero) in this field. Horizon uses this value in Deferred Indexing. (For more information, see “Understanding Deferred Indexing” in the Cataloging Setup Guide.) |
||||||||||
Leave this box unmarked. Horizon uses this value in Deferred Indexing. |
||||||||||
Enter the number of bytes or characters on the database you want Horizon to sort. If you used an SQL script to create your index table on the database, you should enter 250. (For more information on the SQL script, see Creating Database Objects for the Index .) Important: You must enter a value in this field, or the index will not work. |
Creating the auth Index Definition in the Table Editor
To create the auth-based index definition
View: mq_index
Process: Administration\Index Control Menu\Indexes
➢ | In these fields, do the following: |
Field |
Action |
|||||||||
Enter a code for the index. This is the code you assign to a specific search option. (For example, if you are creating an index for a collation key uniform title, you may enter “ckauth.”) |
||||||||||
Description |
Enter a description for the index. For example, if you are creating an index for collation key uniform titles, you may enter “Collation Key (auth)”. |
|||||||||
Enter the name of the index table you created on the database. This is the table that will store the data. This is the index table you created by running the SQL script. (For more information, see Creating Database Objects for the Index . |
||||||||||
Enter “sort_weight” as the sort column. This is the column in the new table that sorts the data. |
||||||||||
Enter “auth” as source table for the raw data (the data you want to index). |
||||||||||
Enter “text”. This is the column in the auth table where the index finds the raw data. You use the text column because it is the column in the auth table that contains the text of the MARC tags and subfields. |
||||||||||
Enter “auth#” as the column link from the index to the source record that is indexed. |
||||||||||
Leave this field blank. |
||||||||||
N_Keys Col. |
Leave this field blank. |
|||||||||
Do one of these options:
A MARC map “tells” Horizon what subfields to pull from which tags under specific conditions for processing and inserting the data into the index table. |
||||||||||
Mark this box. When you mark this, Horizon extracts and indexes only the result of the first tag in the MARC record. |
||||||||||
Ignore Spacer for Indexing |
Leave this box unmarked. |
|||||||||
Mark this box. |
||||||||||
Leave this box unmarked. |
||||||||||
Leave this box unmarked. |
||||||||||
Choose the Multi-Source Collation-Key option. The index type controls what algorithm Horizon uses as it indexes. |
||||||||||
Enter the “UcSrtWt” processor. Horizon uses this processor for unicode browse indexes. |
||||||||||
Note: The Staff-Only option is useful only if your library has public-only indexes defined. This is because both staff-only and combined indexes contain staff-only records. Only public-only entries filter out the staff-only records. |
||||||||||
Enter a “0” (zero) in this field. Horizon uses this value in Deferred Indexing. (For more information, see “Understanding Deferred Indexing” in the Cataloging Setup Guide.) |
||||||||||
Leave this box unmarked. Horizon uses this value in Deferred Indexing. |
||||||||||
Enter the number of bytes or characters on the database that you want Horizon to sort. If you used an SQL script to create your index table on the database, you should enter 250. (For more information on the SQL script, see Creating Database Objects for the Index .) Important: You must enter a value in this field, or the index will not work. |
© 1998-2017 Sirsi Corporation