Page MenuHomePhabricator
Create Task
Maniphest T93527

More search options for Special:SearchTranslations: type,status, lang, grp, case
Closed, ResolvedPublic
Actions

Assigned To
Phoenix303
Authored By
Phoenix303
Mar 22 2015, 6:31 PM
Tags
Referenced Files
F107178: Screenshot_from_2015-03-30_16:52:26.png
Mar 30 2015, 9:53 PM
F106829: Screenshot_from_2015-03-29_13:22:25.png
Mar 29 2015, 6:31 PM
F102979: Screenshot_from_2015-03-23_03:45:46.png
Mar 23 2015, 9:43 AM
F102821: Screenshot_from_2015-03-22_13:50:55.png
Mar 22 2015, 6:52 PM
F102815: Screenshot_from_2015-03-22_02:25:36.png
Mar 22 2015, 6:31 PM
Subscribers
Aklapper
Amire80
Fito
Kghbln
Linedwell
• Manybubbles
Nemo_bis
View All 12 Subscribers

Description

A translator may know the exact kind of special search to perform. For this, the translator should have an option for an advanced search to get more specialized results from the tool. Searching with parameters:

  • type (default is msgall): This gives the type of search.
    • "key" for message-key searches
    • "exact" for exact matches
    • "msgany" to match any word in the query string
    • "msgall" to match all words in the query string
  • status (default is all): This gives the status of result messages.
    • "all" for all messages
    • "translated" to match translated messages
    • "untranslated" to match untranslated messages
    • "outdated" to match outdated messages
  • lang (default from ULS): This gives the target language of the search as 2 letter code. e.g. de for German, fr for French and so on.
  • grp (default is all): This gives the message group that's selected for the search. e.g. MediaWiki, MediaWiki (core) etc.
  • case (default is false): This gives whether the search is case sensitive or not.

Example

Screenshot_from_2015-03-23_03:45:46.png (539×959 px, 81 KB)

Along with this, the search will have autosuggest for tag values.
Example

Screenshot_from_2015-03-30_16:52:26.png (434×731 px, 30 KB)

Related Objects
Search...

Event Timeline

Phoenix303 created this task.Mar 22 2015, 6:31 PM
Phoenix303 raised the priority of this task from to Needs Triage.
Phoenix303 updated the task description. (Show Details)
Phoenix303 added a project: MediaWiki-extensions-Translate.
Phoenix303 added subscribers: Phoenix303, Nemo_bis, Nikerabbit and 5 others.
Phoenix303 updated the task description. (Show Details)Mar 22 2015, 6:52 PM
Phoenix303 set Security to None.
Phoenix303 updated the task description. (Show Details)Mar 23 2015, 9:43 AM
Aklapper renamed this task from Advanced search options for Special:SearchTranslations to More search options for Special:SearchTranslations: type,status, lang, grp, case.Mar 23 2015, 9:52 AM
Phoenix303 mentioned this in T92929: Reinvent Translation Search.Mar 24 2015, 1:08 AM
Nikerabbit triaged this task as Low priority.Mar 27 2015, 5:55 PM

I would like to see user scenarios backing these requirements. Personally I just search first and use the facets to filter down the results if needed.

Phoenix303 updated the task description. (Show Details)Mar 29 2015, 6:31 PM
Kghbln subscribed.Mar 30 2015, 7:51 PM

I personally think it will be nice being able set the values that currently appear in the facets after the search prior to the search. This is because I usually only want to get results for MediaWiki and in the language I translate to. 100% of my searches are messages I have seen live which need to be enhanced by some kind.

Phoenix303 updated the task description. (Show Details)Mar 30 2015, 9:53 PM
Linedwell subscribed.Mar 31 2015, 8:07 AM

I think it should be a good initiative.

Fito subscribed.EditedApr 3 2015, 12:03 AM

Thanks for working on this feature! I have a question:

Will those search parameters appear as a (faded out) prompt (a.k.a. placeholder text) inside the field? Or are the mockups showing text typed by the user only? Either way, I think the search parameters should be discoverable right in the UI, without having to open a separate help page. Maybe it’s a good idea to add a help balloon next to the search field, which would contain the list of available parameters and a brief description of what they do.

Phoenix303 added a comment.Apr 3 2015, 9:04 AM

Thank you all for your feedback.

@Fito The mockup shows text entered by the user and thank you for suggestions to support placeholder text and help tooltip. This mockup is not a final design and more features can be added based on feedback.

Nemo_bis assigned this task to Phoenix303.May 2 2015, 2:04 PM

As agreed, Phoenix will file three (kinds of) subtasks for this:
a) adding operators for filters which already exist (like language and group)
b) adding new filters and corresponding operators, which probably require ElasticSearch index changes (like message key, type, case)
c) status searches, e.g. "outdated translation containing word", with any further subtask for API dependencies or "cross language search" overlaps (e.g. "message key untranslated in language X", in addition to the standard "source message containing word X untranslated in language Y which is T55656)

Nikerabbit moved this task from Backlog to search on the MediaWiki-extensions-Translate board.Jul 21 2015, 8:01 PM
Nemo_bis added a project: Translation-search.Aug 17 2015, 9:35 AM
Nemo_bis removed a subtask: T98559: Autosuggest feature to access operators.Aug 17 2015, 9:43 AM
• WP.NICKNAME.22 subscribed.Aug 24 2015, 2:46 AM
This comment was removed by Aklapper.
Nemo_bis closed subtask T97944: Add operators for new filters (like state, case) as Resolved.Aug 24 2015, 10:59 AM
Nikerabbit closed subtask T97943: Add operators for filters which already exist ( language and group ) as Resolved.Apr 18 2016, 12:27 PM
Nemo_bis mentioned this in T90144: Search for keys (API).Mar 29 2017, 8:51 AM
Aklapper closed this task as Resolved.Sep 30 2019, 10:12 AM

All subtasks are resolved hence assuming this task is also resolved. If it is not, please reopen and elaborate what is needed, plus update/unset the assignee. Thanks.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL