Knowledge (XXG)

:Knowledge (XXG) Signpost/2014-09-10/WikiProject report - Knowledge (XXG)

Source 📝

251:: Check Knowledge (XXG) finds common syntactical errors. Errors range from missing closing tags, missing/extra brackets, accessibility issues and MOS issues. Errors are found by scanning the twice monthly dumps of 47 different Wikipedias and the monthly dump of English Knowledge (XXG). Daily scans are also performed on recently changed articles for five different Wikipedias, include English Knowledge (XXG). A whitelist is used so false positives do not show up as errors. Each different Knowledge (XXG) has their own configuration file. With the configuration file, errors can be turned off or on, errors can be assigned different priority values and each Knowledge (XXG) can have their own whitelist. 465:: We certainly need more Wikipedians to get involved independently if they use automated tools or not. We provide daily lists of pages with errors and everyone is invited to contribute. Pages with ISBN errors have a huge backlog and can't be done via automated tools. Moreover, we certainly prefer manual editing than bot editing since many errors involve checking the edit history. We need editors to have a closer look at pages and check whether the error reported is the result of vandalism or not. 517: 121: 111: 293:, which stopped in 2006. The project was expanded to other Wikipedias and then in 2010, it received its last major update. Until 2013, the project stagnated and infrequent checks against dumps were being made. I had started running the programs on my home computer in 2012 because of Check Knowledge (XXG) being infrequently run on the dump files and I also started making fixes. Check Knowledge (XXG) was ported over to 37: 131: 366: 91: 332:: My background is in math and computer science. Anyone who has ever read a talk message of mine knows that grammar and spelling are something I rarely use. I started out writing articles. I shifted to editing new biography articles, mostly correcting mistakes. Slowly over time I went from correcting new articles to correcting mistakes via Checkwiki. 141: 101: 360:
which fixes dozens of common syntax errors. When I discovered WikiProject Check Knowledge (XXG) I realised it was the perfect ground for me for testing AWB's code and improving it. I am not a native English speaker and sometimes I do not feel comfortable writing large portions of text. I enjoy small
30:
Checking that everything's all right: This week, the Signpost decided to have a look around with WikiProject Check Knowledge (XXG) a maintenance project not concerned so much with articles' content, but in all the tiny errors that are to be found scattered within them. Their front page gives a list
318:: I spend about the same amount of time. And there is extra time of course for fixing bugs on the automated tools, the scripts, etc. If we distribute the work better in the future and more editors involve I hope I'll need to spend less time on fixing and more time on improving the automated tool. 478:: Checking Knowledge (XXG) for syntax fixes is a great task for many editors. It involves reading many different articles, counter-vandalism (counter-vandals are the superheroes of Knowledge (XXG)), improving rendered time of pages and much more. It's the perfect task for 229:, who quietly come around with their tools and fix those small mistakes. It might not get much attention paid to it, but this week, we thought we'd feature them here so you can take a look at their work, and who knows, even give them a hand. So, we spoke to 323:
What motivated you to join WikiProject Check Knowledge (XXG)? Do you find yourself to be a bit of a "grammar nazi" or perfectionist, or maybe you feel it is the best way you can contribute if writing content isn't your
582: 170:, a maintenance project not concerned so much with articles' content, but in all the tiny errors that are to be found scattered within them. Their front page gives a list of things they mainly focus on: 495: 361:
edits and I certainly like to imagine Knowledge (XXG) as a huge encyclopaedia in which all articles follow a certain style. This is how printed books are and this is how I look Knowledge (XXG) to be.
551: 546: 487: 77: 399: 534: 374:
Is most of your scrutinizing of Knowledge (XXG) done manually or with a semi-automated script, tool or bot? Do you find these to be accurate and useful or sometimes making mistakes?
211: 528: 56: 45: 398:. Both AWB and WPCleaner are integrated with Checkwiki. WPCleaner and Checkwiki both use the same configuration files. These three tools are an integral part of Checkwiki. A 541: 432:
Active Wiki Fixup Projects, and do the projects work collaboratively to fix a common problem? How many of your participants are also members of another cleanup WikiProject?
486:
Next week, this report will chat to the editors of Scotland just before their vote for or against political independence. In the meanwhile, check out past reports in the
297:
in late summer of 2013. Since then, several detected errors have been removed, new detected errors added, whitelist function added and a ton of fixes or tweaks done.
691: 423:
is headlines that are all CAPS. 80% of these errors are found on India related articles. Upward of 25% of the broken bracket errors are related to vandalism.
21: 449: 441: 343: 666: 661: 656: 166: 445: 339: 310:: I usually spend 3-4 hours a day fixing new errors found that day. Any "free" time is spent cleaning out a backlog in an error or doing some coding. 651: 207: 290: 646: 516: 50: 36: 17: 482:. It can be beneficial for Visual Editor and automated tools. It's a nice way to get more involved in Knowledge (XXG). Try it! 302:
How much of your time that you spend on Knowledge (XXG) is used "checking" Knowledge (XXG) for errors? Is it time-consuming?
627: 218: 178: 182:
Checkwiki helps clean up syntax and other errors in the source code of the Knowledge (XXG) by finding problems such as:
357: 452:
two very challenging projects too. I think we still have to work hard in further collaboration, distributing work etc.
420: 390:
developers have worked with us to find and fix more errors. Both these tools can correct many errors in bot mode.
623: 416: 193: 415:: There is really no common problem. What I find interesting is what makes up some of the errors. For example, 260:
that shows the errors and where in the article the error is found. One can manually edit the article or use the
672: 605: 479: 395: 387: 269: 261: 226: 457:
How can the average Wikipedian come to help you out; what is a good way for them to start assisting?
200: 286: 609: 247: 230: 419:
is headlines that don't end with an equal sign. 80% of these errors are a result of vandalism.
154: 94: 578: 429: 314: 234: 124: 369:
Bots are only part of the effort to clean up Knowledge (XXG); much of it is also done by hand
186: 383: 265: 104: 289:
and a few others started the project on dewiki around September 2008. It was inspired by
134: 619: 685: 294: 277:
Tell us about the history of WikiProject Check Knowledge (XXG) and how it came to be.
350: 114: 144: 608:
project looks interesting. I already do a bit of cleanup here and there with
257: 614: 356:
banners in talk pages of biography articles. I am one of the developers of
199:
Correct, delete or move code that does not follow conventions, such as the
365: 264:
script to fix the error. One can also load up the errors inside the tools
391: 338:: I started my wikilife by fixing red links in 2005-2006 as a member of 402:
that shows each error and what each tool can fix automatically or find.
382:: It is done by manual editing and by bot. During the past year, the 237:
to get their inside perspective on WikiProject Check Knowledge (XXG).
444:
to be our little sister project. As I said before I used to work at
225:
It's one of those essential but hidden projects home to a number of
364: 55: 470:
Is there anything else you would like to add to the interview?
175: 515: 35: 594: 587: 567: 592:If your comment has not appeared here, you can try 71: 428:What is your inter-WikiProject relationship with 407:What is the most common problem you have to fix? 196:issues, such as small print or heading problems; 450:Knowledge (XXG):Disambiguation pages with links 442:Knowledge (XXG):WikiProject Fix common mistakes 344:Knowledge (XXG):Disambiguation pages with links 446:Knowledge (XXG):WikiProject Red Link Recovery 340:Knowledge (XXG):WikiProject Red Link Recovery 8: 189:, such as a missing close tags or brackets; 692:Knowledge (XXG) Signpost archives 2014-09 394:has been updating his wonderful script, 18:Knowledge (XXG):Knowledge (XXG) Signpost 595: 571: 29: 7: 612:. I'd certainly like to help out! -- 72:Checking that everything's all right 164:decided to have a look around with 57: 31:of things they mainly focus on ... 28: 577:These comments are automatically 167:WikiProject Check Knowledge (XXG) 139: 129: 119: 109: 99: 89: 641:: doing it for free since 2005. 628:22:13, 14 September 2014 (UTC) 588:add the page to your watchlist 241:What is Check Knowledge (XXG)? 1: 342:. Then I shifted into fixing 203:with respect to punctuation; 708: 206:Find articles that have 291:WikiProject Wiki Syntax 585:. To follow comments, 520: 508:"WikiProject report" → 370: 201:position of references 40: 519: 368: 39: 581:from this article's 500:"WikiProject report" 400:listing is available 346:and later by adding 185:Eliminate errors in 572:Discuss this story 557:WikiProject report 521: 371: 358:WP:AutoWikiBrowser 69:WikiProject report 46:← Back to Contents 41: 596:purging the cache 529:10 September 2014 223: 222: 58:10 September 2014 51:View Latest Issue 699: 675: 599: 597: 591: 570: 552:Featured content 539: 531: 524: 507: 499: 355: 349: 210:(list available 176: 157: 143: 142: 133: 132: 123: 122: 113: 112: 103: 102: 93: 92: 63: 61: 59: 707: 706: 702: 701: 700: 698: 697: 696: 682: 681: 680: 679: 678: 677: 676: 671: 669: 664: 659: 654: 649: 642: 634: 633: 601: 593: 586: 575: 574: 568:+ Add a comment 566: 562: 561: 560: 532: 527: 525: 522: 511: 510: 505: 502: 497: 353: 347: 160:This week, the 158: 152: 151: 150: 149: 140: 130: 120: 110: 100: 90: 84: 81: 70: 66: 64: 54: 53: 48: 42: 32: 26: 25: 24: 12: 11: 5: 705: 703: 695: 694: 684: 683: 670: 665: 660: 655: 650: 645: 644: 643: 636: 635: 632: 631: 630: 576: 573: 565: 564: 563: 559: 554: 549: 547:Traffic report 544: 538: 526: 514: 513: 512: 503: 494: 493: 492: 484: 483: 467: 466: 454: 453: 425: 424: 404: 403: 363: 362: 333: 320: 319: 311: 299: 298: 274: 273: 253: 252: 221: 220: 217: 216: 215: 204: 197: 190: 180: 173: 148: 147: 137: 127: 117: 107: 97: 86: 85: 82: 76: 75: 74: 73: 68: 67: 65: 62: 49: 44: 43: 34: 33: 27: 15: 14: 13: 10: 9: 6: 4: 3: 2: 704: 693: 690: 689: 687: 674: 668: 663: 658: 653: 648: 640: 629: 625: 621: 617: 616: 611: 607: 603: 602: 598: 589: 584: 580: 569: 558: 555: 553: 550: 548: 545: 543: 540: 536: 530: 523:In this issue 518: 509: 501: 491: 489: 481: 477: 474: 473: 472: 471: 464: 461: 460: 459: 458: 451: 447: 443: 440:: I consider 439: 436: 435: 434: 433: 431: 422: 418: 414: 411: 410: 409: 408: 401: 397: 396:autoFormatter 393: 389: 385: 381: 378: 377: 376: 375: 367: 359: 352: 345: 341: 337: 334: 331: 328: 327: 326: 325: 317: 316: 312: 309: 306: 305: 304: 303: 296: 292: 288: 284: 281: 280: 279: 278: 271: 267: 263: 262:autoFormatter 259: 255: 254: 250: 249: 245: 244: 243: 242: 238: 236: 232: 228: 227:WP:WikiGnomes 213: 209: 208:invalid ISBNs 205: 202: 198: 195: 194:accessibility 191: 188: 184: 183: 181: 177: 174: 171: 169: 168: 163: 156: 155:Rcsprinter123 146: 138: 136: 128: 126: 118: 116: 108: 106: 98: 96: 88: 87: 79: 60: 52: 47: 38: 23: 19: 638: 613: 606:WP:CHECKWIKI 556: 535:all comments 504: 485: 476:Magioladitis 475: 469: 468: 463:Magioladitis 462: 456: 455: 438:Magioladitis 437: 427: 426: 412: 406: 405: 379: 373: 372: 336:Magioladitis 335: 329: 322: 321: 315:Magioladitis 313: 307: 301: 300: 282: 276: 275: 246: 240: 239: 235:Magioladitis 224: 172: 165: 161: 159: 673:Suggestions 579:transcluded 287:Stefan Kühn 256:There is a 187:wiki syntax 480:WikiGnomes 192:Check for 83:Share this 78:Contribute 22:2014-09-10 667:Subscribe 583:talk page 430:the other 421:Error #58 388:WPCleaner 270:WPCleaner 686:Category 662:Newsroom 657:Archives 639:Signpost 624:contribs 498:Previous 417:Error #8 295:WMF Labs 258:web site 162:Signpost 125:LinkedIn 105:Facebook 20:‎ | 488:archive 413:Bgwhite 380:Bgwhite 330:Bgwhite 308:Bgwhite 283:Bgwhite 248:Bgwhite 231:Bgwhite 115:Twitter 610:AutoEd 324:forte? 135:Reddit 95:E-mail 652:About 542:Op-ed 16:< 647:Home 637:The 620:talk 615:k6ka 604:The 506:Next 448:and 386:and 268:and 233:and 212:here 145:Digg 626:) 392:TMg 384:AWB 351:blp 266:AWB 153:By 80:— 688:: 622:| 496:← 490:. 354:}} 348:{{ 285:: 219:” 214:); 179:“ 618:( 600:. 590:. 537:) 533:( 272:.

Index

Knowledge (XXG):Knowledge (XXG) Signpost
2014-09-10
The Signpost
← Back to Contents
View Latest Issue
10 September 2014
Contribute
E-mail
Facebook
Twitter
LinkedIn
Reddit
Digg
Rcsprinter123
WikiProject Check Knowledge (XXG)
wiki syntax
accessibility
position of references
invalid ISBNs
here
WP:WikiGnomes
Bgwhite
Magioladitis
Bgwhite
web site
autoFormatter
AWB
WPCleaner
Stefan Kühn
WikiProject Wiki Syntax

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.