Page MenuHomePhabricator

Automatic category redirects
Open, LowPublicFeature

Assigned To
None
Authored By
bzimport
Aug 30 2005, 6:05 PM
Referenced Files
F2276: category-redir-api.patch
Nov 21 2014, 8:48 PM
F2275: category-redir.patch
Nov 21 2014, 8:48 PM
F2274: patch
Nov 21 2014, 8:48 PM
Tokens
"Like" token, awarded by Pppery."Like" token, awarded by Lens0021."Like" token, awarded by Wordna."Like" token, awarded by Leventov."Like" token, awarded by Liuxinyu970226."Like" token, awarded by Kozuch."Like" token, awarded by Nemo_bis."Love" token, awarded by He7d3r.

Description

Also proposed in the Community-Wishlist-Survey-2016. The proposal received 47 support votes and was ranked #25 out of 265 proposals. View full proposal with discussion and votes here.


Author: p_simoons

Description:
Supposing category:A redirects to category:B.
Would it be feasible to automatically move all articles placed in cat:A into cat:B instead?
Alternateively, would it be possible to create a Specialpage that lists all categories that are redirects, so that a bot can do the moving?


See Also: T7346

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Related URL: https://gerrit.wikimedia.org/r/65176 (Gerrit Change I29a629a514f9568d0ee4d967c516dfd599dc11ba)

Tyler: The patch received a -1, do you plan to rework it?

If I ever have free time again (read: probably not for a while), I offer to help Tyler address some of the issues with the patch.

(In reply to comment #76)

If I ever have free time again (read: probably not for a while), I offer to
help Tyler address some of the issues with the patch.

That would be great. I don't have much free time myself, although once I do I'll definitely work on it.

(In reply to comment #77)

(In reply to comment #76)

If I ever have free time again (read: probably not for a while), I offer to
help Tyler address some of the issues with the patch.

That would be great. I don't have much free time myself, although once I do
I'll definitely work on it.

yeah, somebody should make a graph of number of commits to mediawiki by volunteers vs when school semester starts.

Remove milestone 1.22 - Given that this has somewhat stalled due to lack of time on the part of interested parties, seems unlikely it could possibly make it to 1.22.

Unknown Object (User) removed a subscriber: Unknown Object (User).Nov 28 2014, 12:52 PM

T77903 isn't a duplicate of this task, it's more of a relatively easy fix until we get those long standing difficult core problems solved, which may not be before a very long time.

This task was mentioned in https://www.mediawiki.org/w/index.php?title=Outreach_programs/Possible_projects&oldid=1404823#Very_raw_projects as a possible candidate for Google Summer of Code or similar programs. Do you think it is a good candidate?

Wikimedia will apply to Google Summer of Code and Outreachy on Tuesday, February 17. If you want this task to become a featured project idea, please follow these instructions.

@Parent5446, this task is assigned to you. Do you want to work on it or propose it to the next GSoC/Outreachy round?

@Bawolff @Parent5446 Has this already been done? If not, is there interest in pushing this for upcoming GSoC round?

Has this already been done?

No.

There is a partial patch from way back. See comments on gerrit.

(In reply to comment #63)

Question:

Is there a potential mentor willing to help potential students interested in
this project?

Yes me :)

Does this still hold true @Bawolff?

In T5311#1095413, @NiharikaKohli wrote:

(In reply to comment #63)

Question:

Is there a potential mentor willing to help potential students interested in
this project?

Yes me :)

Does this still hold true @Bawolff?

Not really. Like if there was a student who really super wanted to do this idea and no other, maybe, but generally I'd rather not mentor this idea, this round.

This is a message posted to all tasks under "Re-check in September 2015" at Possible-Tech-Projects. Outreachy-Round-11 is around the corner. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.

This is a message sent to all Possible-Tech-Projects. The new round of Wikimedia Individual Engagement Grants is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after (T105414). If someone is interested in obtaining funds to push this task, this might be a good way.

This is the last call for Possible-Tech-Projects missing mentors. The application deadline for Outreachy-Round-11 is 2015-11-02. If this proposal doesn't have two mentors assigned by the end of Thursday, October 22, it will be moved as a candidate for the next round.

Interested in mentoring? Check the documentation for possible mentors.

As previously mentioned, this task is moved to 'Recheck in February 2016' as it doesn't have two mentors assigned to it as of today, October 23 - 2015. The project will be included in the discussion of next iteration of GSoC/Outreachy, and is excluded from #Outreachy-11. Potential candidates are discouraged from submitting proposals to this task for #Outreachy-11 as it lacks mentors in this round.

NOTE: This task is a proposed project for Google-Summer-of-Code (2016) and Outreachy-Round-12 : GSoC 2016 and Outreachy round 12 is around the corner, and this task is listed as a Possible-Tech-Projects for the same. Projects listed for the internship programs should have a well-defined scope within the timeline of the event, minimum of two mentors, and should take about 2 weeks for a senior developer to complete. Interested in mentoring? Please add your details to the task description, if not done yet. Prospective interns should go through Life of a successful project doc to find out how to come up with a strong proposal for the same.

@Parent5446 this task has been assigned to you. Do you plan on working on this or mentoring this for the upcoming Outreachy-13 round?

instead of changing the indexes for every member pages of a redirected category, couldn't there exist an index within target categories for listing the other category names that are redirected to it?
In that case, listing the content of the category would list all pages of the target category and of the source redirected categories, merged into a single list to sort.
This could however have an impact on performance if there are many redirected categories to list.

Note that the source category would still list their specific members (but to view them you have to visit these redirected categoties with redirect=no) which remain nidexed there and still need maintenance (using a job queue, or probably still preferably by using some auhtorized bots that may be paced down and will not run before the new redirect is accepted and not reverted) on all member pages to empty the contents of the redirected categories.

Note that most often, the redirected categories just come from an edit to rename it, while preserving its description and edit history into the new target category; however the member pages are still not recategorized. For this reason, renaming a category should still not create a new category with the old name but just the "#REDIRECT". it should better create by default a new category with a template showing a soft redirect by default, so that its members are still vieable in a single click, even if they are also listed in the merge list shown when viewing the target category.

Adding a hard redirect before the soft redirect template in the category description page should better delayed.

Or if possible, the #REDIRECT in a category should not be immediately followed when visiting it via any link on any page as long as it's not empty. (this does not require any edit on many articles and no change in the indexes on the database, just a small patch in MediaWiki to provide better navigation)

@Parent5446 this task has been assigned to you. Do you plan on working on this or mentoring this for the upcoming Outreachy-13 round?

I don't have time to work on it (my patch in Gerrit has been untouched for ages), but I can help mentor it since I remember most of the problems involved.

Looks like from the community wish survey results, that this feature is quite in high demand, see the updated task description :)

@Parent5446 How much work is remaining to be done? Would you be interested in mentoring this for GSOC 2017/ Outreachy Round 14?

This task was proposed in the Community-Wishlist-Survey-2016 and in its current state needs owner. Wikimedia is participating in Google Summer of Code 2017 and Outreachy Round 14. To the subscribers -- would this task or a portion of it be a good fit for either of these programs? If so, would you be willing to help mentor this project? Remember, each outreach project requires a minimum of one primary mentor, and co-mentor.

@Parent5446 Hi! We are in the process of recruiting tasks suitable for volunteers from the community wishlist for the Wikimedia-Hackathon-2017. This task seems like a good fit, but I'm wondering even if it gets picked up would you be around to answer any questions someone might have? Also, if someone claims it, would it be a start over? The hackathon is in May b/w 19-21.

Removing Possible-Tech-Projects as we are planning on killing it soon! Also cannot add Outreach-Programs-Projects as "Contributors" team is working on it!

Tacsipacsi changed the subtype of this task from "Task" to "Feature Request".Jan 10 2022, 9:18 PM
Tacsipacsi added a project: Hungarian-Sites.
Tacsipacsi updated the task description. (Show Details)
Tacsipacsi added a subscriber: Tacsipacsi.

Change 65176 had a related patch set uploaded (by Winston Sung; author: Parent5446):

[mediawiki/core@master] Automatically move category members when redirected

https://gerrit.wikimedia.org/r/65176