Datetime processing isn't handling datetimes with miliseconds.

[greg-slater]

Where a datetime has miliseconds but no 'Z' at the end the date conversion is failing because there isn't a pattern to match this.

In the Camden brownfield land endpoint datetime values are given like this example "2017-12-22T00:00:00.000", but the pipeline is returning an "invalid date" issue for these.

It looks a new pattern should be added to the list used in date.py: https://github.com/digital-land/digital-land-python/blob/main/digital_land/datatype/date.py#L13

as an example:

from datetime import datetime

# converts fine
print(datetime.strptime("2017-12-22T00:00:00.000", "%Y-%m-%dT%H:%M:%S.000"))

# doesn't convert
print(datetime.strptime("2017-12-22T00:00:00.000", "%Y-%m-%dT%H:%M:%S.000Z"))