You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data providers and other stakeholders can benefit from knowing how much uptake the data gets that they are publishing via our services. Similar to https://pageviews.wmcloud.org/ for WikiMedia uptake.
This came up in the context of the US GHG Center, where we have looked at S3 access patterns, but those lack a lot of detail in terms of (geographical) area of interest, etc., and can be biased in all sorts of ways due to the nature of the data.
This is an idea to gather more detailed (yet anonymous) data access metrics on the API level - which collections, date ranges, areas are most often requested? Guarding user privacy would obviously be a concern.
Acceptance criteria
Accepted this idea for further incubation and fleshed out the goals / plan or rejected it
The text was updated successfully, but these errors were encountered:
Data providers and other stakeholders can benefit from knowing how much uptake the data gets that they are publishing via our services. Similar to https://pageviews.wmcloud.org/ for WikiMedia uptake.
This came up in the context of the US GHG Center, where we have looked at S3 access patterns, but those lack a lot of detail in terms of (geographical) area of interest, etc., and can be biased in all sorts of ways due to the nature of the data.
This is an idea to gather more detailed (yet anonymous) data access metrics on the API level - which collections, date ranges, areas are most often requested? Guarding user privacy would obviously be a concern.
Acceptance criteria
The text was updated successfully, but these errors were encountered: