[ckan-dev] Versionning / history of resources
hotz
hotz at informatik.uni-hamburg.de
Tue Jul 7 20:48:00 UTC 2015
Hi Stéphane,
we are working on versioning. We have decided for our application to
handle versioning on dataset level not on resource level. Hence,
if a resource of a dataset changes we create a new dataset which
is a new version of the previous dataset containing the not changed
resource.
The basic idea is that a current dataset has the most recent resources, and
older versions of that dataset are related to it by the CKAN-relation
child-of (and
backward parent-of). The historical resource files have to be stored
somewhere
in an archive.
Hope that helps,
Lothar
Am 07.07.2015 um 15:23 schrieb Stéphane Guidoin:
> Hello,
>
> Some best practice in terms of open data raise the fact that resources
> (files) should be versionned and it should be possible to access past
> version of a resource. In an ideal world, the resource itself should
> contain historical trail (e.g date when a record was created/deleted)
> but it's not always possible.
>
> From my ckan understanding, CKAN does not support that out of the box
> (the only option is to add new resources with dates but you quickly
> end up with dozens of resources in a dataset). Does someone has
> already evaluated how to do that? For example have a resource and a
> link/button to access historical file?
>
> Stéphane
> _______________________________________________
> 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
--
Dr. Lothar Hotz
HITeC e.V., University of Hamburg
Vogt-Kölln-Str. 30, 22527 Hamburg
Tel: 040/42883-2605; Fax: 040/42883-2572
E-Mail: hotz at informatik.uni-hamburg.de
WWW: www.hitec-hh.de
Private page: kogs-www.informatik.uni-hamburg.de/~hotz
More information about the ckan-dev
mailing list