[ECODP-dev] instructions to upload new information from the vocanbulary

Darwin Peltan darwin.peltan at okfn.org
Mon Jun 24 11:40:04 UTC 2013


Hi Jurgen,

Hope you had a good weekend. John already replied to this thread. I've
copied his reply below for reference.

==========

Hi Bert,

Those JSON files were not intended to be the official way of updating the
vocabularies. We use them to do the initial database setup, but I did not
even know that you had your own copy of them in the RPM. However, as all of
this information is stored in the database, it can be updated using the API.

To view or update vocabularies, see:
http://docs.ckan.org/en/ckan-1.8/apiv3.html#ckan.logic.action.get.vocabulary_list
http://docs.ckan.org/en/ckan-1.8/apiv3.html#ckan.logic.action.get.vocabulary_show
http://docs.ckan.org/en/ckan-1.8/apiv3.html#ckan.logic.action.create.vocabulary_create
http://docs.ckan.org/en/ckan-1.8/apiv3.html#ckan.logic.action.update.vocabulary_update

To view or update translations, see:
http://docs.ckan.org/en/ckan-1.8/apiv3.html#ckan.logic.action.get.term_translation_show
http://docs.ckan.org/en/ckan-1.8/apiv3.html#ckan.logic.action.update.term_translation_update_many

The licenses file is slightly different. That is not stored in the
database, and is read by CKAN when it starts up. So you can simply edit
that file and then restart CKAN to change the license information.

Regards,
John

*Darwin Peltan*

*Project Manager  |  skype: darwinp  |  twitter:
@darwin<http://twitter.com/darwin>
*

*The Open Knowledge Foundation <http://okfn.org/>*

*Empowering through Open Knowledge*

*http://okfn.org/  |  @okfn <http://twitter.com/OKFN>  |  OKF on
Facebook<https://www.facebook.com/OKFNetwork> |
Blog <http://blog.okfn.org/>  |  Newsletter<http://okfn.org/about/newsletter>
*
*
CKAN | http://ckan.org | @ckanproject <http://twitter.com/ckanproject>
|open source data management platform
*


On 21 June 2013 14:50, Jurgen Vannerom <jurgen.vannerom at tenforce.com> wrote:

> Gents,
>
> Has there been a respone to the below already ?
> Don't recall having seen it. Maybe I've missed something ...
>
> Best Regards,
>
> Jurgen Vannerom
> Project Manager
>
> E-mail:   jurgen.vannerom at tenforce.com
> Phone:
> Mobile: +32 497591362
> Skype:   Belgium2003
>
>
>
> -----Original Message-----
> From: ecodp-dev-bounces at lists.okfn.org
> [mailto:ecodp-dev-bounces at lists.okfn.org] On Behalf Of Bert Van Nuffelen
> Sent: woensdag 12 juni 2013 12:38
> To: Project list for EC ODP CKAN project
> Subject: [ECODP-dev] instructions to upload new information from the
> vocanbulary
>
> Hi,
>
> we have in the rpm a directory /applications/ecodp/users/ecodp/ckan/data
> which contains the next json files
>
> licenses.json
> odp-accrual-periodicity.json
> odp-dataset-status.json
> odp-dataset-type.json
> odp-documentation-type.json
> odp-interoperability-level.json
> odp-license.json
> odp-temporal-granularity.json
> po-corporate-bodies.json
> po-countries.json
> po-languages.json
>
>
> can you provide us with instructions / configurations requirements so that
> PO can update these themselves. Note that this is working in release
> 00.07.50/00.08.04 as the po-corporate-bodies.json is via a script
> updatable.
>
> Can you provide information on this .
>
> thanks,
>
> 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
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
>
> _______________________________________________
> Ecodp-dev mailing list
> Ecodp-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ecodp-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130624/4f5f036d/attachment.html>


More information about the ecodp-dev mailing list