Archive for November, 2009
- Reviewed a bunch of code – it’s looking great, everyone!
- Began working on RIA showcase poster
- Fixed a little bug that prevented C from syntax-highlighting for students
- Review more code – it looks like a lot is about to come in…
- Publish the last iteration of the new marking scheme document
- Worked on the ticket #457 Flexible Marking Scheme – Change marks.rubric_criterion_id to criterion_id
- Worked on the ticket #174 Performance : Index foreign keys
- Identified how should our work in the course be evaluated?
- Submitted the logging System
- Met with Tara for the notes system
- Added a post in the blog with the model that we are planning to use
- Implement the model in rails
- Make a mock up for the modal dialog
- Write standard messages for the logger in the locale file
- Wrote some comments and reviews
- Other than that, same status as last week (I feel bad, because I was unable to make progress)
- Automated testing (completeness 5%)
- Make progress!
- Lack of time?
- Mock-ups for the Notes tab: http://blog.markusproject.org/?p=764
- Waiting on comments on the notes system prior to being able to examine it technically
- Worked on ticket #442 (70% done). The assignment view now offers to change marking scheme. There is a notice when changing marking scheme.
- Worked on ticket #440 (80% done). The objet and table FlexibleCriterion has been created.
- Submitted review requests for all of the migration files needed for simple grade entry
- Updated my tickets
- Finish the creation form and work on tests for the form (my goal is to submit review requests for these two things by next Friday)
- Once that’s done, the instructor Properties view should be straightforward and then I can work on the Table view
- Published our marking scheme (for the UCOSP, not MarkUs) on the blog post last Friday;
- Sill improved (a little) my job on ticket #400 – Results Functional test is empty;
- Completed ticket #443 – Marking scheme tab but it still has to go through the review board along with the next ticket…
- Almost completed #444 – New Marking Scheme view that only regards the admin stories.
- Finish #444 and post a review request that combines #443 and #444
- Post a review request for my ongoing work with #400
- There was one for a short lap of time, but it’s all clear now thanks to the markus-dev list (i.e. Severin and Mike C.)
This is the model that we are planning to use for the notes system.
We are going to relate the notes to the users that created them and for the groupings that they are assigned to.
Since we are focusing first on doing notes only for groupings the type column won’t be used, but if time permits we will use it to be able to add notes on submissions or assignments.
Depending on what we decide on foreign keys, we will have to add indexes for user_id and groupings_id to increase performance.
I am proposing a possible aggregate view of all notes to be placed on a new tab called “Notes”, displayed to the right of the existing tabs in the list. This tab would only be visible to graders and to admins.
Next to the header on the page, we would put an icon allowing the user to add a new note, which would bring up a modal dialog similar to the ones that Fernando is going to mock up. I picked this location because on the Users pages, there is an “Add New” link in small text next to the title.
The main attraction is the table with the notes in it. After playing around with a couple of more table-like looks, I settled on this one that looks more like messages. There are three columns in each row. The first indicates data in the following format:
[username] on <b>[assignment short identifier]: [comma-separated student usernames]</b>
<small>[full date] at [time]</b>
The second column shows the full text of the note and the third column shows edit and delete icons, if the current user has the privilege of doing so. (Admins can edit/delete all notes and graders can edit/delete notes that they created themselves.)
Each row will be highlighted in grey when hovered over.
Using the “on” method of indicating the object the note is for makes this view much more flexible when we add further objects that we can note on other than just groupings. For a grouping, we would show the assignment short identifier and all of the student memberships. But for an assignment, we would simply show its short identifier or for a student, its username.