Refactor/summary task status scatter

[kacieje]

thoth-tech/doubfire-web:doc/readme migration progress update thoth-tech#432

Description

This PR removes an unused coffee component summary-task-status-scatter. No references to this visualisation could be found for initialisation and it could not be triggered in testing.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Triggering of the component was tested by searching through the code base for references to the component (summary-task-status-scatter and summaryTaskStatusScatter). The component itself (summary-task-status-scatter.coffee) and the visualations template (visualisation.tpl.html were located but no triggers for actual use. Once the changes in this PR were applied, various visualisations were tested and no changes to their functionality were identified.

Testing Checklist:

• Tested in latest Chrome
• Tested in latest Edge
• Tested in latest Safari
• Tested in latest Firefox

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[b0ink]

Hi @kacieje

Thanks for your contribution.

Although this component isn’t currently used, we’d prefer to rebuild it rather than remove it.

The goal is to replace it with a Normalized vertical bar chart, where:

• X-axis: Task Definitions (abbreviations)
• Y-axis: Number of student Tasks per Task Status("Not Started", "Ready for feedback", "Complete", etc.)

This will give staff a clear overview of task completion and how it changes throughout the semester.

I've started the refactor in these PRs, but there's still work to do:
Frontend: #1060
Backend: doubtfire-lms/doubtfire-api#556

I’m currently focused on other features, so this is up for grabs if anyone wants to pick it up and continue.

Notes:

• The frontend PR currently uses placeholder data and is not calling the backend. (Endpoints need to be exposed and hooked up to the frontend)
• The backend aggregates the required data into a single JSON file per unit, but this still needs automation via rake tasks and cron jobs.
• Ideally, we’d store daily snapshots of these JSON files to allow historical views across the semester.