Refresh is designed for use by (student) organizations that regularly host events, whether they be social, philanthropic, sport, etc. The target types of organizations include Class Board, fraternities & sororities, senior societies, and so forth.
One instance of Refresh is intended to be used by a single organization. The organizations members make accounts on the page, where they are users (there can be one or more administrators per page). Administrators can put up events that have occured, and users (as well as administrators) can provide feedback for the events, in the form of ratings or free-response text.
The intent is for organizations to have a log of what their members think of events, be able to identify what their membership prefers, why they prefer it, etc. This app could be expanded to become a more fully featured log in addition to its feedback-gathering capabilities: adding image uploading would allow the administrators to provide something of value for the users, and more detailed feedback fields (as opposed to just ratings and free form text) would provide more valuable data. There could also be more community elements added by facilitating interaction (in the form of replies, rating feedbacks, discussions) between users.
Below is a mostly comprehensive list of the features you'll find
In no particular order:
- Custom rake command for creating the first admin (rake promote_admin)
- Provided default admin account. Email: admin@cis196.com Pass: administrator
- Events & Users index listing
- Event edit / delete function only available to admins
- Make admin / remove admin function only available to admins, and not on yourself
- Much of site is Bootstrapped to make it visually appealing
- Full use of Devise gem for user management
- Use of sendgrid gem for sending emails: when a new event is posted, all users get an email
- All Event Names and User Names are hyperlinked to the corresponding Show pages
- All users have ability to "Add Feedback" from an Event's page
- When a user adds feedback, relevant user & event statistics are updated and saved
- Search function initially searches for Event Names, User Names, and Review Text
- Can filter down what you're searching for after performing an initial search to one or two of those cateogires
- User profile pages display stats, as well as all the reviews that they've written
First Assignment
I developed a schema for two tables that will eventually be key to this site: events and reviews. Events have 5 components: name, rating, attendance, thumbs_up, thumbs_down. Reviews also have 5 components: user, review, rating, thumbs_up, thumbs_down.
Each schema is set up with a controller, model, index, and new action device. This allows the data to be both viewed and added to. The homepage setup has links to each of these respective pages.
Second Assignment
I added edit, show, and destroy functionality for each of the two tables I created for the last assignment. There are now links corresponding to these actions found when viewing the index page for either table.
Third Assignment
Added a users schema so we can have users login using devise (only initially implemented index and new). Incorporated devise onto users. Added a navbar like we did in class. Edited the devise new/edit views to incorporate the name field. Also created my own show page to display the users that I've already made.
Validations added: name can't be blank and must be unique, password must be between 8 and 12 characters long.
Fourth Assignment
Added a "creator" and "creator email" field to the event object. Added a temporary "notify email" to the review structure. Eventually, events and reviews will be linked up and this notify email will be unnecessary.
Added the send grid add-on to the application. The add-on is used to send an email to the notify_email field of reviews when someone posts the review. Local version works. There's a bug in the production version that throws an error when you send an email. Haven't been able to resolve.
Fifth Assignment
Added the use of 4 queries to the app.
"Most Popular Event: " - event with greatest attendance (order by, limit)
- Listed by default in the index events page (events_controller.rb)
"Thumbs Up Reviews" on reviews index (condition)
- Listed in index reviews page (reviews_controller.rb)
"Show 5 most recent reviews" button on reviews index
- Clicking will bring up a page with the 5 most recent reviews (order by, limit)
- new method in reviews_controller: index_recent
- routed it as well
"Sort by rating" button on events index
- Allows sorting of the events (order by)
- Reloads the page with &sort=rating GET param
- events_controller.rb handles the logic here
Sixth Assignment
Progress towards final product: added a search function to the navbar. This allows users to search for events that have happened in the past, displays a list of matches, and upon click navigates you to that event's page. Not as substantial an addition as I would have hoped to accomplish by this marker, will be sure to ramp it up soon.
Note that, for the seventh and final assignment, I scrapped most of what I had done to this point and rebuilt everything you see in the final product (re-used some bits of code).
First Assignment
Spent hours trying to get rails working despite initially having sufficient versions of ruby and rails installed. rails generate was not working, and was having various issues with installing gems (e.g. sqlite3 and pg). Attempted full re-install of rvm, ruby, and rails. Was having issues with re-installing rails until I added to the environmental variable ARCHFLAGS and manually set some paths: sudo env ARCHFLAGS="-arch x86_64" gem install rails -- --use-system-libraries --with-xml=/usr/local/Cellar/libxml2/ . The issue seems to be OSX 10.10 specific.
Second Assignment
One bug I ran across was the use of review_path versus reviews_path. reviews_path is coded to generate a link by appending a dot as a delimiter (e.g. path/to/link.5) as opposed to another slash (e.g. path/to/link/5), as review_path does.
Also had a minor issue with using the rails :delete command for destroying. Apparently the production environment variable (config/environments/production.rb) config.assets.compile must be set to true, otherwise the destroy process won't work when deployed on heroku. Source: http://stackoverflow.com/questions/26697251/rails-apps-destroy-delete-method-is-not-working-on-heroku-but-works-in-local-ma
Third Assignment
Initially forgot that I needed to add a "gem 'devise'..." line in Gemfile -- wasn't sure why bundler wasn't installing devise.
Had an issue getting devise to work on production...realized I forgot to run heroku run rake:db migrate
Fourth Assignment
Didn't have explicit instructions for how to add the creator/creator email fields to my events; was good spending some time in the code without guidance. Note: found out that I needed to run "rails generate migration add_fieldname_to_tablename fieldname:string" in order to add another field to the model.
Fifth Assignment
Implementing the first two queries was straightforward - very similar to methods that were shown in class. For the second two, I did some additional work. For showing the most recent reviews, I created another page associated with another method in the controller. To make this work, I had to add a collection to the reviews resources to allow another view to function. For the fourth query, I added a specially formed button via HTML form that includes a hidden value for the sort parameter. I added logic to the events controller to act appropriately.
Sixth Assignment
Had some null pointer issues because of my edits to index. Made the events/index erb take it into account by checking for a nil @pop_event variable.
Seventh Assignment
Bootstrap was a new experience for me. Surprisingly easy to use - can't wait to apply it to other small projects that I might undertake. Sometimes it was difficult forcing myself to figure out how to use Bootstrap to get something done (centering, etc) as opposed to reverting to raw HTML or CSS coding.
Throughout production, I was fortunate to never experience any problems that I wasn't able to solve by simply reviewing documentation or researching online to find those who had experienced similar problems.
refresh-application.herokuapp.com