Archive for the ‘Status Reports’ Category
- Added test cases to Assignments rspec tests
- Updated Main Controller functional test
- Added Marks Spreadsheets quick links to dashboard & colour-coded due dates
- Make some final visual changes in assignment summaries
- looking over React tables to determine which need a custom sort
- custom sort function for grace credits (sort by fractional value remaining/total)
- small refactoring of last week’s sort functions
- addressing comments from @david-yz-liu and @houndci on PR #1906
- making the compare functions more general; moving some of the parsing work back into table.js
- Fixed up some of the changes with the Tags view.
- Moved the Tags view link up to the sub menu. It was previously located in the sub sub menu. Tags are global in scope as opposed to confined to an assignment.
- Got most of the Results view working. Tags can now be assigned and unassigned from particular submissions. This was done using Ajax to prevent page loads every time a tag is assigned.
- Bug fixes?
- Finishing up the Tag feature.
- Modified existing create function to handle adding a tag from tag view and from individual submission view, (individual submission view will also associate the created tag with the grouping right away)
- Add operation to grab tags not associated with the provided grouping
- Test workflows and fix bugs encountered.
- Modified assignments model, main controller and main index view to display the most ‘recent’ assignment upon load. I mistakenly merged master into my dashboard branch and David asked me to undo the merge and make a new pull request. During that process, however, I messed up my development environment (getting errors) so I am working on fixing that.
- Add spreadsheets to dashboard
- Rearrange elements based on wireframe design
- Pull Request #1878 (last week’s accomplishments)
- Opened Issue #1877
- Pull Request #1892: removed old references to populate_repo_browser
- still addressing some HoundCi comments on that
- added capability for custom sort functions on React Table columns
- fix more tables that don’t sort correctly
- possible write-up on sort behaviour… it wasn’t actually a hard fix and I’m not yet sure if there is enough info there for a ‘significant’ piece of writing
- Modified the Tag controller to allow for tags to be created and for tags to be uploaded.
- Got the React table in the Tags view to display tags that are stored in the ActiveRecord. Also allowed for users to create tags using the Create New Tag dialog.
- Started work on the Individual Submission page by adding in code to display tags that were assigned to a particular submission. Also started working on the ability for users to tag submissions with a particular tag.
- Completion of the Tag view. The React table will have the “Edit” and “Delete” links working as well as the CSV upload and download dialog boxes working.
- The individual submissions view will be fully complete. Users will be able to assign submissions with tags, remove assignments of tags and view the top used tags in the system.
- Coordinated with Nathan regarding the Tagging feature back-end. Started looking into linking the views with the controller.
- Cleaned up view code and continued to add in features that didn’t require the Tagging controller.
- Linking the Tagging controller with the views.
- Have a working prototype of the Tagging feature that involves the simple creation and deletion of a tag.
- Sorting repo files table by revised-by or last-modified no longer breaks the table
- Current path breadcrumb no longer breaks when assignment repository root folder is selected. It was appending the assignment repository folder name repeatedly (e.g. /A1/A1 each time you selected /A1).
- Sort last-modified dates as dates instead of strings
- Fix revision selection
- File Manager view
- I think I have a better understanding of the revision selection problem as described here. I spent a while investigating this. I thought perhaps there was an off-by-one error with the controller using 0-based revisions and the view using 1-based, but now I think revision 0 is just a weird case that *does* exist, but isn’t actually accessible.
- Completed initial prototypes for the Tagging feature views. This includes a new tagging view and additions to the Submissions and Results views to implement the tagging features.
- Created CSS elements for tags and tagging features.
- Improved my proficiency in CSS.
- Getting feedback on the initial prototype and making improvements to it.
- Cleaning up some of the visual elements to make them conform to the MarkUs standard.
- Learned about how the controller connects with the models and views
- Completed dashboard design (sketch and wireframe)
- Started implementation of the new dashboard. I have split the view into two with the list of assignments and grading spreadsheets on the left but I am still trying to change the view on the right through links in the list. Still trying to figure out how the controller links to the view (getting a nil class error)
- Continue to implement the dashboard. Next I will need to implement the functionality t hat determines which assignment to display.
- finished implementing proof-of-concept to create tags associated with groupings, save in database, and retrieve tags by groupings when loading submissions table
- minor revisions to migration files as a result of the code I implemented this week
- opened pull request with migration files and models
- I’m not quite sure what I should do prior to Bryan’s view implementation being merged into the tagging branch. Once that is merged in, I will implement the code in the correct places to allow creation of tags wherever he has created an UI to do so. Also I will implement the code to retrieve tags wherever tags are displayed.
- converting repo browser table to React
- finish converting repo browser table to React
- revised the proposed schema for database definitions upon further research/readings
- implemented two migration files for creating Tags Model and a join table for the has_many_and_belongs_to relationships between tags and groupings
- implemented some code to retrieve tags for each grouping when the submissions table is loaded (hasn’t been tested yet)
- sync up with David/Bryan about my migration files
- implement code to create tags (need to sync with Bryan exactly what information the user will enter for each tag i.e. name, description) etc.
- once code to create tags is implemented, test creating tags and retrieving when submissions table loaded
- revised Dashboard plan based on feedback from Karen and David
- sketched three versions of Dashboard wireframes and chose one with feedback from David
- started implementing the changes (phase one: separate the view with list on the left that controls the details on the right)
- continue implementation of new design
- commit phase one
- Fixed and closed Issue #1720 – Ascending/Descending icons change column widths
- Emailed dashboard plan to Karen and David
- Revise plan based on feedback and design wireframes
- Submitted a new view for issue #1726 (https://github.com/
MarkUsProject/Markus/issues/ 1726). The Flexible Criteria view now has an upload dialog that only enables its upload button when a file is selected.
- Added and improved a Tag view for the tagging feature. This view is not connected to a working controller but has working upload, download, create dialogs and a React table that is currently filled with “dummy data”.
- Submitted a post to the MarkUs blog outlining the tagging feature and upcoming features for it.
- Adding tag functionality to the submissions page and the assignment screen. This will allow filtering by tag and assigning tags to assignments. This will still not be connected to the tag controller.
- Looked over the database schema and wrote up proposed changes to the schema for the tagging project
- Read up on ActiveRecord
- Unfortunately did not have much time to work on Markus due to other course commitments and going out of town for Thanksgiving weekend
- Begin implementing changes reflected by the proposed changes to the database schema
- implement logic to create new tags, query for tags, and display tags next to submissions
- checking out React.js tutorials
- looking over existing React tables for reference
- conversion of table in Repository view to React
Note: I had a hectic sort of week and didn’t put much time into this course; my goal for this week is to put in a minimum of 10h and make up for lost time the following week, which should be less busy.
- closed rspec tests and issue 1701
- started back end investigations for tagging project
- investigated how to interact with database, putting, getting etc.
- grab Bryan’s starter code when it’s ready
- hash out concrete design and schema changes
- start implementing the back end
– Made revisions to grouping rspec test file
– Closed Pull Request #1800
– Write plan for dashboard and send to Karen and David
- Submitted an updated fix for issue #1726 (https://github.com/
- Created a model, controller and new view for the tagging system. This new view can be accessed off each assignment page. It allows administrators to create, manage and delete tags. The view currently has no functionality.
- A major roadblock was learning how to incorporate views into MarkUs. It took several hours to ensure the links and stylesheets all worked for the new view.
- Improving the tag view.
- Adding tag functionality to the submissions page and the assignment screen. From here, TAs can see tagged assignments and can tag assignments with preset tags.
- testing issue #1722
- get a feel for React tables
- begin conversion of table in Repository view to React
- address comments on rpsec pr and resubmitted pr
- submitted a pr for issue #1701 (download all files button not working, include annotations not working for single file downloads)
- address any comments on two outstanding prs
- start working on submission tagging project
- code investigation, how to interact with database
- what steps need to be taken to display table?
- what steps need to be taken to insert tags and associate it with a submission?
- learning more ruby/rspec
- testing issue #1722
- addressing Hound comments on issue #1722 and AssignmentFile spec
- finish testing issue #1722 (i.e. issue #1799)
- get a feel for React tables
- begin conversion of table in Repository view to React
- Submitted a fix for issue #1726 (https://github.com/
MarkUsProject/Markus/issues/ 1726). This issue was a stylistic problem where upload buttons would remain enabled even when a file was not selected. Now, a jQuery script was written that only enables the button when a file is selected. This change was implemented across multiple modal dialogs.
- Started working on the back-end for the new assignment tagging system by creating model and controller Ruby scripts for the tags. With this, a schema was created to illustrate what data needed to be stored and the relationships between the Tag model and other models.
- A major roadblock was understanding how Ruby on Rails stores data using ActiveRecord. This roadblock is still ongoing but the issue is starting to make more sense.
- Getting a simple working model and controller implemented for the Tag feature. Although it won’t have full functionality, it will serve as a starting point for implementing the tagging feature.
- Attended the code sprint in Toronto!
- Fixed Issue #1959 Spreadsheets “Select: All” button doesn’t select all
- Changed spreadsheets to bigger page sizes
- Continue working on Issue #1920
- Expand on rspec for group model
- Write questionnaire for Dashboard usability study
- Attended the code sprint in Toronto and met the rest of the UCOSP participants!
- Fixed Issues #1728 (Can’t upload hidden assignments) and #1729 (Spreadsheet csv shouldn’t require “”).
- Created an rspec test for the Annotations model.
- Continue working on Issue #1726 with Nathan.
- Begin to explore a feature to allow TAs and admins to tag assignments. Currently exploring different options on how this can be carried out. See feature #8 for more information.
- Attended the code sprint in toronto
- worked on my assigned rspec tests
- got my development environment set up
- Finish off issue #1763
- start transitioning from prototype to jquery which is issue #1496
- Attended code sprint in toronto
- finished off first issue
- started working on issue 1726 and 1701
- created rspec test for image_annotations
- address pull request comments on rspec tests
- continue working on issue 1701
- The development environment for the MarkUs Project was setup using Vagrant and Ubuntu 13.
- Submitted pull request #1750 (https://github.com/
MarkUsProject/Markus/pull/1750 ) for a fix to issue #1728 (https://github.com/ MarkUsProject/Markus/issues/ 1728). This issue was a bug that improperly formatted hyperlinks on the assignment dropdown for assignments marked as hidden. To test the fix, several new assignments were created and marked as hidden. The assignment sidebar worked properly for all these new assignments.
- There was some trouble setting up Vagrant and MarkUs on Windows. To get around this, Ubuntu was installed and MarkUs was set up on this environment instead.
- Getting ready for the UCOSP code-sprint in Toronto! Working on new issues and fixing bugs.
- Setup a stable and usable virtual machine running to develop the application in. I had Vagrant running almost immediately and MarkUs shortly there after. However I then noticed that while the application was running in Vagrant there were very long page load times (20+ Seconds). Instead I imported the the VirtualBox machine into Parallels. That improved page load times to about a 1 – 5 seconds on average.
- I fixed Issue #1493 and submitted a pull request. This was a problem with how totals were displayed and updated in the marks spreadsheet.
- I noticed the “total_grade” column is managed in ruby and am unsure why this value is being calculated server side and having to be managed manually when it could simply be a calculated SQL column. I have filed an issue (#1762) in regards to this.
- If Issue #1762 is approved I would like to fix that issue.
- Complete some more tasks/issues. Possibly some of the spreadsheet related items since I now have some experience working with that component in the application.
- Attend the Code Sprint!
- Set up development environment. There was trouble setting up MarkUs on Windows 8.1 so Ubuntu 14.04 was installed and it is now working fine.
- Familiarizing myself with Ruby and Git.
- Work on Issue #1759.
- Fix Issue #1759, test and submit pull request.
- Head to Code Sprint in Toronto!
- Fixed Issues #1746 & #1748. Pull requests have been accepted.
- Determine why some rake tests appear as failing for my environment. Potentially create a couple of issues — depending on their validity — and pick up more issues to tackle.
- Set up dev environment. Have a fix for issue 1730
- submit pull request for my fix
- Set up development environment.
- Read development guideline and other documentation of Markus
- Submit pull request of issue-1735
- More reading and prepare for the Sprint.
- Wait for feedback of the pull request.
- Setting up the development environment. Had some issues dual booting Linux Mint 17 and Windows 8.1 and had to format/repartition my poor laptop 4-5 times (all is well now).
- Reading up on Git and Ruby tutorials
- Reading developer guidelines for MarkUs
- Continue getting familiar with Ruby, Rails and MarkUs
- Get assigned an issue to work on
- Attend Code Sprint!
Alex & Mark
- Solve issue #1456 which is related to SVN repo creation issues (which is a good primer to our main project listed for next week)
- Continue our investigation into how Git has been integrated so far into Markus on the Git branch and assess the contributed code for quality before adding more.