[ckan-dev] CKAN-specific considerations for DCAT-AP

Stefan Oderbolz stefan.oderbolz at liip.ch
Tue Dec 20 19:34:52 UTC 2016


Hi Armin,

We use both as well, here is our DCAT-AP Switzerland schema for
ckanext-scheming:
https://github.com/opendata-swiss/ckanext-switzerland/blob/master/ckanext/switzerland/dcat-ap-switzerland_scheming.json

- Stefan

On Dec 20, 2016 6:29 PM, "Timothy Giles" <timothy.giles at slu.se> wrote:

> ​Yes, I (my colleagues and I) do.
>
>
> We use scheming (fluent, repeating, scheming and composite) to define the
> metadata schema(s) and a custom mapping so DCAT extension can do its thing.
> Works well for us.
>
>
> Regards Tim
>
>
> ------------------------------
> *From:* ckan-dev <ckan-dev-bounces at lists.okfn.org> on behalf of Armin
> Retterath <armin.retterath at gmail.com>
> *Sent:* 20 December 2016 05:53 PM
> *To:* CKAN Development Discussions
> *Subject:* Re: [ckan-dev] CKAN-specific considerations for DCAT-AP
>
> hello together,
>
> is the ckanext-dcat extension compatible to ckanext-scheming? does anyone
> use both extensions together? i think a sync of both will be great - like
> having a minimal schema which allows the export of minimal dcat documents.
>
> best regards
>
> armin
>
> 2016-12-20 16:10 GMT+01:00 Stefan Oderbolz <stefan.oderbolz at liip.ch>:
>
>> Hi Florian,
>>
>> I'm part of the team that implemented DCAT-AP Switzerland for
>> opendata.swiss, an CKAN-based opendata portal for Switzerland.
>>
>> We rely on ckanext-dcat, you can find the source here:
>> https://github.com/opendata-swiss/ckanext-switzerland/
>> blob/master/ckanext/switzerland/dcat/profiles.py
>> DCAT-AP Switzerland is based on the European DCAT-AP standard, but has
>> some fields that are used differently. As a help for the data publishers we
>> setup a handbook with the documentation, so that they have a reference
>> guide: http://handbook.opendata.swiss/en/library/ch-dcat-ap
>>
>> The portal provides 3 ways for data provides to add new datasets:
>>
>> 1. Add them manually using the WordPress backend of opendata.swiss (the
>> source code of this backend can be found here: https://github.com/opend
>> ata-swiss/wp-ckan-backend)
>> 2. Upload a valid DCAT-AP Switzerland XML in the WordPress backend of
>> opendata.swiss
>> 3. Provide a DCAT-AP Switzerland RDF harvester source, we then use the
>> harvester provided by ckanext-dcat to harvest these data providers (
>> https://github.com/ckan/ckanext-dcat#rdf-dcat-harvester)
>>
>>
>> Our learnings:
>> - Get feedback from the data providers early on
>> - If possible, provide a validator for your DCAT-AP profile
>> - If possible, provide an export functionality for manually entered data,
>> so that less experienced users have an easy way to "generate" a valid
>> example
>>
>>
>> Feel free to contact me if you have further questions.
>>
>> Best regards Stefan
>>
>>
>> On Mon, Dec 19, 2016 at 10:03 AM, <Florian.Brucker at mb.karlsruhe.de>
>> wrote:
>>
>>> Dear Tim,
>>>
>>> your profile would definitely be a great help! Since others may be in
>>> the same situation as me you could also think about posting the files on
>>> GitHub or something similar.
>>>
>>>
>>> Regards,
>>> Florian
>>>
>>>
>>> "ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 16.12.2016
>>> 14:58:05:
>>>
>>> > Von: Timothy Giles <timothy.giles at slu.se>
>>> > An: CKAN Development Discussions <ckan-dev at lists.okfn.org>,
>>> > Datum: 16.12.2016 14:58
>>> > Betreff: Re: [ckan-dev] CKAN-specific considerations for DCAT-AP
>>> > Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org>
>>> >
>>> > I can send you are profile, but they are specific to our metadata
>>> schema.
>>> >
>>> > I cant say I am an expert on DCAT AP – the most confusing issue is
>>> > the various examples I find around the web that don’t work with
>>> > validators! We want to connect to oppna data .se and they have
>>> > examples but these don’t validate fully in their sandbox system…
>>> > But, it is still pretty easy to change. I will send you our schema
>>> > document, json and the profile early next week.
>>> >
>>> > Regards Tim
>>> >
>>> > From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org
>>> <ckan-dev-bounces at lists.okfn.org>] On Behalf Of
>>> > Florian.Brucker at mb.karlsruhe.de
>>> > Sent: den 16 december 2016 13:29
>>> > To: CKAN Development Discussions <ckan-dev at lists.okfn.org>
>>> > Subject: Re: [ckan-dev] CKAN-specific considerations for DCAT-AP
>>> >
>>> > Dear Timothy,
>>> >
>>> > thanks for the feedback! Nice to hear that things are working well.
>>> > Is there anything that worked particularly well or not? Anything to
>>> > watch out for when defining the profile?
>>> >
>>> > Are your adaptions to ckanext-dcat available somewhere?
>>> >
>>> >
>>> > Regards,
>>> > Florian
>>> >
>>> >
>>> >
>>> >
>>> > "ckan-dev" <ckan-dev-bounces at lists.okfn.org> schrieb am 16.12.2016
>>> 11:17:28:
>>> >
>>> > > Von: Timothy Giles <timothy.giles at slu.se>
>>> > > An: CKAN Development Discussions <ckan-dev at lists.okfn.org>,
>>> > > Datum: 16.12.2016 11:17
>>> > > Betreff: Re: [ckan-dev] CKAN-specific considerations for DCAT-AP
>>> > > Gesendet von: "ckan-dev" <ckan-dev-bounces at lists.okfn.org>
>>> > >
>>> > > Hi Florian,
>>> > >
>>> > > We use CKANEXT-DCAT as a base and have a custom DCAT AP 1.1 profile
>>> > > defined. It is easy to do, using the current profile as a base. If
>>> > > you know DCAT and have the profile mapped out already, it is a few
>>> > > hours work to implement.
>>> > >
>>> > > Regards Timothy
>>> > >
>>> > > From: ckan-dev [mailto:ckan-dev-bounces at lists.okfn.org
>>> <ckan-dev-bounces at lists.okfn.org>] On Behalf Of
>>> > > Florian.Brucker at mb.karlsruhe.de
>>> > > Sent: den 16 december 2016 11:10
>>> > > To: ckan-dev at lists.okfn.org
>>> > > Subject: [ckan-dev] CKAN-specific considerations for DCAT-AP
>>> > >
>>> > > Hi!
>>> > >
>>> > > The German council responsible for the metadata standard for open
>>> > > government data  has recently decided to develop a custom DCAT-AP
>>> > > profile "DCAT-AP.DE". That profile will be used for collecting and
>>> > > exchanging meta data in the open data portals of the German
>>> > > administration (on federal, state and municipal level). Many of the
>>> > > German open data portals are CKAN-based, so I'm wondering if there's
>>> > > anything CKAN-specific that we should keep in mind while developing
>>> > > DCAT-AP.DE. I'm aware of ckanext-dcat but have never used it
>>> myself.
>>> > >
>>> > > Does anybody have experiences with using CKAN for DCAT-AP and
>>> > > profiles derived from it?
>>> > >
>>> > > Thanks for any input!
>>> > >
>>> > >
>>> > > Regards,
>>> > > Florian_______________________________________________
>>> > > ckan-dev mailing list
>>> > > ckan-dev at lists.okfn.org
>>> > > https://lists.okfn.org/mailman/listinfo/ckan-dev
>>> > > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>> > _______________________________________________
>>> > ckan-dev mailing list
>>> > ckan-dev at lists.okfn.org
>>> > https://lists.okfn.org/mailman/listinfo/ckan-dev
>>> > Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>>
>>> _______________________________________________
>>> ckan-dev mailing list
>>> ckan-dev at lists.okfn.org
>>> https://lists.okfn.org/mailman/listinfo/ckan-dev
>>> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>>
>>>
>>
>>
>> --
>> Liip AG  // Limmatstrasse 183 //  CH-8005 Zürich
>> Tel +41 43 500 39 80 <+41%2043%20500%2039%2080> // GnuPG 0x7B588C67 //
>> www.liip.ch
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org
>> https://lists.okfn.org/mailman/listinfo/ckan-dev
>> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>>
>>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> https://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: https://lists.okfn.org/mailman/options/ckan-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20161220/3785d72f/attachment-0003.html>


More information about the ckan-dev mailing list