resolving "Pelargonium × hortorum" causes exceptions/ errors

[dimus]

@jhpoelen commented on Fri Dec 23 2016

When resolving "Pelargonium × hortorum" using http://resolver.globalnames.org, the following error page is shown: We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly.

Original errors where observed when resolving names using the resolver api. Other examples include: Citrus × paradisi, Acer × freemanii, Malus ×domestica, Abelia × grandiflora, and Platanus × acerifolia.

---

@alexander-myltsev commented on Tue Jan 24 2017

This is not the issue of gnresolver. @dimus , would you figure out where to put it best?

---

@dimus commented on Tue Jan 24 2017

Yes, I'm moving it to gni. May be it is better to wait with this one until we have gnresolver running. @jhpoelen , how important it is for you?

We do not deal with hybrids in gnresolver yet as well :-/

[jhpoelen]

@dimus not a huge issue but generates a bunch of distracting noise and false negatives. How hard is it to fix this?

[dimus]

Hybrids add an additional level of complexity, because they match more 'fuzzy' than non-hybrids. For example if we see Pelargonium hortorum --- should we match it to xPelargonium hortorum or Pelargonium x hortorum or Pelargonium x hortorum and what about Pelargonium hortorum x P. domesticum or Pelargonium domestcum x Pelargonium hortorum? They all kind of connect to each other, but to decide how to match them requires developing robust and reasonable rules.

[jhpoelen]

Did you consider having a hybrid name detector and giving a little more friendly error message rather than making it seem like the server crashed? This would already be an improvement for me. Sort of like a "not yet supported" exception.

[dimus]

Yes, definitely makes sense, I'll schedule it for the next week

[bjonnh]

Any hope to get that resolved? It seems to me that the issue here was also that the x used was a unicode × and not a x.