[ckan-dev] Freshness field

Dan Mihaila danmihaila at gmail.com
Thu Oct 20 13:17:04 UTC 2016


Thank you both for replies, I will check links today.



*Dan Mihaila*, IT Consultant
(M) +40 722 502 304 • (GTalk) dan.mihaila at gmail.com • (Skype) carcotelul
• (Twitter) dan_mihaila • (Yahoo) carcotelul
  <dmihaila at dginternational.org>

On Thu, Oct 20, 2016 at 3:56 AM, Steven De Costa <
steven.decosta at linkdigital.com.au> wrote:

> We also implemented similar fields for  Australian data portals. The
> extension is here:
> http://extensions.ckan.org/extension/agls/
>
> Cheers,
> Steven
>
> *STEVEN DE COSTA *|
> *EXECUTIVE DIRECTOR*www.linkdigital.com.au
>
>
>
> On 20 October 2016 at 03:41, Ian Ward <ian at excess.org> wrote:
>
>> We implement some of these fields in our dataset schema on the Canadian
>> portal.
>>
>> For our "freshness" field I tried to use ISO 8601 repeating intervals as
>> the values stored where they fit our controlled list:
>> https://github.com/open-data/ckanext-canada/blob/canada-v2.
>> 5/ckanext/canada/schemas/presets.yaml#L1871-L1948
>>
>> CKAN includes a date on resources that is updated when new files are
>> uploaded, but nothing for linked resources (all our resources currently)
>> The update date fields we have must be updated manually or harvested from
>> systems that track it.
>>
>> On Wed, Oct 19, 2016 at 1:12 PM, Dan Mihaila <danmihaila at gmail.com>
>> wrote:
>>
>>> Hello,
>>> We want to implement in our HDX data portal (http://data.humdata.org/)
>>> a field (data freshness) which will help users to specify what is the
>>> interval of time the data will refresh or a resource will be updated.
>>> Basically we want to add at dataset level the data_update_frequency field.
>>> Also there are 2 important fields that can help us trying to see what
>>> resources needs updates or updated.
>>>
>>>    1. data_update_frequency  - Dataset expected update frequency  -
>>>    Shows how often the data is expected to be updated or at least checked to
>>>    see if it needs updating
>>>    2. dataset_date  -  Dataset date  -  The date referred to by the
>>>    data in the dataset. It changes when data for a new date comes to HDX so
>>>    may not need to change for minor updates
>>>    3. revision_last_updated  -  Resource last modified date  -
>>>    Indicates the last time the resource was updated irrespective of whether it
>>>    was a major or minor change
>>>
>>>
>>> Are you aware of any extension that is doing this? In case there is no
>>> extension (I couldn't find it) are any other people/projects interested in
>>> such an extension?
>>>
>>> *Dan Mihaila*, IT Consultant
>>> (M) +40 722 502 304 • (GTalk) dan.mihaila at gmail.com • (Skype) carcotelul
>>> • (Twitter) dan_mihaila • (Yahoo) carcotelul
>>>   <dmihaila at dginternational.org>
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>> _______________________________________________
>> 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
>>
>>
>
> _______________________________________________
> 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/20161020/85829ddc/attachment-0003.html>


More information about the ckan-dev mailing list