documentation:indexing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
documentation:indexing [2012/10/17 09:39] – [Normalization Functions] typo fix csharp | documentation:indexing [2016/07/27 09:39] – [Field Aliases] rjs7 | ||
---|---|---|---|
Line 100: | Line 100: | ||
</ | </ | ||
- | Each indexed datum coming from a bibliographic record in Evergreen is extracted based on an Indexed Field Definition. | + | Each indexed datum coming from a bibliographic record in Evergreen is extracted based on an Indexed Field Definition. |
==== Field Class ==== | ==== Field Class ==== | ||
Line 111: | Line 111: | ||
Indexed data from different fields will probably be considered to have different importance when calculating the relevance of a matched query term. For instance, a match in a translated title may be considered less important than a match in the title proper. | Indexed data from different fields will probably be considered to have different importance when calculating the relevance of a matched query term. For instance, a match in a translated title may be considered less important than a match in the title proper. | ||
- | By supplying a higher or lower relative **weight**, one field can be made more or less important, in relevance ranking terms, than others. | + | By supplying a higher or lower relative **weight**, one field can be made more or less important, in relevance ranking terms, than others. |
Evergreen ships with all Indexed Field Definition weights set to 1 by default. | Evergreen ships with all Indexed Field Definition weights set to 1 by default. | ||
Line 163: | Line 163: | ||
First, these aliases provide a mechanism for internationalizing the user-supplied search constraints; | First, these aliases provide a mechanism for internationalizing the user-supplied search constraints; | ||
- | In a similar manner, aliases can be used to map [[http:// | + | In a similar manner, aliases can be used to map [[http:// |
Line 193: | Line 193: | ||
Data extracted from bibliographic record, for indexing purposes, will normally require some normalization. | Data extracted from bibliographic record, for indexing purposes, will normally require some normalization. | ||
- | Normalizer functions are in-database | + | Normalizer functions are in-database |
Twelve normalizer functions are registered in the stock Evergreen installation. | Twelve normalizer functions are registered in the stock Evergreen installation. | ||
Line 203: | Line 203: | ||
|ISBN 10/13 conversion|Translate ISBN10 to ISBN13, and vice versa, for indexing purposes.| | |ISBN 10/13 conversion|Translate ISBN10 to ISBN13, and vice versa, for indexing purposes.| | ||
|Left truncation|Discard the specified number of characters from the left side of the string.| | |Left truncation|Discard the specified number of characters from the left side of the string.| | ||
- | |NACO Normalize|Apply NACO normalization rules to the extracted text. See http:// | + | |NACO Normalize|Apply NACO normalization rules to the extracted text. See https:// |
- | |NACO Normalize -- retain first comma|Apply NACO normalization rules to the extracted text, retaining the first comma. | + | |NACO Normalize -- retain first comma|Apply NACO normalization rules to the extracted text, retaining the first comma. |
|Normalize date range|Split date ranges in the form of " | |Normalize date range|Split date ranges in the form of " | ||
|Replace|Replace all occurances of first parameter in the string with the second parameter.| | |Replace|Replace all occurances of first parameter in the string with the second parameter.| |
documentation/indexing.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1