MarkUs Blog

MarkUs Developers Blog About Their Project

Removing Marks

with 6 comments

Right now, MarkUs lets graders choose a mark from 0 – 4 to assign to a particular criterion on the rubric.  However, MarkUs does not currently allow graders to remove those marks once they’ve been made.  They can change the level, but they can’t flat out remove it.  This problem is filed as ticket #531.

My approach is to simply add a link that allows graders to remove the mark.  Simple as that.  I’ve thrown together a quick and dirty UI mockup – see below:

Remove that mark!

Remove that mark!

It really might be that quick and easy.  In fact, this problem might be ripe for one of my new teammates to sharpen their teeth on. It’ll be a good experience working with RJS, the Rails AJAX helpers, and the Grader View (which is one of my favourite parts of the entire app).  So I’m going to assign this ticket to “nobody”, and see who bites (and who’s reading the blog!).  😀

Written by m_conley

January 25th, 2010 at 5:58 pm

Posted in Uncategorized

6 Responses to 'Removing Marks'

Subscribe to comments with RSS or TrackBack to 'Removing Marks'.

  1. Nice! I was thinking of something very similar. Maybe it’s more intuitive to move that link to the right of the selected/applied level… BTW: I’m reading the blog 🙂


    26 Jan 10 at 12:50 am

  2. […] Wrote a blog post about closing #531: […]

  3. We definitely need the functionality, but I don’t want to add to the vertical space requirements. (I’d actually like to shrink them some more.)

    In OLM we could select the same mark from the list to deselect it. (I.e., 2: Passable ) It wasn’t obvious, but once users new about the feature it worked pretty well.

    I’d be okay with an icon beside the criterion result. Maybe “Clear mark” or “Reset mark” would be better titles.


    29 Jan 10 at 11:54 am

  4. Similar to Severin’s idea, I would implement the button to the right of criteria name. However I notice that if we dont give any mark for a criteria, there will be nothing showed around the criteria name when collapse. Shall we add information such as “no mark” to explicitly tell there is no mark yet?

    Brian Xu

    3 Feb 10 at 12:49 am

  5. I believe we need to modify the result_controller.rb. Since every time you click on a certain criteria it will call the updatemark method in ResultController. I believe we need to apply similar process to remove the mark. Any comment about that?

    Just a quick update: try to modify the update method to save a nil mark, but it won’t allow to save a nil value. But I think the default value is nil, isnt it?

    Brian Xu

    3 Feb 10 at 2:29 am

  6. Brian:

    For your first question, I think that’s associated with these two tickets:

    So yes – the rubric does need some way of making it more obvious to graders that a mark has been made for a criterion.

    Regarding your second message:

    Yes – I believe ResultsController is where you’ll be working in. You’ll want to add a new method that does a delete on a mark for a given criterion on the current result, and that method should also use RJS to generate some Javascript to update the client-side UI to show that this has been done. It’s a little bit tricky, but you’ll learn a lot. Ping me if you have any questions on that.

    Regarding your quick update:

    If you check out the DB schema, the Marks table connects a Result with a particular RubricCriterion. A Mark is given a value – I believe from 0 – 4. If you check, I believe the Mark model validations prevents us from creating a Mark with anything otherwise.

    By default, no Mark exists for a given Result / RubricCriterion. I think this is the state you’ll want to get to – your remove_mark method (or whatever you call it), should *delete* the Mark associated with that Result/RubricCriterion.

    As always, ping me if you have questions.


    Mike Conley

    3 Feb 10 at 6:17 pm

Leave a Reply