You create an index definition for the collation key index you are creating. This 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 this index definition, you assign the index to a search option that displays in staff searching.
To create the index definition in the Table Editor
View: mq_index
Process: Administration\Index Control Menu\Indexes
1 | 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 vernacular titles, you may enter “vntitle.”) |
|||||||
Description |
Enter a description for the index. For example, if you are creating an index for vernacular titles, you may enter “Browse Vernacular Titles”. |
||||||
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 the source table for the raw data (the data you want to index). Typically, this will be either the bib or auth table depending on the type of MARC information you want to index. |
|||||||
Enter “text”. This is the column in either the auth or bib table where the index finds the raw data. You use the text column because it is the column in MARC-based tables that contains the text of the MARC tags and subfields. |
|||||||
Do one of these options:
This column is the link from the index to the source record that is indexed. |
|||||||
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. |
|||||||
Do one of these options:
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 option only if you are creating an authority-based index for authors. |
|||||||
Mark this option only if you are creating an authority-based index for subjects. |
|||||||
Mark this option only if you are creating an authority-based index for series. |
|||||||
Choose the 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. |
2 | Click Page Down. |
3 | In these fields, do the following: |
Field |
Action |
|||||||||
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 .) Note: You must enter a value in this field, or the index will not work. |
© 1998-2017 Sirsi Corporation