[ckan-dev] last_modified field in resources

[Brook Elgie]

Hi Alex,

Sorry for the delay.

You are right, last_modified wasn't updated by CKAN core at all until CKAN
2.5. Before 2.5, it relied on separate extensions such as ckanext-archiver.
It should be used with regard to the resource data, not changes to the
resource metadata.

Some background:
https://github.com/ckan/ckan/issues/1874 - changes to CKAN core to update
last_modified during create/update of resource file
https://github.com/ckan/ckan/issues/3028 - discussion about UI labels for
last_modified, revision_timestamp, etc.

Brook

On 28 June 2016 at 17:17, Alex Gartner <alexandru.gartner+ckan at gmail.com>
wrote:

> Hello,
>
> What is the meaning of the *last_modified *field ? And why isn't it
> automatically populated when you create / update a *resource ?*
>
> According to the changelog
> <http://docs.ckan.org/en/latest/changelog.html?highlight=last_modified>,
> it seems that in the latest version, the field is only populated for
> uploaded resources.
>
> We wanted to store somewhere when a resource was last modified (in CKAN).
> Is the last_modified property in CKAN not the right place ? Maybe it refers
> to when the data inside the resource was last changed and thus needs to be
> manually set ?
>
> I guess we could use the activity history/stream to get the same
> information but it seems a bit more complicated, especially when using the
> API.
>
> Thanks,
> Alex
>
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20160701/1e329942/attachment-0002.html>