ubc-la-hackathon/student-dashboard

Come build a modern web app showing a heatmap of your Canvas discussions!

student-dashboard's Issues

Test all links in readme

Make sure everything points to where it should and there are no dead links

[Bug] Heatmap data persistence

• data in heatmap persists when toggling back and forth between courses in dropdown
• heatmap therefore not accurate
  • shows discussion data on days where there is none

Change color scheme of heatmap

Data: Canvas discussion data

Add in diagram of app architecture

Generate more new ideas

Related to #2.

I came up with many feature ideas for heatmap, but not that many for completely unrelated tools/visualizations.

We should add at least 3 more intermediate and 3 more advanced.

Should we separate out the categories into beginner, intermediate and advanced?

Add list of volunteers under README.md#Volunteers

There are 7 confirmed external volunteers.

Profile
Name:
Position/Company: (optional!)
LinkedIn/Profile: (optional!)
About Me: (What is your educational background? What do you do? What are you interested in? What do you want the students to know about you?)
Ask Me About: (What are you excited to help with/be asked about?!)

Also make sure volunteers have CWLs: https://activate.id.ubc.ca/iamweb/

Choose any course from the course calendar and display information about that course

Data: course calendar data, degree requirements data

Create aggregate discussion

Aggregate discussion from all of your courses instead of one course.

Create a tool that allows you to compare courses that share the same information from a selected field

Data: course calendar data

Create date range selector

Create a date range selector that will filter the data so that the heatmap displays only the data that fits within the specified date range.

Deploy working (static) demo app

Can generate fake data for, say, 3 fake courses, and link it with a timeout to emulate the fetching.

Display a bar chart or bubble chart instead of a heatmap

Data: Canvas discussion data

Create and link feedback survey

The link goes here: https://github.com/UBC-LA-Hackathon/student-dashboard/blob/master/8-Feedback-And-Thanks.md

Create more structured content for intermediate ideas

1. Create _ideas folder in root.

2. Create content for:

   Intermediate Heatmap

   • Create a dropdown that allows users to select what course they want to see the heatmap for.
   • Add a legend to the heatmap showing how many posts each shade of blue represents.
   • When a cell in the heatmap is hovered, display a count of the number of posts.
   • Create a date range selector that will filter the data so that the heatmap displays only the data that fits within the specified date range.
   • Aggregate discussion from all of your courses instead of one course.
   • Create a way to show switch between showing just TA/Instructor posts and all posts.

   Advanced Heatmap

   • When a cell in the heatmap is hovered or clicked, show the discussions that were posted at that date and time.
   • Create a calendar view so that it is possible to navigate between weeks/months.
   • Create a filter that allows users to select a specific individual to see when they post.
   • Run text/sentiment analysis on the discussion posts and use this data to create a heatmap.

   Intermediate New Ideas

   • Create a degree planning tool that shows students what courses they are eligible to register for, given a list of courses in Canvas students have completed and the [degree requirments data (CSV)](TODO: LINK)
   • More ideas?

   Advanced New Ideas

   • ??

Intermediate may have code snippets, advanced will have none, just text.

If this is too much work, we can cut down on the suggestions, or just write up steps for a subset of them.

Fix links after issue#1 is added

The Tasks ordering will break, which will break some links to Tasks. Once #1 is resolved, check links to ensure they work.

Link to survey

Still have TODO item in codebase.

Need to add survey link under "Feedback and Thanks Section"

Once _ideas are complete, remove numbering

The numbers in the names of the individual ideas don't make any sense, remove them once we link them back to https://github.com/UBC-LA-Hackathon/student-dashboard/blob/master/6-Create-Advanced-Data-Viz.md

Create explanation of data for the CSV/JSON

Columns and what they mean.

Make it more explicit that two terminal windows are necessary

One for backend and one for frontend

Create and link presentation signup form

Use Google forms for signup?

Afterwards link on https://github.com/UBC-LA-Hackathon/student-dashboard/blob/master/6-Share-Your-Work.md#present-your-work

Refactor App to not perform data fetching

Architecture could be improved by not performing data fetching within App. It shouldn't be responsible for fetching discussion data, self, other data for other views...

Instead App should simply instantiate child views that are responsible for fetching the data they require. This will also make it less messy for students to build new views - they'll simply delete components they don't need instead of having to also delete the useEffects within App.

Might also be worth creating a Welcome component to encapsulate the welcome message that performs the getSelf fetch.

Documentation also needs to be updated to reflect these changes.

Create a private repo with branches for each reference implementation

This repo contains a fully working application with a branch for each intermediate feature that we've implemented. Volunteers will have access to this "answer key" to get familiar.

Remove signup links after hackathon sells out

Tickets are selling fast, get yours now before they're all gone!

Implement caching so that data for a course that is already fetched is not refetched unnecessarily.

Create "common issues" section

@craigdsthompson:

We might want both generic and specific common issues sections. Maybe we should start with specific, and if the same hints/tips crop up across multiple features, then we aggregate to a generic common issues doc? No strong preference from me at this point.

The "beginner reference for d3" will probably be a generic need.

Update dependencies

Add links to data in step 6

https://github.com/UBC-LA-Hackathon/student-dashboard/blob/master/6-Create-Advanced-Data-Viz.md

Confirm we are using consistent material for D3 -> v5

Review any links and materials/confirm we are using consistent material for D3 -> v5

Create cell hover display count

When a cell in the heatmap is hovered, display a count of the number of posts.

Create TA/instructor heatmap toggle

Create a way to show switch between showing just TA/Instructor posts and all posts.

Add disclaimer that repo is under active development

Remove disclaimer on March 13th

Remove #22 before the event.

Uploads are disabled.

how to able uploads

Scrape course calendar data

http://www.calendar.ubc.ca/vancouver/index.cfm?tree=12,0,0,0

Yikes.

Expand basic build to include a dropdown course filter

Heatmap should display discussion from course selected.

There will also need to be a new Tasks readme created, probably between step 4 and 5.

Determine the courses with no prerequisites or only 1 prerequisite

Data: degree requirements data

Create add legend to heatmap

Add a legend to the heatmap showing how many posts each shade of blue represents.

Split up step 5 into sub-steps

Step 5 is too big on its own.

heatmap changes for blank discussions

If we visit a course with discussions then visit a course without discussions, the application isn't able to alter the heatmap back to blank state.