This is for processing title requests.
Basically, it takes articles tagged with {{title}} and adds it to a queue. The tool gives the target given by the tag (if there is one), and a new article booster decides whether the page should be moved. They can decide whether the title given is appropriate or not.
For example, if there is a page titled “Foo” with the tag {{title|Bar}}, the new article booster would see “Foo” -> “Bar” before the article and would decide whether to move the page. They then decide whether the page should be moved to “Bar” (which would be prefilled) or if the page should be moved to a different title (like “Foobar”). The NABer would be given the entire article contents below so they can make a judgement call as to whether the title is okay.
For empty requests, the NABer can still decide whether they should move the page but will also see the talk page of the article so they can decide which of all the proposed titles would be a good move target. They would be given “Foo” -> ?
and the same interface for moving the page, just they will have to manually enter in a title into an empty field to move the page.
I think this is a good idea, but I’m not sure of the point. I mean, if boosters can already just head to the title category and see all the article content, the title tag, etc., then won’t it also work if they move the page there? It’s a good idea, but I don’t think it would be the very useful as there is already a category for this. However, I’m not a booster, so I’m not sure. Just treat this message like a side-note!
It’s a good idea. It’ll probably be way more easier.
JayneG
6
Thanks for the suggestion @Awesome-Aasim
. I think it’s great to see new ideas coming up from a problem or task you’ve faced on the site, and thinking about how the process could be improved.
Of course even with consensus, we can’t guarantee it will happen right away, but I will definitely keep it and circle back when the opportunity to create a new tool comes up :)
I have to be honest, I really don’t see a need for this. @WikiaWang
basically summed up my thoughts already - we can already do all this without a tool, and it doesn’t take more than just a few clicks to move pages or check Discussion pages. It seems like it would just take up engineer time to build a new tool that only select users can use and that could break with site updates of any sort, and the last I heard was that our engineering team is not that big.
I don’t really see a need for this tool either. I mean - coming from the booster standpoint from way back when this new NAB came through - we used to have the Move tool right in the title in NAB.
Have you tried accessing the Move page via your Admin menu yet? There’s a trigger tool you can use to access this same page, adding it to a Mylinks bar.
I really don’t feel a need for a tool like this, but then that’s how I feel. And besides, part of Moving pages involves updating links to these pages - something you missed when completing all t hose moves this weekend, @Awesome-Aasim
(something the Redirectbot cleaned up for you that you should have done either way).
My thinking aligns with @Galactic-Radiance
and @Byankno1
. Why use valuable engineering time designing a tool that gives no additional functionality and offers only a small time savings? As Alex aptly points out, the tool will likely have to be maintained/updated each time the software changes.
In the software realm I think it best to keep things as simple as possible because levels of complexity cause things to go awry and make the software harder to troubleshoot when it does.
Agreed with all the good people.
I like the idea and it could make things easier, however I don’t think it really needs to be a Community Dashboard tool. Boosters (and I think admins too) are able to simply go to the category. It is also worth noting, it is listed on wikiGnome Tasks
, which are behind-the-scenes tasks, where there usually isn’t much of a queue.
