The Pages Created downloadable report gives details on all articles created during an event. It's purpose is to provide event organizers with data they can sort or combine with other reports to meet their various reporting needs.
The report will be dowonloadable as a CSV file. !!Do we need to let users pick a delimiter? What does Grant Metrics do now?!!
=Report content
The report will include data as well as some descriptive information at the bottom. Find descriptions and definitions of each of these columns below.
===Data / column names
- The left-most column of the report will be a list of page titles.
- The default order will be alphabetical !![how hard is it to ignore articles and such?]!!
The remaining column headings will be, in order
- Title
- URL
- Description
- Creator
- Wiki
- Namespace
- Still exists?
- Edits during event
- Edits subsequently
- Bytes changed during event
- Bytes changed subsequently
- Words added during event
- Words added subsequently
- Article class (where available)
- Pageviews, cumulative
- Avg. pageviews per day
- Incoming links
===Descriptive info and settings
At the bottom of the report, it would be nice if we could list the following in the left column below a header that says: **Report details**
- Event name
- Start time/date
- End time/date
- Location:
- Date of last data update
- Filter settings for download:
- Article Worklist: Applied/Not applied/None supplied
- Categories: Applied/Not applied/None supplied + if applied, list categories [only those actually entered by the user, not subcategories included automatically]
- Participants list: Applied/Not applied/None supplied
- Wikis: list
- Report filename: Can we specify a filename for the report? If so, make it: Summary Data: //EventName//
=Default filter settings
In the its first incarnation, 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.
**LOGIC**
- **Logic, rev 1**: When this report is first created, there will be no filtering controls on the download page. So 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 reflect the intersection of all three (or of whichever of the three the organizer has supplied).
- **Logic, rev 2**: As we add download controls and more filter types (Worklist, Namespace, Wiki), users will have more options to tailor their queries. The controls will enable organizers to turn different filters on or off (e.g., "ignore the participants list in this report").
- However, my assumption is that the logic for all filters will still be AND. I.e., we won't provide the ability for organizers to look for results that are either by the Participants OR in the specified Categories. @Prtksxna does that sound right?
=Definitions of metrics
- **Title: ** include pages as defined in Default Filter Settings, above. Until we build filter controls, this will be Main namespace only. Show title as displayed at page top (e.g., when we do add more namespaces, it will be Talk:Pagetitle).
- **URL** of the page. I don't know whether we have the ability to set default column width for downloads, but if we do there is no need to show the whole URL. !![Is this possible?]!!
- **Description** The short Wikidata description if available and easy to access. Failing that, use the first sentence. If it's possible, please present only normal text (no wikitext, image templates, etc.). !![Is this possible?]!!
- **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** Until we add filtering controls, this will be Main only. !![Should we include it as a marker for later or leave it out?!!
- **Still exists?** answers = yes/deleted. Tells whether the page still exists at the time the data was updated. (E.g., if something was deleted but reinstated, then the answer is "yes".)
- **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.
- **Words changed during event** The net change in words to the page during the event period. Show all numbers with a + sign to indicate direction of change. In our discussions, the point was raised that this calculation may be feasible for some scripts/languages more than others. We will implement for the scripts where we can and leave others for later.
- For scripts/languages where this calculation is not feasible, we can either 1) omit the column, which is preferred, or 2) answer=unavailable !![@Mooeypoo, should I make a separate ticket to investigate this?]!!
- **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.
- **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** Cumulative total pageviews divided by days since creation, presumably. Figure allows comparison of articles from different events and of different ages.
- **Incoming links** A count as of last data update of links to the article.