MarkUs Blog

MarkUs Developers Blog About Their Project

Archive for January, 2015

Status Update – Jan 29 2015

without comments

Christian

  • This week
    • Figured out what was going wrong with displaying remarks to markers
  • Next week
    • figure out why the save button was deleting marks and fixing that

Peter

  • This week
    • Fixed issue-1760 – Converted Student Interface’s marks spreadsheet table to React.js
    • Working on #1974: Add “Bonus” columns to spreadsheets
  • Next week
    • Work on issue #1974
    • Potentially work on #1704: Warn before browsing away whilst uploading spreadsheet marks
  • Others
    • It’s my first time working with React.js so any feedback on implementation would be appreciated

Paymahn

  • This week
    • Finished off #1795. PR still hasn’t been merged but I’m confident it’s done.
  • Next week
    • Start working on integrating MathJax. Will be mostly investigative work and maybe some playing around.

Ryan

  • This week
    • Finished the first iteration of text annotation for specific text selections
      • implemented it by using javas execCommand function
      • this presented several new issues, including breaking original text selection method
      • decided it would be best to redo the highlight function and add classes to the text nodes between the end and start column then split the end/start into two spans, one to leave plain the other to highlight
    • fixed up the way the column offsets were calculated when there were multiple spans in the line
  • Next week
    • I need to finish implementing the new highlight method
      • all that’s left is to clean it up and handle a few edge cases.
  • Problems
    • struggled to parse all the DOM nodes, specifically finding the applied styles

Maryna

  • This week
    • learning respec (BDD, Red/Green testing, basic tests, built in matchers, stubs vs mocks, fixtures and factories
    • examined present markus code
      • Looking at models and associations and attributes to understand DB structure
      • Write the tests for calculate_collection_time and calculate_grouping_collection_time to close ticket #218
  • Next week
    • to continue working on assigned tickets (adding new tests to some implementations)
    • to start looking into translating existing rake tests into RSpec
  • Problems
    • understanding the reasoning/meaning behind some of the code
      • assignment.latest_due_date + hours_sum.hours and hours_sum is always 0. Type casting?

Josh

  • This week
    • NA
  • Next week
    • NA

Written by Paymahn Moghadasian

January 30th, 2015 at 12:28 am

Status Report – Jan 23 2015

without comments

Christian

  • Last week
    • Confirmed existence of #2014
    • Refactored a bit of the remark display in the results controller
    • Made old marks populate the marks fields when remarking assignments (issue 1975)
  • This week
    • Fix issues 2014 and 1869

Maryna

  • Last week
    • worked on issue 76: Disallow non-AssignmentFiles option in Assignment Properties. done and pushed. The major challenge: work on the front end (styling). Had to learn the basis of jQuery to make options pop up in the right places.
    • learning RSpec from the scratch by video tutorials. Reading report provided by one of the students who worked on Markus previously. So far so good.
  • This week
    • review the RSpec tickets assigned by David and find the easiest one to start with.
    • If I would require more time to learn RSpec, my plan is to find some unsigned issues that I could work on in the meantime.

Ryan

  • Last week
    • worked on getting the text annotations to display on only the selected text and not the entire line
    •  managed to get the start and end columns saved into the database while handling a few edge cases
    • made progress getting the data back out of the DB and to the client side.
  • This week
    • Finish off annotations.
  • Having trouble with
    • working with bare bones JS to be consistent with the rest of the annotation class and keep the client side processing to a minimum
    • staying awake after experiencing jet lag and getting back into the swing of things
  • Addendum
    • It turns out that not all of my changes were committed to github, I would assume due to my own user error. It will put me back at least a few hours but I should be able to redo the work and meet my goals regardless. I’ll consider this a lesson learned.

Paymahn

  • Last week
    • Fixed issue 1917. There was an issue with links in the dashboard for spreadsheets and assignments going to settings instead of what would be expected
    • Fixed issue 1884. Flexible criteria could not be downloaded. This was happening because the client was making a POST instead of a GET
    • Worked on issue 1795. The error message for criteria created with a duplicate name was awful. I’ve gotten the message fixed but this broke some tests. I’m in the process of converting the broken tests (and their respective files) to RSPEC
  • This week
    • Looking to finish off issue 1795 (third bullet point above)
    • Will start investigating my project
    • Will need to learn javascript (I’ll probably do some tutorials or something and incessantly annoy Ryan with questions)
  • Having trouble with
    • RSPEC doesn’t make sense (maybe I can’t find the right docs?)
    • Reading docs on relishapp.com
    • Specifically trying to understand how to properly use helper methods for the tests

Peter

  • Last week
    • Learning react framework – tutorials, studying implementations in codebase
    • Updating Student Marks Spreadsheet Table to React (Issue 1760)
  • This week
    • Complete updating Student Marks Spreadsheet Table to React (Issue 1760)
    • Add Bonus Column to Spreadsheet

Josh

  • Last week
    • few more rails tutorials, began (re)familiarizing self with vagrant, bash, virtualbox, etc
    • Not much substantial yet, catching up on classes and stuff
  • This week
    • Begin research/work on #1804 (refactoring Flexible/Rubric criterion models)
    • If possible, begin on issue #1973, but that’s probably a low priority feature atm, and 1804 will likely take at least a few weeks given how little I know of Rails.

Written by Paymahn Moghadasian

January 23rd, 2015 at 2:08 am

Winter 2015 Project List

without comments

1. Spreadsheets improvements (very large)

  • Convert tables to use React
  • Outstanding issues (ordering of columns is still a problem)
  • UI improvements: Anchoring the first column for better horizontal scrolling

2. CSV upload/downloading

The semantics of the different uploading features is varying and unclear.  We especially need to take a close look at the uploading of data in to the spreadsheets, groups, and graders views. Working on this project will require a deep understanding of the operation of each of these uploading functions, looking at the database and repository operations, and documenting the behaviour in the help system.

The other area where CSV uploading needs improvement is that we sometimes encounter performance problems where Apache seems to time out.

3. React refactoring (smallish)#1696

In the past two terms, we have converted tables to use the React library.  As we near the end of this process (spreadsheets are the last ones), the code for the tables could use some refactoring to simplify it and pull together common functions.

4. Get rid of the rest of Prototype #1496 (small)
We have slowly been removing all the Prototype code, and replacing it with JQuery. Aside from the tables that still need to be converted to use React, there are still a few places where Prototype has not been fully replaced. This would be a good project for a student with an interest in learning (more) Javascript/JQuery.

5. Fixing issues with and improving the remark system #1933, #1869, #1975, #1976

We encountered some bugs with the remark request system, and have some feature requests. This will involve the remark request view and the marking scheme models.

5. Git backend #1698 (large)

Alex worked on the git backend last term, and is planning to finish it this term.  The main piece that is left is incorporating authentication so that students can use git directly.  He is planning to work on it again this term.

6. Rails 4.2 upgrade

A lot of work has been done to upgrade MarkUs to use Rails 4.x.  There is still some work remaking to complete this upgrade. This project would be a great one for students with some understanding of Rails, and have an interest in how the Rails framework works.

7. Rspec tests (large, but an ongoing effort)
This summer saw a major effort to change to Rspec tests.  In the fall we were successful in getting all students to write some Rspec tests, and Kuba also spent the term refactoring and testing the Assignment model. A continuing goal is to have everyone on the team write some Rspec tests. It will be a good way to really learn what the models and controllers are supposed to do, and will move the project forward. We plan to set aside a few hours at the sprint for writing tests. There are some outstanding Github issues related to missing tests that can easily be closed with some work.

8. Improve seed data for the development environment

In the dev environment, there is data to populate the data base with users and assignment submissions.  This seed data helps with manual testing and understanding how the system is supposed to work.  We need to increase the size of the seed data to include more students, more assignment submissions, and to increase the diversity of initial scenarios such as different due dates for submissions that affect more of the system.

9. Summary page of all the marks for all students (smallish)
There is currently no view that combines marks from all of the different assignments and spreadsheets. This table would look a lot like the Submissions table or the Summaries table, but would have one column for each assignment and spreadsheet. A new feature would be a way for the administrator to specify a weighting for each piece of work to produce a total. (Good for someone not familiar with Rails.)

10. MathJax support for annotations? #285 (medium?)
It would be nice to be able to use math symbols in annotations. The MathJax library seems to be what we want, and some work has been done on this.

11. UX Refresh of the submissions table (Includes #75) (medium)
We haven’t taken a serious look at what is in the submission table for a long time. For example, we probably don’t need the “can begin grading” field. We would also like to be able to show the grader(s) for each group.

12. Section due dates don’t work #1676 (small)
Some courses would like to have a different due date for each section. This feature seems to have numerous problems with it. There is also a proposal to change the UI for how sections are added.

13. More flexibility in the marking schemes

There are lots of ways in which the two available marking schemes could be improved.

14. API improvements

It would be nice to make the API more powerful so that we could take more advantage of the API for automated operation.  This will also involve writing some scripts and consolidating scripts that interact with the API.

Written by Markus

January 13th, 2015 at 1:23 pm