tnrs_match_names returns NAs for queries with hyphens about rotl

[josephwb]

Hmm, it works for me.

[fmichonneau]

@ShanKothari FYI there is now a binary version of rncl for windows in the
rncl repo: https://github.com/fmichonneau/rncl/tree/master/winbuilds

On Fri, Sep 19, 2014 at 11:47 AM, ShanKothari [email protected]
wrote:

Example:

tnrs_match_names("Heliconia sanctae-martae")
search_string unique_name approximate_match ott_id number_matches is_synonym1
is_deprecated1
Warning message:
In tnrs_match_names("Heliconia sanctae-martae") :
NAs introduced by coercion

The dot function for tnrs returns the proper output.

—
Reply to this email directly or view it on GitHub
#7.

[bbanbury]

I get the same.

tnrs_match_names("Heliconia sanctae-martae")
search_string unique_name approximate_match ott_id number_matches
is_synonym is_deprecated
1

Warning message:
In tnrs_match_names("Heliconia sanctae-martae") :
NAs introduced by coercion
tnrs_match_names("Heliconia sanctae martae")
search_string unique_name approximate_match
ott_id number_matches is_synonym is_deprecated
1 heliconia sanctae martae Heliconia sanctae-martae TRUE
3947133 2 FALSE FALSE

It might be a good idea to handle taxonomic names before passing them to
the API. For example, getting rid of weird characters or numbers, and
gsubbing spaces for underscores.

---

Barb Banbury
http://barbbanbury.info
Department of Biology
University of Washington

On Fri, Sep 19, 2014 at 9:14 AM, Francois Michonneau <
[email protected]> wrote:

@ShanKothari FYI there is now a binary version of rncl for windows in the
rncl repo: https://github.com/fmichonneau/rncl/tree/master/winbuilds

On Fri, Sep 19, 2014 at 11:47 AM, ShanKothari [email protected]
wrote:

Example:

tnrs_match_names("Heliconia sanctae-martae")
search_string unique_name approximate_match ott_id number_matches
is_synonym1
is_deprecated1
Warning message:
In tnrs_match_names("Heliconia sanctae-martae") :
NAs introduced by coercion

The dot function for tnrs returns the proper output.

—
Reply to this email directly or view it on GitHub
#7.

—
Reply to this email directly or view it on GitHub
#7 (comment).