ritstudentgovernment / bikeshare Goto Github PK

When the user tries to register without supplying a phone number, there is a very generic and unfriendly error, and not the expected validation error.

The nav bar has been set to use identicons, which provides a unique picture based on the user's email address. All other uses of gravatar should be updated to use identicons to keep the site consistent.

Mailings need to be sent automatically:

• periodically after bike is overdue
• when there are pending charges
• when charges are resolved

The checkout UI should show the last person who had the bike.

In the user's account, they should see a status bar indicating how much time they have until their rental must be returned.

The username field is used as a unique identifier, but the system is allowing duplicates. Don't allow this.

It may be valuable to users if they could schedule reservations. Given the system's high demand, it's often challenging to get a bike. Are there any stats on how many students walk into Gleason Office but get turned away due to no bikes being around? Or perhaps this could be determined from analyzing web traffic (bounce rate for the racks page). Those numbers may give us insight into how useful the feature would be.

See http://blog.stevensanderson.com/2008/09/01/prevent-cross-site-request-forgery-csrf-using-aspnet-mvcs-antiforgerytoken-helper/

Commenter avatars should be displayed the same as they are on the mechanic/maintenanceDetails page.

When a user has logged in for the first time, the application should create a new user account and direct them to accept the legal agreement to register.

Currently, the textbox for entering the name is highlighted in red when a user is invalid. There should also be a popup explaining why the user can't be given a bike.

Locks and keys should be able to be tracked through the application.

• Track each lock maintained by the program
• Field for missing
• linked to current or most recent bike
• field for date-last-seen
• Admins can easily add new locks to the pool
• Mechanics can easily maintain, pull offline, put online, and reassigned
• checkout person can report locks as lost, stolen, or damaged
• lost and damaged locks can be associated with a charge to the user.

If an image is too large, it should be cropped automatically to keep the layout reasonable.

Content should shrink or disappear to accommodate smaller screen.

On MSSQL, there is a conversion error from datetime2 to datetime. On NPGsql, default value for dates is being stored, instead of inputted value.

The decision to store the hours of operation for bike racks as integers and strings was horribly ill-conceived. There needs to be a better way to store that information.

The listing in the checkout UI does not show unavailable bikes for entering maintenance issues.

There should be buttons that create popups explaining the functionality and policies of the bike share program.

Checkboxes should also be close to the bikes.

Checkout page should display message indicating whether the checkout was successful.

This is critical to the site being useful.

Every day, site administrators should receive an email report that includes a list of overdue bikes, including rental date, username, user first name, user last name, user phone number and user account balance.

object not set to an instance of an object error.

There should be a lock icon with a rollover tooltip explaining that institutional authnames can't be changed.

• There is no hRule underneath the heading
• The cards should display an image of the rack.

There should be an email every time a user rents a bike, and a few hours before a bike is due. sgsvcs should be emailed every time there is a charge.

When the user clicks login, there should be a dropdown with the login form. That has the benefit of training users to know how to use that dropdown, as well as cutting out a step in the process of logging in.

The checkout person is needing to log in again periodically because the session is timing out. Session limits need to be set to a more reasonable limit to prevent issues with checkout.

Users should be able to choose a first and last name.

Many forms are using the model's property name, rather than an appropriate label.

The pagination is broken for the user listing.

Don't rely on Issues pane.

Consider adding a warning popup within a month of registration expiring.

Some cards don't have correct panel styling applied. Other times, panels are offset inappropriately, making it look like there are invisible panels.

When submitting an issue report, a new maintenance issue should be immediately opened.

• checkout person should be able to decide whether bike is to be taken offline or not.

As a site administrator, I need a way to generate excel reports of all of the information available for certain aspects of my site, including:

• All checkouts
• All bikes
• All bike racks
• all users
• all inspections
• all maintenance events

The new charge modal should use the same format as all other modals.

Display stats in a single place for the site. Include things like:

• bikes available
• bikes in the system
• total checkouts
• total unique users
• user's lifetime checkouts
• user's current balance

It would be helpful if each bike in the list has the current renter as well as the date it was last checked out.