Change Details

The Pages Created downloadable reports, in Wikitext and csv formats, give details on all articles created during an event (and potentially other pages, once we implement a namespace filter). Their purpose is to provide event organizers with data to provide to partners, grantors, bosses and event participants in order to demonstrate an event's scope and impact. This task defines the total set of data we want for those reports. The subset of data in the reports and all the elements of the reports are defined in two separate tasks: - **CSV:** The first, partial version of the csv report is defined in T206058. - **Wikitext:** The first, partial version of the Wikitext report is defined in T205502. =Data / column names - Title - URL - ~~*Description~~ - Creator - Wiki - ~~Namespace~~ [Counting Main space only at this time.] - Still exists? !![handled separately in T206695]!! - Edits during event - ~~*Edits subsequently~~ [Complicated, not for MVP] - Bytes changed during event - ~~*Bytes changed subsequently~~ [Complicated, not for MVP] - Words added during event !![handled separately in T206690]!! - ~~*Words added subsequently~~ [Complicated, not for MVP] - Article class (where available) - Pageviews, cumulative - Avg. pageviews per day - Incoming links !!* These features deemed complicated and are not for MVP!! =Metric definitions - **Title: ** include pages as defined in Default Filter Settings, above. Until we build filter controls, this will be Main namespace only. - **URL** of the page. - ~~**Description**~~ Pull from the first sentence of the article, truncated to [100?] characters (not including wikitext). !![Complicated, not for MVP]!! - **Creator** The username of the person who created the article. - **Wiki** where the article exists. Limited to the short list of wikis defined on the Event Setup screen for the event. - ~~**Namespace**~~ !![leave out of reports until we add Namespace filters]!! - **Still exists?** answers = yes/deleted. Tells whether the page still exists at the time the data was updated. !![full details in separate ticket, T206695]!! - **Edits during event** The edit count to the article during the event period. - ~~**Edits subsequently** The edit count to the article from the end of the event period until the last data update. If the event is ongoing, answer="ongoing"~~ - **Bytes changed during event** The net bytes changed to the page during the event period. Show all numbers with a + sign to indicate direction of change. (For //this// report, all numbers will all be positive, but in other reports this number may be negative.) - ~~**Bytes changed subsequently** The net bytes changed to the page from the end of the event period until the last data update. If the event is ongoing, answer="ongoing". Show all numbers with a + or - sign to indicate direction of change. ~~ ![Complicated, not for MVP]!! - **Words added during event:** the net change in words to the given article. !![full details in separate ticket, T206695]!! - ~~**Words changed subsequently** The net change in words to the page from the end of the event period until the last data update. If the event is ongoing, answer="ongoing". Show all numbers with a + or - sign to indicate direction of change. As above, omit for scripts/languages where not feasible and present as decided.~~ !![Complicated, not for MVP]!! - **Article class (where available)** These rankings are [[ https://github.com/x-tools/xtools/blob/master/app/config/assessments.yml | available on five wikis ]]. Each has its own ranking system and codes. Use the codes appropriate to the wiki. - For wikis where article class is unavailable, we can either 1) omit the column, which is preferred, or 2) answer=unavailable !![@Mooeypoo, should I make a separate ticket to investigate this?]!! - **Pageviews, cumulative** Pageviews to the article from creation until last data update. - **Avg. pageviews per day** In order to provide an accurate picture of how many views the page gets //now//, instead of over its entire history, Avg. Pageviews will be an average over the __preceding 30 days__ only. - **Incoming links** A count as of last data update of links to the article. =Fixed vs. Continuing Data Figures like Pageviews naturally continue to develop after the event is over and must be calculated anew every time the data is updated. Other figures can be considered fixed once the event period is over; these could be stored and need never be calculated again. Here is a breakdown of these two types **Remains fixed** - Creator - Wiki - Namespace - Edits during event - Bytes changed during event - Words added during event **Continues to develop** - Title/URL [These may change, though continuity will be maintained by the article ID.] - Description - Still exists? - Edits subsequently - Bytes changed subsequently - Words added subsequently - Article class (where available) - Pageviews, cumulative - Avg. pageviews per day - Incoming links =Default filter settings and logic In the first incarnations of these reports, users will not be able to change the default reporting settings, since the filtering tools we're planning won't be built. The defaults, therefore, are as follows: - **Time period: EVENT** —the articles must have been created during the time period of the event. - **Participants: ON**— if the user has defined a list of participants, then metrics will be restricted to these. - **Categories: ON**—if the user has set categories for the event, the articles must be in those categories. - **Wikis:** those defined for the event in Event Setup **LOGIC** - **Logic = AND**: The relationship among the filters above will be as follows: //Time period AND Participants AND Categories.// In other words, if the organizer has supplied all three types of filtering info, then all three will be applied and results will be presented only for articles at the intersection of all three—or of whichever of the three the organizer has supplied. (As we add download controls and users gain the ability to turn filters off, we'll have to face the question: what is the minimum before performance degrades too much?)

The Pages Created downloadable reports, in Wikitext and csv formats, give details on all articles created during an event (and potentially other pages, once we implement a namespace filter). Their purpose is to provide event organizers with data to provide to partners, grantors, bosses and event participants in order to demonstrate an event's scope and impact. This task defines the total set of data we want for those reports. The subset of data in the reports and all the elements of the reports are defined in two separate tasks: - **CSV:** The first, partial version of the csv report is defined in T206058. - **Wikitext:** The first, partial version of the Wikitext report is defined in T205502. =Data / column names - Title - URL - ~~*Description~~ - Creator - Wiki - ~~Namespace~~ [Counting Main space only at this time.] - Still exists? !![handled separately in T206695]!! - Edits during event - ~~*Edits subsequently~~ [Complicated, not for MVP] - Bytes changed during event - ~~*Bytes changed subsequently~~ [Complicated, not for MVP] - Words added during event !![handled separately in T206690]!! - ~~*Words added subsequently~~ [Complicated, not for MVP] - Article class (where available) !![handled separately in TK]!! - Pageviews, cumulative - Avg. pageviews per day - Incoming links !!* These features deemed complicated and are not for MVP!! =Metric definitions - **Title: ** include pages as defined in Default Filter Settings, above. Main namespace only. - **URL** of the page. - ~~**Description**~~ Pull from the first sentence of the article, truncated to [100?] characters (not including wikitext). !![Complicated, not for MVP]!! - **Creator** The username of the person who created the article. - **Wiki** where the article exists. Limited to the short list of wikis defined on the Event Setup screen for the event. - ~~**Namespace**~~ !![leave out of reports until we add Namespace filters]!! - **Still exists?** answers = yes/deleted. Tells whether the page still exists at the time the data was updated. !![full details in separate ticket, T206695]!! - **Edits during event** The edit count to the article during the event period. - ~~**Edits subsequently** The edit count to the article from the end of the event period until the last data update. If the event is ongoing, answer="ongoing"~~ - **Bytes changed during event** The net bytes changed to the page during the event period. Show all numbers with a + sign to indicate direction of change. (For //this// report, all numbers will all be positive, but in other reports this number may be negative.) - ~~**Bytes changed subsequently** The net bytes changed to the page from the end of the event period until the last data update. If the event is ongoing, answer="ongoing". Show all numbers with a + or - sign to indicate direction of change. ~~ ![Complicated, not for MVP]!! - **Words added during event:** the net change in words to the given article. !![full details in separate ticket, T206695]!! - ~~**Words changed subsequently** The net change in words to the page from the end of the event period until the last data update. If the event is ongoing, answer="ongoing". Show all numbers with a + or - sign to indicate direction of change. As above, omit for scripts/languages where not feasible and present as decided.~~ !![Complicated, not for MVP]!! - **Article class (where available)** These rankings are [[ https://github.com/x-tools/xtools/blob/master/app/config/assessments.yml | available on five wikis ]]. Each has its own ranking system and codes. Use the codes appropriate to the wiki. !![handled separately in TK]!! - For wikis where article class is unavailable, please omit the column, - For individual articles that don't have a class rating but which are in a wiki that does have article classes, answer=unrated - **Pageviews, cumulative** Pageviews to the article from creation until last data update. - **Avg. pageviews per day** In order to provide an accurate picture of how many views the page gets //now//, instead of over its entire history, Avg. Pageviews will be an average over the __preceding 30 days__ only. - **Incoming links** A count as of last data update of links to the article. =Fixed vs. Continuing Data Figures like Pageviews naturally continue to develop after the event is over and must be calculated anew every time the data is updated. Other figures can be considered fixed once the event period is over; these could be stored and need never be calculated again. Here is a breakdown of these two types **Remains fixed** - Creator - Wiki - Edits during event - Bytes changed during event - ~~Words added during event~~ **Continues to develop** - Title/URL [These may change, though continuity will be maintained by the article ID.] - ~~Description~~ - Still exists? - ~~Edits subsequently~~ - ~~Bytes changed subsequently~~ - ~~Words added subsequently~~ - Article class (where available) - Pageviews, cumulative - Avg. pageviews per day - Incoming links =Default filter settings and logic - **Time period: EVENT** —the articles must have been created during the time period of the event. - **Participants: ON**— if the user has defined a list of participants, then metrics will be restricted to these. - **Categories: ON**—if the user has set categories for the event, the articles must be in those categories. - **Wikis:** those defined for the event in Event Setup **LOGIC** - **Logic = AND**: The relationship among the filters above will be as follows: //Time period AND Participants AND Categories.// In other words, if the organizer has supplied all three types of filtering info, then all three will be applied and results will be presented only for articles at the intersection of all three—or of whichever of the three the organizer has supplied. (As we add download controls and users gain the ability to turn filters off, we'll have to face the question: what is the minimum before performance degrades too much?)

The Pages Created downloadable reports, in Wikitext and csv formats, give details on all articles created during an event (and potentially other pages, once we implement a namespace filter). Their purpose is to provide event organizers with data to provide to partners, grantors, bosses and event participants in order to demonstrate an event's scope and impact. This task defines the total set of data we want for those reports. The subset of data in the reports and all the elements of the reports are defined in two separate tasks: - **CSV:** The first, partial version of the csv report is defined in T206058. - **Wikitext:** The first, partial version of the Wikitext report is defined in T205502. =Data / column names - Title - URL - ~~*Description~~ - Creator - Wiki - ~~Namespace~~ [Counting Main space only at this time.] - Still exists? !![handled separately in T206695]!! - Edits during event - ~~*Edits subsequently~~ [Complicated, not for MVP] - Bytes changed during event - ~~*Bytes changed subsequently~~ [Complicated, not for MVP] - Words added during event !![handled separately in T206690]!! - ~~*Words added subsequently~~ [Complicated, not for MVP] - Article class (where available) !![handled separately in TK]!! - Pageviews, cumulative - Avg. pageviews per day - Incoming links !!* These features deemed complicated and are not for MVP!! =Metric definitions - **Title: ** include pages as defined in Default Filter Settings, above. Until we build filter controls, this will be Main namespace only. - **URL** of the page. - ~~**Description**~~ Pull from the first sentence of the article, truncated to [100?] characters (not including wikitext). !![Complicated, not for MVP]!! - **Creator** The username of the person who created the article. - **Wiki** where the article exists. Limited to the short list of wikis defined on the Event Setup screen for the event. - ~~**Namespace**~~ !![leave out of reports until we add Namespace filters]!! - **Still exists?** answers = yes/deleted. Tells whether the page still exists at the time the data was updated. !![full details in separate ticket, T206695]!! - **Edits during event** The edit count to the article during the event period. - ~~**Edits subsequently** The edit count to the article from the end of the event period until the last data update. If the event is ongoing, answer="ongoing"~~ - **Bytes changed during event** The net bytes changed to the page during the event period. Show all numbers with a + sign to indicate direction of change. (For //this// report, all numbers will all be positive, but in other reports this number may be negative.) - ~~**Bytes changed subsequently** The net bytes changed to the page from the end of the event period until the last data update. If the event is ongoing, answer="ongoing". Show all numbers with a + or - sign to indicate direction of change. ~~ ![Complicated, not for MVP]!! - **Words added during event:** the net change in words to the given article. !![full details in separate ticket, T206695]!! - ~~**Words changed subsequently** The net change in words to the page from the end of the event period until the last data update. If the event is ongoing, answer="ongoing". Show all numbers with a + or - sign to indicate direction of change. As above, omit for scripts/languages where not feasible and present as decided.~~ !![Complicated, not for MVP]!! - **Article class (where available)** These rankings are [[ https://github.com/x-tools/xtools/blob/master/app/config/assessments.yml | available on five wikis ]]. Each has its own ranking system and codes. Use the codes appropriate to the wiki. !![handled separately in TK]!! - For wikis where article class is unavailable, please omit the column, - For wikis where article class is unavailable, we can either 1) omit the column, which is preferred, or 2) answer=unavailable !![@Mooeypoo,individual articles that don't have a class rating but which are in a wiki that does have article classes, answer=unrated should I make a separate ticket to investigate this?]!! - **Pageviews, cumulative** Pageviews to the article from creation until last data update. - **Avg. pageviews per day** In order to provide an accurate picture of how many views the page gets //now//, instead of over its entire history, Avg. Pageviews will be an average over the __preceding 30 days__ only. - **Incoming links** A count as of last data update of links to the article. =Fixed vs. Continuing Data Figures like Pageviews naturally continue to develop after the event is over and must be calculated anew every time the data is updated. Other figures can be considered fixed once the event period is over; these could be stored and need never be calculated again. Here is a breakdown of these two types **Remains fixed** - Creator - Wiki - Namespace - Edits during event - Bytes changed during event - - ~~Words added during event~~ **Continues to develop** - Title/URL [These may change, though continuity will be maintained by the article ID.] - - ~~Description~~ - Still exists? - - ~~Edits subsequently~~ - - ~~Bytes changed subsequently~~ - - ~~Words added subsequently~~ - Article class (where available) - Pageviews, cumulative - Avg. pageviews per day - Incoming links =Default filter settings and logic In the first incarnations of these reports, users will not be able to change the default reporting settings, since the filtering tools we're planning won't be built. The defaults, therefore, are as follows: - **Time period: EVENT** —the articles must have been created during the time period of the event. - **Participants: ON**— if the user has defined a list of participants, then metrics will be restricted to these. - **Categories: ON**—if the user has set categories for the event, the articles must be in those categories. - **Wikis:** those defined for the event in Event Setup **LOGIC** - **Logic = AND**: The relationship among the filters above will be as follows: //Time period AND Participants AND Categories.// In other words, if the organizer has supplied all three types of filtering info, then all three will be applied and results will be presented only for articles at the intersection of all three—or of whichever of the three the organizer has supplied. (As we add download controls and users gain the ability to turn filters off, we'll have to face the question: what is the minimum before performance degrades too much?)