gorel / purdue-ride-mapper Goto Github PK

When user registers or activates, the site either needs to redirect or inform the user about the corresponding results

We need to find an easy-to-use API for GeoCoding: translating String locations to a pair of coordinates representing the latitude/longitude of that city.

Very common locations should be hard-coded into the server for performance reasons and to avoid unnecessary calls to the GeoCoding service.

Users will register with a valid *.edu email address, as well as their full name
The server will send an email to the user to verify their account
The user will not be able to view ride listings until their account has been verified
The user will become verified once they click the email link

The registration and logic forms need to have built in verification to make sure the data being sent is in correct format and completely filled out before submitted.

When the user finishes filling out the create a listing webpage,the information will be stored into the database.

We need to do the following to the server:

1. Redirect the current website from /var/www to the repo.
2. We need to install git on our server and check out our repo.
3. We need to make a script or research on how to have our server auto-update when changes are made to the repo. (live updates).

We should come up with a rough mock-up of our database tables. Since we are working on different aspects of the project, I think it would be great for us to work on common data structures. Here are the database tables I did for email verification:

Feel free to build upon that. Of course, everything is still tentative. We should combine our ideas during the meeting on 2/5.

The way the navigation pages are designed, all modules should be accessed via the 'content' div within index.php. Directly accessing other modules might lead to security issues. Need to standardize how pages are being accessed.

Given a list of RideRequests and a RideOffer (or a list of RideOffers and a RideRequest), determine a matching algorithm to determine if a pair of students should carpool together.

If any user forgets his or her password, a mechanism should be in place for resetting the password, possibly via a password reset link.

We need to install mysql onto the server in preparations for designing and implementing our database for our webapp to interact with.

Once the user is logged in, they will remain at the home page. From there they should be able to click "list a ride" or "find a ride" which will take them to a new webpage with a map, options to search, create, etc. We need this to be pretty! This is our most viewed and showcased page on the website.

The matching algorithm works! Now make it work better.

We need a way to store the RideRequests' and RideOffers' source and destination in the database. I would highly suggest including both the String location name and the latitude/longitude of each entry in the database. This will make lookups much faster so we don't have to keep sending requests to whatever GeoCoding API we decide to use.

A system should be put in place that requires anyone who registers for the site to verify their *.edu email address before they are allowed to view any ride requests or offers.

All automated outgoing mails should be sent from localhost.

If certain ride offers or requests seem to be duplicates, “spam,” or inappropriate, I want to be able to delete them from the list of available rides

Emails sent from the server (i.e user sending a message to another on the rides list) should be more informative to facilitate communication between users on their own