Help:CirrusSearch/su

Cara panggancangna pikeun milarian inpormasi dina proyék Wikipédia nyaéta pikeun milarian langsung. Di unggal halaman aya kotak  '$ search'  'kotak.

' 'CirrusSearch' '' mangrupikeun penyambungan MediaWiki anu ngagunakeun Elasticsearch pikeun nyayogikeun kamampuan milarian ditingkatkeun sapanjang  panyungsi MediaWiki standar. Yayasan Wikimédia ngagunakeun CirrusSearch sadayana pikeun Proyék Wikimédia. Kaca ieu ngajelaskeun fitur CirrusSearch. Lamun masalah anjeun can kajawab, mangga naros di kaca obrolan.

Kanggo inpormasi ngeunaan ekstensi MediaWiki, tingali Ekstensi:CirrusSearch.

Kumaha gawéna
Ketik kecap konci sareng frasa terus pencét  Enter  atanapi  Return  dina keyboard. Atawa klik dina ikon kaca pembesar, Milarian atanapi Go tombol. Upami hiji halaman gaduh judul anu sami sareng anjeun asup, anjeun bakal dicandak kana halaman éta. Upami teu kitu, maluruh sadaya halaman dina wiki sareng nampilkeun daptar tulisan anu cocog sareng istilah anu dipilarian atanapi pesen anu nyatakeun yén teu aya halaman ngagaduhan sadayana kecap konci sareng frasa konci.

Upami anjeun klik tombol "" tanpa ngeusian nanaon, anjeun bakal diarahkeun ka "Special: search", anu nawiskeun pilihan milarian tambahan (ogé sayogi dina daptar naon waé hasil pamilarian)

Anjeun tiasa mendakan mangpaat pikeun ngawatesan milarian ka kaca dina namespace spesifik, contona, milarian ngan ukur dina kaca $ pangguna. Parios ngarani tempat anu diperyogikeun pikeun milarian ieu.

Naon anu ngaronjat?
CirrusSearch gaduh tilu perbaikan utama dina pamakean standar standar, nyaéta:


 * Pangrojong anu leuwih hadé pikeun maluruh dina rupa-rupa basa.
 * Pembaruan langkung gancang pikeun indéks teang, anu hartosna parobihan kanggo artikel dibuktikeun dina hasil pamaluruhan langkung gancang.
 * Modél ékspansi, anu hartosna yén eusi eusi sadayana ayeuna dibayangkeun dina hasil pamilarian.

Sabaraha indéks milarian anu diropéa?
Apdet pikeun indéks milarian dilakukeun ampir sacara real waktos. Parobihan kana halaman kedah langsung muncul dina hasil pamilarian. Parobihan kana témplat kedahna épék pikeun artikel anu kalebet témplat dina sababaraha menit. Parobihan modél nganggo parantosan padamelan, janten prestasi tiasa bénten-béda. A null edit dina tulisan bakal maksa parobihan, tapi ieu sanés kedah diperyogikeun upami sadayana bakal dilaksanakeun.

Saran téang
Saran milarian anu anjeun tampi nalika anjeun ngetik kotak milarian anu muncul dina halaman calon digolongkeun dumasar ukuran perkiraan kualitas tulisan. Hal ieu kedah diperhatoskeun jumlah wikilinks anu katampi, ukuran halaman, jumlah tumbu éksternal, jumlah judul sareng jumlah alihan. Saran pamilarian tiasa dipaliré sareng pamundut bakal langsung diarahkeun ka halaman hasil pamilarian. Tambihkeun tilde  sateuacan pamundut na. Conto "~ Frida Kahlo". Saran pamilarian masih bakal muncul, tapi pencét tombol Lebetkeun iraha waé bakal nyandak anjeun ka halaman hasil pamilarian.

ASCII / aksen / tilepan diacritical diaktipkeun pikeun téks Inggris, tapi aya sababaraha pormat masalah sareng hasilna. Ningali.

== Néangan téks lengkep

"Milarian téks pinuh" mangrupikeun "pamilarian anu di-index". Sadaya halaman disimpen dina database wiki sareng sadaya kecap dina kaca anu henteu dialihkeun disimpen disimpen dina pangkalan data milarian, anu mangrupikeun indéks kanggo ampir téks pinuh wiki. Unggal kecap anu ditingali saestuna kana daptar halaman dimana éta dipendakan, ku kituna milarian kecap gancang-gancang milarian rékaman tunggal. Salaku tambahan, kanggo naon parobahan dina kecap, indéks teang diropéa dina detik.

Aya seueur indéks tina "téks lengkep" wiki pikeun mempermudah sagala rupa jinis padamelan anu dibutuhkeun. Wikitext lengkep anu sering diindeks dina sababaraha indéks tujuan khusus, masing-masing nganalisa wikitext dina cara anu ngoptimalkeun pamakeanana. Conto indexes di antarana:


 * téks "bantu", kalebet tulisan suku, caption, daptar eusi sareng wikitext naon waé dikelompokeun ku atribut class=searchaux.
 * Teks "Entri" mangrupikeun wikitext antara luhureun halaman sareng lulugu munggaran.
 * Téks "katégori" indéks daptar di handap.
 * Model saestuna. Upami kecap-kecap anu diturunkeun tina robih citakan, sadaya halaman anu ditambihkeun bakal diropéa. (Ieu tiasa lami, gumantung kana antrian padamelan.) Upami submodél anu dianggo ku modél dirobih, indéksna bakal diénggalan.
 * Eusi dokumén anu disimpen dina halaman ngaran File / Media ayeuna tiasa di-indéks. Rébuan format diakui.

Puluhan basa dirojong, tapi sadayana basa anu dipikahoyong. Aya daptar basa anu ayeuna dirojong di elasticsearch.org; tingali dokuméntasi ngeunaan kontribusi pikeun ngalebetkeun pamundut atanapi patch.

CirrusSearch bakal ngaoptimalkeun pamundut anjeun sareng ngalaksanakeunana. Judul anu hasilna ditimbang ku relevansi sareng diproses pisan, 20 dina hiji waktu, ka halaman hasil pamilarian. Salaku conto, snippét dicandak tina tulisan sareng istilah anu dipilari dicorot dina téks anu kandel.

Hasil survey biasana dibarengan ku sababaraha laporan awal. Éta kalebet  Naha anjeun hartosna  (koréksi ejaan) sareng, nalika henteu aya hasil anu kapanggih, éta bakal nyarios  Némbong hasil  (query koréksi) sareng  milarian  (query anjeun).

Fitur Pilarian ogé kaasup:


 * Susun saran navigasi ku lobana tautan anu katampi.
 * Dimimitian ku karakter tilde  pikeun nganonaktipkeun navigasi sareng saran dina cara anu ogé ngajagaan réngking halaman.
 * Karakter pertandingan pinter anu menormalkeun (atanapi "duka kali") karakter anu teu nganggo keyboard pikeun karakter keyboard.
 * Cocog sareng kecap sareng frasa disorot nganggo wani dina kaca hasil pamilarian. Pananda mangrupikeun analisa kosmetik, sedengkeun anu pariksa indéks panéangan milarian halaman éta, sareng aranjeunna henteu 100% disinkronikeun, khususna kanggo regex. Highlighter tiasa langkung pas atanapi kirang akurat tibatan indéksina

Kata, frasa, sareng modifikasi
Istilah teangan dasar nyaéta kecap atanapi "frasa dina tanda petik". Pilarian ngakuan "kecap" salaku:


 * urutan angka
 * sekuen hurup
 * subwords antara transisi aksara / angka, sakumaha dina txt2regex
 * subwords dina sanyawaName nganggo camelCase

"Kecap terakhir" nyaéta kecap anu teu dipalire (sabab biasana atanapi alesan sanésna). Istilah teang anu dipasihan pakait sareng  eusi  (dikaluarkeun dina halaman). Pikeun ngabandingkeun sareng wikitext, nganggo parameter pencarian insource (tingali section di handap). Unggal parameter panéangan gaduh indéks sorangan sareng narjamahkeun istilah anu disayogikeun ku caraana.

Jarak antara kecap, frasa, parameter sareng éntri parameter tiasa kalebet instansi beresih tina rohangan bodas sareng  aksara kosong . "Aksara Copyspace" mangrupikeun karakter anu sanés angka alpasarer ~!@#$%^&_+-={}|[]\:";'<>?,./ . String anu dicirikeun karakter  greyspace  sareng karakter rohangan bodas nyaéta "greyspace" sareng dirawat salaku wates kecap ageung. Greyspace nyaéta kumaha indéks anu dilakukeun sareng pamundut diinterpretasi.

Dua pengecualian aya di mana 1) embedded:colon mangrupikeun kecap (dirawat salaku surat) sareng 2) komma anu dipasang dina, sapertos dina 1,2,3 , dirawat sapertos 1,2,3 sajumlah. Karak Greyspace teu dipalire kajaba, kusabab sintaksis query, aranjeunna tiasa diinterpretasi salaku modifikasi karakter.

The modifier na ~ * \? - " ! . Gumantung kana panempatan sintaksis, aranjeunna tiasa dilarapkeun kana istilah, parameter, atanapi sadayana pamundut. Modifikasi tina kecap sareng frasa mangrupikeun wildcard, jarakna sareng panyebaran panyungsi. Masing-masing parameter tiasa gaduh modifier-na sorangan, tapi sacara umum:


 * Milarian sareng kecap anu teu jelas atanapi frasa samar tiasa ngandung karakter anu $ $ tilde (sareng nomer anu masihan béja).
 * Aksara anu tilde $ tilde anu siap pikeun istilah pamundut mimiti ngajamin hasil pamilarian tapi teu aya navigasi anu mungkin.
 * Tiasa kartu liar dina hiji kecap janten tanda tanya (lolos) \? pikeun karakter atanapi asterisk karakter $ asterisk kanggo langkung seueur.
 * Logika kabeneran tiasa napsirkeun $ e sareng $ atanapi, tapi parameter henteu tiasa. Catet yén $ sareng $ operator atanapi ayeuna  'teu damel sacara tradisional dina kabeneran logika! "  Kanggo detil, tingali langkung seueur dina [[Pitulung: CirrusSearch / Logical operator | operator logis].
 * Logika kabeneran nyakup $ dash atanapi $ exclaim prefixed dina istilah pikeun ngahirupkeun hartos dawam istilah "match" kanggo "ngaluarkeun".


 * Tanda kutip di sekitar kecap nandaan milarian "frasa pasti". Pikeun parameter, aranjeunna ogé diperyogikeun pikeun ngalebetkeun asupna sababaraha kecap.
 * Kalapa otomatis, tapi tiasa dinonaktipkeun nganggo "frasa pasti".

Hiji kecap frasa tiasa diprakarsai ku sababaraha tip pikeun mesin pencari. Masing-masing metodeu saran ngagaduhan efek samping kumaha toleransi kecap string match. Kanggo tip  greyspace ,  camelCase  atanapi  txt2number :

Laporan "milarian" dipicu nalika kecap anu teu dipikanyaho sacara universal teu dipalire dina hiji kalimat.
 * dibere $ wjgrey atanapi $ wjcamel, mendakan $ wjb ... $ char, dina bentuk saderhana atanapi dina bentuk copyspace.
 * $ txt2n bakal cocog sareng $ t2n atanapi $ t2np.
 * Eureun kecap diaktipkeun pikeun kasus ekstrim (dina periphery) tina frasa grey_space atanapi camelCase. Conto anu nganggo $ an, $ sareng sareng $ a anu $ ihoa pakait sareng $ mihs.

Masing-masing tina jinis patandingan di handap ieu ngandung sareng ngalegaan toléran pertandingan anu saacanna saméméhna:


 * Hiji "frase pasti" "dina tanda petik" bakal toléran (ngagabung sareng) copyspace. Dibikeun $ tepat_phrase atanapi $ tepatna, éta pakait sareng $ persisbracket.


 * A greyspace_phrase dimimitian cek pamendakan sareng  stop word .


 * Dibikeun onta $, éta  salian ti  cocog sareng $ kaméra, di handap pikeun kasus, sabab CirrusSearch henteu sénsitip kana korespondensi.

Urut halaman halaman nyegah anjeun tina nuliskeun tanda petik pikeun milarian dua kecap. Tanpa tanda petik, hiji kecap pasangan indéks dianggo dina ranking halaman, salian pikeun milarian dua kecap dimana waé dina halaman.

Sababaraha parameter napsirkeun frasa kosong, tapi anu lain, sapertos $ insource, napsirkeun ngan biasana "kutipan antara tanda petik".

Catet yén sadaya panungtun henteu peka.

Perhatikeun kumaha kecap "frasa tepat" napsirkeun karakter dipasang: kolon salaku hurup, tapi sanes karakter embedded_underscore. Kajadian anu sami lumangsung sareng karakter koma $ komma dina sajumlah.

Dibikeun $ inthisword, CirrusSearch, nalika dina kontéks "frasa tepat" (anu kalebet kontéks parameter  insource ), moal cocog sareng $ in, $ this or $ word, tapi bakal cocog sareng $ inthiswordcolon.

Upami teu kitu, émut pikeun CirrusSearch,  'kecap-kecap aya serat, nomer atanapi gabungan sareng dua, sareng pasualan teu janten masalah' .

Pilarian kecap umum ngagunakeun karakter ruang sareng agrésif sareng turunan, sareng nalika kecap anu sami dipasihan ku copyspace atanapi karakter camelCase, aranjeunna agrésif kalayan frasa sareng subwords.

Nalika kecap umum sapertos "of" atanapi "the" kaasup kana frasa di copyspace, aranjeunna teu dipaliré supados langkung pakait agrésif.

Istilah teang greyspace_phrase, atanapi camelCase atanapi txt2number, pakait sareng kecap-kecap anu silih tukeur. Anjeun tiasa ngagunakeun salah sahiji tina tilu bentuk ieu. Ayeuna $ camélcase cocog sareng $ camelCase sabab Milarian henteu sénsitip, tapi $ camelCase2 cocog sareng $ camelcase2 sabab camelCase langkung agrésif. Janten sesa Milarian, subword "kecap" henteu peka sensitipna. Ku ngabandingkeun, "frase pasti" berorientasi kana copyspace sareng teu ngalalirkeun transisi angka atanapi huruf ageung sareng alihan. "Frasa anu dicutat" henteu masalah sensitif.

Tina tabél, urang tiasa nganggap yén paluruh dasar $ 1 mangrupikeun jumlah tina pencarian dasar $ 2 sareng $ 3.

Ku nanyakeun patarosan sareng nomer, urang bakal mendakan yén:


 * $ Plan9 atanapi $ Plan_9 pakait sareng: $ plan9, $ plan9, $ planning9th, $ planning92, $ rencana * $ plan92 ngan ukur $ $93 (sanés masalah sensitif) * planét $ pakait sareng $ plan94 atanapi $ planét.

Béntang bintang asterisk $ pakait sareng sekuen hurup sareng angka dina kecap anu dipasihkeun,  tapi sanés karakter anu ngamimitian . Hiji atanapi langkung karakter, persentase kecap, kedah sateuacanna $ asterisk1 karakter.


 * Upami bagian awal ngan ukur hurup, éta bakal ngawateskeun susuratan kana sekuen (nol atanapi langkung) hurup. * Upami ngan ukur nomer, ieu bakal ngawates patandingan kana nomer nomer (nol atanapi langkung), ogé kalebet hurup ordinal (st, nd, rd), hurup modal atanapi singgetan waktos (am atanapi pm); sareng bakal pakait sareng totalitas (dua sisi) a nomer perpuluhan. * Upami teu kitu, koma dianggap bagian tina sajumlah, tapi titik perpuluhan dianggap karakter copyspace sareng bakal ngahapus dua nomer. * Dina "frasa pasti", pakait sareng pamangkungan sareng komposisi.

$ Liar wildcard ngagambarkeun hurup atanapi nomer; $ Bsq ogé katampa, tapi $ bsqast henteu dipikanyaho.

Wildcards mangrupikeun paluruh dasar pikeun kecap, frasa sareng sumber, sareng tiasa ogé alternatif pikeun (sababaraha) maluruh milarian ungkapan biasa (katutupan engké).

Nempatkeun karakter tilde $ $ saatos kecap atanapi frasa ngaktifkeun panéangan anu kabur.


 * Kanggo frasa, éta disebat 'jarak deukeut', sabab kecap-kecap 'proksimal' ditolerir ku frasa anu langkung-langkung sanés ngan 'pas éksprési'. * Contona, $ persis12p pakait sareng $ pasti. * Kanggo kecap, éta hartos karakter tambahan atanapi  dirobih  karakter. * Kanggo frasa, panéangan kabur  meryogikeun  integer nyarioskeun sabaraha kecap tambahan pas, tapi kanggo kecap anu kabur anu jelas tiasa gaduh frékuénsi perpuluhan,  standar  kanggo $ word05 ($ wordtilde), dimana henteu dua huruf maksimum tiasa kapendakan, dirobih atanapi ditambah, tapi henteu kantos dua. * Kanggo frasa jarak, nomer ageung tiasa dianggo, tapi ieu mangrupikeun panyarian "mahal" (lambat). * Kanggo hiji kecap $ wordtilde1 langkung akurat kalayan jarak éditan 2 (standar) sareng $ wordtilde9 kirang akurat,

Pikeun nilai jarak deukeut anu cocog pikeun cocog sabalikna (ti kénca ka kénca), cacah sareng piceun sadaya kecap tambahan sareng tambihan dua kali jumlah kecap sésana dikurangan hiji. (Dina basa sanés, tambahkeun ganda jumlah bagéan). Pikeun algoritma jarak deukeutna, tingali [$ esslop Elasticsearch slop].

Tanda kutip mareuman hémang, $ appendtilde si tilde ngaaktivasi pamangkungan.

Insource
Milarian ku sumber tiasa dianggo pikeun milari kecap-kecap   anu dikaluarkeun dina kaca, tapi dipigawe pikeun milari frasa naon anu anjeun tiasa mendakan - kalebet pananda MediaWiki, dina halaman naon waé, kecuali alihan. Ieu frasa lengkep teu malire copyspace: $ issa pakait sareng $ nagara.

Insource pelengkap. Di hiji sisi, sacara langsung milarian téks pinuh pikeun naon waé kecap anu aya dina wikitext. Di sisi anu sanés, anjeun tiasa ngolah régexp pikeun milarian naon waé. Regex mariksa sadaya karakter téks dina daptar halaman anu dipasihan; aranjeunna henteu ngagaduhan kecap indéks pikeun nyepetkeun hal-hal, sareng prosés lirén upami anjeun kedah ngajalankeun langkung ti dua puluh detik. Regex dilaksanakeun kapungkur, pikeun ngawatesan scanning anu henteu perlu di tingkat karakter, anjeun muka daptar halaman (domain milarian) anu dipilih ku milarian anu diindéks ditambah kana pamundut salaku "klausa" sareng ngalakukeun ieu pikeun sadayana pamenta regex. Insource tiasa maénkeun dua peran, sareng calon anu paling saé pikeun $ insourcearg biasana $ insourcearg2, dimana  arg  sami.

Rumpaka pikeun regexp nyaéta $ insource tanpa rohangan, teras $ regexp. (Teu aya parameter sanésna anu ngijinkeun rohangan. Sakabéh parameter, kecuali $ regex, langkung lega nampi rohangan saatos titik.)

Sumber anu saestuna milarian sareng fungsi milarian éksprési biasa sami dina sababaraha cara:


 * Kadua milarian ngan dina wikitext. * Sanés anjeun mendakan barang "asalna" ku [[$ panyalambungan | panyebaran]. * Sanes dipilampah, sumebar atanapi deukeutna. * Kadua hoyong hasil pangsaeutikna tiasa sareng berpungsi gancang nalika dibarengan ku klausa anu sanés.

Nanging sadayana maluruh saestuna teu malire copyspace; Pilarian wildcard henteu cocog sareng copyspace, janten regex mangrupikeun hiji-hijina jalan pikeun mendakan karakter karakter anu pasti  sareng sagala , contona, dua rohangan. Regex mangrupikeun kelas alat anu milarian béda anu ngagampangkeun cocog sareng string literal (dasar, pamulaan dimimitian) sareng ngamungkinkeun cocog ku ungkapan metacharacter (panggunaan maju) dina wiki. Tingali $ regexanchor di handap.

Rarangken sareng ruang nama

Kanggo Milarian, istilah ruang ngaran dianggo pikeun netepkeun domain milarian awal. Gantina milarian sadaya wiki, standarna mangrupikeun ngaran tempat utama (ruang utama).

Namung ngaran ngaran ukur tiasa ditetepkeun dina pamundut kotak search. Éta mangrupikeun istilah munggaran atanapi istilah pangahirna, dina parameter  awalan .

Anjeun tiasa milarian dua atanapi langkung ngaranspor dina panel  Advanced  tina bar pencari  , anu aya di luhureun sadaya halaman hasil pamilarian, Special: Search. Domain teang anjeun, sapertos profil namespace, tiasa dihartikeun di dieu. Daptar alamat ngaran bakal némbongan dina halaman mimiti hasil pamilarian di hareup pikeun nunjukkeun domain panéangan. Pikeun mareuman ieu, pilih ngaranspasi standar (dipidangkeun dina tanda kurung), pilih "Émut" sareng pencét Milarian.

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.

Enter a namespace name, or enter, or enter a     colon for mainspace. All does not include the File namespace. File includes media content held at Commons such as PDF, which are all indexed and searchable.

When File is involved, a namespace modifier  has an effect, otherwise it is ignored.

Namespace aliases are accepted.

As with search parameters, local and all must be lowercase. Namespaces names are case insensitive.

The prefix: parameter matches any number of first-characters of all pagenames in one namespace. 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 or ' 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.

The prefix parameter goes at the end so that pagename characters may contain " quotation marks.

The Translate extension creates a sort of "language namespace", of translated versions of a page. But unlike namespace or prefix, which create the initial search domain, the inlanguage parameter is a filter of it. (See the next section.)

Exclude content from the search index
Content can be excluded from the search index by adding. This will instruct CirrusSearch to ignore this content from the search index (see for more context).

Additionally content can be marked as auxiliary information by adding. 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.

Filters
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. The search parameters below are filters for which there may be multiple instances.

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.)

Intitle and incategory
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. Intitle and incategory are old search parameters. Incategory no longer searches any subcategory automatically, but you can now add multiple category pagenames manually.
 * cow*
 * Find articles whose title or text contains words that start with cow
 * intitle:foo
 * Find articles whose title contains foo. Stemming is enabled for foo.
 * intitle:"fine line"
 * Find articles whose title contains fine line. Stemming is disabled.
 * intitle:foo bar
 * Find articles whose title contains foo and whose title or text contains bar.
 * -intitle:foo bar
 * Find articles whose title does not contain foo and whose title or text contains bar.
 * incategory:Music
 * Find articles that are in Category:Music
 * incategory:"music history"
 * Find articles that are in Category:Music_history
 * 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

Since Regular expression searches are supported for intitle:
 * intitle:/regex/, intitle:/regex/i

Everything written in the #Regular expression searches is also valid for these searches, including warnings.

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.

Note that some deepcat searches return incomplete results. See bug for more details.

Linksto
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. .)

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:
 * 1) linksto: "Help:Cirrus Search"
 * 2) linksto: Help:Searching
 * 3) linksto: H:S

finds articles that mention "CirrusSearch" but not in a wikilink.

Hastemplate
You can specify template usage with. 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.

Inlanguage
For installations with the Translate extension, inlanguage is important for highly refined searches and page counts.


 * inlanguage: language code

will produce search results in that language only.

For example


 * to count all Japanese pages on the wiki
 * all: inlanguage: ja


 * to filter out German and Spanish pages in the Help namespace
 * help: -inlanguage: de -inlanguage: es


 * to ignore Translate, and where English is the base language, add
 * 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.:


 * To see only JSON pages:
 * contentmodel:json

subpageof
To find sub-pages.
 * subpageof: ParentPage

For example


 * To find all subpages of CirrusSearch.
 * subpageof:CirrusSearch


 * Use double quotes if the parent page contains spaces.


 * subpageof:"Requests for comment"

Articletopic
The articletopic: keyword allows filtering search results by topic. For possible topics see. 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.

Page weighting
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
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:
 * morelike:page name 1|page name 2|...|page name n
 * Find articles whose text is most similar to the text of the given articles.
 * morelike:wasp|bee|ant
 * Find articles about stinging insects.
 * morelike:template:search|template:regex|template:usage
 * Find templates about regex searching for template usage on the wiki.
 * 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:

These settings can be made persistent by overriding  in System message.
 * 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 ( | ): use only the field data. Defaults to : the system will extract the content of the   field to build the query.
 * cirrusMltPercentTermsToMatch : The percentage of terms to match on. Defaults to 0.3 (30 percent).
 * Example:

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  sort 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,recent Technically "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.

For example
 * 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
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   message. replaces the contents of  if the former is specified. The syntax is a bit funky but was chosen for simplicity. Like prefer-recent, boost-templates is only applied when using the default  sort order. Some examples:


 * File:boost-templates:"Template:Quality Image|200%" incategory:china
 * Find files in the China category sorting quality images first.


 * File:boost-templates:"Template:Quality Image|200% Template:Low Quality|50%" incategory:china
 * Find files in the China category sorting quality images first and low quality images last.


 * File:boost-templates:"Template:Quality Image|200% Template:Low Quality|50%" popcorn
 * 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.

Regular expression searches
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.

These return much much faster when you limit the regexp search-domain to the results of one or more index-based searches.

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 develop a simple filter to generate the search domain for the regex engine to search:


 * insource:"debian.reproducible.net" insource: / debian\.reproducible\.net / 
 * insource:"c:\program files (x86)" insource: / C\:\\Program Files \(x86\) /i 
 * insource:"{ {template}}" insource: / "{ {template}}<\/tag>" /
 * insource:"[ [title|link label]]'s" insource: / "[ [title|link label]]'s" /
 * insource: / regexp / prefix:{ {FULLPAGENAME}}

The last example works from a link on a page, but { {FULLPAGENAME}} doesn't function in the search box.

For example: Special:Search/insource:/regex/ prefix: finds the term regex on this page.

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 an HTML 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 creating one the 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. The match will be highlighted. 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.

Metacharacters
This section covers how to escape metacharacters used in regexp searches For the actual meaning of the metacharacters see the explanation of the syntax.

For example:


 * 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.

Refining with an exact string

 * refinining 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.


 * instead of
 * is as good as
 * But  always.
 * And .  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:
 * 1) Write   out. (The /" delimiters "/ are not shown.)
 * 2) Replace   with   (previous double-quote: stop, concatenate, quote restart).
 * 3) Replace   with   (stop, concatenate, start).
 * 4) You get , showing concatenation of the two methods.

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.
 * insource:"[ [link|2\3?]]\" insource:/"[ [link|2\3?]]< "\/" tag>"/

There are some notable differences from standard regex metacharacters:


 * The  or   are not reserved for matching a newline. To search for a string that contains a newline, you can do a search like   which means not a curly brace, then two curly braces, then any two characters except a curly brace, space, or pipe, then a  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:


 * 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 needed. 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   does, but without regard to the number of character positions, or the range in each position, so   works, and even   works.

Regex on titles
The insource keyword does only search the page source content. To run regex searches on the title strings intitle:/regex/ can be used.

Advanced example
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  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.

Paluruh geografis

terbatas

Anjeun tiasa ngawatesan milarian anjeun ka halaman anu dikenalkeun caket sareng sababaraha koordinat geografis anu parantos jelas. Koordinat tiasa ditetepkeun salaku pasangan, atanapi ku cara nyayogikeun judul halaman dimana kéngingkeun koordinat. Jarak pikeun ngabatesan pilarian tiasa napel, upami hoyong. Conto:


 * neartitle:"San Francisco"
 * neartitle:"100km,San Francisco"
 * nearcoord:37.77666667,-122.39
 * nearcoord:42km,37.77666667,-122.39

boosted
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

File properties search
Since MediaWiki 1.28, CirrusSearch supports indexing and searching of properties of files in the  namespace. This includes:
 * file media type
 * MIME type
 * size
 * width & height
 * resolution
 * bit depth for files that support these

filetype
Searching for file type allows to retrieve files according to their classification, such as office documents, videos, raster images, vector images, etc. The following types currently exist:



This list may be extended in the future. See also  constants in.

The syntax of the search is: filetype:{type}. Example:

filetype:video - looks for all videos

The filetype search is not case-sensitive.

filemime
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.

Examples:


 * filemime:"image/png" - look for files with MIME type exactly
 * filemime:pdf - look for all PDF documents
 * -filemime:pdf - skip all PDF documents (notably on Commons)

The MIME type search is not case sensitive.

filesize
Search for file of given size, in kilobytes (kilobyte means 1024 bytes). The syntax is:


 * filesize:{number} or 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

Examples:


 * filesize:>20 or filesize:20 - files 20KB and bigger
 * filesize:<1024 - files smaller than 1MB
 * filesize:100,500 - files with sizes between 100KB and 500KB

File measures
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

Where  can be:

filew or filewidth - file width

fileh or fileheight - file height

fileres - file resolution (see above)

filebits - file bit depth

Examples:

filew:>800 fileh:>600 - files that are at least 800x600 pixels in size

filebits:16 - files with 16-bit color depth

fileheight:100,500 - file between 100 and 500 pixels high

Wikibase search
The extension defines some search keywords in order to make it easier to search for certain Wikibase items. This is useful on and other Wikibase sites, including to search for images with Structured data on Wikimedia Commons. See for details.

Cross-wiki search results
The search on Wikimedia projects includes improved cross-wiki search results (also known as interwiki search results, sister projects search results).

Explicit sort orders
In addition to the default relevance based sort CirrusSearch can provide results a few other explicit sort orders. Specifying a sorting order other than  will disable all search keywords that affect scoring, such as   or. The keywords will still be parsed, but they will have no effect.

Sorting options are currently available from the MediaWiki API by providing the  parameter.

Sorting options can be manually added to a search URL by adding, for example https://www.mediawiki.org/w/index.php?search=foo&sort=last_edit_desc.

Valid sort orders include:

Antarbeungeut pilihan canggih

[[$ gambar-asi | jempol | Antarbeungeut milarian maju

Éta AdvancedSearch nambihan antarbeungeut anu ditingkatkeun dina halaman teang, ngamungkinkeun anjeun ngagunakeun sababaraha pilihan anu dijelaskeun di luhur dina cara anu ramah. Tingali didieu pikeun manual pangguna.

Tingali ogé
 * Parantosan Panyatur - fitur pencarian tambahan CirrusSearch
 * $ glossary - harti, kontéks sareng tautan pikeun istilah anu aya hubunganana.
 * Tingali $ oldsearch kanggo inpormasi anu langkung lengkep ihwal kamekaran sareng debut CirrusSearch.
 * Tingali $ oldsearch kanggo inpormasi anu langkung lengkep ihwal kamekaran sareng debut CirrusSearch.


 * Tingali Bantuan: Milarian kanggo MWSearch, dianggo ku seueur wiki anu teu gaduh sambungan pamilarian.

Tautan éksternal

 * [$ lucene Ti Lucene], dokuméntasi pohara relevan.
 * (as of 2017-12-06)
 * Extension:CirrusSearch/Profiles – setel adjustable anu mangaruhan sababaraha aspék indexing
 * Wikimedia blog articles related to search