Some of the filetype: search types, such as "bitmap" or "drawing", are very un-intuitive and hard to remember. We may want to consider creating a configuration where aliases for existing types are specified, so for example one can do filetype:photo and find photos by translating "photo" to "bitmap".
For more info - threads here: https://lists.wikimedia.org/pipermail/wikitech-l/2016-November/086995.html
and here: https://lists.wikimedia.org/pipermail/discovery/2016-November/001355.html
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Enable configuration for filetype aliases | mediawiki/extensions/CirrusSearch | master | +18 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Smalyshev | T150887 Create config more intuitive aliases for filetype: search | |||
| Resolved | • chelsyx | T152728 Analyze access log to see whether we need to add filetype: aliases |
In the long run, a nice UI that makes all these advanced function obvious would be best. But that's a lot of work, and we have a lot of other UI work to do. Adding a few hard-coded aliases would probably be sufficient for now. @EBernhardson suggested, based on the thread, we could look at the query logs to figure out what aliases people are actually using, then hard code. I think that's an excellent idea, as it guarantees the aliases we use are actually useful to people.
@Smalyshev What do you think of this approach?
@Deskana good idea. I'll implement the infrastructure, and then we could configure it based on query data.
Change 323991 had a related patch set uploaded (by Smalyshev):
Enable configuration for filetype aliases
The infrastructure was added, but I don't want to announce this yet since extra aliases have not yet been added.
Yes we still have T152728 for this which I think we can do somewhere in second half of January.