Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Track use or "people served" #45

Open
TimidRobot opened this issue Mar 10, 2023 · 1 comment
Open

[Feature] Track use or "people served" #45

TimidRobot opened this issue Mar 10, 2023 · 1 comment
Labels
✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work 🏷 status: label work required Needs proper labelling before it can be worked on 💬 talk: discussion Open for discussions and feedback

Comments

@TimidRobot
Copy link
Member

Description

It would be great to track use or "people served"

  • Downloads for openly licensed works
  • Listener statistics for openly licensed works or works that include openly licensed samples
  • Purchases of openly licensed works
  • ???

Questions:

  • Which APIs might provide a direct or indirect indication of use?
  • Are there any free non-API (non-machine-readable) data sources that are big enough to be worth including?
  • ???

(This feature is blocked by #22)

@TimidRobot TimidRobot added 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💬 talk: discussion Open for discussions and feedback labels Mar 10, 2023
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Mar 11, 2023
@Paulooh007
Copy link
Contributor

This will be really helpful in assessing impact or providing valuable information for marketing and promotion efforts.
Although it might be more challenging, cuz not all licensed works are hosted on platforms that provide APIs, and not all APIs will provide usage or download statistics for a particular work.

For Flickr, using the API we can access the view count for a photo, But technically, anyone who has viewed one of your photos has "downloaded" it into their browser, since a browser must download the image to display it. So the question is, does the view count really count as download counts?
The current Flickr data we have recorded the view count already.

The internet archive API also provides a way of getting metadata about an item using the search_items() method, The metadata can include title, collection, downloads etc
I was able to create a simple script that searches for items with a CC BY-NC-SA 4.0 license and
return their download counts, see gist
We may have to get download count (or a cumulative sum) of each item for every licence type

Also, the Wikimedia API's imageinfo module has a globalusage property that gives information about a file's usage across Wikimedia projects, including the number of pages that embed the file, the titles of those pages, and the global usage count. This feature is helpful for tracking how widely a particular file is used across Wikimedia projects.
I’m trying to see how to make this work for our use case.

Though it has it's limitations, the globalusage property may not be available for all files on Wikimedia Commons. In some cases, the API response may not include a globalusage array, even if the file is used on multiple pages across Wikimedia projects. Additionally, the globalusage property only provides information about where a file is used across Wikimedia projects; it does not provide any information about usage outside of Wikimedia projects.

@TimidRobot TimidRobot moved this to Triage in Applications Sep 10, 2024
@TimidRobot TimidRobot moved this from Triage to Backlog in Applications Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work 🏷 status: label work required Needs proper labelling before it can be worked on 💬 talk: discussion Open for discussions and feedback
Projects
Status: Backlog
Development

No branches or pull requests

3 participants