Well, part of the thing is, when you propose to take over the new page, most of the time that means you're taking over doing the whole move. People assume it, because honestly that's what happens in most cases. That's likely part of it.
Reality is that, which when you stop believing in it, doesn't go away. -Philip K. DickDiscussions cannot be moved by someone either way—you need a mod for that.
If you need help with wick migration, you go to Special Efforts.
I agree that this is a huge problem, though. Unfortunately, not enough people care to clean up wicks.
There was a suggestion in Tech Wishlist to add a script which automatically changes wicks, but that may cause crash problems.
"If you aren't him, then you apparently got your brain from the same discount retailer, so..." - Fighteer![]()
So when somebody says "I can create the new page and copy content, but don't know how to make redirects and cannot move 3000 wicks by myself." everyone else sees "I will move the whole page and discussion myself, and do all 3000 wicks myself!" ?
How can any one person be expected to clean up 3000 wicks alone? That's just insane. complaint tangent
Cleaning wicks should be a group project, not dumped on the nearest schmuck or the OP. It certainly should not be ignored entirely while the thread is locked, which has happened before. And to be a group project, with group responsibility, it needs a group thread on Special Efforts and/or TRS that's pinned to the top.
A script, aside from the server capacity issue, is not the answer in the case of renames because:
- Sentences may need rewording unless the rename is a snowclone of the old one (not common)
- Some wicks may have to change to some other trope, which needs a human looking at and evaluation them, for reasons:
- The page was redefined or split in TRS, and some wicks no longer apply
- A subtrope or missing supertrope was created and some wicks should now point there instead
- There was misuse in the wicks that needs cleaning
I think that a script could, at least in theory, work for at least some namespace migration. But not with TRS wick cleanup, unfortunately.
edited 17th Mar '12 1:54:08 PM by ArcadesSabboth
Oppression anywhere is a threat to democracy everywhere.I think the main issue with making it automatic is not so much server crashing (while it's been the main argument, it would depend about who runs the script), but that it messes up alphabetization and grammar. In any case, it's not a viable solution*
For reference, the tropes that are affected by this issue are:
- And The Fandom Rejoiced
- Anime Anatomy
- Cute Shotaro Boy
- Getting Crap Past the Radar
- Immortality
- MacGuffin Girl
- The Mario
- I Got Better / He Got Better
- Token Mini-Moe
- Toy Ship
- Xanatos Roulette
Creating such a thread and sandbox would just need someone making the thread in TRS(to use the tag system to link tot he sandbox, to keep the connection to TRS and to discourage people from using Special Efforts as a dumping ground) and someone pinning it, just like Wick Migration
and Sandbox.Wick Namespace Migration.
The fact that the basic concept works for namespacing might imply that it works for general wick cleanup too.
edited 17th Mar '12 1:55:12 PM by SeptimusHeap
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanThis is what the special efforts subforum is for: jobs that are too big for one person to reasonably be expected to do alone. If you spot one in TRS that has a huge number of wicks to clean and move, first check to see that a Special Efforts Thread doesn't already exist for it, and if there' isn't one, make one and say so in a post in the TRS thread.
Special efforts threads seem to work best if someone serves as cheerleader and progress-keeper in one of the first few posts, keeping a tally of which alphabetical sections are done. (Take a look at the locked thread for Understatement to see what I mean. Either a mod can do the tallying or whoever made the post can. But not knowing which sections have been done, and not really seeing any progress leads to stalling and abandonment of the Special Efforts.
I think the problem there is that being a cheerleader is only a little less effort-demanding than doing it all by yourself. And in this particular case - What Do You Mean, It's Not Awesome? - it didn't work at all, despite the attempt. Certainly not as good as Wick namespace migration, which is why I'm suggesting to do it all in a dedicated thread rather than splitting it between various threads, as the current approach seems to entail.
Yeah, one cannot cheerlead a team consisting of nobody. (The only reply to my appeals was somebody telling me to do it all myself.) I tried cheerleading the disambiguation wick cleanup for World Of Darkness, too. On Special Efforts. That project fizzled out, also.
edited 17th Mar '12 2:40:10 PM by ArcadesSabboth
Oppression anywhere is a threat to democracy everywhere.Yeah, I see this diagnosis:
- Running cleanup in TRS doesn't work:
- That sort of job is very different from what people in TRS usually do.
- You really can't do it in most cases without first Archive Binge the TRS thread.
- People willing to do that work are drained away by Special Efforts, also thanks to the problems mentioned above
- Forum-haters don't do it at all.
- Such TRS threads are often prematurely closed
- Running it in Special Efforts works better, but:
- You need someone willing to babysit the effort
- Forum-haters don't do it at all
- It takes a good forum-wiki communication, which excludes people without much forum connections
- It splits willing people between various Special Efforts threads.
Putting all the things in a sandbox has the advantage that it doesn't need forum access or Archive Binge-ing, and it's centralized. Sure, you need to work out which description of the goal to use (if it's cleanup), but you could use a thread to work it out.
edited 17th Mar '12 2:40:16 PM by SeptimusHeap
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanWhat would help is not a script per se, but partial automation. For example, it would help if from the Wick List I could open a small edit box that edits not the entire page text, but only the paragraph containing that particular wick (and the previous/next paragraphs). This makes it much easier to find things and quickly fix them.
Ctrl+F (or whatever the Mac equivalent is if you use a Mac) and search for the Wiki Word. It should take you right to it.
Edit: Completely and totally ninja'd.
edited 20th Mar '12 11:57:00 AM by Nocturna
@The last few posts:
Automating the stuff done manually via ctrl-F has limitations. Using "StuffToTrope" is the easiest way to do a wick, it's not the only way. There's also {{Stuff To Trope}} and {{Stuff|totrope}} or {{Stuff To|trope}}, not to mention the variations for works that are spread across multiple namespaces or when StuffToTrope is a redirect on Main/ pointing to several different works that happen to have or be commonly known by the same title.
edited 21st Mar '12 5:24:00 AM by Nohbody
All your safe space are belong to TrumpI never feel like searching the name takes up to much time, normally this is done pretty fast.
To prevent
this problem search for only one specific word of the trope name e.g. when renaming Gonna Fly Now Montage I only searched vor Montage. By doing this you will find the name no matter how it was linked. (Of course this only works if the trope name has at least one really specific word)
Most time is spend on rewriting examples or alphabetizing. And this can not be done automatically.
^ That's what I meant, even if I didn't mention the "replace" part of "find and replace" because I'm a forgetful idiot.

It's becoming clear that there's a huge backlog of ignored wicks to clean up from TRS threads. I've seen at least two pages whose TRS threads were locked before anybody bothered to fix their wicks, creating quite awkward situations.
What Do You Mean, It's Not Awesome? has been in limbo in the middle of a rename for a few weeks since I offered to create the new pages, but nobody has stepped up to move discussion, create redirects, help move wicks, etc. so now we have duplicates of that page and its subpages, just sitting there being stupid.
This kind of work keeps bogging down TRS threads. Once the decisions are made, nobody wants to do any work, so it falls to whoever opened the thread (whether or not they have time) or is ignored. If it's too much for any single person to do, it just isn't done at all. Stale threads sit around, ignored, taking up space, and genuine problems don't get fixed.
Proposed Solution:
This was originally Septimus Heap's idea I think. Give TRS a Wick Migration thread similar to the Namespace Migration thread. When wicks are the only things left to do on a TRS thread, the project can move to that wick thread with a link to the TRS thread that had the details. Then the original TRS thread can be closed. Pin the wick thread somewhere so it doesn't fall to the bottom page.
Maybe that's not the ideal solution, but something must be done.
Oppression anywhere is a threat to democracy everywhere.