Module talk:WikiProject banner/Archive 7: Difference between revisions

Revision as of 17:38, 9 August 2021

Revision as of 08:15, 23 September 2021

Line 615:

::<blockquote>"This article has been automatically rated as XX-Class by a bot because other project(s) had used this rating. Please ensure that the assessment is correct before removing the |inherited=yes parameter."</blockquote>

If you want to save on parameters we could use "auto=yes" vs. "auto=inherited" (or just remove any mention of why the bot did what it did...) –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 04:12, 7 September 2009 (UTC)

:I think it is just [[Wikipedia:WikiProject Chicago|WikiProject Chicago]] that you are tagging for at the moment? It would be much easier to just add this as a note to {{tl|ChicagoWikiProject}}. If it ever becomes more widely used we can look at supporting it here. &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 06:43, 7 September 2009 (UTC)

::I've added some code to the [[Template:ChicagoWikiProject/sandbox|/sandbox]] for consideration by the project. &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 06:50, 7 September 2009 (UTC)

I definitely prefer {{para|auto|inherit(ed)}} to a new parameter. [[User:Happy-melon|<span style="color:forestgreen">'''Happy'''</span>]]‑[[User talk:Happy-melon|<span style="color:darkorange">'''melon'''</span>]] 09:22, 7 September 2009 (UTC)

*(reply to both) This is fine with me (using note). How does using "auto=inherited" jive with Martin's usage of "note"? –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 14:48, 7 September 2009 (UTC)

:You would have to disable the default behaviour of auto, and add a note for it. Something like [http://en.wikipedia.org/w/index.php?title=Template:ChicagoWikiProject/sandbox&diff=312394534&oldid=312328175 this] perhaps. &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 14:53, 7 September 2009 (UTC)

::I c what u did thar. I'll play around with it and confer with the sponsoring project. Thanks again, both. –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 14:54, 7 September 2009 (UTC)

:I can sort this out locally, but I was wondering if anyone had any ideas for cases where the bot has assessed both class and importance (in the latter case using a default lowest importance). I was thinking autoimport=, but I was also thinking perhaps it could be passed through the auto= parameter. With a big switch statement it could just say things like "GAlow" "GAmid" etc. What would be best, in terms of forward looking if this were to be eventually provided through the banner? Is there a smarter way to do it? –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 00:24, 9 September 2009 (UTC)

::Anyone? Anyone? [[Ferris Beuller|Beuller?]] –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 14:35, 11 September 2009 (UTC)

:::Although I can't understand how importance could be successfully rated by a bot, I would plump for using a separate parameter for this, as trying to put it together would make it harder to encode and decode. &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 07:53, 13 September 2009 (UTC)

::::The wikiproject will sort categories by the default lowest importance. –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 14:55, 15 September 2009 (UTC)

===Deprecated?===

Line 1,141:

</pre>

Thanks, –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 20:25, 4 October 2009 (UTC)

:{{doing|Thinking}} not ignoring ;) &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 12:45, 7 October 2009 (UTC)

::Me too; I think this is good, but it has caveats to work through. I think we'll want to implement something like {{para|auto|stub}}, {{para|auto|inherit}}, and {{para|auto|yes}} as B/C for "stub". I shall await Martin's words of wisdom... <tt>:D</tt> [[User:Happy-melon|<span style="color:forestgreen">'''Happy'''</span>]]‑[[User talk:Happy-melon|<span style="color:darkorange">'''melon'''</span>]] 13:04, 7 October 2009 (UTC)

:::Yes, I had thought about that as well. We could go one further and allow "auto=XX" for any class, and then if class= does not match auto=, the auto verbiage is suppressed and some kind of maintenance category could be added (Automatically assessed articles that have been re-rated... or something) for a bot or human to clear the auto flag. –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 13:07, 7 October 2009 (UTC)

No words of wisdom, but a few points:

*I would definitely support using the class as the parameter value because it allows for a more descriptive message and would avoid confusion if the class is ever changed without removing the ''auto/inherited'' parameter.

Line 1,152:

*As there are only a handful of projects inheriting classes currently, I have to wonder if it is worth adding the support here when it is so easy to add the note text above to individual banners. (And it would be good to iron out the issues and sort out the best way to do this by working on a small scale first!) I still haven't got round to adding a {{para|needs-image}} parameter yet, and far more banners are likely to find that useful ...

&mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 11:42, 8 October 2009 (UTC)

:I'd suggest continuing to use "auto=yes" for the first issue. There are so many "Automatically assessed articles" that have auto=yes that it will likely never be fully converted to the new method. However, if this isn't preferable, auto=stub-inherit or something could be used. –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 11:47, 8 October 2009 (UTC)

::Why not continue to use banner notes locally for the time being? I would recommend using the class and only displaying when that class equals the current class (as you suggested). And for future-protection you could continue to use {{para|inherited}} for this purpose. (It would be easy to use {{para|auto|<nowiki>{{{WikiProject Automobiles|{{{inherited|}}}}}}</nowiki>}} on relevant banner templates if it was decided later to combine the two parameters ... &mdash;&nbsp;Martin <small>([[User:MSGJ|MSGJ]]&nbsp;·&nbsp;[[User talk:MSGJ|talk]])</small> 12:07, 8 October 2009 (UTC)

:::I think you guys are overthinking things. There are any number of ways that a bot could auto assess an article, so rather than trying to cater for them all it would (IMO) be better to keep the wording for {{para|auto}} generic so that it fits any given situation. "This article was assessed automatically by a bot" is all you really need to say; if necessary, any specifics can be outlined more fully at [[WP:AUTOASSESS]]. That's what I was going for at {{tl|Film}}, anyway. [[User:PC78|PC78]] ([[User talk:PC78|talk]]) 16:44, 8 October 2009 (UTC)

::::I can keep using notes, it's no problem. But I'm getting mixed messages here, someone suggested [[Template talk:WPBannerMeta/Archive 7#need change in auto= verbiage|last time]] to keep it all in the "auto" param =) –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 17:13, 8 October 2009 (UTC)

:::::Yes, I don't see value in using separate parameters. And I agree with PC78. The schema I'd like would be something like this:

:::::*{{para|auto|stub}} &rarr; "This article has been automatically assessed by a bot, as it uses a stub template".

Line 1,162:

:::::*{{para|auto|yes}} &rarr; '''???'''

:::::What to do with {{para|auto|yes}} is, IMO, the main question. [[User:Happy-melon|<span style="color:forestgreen">'''Happy'''</span>]]‑[[User talk:Happy-melon|<span style="color:darkorange">'''melon'''</span>]] 19:54, 8 October 2009 (UTC)

::::::As I intimated above, "auto=yes" will not be deprecated from its existing usage in the foreseeable future. –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 20:01, 8 October 2009 (UTC)

:::::::Actually, what I was suggesting is that we just use:

:::::::*{{para|auto|yes}} &rarr; "This article has been automatically assessed by a bot".

:::::::and not bother with any other parameters and/or variables, because it's suitably generic for whatever the bot is actually doing. The specifics aren't that important, IMO. [[User:PC78|PC78]] ([[User talk:PC78|talk]]) 20:14, 8 October 2009 (UTC)

::::::::Simple is good... Consider this, though. When I do a job for a WikiProject I usually auto-stub first. So I find those articles that have a {{tl|stub}} template and apply the stub class. Afterwards, I do the inheritance task. Now, if, during the inheritance task, I inherit the class of "stub"... What does that indicate? Probably that the inherited class is wrong! (Or that the article lacks a relevant stub template). Either way, it's a potential flag for action for projects that want to keep on top of these things... –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 20:38, 8 October 2009 (UTC)

:::::::::What would your bot normally do in such a situation? [[User:PC78|PC78]] ([[User talk:PC78|talk]]) 20:50, 8 October 2009 (UTC)

::::::::::All projects thus far have wanted to still inherit anyway. My point was that if we use descriptors (auto=stub for 'class stub because we found a stub template' and auto=inherit for inheritance), then we can have a maintenance cat for the intersection of class=stub and auto=inherit. –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 13:22, 9 October 2009 (UTC)

:::::::::::How does the bot currently handle inherited assessments? Does it just give the assessment, or does it also add {{para|auto|yes}}? [[User:PC78|PC78]] ([[User talk:PC78|talk]]) 15:19, 9 October 2009 (UTC)

:::::::::::OK, based on the current run for WP:BIOGRAPHY the bot adds {{para|auto|inherit}} whether or not the banner supports it? To reiterate what I said above, I don't think the banner should display a different message for each situation, because there are too many potential variations to cater for. What we ''could'' do is use different parameter values to populate different categories, which would still allow for the intersections you mention above. [[User:PC78|PC78]] ([[User talk:PC78|talk]]) 19:34, 11 October 2009 (UTC)

::::::::::::Sure, this is something we should set in the bio template itself. Perhaps alongside [[Template_talk:WPBiography#Make_auto.3Dyes_less_obtrusive|this fix?]] –[[user:xeno|<fontb facestyle="font-family:verdana"; color=":black;">[[user:xeno|'''xeno''']]</fontb>]][[user talk:xeno|<fontsup colorstyle="color:black;">^talk</font>]] 02:31, 13 October 2009 (UTC)

== "FI" class, maybe? ==