First mentioned here by User:Jonteemil.
Is there a way to add the ability to search in contributions of a specific user? For example, imagine I want to find all of my contributions in which I've added "Hello" to the page's source. We can currently search the page's source using insource, but we don't have something like byuser to limit the search to specific user(s).
See Also: T12788: Filter page histories by user, or contributions by title
For example, imagine I want to find all of my contributions in which I've added "Hello" to the page's source.
Hi, what is the underlying use case for that?
Hi, what is the underlying use case for that?
Hi. One situation can be when you want to find behavioral similarities between a number of users. For example, you want to see if they've inserted the same suspected text in different articles or not.
Another situation can be searching your own contributions. This can be useful, especially when working with stats. Imagine you want to find out how often an admin notifies the blocked user from the block, or you want to check for all public domain images uploaded by a user etc. I can think of some project-specified uses as well, such as the number of license reviews a Commons license reviewer has done. If these examples aren't enough, I can think of some other ones.
Nonetheless, I can think of technical limitations.
I want to useit to find all the files uploaded by me that have been extracted from a PDF. In the source parameter in {{Logo fur}} in all of them I have written ”extracted from /pdf/”. I would therefor search ”extracted from” and by user(s) Jonteemil and find the wanted files
While perhaps interesting, I can't see this fitting into CirrusSearch. Dealing with the entire history of revisions is outside it's scope.
Closing out low/est priority tasks over 6 months old with no activity within last 6 months in order to clean out the backlog of tickets we will not be addressing in the near term. Please feel free to reopen if you think a ticket is important, but bare in mind that given current priorities and resourcing, it is unlikely for the Search team to pick up these tasks for the indefinite future. We hope that the requested changes have either been addressed by or made irrelevant by work the team has done or is doing -- e.g. upgrading Elasticsearch to a newer version will solve various ES-related problems -- or will be subsumed by future work in a more generalized way.
Re-opening tasks and removing from team workboard per IRC feedback given yesterday and discussion with MPham.