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: Solidify Processing Scripts for Quarterly Analysis #124

Open
1 task done
naishasinha opened this issue Aug 24, 2024 · 1 comment
Open
1 task done
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 first (1) of five (5) issues raised specifically for post-GSoC contributions.

Problem

Due to only having one quarter’s worth of data, current processing scripts (2-process) are not fully optimized for long-term data analysis, which makes it difficult to accurately assess trends and patterns over quarterly periods.

Description

This feature involves refining the processing scripts to handle data collected over a larger period, enabling more robust quarterly analysis. The focus will be on adding code that can effectively compare details of each data source by quarter (ex. 2024Q3 data is compared to all previous quarters’ data) and adding them into separate datasets for report generation.

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
@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
@Clemo97
Copy link

Clemo97 commented Oct 22, 2024

Hey @naishasinha and @TimidRobot , I'm in the middle of tackling this issue and I am having trouble creating a flickr developer account and as such can't get FLICKR_API_KEY and FLICKR_API_SECRET.
I keep getting the "Account Creation Falied" error, no matter what email I use.
Screenshot from 2024-10-21 19-40-09

I have tried contacting flickr customer support, but the issue is yet to be resolved.
How did you guys go about fixing this issue.

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

3 participants