That looks like a cool project! I love the way it enables fans to deep dive into content they already love to get even more enjoyment out of it, but I would also be curious if some folks use it as basically Cliffs Notes for stuff they're interested in but maybe don't have time to fully invest it?

We've started working on some advanced language parsing out of subtitle dialogue, somewhat similar to what you're doing we're trying to make a link back to actors interacting (in our case via character names). I'd be curious to hear how you've developed your scene ontology for categorization/splitting purposes.

Agreed about potential for AI to inform better content decisions, or at the very least decent analytics would push things forward quite a bit. As far as your questions:

1. Data collection and mastering is like 80% of the work as you probably know, themoviedb.org is great and we use it too. Myapifilms.com, allmovie.com are solid sources. We also heavily leverage Wikipedia, google and waybackmachine.org.

2. Angular - personal comfort level + compatibility with the rest of our stack (certain charting libraries and themes we use). We're looking closely at React now and there's a good chance that the next generation of FLIQ moves in this direction.