Expose historical project usage statistics via the API

This was a conscious decision introduced in #3498849: Project usage totals should exclude Drupal 7 branches.

Single entry for specific releases is not an option, but you can parse the field and store it as you need:

"field_active_installs": "{\"8.x-3.x\":1671,\"8.x-4.x\":2,\"5.0.x\":2709,\"5.1.x\":7914}"

For example:

// [data > attributes > field_active_installs]
$field = "{\"8.x-3.x\":1671,\"8.x-4.x\":2,\"5.0.x\":2709,\"5.1.x\":7914}";
$usage = json_decode($field);
foreach ($usage as $branch => $total) {
	echo "Branch: " . $branch . " // Total: " . $total . PHP_EOL;
}

Produces:

Branch: 8.x-3.x // Total: 1671
Branch: 8.x-4.x // Total: 2
Branch: 5.0.x // Total: 2709
Branch: 5.1.x // Total: 7914

Sorry, I get what you are asking now.

You mean weekly data for each branch. That information is not stored as part of the entity itself, it has a separate table.
I guess we could do something like #3559622: Provide way to access all projects maintained by a user, where we create a new endpoint with custom parameters.

I've put some WIP I've been experimenting with just to see if we can reuse some code. I will continue work on it in the coming days.

This will also conflict with the other mentioned issue, so I will fix that once the other is deployed/merged.

I'm happy with the logic here to be reviewed, but as mentioned before, this #3559622: Provide way to access all projects maintained by a user should go first, and I will fix the conflict once merged.

The endpoint will be something like /drupalorg-api/project-usage?nid=3060[&weeks_ago=10]
If no "weeks_ago" param is given, it will be all-time data.

The output will be split by weekly timestamps:

{
  "usage": {
    "timestamp1": {
      "5.x-1.x": 159454,
      "6.x-2.x": 50834,
      "7.x-1.x": 15643,
      "6.x-3.x": 51159
    },
    "timestamp2": {
      "5.x-1.x": 15947,
      "6.x-2.x": 5038,
      "7.x-1.x": 1545,
      "6.x-3.x": 5110
    }
  },
  "success": true
}

Feedback addressed.

Either this or #3559622: Provide way to access all projects maintained by a user can go first and then I'll adapt the other. I don't think it really matters the order, so if this one is ready before it can be merged.

Looks good to me

This is now merged. It will be deployed today.

Deployed.

Example, webform usage for the last year: https://new.drupal.org/drupalorg-api/project-usage?nid=7404&weeks_ago=53

Note that querying all time data for big modules might incur in timeouts when accessed via web (5xx errors).

True! Thanks for reporting. I took some of the logic for the individual weekly jobs, but it was multidimensional arrays, so I'm sure that I forgot to reset something somewhere. Looking into this.

Found the issue! We were literally looping the loop on numbers!

Commit: https://git.drupalcode.org/project/drupalorg/-/commit/eadec4681ee355fcab...

Deploying shortly.

Numbers here https://new.drupal.org/drupalorg-api/project-usage?nid=232629&weeks_ago=2 match exactly what we see in comment #15.

{
    "usage": {
        "1763251200": {
            "6.x-1.x": 22,
            "7.x-1.x": 2,
            "7.x-2.x": 6226,
            "8.x-3.x": 1665,
            "8.x-4.x": 2,
            "5.0.x": 2815,
            "5.1.x": 8236
        },
        "1763856000": {
            "6.x-1.x": 21,
            "7.x-1.x": 3,
            "7.x-2.x": 6162,
            "8.x-3.x": 1612,
            "8.x-4.x": 2,
            "5.0.x": 2552,
            "5.1.x": 8308
        }
    },
    "success": true
}