[Update request]: GDrive section of BB "Dowload data programmatically" needs attention

[DiSanchz]

Request to update content

Background

The section on Google Drive within the Download Data Programmatically building block needs an in-depth update beyond the scope of the summer sprint. While the introductory steps remain valid, its core segment detailing the code for API connection, and programmatic downloading and uploading from Google Drive, do not work. From what I could see as part of my review of the building block during the summer sprint (see issue #742), the issues in the outdated code snippets are not related to minor changes in how this connection to drive should be formulated and handled, but rather to a comprehensive modification in the way it works by Google.

Once updated, the section would probably benefit as well from a thorough text review to ensure it aligns with the new content and structure, and that it is introduced appropriately in the context of the building block as a whole.

This issue was referred to on Pull Request 835

What needs to be updated?

"Downloading data from Google Drive" section from the Dowload data programmatically building block.

Deadline

• To be defined

Checklist

IMPORTANT: Before starting, ensure you are familiar with our style guide.

1. "Do" the content

A first reality check can be conducted by actually WORKING with our content. Just read the building block or tutorial from the perspective of a new user.

Ask yourself the following questions:

• [ ] a. Is it clear what you will learn after reading the building block?
• [ ] b. Is the language professional and transparent, or does the content come across as amateurish?
• [ ] c. Do you run into any issues when working on this building block? Are the visuals clear?

Write down any weird things you want to fix, and keep these notes.

2. Consider the checklist below and complement your initial check with these (more formal) dimensions

• [ ] Keywords and Metadata:
  • Ensure we have complete metadata in our .md files - sometimes, keywords were only loosely entered. Can you expand them? Also, use ChatGPT or similar AI tools to generate relevant other keywords.
• [ ] Section structure and learning goals:
  • Identify a few (say, 1-3) learning goals/objectives of the building block or tutorial, and highlight them at the start.
• [ ] Title and Headings within the Content:
  • Update titles and headings to create a clear and descriptive language that accurately reflects the content's focus.
• [ ] Grammar and Style:
  • Use Grammarly or other language tools to review and correct any grammatical errors or writing inconsistencies in the content.
• [ ] Use of Code Tabs:
  • Check that code that is most optimally presented in a code box is actually included in the code box.
  • If software packages are missing from the code tab (e.g., Stata, R, Python) and you have the expertise, then please add the implementation for the other software packages.
• [ ] Use of Explanation Boxes:
  • Ensure that explanation boxes are used effectively where necessary (e.g., info, warning), providing additional context, tips, or warnings to the users.
• [ ] Media and Visuals:
  • Review and update images or screenshots to enhance the understanding of the content.
  • Add new visuals where this is needed.
  • Add proper image descriptions for accessibility.
• [ ] Links and References:
  • Verify that all links and references are still valid and point to the correct resources. Use persistent links where possible.
• [ ] Version Compatibility:
  • Ensure that the content is compatible with the latest versions of relevant software packages and tools.

3. Work on your changes and commit/do a PR (for testing and reviewing)

• Now you have a good idea of what you need to fix. Create a separate branch for your update, and commit frequently while doing your changes.
• Ask another RA to check your update and identify any other inconsistencies/problems.
• Make a pull request once the content is ready for review.

Remember to create separate branches for each update and submit pull requests once the content is ready for review. Let's collaborate and ensure Tilburg Science Hub is even more valuable for our community.

[shrabasteebanerjee]

Hi @K-sohooli , whenever you are ready to start, perhaps this could be a good one to work on with Diego's help -- I am assigning him as your buddy to troubleshoot any technical questions. Once your contract is sorted, you can set up a meeting with him to coordinate, and let me know if any questions come up!

[hannesdatta]

@K-sohooli - any update?

[K-sohooli]

@hannesdatta - it is now updated. One small feature has been changed in Google Drive, so the part related to that part in "Download Data Programmatically" BB is updated accordingly and the corresponding image is replaced. Additionally, several errors in the Python code have been fixed, along with the addition of a few details for clarification purposes. Finally, a summary has been added to the article. However, the "R" scripts are not reviewed yet. And there are two images related to "R" in the 'download-data.md' file but those images are not included in images folder.