Markus Döring

> So we don't actually need a publishing organization for the resource in the IPT? Not if we want to register it in ChecklistBank. If we want that to happen...

Yes we should explore to do that. Right now we rely on the [name parser to flag names](https://github.com/gbif/name-parser/tree/master/name-parser/src/main/resources/nameparser) as informal, doubtful or no names at all. As this is more...

This isn't auto complete / suggest, but a search and therefore expected behavior - apart from the search with `Gänseblümchen` not returning anything: https://www.gbif.org/species/3117424?vnOffset=20

There is a special property for candidate names in the parsed result: http://api.checklistbank.org/parser/name?q=Candidatus%20Endoriftia%20persephone The name in the label then is quoted entirely.

checklistbank always uses the very latest release, 3.11.0 at this time: https://github.com/CatalogueOfLife/backend/blob/master/pom.xml#L83 The parser exposed at GBIF lacks a bit behind.

The version you mean? You can get that from the API which you can then use to find the corresponding parser and all other dependency versions: https://api.checklistbank.org/version Takes you to:...

The mapping of database fields to the java classes is done in the mybatis sql mapper layer. There are not many write methods, so you cannot easily go back from...

We provide special "simple" dumps that you can load with psql as described here: https://hosted-datasets.gbif.org/datasets/backbone/README.html

We had this desire in the early days of GBIF already and worked with OGC people at TDWG various times, we visited ESRI headquarters for an experimental week. But no...

yes you can, but the UI does not (yet) provide a filter for that. In general the UI does allow you to append other query params though which get added...