Closed gbif-portal closed 9 months ago
This is a published data error, see https://api.gbif.org/v1/dataset/24baf0da-60a9-4a13-99d7-a8c860c3cb30
Though that could mean it's an IPT problem.
Well spotted @MattBlissett There are 2 issues.
For the second issue, the source is the IPT, which is older than the EML specification's guidance on user identifiers.
I have made an issue in the GBIF API, and also fixed it. It has the background on the EML standard: https://github.com/gbif/gbif-api/issues/30
I've also made an issue for the IPT: https://github.com/gbif/ipt/issues/1424
@rpfigueira, Tim and I will decide whether to deploy this small fix to production. We don't usually make production changes on a Friday, especially the Friday before the governing board meeting.
We've decided not to deploy today, there are other changes in the way of a clean deployment.
@rpfigueira, if you'd like the user identifiers on the Azorean dataset to appear correctly, please write them like this in the IPT and republish:
GBIF's processing concatenates the two parts.
the loooong ids now wrap
URL formatting on user IDs
A bit of formatting love is needed on the user IDs on this page. This is a wonderful example of ORCID use from a new publisher
User provided contact info: @timrobertson100 System: Chrome 69.0.3497 / Mac OS X 10.13.5 User: See in registry Referer: https://www.gbif.org/dataset/24baf0da-60a9-4a13-99d7-a8c860c3cb30 Window size: width 1690 - height 1180 API log&_a=(columns:!(_source),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499')),sort:!('@timestamp',desc))) Site log&_a=(columns:!(_source),index:'prod-portal-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499')),sort:!('@timestamp',desc))) System health at time of feedback: OPERATIONAL