[ECODP-dev] rdf2ckan json create statement

Bert Van Nuffelen bert.van.nuffelen at tenforce.com
Thu Jan 10 08:54:42 UTC 2013


Hi John,

which field in the json should be set so that the dataset it being
created in the CKAN database with a human generated url instead with
the uuid generated by CKAN.

@ Dimitrios can you show John which fields we fill for the
create-json/update-json REST request.

from ODP-187:

"
While evaluating the possibility to grab and collect valuable
information on which are the most visited pages on the website, we
discovered that datasets loaded using RDF2CKAN have URLs not user
friendly readable....while dataset published by user directly from the
website do have.

In case of manual publishing, the dataset title is used to define the
URL (correct)
In case of RDF2CKAN upload, the URL looks built based on an internal
ID (not correct)

Example:

> URL of dataset loaded in interactive mode (user account)

EU Cohesion Policy 2007-2013 : Funds allocated by Member State
http://open-data.europa.eu/open-data/data/dataset/Erasmus2011-2012

> URL of dataset loaded in batch mode (RDF2CKAN)

Quarterly cross-trade road freight transport by type of transport (1
000 t, Mio Tkm)
http://open-data.europa.eu/open-data/data/dataset/00YYPa7FUadFAd4HH4quTw

So, in order to be coherent, also have readable statistics on visited
pages, all the dataset URLs have to be built on the mechanism used in
the manual mode, meaning using the words of the title as bricks.
(as looks the case on UK ODP website, also based on CKAN)

PS: Even better, if this this URL will not change if data provider
change the DS title later on, this would be OK.
"

Bert



-- 
Bert Van Nuffelen

Semantic Technologies Software Architect at TenForce
www.tenforce.be

Bert.Van.Nuffelen at tenforce.com
Office: +32 (0)16 31 48 60
Mobile:+32 479 06 24 26
skype: bert.van.nuffelen




More information about the ecodp-dev mailing list