Our user page has three sections which you can find on our slides/report for project 3. We need to implement this UI using HTML and CSS so a user can travel between their home, schedules, and settings. This issue doesn't need to include a complete finalized version of each page, but at least a prototype of each with links to traverse between them.

When things go wrong on different pages of the website an error code and message needs to be displayed. The exits code table of the database is for this, all areas where something goes wrong needs an appropriate error code attached for displaying to the user. This will also involve graphically displaying these errors on the correct page.

This function will cut the camera's recording into 5 minute chunks.

Implement the process that occurs if a recording reaches 15 minutes in length. This is detailed in past documents we have made for the project. The basic idea is queuing the clip for deletion once it has uploaded and sending extra alerts to the user.

This will be implementing the neutral, caution, and alert states of the camera. The previous functions already basically do everything, these states are simply to organize and streamline the cameras processes. This can be implemented early on or later.

Involves implementing an alert system that will notify the user at their email and or sms when a ping from the camera system is received. For this issue actually receiving the ping from the camera system is less important. What's most important to implement is sending an email and text message to a given user.

This is so information stored in the database for a particular user is needed by the system. This includes things like username, cameraID, and scheduling information.

This just involves turning recording on and off, and setting up a folder for recordings to be stored on the Pi.

We need a UI for our homepage that talks about the project and our goals. As well as a top bar with links to either login or register. This should be an easy page to implement and is mainly a problem of aesthetic, trying to make a nice looking home page.

On our registration page I've noticed on some screens it is the wrong size. This can be fixed by changing the css units from px to a more suitable unit. I would appreciate if someone took care of this so I may continue work on other issues.

Allows recording/clips/and pictures taken that are stored on the raspberry pi itself to be deleted.

Have tried several solutions to get it to work, but nothing has so far. Had to do with the Apache rewrite module.

Once the FTP server is set up implement a system for the website to grab files from it. This should also include downloading and deleting files from the server and implementing these videos on a user's home page. Thus this issue will include finalizing the look of a user's user page home page and allowing for the downloading and deletion of videos from it.
(User homepage UI made it's own issue.)

Involves creating a function to detect if a human is on screen using the already implemented object recognition. Will return a true or false value.

This involves encrypting all information before it is entered in the database using the PassLib library in Python. This can be done by having a python script that is called by the PHP script and it's result sent to the PHP script. This will involve adding this feature to every place our database is used.

We received good feedback to add a feature to tell when a package is removed from the screen since we are already implementing object recognition. This can be done with a function to tell if a box is on screen, and another to tell when that function has gone from a yes state to a no state.

What it should do: Require a length of at least 8 with one capital and one number/special character.

What it currently does: Requires a length of at least 8.

On the user page schedule tab a user should be able to add and remove schedules that are stored in our database. This just involves adding the schedule information to our database and displaying visual feedback for the user to view and manipulate their schedules. It would be nice if there was a way to sort these schedules visually as well.

Using the previously build functions implement a feature that will send an alert and picture to a user page when a human is detected on screen when motion is happening.

Create the feature for making video clips after the alert system is in place and sending them to the FTP server in a way that is accessible by the website.

Create the functionality for password resetting, information updating (phone#/email), configuring where they receive notifications, camera linkage to an account, and account deletion. This will also involve graphically implementing these for interaction of a user's settings page as well.

It would be nice if when a failure happens on the registration page that the page doesn't fully reload and get rid off all entered data on the page. Using JS we can keep the previous form data and possibly even do a database check without hitting the submit button. Will require looking into how to check a database in JavaScript. This issue is of lower priority and is mainly just a nice enhancement.

Sessions are needed to create unique user pages for each user. This will likely involve the creating and storing of temporary unique session IDs and checking these when displaying the various user pages. These IDs will need to be deleted upon logout and new ones generated on login.

This should send information such us a user's scheduling information for that camera to it. This can wait for implementation until the camera system is ready to accept schedule information.

This involves using openCV to create a function to recognize at least the following objects:
Trees,
Cars,
Pets,
Boxes,
People.

This function should return an answer of what objects it sees on screen.

This involves testing a connection to the FTP server by writing files to it, and later making it send clips recorded by our camera to the server.

This should be fairly straight forward and involve random number generation, but not using past generated number sequences. Our php will call cmd prompt to execute a python script that creates the hash ID and returns it to the page for use.

This will involve using sessions and the user page so the two issues pertaining to those should be implemented first. Covered by another issue making this one not required.

Using openCV implement a function that returns true if motion is detected by the camera.