Difference between revisions of "Reference:BlueSpiceExtendedSearch"
m (→Further search possibilities) |
(Tag: 2017 source edit) |
Technical background[edit | edit source]
In order to activate the extended search, you will need an applications server like Apache running, otherwise MediaWiki's search function will be used. The search function is based on Apache Soir/Lucene.
Where can I find ExtendedSearch?[edit | edit source]ExtendedSearch is a special page. You will be redirected here when you do not find a suitable hit using the auto complete function.
You can find the search box above any article to the right. You can search for titles (use the arrow) or the full content (magnifying glass).

As you can see in the screenshot, search results are suggested to you as you type, and you can select these too. If none of these results is suitable, you are automatically taken to the search form for the ExtendedSearch. Here you can sort the search results and use facets to fileter them further.
You can also reach this search form by going to Special pages -> BlueSpice -> Extended Search. The "auto complete" function is deactivated here, otherwise it works just like the search box above the article.
What can ExtendedSearch do?[edit | edit source]With the improved search function from BlueSpice you can:
Extension: BlueSpiceExtendedSearch
Overview | |||
---|---|---|---|
Description: | Elasticsearch search backend | ||
State: | stable | Dependency: | BlueSpice |
Developer: | HalloWelt | License: |
GPL-3.0-onlyProperty "BSExtensionInfoLicense" (as page type) with input value "</br>GPL-3.0-only" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. |
Type: | BlueSpice | Category: | Search and Navigation |
Edition: | BlueSpice free, BlueSpice pro, BlueSpice Farm, BlueSpice Cloud | ||
Features
ExtendedSearch replaces the default MediaWiki search engine. It is based on ElasticSearch engine, and provides many improvements over the standard MediaWiki search both in terms of quality of indexed content and user interface.
- Search titles.
- Search the full content.
- Search uploaded or linked files (Office documents and PDFs).
- Search image data.
- Search-as-you-type and auto-complete
- .
- Ignore upper and lower case (case-insensitive).
- Search with the operators AND, OR, NOT.
- Search with wildcards
- .
- Search for phrases
- .
- Fuzzy search
- Sentence components which belong together will be found, like "computer keyboard"
Sorting results[edit | edit source]

The search results are initially sorted according to relevance. You can, however, sort them by title or type or chronologically. The criteria for sorting are shown in a block next to the results and can be chosen by clicking on them.
The current choice/sorting is highlighted in bold. The current sorting direction is shown with an arrow symbol behind the sort criterion and can be changed by clicking on it.
You can find links to further search results right at the bottom. These are shown in the following way: < 1 2 3 4 5 .. 66 > : the arrow to the right takes you to the next page. The current page is highlighted in bold.
Limit the search with facets[edit | edit source]

Category filter: The extended search lets you search within one category or a selection of them. You can also select particular categories which should be searched or blanked our in advance in the search settings (under "Preferences").
Type filter: This lets you filter whether you will search for or in wiki articles (shown as a W on a white background before the hit), for or in PDF, Word, EXCEL or other documents.
Author filter: You can give the author who, for example, you think may have written the article.
Tips for using the extended search[edit | edit source]
- Configure search: A wiki administrator can set up which filters can be chosen in the Preferences, and also which search function comes as default when a user presses enter.
- Personal search preferences: If you want to change the number of hits shown in a search, you can do this in your MediaWiki personal preferences. You can also change the lines per hit and the characters per line. But you can also change the standard namespaces for your searches here.
- So that your search delivers the appropriate results, the content must be regularly indexes (see below under Search administration). This normally occurs "on the fly", i.e. whenever there are new articles/files, changes to the content of articles, or an article is deleted or restored. In the indexing has not been done, searching will give no results. If the indexing is not up to date, new articles and files will not be able to be found.
- Anyone can search if they have read permission in the wiki. This means that results are only shown from namespaces in which the user has read permission. If you cannot find an article even though you know it exists, it may be that you do not have the relevant access permission. Permissions are set up via the PermissionManager.
- Even though the namespace "book" is marked as not searchable, content will be found from within it. "Not searchable" means, here, that the namespace is not searched by default. These standard settings can be overwritten in the user preferences. Whether a page is displayed as a hit depends on the readability of the page and not on the namespace's search settings.
Search administration[edit | edit source]
The following functions are available in the wiki admin area.
-
Search indexing
- Create new index: deletes the index and regenerates completely from now
- Overwrite index: generates a new index without deleting the old one
- Delete index
- Link to the statistics (statistics on search queries in the wiki). If you want statistics about search queries, then those queries made with the auto complete feature in the search box are not included.
- The number of hits shown per page can be set up at WikiAdmin->Preference->Search->LimitResultsDefault
- Weighting of search results: Administrators can prioritize namespaces for the search results. Just go to the namespace manager and mark the checkbox at “content namespace” for the namespace you want to prioritize. Contents of this namespace will be preferred in the search results
Further search possibilities[edit | edit source]
- ServiceCenter: Create a preconfigured search portal with a list of the top five results
- WikiExplorer: Filter metadata from the wiki to find articles using particular criteria.
Case study[edit | edit source]
Problems with the Extended Search
Extended Search stellt ohne Vorankündigung den Betrieb ein
- .
- Search for sentence fragments.
Some aspects of this extension can be configured on Special:BlueSpiceConfigManager, under section "ExtendedSearch". Here wiki administrators can configure:
- external file paths
- layout of the autocomplete box
- language filter
- exclude patterns
Configuration (server)
For boosting by match percent, the following settings are available in the extension itself: "ESMatchPercentBoostFactor": {
"description": "How much to boost the result based on the percent of its title taken up by the search term. Set to 0 to disable",
"public": false,
"value": "0.5"
},
"ESMatchPercentTitleField": {
"description": "Field on which to base the match percent boosting. If empty, default title field of the source will be used",
"public": false,
"value": ""
},
Description:
- ESMatchPercentBoostFactor: The value here is multiplied by the the match percent and by the score of the document. Example: The search term is "Test". The search finds for example "Testpage" and - let's say - assigns a score of 20 to this result. Your search term matches 50 percent of the found name, so its match factor is 0.5. This factor is then multiplied by the value in this setting (by default 0.5), which gives the total boost factor of 0.25. The final score is calculated as "original score + (original score * boost factor)" => 20 + (20 * 0.25 ) = 20 + 5 = 25. This means that because your search term matches 50% of the result, it got boosted by the factor of 5.
- ESMatchPercentTitleField: Field on which the match analysis is performed. Defaults to nothing, so whatever the search lookup sets. It can be set to "prefixed_text" to calculate match percent on the title with namespace prefix, for example, or to something like "basename" to calculate the match percent only on the page name, without the namespace prefix.
Technical Information[edit source]
This information applies to BlueSpice 3 . Technical details for BlueSpice cloud can differ in some cases.
Requirements[edit source]
- MediaWiki: 1.31
- BlueSpiceFoundation: 3.2
Integrates into[edit source]
- BlueSpiceArticleInfo
- BlueSpiceExtendedSearch
- BlueSpiceExtendedStatistics
- BlueSpicePrivacy
- BlueSpiceSimpleFarmer
- BlueSpiceTagCloud
- BlueSpiceVisualEditorConnector
- VisualEditor
Special pages[edit source]
- BSSearchAdmin
- BSSearchCenter
Permissions[edit source]
Name | Description | Role |
---|---|---|
extendedsearch-search-externalfile | Search for external files | accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager |
extendedsearch-search-repofile | Search for files | accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager |
extendedsearch-search-specialpage | Search for special pages | accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager |
extendedsearch-search-wikipage | Search for pages | accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager |
Configuration[edit source]
Name | Value |
---|---|
ESAllowIndexingDocumentsWithoutContent | true |
ESAutoRecognizeSubpages | true |
ESAutoSetLangFilter | false |
ESBackendClass | '\\BS\\ExtendedSearch\\Backend' |
ESBackendHost | '127.0.0.1' |
ESBackendPort | '9200' |
ESBackendTransport | 'http' |
ESCompactAutocomplete | false |
ESDefaultSearchOperator | 'AND' |
ESEnableSearchHistoryTracking | true |
ESEnableTypeFilter | true |
ESExternalFilePaths | array ( ) |
ESLookupModifierRegExPatterns | array ( 0 => '[0-9]{2}\\-[0-9]{2}\\-[0-9]{4}', 1 => '[0-9]{4}\\-[0-9]{2}\\-[0-9]{2}', 2 => '[0-9]{2}\\-[0-9]{4}\\-[0-9]{2}', 3 => '[0-9]{2}\\/[0-9]{2}\\/[0-9]{4}', 4 => '[0-9]{4}\\/[0-9]{2}\\/[0-9]{2}', 5 => '[0-9]{2}\\/[0-9]{4}\\/[0-9]{2}', 6 => '[0-9]{2}\\.[0-9]{2}\\.[0-9]{4}', 7 => '[0-9]{4}\\.[0-9]{2}\\.[0-9]{2}', 8 => '[0-9]{2}\\.[0-9]{4}\\.[0-9]{2}', 9 => '[0-9]{2}\\\\[0-9]{2}\\\\[0-9]{4}', 10 => '[0-9]{4}\\\\[0-9]{2}\\\\[0-9]{2}', 11 => '[0-9]{2}\\\\[0-9]{4}\\\\[0-9]{2}', 12 => '[0-9]{1}\\-[0-9]{2}\\-[0-9]{4}', 13 => '[0-9]{4}\\-[0-9]{2}\\-[0-9]{1}', 14 => '[0-9]{1}\\-[0-9]{4}\\-[0-9]{2}', 15 => '[0-9]{4}\\-[0-9]{1}\\-[0-9]{2}', 16 => '[0-9]{2}\\-[0-9]{4}\\-[0-9]{1}', 17 => '[0-9]{2}\\-[0-9]{1}\\-[0-9]{4}', 18 => '[0-9]{1}\\/[0-9]{2}\\/[0-9]{4}', 19 => '[0-9]{4}\\/[0-9]{2}\\/[0-9]{1}', 20 => '[0-9]{1}\\/[0-9]{4}\\/[0-9]{2}', 21 => '[0-9]{4}\\/[0-9]{1}\\/[0-9]{2}', 22 => '[0-9]{2}\\/[0-9]{4}\\/[0-9]{1}', 23 => '[0-9]{2}\\/[0-9]{1}\\/[0-9]{4}', 24 => '[0-9]{1}\\.[0-9]{2}\\.[0-9]{4}', 25 => '[0-9]{4}\\.[0-9]{2}\\.[0-9]{1}', 26 => '[0-9]{1}\\.[0-9]{4}\\.[0-9]{2}', 27 => '[0-9]{4}\\.[0-9]{1}\\.[0-9]{2}', 28 => '[0-9]{2}\\.[0-9]{4}\\.[0-9]{1}', 29 => '[0-9]{2}\\.[0-9]{1}\\.[0-9]{4}', 30 => '[0-9]{1}\\\\[0-9]{2}\\\\[0-9]{4}', 31 => '[0-9]{4}\\\\[0-9]{2}\\\\[0-9]{1}', 32 => '[0-9]{1}\\\\[0-9]{4}\\\\[0-9]{2}', 33 => '[0-9]{4}\\\\[0-9]{1}\\\\[0-9]{2}', 34 => '[0-9]{2}\\\\[0-9]{4}\\\\[0-9]{1}', 35 => '[0-9]{2}\\\\[0-9]{1}\\\\[0-9]{4}', 36 => '[0-9]{2}\\-[0-9]{2}\\-[0-9]{2}', 37 => '[0-9]{2}\\/[0-9]{2}\\/[0-9]{2}', 38 => '[0-9]{2}\\.[0-9]{2}\\.[0-9]{2}', 39 => '[0-9]{2}\\\\[0-9]{2}\\\\[0-9]{2}', 40 => '[0-9]{1}\\-[0-9]{1}\\-[0-9]{4}', 41 => '[0-9]{4}\\-[0-9]{1}\\-[0-9]{1}', 42 => '[0-9]{1}\\-[0-9]{4}\\-[0-9]{1}', 43 => '[0-9]{1}\\/[0-9]{1}\\/[0-9]{4}', 44 => '[0-9]{4}\\/[0-9]{1}\\/[0-9]{1}', 45 => '[0-9]{1}\\/[0-9]{4}\\/[0-9]{1}', 46 => '[0-9]{1}\\.[0-9]{1}\\.[0-9]{4}', 47 => '[0-9]{4}\\.[0-9]{1}\\.[0-9]{1}', 48 => '[0-9]{1}\\.[0-9]{4}\\.[0-9]{1}', 49 => '[0-9]{1}\\\\[0-9]{1}\\\\[0-9]{4}', 50 => '[0-9]{4}\\\\[0-9]{1}\\\\[0-9]{1}', 51 => '[0-9]{1}\\\\[0-9]{4}\\\\[0-9]{1}', 52 => '[0-9]{1}\\-[0-9]{1}\\-[0-9]{2}', 53 => '[0-9]{2}\\-[0-9]{1}\\-[0-9]{1}', 54 => '[0-9]{1}\\-[0-9]{2}\\-[0-9]{1}', 55 => '[0-9]{1}\\/[0-9]{1}\\/[0-9]{2}', 56 => '[0-9]{2}\\/[0-9]{1}\\/[0-9]{1}', 57 => '[0-9]{1}\\/[0-9]{2}\\/[0-9]{1}', 58 => '[0-9]{1}\\.[0-9]{1}\\.[0-9]{2}', 59 => '[0-9]{2}\\.[0-9]{1}\\.[0-9]{1}', 60 => '[0-9]{1}\\.[0-9]{2}\\.[0-9]{1}', 61 => '[0-9]{1}\\\\[0-9]{1}\\\\[0-9]{2}', 62 => '[0-9]{2}\\\\[0-9]{1}\\\\[0-9]{1}', 63 => '[0-9]{1}\\\\[0-9]{2}\\\\[0-9]{1}', 64 => '[0-9]{2}\\-[0-9]{4}', 65 => '[0-9]{2}\\/[0-9]{4}', 66 => '[0-9]{2}\\.[0-9]{4}', 67 => '[0-9]{2}\\\\[0-9]{4}', 68 => '[0-9]{4}\\-[0-9]{2}', 69 => '[0-9]{4}\\/[0-9]{2}', 70 => '[0-9]{4}\\.[0-9]{2}', 71 => '[0-9]{4}\\\\[0-9]{2}', 72 => '[0-9]{2}\\-[0-9]{2}', 73 => '[0-9]{2}\\/[0-9]{2}', 74 => '[0-9]{2}\\.[0-9]{2}', 75 => '[0-9]{2}\\\\[0-9]{2}', ) |
ESMatchPercentBoostFactor | '0.5' |
ESMatchPercentTitleField | '' |
ESOfferOperatorSuggestion | true |
ESRecentBoostFactor | '0.5' |
ESSearchCenterDefaultFilters | array ( 0 => 'namespace_text', 1 => 'categories', ) |
ESSearchInRawWikitext | true |
ESSourceConfig | array ( 'wikipage' => array ( 'skip_namespaces' => array ( 0 => 8, 1 => 9, ), ), 'repofile' => array ( 'extension_blacklist' => array ( 0 => 'mp4', ), 'max_size' => 20000000, ), 'externalfile' => array ( 'extension_blacklist' => array ( 0 => 'mp4', ), 'max_size' => 20000000, ), ) |
ESWildcardingOperators | array ( 0 => '+', 1 => '|', 2 => '*', 3 => '(', 4 => ')', 5 => '~', ) |
ESWildcardingSeparators | array ( 0 => ',', 1 => '.', 2 => ';', 3 => '-', 4 => '_', ) |
ExtendedSearchExternalFilePathsExcludes | array ( ) |
TagSearchSearchFieldTemplatePath | '/resources/templates' |
API Modules[edit source]
- bs-extendedsearch-autocomplete
- bs-extendedsearch-query
- bs-extendedsearch-resultrelevance
- bs-extendedsearch-stats
- bs-extendedsearch-triggerupdate
- bs-extendedsearch-type-store
Hooks[edit source]
__NOTOC__ BlueSpice has a superior, better organised search function than MediaWiki. This function is able to search for articles and attachments according to both title and content. The first hits are shown as you are typing the search term into the box. If you do not get a suitable hit straight away, the search results can be refined by using facets. On top of this, the search function can be expanded by further packages to extend its functionality (see below). ==Technical background== In order to activate the extended search, you will need an applications server like Apache running, otherwise MediaWiki's search function will be used. The search function is based on Apache Soir/Lucene. ==Where can I find ExtendedSearch?== ExtendedSearch is a special page. You will be redirected here when you do not find a suitable hit using the auto complete function. You can find the search box above any article to the right. You can search for titles (use the arrow) or the full content (magnifying glass). [[File:BlueSpice223-Autocomplete-en.png|thumb|none|400px|Screenshot: The first results start to appear as soon as you start to type in the query]] As you can see in the screenshot, search results are suggested to you as you type, and you can select these too. If none of these results is suitable, you are automatically taken to the search form for the ExtendedSearch. Here you can sort the search results and use facets to fileter them further. You can also reach this search form by going to Special pages -> BlueSpice -> Extended Search. The "auto complete" function is deactivated here, otherwise it works just like the search box above the article. ==What can ExtendedSearch do?== With the improved search function from BlueSpice you can: * '''Search titles''': Search in a selection of areas only according to title. If the search term fully matches an existing article, you will be forwarded to it (this can be activated and deactivated). Search by title by using the arrow button to the right of the search box. * '''{{BSExtensionInfo |desc=Full-text search in articles and files, faceted search, fuzzy search, spellchecker and sorting as well as search-as-you-type and auto-complete functionality. |status=stable |developer=HalloWelt |type=BlueSpice |edition=BlueSpice free, BlueSpice pro, BlueSpice Farm, BlueSpice Cloud |compatible=BlueSpice |category=Search and Navigation |license=GPL v3 only |features='''ExtendedSearch''' replaces the default MediaWiki search engine. It is based on ElasticSearch engine, and provides many improvements over the standard MediaWiki search both in terms of quality of indexed content and user interface. *Search titles. *Search the full content''': Search the complete content in a selection of areas. This is done by using the magnifying glass button to the right of the search box. * Search '''. *Search uploaded or linked files''' (Office documents and PDFs). * *Search image data * '''. *Search-as-you-type''' and '''auto-complete''': As soon as you start typing a search term into the box at the top right, the system starts searching and giving you relevant suggestions. These suggestions are shown in a drop-down menu below the entry box and you can choose individual suggestions by clicking on them. This forwards you to the article named. This function is particularly good for locating articles with long titles or subpages. <br/>If the search term is not found automatically, the menu immediately gives you the possibilities "Suggest article" and "Create article". * Ignore '''. *Ignore upper and lower case''' (case-insensitive). <br/>Example: Searching for "keyboard" gives the same results as for "Keyboard". * *Search with the operators '''AND, OR, NOT'''. <br/>Example: Searching for "keyboard OR keypad" gives results which contain at least one of these two terms. * Search with '''wildcards''': ** <nowiki>*</nowiki>(the star replaces an arbitrary number of characters). This allows you to truncate your search terms to the left or to the right. This means you can search for "User*" (trunkated to the right) or "*preferences" (truncated to the left). ** ''?'' (the question mark replaces a single letter) * '''Search for phrases''' (filter according to author, category and namespace). * '''Fuzzy search''': this means that imprecise search entries (for example typing mistakes) suck as ''keyboarrd'' will be found and a corrected version will be suggested to you. * '''Sentence components''' which belong together will be found, like ''"computer keyboard"'' ==What can I do with the search results?== ===Sorting results=== [[File:BlueSpice2-Suche-Sortierung-en.png|thumb|none|700px|Screenshot: The display of the search results showing the possibile sorting criteria.]] The search results are initially sorted according to relevance. You can, however, sort them by title or type or chronologically. The criteria for sorting are shown in a block next to the results and can be chosen by clicking on them. The current choice/sorting is highlighted in bold. The current sorting direction is shown with an arrow symbol behind the sort criterion and can be changed by clicking on it. You can find links to further search results right at the bottom. These are shown in the following way: < 1 2 3 '''4''' 5 .. 66 > : the arrow to the right takes you to the next page. The current page is highlighted in bold. ===Limit the search with facets=== [[File:BlueSpice2-Suche-Facetten-en.png|thumb|left|220px|Screenshot: Filter (facet) selection in ExtendedSerach]]You can further restrict the search results by using facets (filters) which you can find on the left hand side. The following facets are available: * '''Namespace filter''': You can restrict your search to one namespace or a selection of several. You can also select particular namespaces which should be searched or blanked our in advance in the search settings (under "Preferences"). <br/><br/> * '''Category filter''': The extended search lets you search within one category or a selection of them. You can also select particular categories which should be searched or blanked our in advance in the search settings (under "Preferences"). <br/><br/> * '''Type filter''': This lets you filter whether you will search for or in wiki articles (shown as a W on a white background before the hit), for or in PDF, Word, EXCEL or other documents. <br /><br /> * '''Author filter''': You can give the author who, for example, you think may have written the article. <br /><br /> <br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /> ==Tips for using the extended search== * '''Configure search''': A wiki administrator can set up which filters can be chosen in the [[Preferences]], and also which search function comes as default when a user presses enter. * '''Personal search preferences''': If you want to change the number of hits shown in a search, you can do this in your MediaWiki personal preferences. You can also change the lines per hit and the characters per line. But you can also change the standard namespaces for your searches here. * So that your search delivers the appropriate results, the '''content must be regularly indexes''' (see below under Search administration). This normally occurs "on the fly", i.e. whenever there are new articles/files, changes to the content of articles, or an article is deleted or restored. In the indexing has not been done, searching will give no results. If the indexing is not up to date, new articles and files will not be able to be found. * Anyone can search if they have '''read permission in the wiki'''. This means that results are only shown from namespaces in which the user has '''read''' permission. If you cannot find an article even though you know it exists, it may be that you do not have the relevant access permission. Permissions are set up via the [[PermissionManager]]. * Even though the namespace "book" is marked as not searchable, content will be found from within it. "'''Not searchable'''" means, here, that the namespace is not searched by default. These standard settings can be overwritten in the user preferences. Whether a page is displayed as a hit depends on the readability of the page and ''not'' on the [[NamespaceManager|namespace's search settings]]. ==Search administration== The following functions are available in the wiki admin area. * [[SearchOptions|Search indexing]] ** Create new index: deletes the index and regenerates completely from now ** Overwrite index: generates a new index without deleting the old one ** Delete index * Link to the statistics (statistics on search queries in the wiki). If you want statistics about search queries, then those queries made with the auto complete feature in the search box are not included. * The number of hits shown per page can be set up at WikiAdmin->Preference->Search->LimitResultsDefault * Weighting of search results: Administrators can prioritize namespaces for the search results. Just go to the [[NamespaceManager|namespace manager]] and mark the checkbox at “content namespace” for the namespace you want to prioritize. Contents of this namespace will be preferred in the search results ==Further search possibilities== * [[ServiceCenter]]: Create a preconfigured search portal with a list of the top five results * [[WikiExplorer]]: Filter metadata from the wiki to find articles using particular criteria. [[Category:Extension]] [[Category:BlueSpice_free]] [[Category:BlueSpice_docu]] [[Category:BlueSpice_public]] ==Case study== [http://sourceforge.net/p/bluespice/bugs/227/ Problems with the Extended Search] [http://sourceforge.net/p/bluespice/bugs/235/ Extended Search stellt ohne Vorankündigung den Betrieb ein]. *Search with wildcards. *Search for phrases. *Fuzzy search. *Search for sentence fragments. Some aspects of this extension can be configured on [[Special:BlueSpiceConfigManager]], under section "ExtendedSearch". Here wiki administrators can configure: *external file paths *layout of the autocomplete box *language filter *exclude patterns ===Configuration (server)=== For boosting by match percent, the following settings are available in the extension itself:<syntaxhighlight lang="json"> "ESMatchPercentBoostFactor": { "description": "How much to boost the result based on the percent of its title taken up by the search term. Set to 0 to disable", "public": false, "value": "0.5" }, "ESMatchPercentTitleField": { "description": "Field on which to base the match percent boosting. If empty, default title field of the source will be used", "public": false, "value": "" }, </syntaxhighlight> Description: *'''ESMatchPercentBoostFactor''': The value here is multiplied by the the match percent and by the score of the document. Example: The search term is "Test". The search finds for example "Testpage" and - let's say - assigns a score of 20 to this result. Your search term matches 50 percent of the found name, so its match factor is 0.5. This factor is then multiplied by the value in this setting (by default 0.5), which gives the total boost factor of 0.25. The final score is calculated as "original score + (original score * boost factor)" => 20 + (20 * 0.25 ) = 20 + 5 = 25. This means that because your search term matches 50% of the result, it got boosted by the factor of 5. *'''ESMatchPercentTitleField:''' Field on which the match analysis is performed. Defaults to nothing, so whatever the search lookup sets. It can be set to "prefixed_text" to calculate match percent on the title with namespace prefix, for example, or to something like "basename" to calculate the match percent only on the page name, without the namespace prefix. }}
(47 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{BSExtensionInfo | |
+ | |desc=Full-text search in articles and files, faceted search, fuzzy search, spellchecker and sorting as well as search-as-you-type and auto-complete functionality. | ||
+ | |status=stable | ||
+ | |developer=HalloWelt | ||
+ | |type=BlueSpice | ||
+ | |edition=BlueSpice free, BlueSpice pro, BlueSpice Farm, BlueSpice Cloud | ||
+ | |compatible=BlueSpice | ||
+ | |category=Search and Navigation | ||
+ | |license=GPL v3 only | ||
+ | |features='''ExtendedSearch''' replaces the default MediaWiki search engine. It is based on ElasticSearch engine, and provides many improvements over the standard MediaWiki search both in terms of quality of indexed content and user interface. | ||
− | + | *Search titles. | |
+ | *Search the full content. | ||
+ | *Search uploaded or linked files (Office documents and PDFs). | ||
+ | *Search image data. | ||
+ | *Search-as-you-type and auto-complete. | ||
+ | *Ignore upper and lower case (case-insensitive). | ||
+ | *Search with the operators AND, OR, NOT. | ||
+ | *Search with wildcards. | ||
+ | *Search for phrases. | ||
+ | *Fuzzy search. | ||
+ | *Search for sentence fragments. | ||
− | + | Some aspects of this extension can be configured on [[Special:BlueSpiceConfigManager]], under section "ExtendedSearch". Here wiki administrators can configure: | |
− | |||
− | + | *external file paths | |
− | + | *layout of the autocomplete box | |
+ | *language filter | ||
+ | *exclude patterns | ||
− | + | ===Configuration (server)=== | |
+ | For boosting by match percent, the following settings are available in the extension itself:<syntaxhighlight lang="json"> | ||
+ | "ESMatchPercentBoostFactor": { | ||
+ | "description": "How much to boost the result based on the percent of its title taken up by the search term. Set to 0 to disable", | ||
+ | "public": false, | ||
+ | "value": "0.5" | ||
+ | }, | ||
+ | "ESMatchPercentTitleField": { | ||
+ | "description": "Field on which to base the match percent boosting. If empty, default title field of the source will be used", | ||
+ | "public": false, | ||
+ | "value": "" | ||
+ | }, | ||
+ | </syntaxhighlight> | ||
− | |||
− | + | Description: | |
− | + | *'''ESMatchPercentBoostFactor''': The value here is multiplied by the the match percent and by the score of the document. Example: The search term is "Test". The search finds for example "Testpage" and - let's say - assigns a score of 20 to this result. Your search term matches 50 percent of the found name, so its match factor is 0.5. This factor is then multiplied by the value in this setting (by default 0.5), which gives the total boost factor of 0.25. The final score is calculated as "original score + (original score * boost factor)" => 20 + (20 * 0.25 ) = 20 + 5 = 25. This means that because your search term matches 50% of the result, it got boosted by the factor of 5. | |
− | + | *'''ESMatchPercentTitleField:''' Field on which the match analysis is performed. Defaults to nothing, so whatever the search lookup sets. It can be set to "prefixed_text" to calculate match percent on the title with namespace prefix, for example, or to something like "basename" to calculate the match percent only on the page name, without the namespace prefix. | |
− | |||
− | + | }} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |