Visualization: KSAT's taught by module & Course
What problem(s) will it solve?
What problem do we solve?
Right now we can't see in a graphical fashion which KSAT's are accomplished by which modules and courses. This ticket is intended to iterate on our visualization in order to create a new view of the data to satisfy the following questions:
- Which courses teach which KSATs?
- Which modules teach which KSATs?
- Which modules are part of which courses (probably minor but for IDF... maybe this deserves its own view? maybe not MQT might be large too).
- Which KSATs are taught by OJT by default (neither course nor module; AKA Training mapped is blank)?
- Which KSATs are DELIBERATELY taught by OJT? (This is different and means we've put "OJT" into the training link rather than leave blank).
Who is the intended user(s)?
All users insomuch as that we use this view to quickly get a visual representation of HOW things are taught.
Course Designers/Maintainers - Use this visualization to see trends, clusters, patterns of information and to spot oddities.
- Hmm... I see these two courses share 95% of the KSATs but the 2nd one also teaches 10 more. Maybe I should combine?
Management - They like pictures!
Lay out the expected user experience
- Users would hover over the Visualizations menubar option and see the different choices. This particular ticket would likely be called the "Training View". The visualization that it defaults to is currently the "requirements view"
- After selecting their view Kumu.io would launch into the view of that dataset.
- Oohs and Aah's commence.
Proposal
- We'll need to train and or get people access to the Kumu.io site so they can learn and prototype out how this might look. Recommend using a small dummy dataset to play with.
- Using the dummy dataset propose the view below in comments so we can all see... demo to audiences.
- Once proposal is accepted, we'll work on modifying the kumu.io gitlab job to build an additional/modified links as part of its kumu.json output.
- We'll need to update the website to link to a new embed.
- we'll want to author a new documentation page explaining what people are looking at (minimal) NOTE: need a section for "visualizations"
Further details
We might need to setup a more official kumu.io account.
Permissions and Security
We might need to setup a more official kumu.io account.
- This could require sharing account details :(
Documentation
Update User Documentation
- Create a "Visualizations" section
- Identify the different views
Update Developer Documentation
- Document changes to the Kumu.io job(s)
Update CYT Overview briefing
- None
Availability & Testing
What does success look like, and how can we measure that?
We find the views helpful to understand what-trains-what