WME O5
We currently use regex to read the wikitext of an new incoming revision for the template "citation needed". My hunch is that regex is too primitive to, at speed and accurately, check for the long list of necessary templates. As a product manager, I want to extend at least that functionality or a more reliable method, to communicating to the WME data reuser that our community has labeled data as reliable or otherwise.
These templates added by an editor indicate issues that can be remedied on a fact/in a revision. Should a revision have this template added or removed, it signals that the revision contributes to making an article higher or lower quality. This is a direct heuristic for reusers of all levels to understand if an article's new revision is any more or less safe than the previous one.
Can the payload deliver when it happens in any of the languages that have these templates related in a wikidata item?
Acceptance criteria
- Please consider that this feature should be in prototype by end of current quarter
- Note addition of standard logs and metrics
- Inclusion of all templates in Details and multi-lingual options
To Do
- Rescope and figure out the schema and SLAs
- Start with the following four simple enWiki template
- Template:POV
- Template: Needs clarification
- Template:Update
- Template:Citation_needed
- Consider all dispute templates
Things to consider:
- This will need monitoring and logging as far as ...
- how long does this template remain on the page for
- at what number revision of the article is it added
- more to come ...
- We'll need to write documentation on how to use this, more marketing, as to explain the use and where it comes from.
Details
- The following link has a number of templates that the enWiki community uses for directly flagging content issues at the article level or inline.
- Please note the 7 redirects that are available for POV. This is true for other templates.
- We must include available language versions, as well. We should reference the following list
- See all dispute templates
Implementation
Follow RfC-content-labels