Relevance Ranking Context Set version 1.1Version 1.1, 2nd September 2009see also version 1.0 The default ordering of a result set is left up to the server, including a lack of any explicit ordering. This is addressed in SRU for the most part through the use of the 'sort' / 'sortKeys' parameter in SRU v1.1 and by the 'sortBy' keyword in SRU v1.2 queries. However,for sophisticated relevance based ranking, different algorithms are available, and specific methods might be requested to combine the results of evaluating each operand or clause. This context set attempts to address this issue by defining relation and boolean modifiers for the various known algorithms, and combinations of their results. Several known algorithms have their documentation linked in the table in Appendix A below. If the 'relevant' relation modifier from the cql context set is given, but no named algorithm, then the server should continue to use the basic semantics -- the server may decide which algorithm to use. It is also legal to include both cql.relevant along with an algorithm from this set, in which case that algorithm should be used. Hence there is no need to include an 'any algorithm' relation modifier in this set. Also, please note that, as with all context sets, these modifiers are case insensitive. "rel.algorithm=CORI" and "rel.algorithm=cori" are to be treated the same. This is especially true as most of the modifiers are acronyms so may be entered in upper case into queries, even though they are listed in lower case below. To return relevancy information attached to a record, please see the record metadata extension. (To be written up, ala 'rec' context set)
IndexesThere are no indexes defined in this context set.
RelationsThere are no relations defined in this context set.
Relation Modifiers
BooleansThere are no booleans defined in this context set.
Boolean Modifiers
ExamplesSome examples of how the context set might be used.
Appendix A - Relevance Score Assignment Algorithms
Appendix B - Relevance Score Combination Methods
|
December 16, 2015 |