This is an archive of past discussions about User:Evad37. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Hey Evad, would you have any interest in adopting User:Kephir/gadgets/rater, a tool used to quickly "rate" and organize WikiProject banners? It's an immensely helpful tool (even though I think we'd all be better off if all WikiProject rating was shipped off to Wikidata...) and still widely used despite being abandoned (note the number of unanswered talk page questions). Imagine you're plenty busy maintaining the other now-vital gadgets that you do, but if you see an opportunity to patch up a script in need of some love, the result would be put to good use. czar02:33, 8 September 2017 (UTC)
I've had a look at this, and if I were to take it on, I'd like to do it without have to store separate data for the banners. Which might make it more complicated, but also more robust and easier to maintain. There's also some discussions at Template talk:WPBannerMeta on modernising the whole banner system, which could have an impact on this and other assessment-related scripts. - Evad37[talk]01:17, 10 September 2017 (UTC)
Sounds good. I thought it might be better to make a few jury rigged fixes to keep it afloat than to rewrite it, but I'd definitely hold off on the complete rewrite if the parameter access will potentially change in the template's conversion to Lua. (That said, if it's only changing the internal structure and the user-facing banners will remain the same, then we'll likely still use the existing tool.) czar05:50, 10 September 2017 (UTC)
The main thing that I would suggest is that when you choose 'Biography' it should try to autofill the 'list as' parameter: i.e. strip off anything in parentheses, then autofill as last, first middle+ (with a warning indicating for the user to check it, because this doesn't work with all names, particularly Asian ones). I made this as a suggestion over at script requests, as well as over at the gadget's talk page. Is this possible to implement easily in a script fork? — InsertCleverPhraseHere(or here)01:48, 19 September 2017 (UTC)
@Everyone, can we put each bug report and feature request into an individual ==level 2== section (like we do on WT:XFDC)? It's a bit overwhelming having everything in one unorganised section. Plus that way, once issues are resolved the section can be marked as such and then archived. (I've pulled out what I can see that's not resolved; if I missed anything just add it in a new section below) - Evad37[talk]05:41, 9 November 2017 (UTC)
}}
@Czar and Insertcleverphrasehere: I've got an alpha version of my replacement script working, if you want to try it out. There are likely to be bugs, but it would help to have some feedback on what they are – and also what other features it should have. - Evad37[talk]03:42, 7 November 2017 (UTC)
Works nicely so far and is already an improvement over the old rater ("apply to all" is a godsend). Re: the edit summaries, if all banners are set to start/low (for example), the summary can just be "Assessed at start/low" or "Assessment: start/low" rather than listing the individual changes [1]. My first major ask: a "guess" feature would be amazing. 99% of my clicks in the old rater were for common sense extrapolation. For example, an article has three banners but only one is filled (say C-class/low)—even if I'm going to edit some other part of the template, I might as well set the other two projects to C-class/low too. Another example: let's say zero of three banners are tagged and I go to edit—such articles are almost definitely not above start class (and even if it were, an editor would have to note it manually). It's likely either start/low or stub/low for the three banners. The difference between stub and start is mainly whether the prose exceeds 1500 characters (I calculate through User:Shubinator/DYKcheck.js). And while such an educated "guess" at the click of a button would be helpful, it'd be even better with the option of setting it as default, so that the script automatically suggests entries for the empty fields when applicable and highlights those fields as auto-suggestions that will be saved with the edit. Separately, when going to add a parameter, I get "TemplateData not found. Check the template's documentation." on all banners. Is there a sample WikiProject whose TemplateData I should use as a model? Nice work and thanks again czar05:58, 7 November 2017 (UTC)
I guess what you say about the edit summaries that makes sense, but listing changes individually is a lot easier than having to compare all changes against each other, and potentially against banners which haven't changed.
With regards to guessing the quality, I think using ORES would probably be best way to do it (just because one banner has a class set doesn't mean the article is still at that class). Guessing importance is trickier, since its relative to project scope, but maybe the following could work: If the existing assessment is "top" or "high", guess "mid"; otherwise guess "low".
I added TemplateData to {{WikiProject Australia}} (diff). If you go into edit mode on the doc page, there's a button near the top of the page to create/manage TemplateData through an interface (which is a lot easier than trying to do it manually, since it has to have valid JSON syntax). My script only looks at the parameters, but the rest can be filled in if you want. See Wikipedia:TemplateData/Tutorial for more info. - Evad37[talk]09:03, 7 November 2017 (UTC)
I was thinking that the "guess" could be much more rudimentary. The AI sounds like a lot of work, and possibly overkill. If the article is B- or C-class, the editor's discretion to change the default should be sufficient. The idea is to use the existing rating when one exists (which is still subject to the editor's discretion on whether that rating was correct) and otherwise to assume stub/start (use a character-counter to tell the difference) and low-importance (even if high importance for one project, I'd assume "low" for the others unless the editor has reason to manually raise it). Also the chances of top/high articles getting new banners are tiny. I'm thinking more of saving the same few clicks each time the window opens—it would be more an option to assist the editor than actually predictive of whether the article deserves that specific rating. I updated a TemplateData but the script appears to be using the previous cache—know how to refresh it? Thanks! czar16:19, 7 November 2017 (UTC)
Very nice work. Absolutely love the name autofill for bios! Only scratched the surface, but right off the bat a couple things that would speed things up a wee bit: make the button for 'add project' a bit bigger. After clicking on 'add project' I have to manually click on the field before I can start typing, it would be better to automatically have the field active so that I can start typing the wikiproject immediately. Related to this, you also have to click 'add' manually, it would be nice to be able to just slap enter. If both these things were implemented then I could leave my cursor on the 'add project' button and then rapidly add wikiprojects with just the keyboard and just click once for each project. If that makes sense.
Bug: fails when mainspace page doesn't exist (quality prediction/build interface fails), but works even when draftspace page doesn't exist
Doesn't work with userspace drafts
Doesn't use TemplateData "autovalue". Perhaps I'm reading this backwards, but I understood this TD param to be the one for autofilling the value of the param. For example, for |TaskforceName=yes, the TD should have "yes" set as the value for the taskforce param, and that "yes" should import into the appropriate rater box as well. Another option: The old rater.js used checkboxes, which the new one can use too when the param data type is set to "boolean". The only issue might be that most banner documentation recommend using "yes" instead of "1" as the value.
In all versions - when I am adding project in the drop down (Or whatever) screen - have the template in - I need to press add twice for the process to continueam I doing something wrong? - (unresolved?)
for what ever reason - when I complete an addition - and the small line says done! the close button does not respond Fixed
Wow, you work quick. The keyboard usage is great, definitely speeds things up a lot. I've noticed that the 'close' button (after clicking 'save') does not seem to function (requires page refresh).
The predicted class seems accurate from what I have seen so far, though it does not autofill this when adding wikiprojects (i'm not sure if this is intentional or not, but I think it is at least safe to autofill this bit as 'stub' or 'start' based on length, though I usually just leave it blank for someone from the wikiproject to come by and fill in).
Still getting "TemplateData not found. Check the template's documentation." when clicking 'add parameter' for a wikiproject (biography in this case).
There should be a handy list of suggestions for task forces for the most common wikiprojects, like Kephir's rater lets you select 'sports', 'polititian', etc.
Also the box for the 'living' parameter should always be an active parameter for wikiproject biography as it is essentially required.
I'm encountering a bug where after adding a parameter that I decided to remove, after removing it in the rater and clicking save it does not remove the extra parameters that I had clicked the x on (they are still there when re-loaded).
Per the last error, it would be nice to have a 'code view' section like Kephir's rater, though not essential. For that matter, a 'Preview' button next to the save button (which just opens the save as a preview) would be pretty great.
@Insertcleverphrasehere, most of the banners need TemplateData added manually (see previous section). I imagine they weren't prioritized since TemplateData is primarily used to make mainspace templates accessible in VisualEditor. czar15:21, 8 November 2017 (UTC)
WP Bio has TD now, though the details can still be tweaked, and eventually the TD human-friendly labels might be adopted (e.g., living vs. Living?). Autofill isn't working for me either but ORES is sweet czar16:04, 8 November 2017 (UTC)
Ok I found the bug with autofill. It will work, but only if you save the wikiprojects you have added then reopen the rater. When re-opened, the class and importance fields will be autofilled. Hopefully this should help with tracking down how to fix the bug. — Insertcleverphrasehere(or here)00:39, 9 November 2017 (UTC)
Remove banner bug
Latest comment: 6 years ago2 comments1 person in discussion
My understanding is that they're treated the same as draftspace drafts. Tagging with the banner lets the project keep tabs on its existence. Also some articles are userfied with WP banners intact, so the tool should be usable on such pages czar06:27, 9 November 2017 (UTC)
In all versions - when I am adding project in the drop down (Or whatever) screen - have the template in - I need to press add twice for the process to continue am I doing something wrong? — User:JarrahTree
When viewing a page's history, the Rater tab should still be accessible (it was yesterday if I recall correctly, but perhaps I'm thinking of the old rater.js) czar00:09, 10 November 2017 (UTC)
""TemplateData not found. Check the template's documentation." => "This WikiProject has not been configured for use with this tool. Follow this tutorial [link] or ask for help here [link to this talk page]." We minions can supplement for that low level of support. Yet it would be nice if users could add the basic class/importance even for unrecognized projects and get the error only for adding additional params. czar06:13, 9 November 2017 (UTC)
Done as: "Parameter suggestions not available. This WikiProject banner has not been configured for use with this tool. See the TemplateData quick tutorial or ask for help on the script's talk page."
ORES with a grain of salt
Latest comment: 6 years ago3 comments2 people in discussion
ORES predicts the Alodia (currently rated B-class) as "FA". Does the ORES auto-fill know to max out at B-class? I would personally recommend the autofill just enter "start"-class for anything ORES rates above Stub-class, just because C- and B-class do involve editor discretion that many editors may not be prepared to judge. (Only exception would be when the article has already been rated, e.g., if the other banners read B-class for Alodia, additional banners should autofill to B-class.) Perhaps the ORES text should link to a page that describes how ORES works? Who knows, if ORES ends up relatively inaccurate, might be better to scrap it altogether—wouldn't want editors to feel prompted by ORES to label articles as FA-class out of the blue czar06:41, 9 November 2017 (UTC)
ORES might occasionally make wild predictions, but the autofill logic I've got does already map all non-Stub values to Start. And if other banners have a rating set, it will autofill from that rating rather than ORES. I'll add a link to mw:ORES. - Evad37[talk]08:19, 9 November 2017 (UTC)
I'm encountering a bug where after adding a parameter that I decided to remove, after removing it in the rater and clicking save it does not remove the extra parameters that I had clicked the x on (they are still there when re-loaded). — User:Insertcleverphrasehere
Latest comment: 6 years ago6 comments2 people in discussion
Currently, the script only uses the TemplateData to find what the avilable parameters are, but it is possible to do more: - Evad37[talk]05:41, 9 November 2017 (UTC)
Handle TD's aliases too (if not done already). It should recognize aliases but save to the default format (e.g., |blp= to |living= in {{WP Bio}}).
And just to have it in one place, when TD 'autovalue' is set, show autovalue when the param is manually added but not with suggested params.
I'm not sure the required/suggested need to be highlighted, only shown—they don't need special attention because they're already shown by default. The script should save even when the editor doesn't set the "required" params.
Is there a difference between empty string and removed param? If the string is empty, the param (unless required) should be removed from wikitext, no? I think that's how old rater.js did it. The only tricky part is that suggested params should display in the script (without autovalues) even when their values are empty, but otherwise they should not show in the wikicode
There should be a handy list of suggestions for task forces for the most common wikiprojects, like Kephir's rater lets you select 'sports', 'polititian', etc. — User:Insertcleverphrasehere
This could be handled by the "Suggested" checkbox in TemplateData. We can use "Required" for class/importance and "Suggested" for items we'd like displayed by default. Caveat: Those items displayed by default should ignore the autovalue. The autovalue is useful when I manually add TaskForceX and the checkbox is automatically set to yes, but when TaskForceX shows as a potential option upon adding the banner, setting its checkbox to yes defeats the purpose of suggesting params. czar06:24, 9 November 2017 (UTC)
Follow-up question: How should we enter a set of potential values into TemplateData? For example, TaskForceX-priority can be low, medium, high, etc. Is there a TemplateData field for the param's valid values? czar06:24, 9 November 2017 (UTC)
The <living> (yes/no) parameter is pretty much mandatory when adding WikiProject Biography. Could this parameter be auto included in the list, and possibly changed to read <living?>. I am pretty sure that anything put into this box except 'no' applies the BLP box on the talk page, so no need to include instructions.— Preceding unsigned comment added by Insertcleverphrasehere (talk • contribs)
After adding a wikiproject (by clicking on "Add WikiProject" and adding one), the "Add WikiProject" button is selected, but 'enter' will not click the button. I can even tab through the buttons, selecting each one in turn, but 'enter' doesn't press them. Also, when the rater pops up can you make it so that the "Add WikiProject" button is automatically selected?— Preceding unsigned comment added by Insertcleverphrasehere (talk • contribs)
Interesting bug going on over here that you might want to have a look at. At Rick Brant (Athletics), I can't initialize the rater tool as it gives the following error message:
ORES recommends "stub" on Redirect pages. The script can either autofill "Redirect" or, preferably I think, autofill nothing, as many banners either handle redirects automatically (template does the detection) or not at all. If you choose "autofill nothing", it would be nice to acknowledge that the script detected a redirect and that redirects are often automatically categorized without params (is there a better way to communicate this?), perhaps in the space where the ORES evaluation previously went. czar18:24, 9 November 2017 (UTC)
Done, mostly, now shows redirect target when the page is a redirect, and will not autofill values. Further explanation could still be added if needed. - Evad37[talk]22:25, 13 November 2017 (UTC)
Bug with "Listas" autofill feature
Latest comment: 6 years ago6 comments2 people in discussion
The "listas" autofill part of WikiProject Biography is awesome, but it has a really bad bug. It doesn't save the "listas" parameter unless you click on the autofilled name when in the rater. I need to go back and fix all of the biographies I have been rating, because most of them were autofilled correctly (because your autofill is AWESOME) and I didn't need to modify them. But because I didn't click on them or modify them, the parameter was not saved. — Insertcleverphrasehere(or here)00:58, 11 November 2017 (UTC)
Another minor bug with autofill that I noticed: names that have 'Jr.' after them are autofilled with the 'Jr.' as the last name. This should be stripped off along with parentheses (along with Sr., though it is much more rare). This is not essential, but just noting that it exists if it is an easy fix. — Insertcleverphrasehere(or here)03:02, 11 November 2017 (UTC)
Nice.... You are a machine mate. The autofill works in the vast majority of cases and saves so much time when rating loads of biographies in a row (they are one of the most common types of new articles as well). — Insertcleverphrasehere(or here)05:39, 16 November 2017 (UTC)
WikiProject search function suggestion
Latest comment: 6 years ago5 comments2 people in discussion
I've noticed that the search function only searches by the first letters of the WikiProject, this works pretty well, but can sometimes make finding certain WikiProjects difficult when you don't know what you are looking for. Can I suggest a modification to the search function that prioritises the first letters (as now), but also includes results where the letters typed are, for example, the second word in the wikiproject title (i.e. start typing "martial arts" and "mixed martial arts" will also come up in the search results? — Insertcleverphrasehere(or here)04:39, 12 November 2017 (UTC)
A better example is the one I just tried and failed to find using the search with the rater: "Sports Car Racing". I tried "Racing", "Car", "Auto", etc, but unless I know specifically that it starts with "sports" I am not going to find it (and I even knew that the wikiproject existed, just not what it was specifically called). Eventually gave up and googled "wikiproject car racing" and found it. — Insertcleverphrasehere(or here)03:25, 14 November 2017 (UTC)
Should be possible. It's complicated because I have to override the in-built filtering, but I've successfully done something similar for XFDcloser's Rcat selector. - Evad37[talk]06:37, 14 November 2017 (UTC)
Bug: If you click on either preview/changes, and then click on the other button (changes/preview), the latter won't show and the former preview or diff box becomes unable to be closed. (Ideally we could switch between the two views without clicking "close" on either.) czar08:03, 11 November 2017 (UTC)
WikiProject Disambiguation still doesn't come up as an option when adding wikiprojects. For that matter, if the tool could check for the {{Disambiguation}} template on the article page (or any of its variants i.e. {{disam}}), and automatically add the WikiProject Disambiguation template, that would be awesome (but not if it slows down initialisation of the tool).
Specific for this template, the project says not to create a talk page with this template if no discussion exists. To the larger point, WikiProject recommendation based on categories or article content could be interesting, but I doubt it's worth the work. Both the project banners and the WikiProject system itself are both due for an overhaul (or at least a pointed op-ed in the Signpost...) czar08:11, 11 November 2017 (UTC)
The {{WikiProject New Mexico}} template is a sub-template of wikiproject United States, so these should really be available from search. It seems some states are available and others are not-I also noted that some of the sub-templates of wikiproject Africa are also not available (small african nations mostly). I imagine that the Category:WikiProject banners without quality assessment might also contain inactive wikiprojects? Still, adding inactive wikiprojects is not the end of the world, at least if someone decides to reactivate a wikiproject there will already be a bunch of articles tagged for them. — Insertcleverphrasehere(or here)05:46, 16 November 2017 (UTC)
I really don't know what's happening there – if it happens again (or is still happening), can you look for in the browser console (see here [4] for how to open it) and copy any errors or warnings that are there? - Evad37[talk]02:28, 11 November 2017 (UTC)
Experiencing an error at Talk:Golden Cock and Hen, where I accidentally added wikiproject china, then corrected it by adding wikiproject Korea, and pressing the X on wikiproject China. I went to check and China had not been removed. No matter how many times I restarted the rater, I could not use it to remove wikiprojects. Massive bug, please fix. — Insertcleverphrasehere(or here)10:36, 26 November 2017 (UTC)
Can you set up a togglable (default off) ability to have the rater check to see if the talk page has zero wikiprojects and automatically pop itself up if there are none found? This would be an awesome feature. I personally would just leave it on all the time, then whenever I stumble across a page that doesn't have any WikiProjects I would then be prompted to rate it, and it would also cut out the step of initializing the rater manually when I am patrolling new pages.— Preceding unsigned comment added by Insertcleverphrasehere (talk • contribs)
Sounds like a good idea. It should also be possible to set which namespaces you want the auto-mode to operate in. - Evad37[talk]07:02, 11 November 2017 (UTC)
That's a good point, I wouldn't want the auto mode to pop up in non-main spaces personally, but it would be good to be able to toggle for different namespaces temporarily for certain tasks (for people who like to scroll through drafts for example, or add wikiprojects to AfC submissions before submitting them). — Insertcleverphrasehere(or here)10:27, 11 November 2017 (UTC)
Well, the whole script loads regardless in any page view/mode, and the autostart part set the main part of the script running if no projects are found on the talk. Whether it is a bug or feature depends on your point of view, I guess – after all, it is still an article (or page) without any project banners. - Evad37[talk]02:15, 28 November 2017 (UTC)
Highlight close button and auto close in 5 secs
Latest comment: 6 years ago3 comments2 people in discussion
After clicking save, users must manually click the 'close' button. It would be good to have this auto highlighted so that I can just click enter, and it would also be good to just have the thing automattically close on 5 seconds (assuming that nothing went wrong with the save). Cheers. — Insertcleverphrasehere(or here)23:59, 20 November 2017 (UTC)
Some projects, such as WikiProject Visual arts do not support the importance parameter, but rater tries to add one anyway. Kephir's rater didn't do that. Mduvekot (talk) 03:35, 11 December 2017 (UTC)
Hallo, just tried your script today, and it has some nice features. I have been using User:Kephir/gadgets/rater.js for a long time - but decided to change to your script. rater.js has a hotkey '5' which was really nice. Is it possible you could implement the same feature for this script? Christian75 (talk) 09:06, 18 January 2018 (UTC)
I see what happened. If I type "India" into the box it places {{WikiProject India}}. If I type "India " (with a space) it places {{India}}. See this edit. Thanks for looking into it. I find the script very useful. Thank you very much for writing and maintaining it. Jbh Talk12:57, 11 April 2018 (UTC)
Nice work on the script, although it seems a bit slower than Kephir's version. Could you add the option to group banners in {{WPBannerShell}} if there is more than one? Some pages fall into the area of multiple WPs and full size banners for each often takes a lot of space. Regards SoWhy08:31, 20 March 2018 (UTC)
@SoWhy: The banner shell is already automatically added, but is set for when there are 3+ projects per a previous discussion - Evad37[talk]01:45, 13 April 2018 (UTC)
|living= should be evaluated in every instance of {{WikiProject Biography}}. The param will show by default in Rater.js with an empty checkbox, but when left unchecked, that checkbox should evaluate as |living=no rather than the absence of input. (This is different from other checkbox params, which can freely ignore that whole param if left unchecked.) Any tips on how to set this properly in its TemplateData? czar12:14, 13 May 2018 (UTC)
That's a bug, since it should be already be working that way with how the TemplateData is currently set up. - Evad37[talk]16:07, 13 May 2018 (UTC)
Fixed. It was actually two things: (1) the TemplateData needs to specify the autovalue for Rater to fill in, like this. (2) I needed to adjust the script to actually use such autovalues when it comes across required parameters. - Evad37[talk]17:26, 13 May 2018 (UTC)
Exclude WP Disambigation?
Latest comment: 6 years ago4 comments2 people in discussion
Is there any way to exclude disambiguation pages, or at least to warn editors that new talk pages shouldn't be created if they will only contain the {{WikiProject Disambiguation}} banner? The reason for that is explained in the template's documentation, but it amounts to: 1) the banner serves on purpose (tracking is done via the article category), and 2) some editors find it to be a minor nuisance. – Uanfala (talk)20:04, 10 March 2018 (UTC)
@Uanfala: The script will now give a warning (and ask for confirmation) if a user tries to add the {{WikiProject Disambiguation}} banner when the talk page doesn't exist (and no other banners have been selected). - Evad37[talk]17:19, 31 August 2018 (UTC)
Hi everyone watching this page. The latest version of the script should have improved load times on average. I've implemented some caching so that it doesn't need to request fresh data from the API every time it loads. The improvement on pages which have {{MILHIST}} banners should be quite dramatic, as that one always seems to take a very long time to process (and is probably the main cause behind the slowness reported in § Load time and blp parameter in banner shell above). The more you use the script, and the more banners you encounter, the faster the script should be, generally. (pinging @Sam Sailor and LittlePuppers) - Evad37[talk]03:32, 1 August 2018 (UTC)
Mine is pretty fast already, but good to hear that it will be even faster. Every once in a while I click enter (activating the 'add wikiproject' function) too quickly. This can sometimes result in the 'add template' popup not giving any suggestions (I assume it is because I have pressed enter before the rater was completely finished loading). It was an easy bug to fix(exit and re enter the 'add template' popup), but right now I can't reproduce this bug, so it might have been fixed in this recent update. If so, great! — Insertcleverphrasehere(or here)04:20, 1 August 2018 (UTC)
Can I please request that with rater_autostartNamespaces = 0; that it not automatically pop up on history pages? It gets rather annoying when it blocks your view when quickly checking the history page and I rarely find the need to add wikiprojects from the history page. The History pages are not exactly in 'namespace 0' (or any other namespace) so I don't really know why they should come up with this setting. — Insertcleverphrasehere(or here)23:19, 19 August 2018 (UTC)
I've added some TemplateData to the project banner, with the b-class criteria as suggested parameters; in about a day or so when your local cache expires those parameters will be there by defualt, with checkboxes to easily set them to "yes". - Evad37[talk]10:07, 27 August 2018 (UTC)
However, there is also an explicit no setting in the criteria. Perhaps if the box is not checked 'yes' then it adds 'no'. Kges1901 (talk) 10:52, 27 August 2018 (UTC)
Yeah, a checked box means "yes" and an unchecked box means "no" (or those parameters can be removed) - Evad37[talk]12:08, 27 August 2018 (UTC)
Done, will now offer AL, BL, and CL as possible classes for Military history. As before, it may take about a day or so before your local cache expires and you see the change. - Evad37[talk]08:17, 30 August 2018 (UTC)
Not placing the autofilled text in listas parameter in the dialog
Latest comment: 6 years ago2 comments2 people in discussion
When the listas parameter value is generated automatically, could it be shown in the textbox in the dialog box? It would allow me to see what the auto value was before saving (so that I can make changes if needed).
Any way to have pages marked with this tool not show up on my watchlist without having to visit the talk page afterwards and click the symbol? SEMMENDINGER (talk) 02:32, 21 June 2018 (UTC)
Pretty sure this is a different setting, probably in your preferences about automatically watching any page you create (e.g., any new talk page you create) czar13:26, 21 June 2018 (UTC)
I've been using the original rater script for a little while now, and I just found this script today. I'd like to thank you for updating it. A few initial observations:
It's a bit slower than the original - I find that the original is a bit more snappy than this.
Being able to rate all the wikiprojects at once is nice - although it's much less often useful for importance, as that varies much more between wikiprojects.
There are a lot less random errors than the original.
ORES predictions are nice.
There's no X in the top right, but that's something I'll get used to.
What does autofilled mean?
The preview is nice.
The background doesn't continue if you scroll to the right.
Autofilled means that the value there has been filled in by the script, rather than either being read from the current version of the talk, or being filled in manually by the user. - Evad37[talk]03:53, 1 August 2018 (UTC)
Is there any reason it won't autofill above a start class (i.e. even if ORES predicts B and another project's rating is C, it still autofills as Start)? LittlePuppers (talk) 04:06, 3 August 2018 (UTC)
Is there any reason it won't autofill above a start class – ORES sometimes makes pretty wild predictions, see User_talk:Evad37/rater.js/Archive_1#ORES_with_a_grain_of_salt. Some human discretion should be required for ratings above Start. even if ORES predicts B and another project's rating is C, it still autofills as Start – That's a bug, if there's a rating from another project banner the script is supposed to use that instead of ORES. - Evad37[talk]05:26, 3 August 2018 (UTC)
Okay, thanks (although generally I've found ORES to be pretty good). I just tested it and it does use other projects' classes correctly, so that was just my imagination. LittlePuppers (talk) 05:31, 3 August 2018 (UTC)
Option to require parameters
Latest comment: 6 years ago2 comments2 people in discussion
So I rate a lot of new articles for WP:USRD. The banner should almost always include |state=|needs-map= and |needs-jctint=. Is there a way to configure things so that if I pull up USRD's banner that the script will automatically add these three parameters? Imzadi 1979→23:23, 27 October 2018 (UTC)
So I attempted to tag Vista Equity Partners, but the script is apparently getting caught up on the #ifeq tags on the talk page, which are due to a very odd implementation of {{Old prod full}}. I've left it as-is so you can test it. The full message is below.
Rater [v.0.8.7-beta]
Initialising:
Loading talkpage wikitext... Done!
Parsing talkpage templates...
Checking if page redirects... Done!
Retrieving quality prediction... Done!
Building interface... Failed. API error: Error: Unable to parse template title "Template:#ifeq: 11 September 2013"
Hello Evad37, just wanted to let you know this script doesn't delete stored data causing it to pile up. This can be seen in the developer options of your web browser. I recommend at some point near the end or at the start (to delete the last time's data) you delete the data from the web storage. Thanks, – BrandonXLF(t@lk)00:16, 7 October 2018 (UTC)
Hi BrandonXLF. Stored data persisting is kind of the whole point though. Storing the data locally in localStorage means that the data doesn't have to fetched through the api each time, which is a significant time saving compared to fetching almost 1600 banner template names through about five API requests before the script can show the main dialog. - Evad37[talk]01:03, 8 October 2018 (UTC)
Hello Evad37, That's true, but there's a lot of banner I'm only going to ever use one or twice. Maybe allow for a list of banner to not delete and remove the rest? There's only a few dozen so far, but it could add up. – BrandonXLF(t@lk)02:18, 8 October 2018 (UTC)
Compliments to the creator and watchers - this is now very quick to use and excellent in maintenance mechanical stuff that is so efficient i hav put off starting using a version of awb, due to the efficacy of being able to check edits and all - well done and happy christmas !! JarrahTree10:18, 23 December 2018 (UTC)
India parameters
Latest comment: 5 years ago3 comments2 people in discussion
It seems that there's an error retrieving the template parameter data (phab:T214254). For some reason that error is causing this script to misbehave, rather than fall back to default ("guessed") parameter information. - Evad37[talk]03:01, 20 January 2019 (UTC)
@Titodutta: Fixed. The script will now behave correctly if there's an error retrieving TemplateData, plus the devs have fixed the underlying issue which was causing that error. - Evad37[talk]04:33, 22 January 2019 (UTC)
Script down?
Latest comment: 5 years ago6 comments3 people in discussion
I love your script, to the extent I think I just jinxed it by starting to write a note to someone about how great it is. Now (tragically!) the option isn't showing up among the "More" options on, e.g. Hillel Frisch or Jonathan Rosen, although I do see it here on the talk page for the script. This entirely could be user error on my part, apologies in advance if that's so! Feel free to skim the edit summaries on my last two or three hundred edits in case that might give you any clues--it was working like gangbusters for me the last couple days (as ever! Thank you!) Innisfree987 (talk) 06:40, 6 March 2019 (UTC)
Ah: solved. Thank you DannyS712, bypassing the cache solved it. (Perhaps still odd that it came up at once on perhaps 10 tabs I had open but, anyway, done for now! I'll note details if it happens again.) Thanks again. Innisfree987 (talk) 07:17, 6 March 2019 (UTC)
@Innisfree987: and @DannyS712: - FYI, I recently found out & thought to share. The accesskey is "5". You should be able to use Alt+5 to open Rater (on Windows, or a similar combination for other OSs). So now I don't bother with finding Rater on the menu as the keyboard is so much faster. Also after hitting Close button, I do Ctl+W to close that browser tab. Cheers! JoeHebda (talk) 12:14, 6 March 2019 (UTC)
Greetings, Just now at Talk:Charles I of Austria the following error.
Initialising:
Loading talkpage wikitext... Done!
Parsing talkpage templates...
Checking if page redirects... Done!
Retrieving quality prediction... Done!
Building interface... Failed. API error: Error: Unable to parse template title "Template:{type"
@JoeHebda: Fixed (the wikitext {{{type|proposal}}} had been causing the script to try to use a template with the invalid name "{type") - Evad37[talk]14:12, 13 March 2019 (UTC)
Greetings Evad37 - First of all, I want to let you know how GREAT "Rater" is for doing many article assessments! A tremendous time-saver!
Questions - on Vector skin, Rater appears at bottom of "More" item. Is there a Shortcut key to bypass the menus (best option)? Or to position Rater at top of "More"? Just curious, as this may help speedup even more.
As far as I know, there is no reason to add wikiprojects to redirects. Is there an easy way to suppress the 'autostart' feature for redirects? It would also be nice if it wouldn't pop up when looking at the history of an article, but I can live with that if it is not an easy thing to do. — Insertcleverphrasehere(or here)14:11, 7 January 2018 (UTC)
Many WikiProject banners templates track redirects and auto-rate as redirect when the parameters are absent. Last I checked, though, the rater.js defaults to blank parameters instead of start+low parameters, if that's what you mean. czar23:24, 7 January 2018 (UTC)
Czar Are you saying that we should be adding wikiproject templates to redirects? I've never done this and I've seen the removed from articles that had been converted to redirect. I was referring to the autostart feature, which is disabled by default, but which automatically triggers and pops the rater up when no wikiprojects are listed on the article's talk page. IMO the autostart feature is amazing as is, but should be disabled on redirects, because nearly all redirects lack wikiprojects and there is little reason to add wikiprojects to redirects, though perhaps if some people like to tag wikiprojects onto redirects (not sure if this is a thing or not) it would be better to create a toggle for this? — Insertcleverphrasehere(or here)23:44, 7 January 2018 (UTC)
Yes, many but not all WikiProjects classify redirects (Category:Redirect-Class articles). The ones that don't might remove the banner rather than letting the template sit as "unknown-class". Ah, I misunderstood "autostart" and don't have that activated myself so don't mind me czar00:48, 8 January 2018 (UTC)
Load time and blp parameter in banner shell
Latest comment: 4 years ago4 comments2 people in discussion
On an article like Jalaluddin Haqqani, I initially thought that Rater for some reason would not load. It turned out that I was wrong, it just takes (for me at least) some 8–10 seconds before it loads. Stick in a Hang on! Loading! message?
In cases like this, the banner goes below the comment. Setting it to go on top of everything else is likely correct in most cases? Thanks, SamSailor21:56, 16 July 2018 (UTC)
Having the dashed purple line that surrounds the box for auto-fill disappear when something is copied in
Latest comment: 4 years ago2 comments2 people in discussion
At the moment the textbox for listas will show as auto-filled on the dialog box, even when a new value has been copied and pasted in. It should probably not show auto-filled when a value is copied and pasted in. Thanks, Dreamy Jazz 🎷 talk to me | my contributions09:40, 6 September 2018 (UTC)
Detect the use of 'n' and 'y' when used in a parameter that takes 'no' or 'yes' (such as {{WP Bio}}s living)
Latest comment: 4 years ago2 comments2 people in discussion
Is there a way to set it so that it doesn't automatically fill in importance? I wanted to go through all of the articles that have a quality rating from one wikiproject, but are missing it from another, and just use the same rating, without needing to remove the automatically-assessed importance each time.
@Gryllida, yes, press "enter" when it loads to automatically open the "add wikiproject" prompt. You can then use autocomplete and "enter" to add the wikiproject. The button to add another WikiProject will automatically be selected, if you want to add another. To save changes, press tab seven times (to select the button) and "enter" once more. czar19:38, 24 November 2018 (UTC)
Thanks Czar; it'd be nice to add a separate keyboard shortcut for saving changes also as I would like to add a ton of newly created pages to wikiprojects to increase their involvement in the improvement of these pages. Gryllida (talk) 10:11, 25 November 2018 (UTC)
@Gryllida:I checked your contribs and it seems you haven't been using Rater in a while. Since you made this comment, Evad37 added alt-shift-S as a save button! That should make it a lot easier to use for you. Good luck! Prometheus720 (talk) 15:12, 4 May 2019 (UTC)
Sometimes I find myself in a situation where I want to unset all ratings on a page, for example when the importance is automatically filled in for a bunch of wikiprojects. At the moment this requires unsetting them all manually, or setting all the parameters to something and then setting them to nothing. What would be useful is an "Unset" option for the set all box, which would save time. Danski454 (talk) 20:00, 2 February 2019 (UTC)
I could use a modified version of this. Sometimes I need to remove all quality ratings from all banners (such that the banner templates can auto-assess as redirects, for example), but while the "set all" drop-down lets me set B-class, etc., there is no option to set all quality ratings to blank. This is slightly different from unset all, but could be useful. czar20:24, 2 February 2019 (UTC)
Some WikiProject templates do not have importance parameters (e.g. {{WikiProject Biography}}). If an importance parameter is added, and the user tries to remove it using rater, then the program crashes when generating an edit summary. This also occurs when removing the class parameter from {{WikiProject Essays}}. The error is at lines 1046 and 1047.
Latest comment: 5 years ago10 comments4 people in discussion
{{Resolved}}
Great script! I especially like the auto-load feature that I enabled. However, when I add {{WikiProject Military history}}, the template does not show up on the rater. Further, it auto fills the parameters b1=b2=b3=b4=b5= as "no". It would be nice to be able to actually see the template and check or un-check those parameters. Additionally, not saying you have to do it, but leaving a space where wiki projects could add information like task forces to their template would be great. Thanks again! Eddie891TalkWork16:37, 2 March 2019 (UTC)
Does not appear where after adding what? The instructions show how to edit the MILHIST banner's TemplateData to change the default labels when adding the banner. (You can also add other task force parameters through the rater interface.) czar21:08, 2 March 2019 (UTC)
Hm. Strange. If you type "WikiProject Military history" perfectly each time, it should add the right template as long as the connection is good. If that doesn't work, might be a bug. (If it is a bug, might be hard to track down, as it usually works.) But more often than not, I would just type "military" in that input box and select the right project name rather than needing to get the template name exact. czar22:17, 2 March 2019 (UTC)
MILHIST, and maybe one or two other banners, have a nonstandard internal structure which for some reason results in the script (most likely, the action=parse API) taking a really long time to determine the applicable classes and importances, retrieve the TemplateData, and appear – 10 to 12 seconds on my connection (which is about 7Mbps download speed). Once it's done, it will be cached in localStorage for future use, which should make it faster next time (on the same computer). But that's not such a great UX, so I might have to make a special-case hardcoding of the classes/importances for MILHIST. - Evad37[talk]00:45, 3 March 2019 (UTC)
An FYI for @Audiodude: - You might already know about nonstandard MILHIST template mentioned above, but just in case I thought to pass this your way. Cheers! JoeHebda (talk) 18:43, 3 March 2019 (UTC)
Errors when adding additional parameters to {{Computing}} template
Latest comment: 5 years ago3 comments3 people in discussion
For some reason, when I add an additional parameter (in this case |security=) to {{Computing}}, Rater produces an error dialog Warning {{security}} is not a recognized WikiProject banner. Do you want to continue?. It seems that adding a parameter is triggering the check for a valid WikiProject banner. This only happened the first time I added a parameter to the template. Attempting to add another one in a separate edit (e.g. |security-importance=) didn't trigger the warning again. — AfroThundr (u · t · c)02:51, 15 March 2019 (UTC)
Rater broke for me on Microorganism. Text below:
Rater [v.1.2.0]
Initialising:
Loading talkpage wikitext... Done!
Parsing talkpage templates...
Checking if page redirects... Done!
Retrieving quality prediction... Done!
Building interface... Failed. API error: TypeError: Cannot read property 'length' of null
___________________________________________________________________________________________________________________________________________
I have never had this happen before and I've used Rater for dozens of pages (thanks by the way). Any idea on what is causing this problem on this page specifically? I can tell you more about my beta settings and so on if that might matter. Thanks again for this lovely tool! Prometheus720 (talk) 15:54, 11 April 2019 (UTC)
One of the templates on the talk page isn't being parsed correctly by the script. I'll have to investigate further to determine the exact problem. - Evad37[talk]13:49, 15 April 2019 (UTC)
Also found breaking on Stepnogorsk Scientific and Technical Institute for Microbiology when I tried to add the Wikiproject:Military History template. I think they have a weird one. It didn't show up in the panel (though it was added in the source code). When I tried to open Rater again after adding, it broke and would not load. Upon checking the source in the talk page I found that they have a really weird syntax. Another problem project is maths (they have two templates, one of which is a glorified category called maths banner). It is on my to-do list to talk to these projects and some others and attempt to standardize so that tools like yours are more effective. If you are interested in that conversation let me know. Prometheus720 (talk) 15:59, 15 April 2019 (UTC)
@Evad37: I found another page, Julian Huxley, which has the milhist banner and yet does not break Rater! This one came up looking pretty weird, yes, but it still worked. I had no trouble. So I guess the question is, what is different between the format of this milhist banner and how it is set up on pages that break Rater? Prometheus720 (talk) 01:23, 14 May 2019 (UTC)
Any way to include pageview count from page information in the Rater panel?
Latest comment: 5 years ago3 comments2 people in discussion
Resolved
– Available from the Xtools gadget
I make my decisions on importance based mainly on 3 factors--traffic, importance to the project's discipline (which is sort of like anticipating traffic if the article is better linked-to), and which projects have the most responsibility for the article based on content. Pageview count is a huge part of my assessments, there is no access key for it, and I have to open it in a new tab. It really slows me down. I would estimate that I could probably rate another 25% to 30% more articles in an hour if pageviews were just easy to see in the panel. I am NOT asking for machine-generated importance ratings. I think that would not be good. I'm asking for you to provide the information to users, that's all. I would trade waiting a little longer for it to load, by the way. It's almost certainly faster than me doing it manually. Anyway, thanks again for Rater! — Preceding unsigned comment added by Prometheus720 (talk • contribs) 16:06, 13 April 2019 (UTC)
Greetings, When I attempt to add "Invention" I get the warning box saying it's not a wikiproject. When I type "WikiProject Invention" it adds correctly. Example here. Also on that page, if I activate Rater a second time, Invention does not show up on the list as already being there even though it is present. JoeHebda (talk) 13:42, 15 April 2019 (UTC)
@JoeHebda: If you start typing "Invention" and then select the entry from the dropdown menu, it will automatically add the "WikiProject " to input box. Otherwise, if you just hit enter after typing, the script thinks you mean the non-existent {{Invention}}. The script allows this – typing in any template name (with a warning that it might not be a project banner) – since sometimes project banners have shortcuts like {{HWY}} → {{WikiProject Highways}}, or occasionally a template might not be in the list of project banners (e.g. if it isn't categorised correctly, or if it is very new). - Evad37[talk]14:08, 15 April 2019 (UTC)
Access key for "Save changes" button?
Latest comment: 5 years ago3 comments2 people in discussion
Wondering if there is any keypress to do the "Save changes"? The reason I ask is that the button moves up & down the page depending on how many WPs there are. And sometimes the entire Rater box has a lot of empty whitespace after only 1 or two wikiprojects. JoeHebda (talk) 14:34, 15 April 2019 (UTC)
Done I've added s as an access key – Alt+⇧ Shift+S on Windows. (I do intend to redesign the whole dialog box at some point, but it hasn't been my highest priority) - Evad37[talk]15:09, 15 April 2019 (UTC)
Greetings, For Talk:Antonia of Florence, the wikicode was for {{WikiProject banner|1= and Rater is not following the redirect to {{WikiProject banner shell|1=. I added the "shell" & now Rater correctly displays the WPs. JoeHebda (talk) 12:55, 11 May 2019 (UTC)
@JoeHebda: Fixed (that redirect was created relatively recently, so I needed to add it as a known redirect of WikiProject banner shell) - Evad37[talk]02:29, 12 May 2019 (UTC)
Rater speedup tip
Latest comment: 5 years ago1 comment1 person in discussion
Greetings, At my common.js, I moved the Rater line up near the top (second place) of all the scripts. I noticed overall this causes a slight speedup for the Alt+5 to open Rater. Regards, JoeHebda (talk) 13:51, 20 May 2019 (UTC)
needs-image para not visible in drop down for some WikiProjects
Latest comment: 4 years ago4 comments3 people in discussion
When adding parameters for {{WikiProject Women scientists}} and {{WikiProject Australia}}, the drop down does not display |needs-image= as an option, even though the templates use them. They can be added by typing the whole parameter in, but why is it not in the drop down like the other parameters? --Nessie (talk) 15:15, 21 May 2019 (UTC)
NessieVL, It may be because both template have templatedata (Meaning the script does not grab them itself), but the templatedata does not have the needs-image parameter listed. WelpThatWorked (talk) 15:50, 22 May 2019 (UTC)
WelpThatWorked I didn't even know what templatedata was, but I think I updated them correctly. I assume it takes a bit to propagate to the tool? Is this also how some template parameters (like some on {{WikiProject Biography}} have checkboxes or dropdowns instead of textboxes?
Hi, At Fred Huntington article, when I "X"ed the importance parameter, Rater stalls out. Have seen this behavior on a few other WP Biography articles. A minor issue. Regards, JoeHebda (talk) 14:26, 7 June 2019 (UTC)
I have noticed this also, on any WP that does not use |importance= but has one listed anyways. If you try to remove it, rater stalls out.--Nessie (talk) 03:57, 9 June 2019 (UTC)
Rater for WikiProject military history
Latest comment: 4 years ago9 comments5 people in discussion
Greetings, Wondering if something in Rater tool can be changed to hilight a different color WPMILHIST when it displays? It is a very complicated wikiproject and I just received another talk page message about the incorrect assessments from Rater when I just take the defaults. The details are here on my talk page.
@Adamdaley: has alerted me several times of these errors. It would be helpful in Rater if that wikiproject was hilighted so I can then "Cancel" Rater & let someone else (an expert) deal with the article. Note: the backlog at Category:Unassessed biography articles was previously over 80,000. Yesterday I just completed the Hs & am now working on letter Is.
Rater is a really great tool for being able to quickly do assessments on a large number of articles. Many articles in the backlog are awaiting assessments for 1 to 2 years! Regards, JoeHebda (talk) 16:19, 13 June 2019 (UTC)
Just don't have the rater tool. It's easy to assess WP:MILHIST. Another no no is putting all no's for the b class criteria. Adamdaley (talk) 09:44, 14 June 2019 (UTC)
@Adamdaley: - It would be helpful for MH Assessment Department if that no-no could be added to a new section title, maybe Assessment tips. This guidance and more of your knowledge is valuable. Thanks for contributing. Regards, JoeHebda (talk) 13:13, 15 June 2019 (UTC)
@Adamdaley: I understand your frustration. MILHIST is a very active and respected WikiProject, and I know that Joe made an oops or two per your assessment rules. However, Rater is an incredibly useful tool for almost every other project on Wikipedia, and it's growing in usage because of that. I have personally used it to assess thousands of articles by myself--that task would be impossible if I had to go back and forth between talk page editing and the main article, looking at this or looking at that. Rater allows me to assess from the article page, without remembering exact names of projects (thank you autocomplete), and it allows me to very quickly see all the permitted classes of pages and select accurate ones. It also has autocomplete for extra parameters, which is absolutely 100% needed for the work Joe is doing (working in Biography which could overlap with literally ANY WikiProject out there). You say, "don't have the rater tool," but Joe is not working on MILHIST directly--Joe is working on probably thousands of articles that have many different WikiProjects which needto be added. And this will be a problem whether or not Joe is the one working on this backlog, or whether or not Joe uses Rater, or whether or not it's even a backlog. Every new article made through WP:BIO is going to have this same problem--people are unfamiliar with the MILHIST guidelines and should not be expected to be experts just to notify your project of an article within your scope.
I wrote a guide to the use of Rater, and I would be happy to coordinate with you on the development of a specific guide (or section) devoted to explaining MILHIST assessment to Rater users. I would like Rater and MILHIST to work together, because tools like Rater are desperately needed to maintain our nearly 6 million articles on enwiki, and because I respect the MILHIST model and the quality of your section of enwiki. However, I have to remind you, it is not possible to maintain this entire wiki with editing talk page banners in source mode. Please let me know if you'd be interested in such a joint measure.
And Joe, please do everyone a favor and be a little more careful in how you assess articles. I noticed several people upset with you on your talk page. I don't want to call you out but I don't get those responses. Quality is always better than quantity. I know it is a big backlog but there is no deadline. Thank you for your discussions and your great work on that backlog so far. Prometheus720 (talk) 15:50, 15 June 2019 (UTC)
@Adamdaley: I don't think you understand what Rater does. It allows for normal, manual assessment. A human fills out and checks all of the values input by Rater. It just makes it easier to do that with a little interface rather than making one go into the talk page source and flip back and forth to the article. It isn't a self-driving car, it's just a car with power steering. The human decides where to go and what to do, but it is made easier by a little technology.
Again, I understand your frustration but there is no need to be anything but friendly here. We are trying to build a good encyclopedia for everyone, here. People use Rater because it is a better system than editing talk pages, hands down, and more people will continue to use it as time goes on. I'm not at all asking for the B class criteria. I can find those myself, easily enough. What I am asking for is some cooperation between Rater users and MILHIST to develop a policy for how we can best serve your project. For example, maybe we could highlight your project in the window and give users a little notice. Maybe you'd prefer that we simply tag the page with your banner and not fill out any assessment info, and leave that to you. Or maybe you'd like something else. I have no idea. So if you are so worried about this, why don't we come up with a few guidelines, yeah? Prometheus720 (talk) 06:46, 16 June 2019 (UTC)
I've seen what JoeHebda does. He removes the "B class" criteria and still assess them as "C class" and that's not how it is done. The "B class" criteria requires that code to be there for, Start, C and B class. I've even put it there and he removes it and still classes that article as "C class" and I've asked him to do it properly. But removes it. Adamdaley (talk) 07:03, 16 June 2019 (UTC)
I got the same issue, too. Rater is adding |B-Class-1=no |B-Class-2=no |B-Class-3=no |B-Class-4=no |B-Class-5=no to MILHIST banners, making it look like the user did the B-class criteria checks and all checks failed. SD0001 (talk) 05:53, 17 June 2019 (UTC)
Question - Parsing of Class-B checklist
Latest comment: 4 years ago2 comments2 people in discussion
This was brought up before and I think there was some confusion about how this can be implemented. As far as I understand, it's a relatively minor but useful change. API supports a parameter that overrides the watchlist action. It would be really useful to have at least the "don't change watchlist" option, otherwise all pages get watchlisted for those who have auto-watchlist enabled. The old rater used watchlist: 'nochange' for the edit post and so didn't watchlist pages automatically. Many other tools/script do this too. To avoid forking (and maintaining) the whole script just for one change, could this be added as an optional setting? — HELLKNOWZ ▎TALK11:41, 29 July 2019 (UTC)
Greetings Evad37 - Wondering if add parameter can be pre-filled with "y" or "yes" value? This would be another time-saver. Regards, JoeHebda (talk) 10:35, 31 July 2019 (UTC)
"y" or "yes" isn't neccesarily a valid value for all additional parameters (e.g. taskforce importances). Howver, you can define autovalues in a banner's TemplateData, which Rater will then use when that parameter is added. - Evad37[talk]04:52, 1 August 2019 (UTC)
Yes I did look at TemplateData and maybe it's just me, but it is too complicated for me to understand and to change correctly. So for now I'm manually entering the "Y" for every time to Needs-photo parameter after adding the parameter - a multi-step process. If any expert knows how to do this, your help would be great. All it needs is to have "Needs-photo" auto-fill with a "Y" value when adding for the first time. Cheers! JoeHebda (talk) 18:04, 10 September 2019 (UTC)
@JoeHebda: Which WikiProject banner are you needing this done with? I'm comfortable with the whole TemplateData framework and would be happy to drive by that template's page and update it as you're requesting. Or if you wanted to gain some facility with the system yourself, I could talk you through the process via an instant messenger and then you'd be able to make that improvement to any number of banner templates at your leisure. Let me know if I can be of help either way, pal. Regards, —⚞ 🐈ℛogueScholar₨Talk🗩 ⚟My recent mischief06:57, 16 September 2019 (UTC)
@RogueScholar: Only needed for WikiProject Biography. There are over 75 thousand articles in backlog and many are missing a photo, so having that box appear pre-filled with "Y" or "Yes" is a time-saver. Thanks for your help! Sorry I don't know about instant messanger, but am a good "cloner" so if I can view the changes I can add to my offline WP-notes file (Notepad++) for future ref. JoeHebda (talk) 13:03, 16 September 2019 (UTC)
@RogueScholar: Thanks. I have a whole spreadsheet of all those logs and tools. I'm making sure each of the subprojects has all of them, and then I'm going to add links all at once. If I don't keep getting distracted. --Nessie (talk) 14:42, 16 September 2019 (UTC)
@JoeHebda: Done (click for diff) Like I said, happy to help; I'm something of an assessment nerd myself so I have tremendous respect for you jumping into such a deep hole as WP:BIO. It'll take a few hours for the change to become active for the Rater gadget (I'm not sure why, that's just been my experience.) If you have questions about any of the changes or if something still isn't quite as you had hoped, don't hesitate to hit me up on my talk page. Respectfully, Peter
@NessieVL: Done (click for diff) Everything I said above to JoeHebda goes for you as well of course, Nessie. I hope this solves your immediate problem and gives you some insight into what is, admittedly, a fairly opaque system re: TemplateData. Honestly though, if you're a naturally curious person, just knowing that the information all has to conform to the standards of JavaScript Object Notation gets you where you need to go. The web is literally bursting with online tools like validators that allow you to copy/paste your edits into them and tell you if you've done it correctly and where you went astray if you didn't. Don't let that scare you away from reaching out to me again, though, like I said I'm happy to help with this sort of stuff since it's at the intersection of several of my bailiwicks. Warm regards, —⚞ 🐈ℛogueScholar₨Talk🗩 ⚟My recent mischief14:51, 16 September 2019 (UTC)
RogueScholar Done - Just minutes ago, Rater assessment tool began pre-filling "Needs-photo" / "Photo needed?" with the Checkmark indicating a Yes. Thanks for getting this time-saver done. Regards, JoeHebda (talk) 23:52, 16 September 2019 (UTC)
Placement issue
Latest comment: 4 years ago2 comments2 people in discussion
@OxonAlex: - How do you get that button to appear. Not showing on my menus. Also, I noticed "Move to draft" (also from Evad37) is missing on my menus. JoeHebda (talk) 17:49, 21 October 2019 (UTC)
JoeHebda, my problem is that it isn't showing there. I think it should show there by default.
Interface-protected edit request on 21 October 2019
This edit request to User:Evad37/rater.js has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Please change the instances of 'mw.RegExp.escape' found on lines 212 and 1,647 of the script source code to read 'mw.util.escapeRegExp'. The former was deactivated per phab:T218339 and the latter now provides its functionality. With abudant gratitude, — ⚞ ℛogueScholar🐈 ₨🗩 ⚟21:49, 21 October 2019 (UTC)
FWIW I'm in full agreement with Xaosflux here — Evad37 was recently active and has returned fairly quickly after the pings. I said this at VPT, but I did XFDcloser because, although a personal script, it is heavily relied upon for XfD closures (and it was a trivial fix I was already aware of). I had to get offline for a bit anyway, but I left rater as something certainly far from critical. ~ Amory(u • t • c)23:41, 21 October 2019 (UTC)
Fixed[9]. I don't have any objections to trivial fixes such as [10] if one of my script suddenly stops working due to mediawiki changes. It's happened before (with OOUI in XFDcloser), and it may unfortunately happen again in the future. - Evad37[talk]23:11, 21 October 2019 (UTC)
Bug: Removing | from blp used by WikiProjectBannerShell
Latest comment: 4 years ago2 comments2 people in discussion
The following discussion is closed and will soon be archived: Version 2 has now been deployed to the main script. Thank you to all the beta testers who helped test the new version! - Evad37[talk]05:23, 28 November 2019 (UTC)
What's new?
Redesigned interface, including adding new banners and template parameters right from the main window
Improved preference handling
No need more editing your common.js, preferences now stored in a json subpage of your userspace. And they can be set from within Rater, just click on the cog wheel in the top-left
New preferences include:
Autostart on redirects
minimum number of banners for WikiProject banner shell
bypass redirects to banners
autofill class (from other banners and/or ORES prediction)
Autofill importance
Better template parsing
Better handling of WikiProject banner shell templates. They are now show in the window, can be edited like other banners, will automatically sync relevant parameters from WikipProject Biography banners, and will automatically be added/show when needed (according to you preferences)
Able to unset all class/importance ratings
Better checkbox handling for parameters with one or two allowed values: y, Y, 1, and several other "yes"-like values will result in a ticked box when the allowed value is also "yes"-like -- and similarly for "no"-like values. Unrecognised values will result in an "indeterminate" state for the checkbox.
ORES prediction now includes probability
Detects the (most common) spacing style of existing templates (around pipes, equal signs, and prior to the end braces), and will use this style when editing them
Better placement of banners when adding to talk pages -- should no longer place after existing comments
Edit summary no longer repeats the class/importance multiple times, when they are all the same
Preview and show changes now also show the generated edit summary
To test out the new beta version, change the importScript('User:Evad37/rater.js'); to importScript('User:Evad37/rater/beta.js');. Keep in mind that you'll have to redo your preferences (unless you want the default ones), and check your edits for problems. - Evad37[talk]20:19, 9 November 2019 (UTC)
Getting a visual collision of the robot icon over the field's text
Can't recreate, but had a bug where my (otherwise hidden) scroll bar kept popping in and out repeatedly, which would push everything else on screen back and forth horizontally
After adding a project, the old rater used to re-focus in the main field so I could type another
Did the old version let me click around in the background? Sometimes I ran the DYK script from the sidebar if I wasn't sure the article surpassed the stub character threshold.
As much as I think my new article is FA-worthy, the tool shouldn't auto-ORES assess as GA or FA since those require a review process
First of all, hats off to you for making the OOUI window draggable. That's amazing - I think no one has ever done this before? You should leave a note at phab:T51969 about this possibility. Making the background accessible is very desirable, but the css override seems to be a bit faulty - I tried the same thing yesterday while playing around. The #p-personal toolbar (vector skin, at the top), and the MoreMenu buttons displays upon the rater dialog, when they should have been covered. I tried increasing the z-index of the dialog, but that didn't work. Also, when the dialog covers the "More" menu and the Twinkle menu, the hover menus still show up when the cursor passes over the buttons, even though the buttons are behind the dialog. It would be great if these visual flaws could be fixed (though I don't know if it's possible).
Additionally, it would be good if the user could be allowed to add another banner while the first one is still loading. SD0001 (talk) 12:17, 11 November 2019 (UTC)
Fixed the overlap issues – needed to increase the z-index to more than 100. - Evad37[talk]
That's great! I myself tried with z-idx of 2000, I must have been putting it on the wrong element. Can the dragging be made smoother? It lags when the dialog is being moved around fast. Also, changing the classes/importance using the do all dropdown isn't removing the robot icons. SD0001 (talk) 17:54, 11 November 2019 (UTC)
Done both - set the transition timing to 0s for moving the window frame to get rid of the delay, or at least significantly reduce it. And the autofilled symbols (robot heads) will now disappear when you do a "set all" - Evad37[talk]08:48, 12 November 2019 (UTC)
At least on my end, what now happens is that the dialog doesn't move with the cursor at all. It jumps (to wherever I released the cursor) after about 10-15 seconds. That too some parts of the dialog move first, followed by the rest. SD0001 (talk) 19:16, 12 November 2019 (UTC)
I switched over from a drag-and-drop library to using plain events and callbacks, to save loading a heap of mostly unneccesary code. Not exactly sure what the problem would be... the events are obviously firing, otherwise the dialog wouldn't move at all when you dragged it - Evad37[talk]03:12, 13 November 2019 (UTC)
I'm thinking maybe some browsers/platforms don't fully support pointer events, so I've switched it to just use mouse events; maybe that will help? - Evad37[talk]12:20, 13 November 2019 (UTC) Actually, I was using an experimental/nonstandard window property visualViewport. I think replacing this with standard properties should have fixed it - Evad37[talk]12:58, 13 November 2019 (UTC)
Evaluation reported by JoeHebda
Extended content
Following list of suggestions
ORES predicted class, missing, helpful for comparison, assessment
option to change background color would be helpful, so easier to read
option for different font instead of bold-font
prefer horizontal rectangle box instead of vertical box, left column of Wikiproject names often wraps onto another line.
The ORES prediction should still be there, in the bottom-right corner - and now also has the probability percentage. I think style adjustments overrides should be done in your common.css (or skin-specific css), rather than the script's preferences, because the default styles used by OOUI windows/controls vary based on your skin (e.g. with Monobook, the fonts already aren't bold).
From doing thousands of assessments with Rater (cheers!), overall this new version, while different is still workable. Thanks. JoeHebda (talk) 14:56, 13 November 2019 (UTC)
@JoeHebda: The remaining items should now be fixed. Though for the up and down arrows to work, the focus needs to be in the main "body" of the window, not the header (including top menu bar) or footer. - Evad37[talk]01:50, 27 November 2019 (UTC)
Greetings, For the Rater window, I am able to make it "go horizontal" by switching to accessible font "aphont" and 10pt size. Wondering if a way to make popups for "Add a wikiproject..." and "Set all..." tag to also use a different (smaller) font? JoeHebda (talk) 14:08, 16 November 2019 (UTC)
The CSS you want is
htmlbody.rater-mainWindow-open.oo-ui-window-overlay.oo-ui-menuOptionWidget{/* ... styles for dropdown options ... */}htmlbody.rater-mainWindow-open.oo-ui-window-overlay.oo-ui-labelElement-label{/* ... styles for dropdown labels (e.g. "Classes", "Importances") ... */}
For "Preferences" - it would be helpful to add "Warn before exit" option (Y/N). Being a keyboard-person sometimes when canceling pop-up box using "Esc" key, if I accidently hit a second time, it Exits Rater & all changes lost. Thanks. JoeHebda (talk) 14:21, 18 November 2019 (UTC)
Thanks for continuing feedback. I do intend to do more on Rater this week (the past several days I've been more focused on the new XFDcloser gadget) - Evad37[talk]14:33, 18 November 2019 (UTC)
Done. I've implemented a close confirmation box, whenever there have been changes made (and regardless of closing by pushing the escape key or clicking the close button). I don't think this needs a preference as its just generally a good idea, and common in lots of software. - Evad37[talk]10:47, 19 November 2019 (UTC)
Feedback, status for Nov. 19
Extended content
Thanks Evad37 for above improvements. Firstly, I let those Button widgets & labels default back to bold. Then I changed line-height. Next, I adjusted rater window vheight. Lastly, I changed background-color on those popups - contrast makes it easier to read.
When I first time click on "+ Add parameter" it correctly opens up a new line, however I have to then click on "parameter name" box to open it up. It would be helpful if Rater can automaticly add that line And open with cursor parked inside that location (parm.name).
Maybe it's just me getting used to "the new look & feel" but Rater seems to be faster than before. When this new verion "goes live" these changes for my common.css should still be effective. Thanks again. JoeHebda (talk) 15:47, 19 November 2019 (UTC)
Fixed the focusing: after clicking "+ Add parameter", the parameter name input will be focused (and the list of suggestions will be shown, if there are any) - Evad37[talk]06:00, 22 November 2019 (UTC)
Feedback, WPMILHIST - Nov. 20
Check example at Talk:Owen Magee. The class-b checklist displays as "b1=y" for 1 thru 5, yet rater displays those plus new buttons for "B-Class-1" thru "B-Class-5", all set to No. These additional buttons are not needed as the plain "b1=" are sufficient. JoeHebda (talk) 15:59, 20 November 2019 (UTC)
In preferences, needs a spell check: "Minimun number of banners for WikiProject banner shell" should be "Minimum number of banners for WikiProject banner shell".
I'm encountering an issue (Example here) using Rater to add project banners to redirects when their Talk pages are themselves redirects. I believe the template calls need to be placed below the magic word, but currently they're placed above it which then breaks the redirect. I can't recall encountering this issue in the mainline version of the gadget, but that may be the result of the infrequency of this edge case.
The new version is coming along nicely; I'm quite enjoying the more polished interface and much improved UI text readability. I'm not sure if it's been brought up already, but am I mistaken in thinking that the old version would remove parameter names from the list once they had been applied to a particular template? I don't know that I can precisely articulate why I preferred that behavior, but I do. That's the only quibble I have with it currently. Thanks again for all your work on this, it really is a fantastic tool. — ⚞ ℛogueScholar🐈 ₨🗩 ⚟01:13, 22 November 2019 (UTC)
@RogueScholar: Fixed. On redirected talkpages, the banners will now be placed at the end, preserving the redirect; and I've implemented the filtering out of used parameters from the suggestions - Evad37[talk]06:05, 22 November 2019 (UTC)
@Evad37: I know there aren't too many things considered more gauche in the Wikipediaverse than expressing oneself via GIF, but in this instance I feel nothing else adequately captures my current state of mind. Thank you as well for applying the correct edit to my example diff, though I fear that when I went to do likewise upon reading your reply I may have stumbled onto a related glitch.
Just now on the redirect in question, Rater v2.0.7 failed to manipulate the WP:SCH banner that's already on the talk page, though it did report its presence and existing parameters correctly. When I attempted to change the banner's importance parameter to 'NA' to test the new functionality, it added a second instance of the template with the new parameter rather than modifying the existing one, but (satisfyingly) it did place the duplicate at the bottom of the page correctly. Do you see the same behavior in such a situation too? — ⚞ ℛogueScholar🐈 ₨🗩 ⚟06:52, 22 November 2019 (UTC)
@RogueScholar: Fixed I had the redirect-check in the wrong part of the code, which is why it was not working properly on redirects with existing banners - Evad37[talk]09:34, 22 November 2019 (UTC)
Moved from User talk:Evad37 § Rater gadget
Fixed - Evad37 [talk] 12:44, 9 November 2017 (UTC)
Done as: "Parameter suggestions not available. This WikiProject banner has not been configured for use with this tool. See the TemplateData quick tutorial or ask for help on the script's talk page."
Fixed - Evad37 [talk] 04:48, 10 November 2017 (UTC)
Done - Evad37 [talk] 22:20, 13 November 2017 (UTC)
— Insertcleverphrasehere (or here) 01:10, 11 November 2017 (UTC)
Partly done, {{WikiProject Disambiguation}} now recognised by the script - Evad37 [talk] 13:16, 15 November 2017 (UTC)
Thank you - Evad37 [talk] 15:55, 10 November 2017 (UTC)
Resolved
