CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

« Previous - Version 20/84 (diff) - Next » - Current version
Ingo Renner, 2010-09-14 12:33
updated faceting.sortBy


tx_solr.search

The search section, you probably already guessed it, provides configuration options for the all things related to actually searching the index, setting query parameters, formatting and processing result documents and the result listing.

filter

Since: 1.0
Default:
Type: String

Adds additional parameters to the search initialization.

targetPage

Since: 1.0
Default: 0
Type: Integer

Sets the target page ID for links. If it is empty or 0, the current page ID will be used.

allowEmptyQuery

Since: 1.0
Default: 0
Options: 0,1
Type: Boolean

If enabled, empty queries are allowed.

form

Since: 1.0
Default: simple
Type: String

Sets the form style.

query

The query sub-section defines a few query parameters for the query that will be sent to the Solr server later on. Some query parameters are also generated and set by the extension itself, f.e. when using facets.

query.fields

Since: 1.0
Default: content^40.0, title^5.0, keywords^2.0, tagsH1^5.0, tagsH2H3^3.0, tagsH4H5H6^2.0, tagsInline^1.0
Type: String

Defines what fields to search in the index. Fields are defined as a comma separated list. Each field can be given a boost by appending the boost value separated by the ^ character, that's Lucene query language. The boost value itself is a float value, pay attention to using a dot as the separator for the fractions. Use this option to add more fields to search.

The boost take influence on what score a document gets when searching and thus how documents are ranked and listed in the search results. A higher score will move documents up in the result listing. The boost is a multiplier for the original score value of a document for a search term.

By default if a search term is found in the content field the documents gets scored / ranked higher as if a term was found in the title or keywords field. Although the default should provide a good setting, you can play around with the boost values to find the best ranking for your content.

query.minimumMatch

Since: 1.2 2.0
Default: (empty)
See: http://wiki.apache.org/solr/DisMaxRequestHandler#mm_.28Minimum_.27Should.27_Match.29
Type: String

Sets the minimum match mm query parameter.
By default the mm query parameter is set in solrconfig.xml as 2<-35%. This means that for queries with less than three words they all must match the searched fields of a document. For queries with three or more words at least 65% of them must match rounded up.

Please consult the link to the Solr wiki for a more detailed description of the mm syntax.

query.boostFunction

Since: 1.2 2.0
Default: (empty)
See: http://wiki.apache.org/solr/DisMaxRequestHandler#bf_.28Boost_Functions.29
Type: String

Sets the boost function bf query parameter.
Allows to further manipulate the score of a document by using mathematical functions and field values of the current document.
A common use case for boost functions is to rank newer documents higher than older ones.

Please consult the link to the Solr wiki for a more detailed description of boost functions.

results

results.resultsPerPage

Since: 1.0
Default: {$plugin.tx_solr.search.results.resultsPerPage}
Type: Integer

Sets the number of shown results per page.

results.resultsPerPageSwitchOptions

Since: 1.0
Default: 10, 20, 30, 50
Type: String

Defines the shown options of possible results per page.

results.fieldProcessingInstructions

Since: 1.0
Options: timestamp, utf8Decode, skip
Type: cObject

Mapping of fieldname to processing instructions. Available instructions: timestamp, utf8Decode, skip (removes the field from the result).

results.fieldRenderingInstructions

Since: 1.0
Type: cObject

Additional rendering instructions for specified fields.

results.pagebrowser.templateFile

Since: 1.0
Default: EXT:solr/resources/templates/pi_results/pagebrowser.htm
Type: String

Defines the template used for the pagebrowser.

results.ignorePageBrowser

Since: 1.0
Default: 0
Options: 0,1
Type: Boolean

If enabled, the selected page will be ignored an results by the first record.

results.showDocumentScoreAnalysis

Since: 2.0
Default: 0
Options: 0,1
Type: Boolean

If enabled, the analysis and display of the score analysis for logged in backend users will be initialized.

highlighting

highlighting.highlightFields

Since: 1.0
Default: title,content
Type: String

Should be a comma- or space-delimited list of fields to generate highlighted snippets for.

highlighting.fragmentSize

Since: 1.0
Default: 200
Type: Integer

The size, in characters, of fragments to consider for highlighting. "0" indicates that the whole field value should be used (no fragmenting).

highlighting.wrap

Since: 1.0
Default: <span class="results-highlight">|</span>
Type: String

This is used to format the highlighted parts.

spellchecking

spellchecking.wrap

Since: 1.0
Default: |<div class="spelling-suggestions">###LLL:didYouMean### |</div>|
Type: String

This is used to format spelling suggestions.

lastSearches

lastSearches.limit

Since: 1.0
Default: 10
Type: Integer

Defines the number of last searches, that should get minded.

lastSearches.mode

Since: 1.0
Default: user
Options: user, global
Type: String

If mode is user, keywords will get stored into the session. If mode is global keywords will get stored into the database.

commonTerms

commonTerms.minSize

Since: 1.0
Default: 14
Type: Integer

The difference between commonTerms.maxSize and commonTerms.minsize is getting used for calculating the current step.

commonTerms.maxSize

Since: 1.0
Default: 32
Type: Integer

The difference between commonTerms.maxSize and commonTerms.minsize is getting used for calculating the current step.

commonTerms.limit

Since: 1.0
Default: 20
Type: Integer

Defines the maximum size of the list by commonTerms.select.

commonTerms.select

Since: 1.0
Type: cObject

Defines a database connection for retrieving statistics.

sorting

sorting.defaultOrder

Since: 1.0
Default: ASC
Options: ASC, DESC
Type: String

Sets the order of sortings.

sorting.fields

sorting.fields.relevancy.label

Since: 1.0
Default: sorting_relevancy
Type: String

Defines the name of the relevancy label.

sorting.fields.sortTitle.label

Since: 1.0
Default: sorting_title
Type: String

Defines the name of the title label.

sorting.fields.type.label

Since: 1.0
Default: sorting_type
Type: String

Defines the name of the type label.

sorting.fields.sortAuthor.label

Since: 1.0
Default: sorting_author
Type: String

Defines the name of the author label.

sorting.fields.created.label

Since: 1.0
Default: sorting_created
Type: String

Defines the name of the created label.

faceting

faceting.minimumCount

Since: 1.0
Default: 1
Type: Integer
See: http://wiki.apache.org/solr/SimpleFacetParameters#facet.mincount

This indicates the minimum counts for facet fields should be included in the response.

faceting.sortBy

Since: 1.0
Default: count
Options: count, index, 1, 0, true, false, alpha (1.2, 2.0), lex (1.2, 2.0)
See: http://wiki.apache.org/solr/SimpleFacetParameters#facet.sort
Type: String

Defines how facet options are sorted, by default they are sorted by count of results, highest on top. count, 1, true are aliases for each other.
Facet options can also be sorted alphabetically (lexicographic by indexed term) by setting the option to index. index, 0, false, alpha (from version 1.2 and 2.0), and lex (from version 1.2 and 2.0) are aliases for index.

faceting.limit

Since: 1.0
Default: 10
See: http://wiki.apache.org/solr/SimpleFacetParameters#facet.limit
Type: Integer

This indicates the maximum number of constraint counts that should be returned for the facet fields. A negative value means unlimited.

faceting.singleFacetMode

Since: 1.0
Default: 0
Options: 0,1
Type: Boolean

If it is disabled, the filter GET parameters will be decoded and added to the facet.

faceting.facets

Since: 1.0
Default: type, author
See: http://wiki.apache.org/solr/SolrFacetingOverview
Type: cObject

Defines on which fields you want to facet. It's a list of facet configurations.

 1 plugin.tx_solr.search.faceting.facets {
 2     // type is the name of the facet configuration, you can choose whatever name
 3   type {
 4     field = type // the index field you want to create a facet from
 5     label = Content Type // a label
 6     limit = 10 // only show the first 10 facet options, if there are more options they will be folded
 7     sortBy = index // sorte the facet options alphabetically, otherwise they are sorted by count, options with more results on top
 8 
 9     keepAllOptionsOnSelection = 1 // if set allows to choose more than one option from this facet
10     operator = OR // used in combination with keepAllOptionsOnSelection to set how multiple options from one facet are combined, can also be AND
11     selectingSelectedFacetOptionRemovesFilter = 1 // boolean; if enabled, the facet options behave like switches. On first selection they add the filter for the facet option, on a second click they will remove the filter again. Currently requires keepAllOptionsOnSelection to be set to use this.
12   }
13 
14   myOtherFacet {
15     ...
16   }
17 }

faceting.removeFacetLinkText

Since: 1.0
Default: @facetText (remove)
Type: String

Defines the text for a link used for removing a given facet from the search results.

faceting.showAllLink.wrap

Since: 1.0
Default: <li>|</li>
Type: String

Defines the output of the "Show more" link, that is rendered if there are more facets given than set by faceting.limit.
Type: String