Morten Høfft
Morten Høfft
It might not be the solution, but https://www.tdwg.org/theme/js/theme.js restyles the page as the last action. If the anchor has executed before that (and it might very well), then the position...
Same here I see `[email protected] requires a peer of webpack@^1.9.11 but none was installed.`
> Other parsers (e.g. ETE Toolkit) don't have issues with single quotes in the node names. Single quotes do not work on ETE either. Or rather, it appears to work...
Same as https://github.com/gbif/portal-feedback/issues/4119 And similar to https://github.com/gbif/checklistbank/issues/264
This looks like an API issue API example https://api.gbif.org/v1/species/search?q=G%C3%A4nse&qField=VERNACULAR Website equivalent: https://www.gbif.org/species/search?q=G%C3%A4nse&qField=VERNACULAR None of them show `Gänseblümchen` https://api.gbif.org/v1/species/search?q=G%C3%A4nsebl%C3%BCmchen&qField=VERNACULAR
Ah, sorry @mdoering I completely forgot that, despite being my own implementation. For the LAND portal, @jholetschek wanted a scientific name filter that also supported vernacular names. To support that...
Wasn't it ported to ElasticSearch last year before this issue was created?
I suspected. Perhaps that is a better option. A suggest that supports vernacular names. And an option to prefer accepted. Let me try to specify it and come back. Then...
So far gbif-web project has been using * `!issue=ZERO_COORDINATE` for NOT. * `issue=*` for NOT_NULL (syntax same as a wildcard search) * `!issue=*` for NULL * `recordedBy=*humboldt` for LIKE (could...