You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In CKAN 2.5.1 the last_modified field is getting updated when doing an upload via UI. We also need to check the API upload.
Data team needs this field to be updated when a resource is uploaded/created/modified/etc.
The main task is to check if we can bring the code from 2.5.1 into our version or to make our own action.
Also, after research we could use "revision_timestamp" from resource_revision to update the field with last action for a resource.
The text was updated successfully, but these errors were encountered:
I see that there is a case in which uploaded files get that field populated here but it doesn't seem to be the "default" case. Also, it doesn't deal with API resources in any way as far as i see.
I think, we could change the validation step to update that field automatically.
In CKAN 2.5.1 the last_modified field is getting updated when doing an upload via UI. We also need to check the API upload.
Data team needs this field to be updated when a resource is uploaded/created/modified/etc.
The main task is to check if we can bring the code from 2.5.1 into our version or to make our own action.
Also, after research we could use "revision_timestamp" from resource_revision to update the field with last action for a resource.
The text was updated successfully, but these errors were encountered: