[Feature] Post-GSoC '24: Solidify Processing Scripts for Quarterly Analysis

未關閉
#124 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
python

研究方向

首先閱讀 2-process 下的處理腳本,並追蹤透過 API 擷取的資料如何跨季度收集與表示。預期結果是產生獨立的資料集,用於將每個資料來源(例如 2024Q3)與先前的所有季度進行比較,以產生報告;實作細節仍有待討論。

由索引模型根據 Issue 內容生成。

描述

✨ goal: improvement 🏁 status: ready for work 💬 talk: discussion 💻 aspect: code 🟩 priority: low

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.
主要語言
Python
星號
50
分支
76
平均合併
17 小時 47 分鐘
30 天內合併 PR
7

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

creativecommons/quantifying 的其他 Issue

查看 creativecommons/quantifying 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。