Simple User Test Queries for Koha with Solr/Lucene

Common user queries specify no search options and would often need to be rewritten in the appropriate query language to return the result set intended by the user query. Furthermore, helpful default record indexing and query values need to be selected to support such queries.

Simple user queries do not specify Solr/Lucene syntax in the original user query, although, the rewriting of such queries by Koha may need to specify Solr/Lucene syntax. Solr/Lucene allows bare queries, therefore, some queries may resemble Solr/Lucene syntax queries. The most important simple user queries to test are ones which might be expected to not return an appropriate result set if not automatically rewritten as Solr/Lucene queries. Test queries explicitly written as Solr/Lucene queries belong in Solr/Lucene Test Queries for Koha but not here.

Add simple user test queries for particular expected record retrieval functionality.

Test queries have been organised for ensuring that we do not omit important types of queries. Please also help improve the organisation.

Some good test queries are needed to test each particular query feature in isolation. Real queries combine multiple query features into one query. Your test queries are welcome to combine query features. We need both query feature isolation test queries and query feature combination test queries.

We want your test queries. If you have trouble classifying your test query and have no time to improve the organisation, then please take a guess about where to add your query or add it to the unclassified issues table.

See Solr/Lucene Documentation for documentation of Solr/Lucene query syntax into which some simple user queries may need to be rewritten.

Relation Issues

Relevancy and Result Set Sort Order Issues

Topic	Query	Results	Development Status	Notes
Weightings ranking index match importance.	Gallimard	"Gallimard et la Suisse : un siècle d'affinités littéraires" sorted before a book merely published by Gallimard.		Staff should be able to specify default index weightings when specifying other parameters for indexes in the administrative interface.
Field or field part completeness match ranking.	It	"It / by Stephen King" sorted to the top of the result set before "It came from outer space".

Unclassified Issues

Topic	Query	Results	Development Status	Notes