[ECODP-dev] Update of metadata provided by "old" data providers

Wed Jun 19 11:35:48 UTC 2013

Hi,

Thank you for the additional information. If the datasets have been
imported via the CKAN API (rather than rdf2ckan) and assigned to a
publisher they can be edited by any user who's part of the same publisher.
Therefore if you create users within the relevant publishers they will be
able to edit the meta-data.

Best,

Darwin

---------- Forwarded message ----------
From: ISOARD Olivier (OP) <Olivier.ISOARD at publications.europa.eu>
Date: 19 June 2013 10:40
Subject: RE: Update of metadata provided by "old" data providers
To: Darwin Peltan <darwin.peltan at okfn.org>, Bert Van Nuffelen <
bert.van.nuffelen at tenforce.com>, Project list for EC ODP CKAN project <
ecodp-dev at lists.okfn.org>
Cc: "ZAJAC Agnieszka (OP)" <Agnieszka.ZAJAC at publications.europa.eu>, "HOHN
Norbert (OP)" <Norbert.HOHN at publications.europa.eu>

 Hi,****

** **

Well….****

** **

**Ø  **During the prototyping phase, pilot data providers ingested dataset
into ODP database located @10F premises. Some using batch mode, others
using interactive interface****

**Ø  **At some point in time (end 2012), that records have been exported
from 10F instance and imported into PROD instance for the opening, using
special script. Because that special script used the batch mode to
re-import the data, all these datasets belong now to "api" user.****

** **

The question now is to define how those data providers may come on ODP PROD
and update their data sets. ****

** **

**Ø  **For those who published it initially using batch mode, this
shouldn't be a problem, they just have to re-submit new version of RDF
package****

**Ø  **For the ones that came initially via interactive interface (web site
form), it is another story because even if we create dedicated account for
them (which is planned), they will not have access to past published
dataset (which belong to "api" because of the migration)****

** **

So, here the question debated below: In order to solve the issue for data
provider who was using the website interface for publishing during
prototyping phase, would it be possible (even by script) to move existing
data set from "api" to another account the data provider may access ?****

** **

Hope this is clearer.****

Olivier****

** **

** **

*From:* Darwin Peltan [mailto:darwin.peltan at okfn.org]
*Sent:* Wednesday, June 19, 2013 11:23 AM
*To:* Bert Van Nuffelen; Project list for EC ODP CKAN project
*Cc:* ISOARD Olivier (OP); ZAJAC Agnieszka (OP); HOHN Norbert (OP)

*Subject:* Re: Update of metadata provided by "old" data providers****

** **

Hi,****

** **

>From the email thread below it's a bit unclear to me what you'd like to
change here. If you can summarise please we can advise. ****

** **

Best,****

** **

Darwin****

****

*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 19 June 2013 08:29, Bert Van Nuffelen <bert.van.nuffelen at tenforce.com>
wrote:****

Hi Olivier,

I forward this question to Darwin. So far I am unaware of an easy
track for doing such kind of changes.
@Darwin, can you take this up for this afternoon?

kind regards,

Bert

2013/6/19 ISOARD Olivier (OP) <Olivier.ISOARD at publications.europa.eu>:
> Hi,
>
> And what about the possibility from CKAN to change the owner of a
dataset? If this is possible, then we can imagine re-dispatching these
datasets, initially migrated under "api", to the actual right provider,
once we will have created corresponding separated accounts?
>
> Olivier
>
> -----Original Message-----
> From: Bert Van Nuffelen [mailto:bert.van.nuffelen at tenforce.com]
> Sent: Wednesday, June 19, 2013 9:25 AM
> To: ZAJAC Agnieszka (OP)
> Cc: HOHN Norbert (OP); ISOARD Olivier (OP)
> Subject: Re: Update of metadata provided by "old" data providers
>
> Hi Agnieszka,
>
> a quick reply from my knowledge:
>
> In general we were involved here only in validation and a migration
> process from the release 00.05.0x to release 00.06.0x
> For EEA I am 100% sure we only validated the rdf2ckan package.
> For the others there has been a migration from an old DB to a new via
> the api. That could possible be a reason for not able to update them
> as datasets inserted via the api are not editable by a user.
>
> kind regards,
>
> Bert
>
> 2013/6/19 ZAJAC Agnieszka (OP) <Agnieszka.ZAJAC at publications.europa.eu>:
>> Hello Bert,
>>
>> During tomorrow's telco we would like to raise a new subject – to find
out
>> how to update metadata of the data providers that were sending them
directly
>> to you can be done.
>> It concerns Environment Agency and a few DGs eg. Regio, EAC, Empl, Budg
>>
>> Regards,
>>
>> Agnieszka Zając
>> Open Data Portal Section
>> _________________
>> Publications Office of the European Union
>> Dissemination and Reuse Directorate
>> Unit C1 Common Portal and Open Data Portal
>>
>> L-2985 Luxembourg • LUXEMBOURG
>> Tel: +352 2929.42834
>> agnieszka.zajac at publications.europa.eu
>> http://publications.europa.eu
>> http://open-data.europa.eu
>>
>>
>>
>
>
>
> --
> 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

--
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****

** **
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.okfn.org/mailman/private/ecodp-dev/attachments/20130619/106a3beb/attachment.html>