[okfn-labs] Some further improvements to Recline Data Explorer

[Rufus Pollock]

On 16 March 2012 02:13, Tim McNamara <paperless at timmcnamara.co.nz> wrote:
> The demo looks totally sweet. Would it be useful to get some user
> feedback? I bet I could coral a few people to play around with things.

Yes - would love to get more feedback! I'd really like to do a proper
public release soon so I'd love to get some feedback now.

More new features (would have mentioned yesterday if gh-pages had been
building ...):

* New graph types (bar, points, points and lines)
* Hover on points in charts (and hover shows correct labels e.g. try
it out in first example below)
* Bar charts use labels where x-values are non-numeric (see demo below)

Example (using the demo data):

<http://okfnlabs.org/recline/demo/#graph?graph={"group":"label","series":["y"],"graphType":"bars"}>

More exciting real-data example: Mortality stats for london boroughs
from London DataStore found via PublicData.eu [1] (note how it uses
all our features of url / hash configuration):

<http://okfnlabs.org/recline/demo/?url=http://data.london.gov.uk/datafiles/health/mortality-gender-borough.csv&backend=dataproxy#graph?graph={"group":"Area","series":["Number
of deaths"],"graphType":"bars"}&reclineQuery={"size":33,"from":0}>

NB: i'm well aware of mess in labels at bottom (though hover also
shows the label as well). There is a patch for vertical labels in flot
but has not made it into main yet ... [2]).

Rufus

[1]: http://publicdata.eu/dataset/deaths-and-mortality-ratios-borough
  <http://publicdata.eu/dataset/deaths-and-mortality-ratios-borough/resource/d30ade61-f5e2-4301-b508-a10cf3a97d46>

[2]: https://github.com/flot/flot/pull/15

> On 16 March 2012 13:51, Rufus Pollock <rufus.pollock at okfn.org> wrote:
>> I demo'd latest version of Recline at the Labs show and tell Tuesday.
>> I've since done a few more tweaks, which you can see here:
>>
>> <http://okfnlabs.org/recline/demo/>
>>
>> * Move to bootstrap fully for dropdowns and menus giving nicer styling
>> around buttons and dropdowns
>>
>> * Added support for storing query state in the url e.g.
>> <http://okfnlabs.org/recline/demo/#?reclineQuery={"size":2,"from":0}>
>>
>> * Dropdown menu for search controls containing simple pagination with
>> changing of from / size (offset / limit)
>>
>> * Added support for loading from a query paramemter url in the demo so
>> you can share links with people e.g.
>> <http://okfnlabs.org/recline/demo/?url=http://data.london.gov.uk/datafiles/health/mortality-gender-borough.csv&backend=dataproxy>
>>
>> * Support for guessing google doc json url from simple google docs url
>> (want to see a google docs spreadsheet in recline just do
>> .../recline/demo/?url={gdoc-url}&backend=gdocs)
>>
>> One thing I've been thinking hard about but not reached a clear
>> conclusion on is where to put functionality like filters and facets in
>> the UI. Sepcifically:
>>
>> * Where should they get created from (e.g. from main search drop down,
>> from somewhere else)
>> * Where should facets live (both options and set values)? (Classic
>> approach is Mark's great work with <http://okfnlabs.org/facetview/>)
>>
>> Something like http://documentcloud.github.com/visualsearch/ seems
>> quite nice and very compact but it would not work for complex use
>> cases like those Mark has (where he allows for year ranges and the
>> like). Basically: how complex do these things need to be ...
>>
>> Rufus
>>
>> _______________________________________________
>> okfn-labs mailing list
>> okfn-labs at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/okfn-labs



-- 
Co-Founder, Open Knowledge Foundation
Promoting Open Knowledge in a Digital Age
http://www.okfn.org/ - http://blog.okfn.org/