Dmitry Mozzherin

If you do not mind to use the start/end positions, all should work in one go. However, take in account #38. If your file is tab-separated, all will work, if...

originally gnfinder was made to detect names in BHL, so it uses a space of any kind as a separator between words. The `|` characters should not affect anything, as...

several spaces are ok

CSV and TSV files should work fine, because they are going to be normalized to a plain text with spaces.

It is a limitation we currently have. In old literature, the specific epithet is often capitalized. I did try to make capitalization optional in name finding, but it did cause...

I think now that we have https://app.swaggerhub.com/apis-docs/dimus/gnmatcher/1.0.0 it may be doable to verify every capitalized epithet. I will try to add it for the next version of gnfinder

The problem arises from the following verification of "Spengleri": ``` { "inputId": "ddef4511-d05e-5cca-93a1-711b6e5d6451", "input": "Spengleri", "matchType": "Exact", "bestResult": { "dataSourceId": 172, "dataSourceTitleShort": "PaleoBioDB", "curation": "Curated", "recordId": "62300", "entryDate": "2020-06-05", "matchedName":...

Even if a name verified is "real", we can never guarantee, that verification's best result is not a homonym, and totally different name was mentioned on the page. This is...

Using a year to filter out some false positives would probably help. However to make it helpful instead of introducing more false negatives and false positives is not a simple...

hm, interesting, @gdower, do you know how often such names happen?