Markus Döring

Results 267 comments of Markus Döring

can you give an example of an unclear ISO date? I would have thought it is rather straight forward if it is proper ISO. The dirty parsing happens only once...

I wonder if we can support negation though. It is part of dataset and species freetext queries already: http://api.gbif.org/v1/dataset/search?q=!bird

not coordinate missing = lat is not null: also sth we cannot search for currently as there is no query for (not) NULL

I agree Christian. From a JSON API perspective a possible range given in 2 fields is simpler to use. From a Java perspective I quite like a single date Range...

The IPT rank vocabulary is already far outdated as you can quickly see by the last commmits to the rank enum: https://github.com/gbif/gbif-api/commit/3826c67276b18dbaf1eae6b35e7334360bf3b9a5#diff-aa13cc02e499b7a41c36fc3741978912 If we need to keep the 2 in...

@MattBlissett are these IPNI ranks exposed anywhere? 500 is pretty bad

we have [186 entries](http://api.gbif.org/v1/enumeration/language) now and use Locale to retrieve an english and native title. That would also need to be explicitly listed in the extended enum

The official list has only english titles: https://iso639-3.sil.org/sites/iso639-3/files/downloads/iso-639-3.tab

I've quickly tried an extended enum and its not gonna work. Compilation error "Java code too large"

+1 for Option1 and removal of ymd