Revision as of 06:18, 14 April 2024 by imported>Clump(Reverted edits by 188.242.203.201 (talk) to last version by Username entered already in use and please choose a different name)
第二种索引是标题搜索的自动完成模糊索引。
这种索引会每天更新一次，并且在全文搜索中找到的镜像网站也会更新。
Depending on timing a new page could take two days to be found in the fuzzy title autocomplete.If this is unacceptable for a particular use case, within user search options the title completion can be changed to classic prefix search which uses the full-text search index.
There are many indexes of the "full text" of the wiki to facilitate the many types of searches needed.The full wikitext is indexed many times into many special-purpose indexes, each parsing the wikitext in whatever way optimizes their use.Example indexes include:
"auxiliary" text, includes hatnotes, captions, ToC, and any wikitext classed by an HTML attribute class=searchaux.
"Lead-in" text is the wikitext between the top of the page and the first heading.
The "category" text indexes the listings at the bottom.
Templates are indexed. If the transcluded words of a template change, then all the pages that transclude it are updated. (This can take a long time depending on a job queue.) If the subtemplates used by a template change, the index is updated.
Document contents that are stored in the File/Media namespace are now indexed. Thousands of formats are recognized.
现在已经支持了多种语言，但是我们希望能支持所有的语言。
elasticsearch.org提供了現在支持的語言；查看貢獻文檔以提交請求或補丁。
Third-party open-source libraries are also used to support additional languages not covered by Elasticsearch.
CirrusSearch will optimize your query, and run it. The resulting titles are weighted by relevance, and heavily post-processed, 20 at a time, for the search results page. For example snippets are garnered from the article, and search terms are highlighted in bold text.
Search results will often be accompanied by various preliminary reports. These include Did you mean (spelling correction), and, when no results would otherwise be found it will say Showing results for (query correction) and search instead for (your query).
搜索功能还包括：
Sorting navigation suggestions by the number of incoming links.
Starting with the tilde character ~ to disable navigation and suggestions in such a way that also preserves page ranking.
Smart-matching characters by normalizing (or "folding") non-keyboard characters into keyboard characters.
Words and phrases that match are highlighted in bold on the search results page. The highlighter is a cosmetic analyzer, while the search-indexing analyzer actually finds the page, and these may not be 100% in sync, especially for regex. The highlighter can match more or less accurately than the indexer.
在字、词组、参数之间留空格，并输入进参数，可以包含大量空格实例及“灰色空间字符”。“灰色空间字符”全部是非字母数字字符：$characters。
"Greyspace characters" are all the non-alphanumeric characters ~!@#$%^&()_+-={}|[]\:";'<>?,./.A mixed string of greyspace characters and whitespace characters, is "greyspace", and is treated as one big word boundary.
灰色空間是索引的創建和查詢的解釋方式。[4]
Two exceptions are where 1) an embedded:colon is one word (it being treated as a letter), and 2) an embedded comma , such as in 1,2,3, is treated as a number.
Greyspace characters are otherwise ignored unless, due to query syntax, they can be interpreted as modifier characters.
The modifiers are ~ * \? - " ! . Depending on their placement in the syntax they can apply to a term, a parameter, or to an entire query. Word and phrase modifiers are the wildcard, proximity, and fuzzy searches. Each parameter can have their own modifiers, but in general:
A fuzzy-word or fuzzy-phrase search can suffix a tilde ~ character (and a number telling the degree).
A tilde ~ character prefixed to the first term of a query guarantees search results instead of any possible navigation.
A wildcard character inside a word can be an (escaped) question mark \? for one character or an asterisk * character for zero or more characters.
Truth-logic can interpret AND and OR, but parameters cannot. Note that the AND and OR operators currently do not function in the traditional truth-logic manner! For details see more on logical operators.
Truth-logic understands - or ! prefixed to a term to invert the usual meaning of the term from "match" to "exclude".
Words that begin with - or !, such as -in-law or !Kung can exactly match titles and redirects, but will also match every document that does not contain the negated word, which is usually almost all documents.To search for such terms other than as exact matches for titles or redirects, use the insource search parameter (See section below).
Quotes around words mark an "exact phrase" search. For parameters they are also needed to delimit multi-word input.
Stemming is automatic but can be turned off using an "exact phrase".
The two wildcard characters are the star and the (escaped) question mark, and both can come in the middle or end of a word.The escaped question mark \? stands for one character and the star * stands for any number of characters.Because many users, instead of writing a query, will ask a question, any question mark is ignored unless purposefully escaped \? into its wildcard meaning.
A phrase search can be initiated by various hints to the search engine. Each method of hinting has a side-effect of how tolerant the matching of the word sequence will be. For greyspace, camelCase, or txt2number hints:
given words-joined_by_greyspace(characters) or wordsJoinedByCamelCaseCharacters it finds words joined by ... characters, in their bare forms or greyspace forms.
txt2number will match txt 2 number or txt-2.number.
Stop words are enabled for the edge cases (in the periphery) of a grey_space or camelCase phrase.An example using the, of, and a is that the_invisible_hand_of_a matches invisible hand within the text meetings invisible hand shake.
A "search instead" report is triggered when a universally unknown word is ignored in a phrase.
Each one of the following types of phrase-matching contains and widens the match-tolerances of the previous one:
An "exact phrase" "in quotes" will tolerate (match with) greyspace. Given "exact_phrase" or "exact phrase" it matches "exact]phrase".
A greyspace_phrase initiates stemming and stop word checks.
Given CamelCase it will additionally match camelcase, in all lowercase, because CirrusSearch is not case sensitive in matching.
Note that CamelCase matching is not enabled for all languages.
Some parameters interpret greyspace phrases, but other parameters, like insource only interpret the usual "phrase in quotes".
In search terminology, support for "stemming" means that a search for "swim" will also include "swimming" and "swimmed", but may not include irregular forms like "swam".
Note how the "exact phrase" search interpreted the embedded:colon character as a letter, but not the embedded_underscore character. A similar event occurs with the comma , character inside a number.
Given in:this:word, CirrusSearch, when in an "exact phrase" context, (which includes the insource parameter context), will not match in, this, or word, but will then only match in:this:word.
Otherwise, remember that for CirrusSearch words are letters, numbers, or a combination of the two, and case does not matter.
The common word search employs the space character and is aggressive with stemming, and when the same words are joined by greyspace characters or camelCase they are aggressive with phrases and subwords.
When common words like "of" or "the" are included in a greyspace-phrase, they are ignored, so as to match more aggressively.
A greyspace_phrase search term, or a camelCase, or a txt2number term, match the signified words interchangeably. You can use any of those three forms.[5]Now camelcase matches camelCase because Search is not case sensitive, but camelCase matches camelcase because camelCase is more aggressive.Like the rest of Search, subword "words" are not case-sensitive. By comparison the "exact phrase" is greyspace oriented and ignores numeric or letter-case transitions, and stemming. "Quoted phrases" are not case sensitive.
From the table we can surmise that the basic search parser_function -"parser function" is the sum of the basic searches parserFunction and parser<stems> function<stems>.
The star * wildcard matches a string of letters and digits within a rendered word, but never the beginning character.One or more characters must precede the * character.
When * matches numbers, a comma is considered part of one number, but the decimal point is considered a greyspace character, and will delimit two numbers.
Inside an "exact phrase" * is treated as a greyspace character and not a wild card character, so it delimits words.
The \? wildcard represents one letter or number; *\? is also accepted, but \?* is not recognized.
通配符用于基本单词，短语和内容搜索，也可以是（某些）高级正则表达式搜索的替代（稍后介绍）。
在单词或短语后面加上波形符号~字符可激活模糊搜索。
For a phrase it is termed a proximity search, because proximal words are tolerated to an approximate rather than exact phrase.
For example, "exact one two phrase"~2 matches exact phrase.
For a word it means extra characters or changed characters.
For a phrase a fuzzy search requires a whole number telling it how many extra words to fit in, but for a word a fuzzy search can have a decimal fraction, defaulting to word~0.5 (word~.5), where at most two letters can be found swapped, changed, or added, but never the first two letters.
For a proximity phrase, a large number can be used, but that is an "expensive" (slow) search.
For a word word~2 is most fuzzy with an edit distance of 2 (default), and word~1 is least fuzzy, and word~0 is not fuzzy at all.
For the closeness value necessary to match in reverse (right to left) order, count and discard all the extra words, then add twice the total count of remaining words minus one.(In other words, add twice the number of segments).For the full proximity algorithm, see Elasticsearch slop.
源代码搜索（Insource）功能可被用于查找任何在页面上渲染的“文字”，但它主要用于查找您可能很难找到词——包含MediaWiki标记，在重定向以外的任何頁面上。这个搜索词完全忽略灰色空间：insource: "state state autocollapse"匹配|state={{{state|autocollapse}}}。
insource补充了自己。一方面，它立即对wikitext中的任何单词进行全文搜索。另一方面，它可以处理任何字符串的正则表达式搜索。[6]
正则表达式扫描给定页面列表中的所有文本字符；它们没有单词索引来加快速度，如果运行时间必须超过20秒，则进程被中断。
Regexes run last in a query, so to limit needless character-level scanning, every regex query should include other search terms to limit the number of documents that need to be scanned.[7]Often the best candidate to add to the regex query insource:/arg/ is insource:arg, where arg is the same (and uses no wildcards).
The syntax for the regexp is insource: no space, and then /regexp/. (No other parameter disallows a space. All the parameters except insource:/regexp/ accept space after their colon.)
Insource indexed-search and regexp-search roles are similar in many respects:
Neither does stemmed, fuzzy, or proximity searches.
Both want the fewest results, and both work faster when accompanied by another clause.
But indexed searches all ignore greyspace; wildcards searches do not match greyspace, so regexes are the only way to find an exact string of any and all characters, for example a sequence of two spaces.Regexes are an entirely different class of search tool that make matching a literal string easy (basic, beginner use), and make matching by metacharacter expressions possible (advanced use) on the wiki.See #Regular expression searches below.
The insource parameter treats words with embedded colons as one word. This affects search queries for templates, parser functions, URLs, wikilinks, HTML tags, and comments.
When possible, please avoid running a bare regexp search. See how this is always possible at #Regular expression searches, below.
To search for words that begin with - or !, such as -in-law or !Kung, use a case-insensitive insource query together with a simple search on the "plain" version of the term (to avoid a bare regexp search). For example, "in-law" insource:/-in-law/i or "kung" insource:/!kung/i.
前缀和名字空间
Prepending a namespace term like file: to a search query limits results to a specific namespace, instead of searching the entire wiki.The default namespace is "Main".
Only one namespace name can be set from the search box query.It must be the first term in the query, or, if used as part of a prefix: term, must appear as the last term in the query.
Two or more namespaces may be searched from the Advanced pane of the search bar found on the top of every search results page, Special:Search.Your search domain, as a profile of namespaces, can be set here.The namespaces list will then present itself on the first page of future search results to indicate the search domain of the search results.To unset this, select the default namespace (shown in parentheses), select "Remember", and press Search.
The search bar graphically sets and indicates a search domain. "Content pages" (mainspace), "Multimedia" (File), "Everything" (all plus File), "Translations", etc., are hyperlinks that can activate the query in that domain, and then indicate this by going inactive (dark). But the query will override the search bar.When a namespace or prefix is used in the query the search bar activations and indications may be misleading, so the search bar and the search box are mutually exclusive (not complementary) ways to set the search domain.
A namespace term overrides the search bar, and a prefix: term overrides a namespace.
To specify a namespace name, prefix it with a colon, e.g., talk:.Use all: to search across all namespaces, or : (a single colon) to search just the main article namespace.
As with search parameters, local: and all: must be lowercase.Namespaces names, though, are case insensitive.
名字空间的别名也是被接受的。
talk: "Wind clock"
Find pages in the Talk namespace whose title or text contains the phrase "wind clock".
file: "Wind clock"
Find pages in File namespace, whose title, text, or media content contains the phrase "wind clock".
file: local: "Wind clock"
过滤来自共享资源wiki的结果。
local: "Wind clock"
已忽略。 Searches mainspace. Local is ignored unless File is involved.
prefix:
The prefix: parameter matches any number of first-characters of all pagenames in one namespace.[8]When the first letters match a namespace name and colon, the search domain changes.
Given a namespace only, prefix: will match all its pagenames. Given one character only, it cannot be - (dash), ' (quote), or " (double quote). The last character cannot be a colon.
For pagenames that match, their subpage titles match by definition.
The prefix: parameter does not allow a space before a namespace, but allows whitespace before a pagename.This term always goes at the end, so that pagename characters may contain quotation marks (").
prefix:cow
Find pages in mainspace whose title starts with the three letters c o w.
domesticprefix:cow
Find pages in mainspace whose title starts with the three letters c o w, and that contain the word "domestic".
domesticprefix:cow/
List any existing subpages of Cow but only if they contain the word "domestic".This is a very common search and is frequently built using a special URL parameter called prefix=.
domesticprefix:Talk:cow/
List any subpages of Talk:cow, but only if they contain the word "domestic".
1967prefix:Pink Floyd/
List any subpages of Pink Floyd, but only if it also contains the word "1967".
The Translate extension creates a sort of "language namespace" of translated versions of a page.However, unlike namespace or prefix, which create the initial search domain, the inlanguage parameter is a filter of it. (See the next section.)
从搜索索引中排除内容
Content can be excluded from the search index by adding class="navigation-not-searchable". This will instruct CirrusSearch to ignore this content from the search index (see <translate> task <tvar name=1>T162905</tvar></translate> for more context).
Additionally content can be marked as auxiliary information by adding class="searchaux".This will instruct CirrusSearch to move the content from the main text to an auxiliary field which has lower importance for search and snippet highlighting.This distinction is used for items such as image thumbnail descriptions, 'see also' sections, etc.
过滤器
A filter will have multiple instances, or negated instances, or it can run as a standalone filtering a search domain.A query is formed as terms that filter a search domain.
Adding another word, phrase, or parameter filters more. A highly refined search result may have very many Y/N filters when every page in the results will be addressed. (In this case ranking is largely irrelevant.)Filtering applies critically to adding a regex term; you want as few pages as possible before adding a regex (because it can never have a prepared index for its search).
A namespace is a specified search domain but not a filter because a namespace will not run standalone.A prefix will negate so it is a filter.
以下搜索参数是过滤器，可能同時有多個項目。
Insource (covered above) is also a filter, but insource:/regexp/ is not a filter. Filters and all other search parameters are lowercase. (Namespaces are an exception, being case insensitive.)
在标题中和在分类中
Word and phrase searches match in a title and match in the category box on bottom of the page. But with these parameters you can select titles only or category only.
cow*
搜尋標題或內文由cow開頭的頁面
intitle:foo
查找标题包含foo的条目。词干提取对foo启用。
intitle:"fine line"
Find articles whose title contains fine line. Stemming is disabled.
intitle:foo bar
查找标题包含foo或包含bar的条目。
-intitle:foo bar
查找标题既不包含“foo”、也不包含“bar”的词条。
incategory:Music
查找属于“Music”分类的词条
incategory:"music history"
查找属于“Music_history”分类的词条
incategory:"musicals" incategory:"1920"
查找同时属于“Musicals”和“1920”分类的词条
-incategory:"musicals" incategory:"1920"
查找属于“1920”分类，但不属于“musicals”的词条
Intitle and incategory are old search parameters. Incategory no longer searches any subcategory automatically, but you can now add multiple category pagenames manually.
<td class="mw-version-versionbox" title="<translate nowrap> The latest stable version is <tvar name=1>1.41</tvar></translate>">
When possible, please avoid running a bare regexp search. See how this is always possible at #Regular expression searches, below.
Deepcategory
Deep category search allows to search in category and all subcategories. The depth of the tree is limited by 5 levels currently (configurable) and the number of categories is limited by 256 (configurable). The deep search uses SPARQL Category service from WDQS. Keywords are deepcategory or deepcat. Example:
deepcat:"musicals"
Find articles that are in Category:Musicals or any of the subcategories.
The DeepCat gadget that previously implemented the parameter was sunsetted in January 2020.
链接到
Linksto finds wikilinks to a given name, not links to content. The input is the canonical, case sensitive, page name.
It must match the title line of the content page, exactly, before any title modifications of the letter-case. (It must match its {{FULLPAGENAME}}, e.g. Help:CirrusSearch/zh.)
Linksto does not find redirects. It only finds [[wikilinks]], even when they are made by a template.It does not find a link made by a URL, even if that URL is an internal wiki link.
To find all wikilinks to a "Help:Cirrus Search", if "Help:Searching" and "H:S" are redirects to it:
linksto: "Help:Cirrus Search"
linksto: Help:Searching
linksto: H:S
CirrusSearch -linksto: Help:CirrusSearch finds articles that mention "CirrusSearch" but not in a wikilink.
有模板
You can specify template usage with hastemplate: template. Input the canonical pagename to find all usage of the template, but use any of its redirect pagenames finds just that naming. Namespace aliases are accepted, capitalization is entirely ignored, and redirects are found, all in one name-search. (Compare boost-template no default namespace; linksto no namespace aliases, case-sensitive, no redirects; intitle no redirects.)
Hastemplate finds secondary (or meta-template) usage on a page: it searches the post-expansion inclusion. This is the same philosophy as for words and phrases from a template, but here it's for templates from a template. The page will be listed as having that content even though that content is not seen in the wikitext.
hastemplate: "quality image", finds "Template:Quality image" usage in your default search domain (namespaces).
hastemplate: portal:contents/tocnavbar, finds mainspace usage of a "Contents/TOCnavbar" template in the Portal namespace.
For installations with the Translate extension, hastemplate searches get interference wherever Template:Translatable template name wraps the template name of a translatable template. Use insource instead.
在语言中
For installations with the Translate extension, inlanguage is important for highly refined searches and page counts.
will produce search results in that language only.
例如
计数wiki上的所有日语页面
all: inlanguage: ja
在帮助名字空间中过滤掉德语和西班牙语页面
help: -inlanguage: de -inlanguage: es
忽略翻译，如果英语是基本语言，则添加
inlanguage:en
Contentmodel
The contentmodel: keyword allows to limit the search to pages of a specific content model. For possible models cf. Content handlers. E.g.:
只查看JSON页面：
contentmodel:json
子页面属于
要查找子页面。
subpageof: 父页面
例如
查找所有CirrusSearch的子页面。
subpageof:CirrusSearch
Use double quotes if the parent page contains spaces.
subpageof:"Requests for comment"
unlike prefix:, do not include the page namespace in the keyword value. If you want to limit to sub-pages of a particular namespace use the namespace filter.
Articletopic
The articletopic: keyword allows filtering search results by topic. For possible topics see Help:CirrusSearch/articletopic.E.g. articletopic:books will filter the search results to articles about books.articletopic:books|films will filter to articles about books or films.articletopic:books articletopic:films will filter to articles which are about both books and films.
Only mainspace articles belong into topics, and topics are only available on Wikipedias.Unlike other filters, articletopic also does page weighting: articles which are a stronger match for a topic will be higher in the search results (while articles which aren't about that subject at all will be removed from the result set completely).
Topic models are derived via machine learning from ORES.Any given article receives a score on dozens of different topics, and therefore may appear under different keywords.For instance, the article on Albert Einstein may appear as a "physics" article and a "biography" article.All Wikipedias have scores available -- some have local-language topic models that have coverage on all articles.Other languages do not have local ORES models, and are using English-language scores assigned to articles in the local language that also exist in English Wikipedia.The languages with such "cross-wiki" scores do not have 100% coverage -- depending on the language, it may only be something like 60% of articles that have topics available.
Topic-related search data is updated weekly, so recently created articles might not show up in topic-based search queries.
Pageid
The pageid: keyword restricts search results to the given set of page IDs.This is not really useful for manual searching; it can be used by software tools for checking whether a set of pages match the given set of search conditions (e.g. for re-validating cached search results).
页面权重
Weighting determines snippet, suggestions, and page relevance. The normal weight is one. Additional weighting is given through multipliers.
If the query is just words, pages that match them in order are given a boost. If you add any explicit phrases to your search, or for certain other additions, this "prefer phrase" feature is not applied.
morelike is a "greedy" keyword, meaning that it cannot be combined with other search queries. If you want to use other search queries, use morelikethis in your search:
morelikethis:bee hastemplate:"featured article"
Find articles about bees that also have the "featured article" template.
The morelike: query works by choosing a set of words in the input articles and run a query with the chosen words. You can tune the way it works by adding the following parameters to the search results URL:
cirrusMltMinDocFreq: Minimum number of documents (per shard) that need a term for it to be considered.
cirrusMltMaxDocFreq: Maximum number of documents (per shard) that have a term for it to be considered.
cirrusMltMaxQueryTerms: Maximum number of terms to be considered.
cirrusMltMinTermFreq: Minimum number of times the term appears in the input to doc to be considered. For small fields (title) this value should be 1.
cirrusMltMinWordLength: Minimal length of a term to be considered. Defaults to 0.
cirrusMltMaxWordLength: The maximum word length above which words will be ignored. Defaults to unbounded (0).
cirrusMltFields (comma separated list of values): These are the fields to use. Allowed fields are title, text, auxiliary_text, opening_text, headings and all.
cirrusMltUseFields (true|false): use only the field data. Defaults to false: the system will extract the content of the text field to build the query.
cirrusMltPercentTermsToMatch: The percentage of terms to match on. Defaults to 0.3 (30 percent).
These settings can be made persistent by overriding cirrussearch-morelikethis-settings in System message.
Prefer-recent
Adding prefer-recent: anywhere in the query gives recently edited articles a slightly larger than normal boost in the page-ranking rules.Prefer-recent is only applied when using the default relevancesort order.
It defaults to boost only 60% of the score, in a large, 160-day window of time, which can be entered in the query as prefer-recent:0.6,160. This plays well with other page ranking rules, and is intended for most searches.
You can manipulate the rules: prefer-recent:boost,recentTechnically, "boost" is the proportion of score to scale, and "recent" is the half life in days.The boost is more than the usual multiplier, it is an exponential boost.The factor used in the exponent is the time since the last edit.
例如
prefer-recent:,7
Pages older than 7 days are boosted half as much, and pages older than 14 days are boosted half as much again, and so on.For a simple "sort by date" in highly refined search results, where page ranking and boosting are largely meaningless, just boost the entire score.
prefer-recent:1,7 - weeks
prefer-recent:1,1 - days
prefer-recent:1,0.0007 - minutes
prefer-recent:1,0.0001 - 8.64 seconds
prefer-recent:1,0.00001 - seconds
推动-模板
你可以根据所用模板不同来调整搜索结果的排列顺序，比如boost-templates:""；或使用新语法cirrussearch-boost-templates来设置默认选项（通过发送系统消息）。boost-templates:""会取代cirrussearch-boost-templates的设置（如果后者已经被设置的话）。这一语法很特别，但若使用得当则能简化搜索。Similar to the prefer-recent feature, boost-templates is applied as part of the default relevancesort order. It has no effect on other search orders.
The syntax of the message is as follows:
Everything from a # character to the end of the line is considered a comment, and ignored.
Every non-blank line is interpreted as the exact name of a template that should receive boosting (including namespace prefix), followed by a pipe "|" character, followed by a number, followed by a "%" character.
Template:Foo|150.234234% # decimal points are not allowed.
Foo|150% # technically valid, but acts on transclusions of Foo (main space article) instead of Template:Foo.
Find files about popcorn, sorting quality images first and low-quality images last. Remember that through the use of the cirrussearch-boost-templates message this can be reduced to just popcorn.
不要在表示比例的百分数中添加小数点。这样做不会起作用，而且搜索结果也不会有很大差别。
cirrussearch-boost-templates使用警告：如果你在排序比例中设置了一个非常大或非常小的值，全文搜索将会受到影响。For example, if Wikipedia were to boost the "Featured article" template by 1 million percent, then, searches for any term mentioned in featured articles, would rank the featured article above even the dedicated article about that term.
Phrase matching would be similarly blown away, so a search like brave new world would return a featured article as first result even if it merely has those three words mentioned throughout it, instead of the more relevant article about Brave New World itself.
Do not run a bare insource:/regexp/ search. It will probably timeout after 20 seconds anyway, while blocking the queries of responsible users.
A basic indexed search finds words rendered visible on a page. Hyphenation and punctuation marks and bracketing, slash and other math and computing symbols, are merely boundaries for the words. It is not possible to include them in an indexed search.Mostly that search behavior is wanted by the user. However, sometimes one wants to have the ability for a more precise search.
To get around the syntactic deficiency of index-based searches regexp searches can be used.But as queries with only regexp expressions are very slow and resource consuming, they should always be combined with an index-based search, such that the regexp search-domain gets limited to the results of one or more index-based search.
An "exact string" regexp search is a basic search; it will simply "quote" the entire regexp, or "backslash-escape" all non-alphanumeric characters in the string. All regexp searches also require that the user develops a simple filter to generate the search domain for the regex engine to search (index based search domain marked bold, regexp part marked in italics):
A query with no namespace specified and no prefix specified searches your default search domain, (settable on any search-results page, i.e. at Special:Search). Some users keep their default search domain at "all namespaces", i.e. the entire wiki. On a large wiki if this user does a bare regexp search it will probably fail, incurring a timeout, before completing the search.
A regex search actually scours each page in the search domain character-by character.By contrast, an indexed search actually queries a few records from a database separately maintained from the wiki database, and provides nearly instant results.So when using an insource:// (a regexp of any kind), consider adding other search terms that will limit the regex search domain as much as possible.There are many search terms that use an index and so instantly provide a more refined search domain for the /regexp/. In order of general effectiveness:
insource:"" with quotation marks, duplicating the regexp except without the slashes or escape characters, is ideal.
intitle (without regex search), incategory, and linksto are excellent filters.
hastemplate: is a very good filter.
"word1 word2 word3", with or without the quotation marks, are good.
namespace: is practically useless, but may enable a slow regexp search to complete.
To test a bare regexp query you can create a page with test patterns, and then use the prefix parameter with that fullpagename.
匹配项会被高亮。
It searches that page (in the database) and its subpages.
Search terms that do not increase the efficiency of a regexp search are the page-scoring operators: morelike, boost-template, and prefer-recent.
元字符
此节包含如何在regexp搜索中，避免元字符（metacharacters）的内容
For the actual meaning of the metacharacters see the explanation of the syntax.[9]
The use of an exact string requires a regexp, but the regexp term obligates the search to limit itself. Add a regexp term, never search a bare regexp. Start by noting the number of pages in a previous search before committing an exact string search. Querying with an exact string requires a filtered search domain.
例如：
to search a namespace, gauge the number of pages with a single term that is a namespace. This will list the number of pages in that namespace.
starting out to find again what you may have seen, like "wiki-link" or "(trans[in]clusion)" start with namespace and insource filters.
There are some notable differences from standard regex metacharacters:
The \n or \r\n are not reserved for matching a newline.
To search for a string that contains a newline, you can do a search like insource:/[^\}]\}\}[^\} \|]{2}\<noinclude/i which means not a curly brace, then two curly braces, then any two characters except a curly brace, space, or pipe, then a <noinclude> tag.The "any character except" will include a newline in the search.Note thas this search was designed only to match to the following string:
}}
<noinclude>
The dot . metacharacter stands for any character including a newline, so .* matches across lines.
The number # sign means something, and must be escaped.
The ^ and $ are not implemented. Like "grep" (global per line, regular expression, print each line), each insource:// is a "global per document, regular expression, search-results-list each document" per document.
< and > support a multi-digit numeric range like [0-9] does, but without regard to the number of character positions, or the range in each position, so <9-10> works, and even <1-111> works.
Substitutions for some metacharacters
While character classes \n, \s, \S are not supported, in case of an acute need to use them in a regular expression, you may use these workarounds:
Any character except for a newline (and tabulation; you can add it to character set to include it as well)
\s
[^!-]
A white space character: space, newline, or tabulation
\S
[!-]
Any character except for white space characters (not a space, not a newline, and not a tabulation)
In these ranges, " " (space) is used as the character immediately following control characters, "!" – the character immediately following it, and "" as the U+10FFFF character, which is the last character in Unicode.Thus, the range from " " to "" includes all characters except for control ones, of which articles may contain newlines and tabs, while the range from "!" to "" includes all characters except for control ones and the space.
通过准确字符串改善
refining an ongoing search process with what you want to see, like "2 + 2 = 4", or "site.org" This is ideally the best use of regex, because it adds it as a single regexp term while refining a search, the limited number of pages the regexp must crawl is can be seen.
You can start out intending an exact string search, but keep in mind:
regex only search the wikitext not the rendered text, so there are some differences around the markup, and even the number of space characters must match precisely.
You are obligated to supply an accompanying filter.
You must learn how to escape regex metacharacters.
There are two ways to escape metacharacters. They are both useful at times, and sometimes concatenated side-by-side in the escaping of a string.
Backslash-escape one of them \char. The insource:/regexp/ uses slashes to delimit the regexp. Giving /reg/exp/ is ambiguous, so you must write /reg\/exp/.
Put a string of them in double quotes "string". Because escaping a character can't hurt, you can escape any character along with any possible metacharacters in there. Escaping with quotes is cleaner.
You can't mix methods, but you can concatenate them.
Double-quotes escaping using insource:/"regexp"/ is an easy way to search for many kinds of strings, but you can't backslash-escape anything inside a double-quoted escape.
/"[[page/name|{{temp-late"/ instead of /\[\[page\/name\|\{\{temp\-late/
/"literal back\slash"/ is as good as /literal back\\slash/
But /"This \" fails"/ always.
And /"This \/ depends"/. It finds the \/ literally, which is not the / you probably wanted.
Backslash-escape using insource:/regexp/ allows escaping the " and / delimiters, but requires taking into account metacharacters, and escaping any:
To match a / delimiter character use \/.
To match a " delimiter character use \".
The escaped metacharacters would be \~\@\#\&\*\(\)\-\+\{\}\[\]\|\<\>\?\.\\.
The equivalent expression escaped with double-quotes is "~@#&*()-+{}[]|\<>?.\".
The simplest algorithm to create the basic string-finding expression using insource:/"regexp"/, need not take metacharacters into account except for the " and / characters:
Write the/str"ing out. (The /" delimiters "/ are not shown.)
Replace " with "\"" (previous double-quote: stop, concatenate, quote restart).
Replace / with "\/" (stop, concatenate, start).
You get insource:/"the"\/"str"\""ing"/, showing concatenation of the two methods.
While refining a regexp on a search results page, keep in mind that the snippet "wikitext" has modified spacing. Regex are sensitive to space characters, so copying from snippets is dangerous.
The square-bracket notation for creating your own character-class also escapes its metacharacters. To target a literal right square bracket in your character-class pattern, it must be backslash escaped, otherwise it can be interpreted as the closing delimiter of the character-class pattern definition.The first position of a character class will also escape the right square bracket. Inside the delimiting square brackets of a character class, the dash character also has special meaning (range) but it too can be included literally in the class the same way as the right square bracket can.For example both of these patterns target a character that is either a dash or a right square bracket or a dot: [-.\]] or [].\-].
For general examples using metacharacters:
insource:"2+2=4" insource:/"2+2=4"/ matches "2 + 2 = 4", with zero spaces between the characters.
insource:"2 + 2 = 4" insource:/2 ?\+ ?2 ?= ?4\./ match with zero or one space in between. The equals = sign is not a metacharacter, but the plus + sign is.
The insource keyword does only search the page source content.To run regex searches on the title strings intitle:/regex/ can be used.
高级示例
For example, using metacharacters to find the usage of a template called Val having, inside the template call, an unnamed parameter containing a possibly signed, three to four digit number, possibly surrounded by space characters, and on the same page, inside a template Val call, a named argument fmt=commas having any allowable spaces around it, (it could be the same template call, or a separate one):
Note that the = sign in "fmt commas" is not needed but that adding it would not change the search results.It is fast because it uses two filters so that every page the regexp crawls has the highest possible potential.
地理搜索
Searching based on the (primary) coordinates associated with pages.Depends on Extension:GeoData and {{#coordinates:}}
You can alternatively increase the score of pages within a specified geographic area.The syntax is the same as bounded search, but with boost- prepended to the keyword.This effectively doubles the score for pages within the search range, giving a better chance for nearby search results to be near the top.
boost-neartitle:"San Francisco"
boost-neartitle:"100km,San Francisco"
boost-nearcoord:37.77666667,-122.39
boost-nearcoord:42km,37.77666667,-122.39
文件属性搜索
<td class="mw-version-versionbox" title="<translate nowrap> The latest stable version is <tvar name=1>1.41</tvar></translate>">
Since MediaWiki 1.28, CirrusSearch supports indexing and searching of properties of files in the File: namespace. This includes:
file media type
MIME type
size
width & height
resolution
bit depth for files that support these
While these predicates are useful only for files, they by themselves do not limit search to the File: namespace. It is recommended to include this namespace in a search or restrict the search to only this namespace when using these conditionals.
文件类型
文件類型搜索允許根據分類搜索文件，例如辦公室文件、影片、點陣圖、向量圖等。目前存在以下類型：
UNKNOWN
BITMAP
DRAWING
AUDIO
VIDEO
MULTIMEDIA
OFFICE
TEXT
EXECUTABLE
ARCHIVE
This list may be extended in the future. See also MEDIATYPE_* constants in Defines.php.
The syntax of the search is: filetype:{type}. Example:
filetype:video - looks for all videos
The filetype search is not case-sensitive.
文件mime
Matches file MIME type. The syntax is:
filemime:{MIMEtype} - look for files of this MIME type
The argument can be quoted to specify exact match. Without quotes, partial matches to components of MIME type will be accepted too.
示例：
filemime:"image/png" - look for files with MIME type exactly image/png
filemime:pdf - look for all PDF documents
-filemime:pdf - skip all PDF documents (notably on Commons)
The MIME type search is not case-sensitive.
文件大小
搜索指定大小的文件，單位為千位元組（1024位元組）。語法為：
filesize:{number}或filesize:>{number} - file with size at least given number
filesize:<{number} - file with size no more than given number
filesize:{number},{number} - file with size between given numbers
示例：
filesize:>20或filesize:20 - 至少20KB的文件
filesize:<1024 - 小于1MB的文件
filesize:100,500 - 大小在100KB到500KB之間的文件
文件度量
It is possible to search for specific file measures: width, height, resolution (which is defined as square root of height × width), and bit depth. Not all files may have these properties. The syntax is:
{measure}:{number} - file with measure that equals to given number
{measure}:>{number} - file with measure that is at least given number
{measure}:<{number} - file with measure that is no more than given number
{measure}:{number},{number} - file with measure that is between given numbers
measure可以：
filew或filewidth — 文件宽度
fileh或fileheight — 文件高度
fileres — 文件解析度（見上方）
filebits — 文件位元深度
示例：
filew:>800 fileh:>600 — 大小至少為800x600像素的文件
filebits:16 — 有16位元顏色深度的文件
fileheight:100,500 — 文件高度在100到500像素之間
Wikibase搜尋
The Wikibase extension defines some search keywords in order to make it easier to search for certain Wikibase items. This is useful on Wikidata and other Wikibase sites, including to search for images with Structured data on 维基共享资源.
详情请见Help:WikibaseCirrusSearch。
跨維基搜索結果
There are two kinds of cross-wiki results that may be shown when searching on Wikipedia.
Cross-project search (also known as interwiki search, sister search, or sister projects search) shows additional results from other projects (Wiktionary, Wikisource, Wikiquote, etc.) shown to the side on the Wikipedia results page.Cross-project search is available on most Wikipedias with sister projects.
Cross-language search (see blog post) refers to additional results shown below the main results that are from a Wikipedia in a different language.Cross-language search uses a heavily modified and optimized version of a light-weight language detector called TextCat.Cross-language search is currently only available on a few Wikipedias (see TextCat link for details).
Explicit sort orders
In addition to the default relevance based sort, CirrusSearch can provide results using a few other explicit sort orders.Specifying a sorting order other than relevance will disable all search keywords that affect scoring, such as prefer-recent or boost-templates.The keywords will still be parsed, but they will have no effect.
Sorting options are currently available from the MediaWiki API by providing the srsort parameter.
Guidance:
Sorting options can be manually added to a search URL by adding &sort=order, for example:
The AdvancedSearch extension adds an improved interface to the search page allowing the use of several options described above in a user-friendly manner. See here for the user manual.
↑A slow regex search cannot disable search, but can disable another's regex search, since there are only a limited number of regex searches allowed at a time.
↑Prefix does not match on first-characters of fullpagenames, so you cannot search two namespaces at once just because they start with the same letters, such as both namespace and namespace talk in one query.
