Project Description:
Request System We are looking for a Ruby on Rails developer to build a module for a Rails App where users can make submit requests. We will provide the a base project that includes two user roles, admin and user. Project will also include Twitter Bootstrap CSS to use for the UI and jQuery. USER ROLE 1) Create a request The user has the ability to fill out a form and submit it. The data gets stored in the database. The fields are: - Phone number (text field) - Request type (select drop box with options: plumbing, ele ctrical, other) - Details of request (textarea) - Photos (file uploader. user is able to browse computer for image and upload. User has the ability to ADD ANOTHER PHOTO, creates another file upload field. max 5.) - Permi ssion to enter. (2 radio buttons: yes, no.) Other Notes: - Request type needs to be a separate mo del, with a belongs to/has one relationship to requests. A UI is not required for managing request types, simply adding the data to the seed file if sufficient. - Photos should be saved to Amazon’s S3 service. - Refer to screenshot provided. - You do not have to stick to the interface provided for uploading photos. You may use any ruby gems that help get the job done allowing for multiple images to be uploaded 2) View History Users need to be able to view a list of all their submitted requests in order by date submitted. User can click edit request to see the full details of that request. - Refer to screenshot provided. 3) Provide Feeback When the request status is marked as completed (by the admin), the user should be able to a provide feedback by selecting a satisfaction rating. - Refer to screenshot provided. ADMIN ROLE We require backend functionality for all CRUD operations for managing requests. The administrator can see all the requests in a list with the following columns: - user name - user email - phone number - request type - status - rows with a status of unread should be highlighted, similar to unread messages in an email system. The administrator can click any request to see the full details of the request - the details page has all the submitted data plus the ability to update the status of the request - Status should be a drop down select box with: unread, pending, complete, rejected - Statuses can be saved as strings (force lowercase), relationship is not required Technologies we require you to use: - Sass or Scss - Haml templating language - Rails 3.2.7+ - Ruby 1.9.3 - jQuery + any plugins necessary - MySQL
Additional Project Description:
12/11/2012 at 6:25 EST
** Formatting of the description is being compacted. Please reference the PDF attachment for the full description**
