[ckan-dev] Versioning datasets

[Andrew Smith]

Hi Adil,

Versioning is something we needed for our site, so we commissioned an
extension to handle it:
https://github.com/aptivate/ckanext-datasetversions
Each version is a full ckan dataset. The collection of versions are
then linked together using the parent-child relationship which can be
established in the API. It allows both the resources and the metadata
to alter between versions.

Here is a example of it in use:
https://maps.mapaction.org/dataset/irma-jamaica-ma412-v6

Old versions are still accessible as long as they remain public.

It may or may not fit your use case, but pull requests are always welcome. ;-)
I hope that's helpful.
Andy


Andy Smith
Technical Director
MapAction
Mapping for people in crisis


On 18 July 2018 at 11:52, Adil Hasan <adilhasan2 at gmail.com> wrote:
> Hello,
> I have hunted around, but can't seem to find an answer to my question. I
> hope this is the right place to post.
>
> Does CKAN support versioning of datasets?
>
> E.g. if I upload a dataset and
> I then publish the dataset (ie issue a DOI) the dataset is then closed
> so users know they are always accessing the same dataset.
>
> If at a later point in time I decide to update the dataset I should be
> able to create a new version of the dataset that contains the
> additional/changed files.
>
> Is this supported in CKAN? Or, is this something that the API can
> support?
>
> Many thanks,
> adil
> _______________________________________________
> 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