Wikipedia:Village pump (proposals)/Archive AE#Proposal: Complete the shortcut alphabet
{{Wikipedia:Village pump/Archive header}}
Currency/Money tags and automatic conversion/inflation adjustment?
(copied from the help desk)
I'm sure this has come up in the past but I can't seem to find any of those previous discussions.
I was thinking that a lot of articles contain references to sums of money and many of those are historic. It would be great if there was a currency tag where the editor can input the amount, type and date of the currency and the wiki would automatically convert that to present day US/EU amounts while still displaying the original amount. This could be done pretty easily with a lookup table with inflation and exchange rates for various popular currencies. -Shaocaholica 21:24, 21 February 2007 (UTC)
:Hmm... agreed, a lookup table would be handy for that. Unfortunately, wikis aren't good at making lookup tables (at least not the sort the page parser can read) -- if we do it on-wiki, it'd have to be done with an army of meta-templates. I probably know enough about templates to set it up, if I can get the methods down, although (funny thing) I don't know enough about currency exchange to know the methods -- I'd need at least a crash course in getting that done. However, this sort of proposal should probably be run past the community, before being implemented; the village pump is as good a forum as any (if nothing else, they may be able to direct you to any prior discussions, if they do exist). – Luna Santin (talk) 20:01, 21 February 2007 (UTC)
::I happen to be someone who's interested in both currency and template. Perhaps I can help. But I'd like to ask some questions first. What is the resolution of this historical exchange rate? (daily? monthly? yearly?) How is it stored in wiki? How do you want to update them? bot? oanda.com has daily historical exchange rate, but only for a few recent years. --ChoChoPK (球球PK) (talk | contrib) 04:10, 22 February 2007 (UTC)
::Wonderful--I think for out purposes annual would be sufficient resolution; It would be nice to go back as far as possible, but I know just enough to be aware of the really difficult problems here. DGG 07:06, 22 February 2007 (UTC)
::My comment ([http://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29/Archive&oldid=78477936#Past_costs_in_terms_of_today.27s_dollars_.28Inflation.29_2 eg]) the few times that this has come up is that it's really not a good idea. Historical "equivalent values" are very much an art, not a science; there's half a dozen different methods you can use, depending on what the thing being measured is and how much it was, and the results can easily vary by up to an order of magnitude or more; even done by hand, a large number of the equivalent values we have in articles are just plain wrong (usually using a consumer-price index to calculate something that's a sizable fraction of GDP...). I would strongly, strongly oppose any unchecked "on-the-fly" automatic conversion system; it's going to give spurious or misleading values as often as it gives helpful ones. It's not so bad for the last few decades, but for anything before that...
::Exchange rates are a little more sensible, but I'm not convinced they're needed for non-contemporary values. Shimgray | talk | 23:23, 22 February 2007 (UTC)
All Wikipedia templates should use small icons instead of large boxes: what do you think?
I just created {{t1|Original research2}} with a small icon, which I think should replace {{t1|Original research}} for the fact that large tags are ugly, bloated and self-referential, among other things, and really do marr the way Wikipedia looks sometimes. If you see what I've written on my user page as well as this discussion based on this essay, I suggest the creation of more such 'small icon' templates (which I will attempt to do if people think this is a good idea) and replacing all large templates at the top of pages using bots, which I don't know how to use and would greatly appreciate if someone made a bot to replace the tagged templates with the icon templates, so that all pages using the {{t1|Original research}} tag would have that changed to {{t1|Original research2}}, for example, although all templates using tags at the top of pages should ideally in my view be replaced with ones with small icons, of course. I'd really like to see this change the way Wikipedia looks for the better, but I thought I'd put it to users here for discussion.--h i s s p a c e r e s e a r c h 03:06, 21 February 2007 (UTC)
:You're taking this too far. Minor issues like Current Events and Semiprotection could stand to have less prominent warnings at the top, but we need something more noticeable than a little icon there for tagged articles with significant issues, and we don't want to hide the fact that our pages have issues when we know about it. People shouldn't go into articles full of biased language or original research without a warning beforehand, thinking they're wikipedia's best work, we need a warning to tell them "yes we recognize there's a problem, watch out for it, and we're working on it." Icons or little single line notices would be fine for current events and semiprotection , but serious warnings like POV, OR, and other major content issues should be the first thing a user reads. A neater cleaner appearance, achieved by sweeping serious problems under the rug, isn't worth it. It's like taking down all the warning signs around a big spill or construction zone because they're ugly. Night Gyr (talk/Oy) 03:31, 21 February 2007 (UTC)
:Further, using an icon gives absolutely no information about why the tag was added or what it means. We need the talk page link, at least. If you want something less prominent and more helpful, add {{tl|or}} or {{tl|sectOR}} to the specific parts you're concerned with, which both takes away the tag from the top and tells people where the problem is. Night Gyr (talk/Oy) 03:39, 21 February 2007 (UTC)
::You can look over the icon and the caption that comes when you hover over it explains everything. This could be told to new users, in some way. If any more icons are created, we'll have to work out a way in which icons don't cover each other up, too.--h i s s p a c e r e s e a r c h 04:06, 21 February 2007 (UTC)
:::Unviable. Hover boxes are both difficult to spot and a browser-specific feature. And the boxes are there for unregistered readers as much as anyone, to whom we have no prior opportunity to tell these things. Deco 06:31, 21 February 2007 (UTC)
:A box generates not only a visual feedback, but also a logical division: you must read everything inside this box to get a concept and is, in itself, conclusive, regardless of other boxes around. The icon has a main drawback: it does not give immediate feedback (the user must hover the mouse there). We want to make it public, in the most easier way, that the article has some problem. A small icon does not give the same information as a ugly purple box. -- ReyBrujo 04:20, 21 February 2007 (UTC)
::Your points do have some validity certainly, but I urge you to read User talk:Shanes/Why tags are evil and tell me specifically why that essay is wrong.--h i s s p a c e r e s e a r c h 06:21, 21 February 2007 (UTC)
:::Because it doesn't talk about content-related tags at all. I agree with the rant entirely (especially about spoilers), but tags that mention potential problems with the content of an article should be front-and-centre so people are aware of the problems before reading. Fagstein 06:51, 21 February 2007 (UTC)
::::Regardless, I've mentioned this whole idea to WikiProject Templates.--h i s s p a c e r e s e a r c h 11:03, 21 February 2007 (UTC)
:::::I think the small icons on the article pages are an improvement over the big template messages. Too often, the big template messages are used as an article-defacing weapon among editors to display their disagreement over that article. The talk page of an article is the place to discuss and inform each other of our concerns in order to improve an article, that includes maintenance and cleanup tasks (and templates in my opinion). It’s of course good to inform the reader of those concerns as well, but we don’t have to scream it out loud to them with big ugly colorful templates. The icons suffice and keep the layout of an article acceptable. --Van helsing 11:16, 21 February 2007 (UTC)
::::I think top-tags that inform the reader about an article having serious problems with factuality or bias are fine. So, tags like {{t1|TotallyDisputed}} and {{t1|POV}}, are important enough to put on top to inform and warn the readers. But in general we're using the tags too often now and in cases where a simple suggestion on talk would be much more appropriate. {{t1|wikify}}, {{t1|Uncategorized}}, {{t1|Cleanup-rewrite}}, {{t1|Copyedit}}, {{t1|Grammar}}, {{t1|Citation style}}, to name just a few, are all meant well, but they are rather confusing and distracting, and outright irrelevant to the 99% who don't even know what the word "wikify" means. They just want to learn about some part of European history or a poet or a disease. The articles should be about the subject or topic, not about Wikipedia or even about the subject on Wikipedia. Pick any article that isn't featured, and I'll have no problem in finding a tag that covers whatever flaw the article has that keeps it from being featured. We have tags for every flaw now. But do we really want a million articles to start with a big framed self referencing box? I hope not. We should keep improvement-suggestions on talk in my opinion, but as a compromise I'm fine with making most of these tags into icons. Editors will quickly learn what the icons mean, while they will be easy to ignore for those 99% who don't care about editing. Shanes 14:13, 21 February 2007 (UTC)
::::: Totally agree! Isn't one of the main benefits of those tags that they also categorize the page? I think well-intended non-wikipedians fix grammar and do minor copy-editing whenever they see such problems. I'm very sceptical that when seeing a {{tl|copyedit}} sign, they will stop and copy-edit the entire page, so it makes sense that any notices intended for maintenance should be very discrete. However, as said before, non-compliance tags are very important to even the casual reader. --Merzul 18:34, 21 February 2007 (UTC)
:::::: Well, at least some people seem to be in favour of my icons now.--h i s s p a c e r e s e a r c h 18:28, 22 February 2007 (UTC)
The whole point of such templates is to be noticed - a tiny icon in the corner won't be noticed, so you might as well just remove the template completely (and manually add the category). I think the templates serve a useful purpose, though, so I don't think they should be removed. --Tango 18:44, 22 February 2007 (UTC)
:Suggesting improvements to articles is good, and I can understand why you want them to be noticed, but drawing attention to your suggestions by putting them smack on top of articles is bad. You should use the talk page for things like that. That's what we have talk pages for. We would like the articles to be about the topic only. The style manual states that articles should start with a lead section explaining that topic, not with a self reference about that article on Wikipedia. Shanes 19:51, 22 February 2007 (UTC)
I agree with Tango and Nightgyr. Plus, I dislike the icons that are in the top corner already, and wouldn't want to see more. --Quiddity 18:49, 22 February 2007 (UTC)
It's far too easy to completely miss seeing icons that are in the corner of a page already - I can't remember the number of times I didn't realize an article was sprotected until I clicked Edit. Per arguments above, cleanup and other maintenance templates are intended to be noticeable - if someone finds them ugly, hopefully that'll be incentive to do something to the article to merit removing it. — PSUMark2006 talk | contribs 02:44, 23 February 2007 (UTC)
Matching entries on the history page
What I think would be very handy on a history page is a method that shows what past entries match the current entry. That way you can tell at a glance if the current entry had been reverted and to what prior date (without necessarily having to trust the comments). So if the matching pages could be hilighted in some manner (perhaps through the background color) it would save having to do as many page comparisons to check for vandalism. That would greatly speed up page watch checks. Thanks! — RJH (talk) 15:36, 20 February 2007 (UTC)
:P.S. To save compute time, the required information could be stored whenever a true page revert occurs. — RJH (talk)
::Probably checking just a few (five or less?) prior versions would get 90% of the cases; maybe even checking just the last two would get the vast majority. Even then, I'd worry about a bit about additional server load (yes, I know about Wikipedia:Don't worry about performance, but still ... ). Perhaps it should only check if there is an automatic edit summary ("AES" to start the edit summary) or the edit summary starts with "rv" or "re"? (I do agree that this would be useful.) -- John Broughton (♫♫) 21:54, 20 February 2007 (UTC)
:::Yes, a check of the last five or so cases would be sufficient in most cases. That would be beneficial. — RJH (talk) 16:13, 22 February 2007 (UTC)
Exporting articles to PDF
I think we should export articles to PDF. Does that sound good to anyone? - Patricknoddy 13:09, 19 February 2007 (UTC)
:That sounds hard on the servers. However, anyone can download Wikipedia's database and do it, as the license is free you could even sell the results. HighInBC (Need help? Ask me) 13:11, 19 February 2007 (UTC)
:If you are on Mac OS X, you can export to PDF. Go to File Menu and select Print. On the Print dialog you will see a PDF button in th bottom left corner. Click on it and select "Save As PDF". Voila!—Perceval 03:04, 20 February 2007 (UTC)
:If you use Windows, download [http://sourceforge.net/project/showfiles.php?group_id=57796&package_id=53473&release_id=442172 PDFCreator] which lets you easily convert anything into a PDF. Koweja 18:51, 20 February 2007 (UTC)
:What I mean is that like maybe we should create like a WikiProject-type group of editors to transport articles to PDF. - Patricknoddy 20:40, 21 February 2007 (UTC)
:This is the worst idea I have ever heard. PDF [http://www.useit.com/alertbox/20030714.html is not fit for human consumption]. It's a printer format. It should be used as a printer format, and nothing else. Raul654 17:41, 22 February 2007 (UTC)
::Disagree. I have in the past submitted reports in PDF as most people do not have PDF editors - making it almost read only on Windows computers. Thus, it was hard to lift your report or edit it to suit another purpose. I, however, disagree with exporting articles unless it is for personal usage. Ronbo76 05:33, 23 February 2007 (UTC)
So? What if someone wants to say, print it? HighInBC (Need help? Ask me) 05:29, 23 February 2007 (UTC)
:Then they can use one of the methods mentioned above! Or use the "printable version" link in the toolbox.
:Having editors/processors spend time exporting every diff of every article into PrettyDumbFormat is wasteful... --Quiddity 19:07, 23 February 2007 (UTC)
Watch Users
This is a feature request that will help vandal patrollers. Currently you can only watch changes made to an article. What I propose is to add the ability to ‘watch’ a user or ip. In this way, when you have spotted some vandalism you can add it to you watch list and keep an eye on it for a few days to see if the vandalism is recurrent.
Currently you could improvise this with some of the third-party tooling some of the patrollers use, but it would be nice to have integrated.
What do you think about this, would it be a helpful addition?
Sander123 12:37, 19 February 2007 (UTC)
:The bot pkgbot on the IRC channel #vandalism-en-wp has the concept of "blacklisted users" (all their edits are immediately reported) and "greylisted users" (like blacklisted, except it's automatically maintained and consists of users who were recently reverted). You can read more here: WP:CUV/Bots#Lists_of_users. It might still be nice though to have your own user watchlists for watching edits of friends as well as vandals that you directly associate with, and if anyone's concerned about privacy, it wouldn't reveal anything not available already through contributions. Deco 21:08, 19 February 2007 (UTC)
::I've wanted something like this before; but the problem is that it would ease wikistalking. ~ ONUnicorn(Talk|Contribs)problem solving 21:20, 19 February 2007 (UTC)
:::The privelage of watching users could be limited to admins to prevent this. Watching users would mostly apply to admins anyways. Captain panda In vino veritas 03:49, 20 February 2007 (UTC)
::I would love this option, I see not need to limit this to admins, some of our best vandal fighters are not admins. Also, all the information is already available for those who wish to wikistalk, and this feature would make such stalking easier to detect and track. No new information is being made available, just in a more convenient manner. HighInBC (Need help? Ask me) 03:51, 20 February 2007 (UTC)
:::That works for me. I was just trying to get the good of the watching users but trying to limit wikistalking. Captain panda In vino veritas 03:53, 20 February 2007 (UTC)
::::Wikistalking is a bit independent from this, I guess. If you want to follow any particular user you can just bookmark his contributions page. The problem is, I might want to follow 10 ip addresses that are vandal only, but without the inconvenience of having to check my bookmarks every day. Sander123 09:07, 20 February 2007 (UTC)
:::::WikiProject user script's script page has a script called 'user watchlist', which might do what you want. --ais523 09:14, 20 February 2007 (UTC)
::::::It doesn't work on many platforms. Won't work with anything but IE, and doesn't work on my W2K even with IE. — coelacan talk — 22:28, 22 February 2007 (UTC)
:::::::Yes, it is a bit buggy. I might also add that people living to the east of the Greenwich Meridian are likely to see less results than people living to the west, due to a bug in the way it deals with timezones. It also doesn't work very well if you use it very soon after midnight, for similar reasons. Tra (Talk) 22:45, 22 February 2007 (UTC)
Merge GA with FA? A-Class?
:See revised proposal section below
I just wanted to moot some discussion here before I did anything rash and MfD'd WP:GA, but it seems to me from reading the GA criteria against the FA criteria, there is a rapid trend in the continually evolving GA project policy towards convergence with the FA process. The key catalyst that caused me to notice this was the relatively recent strict rules adopted by GA requiring adequate citation for all GAs. It appears to me that the only major substantive difference between the two mechanisms is the approval process; for all other intents and purposes the content requirements are nearly identical.
If this is so, why not consolidate these two units together, and gradually review all GAs, a la Wikipedia:Featured articles with citation problems, for promotion to FA status. Because otherwise all I can differentiate between GA and FA is that one is better for instant gratification.
(edit): I'd also suggest that GA's which fail FA criteria in a merge be re-classified as A-class articles. This means that all articles can be individually assessed at any class level, with only one (final) candidacy step in the process, for FAC.
Thank you for your time, Girolamo Savonarola 22:48, 17 February 2007 (UTC)
:Seems that a link to Wikipedia:Compare Criteria Good v. Featured is appropriate here.
: Generally, I agree with this proposal to merge the two, but I would keep separate criteria for each on the same "guideline". (Why are none of the Featured and Good article pages tagged as guidelines?) —Doug Bell talk 23:47, 17 February 2007 (UTC)
:I like the idea. HighInBC (Need help? Ask me) 23:49, 17 February 2007 (UTC)
:The difference in approval process is a major distinction and quite likely a useful one. The GA process is far more scalable than the FA system, which is never going to assess more than a tiny fraction of the articles on Wikipedia. We should see much quicker results from GA. We haven't thus far, however, for which one can offer two reasons:
:#The GA process is bloated. It is not clear why a central candidate page exists, when all the work takes place on the talk page, but having this page certainly substantially increases the difficulty in nominating articles.
:#Further, for many articles its purpose has been obviated by effective WikiProject assessment systems.
:At the moment the GA process is probably too similar to the FA process to be adding much benefit to Wikipedia. As far as a "merger" goes, it's not clear what that would entail, but assuming that we don't want to change the FA process, it must basically mean scrapping GA. I think it would be worth at least attempting to go back to the original, simpler GA system, thus creating a clearer distinction between the processes. Christopher Parham (talk) 01:13, 18 February 2007 (UTC)
:I oppose any merger; I think there's a definite difference in actual quality, even if it's not expressed clearly in the criteria. Have a look at GAs which have failed FACs to see some of the differences. Trebor 01:52, 18 February 2007 (UTC)
::So you just think that nothing whatsoever should be done? Girolamo Savonarola 15:25, 18 February 2007 (UTC)
:::I don't know; I'm not really involved with the GA process (other than putting a couple of articles through). But many Good Articles come to FAC and fail, so there is a definite difference in standards (even if it isn't apparent from the criteria). FACs only work if there is an editor willing to work on the article, and if GAs haven't already been put through FAC then it implies there is not. Trebor 15:51, 18 February 2007 (UTC)
::I don't doubt that there is some difference, but I am questioning if it is enough of a difference to warrant the entire GA apparatus. At the current time, I'd say not. I'd merge the two projects as per my original comment, and abolish the GA class. This would benefit the assessment structure as well, since the articles can still be assessed as Stub, Start, B, or A class by a single individual, based on criteria. So I'd presume that most of the GA's which fail FA in a merger would likely be recategorized as A-class. So structurally, the article is individually assessed from Stub thru to A class, and then if the article is deemed good enough, it only has to jump through one candidacy process - the FAC. Much more linear, simple, and less bureaucratic. Girolamo Savonarola 16:03, 18 February 2007 (UTC)
:::That sounds less like a merge and more like an abolition of the GA-class and framework, which would warrant an MfD (note I'm not saying I'm necessarily against that, just saying what it sounds like). There has been a slight lack of clarity in the assessment criteria with GA- and A-class being on different scales, and overlapping to a large degree, so it would be good to clear up where they fit in. But a blanket put-through of all GA articles to the (already fairly overloaded) FAC process, regardless of whether there are editors willing to improve them, would be a mistake in my eyes. Trebor 17:54, 18 February 2007 (UTC)
- fix, don't merge. The GA idea was to have a quick and unbureaucratic way of assessing articles that are clearly good, without meeting the formal FA requirements. Now, it appears a whole bureaucracy has accreted around GA assessment as well. The solution is to get rid of it, and turn "GA" back into what it was supposed to be. There are many, many articles on WP that are good without being likely to become FA anytime soon. "GA" to my mind is a tool to facilitate measuring of the distribution of quality on Wikipedia. I say, leave FAC as it is, an assessment on the very best on WP, and turn GA back into something simple and unbloated. dab (𒁳) 16:03, 18 February 2007 (UTC)
::That simple process, in my mind, is more or less equivalent to giving an A-class assessment. See my above comment and my revised proposal. Girolamo Savonarola 16:04, 18 February 2007 (UTC)
- No merge. The difference between GA and FA is the difference between one set of eyes and several set of eyes. Hence the FA process is more like a fine tooth comb that can get to the nitty gritty assessment pieces. The purpose and benefit of the GA process is that with a single reviewer you will obviously get assessment and feedback much quicker. Of course the quality of that review is dependent on the quality standards that the GA reviewer is upholding. The push towards stricter citation is a positive development because more articles that are actually good are being recognizes and more articles that are substandard are being improved and brought to compliance with simple policies like WP:V and WP:NOR. The GA assessment process is more approachable than the FA process and is a good way for new editors (or editors new to FA) to become familiar with a criteria similar to FA but only have to deal with the feedback of one reviewer. As the overall quality of GA reviews improve then you will see more GAs succeeding at FAC. AgneCheese/Wine 16:26, 18 February 2007 (UTC)
::So what would the argument be against simply folding GA into the A-class for assessment, then? Since they both require just one reviewer, and have similar criteria. Girolamo Savonarola 17:44, 18 February 2007 (UTC)
=Revised proposal=
Here is my revised proposal based on discussions above. There seems to be a view that the GA has become overly hampered down with bureaucracy, and to many extents apes the FA criteria and structure to a high degree, with the most notable difference being the single reviewer of GA versus the community of reviewers for FA. GA also has been a curious question in regards to its somewhat incongruous shoehorning into the assessment classes (it should be noted that the GA class was not originally proposed in assessment).
Given the more rigorous GA standards from the past, its single reviewer characteristic, and the unnecessary bureaucracy, what I propose now is a merge of GA into A-Class assessment. The standards for the two, content-wise, are nearly identical, and like GA, assessment only requires a single reviewer to judge the article against the class criteria. It makes article assessment classes more straightforward, with all classes up to A being solely based on assessment, with a final bureaucratic candidacy process only required for the top distinction, FA. Based on the current criteria, it is likely that most, if not all, of GA-class articles would qualify for A-class easily. It is also much easier to implement than kicking up the current GA's for (gradual) integration into FAC, which has been noted would be a problem without an active editor. Reassessing GA's into A-class would not face this problem.
I look forward to your comments! Thanks, Girolamo Savonarola 18:19, 18 February 2007 (UTC)
:I would support that in principle, although I'm not really involved with the GA process (you may want to leave a message on GA talk). However, the assessment process is fairly haphazardly applied too, depending on the activeness of the Wikiproject (for instance the MilHist Proj seems to have a multiple-user assessment for A-class; others barely assess at all). Given my lack of familiarity with the issue though, I will see what others think (particularly if they can explain the need for, and differences between, GA and A class). Trebor 18:53, 18 February 2007 (UTC)
- We seriously do not need three different classifications for the quality of articles. >Radiant< 13:05, 19 February 2007 (UTC)
Since GA has already been shoehorned into the assessment system, perhaps the rating can be repurposed as effectively a 'B+' grade. There is currently too large of a chasm between A-class ratings (which are rare, and have an associated process in some wikiprojects) and B-class ratings (in practice used for a large range of article qualities that meet the general description of 'okay', which is not at all consistent with the rating's description). This classification could imply that the meat of the GA criteria are met (neutral, stable, referenced, reasonably complete) while allowing things like omission of minor content details, mixed referencing styles or minor formatting issues, or some prose problems, all of which (I think) would generally disqualify an article from an A rating.
I'd like to see most of the bureaucratic apparatus of GA scrapped, and what remains repurposed for its original intention: identifying excellent short articles. Current practice seems to be to call almost all short articles 'start' or 'B', on the assumption that they need expansion, but some topics just don't require more than a few paragraphs. Current practice also essentially blocks these articles from FA status, with the odd rare exception for a hurricane article. Whether this assessment class should also become part of the rating system is not obvious, as the existing ratings are not length-dependent and the 1.0 project might be too far along to permit adding or removing ratings at this stage. Opabinia regalis 17:46, 19 February 2007 (UTC)
:You want another rating? Frankly, I think some simplification is necessary. The larger chasm (IMHO) seems to be between Start and B-class. I'm not so concerned with whether or not B and A are massively different, so long as the grading scheme offers some clear identifiers (which I believe it already does, for the most part). These aren't real grades, and no one is being judged, so the need to be so precise is actually adverse to the idea of a grading asssessment (especially given that the articles are constantly evolving). It's a very coarse-grained way of tracking the general progress of a group of articles even moreso than it is used to track any individual one. Any more attention paid to how to exactly quantify the ever-shifting state of an article seems like it would only divert energies more properly spent working on the articles themselves.
:The idea is to have a coarse-grained and efficient system requiring a minimal amount of effort. Assessments shouldn't require long perusal of a given article - it should generally be obvious on a quick skim. Making more subtle gradations simply adds more time to the assessing editors' evaluations, and furthermore is likely to adversely affect the willingness of many of them to continue assessments, especially if more rules and grades are being added. The only level at which any prolonged effort should exist is the FAC. Thank you, Girolamo Savonarola 17:59, 19 February 2007 (UTC)
::Well, yes. There are currently six assessment ratings. Two (GA and FA) have separate processes and can't be assigned by an individual assessor. A third (A) is rarely used, and some projects also confine its use to articles that have been reviewed by multiple people. That leaves an individual assessor with stub, start, and B. Since stubs are usually unambiguous, assessors sort articles into start or B. Surprise! We have an encyclopedia full of start and B-class articles. I'm sure it varies between wikiprojects, but I see much larger variations in quality within than between these two rating classes, and a large gulf in quality between B and A.
::So if I were designing the rating system from scratch, it would have five levels available to assessors, of which the lowest (stub) is unambiguous, and the highest (A) is regulated by the corresponding wikiproject. (Obviously FA retains its own process.) That leaves an individual assessor with a practical choice of start, B, or B+/GA/whatever, which I suspect would help in distinguishing between 'usable' articles and 'raw material' articles. It also eliminates the problem of what to assign the current crop of GAs (and GA-quality articles) if the GA process is shut down or reformed. I would not agree that all current GAs are A-class, given the way the A rating has mostly been used. (It's possible, of course, that the problem is underuse of/overly variable standards for A ratings.) Opabinia regalis 18:29, 19 February 2007 (UTC)
:::Well, to be succinct, I believe that another rating is equal to more bureaucracy. If that's the case, then there's no point. I think you also underestimate both what a B article is and what an A is (and would be under this proposal). They should be clearly distinct. And yes, that may mean more clarity on the grading scheme definitions, but that is a lot easier than forcing yet another grade upon everyone. Please also think over my comments above about the process needing to be coarse-grained. I believe that those sentiments were reflected during the actual creation of the assessment schemata. Girolamo Savonarola 18:39, 19 February 2007 (UTC)
::::Keep in mind, also, that some projects are adopting more well-defined standards for B-Class (e.g. here). Kirill Lokshin 18:54, 19 February 2007 (UTC)
:Yes, please! This will significantly simplify the overall structure of the various assessment schemes (since they won't be structured as internal → external → internal → external, but rather as internal → internal → external, going outside a project only for the final FAC) and get rid of the GA backlog/bureaucracy/etc. issues at the same time. Kirill Lokshin 18:54, 19 February 2007 (UTC)
::Does an assessment from one Wikiproject apply for all? For instance, if WikiProject Biography assessed a military figure as A-class, would that be accepted by MilHist? Trebor 19:24, 19 February 2007 (UTC)
:::In general, it depends on the projects involved, and whether they have particular requirements for a particular assessment level. In your specific example, not necessarily, since MilHist has a formal review process for A-Class (it would, of course, be a fairly good indication that the article ought to be submitted to that review); conversely, an A-Class rating from MilHist is often copied by other projects that don't have any sort of formal review. Kirill Lokshin 19:30, 19 February 2007 (UTC)
::::Okay, that's what I would've thought. I'm just trying to think things through with regards to rating. One advantage to GA is that articles are centrally reviewed, so GAs are roughly the same quality across the project; considering the difference in activeness of Wikiprojects, A-class could end up being applied rather inconsistently. Although maybe that's not a problem, as you could take into account the processes of the project when considering the "authority" of the rating. (Excuse me thinking out loud here.) Trebor 19:39, 19 February 2007 (UTC)
:::::That's true, I suppose. (But GAs do tend to vary quite a bit depending on who's doing the actual reviewing; so I suspect that the consistency is actually pretty similar across both processes.) Kirill Lokshin 19:44, 19 February 2007 (UTC)
With the over-reaching criteria thing, a big problem with that is that discussion is rather difficult to start. Not because there's some group of people forcing GA to go one way with things, but because many people involved don't contribute to the discussions unless something really nasty happens, there's just so many candidates on the list it takes up a bunch of time :/. I for one have some things i'd like to change with the rules so that they'd go back to older, simpler versions, but I dunno how to start the discussion when sometimes people don't pay attention, and often times large chunks of rules get changed based on the discussions of maybe 3 or 4 people. Not that anyone's trying to make things bad on purpose mind you, its just discussion of process isn't very good yet.... Homestarmy 20:24, 19 February 2007 (UTC)
:I don't think that anyone is acting out of bad faith, but my whole point is that the GA process is massively inefficient and in some ways counterproductive to other larger processes. I believe that it has some merits, but it also had the bad luck to be created at about the same time, but with little true coordination with, the assessment project for 1.0. Had assessment been started a year earlier, I wonder if GA wouldn't have instead been the efforts of people to create more rigid A-class standards. And with regard to consistency of A-classification across different WikiProjects, surely we can all agree that this can be much more easily improved with tighter and clearer assessment guidelines? Girolamo Savonarola 20:34, 19 February 2007 (UTC)
::The thing is, many of the things making it more inefficient resulted from the 3 to 4 people discussions i'm talking about, and when the changes happened, not many people really said much. If there were more people to talk about things then there's certainly several rules I for one would like to see reverted to earlier versions, when GA wasn't really as inefficient. But when sometimes I propose things and maybe one person responds, (Like when I got the MoS criteria changed) it makes me feel like it would be a bad idea to just do something like that and change rules back when not many people might notice, it already has confused things a good bit in the past when that kind of thing happens. Homestarmy 20:54, 19 February 2007 (UTC)
Yeah... everyone's going to want to get their hard-worked on article to be good, instead of A-class. It's an issue that's occurred to me before.--h i s s p a c e r e s e a r c h 17:07, 20 February 2007 (UTC)
This discussion seems to have lost momentum, which is a shame because I think this is worth trying to sort out. Do people have objections to merging GAs into A-class, and think GAs are worth keeping separate? Trebor 16:32, 21 February 2007 (UTC)
: No objections to deprecating the GA rating in the assessment scheme, though I would oppose default mass migration of GA to A. That's something for wikiprojects to handle. If the goal is to disassemble the centralized GA bureaucracy, the proposal should be posted there, and probably at WT:FA too. Opabinia regalis 04:30, 22 February 2007 (UTC)
::Sorry, I just saw this discussion for the first time! It arises from the fact that the GA level as in the assessment scheme overlaps with B and (mostly) A, leading to ambiguity and confusion. I am proposing to remove the GA-level from the WikiProject assessment scheme, but have WP 1.0 bot read GAs so that WikiProjects have all GAs listed in their "WikiProject Foobar Articles by Quality" worklists. I think that should keep everyone happy and resolve this problem. Please read the proposal and leave comments. Thanks, Walkerma 04:52, 22 February 2007 (UTC)
- I suppose merging A-class with GA-class for these purposes. Considering that "A" and "B" are the only letters that the system actually uses (it uses "Start" instead of "C", "Stub" instead of "D", and nonexistent articles would presumably be "F"), rendering their use kind of arbitrary and potentially opaque (especially to people unfamiliar with the A/B/C/D/F grading scale), it might be worthwhile to replace "A" with "GA" (or perhaps "Good", to mirror "Start" and be more descriptive to people unfamiliar with WP:GA), and to replace "B" with something that is also more descriptive. Perhaps "OK"-class. (Another, related problem that is probably more significant is that "Start" and "Stub" start with the same first two letters; this is obviously a very bad idea.) -Silence 21:22, 22 February 2007 (UTC)
First link on page ought to be changed
The first link on the page to:
http://en.wikipedia.org/w/opensearch_desc.php
Gives a file of the type:
application/opensearchdescription+xml
It would be far better to link to http://en.wikipedia.org/
Lynx doesn't have a native viewer for this application, and I belive most browsers don't. Falcone 09:15, 14 February 2007 (UTC)
:Are you talking about the article OpenSearch? Or something else? I can't see anything using that link anywhere... --Quiddity 18:11, 15 February 2007 (UTC)
::He's talking about
- most browsers don't display this, and some can presumably use it to add search box abilities. --Random832(tc) 19:33, 15 February 2007 (UTC)
:::Oh, the html header metadata. I don't know anything about that.
:::Anyone else? --Quiddity 19:05, 17 February 2007 (UTC)
::::I think you'll have to ask at Wikipedia:Village pump (technical). --Quiddity 19:00, 23 February 2007 (UTC)
Proposal: Infinite Ban on all Wiki Abusers
I have being distressed, especially lately, but in fact throughout my tenure as a Wikipedian, by the number of fellow Wikipedians who have left our community. By that I mean those who have chosen or being forced to leave due to personal attacks and vandalism, either of their home pages or articles.
Its being my experience that ALL of those who fall under this category have being people who have added tremendously to our project, both in scope and depth. It is therefore a source of anger that ahmadans, who's tenure here is bellicose, offensive and in no way a meaningful contribution to Wikipedia, has driven so many invaulable colleges away.
Therefore, I wish to open a discussion on effective ways of dealing with such abuse. For my own part I would like to see such abusers (as opposed to the general Wiki user and contributor) banned very quickly indeed. Attacks by such abusers usually have being on-going for quite some time before a warning is given, and further time elapses with furthing warnings before a ban is evoked. Yet even then such bans have a finite duration.
My proposal is to replace the first warning with an outright infinite ban on any and all abuse. I would like to see this apply in the following cases:
- 1 - Where abuse has occoured on several occasions (i.e., more than twice) prior to it being brought to the attention of the wider Wiki Community.
- 2 - Where an apology for bad beheaviour and promise of future good conduct has being asked for and not given within a set time-limit.
- 3 - Where an apology for bad beheaviour and promise of future good conduct has being given and broken (no time limit on such a promise).
In my own experinece, an Infinite Ban on abusers is the only course of action open to us. We have all seen that if a given 'contributor' begins such beheaviour they will continue with it whenever and wherever they please. Therefore, simple warnings are just not good enough. Action must be taken as soon as any abuse is detected. As with illness, prevention is better than cure. And while we cannot perhaps repair the damage abusers have committed (and which we were unable to prevent) on our fellow Wikipedians in the past, it is only in our common interest for each other and Wikipedia that we do so in future.
I would very much appreciate the thoughts of other Wikipedians on this subject. Is mise, le meas mor, Fergananim 11:24, 11 February 2007 (UTC)
:There are already Community bans for people judged harmful to the community. Night Gyr (talk/Oy) 00:43, 12 February 2007 (UTC)
I would like to remind, regarding this proposal, that no one is without the potential for reform. People can grow out of ridiculous vandalism, and the reason Wikipedia is successful is because of the diversity. Aceholiday 17:26, 16 February 2007 (UTC)
::I don't think a blanket policy is needed when we have a forum for discussing these things. HighInBC (Need help? Ask me) 17:27, 16 February 2007 (UTC)
:::I, too, suspect that a blanket ban would end up (1) not solving the situation and (2) giving the real trouble makers (who know the rules and how to exploit them) another weapon to use. semper fictilis 17:59, 22 February 2007 (UTC)
Can there be any systematic topic for the discussion of tourism entrepreneurship development?
Anjan Bhuyan 09:17, 25 February 2007 (UTC)Anjan Bhuyan
Assuming I understood your question properly, my answer is that discussions taking place on Wikipedia should revolve around its development as an encyclopedia, the development of articles, the Wikipedia-based actions of users or otherwise be located at the reference desks. Thus, unless you're talking about creating an article called 'tourism entrepreneurship development' for the purpose of presenting encyclopedic information, then I think the answer may be 'no'. --Seans Potato Business 14:50, 25 February 2007 (UTC)
Regarding the multiple Account creation
Hey,
I am a student at the Indiana University. I usually look up wikipedia and its sister webpages for many of my projects and class related activities. It is of great help to me. Thank You.
The problem, rather a suggetion I would like to tell, is that you could integrate and make a common Username and password to your verious websites of the Wiki. This is a very small thing, but creating a username and password for each and every Wiki site and its sisters, like the Wikiversity, Wikimedia and others, is really a wierd feature. If it were common, it would prove useful to the users of Wikipedia and to you too. It would save some space in your servers, instead of a person having 20 records of usrenames and passwords for using wikipedia, wikiversity, wikipedia(in other languages), etc.
Thank You for your consideration.
Hardik Dani
:It's currently being worked on and hopefully it will be implemented soon. Tra (Talk) 01:40, 26 February 2007 (UTC)
Dynamic content
You guys should add a feature so that content can be marked as dynamic. For
example, many numerical references in the encyclopedia are continuously
becoming obsolete. If there were a sort of programmability to the pages,
certain information could be collected from the internet every time the page
is loaded. For example, a reference in a wikipedia entry on TUMORS to the #
of hits returned by an online medical database with the search of TUMORS
could be dynamically checked by the wiki page, and then the info is always
up-to-date. wikipedia is amazing. —The preceding unsigned comment was added by 69.143.218.127 (talk • contribs){{#if:{{{2|}}}| {{{2}}}|}}.
:I can't see how the specific example you gave would be of use (maybe it wasn't intended to be useful, and was just their for clarification) but the idea sounds good. The function should be able to retain the last available information in the event that the other website is compromised or something. There might be some technical problems. I would be worried about reliability of sites that WP has no control over but at the same time I like the idea... --Seans Potato Business 23:30, 25 February 2007 (UTC)
:Some devs are working on it, see meta:Wikidata and OmegaWiki. No ETA though. --Quiddity 01:15, 26 February 2007 (UTC)
:::There will be quite a lot of uses. Returning no. of hits isn't one, because normally you don't just want to look at the number but to view the results. I don't think there is presently any restriction on an external link that sends a search query, but in my experience such links need checking every few months. As Quiddity says, we will need to be careful in choosing the sources--and I think we'd need a new policy for live links. I would accept official government sources, and major associations. DGG 04:14, 26 February 2007 (UTC)
Cut-off point change to {{tl|Wikipedialang}}
With the continuing growth of all the Wikipedias, I feel that the "20,000 articles" mark is too low a cut-off point. I suggest that the point be changed to 25,000 instead, which (separating out those that make 50,000) would look like as follows:
----
{{#switch:{{FULLPAGENAME}}|Special:Statistics=|This Wikipedia is written in English. Started in 2001, it currently contains {{NUMBEROFARTICLES}} articles. }}Many other Wikipedias are available; the largest are listed below.
- More than 50,000 articles: Bahasa Indonesia · Català · Česky · Dansk · Esperanto · עברית · Magyar · Norsk · Română · Slovenčina · Українська
- More than 25,000 articles: Български · Eesti · Hrvatski · 한국어 · Lietuvių · Srpski · Sinugboanong Binisaya · Slovenščina · తెలుగు · Türkçe
Complete list · [http://en.wikipedia.org/wiki/Wikipedia:Multilingual_coordination Multilingual coordination] · Start a Wikipedia in another language
----
This seems less cluttered, and adds more value to the Wikipedias that make the mark. There's always more room for expansion!
Please reply at Template talk:Wikipedialang#Cut-off point change, thanks :) Jack · talk · 09:54, Thursday, 15 February 2007
09:54, 15 February 2007 (UTC)