[ckan-dev] "Permanence" of the data: how can CKAN help me ?

[Antoine Logean]

Hi everybody,

I already ask this question to the CKAN-discuss list. But it seems that this CKAN-dev list is much more "active". So I ask the question here again. Sorry for the cross posting …

My question is related to the support and implementation of the "permanence" [1] principle of Opendata within CKAN:

Let say you have a data provider that update its data every month:
- what is the best way in CKAN to keep track of the old versions of the data ?
- how can I define in CKAN different versions of the same dataset ?
- how can I inform the consumer that there is a new version of the data, that the data structure or interface has changed ? Does CKAN provide here some standard processes ?

I am interested of any experiences or informations related to this issue.

Thanks for your help

Antoine Logean

[1]  "… 9. Permanence: The capability of finding information over time is referred to as permanence. Information released by the government online should be sticky: It should be available online in archives in perpetuity. Often times, information is updated, changed or removed without any indication that an alteration has been made. Or, it is made available as a stream of data, but not archived anywhere. For best use by the public, information made available online should remain online, with appropriate version-tracking and archiving over time."
see http://sunlightfoundation.com/policy/documents/ten-open-data-principles/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130122/51870115/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130122/51870115/attachment.sig>