Last modified: 2013-06-18 16:42:54 UTC
As the number of features grows, the list of logs at [[Special:Log]] has also grown. It currently includes some 18 logs with some omitted (oversight) and others proposed for addition (eg bug 17806). This availability of data is good but has a difficult side; users checking out editing issues now have to check several logs on any given point, to be sure they are seeing "the full story". This comes to a head with deletion where a deletion might be in any of the delete, suppress, oversight, or (proposed) revdel, logs. Or indeed have actually been a page move, perhaps with move log redaction or username suppression. I would like to suggest that the dropdown list of logs be enhanced, to help handle this. Here are 2 ways this might be done in the interface. In the first, the dropdown box is still one long list, but has groups highlighted in the list. In the second, there is a dropdown for log category and then a second box to select the log (or "all") within that category. As an aside, also simplify to "all logs"; if the user can't see a log, then just don't have the log listed or show results from it. --- ENHANCED DROPDOWN BOX - VERSION #1 --- ALL LOGS All local logs All global logs affecting the local project [ie global account, block, and rights logs] ALL BLOCK LOGS Global block log Local block log ALL DELETE LOGS Delete log RevDeleted log Suppression log ALL USER ACCOUNT LOGS User creation log User rename log User rights change logs ...etc --- ENHANCED DROPDOWN BOX - VERSION #2 --- Type of log: Specific log All logs Select from: All logs - All global logs - All local logs Block logs Select from: All block logs - Global block log - Local block log Delete logs Select from: All delete logs - Deletion - RevDeleted - Suppression - Oversight User account logs Select from: All user logs - Creation - Rename - Local rights change - Global rights change ...etc
(In reply to comment #0) > As the number of features grows, the list of logs at [[Special:Log]] has also > grown. It currently includes some 18 logs with some omitted (oversight) and > others proposed for addition (eg bug 17806). This availability of data is > good > but has a difficult side; users checking out editing issues now have to check > several logs on any given point, to be sure they are seeing "the full > story". Both statements of problems look wrong to me: 1) more features don't need more logs, 2) if you want to see "the full story", just select "all logs". > [...] > Here are 2 ways this might be done in the interface. In the first, the > dropdown > box is still one long list, but has groups highlighted in the list. In the > second, there is a dropdown for log category and then a second box to select > the log (or "all") within that category. Both proposed solutions are IMHO bad ideas because they would add clutter, without a clear rationale (see above). > As an aside, also simplify to "all logs"; ? > if the user can't see a log, then > just don't have the log listed or show results from it. This is reasonable: it should be another bug, *if* still a problem. Doesn't seem to be one, because I can't see (for instance) the checkuser log as an option. I'm closing this bug because the problems it intends to address are unclear (or not stated at all) and the solutions proposed are not acceptable. Feel free to reopen if you think this is really needed, but please explain why: also consider to open different requests, for instance: a) the last note above; b) actual bugs like excessive number of logs created that should rather be a single log (log_type) with different actions (log_action), as already done with some logs which were merged; c) logs that should be hidden by default because they make the "all logs" view cluttered, if there's any (there shouldn't); d) a feature request for multiple selection of logs from the dropdown.
