i think what you’re saying has merit, but i think this is technically a little different from what is being requested in this thread. it’s a very subtle but important difference.
the request as written is asking for Orange-crownedWarblerIMG to be treated as a single string rather than being parsed as two separate strings Orange + crownedWarblerIMG.
i think you’re asking for a filename string like Orange-crowned_Warbler to be able to be matched to a taxon named “Orange-crowned Warbler”, which is currently not possible. currently, a filename like Orange-crowned_Warbler could be matched only to a taxon named “Orange crowned Warbler” (without the hyphen in the taxon name).
i support the kind of request that i think you’re asking for though, and if the original request is implemented, i think it would makes sense to also incorporate this other request at the same time.
…
here’s a little more detail about what happens if currently if you try to match on some variation of Orange-crowned Warbler in the filename:
if you have a file named any of the variations below, the observation will get loaded as an Orange:
orange crowned warbler.jpgorange-crowned-warbler.jpgorange_crowned_warbler.jpgorange+crowned+warbler.jpg
if you have a file named leiothlypis celata.jpg (or any variation of that), the observation will get loaded as an Orange-crowned Warbler.
if you have a file named orangecrownedwarbler.jpg, the observation will get loaded without an automatic taxon.
if you have a file named orange balsam.jpg (or any variation of that), the observation will get loaded as Common Jewelweed (aka Orange Balsam).
so currently, because there’s a hyphen in the taxon common name, there’s no combination of words based on the taxon common name that you can include in a filename to trigger an automatic Orange-crowned Warbler id.