Application Tracker: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 22: | Line 22: | ||
We envision this being written in Rails, and are open to it being a plugin to an existing application (eg. Redmine) or a standalone application altogether | We envision this being written in Rails, and are open to it being a plugin to an existing application (eg. Redmine) or a standalone application altogether. We are not entirely beholden to Rails as the implementation language, though we do have a strong preference for it. Put it this way: If we do not get a qualified applicant to build the application in Rails, then we're willing to consider building it in something else. | ||
Your ideas are GREATLY appreciated! |
Revision as of 15:25, 23 March 2010
Basic tool requirements:
General
- Create a database of profiles for people interested in applying to open Berkman positions,
- Accept application materials – CVs, cover letters, other various attachments/files including links and multimedia.
Administrators / decision makers
- Can manage job listings,
- Have the ability to report on candidates and the materials they've submitted,
- Can classify and download all of a certain kind of file (eg: all CVs, or all proposals, or all letters of recommendation, etc.),
- Are able to download all materials for a specific candidate (eg: get all of John Smith's application materials),
- Have the ability to send responses to applicants individually and as a group (eg: when a position has been filled, email all other applicants of the change in status),
- A basic "workflow" to track decisions and where an applicant stands in the process.
The applicant
- Can manage their profile and complete it incrementally,
- Can apply to multiple positions and tailor their application/letters/files to each application,
- Allow non-applicants – primarily people submitting letters of recommendation on an applicant’s behalf – to submit materials that would link to the applicant’s application
We envision this being written in Rails, and are open to it being a plugin to an existing application (eg. Redmine) or a standalone application altogether. We are not entirely beholden to Rails as the implementation language, though we do have a strong preference for it. Put it this way: If we do not get a qualified applicant to build the application in Rails, then we're willing to consider building it in something else.
Your ideas are GREATLY appreciated!