Extension talk:AdvancedSearch

Jump to navigation Jump to search

About this board

Discussion page for technical answers around the Extension AdvancedSearch.

Question:How can I use AdvancedSearch on mobile?

1
103.196.22.125 (talkcontribs)

I only see it on desktop but mobile

Reply to "Question:How can I use AdvancedSearch on mobile?"

Suggestion: Add ascending order (first to last) as sortable options

4
Summary by 197.235.204.181
197.235.68.39 (talkcontribs)

As a user, I'd like to be able to sort search results by last edited dates by ascending order.

As a user, I'd like to be able to sort page creation dates by ascending order, so that I can read the most recent pages about a topic.

As a user, I'd like to be able to sort page creation dates by ascending order, so that I can view the recent files / images (from the file namespace) matching my interests.


Christoph Jauera (WMDE) (talkcontribs)

Hey and thanks for your question! If you uses the AdvancedSearch interface you already can set the sort order as described. Just chose "Edit date - current on top" or "Creation date - current on top" in the "Sorting order" drop-down in the expanded interface.

197.235.59.131 (talkcontribs)

Well, the current sort is based on last to first, compare descending edits (starting from 13 August 2019 -> 1 October 2012) - www.mediawiki.org/w/index.php?title=Special:Search/monkey&sort=last_edit_desc while www.mediawiki.org/w/index.php?title=Special:Search/monkey&sort=last_edit_asc shows results in the ascending direction (from 12 October 2012 to 13 August 2019 ).

The same applies to creation date. So if the current dropdown options are to be followed, it would need two extra items namely "Edit date - current at bottom" or "Creation date - current at bottom", or something like that.

T0lk (talkcontribs)
Reply to "Suggestion: Add ascending order (first to last) as sortable options"
Blinkingline (talkcontribs)
Product Version
MediaWiki 1.33.0
PHP 7.2.24-0ubuntu0.18.04.1 (fpm-fcgi)
MySQL 5.7.28-0ubuntu0.18.04.4
ICU 60.2
Elasticsearch 6.5.4


AdvancedSearch 0.1.0 (76eea63) 16:40, 25 March 2019 GPL-2.0-or-later Easy access to advanced search capabilities on Special:Search Thiemo Kreuz, Gabriel Birke, Tonina Zhelyazkova, Christoph Jauera, Kai Nissen and Tim Eulitz
CirrusSearch 0.2 (2daa9b8) 09:07, 25 March 2019 GPL-2.0-or-later Elasticsearch-powered search for MediaWiki Nik Everett, Chad Horohoe, Erik Bernhardson and others
Elastica 6.0.2 (eee38b0) 07:37, 10 September 2019 GPL-2.0-or-later Base Elasticsearch functionality for other extensions by providing Elastica library Nik Everett and Chad Horohoe

I'm sure this is something I just haven't configured correctly, but can someone point me to how this should be configured?

I'm trying to search multiple categories with Advanced Search. Using the default setup in CirrusSearch, which appears to be

$wgCirrusSearchCategoryEndpoint = '';

and getting the following message:

$wgCirrusSearchCategoryEndpoint should be set to a valid SPARQL endpoint to use deep category search.


So it makes sense that I'm getting the error, I just don't know what this endpoint should look like.

Any assistance?

Bawolff (talkcontribs)
Blinkingline (talkcontribs)

Right, but I would want this for just within my own wiki.


Bawolff (talkcontribs)
Blinkingline (talkcontribs)

What I don't understand really is why it's using DeepCat at all. What i'm looking for in the instance of THISWORD but not THATWORD in 5 different categories, but none of them are Subcategories....


Seems like a lot of work for something that sounds so simple...I suppose I will look for a workaround, since for such a small wiki, this seems like way more work with not a lot of benefit.


Reply to "Error using deepcat"
Revansx (talkcontribs)

Great extension. Thanks!

Please add a feature to allow users to find and select categories to search in the same way that namespaces are selected (as tokens). Thanks! Revansx (talk) 15:20, 24 October 2019 (UTC)

Reply to "Search specific Categories?"

Suggestion: Consider adding preset file dimensions (width and height)

2
Summary by Christoph Jauera (WMDE)
197.235.52.125 (talkcontribs)

As a user, I'd like to quickly search for images of certain sizes to add to a page or use externally.

Proposed solution

  1. Add standard preset options of dimensions, e.g.:
    1. large: >= 1024 x 724
    2. medium : between 1024 x 724 and 640 x 480
    3. small: < 640 x 480

This would make it easier for the average person who may not even know about dimensions to search for files. For example, someone just wants a random cat image to add as a background to their devices like mobile, desktop, etc.

Christoph Jauera (WMDE) (talkcontribs)
Reply to "Suggestion: Consider adding preset file dimensions (width and height)"

Suggestion: Implement ability to search for files by size

2
Summary by Christoph Jauera (WMDE)
197.235.52.125 (talkcontribs)

As a user, I'd like to search files by size, so that I can find files of certain quality or simply a sample files.


Proposed solution

Implement the filesize filter that applies to all files.

Christoph Jauera (WMDE) (talkcontribs)
Reply to "Suggestion: Implement ability to search for files by size"

Suggestion: Add ability to sort items by alphabetical order

9
Leyo (talkcontribs)

In addition to the three sorting order options (relevance, edit date, creation date) I'd like to propose a forth one: alphabetical order.

Trilotat (talkcontribs)

I second this recommendation.

Michael Schönitzer (WMDE) (talkcontribs)

Thank you for your feedback! AdvancedSearch can only support the search options that the search back-end provides. So unfortunately we can't fulfill this currently. To get alphabetical order supported by the back-end please report your needs and usecase to the Team Wikimedia Search Platform who are developing the back-end.

Leyo (talkcontribs)

To its talk page, even though it is currently still red?

Michael Schönitzer (WMDE) (talkcontribs)
Leyo (talkcontribs)

I am not on IRC. I would prefer to communicate using the talk pages. Otherwise, could you please put forward my suggestion?

197.235.200.232 (talkcontribs)

Alphabetic sort was deliberately deactivated, so it is unlikely it will be enabled for wikimedia wikis. See gerrit.wikimedia.org/r/#/q/I745b2c463681cb68c16b9b18a07f79f3ba392d92 .

Leyo (talkcontribs)

Well, that was in May 2018, i.e. long before the AdvancedSearch extension was activated.

197.235.59.131 (talkcontribs)

Advancedsearch is just a "cute" way of interacting with the search engine, and its backend. If it is not supported by the backend, then this extension can't do anything about it.


Also, you're wrong about the timeline. Advancedsearch has been active longer than that ( 2017) as a beta feature.

Reply to "Suggestion: Add ability to sort items by alphabetical order"

Issue: Sortable search results inconsistency

7
197.235.236.246 (talkcontribs)

Apparently it is now possible to sort search results using this GUI. However it has the following issues:

  • Sort direction- it isn't clear of it is ascending or descending
  • when sorting by creation timestamp - the timestamp shown is last edited date, this makes the results confusing because creation date is expected.
  • cirrus sort options- the label changes to a system message when one uses sort options that cirrus supports but this extension doesn't, e.g. "sort=incoming_links_asc" or last edit ascending.
Michael Schönitzer (WMDE) (talkcontribs)

Hi, Thank you for your feedback. About the first question: the text in the option-field should say that the current edited/created are on top – isn't that the case for you or did you not find that understandable? About the last point: there is no keyword for this feature by the backend, would you want those? If so for what for? If not I probably misunderstood you, could you please explain more?

197.235.74.147 (talkcontribs)

Question 1: It is not clear. Or understandable.


Question 3: it is supported by the api and backend, see sort orders .

197.235.55.190 (talkcontribs)

> About the last point: there is no keyword for this feature by the backend, would you want those?

I realized I didn't answer this question. It is simple, the current Graphical User Interface (AdvancedSearch) only shows the sort order in one direction. It should support both ascending and descending order, as the cirrussearch backend does, compare e.g.:

Note: Currently, for whatever reason creation doesn't work on this wiki. It works elsewhere : Topic:V4egn7g6uoxtxokg

197.235.55.190 (talkcontribs)

It is also pretty simple to add other sort orders considering that it is easy enough to just change the URL manually, so there doesn't seem to be any reason why one would exclude them. Maybe they would be made less prominent to avoid confusing the average reader who may not know what they mean.

Michael Schönitzer (WMDE) (talkcontribs)

One more question: What language do you use the interface in?

197.235.68.39 (talkcontribs)

>One more question: What language do you use the interface in?

English ...

Reply to "Issue: Sortable search results inconsistency"

typo in the Sorting Order info

2
Trilotat (talkcontribs)

When clicking on the "i" button for information, the Sorting Order, Description says, "Change the sorting order of results. The standard is that most relevant pagest..."


"pagest" should be "pages."


Also, could "title" be an option?

Michael Schönitzer (WMDE) (talkcontribs)

Thanks! I reported it to the developers: T229216

Reply to "typo in the Sorting Order info"
Pretor~nowiki (talkcontribs)

Is it possible to remove the namespace pane (force it not to load) and keep the advanced search pane?

Gabriel Birke (WMDE) (talkcontribs)

At the moment there is no setting. It should be relatively simple to implement, maybe you can propose such a setting on Phabricator?

As a workaround for your own installation, you can edit the file modules/ext.advancedSearch.init.js and remove/comment out the lines

$advancedSearch.append( buildNamespacesPaneElement(
   state,
   headerContainer,
   namespacePresets,
   namespaceSelection,
   searchableNamespaces
) );

That will disable the namespaces without ill effects.

Reply to "Remove namespace pane"