Markus Döring

thanks @afuchs1 this is very helpful. Even if nomenclatural data wants to be objective and rule based there might be different opinions and for sure wrong evaluations of rules or...

My immediate reaction would be to place the novum status on the TN as it comes in from the TNU. The problem only arises if the TN is normalised; shared...

I agree. Even though it feels silly I have the same reservation for UUIDs. That's why we decided in COL to use short alphanumerical strings that try not to resemble...

See also https://github.com/jankotek/mapdb/issues/871

I am sure we index datasets having measurements and facts. But I am afraid we do not allow searching for them at this stage. They should be exposed in the...

Example records: https://demo.gbif.org/occurrence/202057537 https://demo.gbif.org/occurrence/202057542 http://api.gbif.org/v1/occurrence/202057537/verbatim

indeed. The docs are old and outdated. @MortenHofft can you update them according to the [ParsedName class](https://github.com/gbif/gbif-api/blob/master/src/main/java/org/gbif/api/model/checklistbank/ParsedName.java#L47)? Or let me know where/how to do that

Have you thought about creating a custom ISODate type/class instead that we would use for the eventDate field and potentially others? It could serialize into the real ISO format

As all 3 are key properties of an occurrence, the who where when, Id propose to flag proper issues for that in all 3 cases. How about TAXON/DATE/COORDINATE_MISSING? Alternatively no...

but it would allow us to keep the single dwc term as a java property which is nice. Do you think ser/de really is an issue? we need to parse...