EventDate on related records

[MortenHofft]

Now that we are changing the API to better reflect ranges, I guess that should be reflected in clustered records as well?
I mean this endpoint https://api.gbif.org/v1/occurrence/4506846570/experimental/related
I do not believe it is automatically processed the same?

[MattBlissett]

https://api.gbif.org/v1/occurrence/1019610912/experimental/related

An event date of 1833 seems to have been interpreted as 1833ms after the Unix epoch. It's not using an ISO 8601 date either, there should be a T.

[bwakkie]

@MattBlissett
Not sure what you are saying: eventDate "1833-01-01 00:00:00" so no unix time? (or maybe changed in the mean time?)

1883 cannot be converted to ISO 8601 date. So only year need to be filled.

Here you see the common error by adding 01 for month and day (sometimes you'll see 12-31)
Most of the time historically this is just a year but a date had to be entered.