Skip to content

Compilation of features that I do not intend to implement #9

@pakshuang

Description

@pakshuang

On the learning platform Coursemology, the date where a student can begin working on an assignment is shifted depending on the timing of their previous submissions, deadlines are sometimes also adjusted when a student submits previous assignments late enough. The mechanisms of this date shifting is unknown. This is the rationale for 2 decisions about the implementation of this bot:

  1. Assignment start dates are not included in reminders because it varies greatly from the standard date given. These reminders are sent by Coursemology already anyways.
  2. Personal adjusted deadlines are not included because the deadlines of individual's are unknown to me, and any elegant solution would have me gain access to student's Coursemology accounts. This is a can of worms I do not wish to open. These reminders are sent by Coursemology already anyways.
  3. It is possible for the reminder bot to be deployed as a personal bot instead, where the student can indicate what events they would like to receive reminders about, and how far the lead time should be. For example, if a student does not wish to participate in contests and lecture reflections and also wants reminders for events within a week from today. However, this would change the resource requirements from O(1) to O(n), where n is the number of students who wish to receive reminders. I don't think that the marginal increase in functionality warrants such an increase in resource requirements.

Metadata

Metadata

Assignees

No one assigned

    Labels

    wontfixThis will not be worked on

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions