Minor question, OH&S. Do you happen to know the specifics for what fully happens when comments are disabled then re-enabled via admin controls? (I'm looking into the possible options for tackling the load of comments) If not then never mind, I'll try asking on Community Central.
P.S. Do you reckon the episode image template idea from a few weeks back would be feasible or unfeasible?
I've come across conflicting information previously - some say that disabling the comments hides the existing comments and they return once it is switched back on, others say that it wipes them out.
The template idea might not be feasible - what I was wondering was whether it would be possible to rig up a template which produces a link leading to the Special:WhatLinksHere for the page it is on, but set to Files. (e.g. Links for Haimura, Files (long link))
The reason I was thinking about whether this would be possible is because when the systematic sweep for the images is eventually carried out, one of the things that will be added will be a link to the article covering its source. This source link could be used to keep track of images on the wiki from a particular source. Another thing was, if it is possible to make a template that automatically links to the File-specific WhatLinksHere, it could in turn be placed into the infoboxes for stuff like novels or episodes (in a non-obtrusive manner) for quick access.
This isn't something which can be carried out yet, but would it be possible to give the bot an identification sweep task at some point, OH&S?
P.S. I created a new category and tracking template yesterday for a large-scale project. Details here. Also, I've asked about the comment stuff on Community Central and got an answer of what would happen to the existing comments if commenting was disabled temporarily (hopefully it won't be required, but if the worst came to the worst, it won't result in the loss of the existing ones).
P.P.S. Any thoughts on the matter of the private juvenile hall?
Due to the size of certain tasks, I'm trying to make my own bot account, though I'm having some trouble in connecting it to AutoWikiBrowser as suggested by Community Central's Help:Bots. Any advice, OH&S?
Yeah. I have multiple web browsers installed on my PC and I use different ones for different purposes. I use a Firefox-variant browser to log into my main account; while I use regular Firefox to log into my bot account. This saves me the hassle of logging on and off. In fact I have shortcuts to the profile pages for both of my accounts on my desktop. But do what ever works for you.
On my bot account, I import the JS scripts from the Developer Wiki and don't use any extra software. At the time, I couldn't be bothered to learn how to connect it to other software; and mass edit scripts were sufficient for what I was attempting to do.
I see. It probably would be best to take your approach, rather than waste time trying to get the extra software to work.
The large-scale operation I had planned was a series of sweeps to identify which images are lacking information (either description or licensing) without having to go through the whole lot manually, followed by a sweep to add a basic structure and tracking tags to them (ImageReqInfo) - giving us a convenient list via WhatLinksHere.
It all depends on whether you are lucky enough to find a JS script on the Dev Wiki that satisfies your need. If not, then looking into AWB might be the way to go. I'm not sure; I need to read up on what AWB actually does.
If my understanding is correct, you're trying to centralize the work on different projects so that anyone can contribute to them; specifically using the functionality provided by wiki templates?
You know what, that's actually a brilliant idea. It's similar to something like GitHub where everyone can work on the project together instead of doing things separately and there being clear documented changes between edits by different users.
I was thinking that it would be a bit more flexible for joint work than the Open Sandbox idea.
With the top bar, the users working on the joint draft can place the template wherever they like on their sandbox, view its current state on their sandbox, edit it with a click from their sandbox and then jump back once they've finished.
If it is OK OH&S, could you try one of them out at some point and see if there are any areas in which they could be improved? At the moment, there are fifty active ones and ten inactive ones (I got a bit carried away), as well as a template for their overview and development.
I don't know; its basic intended function appears to work fine. I've added myself to Shared Draft 31 as a test.
Certainly there are a lot of templates. I'm wondering which of those could be cleared or consolidated together. At this stage, I'm not too concerned with the number.
It would be good for there to eventually a page dedicated to the list of shared drafts as a directory that can be linked to on the front page slider/intro template.
On another topic entirely, I'm thinking of updating the Franchise Overview template. I'm not quite happy with Dark Matter getting its own space despite there being only one special chapter and announcement for a continuation. I'm thinking of using that space as a general 'Other' section and grouping together Virtual-On and any other special manga that's serializing.
With regards to the Shared Drafts, There is a list of what they are currently being used for on the overview/development template page. Some of them are currently being used for collection purposes (e.g. collecting and confirming all of the R-S/anime design images on the wiki, gathering the different term Nihongo and localizations etc), some for tracking and monitoring (e.g. the current status of the chapter/episode page sections), some for regularly updated tasklists (rather than in repeated posts, e.g. the image tasklist) and a number I'm thinking of using for a brainstorming session (Magic and Academy City being the main two in mind at the moment).
One idea which has just come to mind is rigging some sort of mechanism so that the list updates itself automatically depending on the subject listed on the template itself, though that might require a fair amount of tinkering and is not as urgent as other tasks we have on the go.