[ckan-dev] CKAN - DCAT

Tue Jun 25 14:29:43 UTC 2013

Hi Pascal and Ross,

We are actually doing some work on this front as we speak, on the
context of the publicdata.eu project. It is still very early stages
but basically the idea is to be able to provide the datasets metadata
in a dcat-like form dump (xml-rdf and json), including the most
relevant fields, and being able to harvest it from other catalogues.
One of the main requirements has been to keep it super simple to start
with, we'll try and post an early draft as soon as possible to gather
feedback.

Cheers,

Adrià

On 25 June 2013 15:07,  <p.romain at cg33.fr> wrote:
>
>
>
>
> -----ckan-dev-bounces at lists.okfn.org a écrit : -----
> A : CKAN Development Discussions <ckan-dev at lists.okfn.org>
> De : Ross Jones
> Envoyé par : ckan-dev-bounces at lists.okfn.org
> Date : 25/06/2013 13:54
> Objet : Re: [ckan-dev] CKAN - DCAT
>
>
> Hi Pascal,
>
> At the moment, I don't believe that any of your questions are implemented,
> but I think all are possible.  But perhaps this should be added to the
> comments about DCAT on the roadmap?  You can add a comment, vote up etc at
> https://trello.com/card/better-support-for-dcat/50b4ef4201d86a1603002077/3
>
> Specifically though:
>
> - Is there a way to define metadata for a ckan catalogue (extracted from the
> production.ini file for example with other sources of information) ?
>
> Not that I've seen.  How much and what type of metadata are you thinking of?
> Could you give an example?
> ##############################"
> In the european DCAT implementation profile the following fields are listed
> as mandatory
> dct:description
> dct:title
> dct:license
>
> Those ones are recommended
> dct:issued
> dct:language
> dct:modified
> foaf:homepage
>
> the last one is optional
> dct:spatial
> ##################################
>
> - Could the revisions stored in CKAN be exported as dcat:catalogRecord ?
>
> Possibly, but this might be a *lot* of data for some users. Do you
> specifically mean in the rdf dump or at runtime?
> #############
> In the rdf dump that would be nice already :)
> #############
>
> - Is there a way to export the entire catalogue as a single dcat:catalogue
> file ?
>
> The rdf-export paster command is pretty simple, I can't imagine it would
> take much to include in it a dcat:catalogue export as well.
> #############
> It would be a nice feature to implement and to ease the creation of a
> dataset that contains the métadata describing all the datasets.
> I will add my comments to the roadmap
> #############
> Hope this helps a little.
>
> Yes thanks for your input
>
> Pascal
>
> Ross.
>
>
> On 25 Jun 2013, at 11:37, p.romain at cg33.fr wrote:
>
> Hi,
> I posted this message in the discussion list but it doesn't seemed to have
> reached its target so I try on this dev list.
>
> With the release of the G8 opendata charter
> (https://www.gov.uk/government/publications/open-data-charter) and the G8
> metadata mapping, a general guideline seems to be emerging from the opendata
> community.
> It echoes the work undergoing at the european commission on the DCAT
> implementation profile
> (https://joinup.ec.europa.eu/asset/dcat_application_profile/asset_release/dcat-application-profile-data-portals-europe-final-draf)
> I tried to map the good practicies contained in this checklist
> http://checklists.opquast.com/en/opendatawith the CKAN-DCAT mapping and
> found that CKAN is a very natural candidate for this implementation profile
>
> good pratice
> SDO                        DCAT                        ADMS
> http://checklists.opquast.com/en/opendata/criteria/20959/
> adms:contactPoint
> http://checklists.opquast.com/en/opendata/criteria/20941/
> sdo:description          dcterms:description        dcterms:description
> http://checklists.opquast.com/en/opendata/criteria/20955/
> dcterms:identifier
> http://checklists.opquast.com/en/opendata/criteria/20942/
> sdo:datePublished      dcterms:issued                 dcterms:created
> http://checklists.opquast.com/en/opendata/criteria/20945/
> sdo:inLanguage           dcterms:language
> http://checklists.opquast.com/en/opendata/criteria/20963/
> dcterms:license
> https://checklists.opquast.com/en/opendata/criteria/20943/
> sdo:dateModified        dcterms:modified         dcterms:modified
> http://checklists.opquast.com/en/opendata/criteria/20976/
> dcterms:accrualPeriodicity
> https://checklists.opquast.com/en/opendata/criteria/20944/
> sdo:publisher               dcterms:publisher         dcterms:publisher
> http://checklists.opquast.com/en/opendata/criteria/20946/
> sdo:spatialCoverage   dcterms:spatial                dcterms:spatial
> http://checklists.opquast.com/en/opendata/criteria/20965/
> sdo:about                    dcat:theme                 dcterms:subject
> http://checklists.opquast.com/en/opendata/criteria/20941/
> sdo:name                    dcterms:title                 rdfs:label
> http://checklists.opquast.com/en/opendata/criteria/20954/
> sdo:version                 dcat:catalogRecord        radion:version
>
>
> CKAN was build from the beginning with the DCAT model in mind and offers a
> natural mapping between the values field in the dataset and resources forms
> and a DCAT record (just append .rdf at the end of each dataset url)
> However in the distribution I use (1.7.2) the RDF dump that produces an rdf
> export of the entire catalogue only produces single record exports
> (when issuing the paster -plugin=ckan rdf-export
> /home/opendata/ckan/dumps/mydump.rdf)
>
> So my question are :
> - Is there a way to define metadata for a ckan catalogue (extracted from the
> production.ini file for example with other sources of information) ?
> - Could the revisions stored in CKAN be exported as dcat:catalogRecord ?
> - Is there a way to export the entire catalogue as a single dcat:catalogue
> file ?
>
> Best,
> Pascal Romain
> @datalocale
>
> __________________________________________________________________
>
> Ce message et toutes les pièces jointes sont confidentiels et établis à
> l'intention exclusive de ses destinataires. Ce message ne constitue pas un
> document officiel. Seuls les documents revêtus de la signature du Président
> du Conseil Général ou d'un de ses délégataires sont de nature à engager le
> Département.
> Toute utilisation ou diffusion non autorisée est interdite. Tout message
> électronique est susceptible d'altération et le Département de la Gironde
> décline toute responsabilité au titre de ce message s'il a été altéré,
> déformé, falsifié.
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
> __________________________________________________________________
>
> Ce message et toutes les pièces jointes sont confidentiels et établis à
> l'intention exclusive de ses destinataires. Ce message ne constitue pas un
> document officiel. Seuls les documents revêtus de la signature du Président
> du Conseil Général ou d'un de ses délégataires sont de nature à engager le
> Département.
> Toute utilisation ou diffusion non autorisée est interdite. Tout message
> électronique est susceptible d'altération et le Département de la Gironde
> décline toute responsabilité au titre de ce message s'il a été altéré,
> déformé, falsifié.
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>