Dmitry Mozzherin

| Try [Quercus robur](https://resolver.globalnames.org/name_resolvers.json?names=Quercus%20robu), [Pinus pinaster](https://resolver.globalnames.org/name_resolvers.json?names=Pinus%20pinaste), [Zea mays](https://resolver.globalnames.org/name_resolvers.json?names=Zea%20may), [Oryza sativa](https://resolver.globalnames.org/name_resolvers.json?names=Oryza%20sativ) ... but in verifier. Some of these do not work because fuzzy match works with stemmed versions. So, for example...

> example: [Ulva lactuca](https://resolver.globalnames.org/name_resolvers.json?names=Ulva%20lactuca&data_source_ids=195) matches in ds 195; but changed to [Vlva lactuca](https://resolver.globalnames.org/name_resolvers.json?names=Vlva%20lactuca&data_source_ids=195) there is no resolver fuzzy match) This happens because there is a quota on how many errors...

Comparing resolver and gnverifier: In my case how and where resolver and gnverifier differ I do have an idea, because I wrote the code and used modified ideas from resolver...

> I see ... quite complicated to tune the tool for every need. Indeed. My goal is more to figure out an intersect space from existing usecases where gn tool...

> It would be great if [gndiff](https://github.com/gnames/gndiff) has finally options to fine-grain "configure its fuzziness" with all those numerical parameters you mention, plus let user select output detail (i.e. choosing...

ah sorry about that, I thought it was general thoughts, and I just did not get to it yet:) I'll take a look. As a rule of thumb, when there...

Looks like this approach is not failproof, I am going to leave it in favor of just running one job.

Having 2nd attempt

Hi @thompsonmj , thank you for the feedback! Do you mean using postprocessing to sort results by the unique IDs?

I think I did understand your point @thompsonmj. Do I understand correctly, that you use command line `gnfinder` tool?