Right now, /data/ contains arbitrarily named event streams. People couldn't quite distinguish which one has some good test data or if there's a special invariant in one of them.
0.json doesn't show the domain properly but only lists the 4 basic events before a game can take place. Extending this to a minimal example and calling it single_game.json would be nice
2.json is the most interesting that I found, with meaningful strings and lots of interaction. It might still be nice to remove some of the extra quizzes (most quizzes appear 3 times) and call this e.g. game_show.json
The rest are nonsensical (for good reasons, I understand) but don't really provide any more value apart from being huge and benchmarking the performance of the projection. We could potentially just keep one or two of them or replace them altogether with streams that focus on a single aspect, e.g.:
Going over a longer timespan (2-3 years) where ppl only play 1-2 times a month (long_timespan.json)
Have a few quizzes that are in high demand but they vary in difficulty (lots_of_interaction.json)
Right now,
/data/contains arbitrarily named event streams. People couldn't quite distinguish which one has some good test data or if there's a special invariant in one of them.0.jsondoesn't show the domain properly but only lists the 4 basic events before a game can take place. Extending this to a minimal example and calling itsingle_game.jsonwould be nice2.jsonis the most interesting that I found, with meaningful strings and lots of interaction. It might still be nice to remove some of the extra quizzes (most quizzes appear 3 times) and call this e.g.game_show.jsonThe rest are nonsensical (for good reasons, I understand) but don't really provide any more value apart from being huge and benchmarking the performance of the projection. We could potentially just keep one or two of them or replace them altogether with streams that focus on a single aspect, e.g.:
long_timespan.json)lots_of_interaction.json)