Design visualizations for the Study Group Events page

[auremoser]

Description

The Study Group Events Page is an open canvas for additional visualizations about upcoming events. We'd like to solicit designs for visualizations (charts, graphs, maps) to populate this page with update-able data about Study Group activity globally.

Process

1. Step 1: Person learns about the Study Group Program.
2. Step 2: Person finds the Study Group Events page.
3. Step 3: Person learns more about events happening at individual study groups globally.

Expected result

Ideally, the Study Group Events Page would be a single location/url where people could view statistics and activity updates on the Study Group Project and activity from all of the forks of that project.

Current result

Currently, we have a form link on the Study Group Events page which allows you to submit information manually about your events. It would be great to automate additional inputs to the page (visualizations or just event data).

Possible Fix

There is a sg-events repository with data collected from Study Group forks, but it would be nice to visualize those data.

Here is the repository where the code for the Events page is stored, the README contains valuable information about how it works and how to run it locally.

Image

Study Group Events Page

---

References

• sg-events repository - where we store data collected on Study Group forks
• Study Group Events repository - the code we use to build a little website to display data collected from Study Group events
• Study Group Events site - the website where the repository above displays visualizations or upcoming events
  [if relevant, reference related issues here]

[AnamikaD]

@auremoser what kind of visualization you want? like charts etc!

[auremoser]

I think it would be nice to develop visualizations other than the map on the Study Group Landing Page.

Charts in any form are totally welcome, but perhaps something that shows time-series visualizations of the following:

• how many forks of the Study Group Repo
• what countries the forks come from (where known)
• member counts (maybe from the members.yml file) from Study Groups (an average number, by month perhaps)
• lessons available in the lessons repo, by theme (like a bar chart with how many lessons/issues for lessons exist for Python/R/Open Science/themes used as "labels" in the issues queue
  • how many lessons per theme/language
  • how many lessons per level (beginner, intermediate, advanced)

These are just ideas! I'm open to other suggestions/proposals too!

For reference, I think the Github report card is inspiring; not the same use case as here, but at least it's working with Github data which could be a valuable model.

[AnamikaD]

@auremoser Thank you for the guide! The ideas are great. I will send you the draft proposal.