Project usage overview page: Filter by version

+1 this page can not be used to find the best and greatest anymore, and better modules tend to be overlooked by older more popular ones. There are about 11 modules in the top 25 that I personally would not use in D7 or are only for D6 or less.

2nd half of the original report (about the project browsing/search pages) is duplicate with #377736: Module filter or sort by release should impact what information is displayed.

However, yes, it'd be nice to be able to filter the usage overview page by version. Moving to a more appropriate queue for where this code lives to actually implement the change. We already have the data separated by version in the {project_usage_week_project} table, so it's mostly just a UI and caching question to get this done. The code lives in project/usage/project_usage/includes/pages.inc in the project_usage_overview() function. It's pretty evil code, generating an insane query that lets you table sort by any week. Currently it's also doing some nasty SUM(DISTINCT p{$i}.count) AS week{$i} stuff to get the total across all versions. So, if you *did* filter by a version of core (stored as {project_usage_week_project}.tid) it'd actually simplify the query tremendously.

Maybe we could filter by a specific version by default, but retain the option to show totals across "all versions" or something in case people really want that.

Cheers,
-Derek

I would be very happy with just a singular version per page and that sounds like it follows the KISS principle, but other users would (maybe) still prefer being able to see the combined results? Is there an easy way to poll users before starting work on this issue?

Personally, I would find a separate page per major core version to be completely acceptable, and much better than the current combined page. I have no objections to a combined page if people want that, but I can't think of a time when that was ever the information that I wanted. Considering we already have the combined page, I'm not clear what is gained by removing it, but a huge +1 to providing per-major-core-release pages.

Marked #1297804: Project usage: Option to display overall module usage statistics by Drupal version a duplicate, and replied to http://drupal.org/node/329620#comment-4623900. If anyone finds any other duplicate issues or places asking about this, please link them to here. Let's get some eyes on this.

Here's the query I ran manually from the d.o database, slightly cut down from the full 3-week comparison query that project_usage_overview() runs:

SELECT
  n.nid,
  n.title,
  pp.uri,
  SUM(DISTINCT p0.count) AS week0
FROM node n
  INNER JOIN project_projects pp ON n.nid = pp.nid
  LEFT JOIN project_usage_week_project p0 ON n.nid = p0.nid 
WHERE
  n.nid IN (SELECT nid FROM project_usage_week_project)
  AND n.status = 1
  AND tid = 103 /* This is new; 103 for Drupal 7; Drupal 6 is 87 */
GROUP BY n.nid, n.title
ORDER BY week0 DESC;

Here are the results, as CSV.

It'd indeed be nice if we could find this information out whenever we wanted, since the delta between the two is quite significant. Hope that query helps someone who has time to make that happen. :)

Hm. D.o's file upload doesn't seem to be working. Let's try this:

D7: http://dl.dropbox.com/u/10160/d7-top-modules.txt
D6: http://dl.dropbox.com/u/10160/d6-top-modules.txt

The disparity between versions is going to get bigger with 8.x/7.x vs. 7.x/6.x, so bumping to major.

A display that allowed the user to not only specify the Version, but also put 'between dates X and Y' would help expose the 'rising stars'

I guess this is even more advantageous to get in.

On the Module page, if you filter by Drupal 7, and sort by most installed, it counts the total number of installations (including D6 and before).

This appears OK.

The order of the 10 most installed modules, filtered by 8.x (bracketed values have 7.x stats). Correctly ordered with the ones I checked, and definitely are not order by total combined.

Drupal: 101,856 (1,056,153)
Token: 15,072 (749,378)
CTools: 15,027 (872,427)
Admin Toolbar: 12,334 (0)
Pathauto: 11,269 (657,569)
Devel: 7,522 (209,561)
Metatag: 6,740 (317,585)
Field Group: 6,546 (265,023)
Layout plugin: 6,436 (0)
Google Analytics: 5,836 (353,311)
Libraries API: 4,019 (698,383)

For performance, I think tabbed versions would be best. Without additional work, I guess it would look something like:

Random aside: This seems strange that the usage of the most installed module is only about ~15% core, nearly suggests most installs don't have any contrib modules or the stats are out....

A display that allowed the user to not only specify the Version, but also put 'between dates X and Y' would help expose the 'rising stars'

I agree with @petednz on this - or perhaps a "Position 30 days ago"-column, with a red or green arrow pointing up or down could also accomplish this?