Implement the lost password view controller from the login screen to allow for a lost password recovery.

The current Lost Password link at the bottom of the login view takes the user to a blank view controller and has no features to actually recover lost passwords. This is not the desired functionality for this feature. The view must be populated and appropriate calls to Firebase to actually allow the recovery of a password.

Allow students in the list to be deselected when they are no longer a part of bean count.

When the user is in editing mode on the student table view, allow the user to select or deselect students on the bean count app as they enter or exit bean count. This data should be uploaded to Firebase such that the change is reflected on other devices.

Concurrency errors cause the student table view controller to load before any information about the user selected location is entered.

Need to load the location during login. Load the user's selected location from Firebase and then load that location's data. This must be done before the app segues into the student table view.

In the student table view, when editing the data, the settings button remains visible. When the table view begins editing, the button should disappear.

Currently, if logging in to an account that has no selected location or, for some reason, the account settings don't exist in the database, the app will crash.

The fix is to check if the values exist. If not, respond appropriately.

All images need to be resized to the size they will be used at. I believe that for the moment, all images are in 24p x 24p. All images need to be checked and resized to save space and optimize performance.

Implement the add student button that appears when the student table view is in editing mode.

Currently, the add button has no associated action. It should instead open a new view controller that has the fields appropriate to defining the values for that student. For now, just the student name.

After the user has added a student, which is only possible in the event they have a location currently selected, the students information should then be uploaded into firebase under the current location.

Each student should have a unique ID that defines them, as well as their name and current location in bean count. A deleted student should then be marked in the database as deleted.

After adding a student, the student should be able to be deleted. This will allow students who drop, etc. to be discarded. The bean count numbers of the others should remain unchanged.

In the editing mode, the user should be able to swipe right on a student in the table view and select the student for deletion. This marks the user for deletion in the database and ensures the data will not be displayed.

As an extension, the user should also be able to delete all the students in the current list. This marks them all for deletion.

Add the ability to view the entered information about a student. When the student is selected in the table view, it should take the user to another view that displays the information entered in the tags when creating a user. It should also allow editing.

Need to load the students in the current location list and populate the student table view with them.

Download the list of students for the current location. The students marked for deletion shouldn't be loaded and the remainder should be loaded in bean count order. They are then loaded into an array for displaying into the table view.