MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for January, 2010

January 22nd Status Update

with 2 comments

Victoria

Status

  • Completed my first wireframe for the TA Assignment view which I will be calling “Assign Graders”.
  • Came up with some new ideas for this “Assign Graders” view that may or may not be useful to the user.

Next Steps

  • Quite a few wireframes still need to be completed before I can put a report/blog post together for some usability feedback.
  • Will be running my new ideas by Karen in next Wednesday’s UI meeting.

Roadblocks

  • None

Brian Xu

Status

  • Worked on bug #570
  • Started learning writing test cases
  • Request review of code for the #570

Next Steps

  • Finish test cases of #570
  • Find another bug to fix
  • Start to work on the flexible marking scheme

Roadblocks

  • Lack of time

Farah

Status

  • Victoria and I discussed ideas for the new “Tasks” tab at the code sprint
  • Worked on and finished implementing alphabetical pagination for the grades table (this will be helpful when trying to find/enter the grades for a particular student)
  • Started to work on tests for the grades table

Next Steps

  • Continue working on tests and then update my review request
  • Work on the student view for grade entry forms
  • Victoria is going to create a blog post about design ideas for the “Tasks” tab and then I’m going to follow up on that post with a post on development plans.

Roadblocks

  • None this week

Robert

Status

  • Met with UWaterloo user, Byron Weber Becker, to obtain his thoughts and usage issues
  • Worked on one of the bugs [510] for 0.6. I still need to write tests for it for it to properly ship.

Next Steps

  • Write tests for 510 fix

Roadblocks

  • My assignment deadlines and midterms are all thursdays it seems so I’m scheduling when I work on MarkUs to weekends, so I haven’t done much this week

Mike

Status

  • Reviewed the code that was submitted since the code sprint
  • Merged Bryan Shen’s <form> fix for app/views/students/edit.html.erb into 0.6 branch
  • Did some tech support with various team members over IRC, email, and Squad

Next Steps

  • Close a ticket or two if I can catch my breath – I’m thinking #530, and #531 in particular

Roadblocks

  • None

Bryan Shen

Status

  • Set up environment on Ubuntu
  • Updated installation guide for Linux
  • Reviewed some recently commited code

Next Steps

  • Study how to add flexible criteria (controller already there) into the application
  • Get more knowledge of Ruby on Rails

Roadblocks

  • Migrating from Windows to Ubuntu is not so easy to me
  • Didn’t have too much time during the weekdays

Joseph

Status

  • met with Robert and Professor Becker

Next Steps

  • finish off the tests for the bug I was fixing during the code sprint
  • look at the paging issue that Professor Becker reported
  • come up with a solution, and propose it to markus-dev
  • implement solution if approved

Roadblocks

  • My laptop is dead and I do not have sudo on the student computer environment
  • the replacement parts have arrived at my parents and my friend is bringing it back for me this Sunday
  • I’ll be back in business on Sunday!
Status:
-Victoria and I discussed ideas for the new “Tasks” tab at the code sprint
-Worked on and finished implementing alphabetical pagination for the grades table (this will be helpful when trying to find/enter the grades for a particular student)
-Started to work on tests for the grades table

Next Steps:
-Continue working on tests and then update my review request
-Work on the student view for grade entry forms
-Victoria is going to create a blog post about design ideas for the “Tasks” tab and then I’m going to follow up on that post with a post on development plans.

Roadblocks:
-None this week

Written by m_conley

January 22nd, 2010 at 1:52 am

Posted in Uncategorized

Who is Doing What: Winter 2010

without comments

The MarkUs team is meeting weekly on irc.freenode.net #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

Code Sprinting with MarkUs: Plans for the semester

with one comment

It’s Day 2 of the code sprint and the MarkUs team had a meeting this morning to discuss our plans for the semester. Here’s a list of the tasks we discussed:

  • Simple Grade Entry
    • Used for entering grades for labs, tests, exams, etc.
    • Farah worked on this last semester and will be finishing it off
    • The main things remaining:
      • Attaching graders to a grade entry form
      • The ability to release/unrelease marks
      • The ability for a student to see his/her marks for each question
      • The ability to upload/download the grades in CSV format
      • Tests
  • Flexible Criteria Marking Scheme
    • Allows the instructor to specify a description of a criterion and the total number of marks for that criterion
    • The ‘Laval Trio’ worked on this last semester
    • The main things remaining:
      • The ability to grade an assignment using the flexible criteria marking scheme
      • The ability for a student to see his/her marks for such an assignment
      • Tests
  • Notes System
    • Allows instructors and TAs to add notes related to a grouping and assignment
    • Tara and Fernando worked on this last semester
    • Things to consider:
      • Linking it up in the right places
      • Attaching notes to student
      • General notes to TAs
  • “Snapshot”? for grades
    • Currently, after making a change to a mark, there is no way to just undo this change and go back to what the mark originally was
    • Possible solutions to consider:
      • The grader should download the CSV file containing all the grades before doing remarks
      • Automatically take a snapshot every time the grades are released/unreleased
      • Take a ‘snapshot’ of the marks for a particular assignment for a student and include this information in a note
  • TA Assignments
    • Currently, we don’t have a way of assigning TAs to a subset of rubric criteria elements
    • Things to consider:
      • Defining tasks for TAs (and how to assign TAs to tasks and groups)
      • Redistributing the tasks
      • Make the rubric criteria that a particular TA is responsible for stand out in some way
      • Improving the current “attaching graders” view
  • Testing
    • Our current fixtures are fragile
    • Gabriel started looking into the possibility of moving over to machinist last semester
  • Cloning Rubric Criteria
    • We want to add the ability to copy either a subset of rubric elements or all the rubric elements from one assignment to another
    • We should also be able to tweak these rubric elements after cloning
  • Keyboard Shortcuts
    • These will help to save time when marking
  • Annotations for Dan
    • We have a blind instructor at U of T who would really like to use MarkUs
    • We need to figure out how to make the TAs annotations for an assignment accessible to him
  • API
    • Allows instructors to write scripts to automate cumbersome tasks
    • Adding test results
    • Automatically adding marks to a rubric (eg. run tests, calculate a mark based on the number of tests that passed and add it to the rubric)
  • UI
    • There are lots of things we can improve
    • The “attaching graders” view is part of this
  • Tickets

We split the tasks up this morning as well. Here’s the breakdown:

  • Farah is going to finish the simple grade entry feature.
  • Victoria and Farah are going to work on improving the UI. One of the first things they will look at is TA assignments.
  • Joseph and Robert are going to work on the notes system and the API.
  • Brian and Bryan are going to work on finishing up the flexible criteria marking scheme and on testing.

We’re off to a great start!

Written by Farah Juma

January 16th, 2010 at 2:54 pm

Posted in Uncategorized

Some good Ajax sources

without comments

Over the break, I started learning about Ajax in order to improve the table view for simple grade entry. Just thought I’d post some of the helpful sources I’ve come across:

Enjoy!

Written by Farah Juma

January 4th, 2010 at 5:26 pm

Posted in Uncategorized