Check-in Check-out Asset Tracker: Difference between revisions

From Berkman Klein Google Summer of Code Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 17: Line 17:
*A working knowledge of Redmine's internals
*A working knowledge of Redmine's internals
*Understanding of web based security best practices
*Understanding of web based security best practices
Mentor: [mailto:epopko@cyber.law.harvard.edu epopko@cyber.law.harvard.edu]
General Questions: [mailto:berkmancenterharvard@gmail.com berkmancenterharvard@gmail.com]

Latest revision as of 10:27, 19 March 2012

We are looking for a student to continue working on the existing code base and to see about refining some of the following features:

  • Automated email messages triggered by conditions related to the asset.
  • Reporting tools including general audits of all assets and conditional audits of assets.
  • Control model for users vs. admins in the system
  • A refinement of the reservation system to include or build on the following features.
    • More granular control of a reservation's time beyond just a date range.
    • The ability to set up recurring reservations
    • Reservation report pages for users and admins
  • More optimization of the GUI


Skills we are looking for to help complete this project:

  • A solid working knowledge of MySQL databases
  • A solid understanding of the Ruby-on-Rails framework
  • A working knowledge of Redmine's internals
  • Understanding of web based security best practices


Mentor: epopko@cyber.law.harvard.edu

General Questions: berkmancenterharvard@gmail.com