\n\tNov 14, 2016 – Nov 23, 2016\n<\/p>\n
\n\tThis cycle we experimented with reviving the student record concept. In STEP this entity is the degree record. This data entity attempts to group a series of quarters for a single student into a collection of effort toward a degree (or certificate, etc). In our reporting and creation of other features we keep coming up with needs for data points like "when did the student enter this program", "what is a student's status".\n<\/p>\n
\n\tThe difference in our approach this time is that we want to make student "Record" user manageable. We will still have the logic we have defined for expected pathway transitions. But when our automated grouping doesn't represent an edge case the way we want, we will have GUI edit tools allowing admin staff to manually group quarters into a Record.\n<\/p>\n
\n\tRight now student "Record" has been prototyped and is under consideration. We will be careful not to couple it to other features until we have decided on its utility.\n<\/p>\n
Nov 14, 2016 – Nov 23, 2016 This cycle we experimented with reviving the student record concept. In STEP this entity is the degree record. This data entity attempts to group a series of quarters for a single student into a collection of effort toward a degree (or certificate, etc). In our reporting and creation of other features we keep coming up with needs for data points like "when did the student enter this program", "what is a student's status"….<\/p>\n