Truncate date ranges?

[matthewhanson]

From Rob:

It would be useful, especially for fetching, if we could check all date ranges against the asset start and end dates. Having said that, do we have a convention for specifying asset availability? Sorry this is actually two issues. Should it be something like
_availability = {'start_date': '2001-01-06', 'end_date':'2009-11-04'} _availability = {'start_date': '2001-01-06', 'end_date':''} # indicates available up to present
or to get fancy _availability = {'start_date': '2001-01-06', 'end_date':'', 'latency':100'} # indicates there is a 100 day delay in availability

[matthewhanson]

This does make sense to have in core as it's generally applicable.
I will - add stub variables to the core Asset class that define some defaults for availability to be overridden by sensors - Bound the requested dates by "start_date" and "end_date - latency" in the inventory init
I think that's really all that will be needed

[ircwaves]

Seems like maybe this should be required in data.core. Is there a case where one would not want to require an asset to have startdate and latency?