Nuria,
thanks for the feedback – for context, the reason why I am asking is that:
• I was under the impression that this data was already being stored somewhere in temporary tables by Wikimetrics when generating project-level reports
• this is quite similar to one of the earliest feature requests that we had for UserMetrics (the predecessor of Wikimetrics) under the notion of “generated cohorts”:
1) take the non-aggregate output of a report (say all registered users or new active editors from foowiki in a given time period)
2) save the output as a cohort
3) re-run that cohort through a different metric
Using Quarry still relies on the end user’s ability to understand how to turn a research question into a query. Having a curated query library is a good step in that direction, but that still requires some basic knowledge of SQL.
D
Dario:
There are no technical blockers to be able to generate that data. Now, product wise it does not seem like a fit as wikimetrics' purpose is to produce data and run metrics. All wikimetrics computations are pre-canned.
It seems to me the use cases you passed along are better fitted by a tool being able to freely query the db like quarry.
Thanks,
Nuria
_______________________________________________
Wikimetrics mailing list
Wikimetrics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimetrics