This task involves the work of deciding how we'll evolve the set of Edit Check tags, in the context of Multi-check deployment, to help us (volunteers and staff):
- See the full range of edits people publish in edit sessions where the Reference Check is shown
- Detect false positives. Read: identify edits where the Reference Check was shown when it does not make sense for it to have been.
Requirements
| Current tag name | Current meaning | Revised tag name | Revised meaning | Notes |
|---|---|---|---|---|
| editcheck-reference-decline-uncertain | Tag applied to edits when people decline to add a reference and indicate they are not sure what citation to add as the reason for doing so. | Deprecate | Deprecate | This tag will be deprecated. Reason: this tag loses its meaning in the future where multiple Reference Checks have the potential of being shown within a single edit session. |
| editcheck-reference-decline-other | Tag applied to edits when people decline to add a reference and select "Other" when prompted to share why they made this choice. | Deprecate | Deprecate | See above |
| editcheck-reference-decline-common-knowledge | Tag applied to edits when people decline to add a reference and indicate the information they are adding is common knowledge when prompted to share why they made this choice. | Deprecate | Deprecate | See above |
| editcheck-reference-decline-irrelevant | Tag applied to edits when people decline to add a reference and indicate the information they are adding is common knowledge when prompted to share why they made this choice. | Deprecate | Deprecate | See above |
| editcheck-references | Tag applied to all edits that meet the conditions that could cause the reference edit check to be shown. | No changes to tag name | No changes to existing meaning | Both the name and meaning of this tag will remain as-is. |
| editcheck-newreference | Tag appended to all edits made using the visual editor to pages in the main namespace that involve an edit where people add a net new reference. | No changes to existing name | No changes to existing meaning | |
| editcheck-newcontent | Tag applied to all edits in which new content is added. Where "new content" in this context is defined by the conditions that were defined in T324730 and are now codified in editcheck/modules/init.js. | No changes to tag name | No changes to existing meaning | |
| editcheck-references-activated | Tag applied to edits where the reference check is actually shown to people in the process of publishing an edit. | editcheck-references-shown | No changes to existing meaning | Revise tag name to make meaning more clear. |
Done
- Requirements are implemented
- @Trizek-WMF: update mw:Edit check/Tags to reflect Requirements
Background
editcheck-references-activated is implemented in such a way that the tag is appended to all published edits if, at any point, during said browser pageview the Reference Check was shown.
This approach is helpful in so far as it enables us to see the full range of edits people publish in response to seeing the Reference Check...even when the edits people end up publishing should not have caused the Reference Check to become activated in the first place.
This approach can also be confusing in so far as it can be difficult to differentiate between the following two cases:
- The Reference Check was shown when it shouldn't have been
- The Reference Check was shown as expected and in response, someone revised their edit in a way that makes it look like the Reference Check was shown in error
i. E.g. maybe someone decides to "back out" of the Reference Check workflow and remove the new content they were seeking to add.