XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Minor
    • None
    • TPDM v0.7.0
    • People

    Description

      Through the mapping process, we learned a few of our Canvas course and grade related information could not fit within the TPDM.  These were the fields and how they relate to Relay. We are hoping optional fields could be included for our use cases described below.

      • Assignment Level: 
        • (1) Canvas “points_possible” value indicates the total points possible for the assignment. The TPDM has a MaximumScore field within the RubricLevel domain, but there doesn't seem to be a similar field for assignments, which has been mapped to the Gradebook domain in Core. For additional context, students receive a grade for their submission of an assignment, and some assignments are associated with rubrics. Not all assignments in a grade book have rubrics.
        • (2) The TPDM does not have a field for “group weight” for assignments. 
        • (3) GradeType as an indicator of what format the grades are held would be a helpful optional field. Our grades can take on different numerical format (e.g. points, percent, or pass_fail). Core does capture the numeric grade earned or letter grade, but including this allows is not a clear indicator of what the number represents. Points, percent and pass_fail all take on numeric values and it would be unclear to distinguish what type of grade or score the values truly represents. 
      • Use Cases: Having these indicators will help us to track progress and report out to campuses where students need more support. Our campus deans have often requested us to report out the assignment group's weight and the points possible as a way to understand the values associated with a total percent of a grade. The end grade for the course is valuable, but including the additional context of the weight and points possible allows for a better overview when displaying information to ensure we’re comparing grades (and student’s progress) with assignments that have an actual comparable match. It also ensures equity since one assignment with a lower point_possible and weight value should not be seen as a comparable match to one with a higher point and weight value. 
      • Rubric Level:
        • (4) Mastery indicator and (5) percent and points_possible for to show how the student did on a rubric associated with an assignment.
        • Use Cases: The mastery boolean indicator and points possible, gives our accreditation team and deans the ability to see how many students mastered a learning outcome. Its will be helpful for us to display/report this information to our campuses to either (1) dig in deeper to which learning outcome row has frequently been the lowest, (2) what support can be created for continuous improvement, and (3) our accreditors like CAEP often request this information in updates, reports, or site-visits.
      • Submission Level
        • (6) Graded_at, (7) Attempts, (8) excused are fields we were not able to be mapped in the TPDM. 
      • Use Cases: Our leadership/deans want to know the efficiency of our faculty and what supports that should be created for students. To have the ability to track how many attempts on an assignment can help determine if there should be an intervention if there are many attempts to one assignment for students. This will help faculty advisor their students better while allowing for the leadership in the campus to know how faculty are doing as well.

      Attachments

        Activity

          People

            Unassigned Unassigned
            tfernandez Tiffany Fernandez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Salesforce