Can't wrap my head how I'm supposed to model some things

>>52486771
This is a great question that I wish somebody would answer.

>>52486816
It's seems to be more of a statement, rather a question.

Sorry, I've not made it clear, I want to know if there's any material to read about "choosing" how to model things into objects.

Look into OO Software Design with UML and GRASP-patterns.

flowchart?

rebump

SICP

Maybe you're not supposed to wrap your head around it all.

Shit like IMDB probably has multiple people on the team each designated a certain aspect. You're probably expecting too much of yourself.

What language are you using? Are you just building the db with pure sql? What you described is really easy with django.

>>52487817
I was using mongodb, but I don't think the problem is on this point. It's more about being able to solidly construct classes that could be interpreted in various ways.

Going to take a look at the recommendations when I go home.

>>52487767
Imdb is an SQL database that is also designed like shit. They have two different tables for actors and actresses for fuck's sake.

>>52487875
You just need define one to many relationships between your models. I have no idea how to do that in mongo

>>52486771
Take a look at the alternate movie database. It's a good place to start learning about modelling this sort of stuff.

Each type is a container type capable of holding more types.
Use composition, minimal inheritance.
Easy.
A show may contain seasons, just as a season may contain episodes, an episode acts, and a trilogy hobbits.

>>52486771
id/parent_id tree structure with a row type (ex. video)

https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model

Look into databases. That's what U R doing.