eduardspirache / video-database

Personalized movie & series platform with OOP & Java. Focused on code quality, used checkstyle for compliance

Video Database

Developed a simplified platform for movie & series information with personalized recommendations. Utilized OOP concepts such as inheritance, aggregation, polymorphism, and abstraction. Practiced Java programming and emphasized code quality for design and structure. Used checkstyle for code style compliance.

Implementation

The implemented platform simulates actions that users can perform on a movie viewing platform: ratings, movie viewing, searches, recommendations, etc.

The entities that were modeled are:

Video

- Of two types: movies and shows (TV series). The difference between them is that TV series have seasons.
- All videos have in common a title, release year, one or more genres (e.g. comedy, thriller)
- The seasons of a TV series are associated with a number, the duration of the entire season, and a rating.
- Movies have duration and rating.

User

- Has two categories: standard and premium.
- Has favorite videos and viewed videos.
- Data for these entities is loaded from JSON files provided as input in tests. They are kept in a Repository.

Users can perform the following three types of actions: commands, queries, and recommendations.

Execution of the project

1. The data read from the test JSON file is loaded into objects.
   
2. Actions (commands, queries or recommendations) are received sequentially and executed as they are received, their result having an effect on the Repository.
   
3. After executing an action, the result of the action is displayed in the output JSON file.
   
4. Upon completion of all actions, the program execution is also completed.
   

Commands

These represent a user's ability to perform direct actions and are of 3 different types.
- Favorite - adds a video to the user's list of favorite videos if the user has already viewed it.
- View - views a video by marking it as seen. If the user has already seen it, the number of views of that video by the user is incremented. When viewing a TV series, all seasons are viewed.
- Rating - provides a rating for a video that has already been seen (for TV series, it is applied per season, unlike viewing, where it is done for the entire series).
The rating varies depending on the type - for TV series it is per season.
The rating can only be given once by a user. For TV series, it can only be given once per season.

Queries

These represent global searches performed by users for actors, videos, and users. The results of these queries are displayed as output of the test.

A query contains the type of information being searched for: actor/video/user, the sorting criteria, and various parameters.Queries include the sorting order as a parameter, whether sorting is to be done in ascending or descending order. The secondary sorting criterion is alphabetical order in descending/ascending order depending on the order from the first criterion.

Recommendations

These represent suggestions made to users based on their viewing history, favorites, and ratings. Recommendations are made based on different criteria, such as genre, actor, etc. The recommendations made are displayed as output of the test.