Analytics/Visualization, Reporting & Applications/GlobalDevFeedback

Be wilder.
 * I was born to be wild Jwild (talk) 21:05, 16 August 2012 (UTC)

Laundry list from my first full graph creation experience
Note: I was creating this graph: http://global-dev.wmflabs.org/graphs/ar_wp
 * Automatic sorting would be great (e.g., I was making a stacked line chart, and I want the smallest to go on the bottom, but I had to do it all by eye/hand for ~20 rows)
 * Coloring of lines: if you add too many fields into the graph, the color swatch does not reloop, it just starts making the lines/segments black! (note: if I clicked the color swatch, it would then apply a color, but if I did not, it would display as black)
 * automatic saving: yes - i learned the hard way that this wasn't like google docs :)
 * Confirmation of successful "save": it would also be great to get a little confirmation at the top if my saving attempts are successful
 * significant figures: can't find a way to change the sig figs that are being displayed (e.g., so, instead of "300.0" to just have "300," since editors are always a whole number)
 * Similarly, once the numbers get above 1000, they start to round ("1.2K"). Is there a way to make this optional, and/or eliminate it? For the smaller numbers our languages are working with, the exact number matters a lot (e.g., if the number of active editors is 1549 in July vs 1551 in August, which currently would just report as "1.5K" and "1.6K").

Overall, I'm really glad I have something to log feedback about - thank you for building this :) Jwild (talk) 21:05, 16 August 2012 (UTC)

Some future visualizations

 * 1) MAPS! We need to be able to look at saturation of editors by geography
 * 2) Bar charts (Cluster, stacked)

Use cases
In order for Limn to replace current ad-hoc workflows for data analysis and visualization for Global Development projects, it needs to support the most common and important activities that those projects perform with data. In order to make sure Limn does what we need it to to work for us, rather than trying to make it do everything, we propose to create strong, representative use cases to guide development efforts, rather than providing developers with a laundry list of features.

Annotate visualizations
Currently, it is not possible to annotate a chart or graph directly in Limn. The ability to annotate charts is especially important when the charts are being used to communicate research findings to a broader audience: such as in a project status report or a presentation slide deck.
 * Examples
 * See this presentation on Arabic Wikipedia for an example of Limn visualizations that have been exported to PNG and annotated in a presentation software tool. Supporting direct annotation of Limn charts would make it easier for project teams to have presentations and discussions around their data without exporting it from Limn.
 * Recommendations
 * Provide a palette of basic chart annotations such as text boxes, arrows, as well as brackets (i.e. {, [), highlight boxes and highlight shading for emphasis. Additional options may be added as the need arises.

Group related data
Currently, it is not possible to visually 'group' similar data. Since Limn will frequently be used to compare/contrast cohorts of editors under different conditions (different edit counts, different wikis, etc), allowing users to present different cohorts are related or different would be useful.
 * Examples
 * I want to visualize the number of scholarships (broken out into partial and full scholarships) across WMF, WMFUK and WMFR. I would like to be able to easily compare the relative proportion of full scholarships, and the total amount of money disbursed across the three different chapters.
 * Recommendations
 * Limn should support visualization of categorical data with stacked and/or clustered bar charts.