Last modified: 2014-10-03 17:52:02 UTC
for example: 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.
Note: Dario created the example/description above.
I think this needs quite a bit of definition. Wikimetrics is not the best tool to "create" cohorts, and "ad hoc" query tool will be a lot better. We can chain metrics and run the output of newly created users through another metric but, to be clear, that cohort will not be persisted, nor linked to the user.
Here's the thread on wikimetrics-l https://lists.wikimedia.org/pipermail/wikimetrics/2014-October/000165.html The related story on chaining is here: https://bugzilla.wikimedia.org/show_bug.cgi?id=67501 At this time, this is relatively low priority and yes it needs more scope/definition/tasking before we would start any work on this.
