Expose organization contributed rank and weighted credits

Ready to test. Check as anonymous user: https://fjgarlin-drupal.dev.devdrupal.org/api-d7/node/1758226.json
MR: https://git.drupalcode.org/project/drupalorg/-/merge_requests/270

Nice! Can you share the HTTP basic credentials, or if they can't be public feel free to DM them to me on the Drupal Slack?

Is it a big deal to run the script on your dev site that updates the annual issue credit stats?

I went to compare against https://fjgarlin-drupal.dev.devdrupal.org/drupal-services but none of the stats are showing there. The stats at https://fjgarlin-drupal.dev.devdrupal.org/api-d7/node/1124040.json don't match what's on production right now either, so I can't confirm that this is exposing the right data.

If you say "trust me, this is right and it will take 3 days to regenerate credits on the dev site" then +1 from me, given that the fields do actually show up in the response.

The basic auth credentials for public drupal.org dev sites are just: drupal/drupal

Dev sites have a truncated database because the dataset is simply too large - so yes - you will see a more accurate picture on production.

This is deployed.

Thank you!

I'm still not sure what exactly is being exposed though. At https://www.drupal.org/drupal-services → we see "2,640 issue credits weighted, last 12 months" for Lullabot. I don't see 2640 anywhere in https://www.drupal.org/api-d7/node.json?nid=1124040 → . I thought that would be "field_org_issue_credit_year": "687", but I'm unclear what 687 is referring to. Is the marketplace showing the field_weighted_org_issue_cred_yr field that is still hidden?

If we look at Lullabot in the marketplace https://www.drupal.org/drupal-services → , we can see "2640 issue credits, weighted, last 12 months".

2640 is a calculated number, so you will not find it in the json output. It is 687 issue credits, with a factor/weight of 1 for most issues, and 10 for core issues or strategic initiatives (ie: navigation, project_browser, automatic_updates...). More info on weighting here: https://www.drupal.org/drupalorg/docs/marketplace/contribution-credit-we... →

If you check Lullabots json node: https://www.drupal.org/api-d7/node/1124040.json →
- field_org_issue_credit_count: 157 // Issues in the last 3 months
- field_org_issue_credit_year: 687 // Issues in the last year
- field_org_marketplace_rank: 3600 // DCP levels weights. Lullabot is Platinum Drupal Certified Partner.
- field_org_contribution_rank: 3630 // Total value from all contributions: 2640 (from above) + case studies + contributor roles + project supported + ...

Note that in this case, field_org_contribution_rank and field_org_marketplace_rank having a similar value is a total coincidence as they are not related at all.

We have a script that runs weekly and makes all the calculations, to make the sorting easier, storing the value in "field_org_contribution_rank".
- Script: https://git.drupalcode.org/project/drupalorg/-/blob/7.x-3.x/drupalorg/dr...
- field_org_marketplace_rank: https://git.drupalcode.org/project/drupalorg/-/blob/7.x-3.x/drupalorg/dr...

You can also see more details about the total value if you check Lullabot "owner tools" (only the node creator can see this). In there, it breaks down some of the values.

Finally:
- The marketplace ( https://www.drupal.org/drupal-services → ) is sorted by field_org_marketplace_rank first, and then field_org_contribution_rank.
- The organizations listing ( https://www.drupal.org/organizations → ) is sorted by field_org_contribution_rank.

I hope all this info helps.

It does, thank you so much!

Automatically closed - issue fixed for 2 weeks with no activity.