Hi Dan, Sorry for the late response to this-- ** Make a new cube that examines site versions and client information* ** Just use the private data as we're already doing, but aggregate it hourly or daily as needed, to make analysis much faster.*
How can I help add/keep this to/on your roadmap? -J On Fri, Jun 5, 2015 at 12:28 PM, Dan Andreescu <[email protected]> wrote: > On Fri, Jun 5, 2015 at 3:09 PM, Oliver Keyes <[email protected]> wrote: > >> If we can't share it with the public then it seems like it shouldn't >> be part of a proposal for an API. >> > > Right, to clarify, this proposal is for a public data set and API. > > >> >>> Thanks Dan, and apologies if these are naive questions: >> >>> >> >>> For mobile web can we also see beta v. stable? This is important for >> >>> tracking prototypes, which is one of the core product uses for this >> data. >> >>> >> >>> For apps can we see ios v android? >> > > Jon, we chose to not include that information in order to limit the amount > of data that we'd have to deal with. If it gets too large, it won't fit > into PostgreSQL. For the iOS / Android and beta / alpha versions of the > site we can either: > > * Make a new cube that examines site versions and client information > * Just use the private data as we're already doing, but aggregate it > hourly or daily as needed, to make analysis much faster. > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > >
_______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
