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
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
We are looking to create an asset tracking system to help track information technology resources commonly found in institutions.  This includes both physical assets like a computer or camera as well as things such as software licenses.  A check-in and check-out system is key for this project as well as auditing capabilities of inventory.  Our hopes are that this application will be able to be used in a number of different environments other then just ours.  This project is starting from scratch but we are willing to look at customizing existing applications.
We are looking for a student to continue working on the existing code base and to see about refining some of the following features:


Specifically we're looking to  
*Automated email messages triggered by conditions related to the asset.
* Create a flexible and expandable database with a web front end.
*Reporting tools including general audits of all assets and conditional audits of assets.
* Allow for users to reserve resources.
*Control model for users vs. admins in the system
* Ability to work with LDAP for populating users and access control.  This will give the application the ability to work in a number of different enterprise environments.
*A refinement of the reservation system to include or build on the following features.
* Allow administrators to run reports to help indicate things such as warranty or license expiration as well as who a resource is allocated to.
**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


We have an eye towards developing this application in Rails but, as we are starting fresh we are open to your ideas.
 
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: [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

Retrieved from "http://cyber.harvard.edu/gsoc/?title=Check-in_Check-out_Asset_Tracker&oldid=249"