MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for the ‘notes’ tag

Introducing MarkUs 0.7.0!

with 2 comments

Wow, what a great semester!  The team worked really hard, and should be very proud of themselves.  Besides all of the fixed bugs and the newly written tests, the MarkUs team cranked out the following new features:

  • A more stable, polished, and usable notes system.  Notes can now be applied to students, groups, and assignment submissions
  • An alternative, “flexible” marking scheme type that allows graders to input arbitrary numerical grades, as opposed to the more strict rubric marking scheme
  • A new marks spreadsheet feature that allows instructors and graders to input grades from assignments, quizzes, or tests, in an Excel-like web-based spreadsheet.  Grades can also be uploaded and downloaded via CSV file
  • The table of student submissions can now be bookmarked, and the back-button works correctly
  • Lots of bugfixes and usability fixes.

So what are you waiting for?  Get MarkUs 0.7.0 right now!


Benjamin Vialle
Christian Jacques
Nelle Varoquaux
Victoria Mui
Joseph Maté
Robert Burke
Bryan Shen
Brian Xu
Fernando Garces
Farah Juma
Severin Gehwolf
Mike Conley

Written by m_conley

April 28th, 2010 at 11:16 pm

Posted in Uncategorized

Who is Doing What: Winter 2010

without comments

The MarkUs team is meeting weekly on #markus on Fridays at 3:30PM.  Every Thursday, each member of the team (including myself) must come up with a “punchline” status update.  These updates are short, bulleted, straight-to-the-point reports that tell us how everybody is doing.  They follow a very simple format: see these three examples.  The punchlines need to be published on this blog every Thursday, and it is every team member’s responsibility to give them a read before coming into the meeting.

But instead of everybody logging in and editing a single blog post for the status updates, we’ll rotate responsibility for collecting/publishing punchlines every week.  Similarly, we will rotate the duty of converting our IRC meeting logs into notes.

Here’s the schedule outlining who is doing what each week.  Teammates:  I highly suggest bookmarking this page.

  • Jan 22:  punchlines:  Mike, minutes:  Robert
  • Jan 29:  punchlines:  Robert, minutes:  Farah
  • Feb 5:  punchlines:  Farah, minutes:  Joseph
  • Feb 12:  punchlines:  Joseph, minutes:  Victoria
  • Feb 19:  punchlines:  Victoria, minutes:  Bryan S
  • Feb 26:  punchlines:  Bryan S, minutes:  Brian X
  • Mar 5:  punchlines:  Brian X, minutes:  Mike
  • Mar 12:  punchlines:  Robert,  minutes:  Farah
  • Mar 19:  punchlines:  Joseph,  minutes: Victoria
  • Mar 26:  punchlines:  Bryan S,  minutes: Brian X

Written by m_conley

January 18th, 2010 at 9:04 pm

Posted in Uncategorized

Notes System: Initial Design

with 4 comments

At the code sprint, we tossed around some ideas for the “Messages between TAs and instructors” feature that Karen asked for. Today, I’ve been brainstorming what I think this feature should look like, functionally.

Feature goal

To allow small pieces of information to be left on various aspects of the course, pertaining to something specific, to alert others to the problems (or good things!), with a timestamp. These could potentially pertain to an assignment, a student, or a grouping, or we could limit these to just one of these types.

Example uses

If students are suspected to be cheating, then the grader could “flag” the assignment for the instructor by leaving a note. Since other graders can also see it, then they can see that this student was previously flagged for cheating. If the student is sick and gets an exemption on part of the assignment, then a note could be placed on the affected assignment for the grader to take that into account during marking.

Can anyone think of other potential uses of this feature?

Where to create these?

Now that we have some idea of how this could be used in a real course – it’s always key to keep the users in mind – we need to think about where in the work flow we would want to create these pieces of information.

While marking an assignment, we should be able to make notes. These would be noted against the grouping, since this encompasses assignments where the students work alone, as well as assignments where the students work together and keeps in mind the idea that one student having a problem can affect all students in the grouping. It also allows us to have notes go against a single object, since a grouping represents an assignment as well as the students working on it.

We should also be able to make a comment about a particular student in general or about a a particular student on an assignment, not from the marking view. Should we also be able to comment about an assignment? This could be incorporated into the viewing of the comments described below.


What about replies to a comment? Should we incorporate these into our feature? I think that we shouldn’t at this time, since the initial idea is for more one-off ideas, but I think that the model should be designed in a flexible enough way such that we can have multiple notes against the same object, which would allow for multiple notes to be left against an object and thus “replies” of a sort without complicating the model too much.

Where to view these?

I propose adding a new tab in the menu for Admins and Graders, with its text being the name we decide upon for this feature. In here, we can display all of the messages (paged in case there are a lot of them?) and have a link to add new ones as well. Would distinguishing the new comments made since last login from the previous ones be useful? You should be able to sort the view. You should also be able to filter it by assignment or by student ID (which would obviously return all comments left against that student, as well as comments left against any groupings it is a member of).


At the code sprint meeting, someone suggested modifying the annotations model for these notes, but that idea was declined since we don’t want to relate these to the code. The conclusion was that we will need a new model to represent these ideas.

The pieces of information that we need to store are: the user who wrote the note, the timestamp from when it was written, the object ID that it is against, the type of object it is against (grouping, student, assignment, etc.), and the actual text of the note itself.


We need to consider how we’re going to name this feature. Several initial possibilities come to mind: Messages, Notes, and Comments. (I actually found all three of these used interchangeably in my notes from the Sunday code sprint meeting!)

  • I don’t like the term “Messages” because it implies that they are sent from one person to another, which these won’t be – they’ll be available for viewing by all instructors AND graders. I do, however, like its implication that these are being shared with other people.
  • The term “Comments” is too close to the ideas of commenting code and the overall comments on an assignment that are shared with the students. I think that a new term is in order to ensure that information is not left in this field that the students shouldn’t see.
  • My favourite is definitely the term “Notes” because it implies that these are small pieces of information, pertaining to something specific. It doesn’t carry the connotation that it is just between specific individuals, so it is much more fitting than “Messages”.

I am definitely open to suggestions on other names or further comments on the names that I have suggested.

Anything else?

Are there any other pieces related to this feature that I haven’t outlined? I look forward to hearing your ideas about the upcoming notes feature in MarkUs!

Written by Tara Clark

October 17th, 2009 at 10:47 pm

Posted in Uncategorized