[ckan-dev] Resource.hash

[John Glover]

Hi Toby,

1) If you want to check an external resource regularly to see if it has
changed, how would you do that? Currently we store the hash in that field
and then update it when necessary. It could also be used by people that
want to verify that they have downloaded the correct file.

2) Are you referring to when the external resource is changed or when the
CKAN resource is changed?

3) It's not ideal, but I'm not sure how else you are proposing to handle
this. It should not be editable through the WUI though.

4) Not without breaking things.

John


On 29 May 2013 13:52, Toby Dacre <toby.okfn at gmail.com> wrote:

> Resources have a hash field.
>
> This is used by the datastorer to see if a resource has changed I am
> not sure why last modified is not used here.
>
> We have a failing test that seems to be related to this
> https://github.com/okfn/ckan/issues/818 as the results are ordered by
> hash which I think may be ''
>
> So my questions are.
>
> 1) why do we have this field/ what is the usecase ?
>
> 2) If it should change when the resource is updated - should this not
> be moved into the model so it is always done?
>
> 3) should it be even changable by a user?
>
> 4) Can we just kill it?
>
>
> --
> Toby Dacre
>
> The Open Knowledge Foundation
>
> Empowering through Open Knowledge
> http://okfn.org/  |  @okfn
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130529/f220e996/attachment-0001.html>