[ckan-dev] Versionning / history of resources
Stéphane Guidoin
stephane.guidoin at gmail.com
Thu Jul 9 01:01:31 UTC 2015
Thanks Lothar,
That's an interesting model! If you end up with a more stable stable
that you can publish, please share it on the mailing list! We are not
starting development very soon, we are mainly gathering needs and
existing extensions code that could fulfill it.
Thanks
Stéphane
On 2015-07-07 17:13, hotz wrote:
> We are currently developing it and have no repo.
> Here is a (still buggy) development side:
> http://hitec-race.informatik.uni-hamburg.de/dataset/3d-stadtmodell4
>
> "Frühere Version" means "Earlier Version" and
> "Nachfolgende Version" means "Succeeding Version".
> Click on "Nachfolgende Version" and you will be moved to the next
> dataset, etc.
> Those datasets have all the same title (still) and nearly no
> difference (because of bugs).
> However, by these links the user can navigate through the versions.
> Do not click on "Frühere Version" this is linked to another wrong
> dataset, we are under
> development....
> Best,
> Lothar
> Just say "Lothar" (which is the surname) , that would be enough ;-)
>
>
> Am 07.07.2015 um 22:59 schrieb Stéphane Guidoin:
>> Thanks Hotz!
>>
>> Do you have a repo or some code you have developed for that? Or
>> something that I could access to see how it behaves?
>>
>> Stéphane
>>
>> 2015-07-07 16:48 GMT-04:00 hotz <hotz at informatik.uni-hamburg.de
>> <mailto:hotz at informatik.uni-hamburg.de>>:
>>
>> 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 <mailto: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
>> <mailto:hotz at informatik.uni-hamburg.de>
>> WWW: www.hitec-hh.de <http://www.hitec-hh.de>
>> Private page: kogs-www.informatik.uni-hamburg.de/~hotz
>> <http://kogs-www.informatik.uni-hamburg.de/%7Ehotz>
>>
>> _______________________________________________
>> ckan-dev mailing list
>> ckan-dev at lists.okfn.org <mailto: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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150708/716c013f/attachment-0003.html>
More information about the ckan-dev
mailing list