[ckan-dev] Connecting different versions of data packages

[David Read]

Hi Rustam,

The boundary between packages and resources is not exact, but for me
the key thing is in the metadata. If these two APIs have basically the
same title, tags, functionality, author etc.etc then they should be in
the same package, just as two separate resources.

If however there are significant differences in the metadata then they
should be different packages. We have a feature called 'related
packages' that creates explicit links. Here's more info:

http://trac.ckan.org/ticket/253

We've not done an edit interface yet as it's still pretty prototype,
but it has been set via the API:
http://ckan.net/package/bio2rdf-go

David

On 14 July 2011 16:14, Rustam Mehmandarov <minspamboks at gmail.com> wrote:
> Hi all,
>
> I am looking for a functionality for connecting several packages
> together as different versions of the same source. For example, of you
> add a data package describing some kind of API v.1.0, and then v.2.0
> is released. Then, I'd like to create another data package for this
> new version and mark that those two packages are related. Does CKAN
> offer any functionality for that already?
>
> I was thinking of implementing this with tags, but I think that it is
> not really easy to explain to users that they should use the same
> field both for linking and tagging...
>
> Any suggestions?
>
> Thanks,
> Rustam
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>