namgk / ckan-timeseries Goto Github PK

users should be able to specify the timestamp in their records, this override the auto generated one.

For the custom format of fromtime/totime (e.g "last 1d,2m"), no timezone information is specified.

To fix this, either add zone information on the query so it becomes something like "last 1d,2m+00:08", this looks messy.

Other way is to introduce new timezone parameter, maybe "timezone", which if missing, UTC will be used as default.

It would be interesting if one can query with a fromtime value and totime to be relatively specified to fromtime.

For example a query like this might be good to have:

fromtime: "2016-10-18"
totime: "next 1d"

For large table, it takes very long time for a datastore resource to be displayed on CKAN web interface. This is due to the count operation on result returned from database. The web interface does not impose any filter so basically all records are returned and limit is applied. Then the count operation is applied to a large number of records.

Consider to calculate count based on max id and min id since id is auto-incremental.

All newly created resources should have a default retention policy attached to it specify when the old data are to be deleted.

An user can specify his own policy, but the period must be shorter than the default one, otherwise, the default one will be used.

Refer to: https://github.com/namgk/ckan-timeseries/wiki/Design:-retention-policy