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

Sun Mar 18 04:08:50 UTC 2012

My 2c, and I may be biased because I have spent a lot of time with
Refine. Here are a few things that I would really like:

 - clone columns
 - demonstrable rollback path (pref. sharing changeset format w/
Google Refine to allow interoperability)

Both of these things make it much easier to safely experiment with the data.

Maybe we could do some data introspection to produce aggregate stats,
ala R's data frame, for each of the columns?

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