編輯檢查
編輯檢查
在人們編輯時提供有關維基百科方針的可操作回饋。
|
在2024—2025年的會計年度中,編輯團隊正在對視覺化編輯器進行一系列改進,以幫助新志願者理解並遵循對維基百科專案進行建設性更改所需的一些方針與指引。
您可以在下文看到本專案的目標、歷史以及維基媒體基金會產品部門優先考慮這項工作的原因。
參閱Editing team/Community Conversations 以了解有關此專案的預定會議。
Several features are available within Edit Check:
目標
- 來自撒哈拉以南非洲地區的新人和新手貢獻者在編輯並發布他們滿意且資深志願者認為有用的變更時,會感到足夠安全和自信。
- 英語和法語維基百科的管理人員會注意到新手的編輯品質有所提升,並有動力配置編輯檢查呈現方針的方式。
狀態
Edit Check work is ongoing in a few areas:
- T341308 - Refining the user experience for showing multiple Edit Checks within a single edit
- T360591 - Developing an API to increase the speed and ease with which new Edit Checks and Suggested Edits can be introduced within/alongside the visual editor.
- T364505 - Creating a UI framework to ensure people experience new Edit Checks and Suggested Edits as part of a common language
- T368274 - Researching the feasibility of using a large language model to detect peacock behavior within the edits people are making.
Looking ahead, the Editing Team will continue developing Edit Check during the 2024-2025 fiscal year. This work will support the Wiki Experiences Objective.
In other Edit Check news:
- Selena Deckelmann shared a demo of Reference Check at Wikimania
- After an informal demo with Polish users present at Wikimania, volunteers at pl.wiki decided to enable the Reference Check.
- Following Wikimania as well, volunteers at en.wiki are discussing deploying Reference Check.
- Note: if you are interested in enabling the Reference Check at your wiki, please ping User:Trizek (WMF) or User:PPelberg (WMF), or contact us on our talk page.
This Wednesday (3 July) from 17:30 until 18:50 UTC, the Editing Team will host the next Community Conversation.
Wednesday's conversation will be focused on the following Edit Check-related topics:
- Discussing the user experience for Paste Check. This next Edit Check we'll be introducing is meant to help newcomers adding new content unknowingly make a copyright violation.
- Reviewing the state of the Edit Check proejct. What Checks are available at what wikis? What new Check are being planned? More broadly, what strategy is guiding the Edit Check in this coming year? Etc.
On Tuesday (18 June), Reference Check became available by default at all Wikipedias except bn, de, en, hi, id, nl, pl, and ru.[1]
從週四(6月13日)開始,嘗試在視覺化編輯器(桌面版和行動版)中新增外部連結的使用者在嘗試連結到被專案封鎖的網域時將立即收到回饋。
連結檢查(我們如此稱呼)根據以下來源評估人們嘗試連結的所有外部網域:
- 本地名單:
MediaWiki:BlockedExternalDomains.json
andMediaWiki:Spam-blacklist
- 全域名單:
meta:Spam_blacklist
演示:進行編輯時的「編輯檢查」 目前,人們在編輯時有可能在兩種情況下遇到「編輯檢查」:
- 在發布流程中,當人們試圖在為提供參考的情況下發布新內容
- 在Citoid中,當人們試圖引用的網域被專案認為應該封鎖
While presenting Checks in the moments above have proven effective, for a while, volunteers and staff have been sharing ideas for Checks that could appear while people are actively adding/changing content within the article.
With this initial technical demo, the Editing Team is exploring what it could be like for Checks to:
- Appear within/alongside the editable document, in the moment when people make a change that causes a check to be activated
- Respond when people make a change that impacts the Check that they activated
What do you think about this idea? What questions/concerns/ideas/etc. does it bring to mind?
Please share what you think on the talk page!
「參考檢查」的A/B測試報告現已出爐。「參考檢查」提高了新手編者發布的編輯品質,並且沒有造成任何嚴重干擾。
「編輯檢查」A/B測試(T342930)的初步結果得出了以下結論:
- 當「編輯檢查」運作時,新人和新手貢獻者新增為新內容編輯新增參考資料的可能性是原來的2.3倍。
- 沒有觀察到編輯完成率和編輯放棄率急劇下降。
- 「編輯檢查」對於新手和行動裝置使用者的影響尤為明顯。
- 我們觀察到,與不顯示「編輯檢查」的情況相比,顯示「編輯檢查」的編輯品質略有下降甚至沒有變化。
- 這確實增加了帶有參考的新內容編輯被還原的比例。我們需要進一步調查影響。
作為結果,「編輯檢查」已預設部署至A/B測試wiki。
Reference Reliability
-
Reference Reliability (mobile)
-
Reference Reliability (desktop)
On 7 March, the first iteration Reference Reliability check became available to everyone at all wikis, by default.
This means that whenever anyone attempts to cite a source that a project has blocked, they will be made aware directly within Citoid and prompted to try another source.
Where "blocked" on in this context means the domain someone is attempting to cite is lited on MediaWiki:Spam-blacklist
or MediaWiki:BlockedExternalDomains.json
.
進行中
- 參考檢查部署 - 第一版「編輯檢查」(參考文獻)現已在22個wiki上線。 新一批wiki是用於A/B測試。 我們將驗證使用者是否會與「編輯檢查」互動並繼續編輯。
- 多重檢查 - 目前,「編輯檢查」配置會向人們顯示一條回饋,無論是否需要其他回饋。 使用者體驗正在設計當中,以便在單次編輯中顯示多個檢查。
即將到來
- 參考可靠性 - 「參考可靠性」會通知使用者該來源是否列在
MediaWiki:Spam-blacklist
或MediaWiki:BlockedExternalDomains.json
中。 這將與「參考檢查」的A/B測試一起部署。
進行中
- 參考檢查部署 - 第一版「編輯檢查」(參考文獻)現已在11個wiki上線。 您可以透過造訪編輯檢查/部署狀態 上列出的Special:Recent變更的連結來查看人們正在進行的編輯類型。 ar.wiki和vi.wiki的額外部署預定於12月4日當週進行。
- 社群通話會議 - 11月28日(星期二),10名法語志願者與編輯團隊成員一同參加了社群通話會議。 在此處查閱對話摘要 。
- 參考可靠性 - to support the next Edit Check (reference reliability), the team is developing an API that will enable Citoid to provide people feedback when the domain they are attempting to cite exists on
MediaWiki:Spam-blacklist
orMediaWiki:BlockedExternalDomains.json
.
即將到來
- 使用者腳本 - 「編輯檢查」即將能透過使用者腳本 使用。 This will make it easier for volunteers to experiment with Edit check regardless of if and how it is deployed at the wiki they are wanting to assess it on.
- 多重檢查 - Currently, Edit Check is configured to show people one piece of feedback, regardless if other feedback might be warranted. The team is in the early stages of designing a user experience that will accommodate presenting people with multiple checks within a single edit.
下一個功能:參考可靠性
The first Edit Check (editcheck-references
) prompted people adding new content to include a reference when they did not do so themselves.
The next Edit Check will prompt people to replace a source when they attempt to cite a domain a project has deemed to be spam.
The Editing Team sees this as a first step towards a potential future where editing interfaces can use the consensus stored in pages like w:WP:RSP to offer people feedback about the source they are attempting to cite.
我們正在探索的設計如圖所示。
我們現在需要您的幫助: 您最喜歡哪一種措施? 您如何欣賞這種措施? 這些措施帶給您哪些問題或擔憂?
上週三(2023年10月11日),「編輯檢查」可供第一批wiki的桌面版和行動版視覺化編輯器使用: dag.wiki, ee.wiki, fat.wiki, gur.wiki, gpe.wiki, ha.wiki, kg.wiki, ln.wiki, tw.wiki
You can review the edits Edit Check was activated within by filtering Special:RecentChanges using the editcheck-references-activated
tag.
Reporting False Positives
Ahead of the first iteration of Edit check being offered at an initial set of partner wikis, there is a new page to report false positives: Edit check/False positives .
The page draws inspiration from Wikipedia:Edit filter/False positives. 它的設計便於以下操作:
- 報告不應該啟動「編輯檢查」的編輯;以及
- 建議更改「編輯檢查」的配置方式
We are curious to know what – if any – questions, concerns, and/or ideas this new page brings to mind.
Trying Edit Check in production
As of today, anyone can try Edit Check by editing any Wikipedia page in the main namespace using VisualEditor.
若要試用「編輯檢查」,請將下列參數附加到您要編輯的頁面的URL末尾:ecenable=1
。
例如 https://en.wikipedia.org/wiki/Jollof_rice?veaction=edit&ecenable=1
Baseline metrics
編輯團隊計劃使用以下兩項指標來評估最初的「參考檢查」的影響:
- 依使用者體驗等級的新內容編輯被復原的比例減少
- 包含參考文獻的新內容編輯比例增加
為了幫助設定上述兩項指標的目標,我們最近完成了基準分析。 以下是我們了解到的一些情況:
- Across all Wikipedias, new content edits that include a reference are ~2x less likely to be reverted (6.2%) than edits that do not include a reference (11.5%)
- Across all Wikipedias, newcomers and junior editors are less likely to include a new reference with new content edits compared to more senior editors.
- Of all the new content edits newcomers make across Wikipedias, 12% of these edits include a reference.
- Of all the new content edits people who have made >500 cumulative edits across Wikipedias, 26% of these edits edit include a reference
儲存並顯示拒絕回應
In March, we shared plans to present people who decline to add a source when Edit Check prompts them to do so with a way to share why they made this decision.
This past week, we converged on how Edit Check will initially make these responses available to experienced volunteers...
To start, the reason someone selects for declining to add a reference when Edit Check invites them to do so will get logged as an edit tag that is "appended" to that edit.
兩個新的變更標籤
This week, two new Edit Check-related change tags became available that you can use to filter Special:RecentChanges.
These tags will help us collectively evaluate the extent to which the reference Edit Check increases the likelihood that people accompany the new content they're adding with a reference.
標籤 | 說明 | 試用 |
---|---|---|
editcheck-newreference
|
Edits made with the visual editor that involve people adding a new reference to an article in the main namespace. | en.wiki, fr.wiki |
editcheck-newcontent
|
Edits made with the visual editor that involve people adding new content to article in the main namespace | en.wiki, fr.wiki |
Note: the logic that determine when the two tags get applied is the same logic that is used to decide whether people should be presented with the reference Edit Check.
「編輯檢查」原型(行動版)準備就緒
A prototype for the first Edit Check is ready! Now, we need your help identifying how it might need to be fixed and improved before being enabled in production as a beta feature.
You can find instructions for trying out the Edit Check prototype and sharing feedback about on the talk page: Seeking Feedback: Edit Check Prototype .
For context, this first Edit Check that will prompt newcomers who are contributing new content without including a corresponding reference to consider doing so.
First version
The first version of Edit Check is almost ready for you all to try!
Within the next week, you can expect us to share a link to a test wiki where you can try the Edit Check prototype.
This first iteration will invite people who add more than 50 new characters to an article in the main namespace to include a reference in the edit they're making, IF they have not already done so themselves.
In the meantime, you can see the kinds of edits EditCheck currently thinks warrant a reference, by filtering Recent changes using the newly-introduced editcheck-references
tag. View the tag on en.wiki and fr.wiki.
Informed by community conversations (still ongoing)[2][3][4][5] and a series of technical and design investigations[6][7][8], during February the Editing Team became clear about the first version of Edit Check on mobile...
- User Experience: the first version of Edit Check will introduce a new step within the mobile visual editor's publishing workflow that people will see if/when they add new content without a reference. Design for the desktop user experience is still underway. See T329579.
- Usability Testing: to learn whether people understand and can intuitively navigate the mobile Edit Check workflow, we will soon begin a series of usability tests. See T327356.
- Technical Investigation: Edit Check will use a "transaction-based" approach for determining what new content is added within a given edit session. Work on developing a way to detect individual sentences is ongoing in T324363.
- Initial Heuristic: To start, the initial Edit Check heuristic will be relatively straightforward in so far as it will prompt people to decide whether the change they are making warrants a reference if/when they are adding a new paragraph and that paragraph does not already contain a reference. See T324730 and T329988#8654867.
Next up: the Editing Team will be implementing the initial Edit Check heuristic (T324730) and a corresponding hidden change tag (T324733) so that we – volunteers and members of the Editing Team – can evaluate the extent to which the reference check heuristic is getting initiated in expected cases.
Work on Edit Check is underway! Below you will find an overview of what the Editing Team is actively working on…
- Community conversations: Between October 2022 and January 2023, the Editing Team hosted seven community conversations to learn what contributing to Wikipedia has been like for people living in and from Sub-Saharan Africa. Next week, you can expect the team to publish the findings from these conversations and how they will inform the work we do on this project.
- Initial Focus: The first feature the team will be introducing is one that checks whether the new content people are attempting to add includes a reference. Learn more in the Strategy and Approach section below.
- Design: The team is actively working on a proposal for what the mobile user experience for the first reference check could be like. In the coming weeks, we will be inviting volunteers to help us revise and refine these designs. In the meantime, you can follow along with this work in Phabricator.
- Talking with experienced volunteers: for the "reference check" to be useful to inexperienced and experienced volunteers alike, it will need to guide people to cite references in ways that projects expect. In the coming weeks, we'll begin conversations with experienced volunteers to learn what these expectations are so that we can ensure Edit Check is configured in ways that align with them.
- Technical investigations: For the "reference check" to work, the software will need to know when people are attempting to add new content, whether that new content warrants a reference, and whether it currently contains a reference. The Editing Engineering team is currently doing a series of technical investigations to decide how we will approach building this functionality.
策略與措施
To equip newcomers and Junior Contributors from Sub-Saharan Africa with the know-how and tools to publish changes they are proud of and that experienced volunteers consider useful, the Editing Team will be introducing new functionality within the visual editor (desktop and mobile ) that will check the changes people are attempting to make and present them with actions they can take to improve these changes in ways that will align with established Wikipedia policies and guidelines.
The first "check" the Editing Team will be introducing is one that will detect when people are attempting to add new content to an existing article without a corresponding reference and prompt them to do so. The functionality will be accompanied by a complimentary set of features that will enable moderators to configure the user experience newcomers and Junior Contributors will see to ensure the software is guiding them to take actions that align with project policies and conventions.
挑戰
The visual editor's growing popularity among people who are new to editing Wikipedia[9] leads us to think that the editing experience has been reasonably successful at helping inexperienced volunteers learn the technical skills necessary to publish changes to Wikipedia.
The trouble is that the visual editor and other editing interfaces do not make people aware of the Wikipedia policies and guidelines they are expected to follow.
As a result, the changes inexperienced volunteers publish often break established best practices and lead to undesirable outcomes for inexperienced volunteers, experienced volunteers, and Wikipedia projects as a whole:
- Inexperienced volunteers become disappointed and frustrated when the good-faith change(s) they arrived to the wiki seeking to make are undone (read: reverted), deleted, and/or scrutinized in inequitable ways. These poor interactions are demotivating and drive these could-be volunteers and community members, and the knowledge that are uniquely positioned to offer, away.[10]
- Experienced volunteers/moderators need to do more work reverting low-quality edits and posting messages on inexperienced volunteers' talk pages to make them aware of the policies and/or guidelines they are likely to have unknowingly broken. Continually needing to educate inexperienced volunteers and undo their changes can lead to experienced volunteers becoming skeptical of inexperienced volunteers and impatient with them.
- Wikipedia projects struggle to grow and diversify their volunteer populations and shrink the knowledge gaps present within Wikimedia wikis.
This project seeks to address the challenges above by:
- Offering inexperienced volunteers relevant and actionable feedback about Wikipedia policies in the precious moments when they are in the midst of making a change using the visual editor.
- Equipping moderators with a new ability to specify the feedback inexperienced volunteers are presented with while they are editing
改變理論
This project is built on the belief that by surfacing relevant guidance in the precious moments when inexperienced volunteers are in the midst of making a change to Wikipedia and equipping them with the know-how and tools necessary to apply this guidance, they will make changes they are proud of and that experienced volunteers value.
In the longer term, the Editing Team thinks that people who are new, particularly people who have historically been excluded from and harmed by established power structures, will feel safe and motivated making changes to Wikipedia if they can accurately predict whether the changes they are attempting to make are aligned with existing Wikipedia policies, guidelines, and/or cultural conventions.
More broadly, the Editing Team thinks that to evolve towards a future where wikis' policies and cultural norms – and ultimately, content – reflect the diverse experiences of the people these projects are intended to serve, we first need to make the norms and standards that are currently in place legible and actionable to people while they are editing.[11] This way, volunteers can develop shared awareness of cases where these norms and standards are not having the impacts they were intended to have and decide what – if any – changes they think are worth making to them in response.
主要受眾
編輯團隊的工作重點是滿足以下人們的需求:
- 經驗: 正在學習為維基百科做出貢獻的基礎知識
- 在這個專案的背景下,仍在「學習基礎知識」的人是指對一個或多個維基百科中累積編輯少於100次的人。這包括第一次編輯維基百科的人。
- 所在地: 生活在撒哈拉以南非洲地區
- 專案: 為英語和法語維基百科做出貢獻
- 動機: 尋求填補他們在維基百科中注意到的空白
以上所列的四個重點標準是以下的產物:
- 來自非洲或亞洲的新手是其他地方的兩倍。[12]
- 該運動在努力留住歐洲和北美洲以外的編輯者。[12]
- 來自撒哈拉以南非洲地區的人在運動中的代表性不足:儘管來自撒哈拉以南非洲地區的人佔全球人口的15%和全球網路人口的7%,但僅佔活躍獨立編輯者的1%。[13]
- 撒哈拉以南非洲地區有80%的註冊編輯者為英語或法語維基百科做出貢獻。[14]
設計
參考檢測
To start, the Editing Team is pursuing an approach with Edit Check that minimizes the likelihood of false positives and is implemented in ways[15] that empower volunteers, on a per-project basis, to evolve the heuristic[16] to become more robust over time.
This strategy amounts to the initial reference Edit Check becoming activated if/when all of the following conditions are met:
- A minimum of one new paragraph of text is added to the article someone is editing
- The "new paragraph(s) of text" someone has added does NOT include a reference
- The changes described in "1." and "2." are happening on a page within the main namespace (NS:0)
The conditions above are implemented and maintained in code here: editcheck/init.js.
The Editing Team arrived at the decision to start with a relatively limited and straightforward set of rules in order to:
- Increase the likelihood that newcomers and Junior Contributors find the guidance Edit Check is presenting them with, and the editing experience more broadly, to be intuitive and straightforward so that they feel encourage to return to edit again
- Decrease the likelihood that Edit Check is creating more work for experienced volunteers by prompting newcomers and Junior Contributors to add sources when they are not needed
You can learn more about the assumptions that informed the thinking above in phab:T329988#8654867.
其他應用
可配置性
The Editing Team thinks it is crucial that moderators be empowered to configure when, and for whom, Edit Check becomes activated. This way, they can be confident the software is promoting behavior they deem to be productive and modify the software when it is not.
In line with the above, and drawing inspiration from how the Edit filter and Growth Team Community configuration systems afford volunteers the ability to audit and configure how they function on-wiki, Edit Check will enable volunteers, on a per project basis to:
- Audit and edit the logic that determines when the reference Edit Check becomes activated and
- Review the edits people who are shown Edit Check are making
落實上述內容的工作正在phab:T327959中進行。
使用者體驗
行動版
The first version of Edit Check will introduce a new step within the mobile visual editor's publishing workflow that people will see if/when they add new content without a reference.
桌面版
桌面版的使用者體驗仍在設計當中。 參見T329579。
Experiments
Reference Check A/B Test
To learn whether the Reference Edit Check is effective at causing newcomers to make edits they intended and experienced volunteers value, we conducted an A/B test with 15 Wikipedias.
Below you can read more about what this experiment demonstrated, what the Editing Team is planning in response, and more details about the test's design.
Conclusion and next step(s)
Reference Check caused an increase in the quality of edits newcomers publish and did not cause any significant disruption.
This combination is leading the Editing Team to be confident that offering Reference Check as a default-on feature would have a net positive impact on all wikis and the people who contribute to them.
You can read the full A/B test report here.
Findings
New content edits *with* a reference
People shown the Reference Check are 2.2 times more likely to publish a new content edit that includes a reference and is constructive (not reverted within 48 hours).
- Increases were observed across all reviewed user types, wikis, and platforms.
- The highest observed increase was on mobile where contributors are 4.2 times more likely to publish a constructive new content edit with a reference when Reference Check was shown to eligible edits.
Revert rate
- New content edit revert rate decreased by 8.6% if Reference Check was available.
- New content edits by contributors from Sub-Saharan Africa are 53% less likely to be reverted when Reference Check is shown to eligible edits.
- While some non-constructive new content edits with a reference were introduced by this feature (5 percentage point increase), there was a higher proportion of constructive new content edits with a reference added (23.4 percentage point increase). As a result, we observed an overall increase in the quality of new content edits.
Constructive Retention Rate
- Contributors that are shown Reference Check and successfully save a non-reverted edit are 16 percent more likely to return to make a non-reverted edit in their second month (31-60 days after).
- This increase was primarily observed for desktop edits. There was a non-statistically significant difference observed on mobile.
Guardrails
Edit Completion Rate
- We observed no drastic decreases in edit completion rate from intent to save (where Reference Check is shown) to save success overall or by wiki.
- Overall, there was a 10% decrease in edit completion rate for edits where Reference Check was shown.
- There was a higher observed decrease in edit completion rate on mobile compared to desktop. On mobile, edit completion rate decreased by -24.3% while on desktop it decreased by -3.1%.
Block Rate
- There were decreases or no changes in the rate of users blocked after after being shown Reference Check and publishing an edit compared to users in the control group.
False Negative Rate
- There was a low false negative rate. Only 1.8% of all published new content edits in the test group did not include a new reference and were not shown Reference Check.
False Positive Rate
- 6.6% of contributors dismissed adding a citation because they indicated the new content being added does not need a reference. This was the least selected decline option overall.
Test design
11 Wikipedias participated in the test. At each wiki, 50% of users were randomly assigned to a test
group and 50% were assigned to a control
group.
Users in the test
group were shown the Reference Check notice prompting them to decide whether the new content they were adding need a reference (if they had not already added one themselves).
User in the control
group were shown the default editing experience, even if they did not accompany the new content they were adding with a reference.
Timing
This analysis was completed on 16 April 2024 and analyzed engagement data at the 11 participating wikis from 18 February 2024 through 4 April 2024.
Evaluating impact
The viability of the features introduced as part of the Edit Check project depends on the impacts it causes and averts.[17]
This section describes the:
- Impacts the features introduced as part of the Edit Check are intended to cause and avert
- Data we will use to help[18] determine the extent to which a feature has/has not caused a particular impact
- Evaluation methods we will use to gather the data necessary to determine the impact of a given feature
ID | Outcome | Data | Evaluation Method(s) |
---|---|---|---|
1. | Increase the quality of edits newcomers and Junior Contributors editing from within Sub-Saharan Africa publish in the main namespace | Decrease in the proportion of published edits that add new content and are reverted within 48 hours or have a high revision risk score
Comments/reports from experienced volunteers about the quality of edits Edit Check is activated within[20] |
A/B test[21], qualitative feedback (e.g. talk page discussions, false positive reporting) |
2. | Increase the likelihood that newcomers and Junior Contributors editing from within Sub-Saharan Africa will accompany the new content they are adding with a reference | Increase in the percentage of published edits that add new content and include a reference
Increase in the percent of newcomers or Junior Contributors from SSA that publish at least one new content edit that includes a reference Increase in the likelihood that someone includes a reference the next time they contribute new content. |
A/B test[21] |
3. | Newcomers and Junior Contributors editing from within Sub-Saharan Africa will report feeling safe and confident making changes to Wikipedia | Newcomers and Junior Contributors find the feedback and calls to action Edit Check presents them with to be:
|
Qualitative feedback via channels like:Community Calls, talk pages, event organizers, etc. |
4. | Experienced volunteers will independently audit and iterate upon Edit Check's default configurations to ensure Edit Check is causing newcomers and Junior Contributors to make productive edits. | ||
5. | Newcomers and Junior Contributors will be more aware of the need to add a reference when contributing new content because the visual editor will prompt them to do so in cases where they have not done so themselves. | Increase in the percent of newcomers or Junior Contributors from SSA that publish at least one new content edit that includes a reference. | A/B test[21] |
ID | Outcome | Data | Evaluation Method(s) |
---|---|---|---|
1. | Edit quality decreases | Increase in the proportion of published edits that add new content and are reverted within 48 hours or have a high revision risk score
Comments/reports from experienced volunteers about the quality of edits Edit Check is activated within[20] |
A/B test[21], qualitative review and feedback |
2. | Edits become more difficult to patrol because unreliable citations are difficult to detect | Significant increase in the percentage of new content edits new and developing volunteers make that include a reference
Comments/reports from experienced volunteers about the quality of edits Edit Check is activated within[20] |
A/B test[21], qualitative review and feedback |
3. | Edit completion rate drastically decreases | Proportion of edits that are started (event.action = init ) that are successfully published (event.action = saveSuccess ).
|
A/B test[21] |
4. | Edit abandonment rate drastically increases | Proportion of contributors that are presented Edit Check feedback and abandon their edits (indicated by event.action = abort and event.abort_type = abandon )
|
A/B test[21] |
5. | Blocks increase | Proportion of contributors blocked after publishing an edit where Edit Check was shown is significantly higher than edits in which Edit Check was not shown | A/B test[21] |
6. | High false positive or false negative rates | Proportion of new content edits published without a reference and without being shown Edit Check (indicator of false negative)
Proportion of contributors that dismiss adding a citation and select "I didn't add new information" or other indicator that the change they are making doesn't require a citation |
A/B test[21], qualitative feedback received from volunteers about the accuracy and usefulness of Edit Check's current configuration [23] |
7. | Edit Check is too resource intensive to scale | Efficiencies do not emerge over time making each new Edit Check as "expensive" to implement as the first one | Qualitative assessment by the Edting team |
Deployment process
Please see Deployment status#Deployment process .
背景
Volunteers throughout the movement have a long history of working to:
- Proactively educate and guide newcomers to make changes they feel proud of and changes that improve Wikipedia
- Prevent people from publishing destructive changes, and
- React to and moderate changes to Wikipedia articles.
The Editing Team and this project have been inspired by these efforts, some of which are listed below. If there is a project or resource you think we should be aware of, please add it here!
倡議 | 說明 | 主導人 |
---|---|---|
CopyPatrol | Tool that allows you to see recent Wikipedia edits that are flagged as possible copyright violations | Community Tech Team |
paper: Automatically Neutralizing Subjective Bias in Text | Method for automatically bringing inappropriately subjective text into a neutral point of view ("neutralizing" biased text). | Reid Pryzant, Richard Diehl Martinez, Nathan Dass, Sadao Kurohashi, Dan Jurafsky, Diyi Yang |
Wikipedia:Citation watchlist | User script that adds visual indicators to watchlist and recent changes entries when unreliable sources are added to articles. | Harej, Ocaasi |
Internet Archive Reference Explorer | Explore references included in Wikipedia articles via a range of criteria | |
WikiScore | A tool created to validate edits and count scores of participants in wikicontests. | |
Earwig's Copyvio Detector | This tool attempts to detect copyright violations in articles. | The Earwig |
CiteUnseen | A user script that adds categorical icons to Wikipedia citations, providing readers and editors a quick initial evaluation of citations at a glance. | SuperHamster |
Credibility bot | Monitors and collects data on source usage within Wikipedia articles | Harej |
Salebot (fr.wiki) | A counter-vandalism bot that uses regex to identify issues. | |
Edit intros (en.wiki) | A message is shown automatically when editing a page categorized as either Category:Living people or Category:Possibly living people. | |
Make edit notices more visible in Visual Editor | How might we make it so people who are in the midst of an edit are likely to see and "internalize" the information that is currently presented within Edit Notices? | User:Stjn |
Internet Archive Reference Explorer | Automatically detect source quality | Ocaasi |
Wish: Reference requirement for new article creation | Require new article to include references | User:Mega809 |
編輯提示 | Enables individual volunteers and projects to display a custom notice above the edit form, depending on the page, namespace, or other circumstances. | |
頁面提示 | ||
維護模板 | ||
Extension:AbuseFilter | Enables privileged users to set specific actions to be taken when actions by users, such as edits, match certain criteria. | |
Extension:Disambiguator | Displays a notification in the 2006/2010 wikitext editor whenever one adds a link to a disambiguation page. | Community Tech |
ORES | Halfak (WMF) | |
建議編輯 | ||
CiteHighlighter | Highlights 1800 sources green, yellow, or red depending on their reliability. | Novem Linguae |
Checkwiki | Helps clean up syntax and other errors in the source code of Wikipedia | Stefan Kühn, Bgwhite |
編輯差異標記 | Showcases all the different tags that can be automatically determined (generally via basic heuristics) for a given Wikipedia edit diff. | Isaac (WMF) |
CivilityCheck | A project to evaluate the civility in the comments of Wikipedia discussions in order to address the problem of abuse that leads to declining editorship within the Wiki community. | Deus Nsenga, Baelul Haile, David Ihim, and Elan Houticolo-Retzler |
BOTutor | A bot that sends a message to people who attempt to publish an edit that triggers an existing set of rules | ValeJappo |
Gadget-autocomplete.js | ערן | |
Text reactions | A proposal that would make it possible for the editing interface to react to what the people enter in the editing area | SD0001 |
Editwizard | A step-by-step process for guiding newcomers to source the content they are attempting to add to Wikipedia articles | Ankit18gupta, Enterprisey, Firefly, and SD0001 |
Headbomb/unreliable | "The script breaks down links to various sources in different 'severities' of unreliability. In general, the script is kept in sync with WP:RSPSOURCES, {{Predatory open access source list}}, WP:NPPSG, WP:SPSLIST (not fully implemented yet) and WP:CITEWATCH, with some minor differences." | Headbomb, SD0001 |
The Wikipedia Adventure | Game based on the tech of Extension:GuidedTour that teaches basic wikitext markup and the rules about reliable sources and neutral point of view. Research into its effectiveness is described at meta:Research:Impact of The Wikipedia Adventure on new editor retention. | Ocaasi |
w:Help:Introduction | The primary tutorial for new editors at English Wikipedia, covering both policies and technical how-to for VisualEditor and wiki markup. Most recently overhauled in late 2020 and more actively maintained than TWA. | Sdkb, Evolution and evolvability, and others |
User:Phlsph7/ HighlightUnreferencedPassages |
A user script to highlight passages that lack references with a red background. Its main purpose is to help users quickly identify unreferenced passages, paragraphs, and sections in mainspace articles and drafts | Phlsph7 |
Wish: Add notice to the visual editor that unsourced edits may be reverted | A notice in the "Publish changes" dialogue of the visual editor that states that unsourced edits will be reverted | User:Lectrician1 |
Wish: Warn when adding a url reference that matches the SpamBlacklist | Warn when the url added as reference is registered in the SpamBlacklist, and thus prevent the warning from appearing when saving the page. | User:DSan |
Edit FIler #686 | Edit Filter that is triggered when a new user possibly adding unreferenced material to BLP | User:Rich Farmbrough |
WikiLearn | Platform for training | |
DannyS712/copyvio-check.js | Automatically checks the copyvio percentage of new pages in the background and displays this info with a link to the report in the 'info' panel of the Page curation toolbar. | DannyS712 |
XLinkBot | A bot that warns people who have added an external link that is inappropriate in some way. | Versageek, Beetstra |
參見
參考資料
- ↑ Reference Check will be made available to remaining wikis via T366381 and T367343.
- ↑ Editing team/Community Conversations#January 2023
- ↑ T327330
- ↑ Talk:Edit check#So glad to see!
- ↑ en:When should newcomers be prompted to add sources?
- ↑ T324364
- ↑ T323145
- ↑ T326856
- ↑ Superset: Wikipedia edits by interface and experience level
- ↑ Growth Team: IP editing Research Report
- ↑ The Tyranny of Structurelessness
- ↑ 12.0 12.1 2021年社群見解報告
- ↑ 區域季度學習會議(2022年6月,Google簡報)
- ↑ Superset
- ↑ T327959
- ↑ T324730
- ↑ Where "viability" in this context refers to a feature being fit for being scaled to all projects as determined by the extent to which it has been proven to have a net positive impact on wikis and the volunteers who build and maintain them.
- ↑ Emphasis on "help" seeing as how all decisions will depend on a variety of data, all of which need to be weighted and considered to make informed decisions.
- ↑ T325838: Finish Edit Check measurement plan proposal
- ↑ 20.0 20.1 20.2 At every project where Edit Check is available, volunteers will be able to use the
editcheck-reference-activated
tag to review edits where the reference check is shown to people in the process of publishing an edit. Learn more about Edit Check tags. - ↑ 21.0 21.1 21.2 21.3 21.4 21.5 21.6 21.7 21.8 [Analysis] Run an A/B test to evaluate Edit Check (references) impact
- ↑ T325851: Conduct pre-mortem for Edit Check project
- ↑ In addition to existing feedback channels (Phabricator, talk pages, etc.) there will be a minimum of two additional ways for people to share feedback about Edit Check: A) reporting edits that you think Edit Check should not have been shown within and B) declining to add a reference mid-edit by indicating you think Edit Check was shown when it shouldn't have been.