68:
38:
311:
at that point; if there is vandalism then the bot can be told to update the end-time of the monitoring for a further few months from that date. As such it's not the same as OTRS, because any user can tag, any user can help watch, and it is intended to be used on any page with a blp concern, not just the ones specifically brought to OTRS attention.
125:
310:
A typical context is some less active biographical article that has had some vandalism or other problem editing, and having reverted we want to ensure the vandalism isn't put back 2 weeks later. So we monitor its edits for a few months "to play safe". If all's good then it automatically gets delisted
165:
whereby a user who feels a page is at risk from a BLP perspective (vandalism, smearing, improper negative or unsourced information being added, or "slanting"), or any untoward editing related to biographical material, may "tag" the page after correction, to automatically have its edits watched for an
448:
then the bot will check and update itself for that article. This is the fastest and easiest way to ensure a newly watched article will be noticed, and also makes the edit history easy to follow. The !tag command (when approved) is the other quick way, and both tags the article and updates the bot to
202:
In practice if a page were sporadically "targeted" by someone, then it may not be noticed that the problem was reinstated, even though the article subject believes it has been fixed and may have been told this. Clearly it is also utterly unfair and unreasonable to expect a biography subject, who may
324:
pages should be tagged when there has been activity that suggests they may be more likely to be "hit" again by problem editing, or when there is some kind of other concern, such as a BLP subject with concerns. In general, "driveby" (once off) vandalism is less appropriate for tagging. Factors that
357:
in a few weeks time, where a bad version might stand a while before being seen and identified by editors or readers. Therefore the article is set to be watched for an extended period by the fixing editor, in order to be sure that the problem is not recurrent, or is proactively being checked for.
481:
Various methods are used to protect against abuse or bypassing. Note that the bot cannot watch articles and additions when switched off. It will notice newly tagged articles on start-up, and report them so their recent edits may be reviewed. It will also notice articles that have been manually
198:
Whilst some pages are watched by many people and have a high profile, inevitably most do not, and only come to attention when a problem arises. Sometimes this is noticed by the biography subject themselves. In such cases, once rectified, it can be difficult to ensure that the problem is not
286:
The ideal scenario is an article that would not otherwise be sure to have problem editing noticed promptly, or which has caused upset and additional care is required to ensure the maximum level of awareness, and where it is not certain that enough users are regularly watching the article
569:- reload category (ie, checking its own list of monitored articles against the actual list of pages tagged on the wiki and synchronizing the two). Also reports any discrepancies found, ie items that appear to have been newly tagged, or manually detagged, without bot awareness.
506:
Watching lasts for several months, and may be extended at any time the problem is seen to require it. Monitoring ends automatically after several months, if no user has seen the need to update the date tag to signify a further period is needed.
78:. Users are currently encouraged to tag articles that meet the "at risk" criteria for BLPWatch, and also encouraged to join the monitoring channel to watch for recent changes to BLPWatch-tagged articles as soon as the bot begins running.
349:
The other criterion is article activity and profile. An article that has significant activity already, or where bad edits are obviously being watched for and rapdily noticed anyway, is less likely to need watching this way as well.
452:
If the edit summary does not contain "blpwatch", or if the bot is off at the time of tagging or does not for any other reason become aware, it will become recognized at the sooner of bot restart, and use of !add <article:
621:
is kept, readable by anyone with a web browser, that lists all events. Events listed include: bot start/stop, page tag/detag, and pages that were found to be newly tagged/detagged on startup. The link is at <TBA:
535:- "restarts the clock" on monitoring. Use this if an article has had continuing problems, to renew the monitoring period "from today". Only use when an edit makes it likely there may be ongoing problems.
253:
that does this task is designed to help users track edits on any BLP related "at-risk" pages, easily. It also watches carefully for attempts to bypass the system. It is currently awaiting approval.
283:. This process is designed for lower profile articles, where multiple eyeballs are less likely or where errors or further mis-editing may not otherwise be noticed and removed in seconds or minutes.
423:
hint what sort of issue to watch for. In some cases the issue may not be obvious unless users are told. Example reasons - "obvious vandalism", "insertion of POV related to X", "claims about Y".
500:
436:
Please be careful not to tag articles unnecessarily, since tagged articles must have each edit reviewed. Deliberate inappropriate misuse or removal of the tag will be treated seriously.
573:
The following three commands are being trialled for approval. If approved they will be restricted to approved users only, and the user that uses them will be named in the edit summary:
432:
of appropriate content, or "massaging" of text to a favorable non-neutral viewpoint. It is effectively able to be used for any BLP related risk, which requires attention to all edits.)
631:!info !info George Bush !revert 3 !untag 76 !tag Michael Jackson 03/2008 porn images/links !reason Michael Jackson slurs and general vandalism !redate Michael Jackson !redate 17
382:. It's that simple. The bot will pick this up and begin to monitor it when it next restarts. Since this could be some time, to force the bot to monitor it immediately, say
195:, and an unknown number of other pages which may contain biographical information or where biographical information may be added. It can also be edited by almost anyone.
176:
BLPWatch is most suitable for biographical articles that have been rectified following obvious problems or following consensus, but where concerns exist over repetition.
690:
83:
75:
550:
With an article it provides information on the monitoring status of an article, and the date monitoring was last started or reset and the user (if known) and reason.
499:, and the details of the BLP problem being watched and the editor making the edit. There is also a category, so an on-wiki "watchlist format" page is available at
650:
206:
Although this applies to all pages and all articles in principle, it is of especial priority when it refers to biographical material about living people.
270:
The subject of the article has complained and we wish to be sure that the article is being watched against further quality issues for an extended period.
133:
Any page that is considered "at risk" of untoward editing of biographical material may be tagged for BLPWatch monitoring by any editor, and will then be
52:
Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the
261:
If BLP related material or pages are felt to be at risk of mis-editing, then the page can quickly be tagged by anyone for watching. Example reasons:
173:
feed specifically for BLP-related pages that any user deems "at risk", together with protective code to address vandalistic removal of monitoring.
645:
17:
53:
232:
template (where 'from' is today's date in the format MM/YYYY). They will then automatically be watched and all edits reported to an
706:
180:
203:
have no interest or desire to know about
Knowledge, to have to watch it themselves and be forced to do so hourly or daily.
346:
In general, edits that would merit watchlisting the article as well as fixing, are likely to be edits one would tag for.
466:
will track all edits to tracked articles, and all newly tracked articles, that are added to the bot by resetting it (say
495:
where any user may stay and watch for BLP edits needing checking. A typical report will list the entire edit summary, a
614:
by the bot, which can be used as a shortcut to refer to that page or edit in bot commands for a short time afterwards.
660:
711:
475:
353:
As such, the typical BLPWatch article is a page that has been hit, and may or may not get hit again, but where
428:(Note that BLPWatch can also be used to protect articles against other less common forms of risk, for example
222:
BLPWatch is a monitoring system by which pages deemed "at risk" of BLP issues may be tagged by adding the
209:
Users are asked to help ensure the quality of BLPs by watching the output of BLPWatch when they are able.
192:
684:
672:
371:
226:
655:
288:
522:- tells the bot that an article has been added, without needing to recheck the category via !reset
406:
is the date at which watching starts or was restarted from (usually today's date), in the format
96:
45:
37:
162:
678:
463:
603:
or have another good reason (eg OTRS), you can gain access to these commands by contacting
553:
Without an article it provides information on BLPWatch itself, the bot, and its watchlist.
243:
137:
by users for a period of some months, easily extensible in the case of ongoing problems.
482:
detagged, and which may therefore need checking for improper removal of watched status.
604:
496:
700:
486:
279:
Pages that have a high profile and many users already watching in the usual way, are
250:
233:
152:
142:
138:
337:
Subtle problematic edits that might not be noticed in future and need vigilance, or
170:
23:
141:
are asked to help monitor the reports from BLPWatch to ensure quality control of
303:
way that articles at risk related to BLP can be watched for an extended period
355:
it would possibly not be promptly noticed by editors, if it were hit again
267:
The article has been vandalized in a way that suggests it may be again.
334:
Targeted problematic edits (someone singling out the specific article)
331:
Multiple attempts to make problematic edits (now or in recent history)
166:
extended period of time on behalf of users and biography subjects.
454:
or !reset, provided the tag has not been removed in the meantime.
593:- allows trusted users to "quick revert" based upon edit summary
393:
The recommended location for the tag is the bottom of the page.
485:
All articles being watched will have their edits passed to the
563:- saves a list of the current watchlist to the bot's wiki page
119:
62:
32:
151:
Quality control on biographical articles ("BLPs", short for "
444:
If an edit summary contains the word "blpwatch" in any form
446:(blpwatch, !blpwatch, {{blpwatch}}, turn blpwatch off, etc)
515:
The bot responds to the following commands from any user:
501:
Special:Recentchangeslinked/Category:BLP watched articles
307:
constant checking by editors or the biography subject.
179:
For manual patrol of biographies of living persons, see
111:
104:
74:
This page describes a process based upon a bot that is
88:
This notice can be removed when the trial period ends.
340:
A higher level of concern than usual for any reason.
44:
This page is currently inactive and is retained for
82:Automated tags and tag management capabilities are
191:As of March 2008, Knowledge contains some 260,000
691:Knowledge:Bots/Requests for approval/BLPWatchBot
580:- allows trusted users to quickly detag articles
199:reinstated days, weeks, or a few months later.
187:The need for monitoring of biographical material
503:, but this cannot detect removal of the tag.
8:
651:Knowledge:Biographies of living persons/Help
273:The article is prone to disruptive editing.
681:- the BLPWatch monitoring bot's user page
380:actual page/s affected that need watching
687:- the discussion page for the bot itself
646:Knowledge:Biographies of living persons
246:, technical assistance, and the like.
18:Knowledge:Biographies of living persons
640:Policies, guidelines and project pages
325:make a page more appropriate include:
193:biographical articles on living people
155:") is a high priority for Knowledge.
693:- Bot approval request page (current)
539:!info <optional article or id: -->
474:in IRC). The relevant category is at
7:
675:- the template used for this process
527:{{Blpwatch|from=DATE|reason=REASON}}
295:Comparison with other BLP processes
242:. Such channels already exist for
31:
299:BLPWatch aims to provide a quick
667:BLPWatch and BLPWatchBot related
123:
66:
36:
597:If you are heavily involved in
169:It is effectively a controlled
584:!reason <article or id: -->
533:!redate <article or id: -->
181:Knowledge:Living People Patrol
1:
578:!untag <article or id: -->
476:Category:BLP watched articles
153:biographies of living persons
257:When is BLPWatch appropriate
76:being presented for approval
661:Knowledge:Flagged revisions
623:or can be found via !info.
462:Once an article is tagged,
728:
374:|from=DATE|reason=REASON}}
229:|from=DATE|reason=REASON}}
94:
585:reason=<newreason: -->
529:- quickly tags an article
472:!add <articlename: -->
281:unlikely to need BLPWatch
131:This page in a nutshell:
610:All edits are given an
135:automatically monitored
707:Inactive project pages
600:#wikipedia-en-blpwatch
492:#wikipedia-en-blpwatch
239:#wikipedia-en-blpwatch
236:monitoring channel at
685:User talk:BLPWatchBot
526:!tag <article: -->
520:!add <article: -->
390:in the IRC channel.
384:!add <article: -->
84:currently under trial
587:- updates the reason
656:Knowledge:Vandalism
591:!revert <id: -->
320:When to tag a page
291:, to ensure this.
218:Summary of process
24:Knowledge:BLPWatch
712:Knowledge patrols
673:Template:Blpwatch
458:Effect of tagging
362:How to tag a page
289:in the normal way
163:monitoring system
149:
148:
93:
92:
61:
60:
22:(Redirected from
719:
679:User:BLPWatchBot
375:
230:
127:
126:
120:
114:
107:
89:
70:
69:
63:
57:
40:
33:
27:
727:
726:
722:
721:
720:
718:
717:
716:
697:
696:
637:
632:
629:
617:Additionally a
513:
460:
442:
399:
397:Date and reason
369:
364:
322:
317:
315:Operation guide
297:
259:
224:
220:
215:
189:
139:IRC-based users
124:
118:
117:
110:
103:
99:
80:
67:
51:
29:
28:
21:
20:
12:
11:
5:
725:
723:
715:
714:
709:
699:
698:
695:
694:
688:
682:
676:
669:
668:
664:
663:
658:
653:
648:
642:
641:
636:
633:
630:
628:
625:
601:
595:
594:
588:
581:
571:
570:
564:
558:
557:
556:
555:
554:
551:
536:
530:
523:
512:
509:
493:
459:
456:
441:
438:
434:
433:
425:
424:
412:
411:
398:
395:
376:
363:
360:
344:
343:
342:
341:
338:
335:
332:
321:
318:
316:
313:
296:
293:
277:
276:
275:
274:
271:
268:
258:
255:
240:
219:
216:
214:
211:
188:
185:
171:recent changes
147:
146:
128:
116:
115:
108:
100:
95:
91:
90:
71:
59:
58:
50:
41:
30:
15:
14:
13:
10:
9:
6:
4:
3:
2:
724:
713:
710:
708:
705:
704:
702:
692:
689:
686:
683:
680:
677:
674:
671:
670:
666:
665:
662:
659:
657:
654:
652:
649:
647:
644:
643:
639:
638:
634:
626:
624:
620:
615:
613:
608:
606:
602:
599:
592:
589:
586:
582:
579:
576:
575:
574:
568:
565:
562:
559:
552:
549:
548:
547:
546:
545:is an alias)
544:
540:
537:
534:
531:
528:
524:
521:
518:
517:
516:
510:
508:
504:
502:
498:
494:
491:
488:
483:
479:
477:
473:
469:
465:
457:
455:
450:
447:
439:
437:
431:
427:
426:
422:
418:
414:
413:
409:
405:
401:
400:
396:
394:
391:
389:
385:
381:
377:
373:
368:
366:Add the tag:
361:
359:
356:
351:
347:
339:
336:
333:
330:
329:
328:
327:
326:
319:
314:
312:
308:
306:
302:
294:
292:
290:
284:
282:
272:
269:
266:
265:
264:
263:
262:
256:
254:
252:
247:
245:
241:
238:
235:
231:
228:
217:
212:
210:
207:
204:
200:
196:
194:
186:
184:
182:
177:
174:
172:
167:
164:
161:is a new BLP
160:
156:
154:
144:
140:
136:
132:
129:
122:
121:
113:
109:
106:
102:
101:
98:
87:
85:
79:
77:
72:
65:
64:
55:
49:
47:
42:
39:
35:
34:
25:
19:
618:
616:
611:
609:
598:
596:
590:
583:
577:
572:
566:
560:
542:
538:
532:
525:
519:
514:
511:Bot commands
505:
490:
484:
480:
471:
467:
461:
451:
445:
443:
435:
429:
420:
416:
407:
403:
392:
387:
383:
379:
367:
365:
354:
352:
348:
345:
323:
309:
304:
300:
298:
285:
280:
278:
260:
248:
237:
223:
221:
208:
205:
201:
197:
190:
178:
175:
168:
158:
157:
150:
134:
130:
81:
73:
54:village pump
43:
464:BLPWatchBot
440:Recognition
105:WP:BLPWATCH
701:Categories
449:watch it.
244:unblocking
48:reference.
46:historical
234:IRC-based
97:Shortcuts
635:See also
627:Examples
489:channel
372:Blpwatch
301:informal
227:Blpwatch
213:Overview
159:BLPWatch
112:WP:BLP/W
612:item id
430:removal
408:MM/YYYY
378:to the
305:without
567:!reset
468:!reset
417:reason
388:!reset
561:!dump
543:!help
421:brief
419:is a
16:<
605:ST47
497:diff
415:The
404:date
402:The
249:The
143:BLPs
622:-->
619:log
487:IRC
470:or
453:-->
386:or
251:bot
703::
607:.
478:.
370:{{
225:{{
183:.
541:(
410:.
145:.
86:.
56:.
26:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
