Temporal Coverage for dataset: Need to set start date but no end date

[petzlux]

Detailed Description

In the dataset creation form, one can set a start date and end date for a dataset. But if a start date is set, an end date has to be set as well. This not always makes sense. Currently, in the data entry form, it is required to set both start and end date.

Context

For example for meteorological realtime data, data collection started sometime in the past, but will be collected for the foreseeable future. So in this case, we can define a start date, but no end date.

Possible Implementation

Remove the obligation to set an end date, when a start date is set.

[ColinMaudry]

For temporal request, the Memento protocol offers a standard way for a client to GET a resource with a datetime factor to server.

https://www.w3.org/blog/2016/08/memento-at-the-w3c/

Github, Wikipedia, Google Search, among others, support the accept-datetime header for their core services.

(@noirbizarre requested this input a while ago :blush:)