Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Aggregate Student Summary and Student Timeline #231

Closed
philipmjohnson opened this issue Apr 20, 2018 · 0 comments
Closed

Implement Aggregate Student Summary and Student Timeline #231

philipmjohnson opened this issue Apr 20, 2018 · 0 comments
Assignees
Projects

Comments

@philipmjohnson
Copy link
Contributor

philipmjohnson commented Apr 20, 2018

Please do work for this task in a branch called issue-231.

Aggregate Student Summary Statistics

In /radgrad@hawaii.edu/analytics/students/summary, select a time interval, and the system will generate aggregate summary statistics relative to the current student population.

Absolute numbers (and percentage) of students who did the following during the interval:

  • logged into the system
  • exhibited one of the six "behaviors" listed below.
  • (later) how many "Engagements" occurred

Absolute numbers (and percentages) of students at each level by the end of the time interval. (if this is easy to do).

Individual Student Timeline

In /radgrad@hawaii.edu/analytics/students/<student>?start=2018-01-01&end=2018-05-02

Create a vertical timeline with dates and actions that occurred on that date for that student. Each entry in the timeline refers to a single session. The label is the date and the start time of the session. The first line indicates the number of minutes in the session. A session can contain one or more high-level "behaviors". The initial set of behaviors are:

  1. "Change Outlook": This corresponds to a change in interests, career goals, or degree plan. It would be good to know the "before" and "after" state when any changes are made.

  2. "Exploration": This corresponds to viewing entries in the Explorer. It would be good to track which entries are actually retrieved so we know which career goals, interests, etc. are most interesting. How long did they stay in each page of the Explorer before clicking away?

  3. "Planning": This corresponds to work with the Degree Planner. It would be good to know when courses and/or opportunities are added and/or deleted. How long did they spend on planning before clicking away?

  4. "Verification": We want to know when a student requests verification, and what opportunity was requested.

  5. "Reviewing": When a student submits a review of a course. How long did they spend on this?

  6. "Mentorship": When a student visits the MentorSpace page, and how long they stayed there before clicking away.

  7. "Level Up": When a student achieves a new level.

  8. "Complete Plan Achieved": The moment when a student has first created a degree plan that, if executed to completion, will result in at least 100 points in all three ICE categories.

In addition, this timeline should (eventually) record when a user received an "Engagement" (such as an email).

Augment user interaction types

Log the following user interactions:

  • Add review
  • Change of level
  • Request verification
@philipmjohnson philipmjohnson changed the title Implement Student Event Timeline Implement Student Activity Timeline Apr 20, 2018
@philipmjohnson philipmjohnson added this to Backlog in M6 Apr 21, 2018
@philipmjohnson philipmjohnson removed this from Backlog in M6 Jun 18, 2018
@philipmjohnson philipmjohnson added this to Backlog in Fall 2018 Jun 19, 2018
@philipmjohnson philipmjohnson moved this from Backlog to In progress in Fall 2018 Jun 19, 2018
@philipmjohnson philipmjohnson changed the title Implement Student Activity Timeline Implement Aggregate Student Summary and Student Timeline Jun 19, 2018
@philipmjohnson philipmjohnson moved this from In progress to Done in Fall 2018 Oct 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants