Change Details

Organizers, their sponsors and partners want to know how much work was done during an event. "Bytes changed" has been a metric for this, but it is imperfect in many ways. "Words added" would be a way to judge how much writing was accomplished, but this metric is problematic. The task here is to figure out how to include a figure for Words Added in (to begin with) the Event Summary (T205561 and T206692 ) and Pages Created (T206058 and T205502) reports.. =Definitions - **Pages Created and Improved reports**: These reports list is a list of articles created and improved, so the metric will show the net change in words to the given article. Use a minus sign to indicate negative numbers, in the event of negative change (possible for Pages Improved, though not for Pages Created). - **Event Summary report:** here, the metric will count the net change in words added during the event—essentially a sum of the figures above. =Caveats and limitations **Where possible: **it's understood that determining what is and isn't a "word" is harder in some scripts than others. The first release of this will be for those scripts where we have relative confidence. For other scripts, we will fill these fields with an "n/a," to signify "not available." **Standard definitions:** I imagine there are various techniques for defining and deriving what is a "word." Any standard definition is acceptable, so long as it doesn't include wikitext codes in the count.

Organizers, their sponsors and partners want to know how much work was done during an event. "Bytes changed" has been a metric for this, but it is imperfect in many ways. "Words added" would be a way to judge how much writing was accomplished, but this metric is problematic. The task here is to figure out how to include a figure for Words Added in (to begin with) the Event Summary (T205561 and T206692 ) and Pages Created (T206058 and T205502) reports.. =Definitions - **Pages Created and Improved reports**: These reports list is a list of articles created and improved, so the metric will show the net change in words to the given article. Use a minus sign to indicate negative numbers, in the event of negative change (possible for Pages Improved, though not for Pages Created). - **Event Summary report:** here, the metric will count the net change in words added during the event—essentially a sum of the figures above. =Caveats and limitations - **Where possible: **it's understood that determining what is and isn't a "word" is harder in some scripts than others. The first release of this will be for those scripts where we have relative confidence. - **For scripts that are not amenable**, we will fill these fields with an "n/a," to signify "not available." - **Standard definitions:** I imagine there are various techniques for defining and deriving what is a "word." Any standard definition is acceptable, so long as it doesn't include wikitext codes in the count.

Organizers, their sponsors and partners want to know how much work was done during an event. "Bytes changed" has been a metric for this, but it is imperfect in many ways. "Words added" would be a way to judge how much writing was accomplished, but this metric is problematic. The task here is to figure out how to include a figure for Words Added in (to begin with) the Event Summary (T205561 and T206692 ) and Pages Created (T206058 and T205502) reports.. =Definitions - **Pages Created and Improved reports**: These reports list is a list of articles created and improved, so the metric will show the net change in words to the given article. Use a minus sign to indicate negative numbers, in the event of negative change (possible for Pages Improved, though not for Pages Created). - **Event Summary report:** here, the metric will count the net change in words added during the event—essentially a sum of the figures above. =Caveats and limitations - **Where possible: **it's understood that determining what is and isn't a "word" is harder in some scripts than others. The first release of this will be for those scripts where we have relative confidence. - **For scripts that are not amenable**, we will fill these fields with an "n/a," to signify "not available." **Where possible: **it's understood that determining what is and isn't a "word" is harder in some scripts than others. The first release of this will be for those scripts where we have relative confidence. For other scripts, we will fill these fields with an "n/a," to signify "not available." - **Standard definitions:** I imagine there are various techniques for defining and deriving what is a "word." Any standard definition is acceptable, so long as it doesn't include wikitext codes in the count.