The project goal for outreachy

Open
  • Is something wrong?
#158 26 comments 0 reactions 1 assignee View on GitHub

@TimidRobot is already working on this.

Since Oct 8, 2025.

Assessment

This issue has not been assessed yet.

Description

✨ goal: improvement ❓ talk: question 🏁 status: ready for work 📖 aspect: docs 🟨 priority: medium

Description

I have studied the documentation for the codebase written by the 2024 GSOC contributor and I quite undertand the workflow of the software especially when fetching data using APIs. While I was reading her article I saw that she talked about the pre automation code which I also see in the codebase. In this section of the codebase, there are code implementation for other data sources. She also mentioned that the pre automation code was written by previous developers, but I am guessing I have to focus on the the part she had worked on which is the lastest. I can find that part under the scripts section and it only has code for GCS and Github.

Looking at the project goal, we want to add new data sources to the project. My question is are we looking to add other sources like wikipedia, youtube ... like the ones in the pre automation code or entirely different data sources that I might have to make research on. Or start with the wikipedia, youtube, like the ones in the pre automation code.

Then when I run the 1-fetch script, am I in the dev environment? I also don't get any option to select, it just runs and I don't see any dataset. This is what it look like:

PS C:\Users\User\Documents\creative\quantifying> python scripts\1-fetch\gcs_fetch.py

2025-10-07 22:53:41,975 - INFO - gcs_fetch - Script execution started.
2025-10-07 22:53:41,975 - INFO - gcs_fetch - Parsing command-line options
2025-10-07 22:53:41,977 - INFO - shared - PATHS:
    repo: C:\Users\User\Documents\creative\quantifying
        dotenv:         .\.env
        data:           .\data
        data_1-fetch:   .\data\2025Q4\1-fetch
        data_2-process: .\data\2025Q4\2-process
        data_3-report:  .\data\2025Q4\3-report
        data_phase:     .\data\2025Q4\1-fetch
        data_2-process: .\data\2025Q4\2-process
        data_3-report:  .\data\2025Q4\3-report
        data_phase:     .\data\2025Q4\1-fetch
        data_quarter:   .\data\2025Q4
2025-10-07 22:53:41,977 - INFO - gcs_fetch - Getting Google Custom Search API Service.
2025-10-07 22:53:42,029 - INFO - gcs_fetch - Last completed plan index: 0
2025-10-07 22:53:42,057 - INFO - gcs_fetch - Beginning to fetch results from Google Custom Search (GCS) API
2025-10-07 22:53:42,057 - INFO - gcs_fetch - Query: index: 1, tool: CC BY 4.0
Dominant language
Python
Stars
52
Forks
75
Avg merge
1d 14h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from creativecommons/quantifying

All issues in creativecommons/quantifying

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.