[ckan-dev] Global Resource Identifier: is it possible?

[Adrià Mercader]

Hi,

If I understood Alessandro correctly, I think he was asking about whether
CKAN dataset can be safely uniquely identified using their ids. In theory
the answer is yes, because as Alessio pointed out we use UUIDs for them,
but in some cases like the ones Steven mentions (CKAN-CKAN harvesting, the
same id is shared across instances). You could argue that that still is the
same dataset, just living in two different portals, but if you want to
distinguish these datasets you might need to use a hash of id + site url or
something similar.

Hope this helps,

Adrià

On 7 April 2015 at 12:40, Steven De Costa <steven.decosta at linkdigital.com.au
> wrote:

> Yep, but I was wondering if Alessandro was talking about a DB that
> potentially had IDs from different CKAN instances. If so the you'd want
> to also match on the harvest source ID/URL.
>
> For example, on data.gov.au and data.sa.gov.au each Solr service picks up
> results from either of the two. More instances canbe linked into the
> results without conflict too.
>
>
> On Tuesday, April 7, 2015, Alessio Dragoni <alessio.dragoni at gmail.com>
> wrote:
>
>> aĺ the IDs in CKAN are UUID
>> On Apr 7, 2015 1:06 PM, "Alessandro Portosa" <alessandro.portosa at eng.it>
>> wrote:
>>
>>> Hello, I have a question on how the resource (or even the dataset) ID is
>>> generated.
>>> Context: I have integrated CKAN inside an analysis tool, where resources
>>> medata can be saved locally.
>>> The tool should not be tied to a specific CKAN instance, but the user
>>> can change the target CKAN url (datahub.io, data.gov, and so on). My
>>> problem is: I would like to globally identify resources and dataset, but
>>> I'm not sure how the ID is built. Can anyone give me explanation about
>>> that? It is really important for us, because metadata are saved in our DB
>>> using CKAN resource ID as primary key and I need to be sure that there will
>>> be no conflict if using different CKAN instances.
>>>
>>> Alessandro.
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>
> --
> *STEVEN DE COSTA *|
> *EXECUTIVE DIRECTOR*www.linkdigital.com.au
>
>
>
>
> _______________________________________________
> 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/20150407/ffbcb458/attachment-0003.html>