User talk:OhanaUnited/assessment.js

Use

As with any automated tool, you are responsible for your own edits. I'm lazy and not much for change control, so an update could accidentally lead to the script temporarily not working!

Directions

Mostly self-explanatory. Clicking on a grade link once you've chosen drop-down box parameters initiates the loading of the talk page with the updated template.

Keyboard shortcuts (accessibility thingies) are available, with alt-1 (or similar, depending on your browser) being the equivalent of clicking "Stub", alt-2 for "Start", and alt-3 for "B".

A cookie keeps track of the number of articles assessed. This is shown as "(n assessed)", where n is a number and a link, and where clicking on the link resets the counter to zero.

Objective, and authorship

He created this script in response to what he saw as an unmet need regarding the logistics of the article assessment system, and as a programming challenge. He didn't necessarily "approve of" the existing assessment system, or any "volume-based" approaches to implementing it. He has on a number of occasions mentioned his concern that there are basically only two non-trivial ratings that can be assigned: "Start" and "B". He did indeed sympathize with editors who are annoyed by "drive-by" assessments (though he thought they think these assessments are something they're not; he saw them as a rough measurement that contributes to an overall statistical picture). He had stated that his preferred assessment system would have more dimensions, which may not be feasible for a number of reasons. He had also stated that, as long as "this is a wiki", one should not have to go through a committee to give an article a rating that suggests it is "GOOD!".

The philosophy he left you with is this. The script will help with the implementation of the current assessment system, so that we can see just how useful that system is. It's early in the ballgame. Let's get it moving, even if it ends in a rain-out.

All code except for the XMLHttpRequest and Cookie wrappers is by Outriggr. He released it under the GFDL by posting it. Otherwise, he releases it under cc-by-sa-2.5.

Branching

To he or she who inherits this script: please rewrite it to act on templates more generally, such that a user can add their own template as object code in their monobook.js. It would include optional arrays of "workgroups" and "yes/no" attributes like "needs-infobox", etc. which would show up in the interface. I'm sure you can also reduce the three AJAXy functions into one. Then see the "known issues". And if the script commenting sucks, then... ha ha! –Outriggr § 04:33, 29 May 2007 (UTC)

On September 11, 2008, Outriggr chose to delete the script. I have retrieved the deleted script. OhanaUnited^{Talk page} 01:35, 27 October 2008 (UTC)

Setup

Installation

In your monobook.js,

1. copy and paste the five lines below into monobook.js. (If you are using my former metadata.js, remove it.) Next, you will customize two of the lines so the script does what you want.
2. replace the template code in the "assessmentMyTemplateCode" line with the names of the templates you want to use. Include any template options you wish. Here you are specifying which templates will show up in the script interface for adding to articles. (You could have one or thirty.) Most wikiproject templates have the form "{{TemplateName|class=|importance=}}", so when in doubt, just replace "TemplateName" with the desired template. The syntax of this line is to place the template code inside quotation marks, with a comma after each template code except the last, and square brackets around the whole set of quotation marks, code, and commas. You should be able to figure this out by looking at the example installation.
3. specify your default template by changing assessmentDefaultProject to equal whatever you want as a default. It should be an exact match to a template listed in your collection, with the correct spelling and letter case.
4. Save the edit to monobook.js, then refresh your browser as the page directions indicate.

// [[User:OhanaUnited/assessment.js]] <nowiki>
importScript('User:OhanaUnited/assessment.js'); 
assessmentMyTemplateCode = ["{{TemplateA|class=|importance=}}", "{{TemplateB|class=|importance=}}", "{{TemplateC|class=|importance=}}"];
assessmentDefaultProject = "TemplateA";
// </nowiki>

User options

For all options, spelling and CaSe are important. All settings are specified in your "monobook.js".

• REMOVED - HAS NO CONSEQUENCES IF LEFT IN YOUR MONOBOOK.JS: You can specify the project templates you want to include. (If you don't, a long list of all included projects will default.) In monobook.js, add a line in the following form, replacing the three names listed below with the template names of the projects you want to use—as many or as few as you wish, separated by commas and set off by quotation marks. The drop-down box will then include only the projects you specify here, if they have been set up in the script. The first project in the group will be the default project.

assessmentMyProjects = ["WPBiography", "WPMILHIST"];

or

assessmentMyProjects = ["WPAstronomy", "WPAVIATION", "WikiProject China", "Physics"];

• You can specify whether assessment talk page edits should be minor or not. To make them "not minor", add the following to your monobook.js:

 assessmentMarkAsMinor = false;

• The script will maintain all watchlist settings, and if you have the Wikipedia Preference "Add pages I edit to my watchlist" turned on, by default all assessed articles will be added to your watchlist. To prevent this (i.e. to maintain the watchlist status of only pages you already have watchlisted), add the following to your monobook.js:

assessmentOverrideWatchPref = true;

• You can set the following defaults related to WPBiography or other projects:

assessmentDefaultPriority = "Mid";  // (applies to any project with priority/importance ratings)
assessmentDefaultWorkGroup = "workgroupname";  // (applies to WPBiography - example "politician-work-group")
assessmentDefaultLiving = "yes" or "no";  // (applies to WPBiography - defaults only if status cannot be determined from the article)
assessmentDefaultMilHistTaskForce = "task-force-name"  // (applies to WPMILHIST)