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] Post-GSoC ’24: Flesh Out Data and Report Details #126

Open
1 task done
naishasinha opened this issue Aug 24, 2024 · 0 comments
Open
1 task done

[Feature] Post-GSoC ’24: Flesh Out Data and Report Details #126

naishasinha opened this issue Aug 24, 2024 · 0 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work 💬 talk: discussion Open for discussions and feedback

Comments

@naishasinha
Copy link
Member

Context

Automating Quantifying the Commons was a project endeavor for the Google Summer of Code 2024 program, in which a baseline automation software for data gathering, processing, and analysis was successfully developed. However given the time and resource constraints that we had to consider, there are still addressable endeavors to improve this codebase over the upcoming quarters and years. This is the third (3) of five (5) issues raised specifically for post-GSoC contributions.

Problem

The current API fetching capacity limits the level of detail that can be incorporated into the data analysis, restricting the insights that can be drawn. As an example, the Google Custom Search data source only fetches data by license, country, and language, given the API restrictions.

Description

Once more data is collected, this feature will involve expanding the data features to incorporate more detailed analysis. The approach should draw on pre-automation work from the 2022 Data Discovery Program.

NOTE: since contributing to this specific issue is limited by access to API data fetching and the fact that the solution is long-term, this issue is being set as a discussion for all open-source developers to be able to pitch their ideas for final implementation by the developer(s) who work on the codebase.

Implementation

  • I would be interested in implementing this feature.
@naishasinha naishasinha added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 💬 talk: discussion Open for discussions and feedback labels Aug 24, 2024
@naishasinha naishasinha changed the title [Feature] Post-GSoc ’24: Flesh Out Data and Report Details [Feature] Post-GSoC ’24: Flesh Out Data and Report Details Aug 24, 2024
@TimidRobot TimidRobot added 🏁 status: ready for work Ready for work and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Aug 28, 2024
@TimidRobot TimidRobot moved this to Backlog in Applications Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work 💬 talk: discussion Open for discussions and feedback
Projects
Status: Backlog
Development

No branches or pull requests

2 participants