Help:CirrusSearch/de

CirrusSearch is a new search engine for MediaWiki. The Wikimedia Foundation is migrating to CirrusSearch since it features key improvements over the previously used search engine, LuceneSearch. Diese Seite beschreibt die Merkmale, die sich gegenüber früheren Lösungen verändert haben.

Häufig gestellte Fragen
Falls deine Frage hier nicht beantwortet wird, stelle sie auf der Diskussionsseite. Jemand wird dir dann darauf antworten.

Was wurde verbessert?
Die neue Suchmaschine weist drei wesentliche Verbesserungen gegenüber der alten Suchmaschine auf, namentlich:


 * Bessere Unterstützung für Suchanfragen in unterschiedlichen Sprachen.
 * Schnellere Aktualisierungen für den Suchindex, d. h. Änderungen an Artikeln werden viel schneller in den Suchergebnissen sichtbar.
 * Expandieren von Vorlagen, d. h. der gesamte Vorlageninhalt von Artikeln wird in den Suchergebnissen angezeigt.

Aktualisierungen
Der Suchindex wird nahezu in Echtzeit aktualisiert. Du solltest nach deinen Änderungen suchen können, sobald du sie gemacht hast. Veränderungen an Templates sollten in den Artikeln, die sie enthalten, innerhalb von "Minuten" wirksam werden Da Veränderungen an Templates in einer Warteliste abgearbeitet werden, kann die Performance variieren. Ein null edit an dem Artikel wird die Veränderung erzwingen, dies sollte aber, wenn alles normal verläuft, nicht nötig sein.

Suchvorschläge
Wenn du etwas in das Suchfeld eingibst, das dir mögliche Seiten zur Auswahl gibt, dann sind die Ergebnisvorschläge, die du erhältst, inhaltlich dieselben wie die Artikel, sortiert nach der Anzahl der eingehenden Links. Anzumerken ist, dass, wenn du deine Suche mit ~ beginnst, keine Artikel gefunden werden während du schreibst, und du gefahrlos zu jeder Zeit die Eingabetaste drücken kannst, um auf die Ergebnisseite zu kommen.

ASCII/accents/diacritics folding is turned on for English text, but there are some formatting problems with the result. See 52656.

Volltextsuche
Die Volltextsuche (die die Seite mit den Suchergebnissen für dich produziert) sucht in Titeln, Weiterleitungen, Überschriften und im Artikeltext und sollte keine Überraschungen mit sich bringen. Der große Unterschied ist hier, dass Vorlagen expandiert werden.

Stemming
There is support for dozens of languages, but all languages are wanted. There is a list of currently supported languages at elasticsearch.org; see their documentation on contributing to submit requests or patches.

Filters (intitle:, incategory: and linksto:)


Wir haben hier die Syntax ganz ordentlich gestrafft.


 * intitle:foo
 * Findet Artikel, deren Titel foo enthält. 'Stemming' für foo ist aktiviert.
 * intitle:"foo bar"
 * Findet Artikel, deren Titel foo und bar enthält. 'Stemming' für foo und bar ist aktiviert.
 * intitle:foo bar
 * Findet Artikel deren Titel foo enthält und deren Titel oder Text bar enthält.
 * -intitle:foo bar
 * Findet Artikel, deren Titel nicht foo enthält und deren Titel oder Text bar enthält.
 * intitle: foo bar
 * Syntax error, devolves into searching for articles whose title or text contains intitle:, foo, and bar.
 * incategory:Musik
 * Findet Artikel aus der Kategorie:Musik
 * incategory:"Musik Geschichte"
 * Findet Artikel aus der Kategorie:Musik_Geschichte
 * incategory:"musicals" incategory:"1920"
 * Find articles that are in both Category:Musicals and Category:1920
 * -incategory:"musicals" incategory:"1920"
 * Find articles that are not in Category:Musicals but are in Category:1920
 * cow*
 * Find articles whose title or text contains words that start with cow
 * linksto:Help:CirrusSearch
 * find articles that link to a page
 * -linksto:Help:CirrusSearch CirrusSearch
 * find articles that mention CirrusSearch but do not link to the page Help:CirrusSearch

prefix:
Auf der Syntax für prefix: in ihrer heutigen Form baut ein ganzes Bündel Funktionalitäten auf, deshalb ist sie so genau wie möglich wiedererschaffen (recreated) worden.


 * prefix:cow
 * Findet Artikel in inhaltlichen Namensräumen, deren Titel mit dem Wort "cow" beginnt.
 * domestic prefix:cow
 * Findet Artikel in inhaltlichen Namensräumen, deren Titel mit dem Wort "cow" beginnt und die das Wort "domestic" enthalten.
 * domestic prefix:Cow/
 * Findet alle Unterseiten des Artikels "Cow" in inhaltlichen Namensräumen, die das Wort "domestic" enthalten. Das ist eine weitverbreitete Suche, und häufig wird sie mit Hilfe des URL Parameters namens  zusammengestellt.
 * domestic prefix:Talk:Cow/
 * Findet alle Unterseiten der Diskussionsseite "Talk:Cow" im Namensraum Benutzerdiskussion, die das Wort "domestic" enthält.
 * cow prefix:Pink Floyd/
 * Findet alle Unterseiten des Atikels "Pink Floyd" in den inhaltlichen Namensräumen, die das Wort "cow" enthalten. Der Leerraum spielt keine Rolle mehr.

Note that the old rule of having to put prefix: at the end of the query still applies.

Spezielle Operatoren

 * Find articles whose text is most similar to the text of the given articles.
 * Find articles in the talk namespace whose title or text contains the word foo
 * Find articles in the file namespace on this wiki and commons whose title or text contains the word
 * You can add  to the query (like  ) to remove the results from commons
 * Find articles in the file namespace on this wiki and commons whose title or text contains the word
 * You can add  to the query (like  ) to remove the results from commons
 * You can add  to the query (like  ) to remove the results from commons
 * You can add  to the query (like  ) to remove the results from commons

Meinten Sie
"Did you mean" suggestions are designed to notice if you misspell an uncommon phrase that happens to be an article title. If so, they'll let you know. They also seem to suggest more things than they ought to sometimes.

Prefer phrase matches
If you don't have too much special syntax in your query we'll give perfect phrase matches a boost. I'm being intentionally vague because I'm not sure exactly what "too much special syntax" should be. Right now if you add any explicit phrases to your search we'll turn off this feature.

Unscharfe Suche
Putting a ~ after a search term (but not double quotes) activates fuzzy search. You can also put a number from 0 to 1 to control the "fuzziness" fraction, e.g. nigtmare~.9 or lighnin~.1 or lighnin~0.1. Closer to one is less fuzzy.

Phrase search and proximity
Surrounding some words with quotes declares that you are searching for those words close together. You can add a ~ and then a number after the second quote to control just how close you mean. The proper name for this "closeness" is "phrase slop". The default "phrase slop" is 1.

Anführungszeichen und genaue Suche
Quotes turn on exact term matches. You can add a ~ to the quote to go back to the more aggressive matcher you know and love.

prefer-recent:
You can give recently edited articles a boost in the search results by adding "prefer-recent:" to the beginning of your search. By default this will scale 60% of the score exponentially with the time since the last edit, with a half life of 160 days. This can be modified like this: "prefer-recent:,". proportion_of_score_to_scale must be a number between 0 and 1 inclusive. half_life_in_days must be greater than 0 but allows decimal points. Dit nummer werkt vrij goed als heel klein. I've tested it around .0001, which is 8.64 seconds.

This will eventually be on by default for Wikinews, but there is no reason why you can't activate it in any of your searches.

hastemplate:
You can filter pages to just those that use a template by adding  to the search. We try to emulate the template inclusion syntax so  finds pages with   and   would find transclusions of the article   from the main namespace. You can omit the quotes if the template's title you are looking for does not contain a space. will filter pages that do not contain that template.

You can combine all sorts of fun search syntax to get only middle quality images of china.

boost-templates:
You can boost pages' scores based on what templates they contain. This can be done directly in the search via  or you can set the default for all searches via the new   message. replaces the contents of  if the former is specified. The syntax is a bit funky but was chosen for simplicity. Some examples:


 * Find files in the China category sorting quality images first.
 * Find files in the China category sorting quality images first.


 * Find files in the China category sorting quality images first and low quality images last.
 * Find files in the China category sorting quality images first and low quality images last.


 * Find files about popcorn sorting quality images first and low quality images last. Remember that through the use of the  message this can be reduced to just.
 * Find files about popcorn sorting quality images first and low quality images last. Remember that through the use of the  message this can be reduced to just.

Don't try to add decimal points to the percentages. They don't work and search scoring is such that they are unlikely to matter much.

A word of warning about : if you add really really big or small percentages they can poison the full text scoring. Think, for example, if enwiki boosted featured articles by a million percent. Then searches for terms mentioned in featured articles would find the featured articles before exact title matches of the terms. Phrase matching would be similarly blown away so a search like  would find a featured article with those words scattered throughout it instead of the article for Brave New World.

Sorry for the inconsistent  in the name. Sorry again but the quotes are required on this one. Sorry also for the funky syntax. Sorry we don't try to emulate the template transclusion syntax like we do with.

insource:
will search text just in the wikitext. This will pick up template parameter names, URLs in link tags, etc. It has two flavors:
 * and
 * These work pretty similarly to  or regular text search in that they are fast but ignore punctuation.


 * and
 * These run Regular expressions against the page source. They aren't efficient and we only allow a few of them to run at a time on the search cluster but they are very powerful. See the explanation of the syntax and the Lucene grammar for regular expressions. The version with the extra  runs the expression case insensitive and is even less efficient. Note that if the regexp contains whitespace, you must either escape each space character (\ ) or put everything after   in quotes (insource:"/foo bar/").
 * Tip: These return much much faster if there are other filters. Instead of searching for  search for.

Auxiliary Text
Cirrus considers some text in the page to be "auxiliary" to what the page is actually about. Examples include table contents, image captions, and "This article is about the XYZ. For ZYX see ZYX" style links. You can also mark article text as auxiliary by adding the  class to the html element containing the text.

Auxiliary text is worth less than the rest of the article text and it is in the snippet only if there are no main article snippets matching the search.

Lead Text
Cirrus assumes that non-auxiliary text that is between the top of the page and the first heading is the "lead in" paragraph. Matches from the lead in paragraph are worth more in article ranking.

Commons Search
By default when the search contains the file namespace, Cirrus will search commons as well. You can disable this behavior by adding  to the search. If you are using a namespace prefix to select the namespace the syntax looks like. If you aren't using a namespace prefix to select the namespace then the syntax looks like.

Siehe auch

 * Full specifications in the browser tests