You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There looks to be a mismatch in date displayed when I look in our hosted portal in related resources tab. In this record of Cryptotis thomasi it showns 11 may for the related occurrence:
And it looks weird considering that they are supposed to be clustered because they have some equal information.
I haven't looked yet, but I'm 99% sure it is because it is using the browsers timezone when formatting the date. I probably didn't properly specify that it should use UTC. And dates used to include the timezone, but after a change within the last year in how we handle dates, precision and ranges, then the timezone Z is not longer included in the date string. And so the formatting falls back to using local time.
May I ask what operating system (windows/mac), browser(chrome,safari,firefox,internet explorer7) and browser version you are using? The library we are using depends on the browser being able to understand timezones.
I've looked and annoyingly I do not really get it. The first time shows correctly with hours. And the second that only has date resolution shows the wrong date. Neither of them has a time zone specified. So I would have expected the browser to handle them the same.
Anyhow, I've tried to be more explicit and add Z when not specified to the interpretation. And then similarly define it as UTC when displayed. That should hopefully fix it. Could you please check the behaviour in staging?
There looks to be a mismatch in date displayed when I look in our hosted portal in related resources tab. In this record of Cryptotis thomasi it showns 11 may for the related occurrence:
And it looks weird considering that they are supposed to be clustered because they have some equal information.
But when I look for that occurrence in GBIF it shows 12 of may: https://gbif.org/occurrence/3710474697
And it is shown correctly in occurrence search in GBIF
No idea why it is showing some dates mismatched by one day, but other records were behaving similarly.
Thanks in advance,
The text was updated successfully, but these errors were encountered: