This is the weekly scrum issue, per the requirements of the project. Be sure to answer the following questions in 1-2 sentences:

• What have I done this week? (with link(s) to the relevant GitHub Issue(s))
• What will I do next week? (with link(s) to the relevant GitHub Issue(s))
• What is holding me back? (if applicable)

Find random products online, store them in a file (JSON, csv, txt, whatever), and then populate the DB with them when the application is started.

As the application evolves and new functionality is introduced, it is important to ensure that our documentation stays up to date. This should include an updated ER diagram and UML class diagram to reflect the state of the application following the completion of the milestone 3 objectives.

they look bad, my bad.

This is the weekly scrum issue, per the requirements of the project. Be sure to answer the following questions in 1-2 sentences:

• What have I done this week? (with link(s) to the relevant GitHub Issue(s))
• What will I do next week? (with link(s) to the relevant GitHub Issue(s))
• What is holding me back? (if applicable)

A simple login/registration page should be implemented. This functionality relies on #3 and will insert into the User table upon registration. Should a user already exist, an appropriate error will be displayed to the user. This will direct insertions and lookups of the backend databases being persisted by the application.

Appropriate tests should be created that are automatically run on push to the repo via Maven. These should cover an appropriate breadth of the code while confirming functionality, with specific importance for testing the persistence of the created database.

• Create test cases for the backend models
• Create test cases for the RegistrationController
• Create test cases for the UserController
• Create test cases for the ProductController

Functionality should be added to not only rank available products by the similarity score, but the individual reviews on a product should also support this functionality.

The landing page is the page a user will encounter upon successfully logging into the system. The current plan for the landing page is to include a sidebar where the user can quickly navigate to products or reviews they have previously written, however, the actual pages for the reviews a user has written and the product pages are separate issues.

The user page should display the reviews a user has reviewed thus far if any. As this is not meant to be a social platform, nothing apart from the username of the user and their reviews need to be displayed on the page. This will require interaction with the backend databases being persisted by the application.

This issue should cover the creation of a database to track three tables. These tables are:

• A User table
• A Product table
• A Reviews table

Ensure that the NavBar is universal across the site (where a user has authentication) and can be used to navigate the entire site without the need for manually entering any URL changes.

The application should be able to list products for a given category and to sort these products by average rating. This requires an adaptation of the Product model to include a category in its underlying model.

For any created aspects of the application, UML documentation will need to be made to represent the system for each iteration. These should be focused on the backend functionality where appropriate, with a general focus on class diagrams above all else. The database schema can be auto-generated via IntelliJ and is not as much of a concern on the documentation front.

This likely needs JavaScript.

This button should appear after a user is following another user. The option to remove that other user for the main user's following list should occur when the button is pressed.

A product page should be created to display product reviews to the user. This page should simply display a product title, with an image of the product, along with the reviews for the product. These reviews should include the score (out of 5 stars), alongside the username of the user who reviewed the product. This will require interaction with the backend databases being persisted by the application.

An important aspect of the application is being able to follow users. Alongside this functionality, a user should be able to see whose ratings are most "similar" to theirs. This is done by calculating the Jaccard distance between users to determine similarity.

The data contained within the database pertaining to products, users, and reviews should be persisted between deployment in some capacity to make the application consistent between deployments.

To adhere to good CI practices and to generally benefit from the practice, it is vital that our tests are exhaustive and up to date. Throughout the development of milestone 2, tests should be updated to address any added functionality, and new tests should be created to test any features that fall outside of the scope of the classes created for milestone 1.

As the application evolves and new functionality is introduced, it is important to ensure that our documentation stays up to date. This should include an updated ER diagram and UML class diagram to reflect the state of the application following the completion of the milestone 2 objectives.

As the project reaches its completion, a general refactoring pass should occur once the final features have been added to the system to ensure naming consistency, minimal code reuse, JavaDoc completion, among other good practices.

Ensure that all the pages on the site follow the same styling format and move the style into a core file

This is the weekly scrum issue, per the requirements of the project. As this is the final iteration of the project, there is no need to discuss future work as all objectives should be complete by the submission date. Be sure to answer the following questions in 1-2 sentences:

• What have I done this week? (with link(s) to the relevant GitHub Issue(s))
• What was holding me back? (if applicable)

Per the project requirements, products should provide a hyperlink to the website where they are available for purchase. This is likely a quick addition, requiring a minor modification to the backend Product model class and some minor HTML changes to the product page.

Ideally, a user should be able to navigate to another user's profile and see all of their reviews.

As the users maintain a user list of those users a user wishes to "follow", the website should be able to display the average rating of a product sourcing the scores from only the users a user is following.

• Display the average rating of the product
• Filter reviews by reviewer

The degrees of separation between users should be calculated and displayed beside any user's review on a product page, something similar to how LinkedIn implements this feature.