You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we don't have a predefined column to expose the upcoming moments for each moment ID (and we should not). So I'm wondering if you guys have any input on what's the best way to achieve this?
What I'm thinking right now is using the met_end of a currently playing moment and compare that with met_start of all moments (global? or only within this story) after +/- some offset to allow certain range.
I'm just not clear if this is to be used, what's the best offset could be used? 1 min, 2mins?, 30s....
So will that be predefined as in db? When I look at the story table and moment_story_join table I dont see any metadata yielding this kinda of information.
...
And that the moment_IDs themselves (in order or not) should not suggest any order of the moments in the story anyway
Right now we don't have a predefined column to expose the upcoming moments for each moment ID (and we should not). So I'm wondering if you guys have any input on what's the best way to achieve this?
What I'm thinking right now is using the met_end of a currently playing moment and compare that with met_start of all moments (global? or only within this story) after +/- some offset to allow certain range.
I'm just not clear if this is to be used, what's the best offset could be used? 1 min, 2mins?, 30s....
Link to the database schema https://github.com/UTD-CRSS/exploreapollo.org-schema/blob/channelChunk/README.md
The text was updated successfully, but these errors were encountered: