How practical-recommender-systems/moviegeek works
Project type and purpose
• This is a full‑stack Django web application (“MovieGEEK”) whose primary purpose is to demonstrate and serve a variety of recommender‑system algorithms. It collects movie and rating data, builds recommendation models, evaluates them, and presents analytics and recommendations via a web UI.
File structure
• Top‐level Django project: prs_project/ (settings, WSGI, URLs) and manage.py.
• Django apps:
• collector/ – endpoints and models for ingesting movie/rating data
• builder/ – batch calculators that build recommendation models (e.g., matrix factorization, item similarity, LDA)
• evaluator/ – code to run algorithmic evaluations and coverage/precision metrics
• recommender/ – Django views/models for serving recommendations at runtime
• analytics/ – views/templates for visualizing model outputs (clusters, similarity graphs, LDA topics, user/item analytics)
• moviegeeks/ – core app for browsing/searching movies, detail pages
• Support code:
• recs/ – reusable recommender classes (BPR, FunkSVD, popularity, content-based, neighborhood)
• populate_*.py scripts & db-migrate.sh – database setup and data loading
• notebooks/ – exploratory analyses
• Configuration: Dockerfile, docker-compose.yml, .travis.yml, requirements.txt, prs_project/settings.py.
Additional insights from README
• Uses SQLite (or PostgreSQL) for the movie/rating database.
• External dependency on “themoviedb.org” API for movie posters.
• Supports both Dockerized deployment and virtualenv.
• Batch pipeline: build models → migrate schemas → populate data → evaluate algorithms → serve via web.