https://test.wikipedia.org/wiki/Page_count_by_namespace (Against the testwiki db)

Code at: https://github.com/Niharika29/database-reports

Looks good. Here are my suggestions:

• Remove the 'No.' column as I don't see any useful purpose for it (although I know it is in the original version of the report)
• Add a description to the top of the report similar to the one at https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Page_count_by_namespace

In T110575#1582249, @kaldari wrote:

• Remove the 'No.' column as I don't see any useful purpose for it (although I know it is in the original version of the report)
• Add a description to the top of the report similar to the one at https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Page_count_by_namespace

{{done}} https://test.wikipedia.org/wiki/Page_count_by_namespace

Can we keep all the database reports code in the same repository (https://github.com/mzmcbride/database-reports)? I or @MZMcBride can give you access to the git repo and tool labs tool so you can set up and fix reports.

We already have a standardized class system for reports, similar to the QueryPage abstraction in MediaWiki, see the reports in https://github.com/mzmcbride/database-reports/tree/master/reports, it would be nice if future reports also followed that format.

In T110575#1586537, @Legoktm wrote:

Can we keep all the database reports code in the same repository (https://github.com/mzmcbride/database-reports)? I or @MZMcBride can give you access to the git repo and tool labs tool so you can set up and fix reports.

We already have a standardized class system for reports, similar to the QueryPage abstraction in MediaWiki, see the reports in https://github.com/mzmcbride/database-reports/tree/master/reports, it would be nice if future reports also followed that format.

That makes sense, and that was my original intention as well, but I didn't find any helpful documentation to ease my job. Can you add some documentation to the repo? Especially how to run and test specific scripts?

@MZMcBride, @Legoktm, I have some questions about the labs setup:

1. There's a file bin/dbreps which does all the parsing and formatting work for a report, apparently. Why is this file not a part of the main database-reports directory? There's a recurring error about it not being able to concatenate strings and ints/longs which I'd like to fix in that file for once and for all.
2. I want to test on wikis other than enwiki. How do I do that? What is data/project/enwiki folder for? It was a prerequisite when I tried running my report on testwiki.
3. What is the purpose of ~/.dbreps.ini and what do the fields dumpdate and userdb mean?

In T110575#1606937, @NiharikaKohli wrote:

@MZMcBride, @Legoktm, I have some questions about the labs setup:

1. There's a file bin/dbreps which does all the parsing and formatting work for a report, apparently. Why is this file not a part of the main database-reports directory? There's a recurring error about it not being able to concatenate strings and ints/longs which I'd like to fix in that file for once and for all.

https://github.com/mzmcbride/database-reports/blob/master/dbreps and you'll need to run some version of setup.py install to update the copy at bin/dbreps I think.

2. I want to test on wikis other than enwiki. How do I do that? What is data/project/enwiki folder for? It was a prerequisite when I tried running my report on testwiki.

general type reports take the database name as an argument IIRC. I'm not sure what data/project/enwiki is for...

3. What is the purpose of ~/.dbreps.ini and what do the fields dumpdate and userdb mean?

It has the bot's username/password and some other configuration. Those are for scripts that read dump files instead of using a database. grepping for "dumpdate" only shows one script that uses it though.

In T110575#1582249, @kaldari wrote:

Looks good. Here are my suggestions:

• Remove the 'No.' column as I don't see any useful purpose for it (although I know it is in the original version of the report)

For what it's worth, many/most database reports have this No. column. It's just basic enumeration, but that itself can be helpful to get an understanding of the size of a data set or to point to a particular row. This simple enumeration is common in spreadsheet programs and elsewhere, of course.

In T110575#1586025, @kaldari wrote:

Actually, I guess we have to complete the Bot permission request and start running it before this is technically finished.

Yeah, https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Page_count_by_namespace should be updated to consider this task resolved, in my opinion.

@MZMcBride I could see the No. column be useful for some reports, but in reports like this one it is just confusing. For example, I first thought that it was the number of the namespace. It's also isn't very useful in reports that are already limited to a specific number of entries.