You’ve given me something to think about and I think you’re right, there is an element of time missing. In fact there is a few parallel time elements missing from this too
For example, when we are shooting there is a rough formula for how long of a day we need to get those scenes. Usually it’s 1 hour per 1 page scene plus an extra 30 mins added on for each character in the scene. But that doesn’t translate to the final product as that information tells us nothing about how long or important a scene should be in the final product.
But it’s also possible I’m getting too ahead of myself here and maybe there’s another object that is created that includes the scene, production and final product objects instead of jamming it all into this object.
It's not clear what the idea is here. Which is why all the questions. I suspect, as you said, that a much more complex data structure would be required to encode all the various aspects of production into its constituent elements and the relations between the elements.
I would guess, that the first step would be to establish how the process of production (screenplay, scenes, camera angles, locations etc.) relates to the final product: scene frames. Each scene must have many shared elements as well. That would have to be encoded too.
For example, when we are shooting there is a rough formula for how long of a day we need to get those scenes. Usually it’s 1 hour per 1 page scene plus an extra 30 mins added on for each character in the scene. But that doesn’t translate to the final product as that information tells us nothing about how long or important a scene should be in the final product.
But it’s also possible I’m getting too ahead of myself here and maybe there’s another object that is created that includes the scene, production and final product objects instead of jamming it all into this object.
Open to anything suggestions you may have.