[ckan-discuss] CKAN suggestions

David Read david.read at okfn.org
Thu Nov 24 10:48:06 GMT 2011

On 23 November 2011 20:50, Augusto Herrmann <augusto.herrmann at gmail.com>wrote:

> IMHO, both a controlled vocabulary and flexible folksonomy tags are useful
> and can coexist in harmony. As Morville & Rosenfeld put it on their
> Information Achitecture book [1], "on some projects, we'll have the
> opportunity to bridge the gap, using both tags and taxonomies to connect
> users with the content they seek."

Great to hear it, and interesting point of view in the book too. Anyone
else interested in having a controlled vocabulary? I guess it's going to be
more attractive to the the governments and institutions with data
catalogues they have a bit more control over populating and idea of how
they want them categorised.

> In December I shall take some days off work, and a side-project I'm
> considering to undertake is building a simple python package, dependant on
> RDFLib, to ease the manipulation of SKOS data. That should make it easier
> to create a CKAN plugin for a controlled vocabulary that can import from

This sounds v. useful! I guess for CKAN's initial purposes we just need URI
and English translation for each term, but other other properties could be
stored and exploited in extensions etc. in the future. It would be great to
make this multilingual from the start too.


> [1] http://books.google.com/books?id=2d2Ry2hZc2MC&pg=PA80
> Cheers,
> Augusto Herrmann
> On Tue, Nov 22, 2011 at 1:00 PM, David Read <david.read at okfn.org> wrote:
>> On 22 November 2011 14:00, Richard Cyganiak <richard at cyganiak.de> wrote:
>> > (Apologies for responding to such old mails – I'm catching up on some
>> unread list mails, and some things are just too interesting to let them
>> pass by without a comment ;-)
>> >
>> > On 31 Oct 2011, at 17:22, David Read wrote:
>> >> * Controlled Vocabulary Support - SKOS
>> >>     Besides the existing folksonomy tags for packages, there should be
>> >> the possibility that the catalog administrator could set up a
>> >> controlled vocabulary, in SKOS format, that would be used in a
>> >> specific field when an user would register or edit a package. The
>> >> field could use autocomplete to search on the labels for the
>> >> skos:Concept s and display them for users, but record the concept URIs
>> >> on the database.
>> >>
>> >> DR: I think this is a great idea. We've had several people mention
>> supporting a field for a controlled taxonomy. Which one used should be
>> configurable by instance, but for thedatahub.org we'd want something
>> pretty generic. How do people feel about SKOS, Eurovoc etc?
>> >
>> > If you decide to add support for controlled vocabulary, then I fully
>> support the idea of being able to import the vocabulary from SKOS.
>> >
>> > Note that EUROVOC is available in SKOS format:
>> > http://thedatahub.org/dataset/erovoc-in-skos
>> Perfect - thanks! I would love to be able to import this sort of
>> controlled vocabulary into CKAN.
>> Does anyone else agree with the usefulness of a controlled vocabulary,
>> or are flexible tags useful in general? If we can get enough weight
>> behind controlled vocab, then we can prioritise some time for it to be
>> coded into CKAN.
>> David
>> >
>> > Best,
>> > Richard
>> _______________________________________________
>> ckan-discuss mailing list
>> ckan-discuss at lists.okfn.org
>> http://lists.okfn.org/mailman/listinfo/ckan-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-discuss/attachments/20111124/bf3a6c87/attachment-0001.htm>

More information about the ckan-discuss mailing list