Visualized Subtitle Analysis
- Master branch ALWAYS contains a working version
- We use node.js hosted on cloud9
- The code is organized strictly modular
- We use issues to track not yet done work
- Each issue is handled in an own branch
- Server (Node.js npm)
- Express.js
- Opensubtitles-Client
- Templating with Jade
- Client
- D3.js
- C3.js for easier D3 handling
- jQuery
- List of available subtitles --> works
- local --> yeah
- id and/or imdbid, movie name --> yeah
- selectable e.g. via autocomplete search input field --> yeah
- List already created and filtered --> subtitles.txt (40000-ish movies) --> yeah
- create server-side, show client-side --> yeah
- Filter subtitle files for a specific movie --> works
- Opus dump? --> nope
- Use API? --> yeah
- Limit available movies and store list locally? --> yeah
- Always use the best rated sub file --> yeah
- server-side --> yeah
- Download the selected subtitle file --> works
- Opus dump? --> nope
- Use API --> yeah
- server-side --> yeah
- Preprocess file --> works
- convert into object --> works
- server-side --> works
- NLP
- Node.js. natural vs. stanford
- sentiment analysis. sentiment vs. Sentimental
- server-side
- Module Templates
- Meta Module
- Timeline Module
- Settings Module
- Sequence Text Module
- Time Statistic Module
- ... Module
- Visualise
- D3/C3
- plain text
- client-side
- View: List of all available movies (?)
- Filter that view (genres, ...) (?)
- View: Analyse one single movie
- View: Analyse and compare two (or more?) movies
- Module: Search mask with autocomplete for one single movie
- GET-Routing via id/movie name/imdb --> queryString vs. path
- subvis/ --> home. list of all movies or simple landing page
- subvis/1583 --> path routing via id or imdb
- subvis/Pulp+Fiction --> path routing via movie name
- subivs/single?id=1583 --> queryString routing via id
- subvis/single?imdb=1234 --> queryString routing via imdb
- subvis/single?name=Pulp+Fiction --> queryString routing via movie name
- subvis/multi?id1=1583&id2=1234 --> queryString routing using two movies
- Or no advanced routing and just use a plain search field based UI