To allow searches to be restricted by content model (e.g. to javascript pages, or to geo-shapes), ContentHandler::getFieldsForSearchIndex() and getDataForSearchIndex() should expose the content model name to the search engine. A keyword like "contentmodel" or "pagetype" could be used to filter by it.
QUESTION: should we expose the internal distinction between content model and media type, between uploaded media and page content? Or should we rather hide that distinction?
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add contentmodel: query feature | mediawiki/extensions/CirrusSearch | master | +42 -0 | |
| Add content model indexing | mediawiki/core | master | +8 -2 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T91505 [Epic] Adding new datatypes to Wikidata (tracking) | |||
| Resolved | • Jonas | T57549 [Story] Add a new datatype for geoshapes | |||
| Resolved | WMDE-leszek | T155137 Allow filtering for type when search in data namespace | |||
| Resolved | Smalyshev | T156371 ContentHandler should expose the content-model to search engines. |
Change 334412 had a related patch set uploaded (by Smalyshev):
Add content model indexing
When we have multiple content pages, we probably will have to put array there instead of one item, but ES supports it.
Yay for the patch!
@Smalyshev does this automatically introduce a keyword? Can I use content_model:javascript in the search box now?
Re multiple content objects (MCR): it's probably sufficient to make the model of the main content object searchable. Other slots tend to be auxilliary, like license info, categories, quality assessment, etc. We should index the content of all the slots, but the model of the other slots isn't so interesting.
No, keywords are handled in different code (CirrusSearch, not core). I can add patch for that too.
As for indexing secondary slots, I think we need to have bigger discussion on how MCR will be indexed. Current indexing assumes each field has only one instance, but that may not be true for MCRs. Let's have a dedicated task and discuss it.
Also I think to make it actually work you'd need a reindex (probably should be coordinated with other reindexes via T147505).
Change 334715 had a related patch set uploaded (by Smalyshev):
Add contentmodel: query feature