Skip to main content

NSERC USRA position for CS undergrad

Student will contribute to the development of a web-based front end for a database and will recurrently test and maintain the site. This position will involve learning about ontologies and knowledge engineering.

1) Test existing site, a web-based front-end to a MYSQL database of rhetorical figuration. 
2) Contribute to the ongoing development of the site, from technical, functional, and aesthetic perspectives. 
3) Expand the capabilities of existing site (including the incorporation of a wiki and a blog). 
4) Tasks will include: 

  • Updating and writing documentation of program development and subsequent revisions, inserting comments in the coded instructions so others can understand the programs. 
  • Updating and writing computer programs to handle specific jobs, such as storing, retrieving and displaying data in multiple 'views. 
  •  Repairing or expanding existing programs to increase operating efficiency or adapt to new requirements. 
5) Consult with subject-matter experts, managerial, technical personnel to clarify program intent, identify problems, and suggest changes. 


1) Strong programming and testing skills.
2) Familiarity with databases (especially MYSQL and RDF)
3) Able to work independently and with a team.
4) Design training and sensibilities an asset but not required. 
5) Experience with ontologies (OWL, Protege) an asset but not required.

Note for co-op students: If you apply after the co-op deadline, you must check with your co-op advisor that can still use the USRA as your co-op term. If you can proceed with the USRA, you must ask your advisor to remove you from JobMine.


Chrysanne Dimarco 
Voice: (519) 888 4567 x34443
Email: cdimarco AT

Randy Allen Harris
Linguistics, rhetoric, and communication design
HH247, x35362


Popular posts from this blog

Enrollment caps have been restored for CS courses

As per the course selection policy, enrollment caps for all CS courses have been returned to their actual class size. If the class or section is full then it means that you will need to wait for another student to drop it. You have until 11.59 p.m. on Monday May 14 to add courses.

The following courses still have waiting lists and department consent applied so you will NOT be able to add these courses.

CS 454CS 458CS 486CS 488CS 492

Course enrollment for Spring 2018

Appointments for course enrollment began on Monday 26 March and open enrollment begins on Wednesday 28 March.

For students trying to add CS courses, we encourage you to review the course selection page.

In Computer Science,  we drop the enrolment caps by approximately 15% of the total enrolment number for the course to give advisors room to handle special cases. We will return the enrolment caps to their actual size in the second week of classes after we have had time to deal with the special cases. This will occur on Friday, May 4, 2018, (we don't know the precise time) and remaining space will be available on a first-come-first-served basis only if the section isn't already at its enrolment total. WHAT IS A SPECIAL CASE?
1. Students who selected courses but something went wrong because of: enrollment capacity in a course **a time conflict **an academic enrolment block was applied after course selectiondropping or failing a course after course selection** Please re…

CS/Data Science/Digital Hardware option transfers NOW OPEN

The CS Undergraduate Advising Office has opened applications for CS transfers for Fall 2017. The online application is available at will be open from Tuesday, December 5 until Sunday, December 31, 2017, at 11.59 p.m.

We're accepting applications for:

Transfer from Math to CS - at a minimum, must have taken CS 136 or be taking it in Fall 2017.Transfer from CS to BCS (Data Science) - must have taken STAT 231 or be taking it in Fall 2017.Transfer from CS to CS/Digital HardwareAdding a Joint CS to an out-of-faculty planTransfer from outside of Math to CS (pending approval from Math)Answers to common questions about the transfer process can be found in the CS FAQs (particularly #2 and #151).