[okfn-labs] Next generation data catalogues.

[Friedrich Lindenberg]

Hey Ross,

that sounds cool, it'd certainly be fun to keep the -labs list in the loop.
For what it's worth, we also still have
https://github.com/pudo/datahubhanging around, so if you want to play
with concepts that may be easier to
hack than CKAN proper. In terms of other tech, I'd also really look at
Max's dat stuff. He's apparently started working on that and I feel it
could be a useful data transfer convention.

Finally, my sense is that this should be driven by _activities_: what do
you want to do? If the answer is "search data", then you have a problem
(because, well, Google). Nobody has ever really wanted to "read and update
metadata". "Explore" and "visualise" are mostly BS: why? Whats your larger
aim? How often do you do that? Who are you, anyway? "Upload" has existed
for years... And a whole generation of fake-social catalogues has just died
off (RIP BuzzData).

Maybe there's some help in being more specific: Heroku data clips are cool,
and a weird percentage of my data projects now depends on Nomenklatura
(even though I'm still pretty much its only user :( ). Also, Google
Spreadsheets: amazing table UI and horrible API, but it works for people.

Cheers,

 - Friedrich







On Mon, Aug 26, 2013 at 4:45 PM, Ross Jones <ross at servercode.co.uk> wrote:

> Hi,
>
> There was a bit of discussion on the #ckan channel this morning between
> some developers
> building data catalogs around what a next-generation data catalog would
> look like.  It was
> noted that it might _not_ look like CKAN, and so we booted up the
> catalog-ng organisation
> on github (https://github.com/catalog-ng) as a place to work on some
> ideas and proof-of-concepts
> around what we think would be included in a new data catalog using the
> knowledge gained
> working with CKAN.
>
> There really isn't a plan yet, certainly the intention isn't to damage
> CKAN in any way, but more
> of a way to experiment with building catalogs without any of the baggage
> involved with a
> mature product - what would you build today with the new tech available
> and the experience
> of working with CKAN.  Rather than go through the process of doing this
> outside, I thought it might
> be useful to do this as part of labs and keep it inside OKF, and possibly
> keep it on a OKF mailing list.
>
> Does this belong in OKFN-labs? Does the idea of building something new in
> that area sound
> vaguely interesting to anyone (other than those of us with work with CKAN
> day-to-day)?
>
>
> Ross.
> _______________________________________________
> okfn-labs mailing list
> okfn-labs at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/okfn-labs
> Unsubscribe: http://lists.okfn.org/mailman/options/okfn-labs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/okfn-labs/attachments/20130826/bfd0f4c8/attachment-0002.html>