Taxize & EOL web ressources

taxize
r
Tags: #<Tag:0x00007ff646044bf8> #<Tag:0x00007ff6460449f0>
#1

Hi @sckott,

Is the EOL ID returned by taxize::get_ids() corresponds to the EOL page ID and not the taxon ID?
How can I exploit EOL web ressources based on the page ID?

I always get a 500 when I request the URI: https://eol.org/pages/:id like: https://eol.org/pages/7323218 (for taxon Pterapogon kauderni). I had a look at the documentation but found nothing.

Thanks for your time.
Steve

3 Likes

#2

hey @SteveViss thanks for your question. I don’t know what version of taxize you’re using, but with the current cran version i get:

get_ids('Pinus contorta', db="eol")
#> $eol
#> Pinus contorta
#>      "6946713"
#> attr(,"class")
#> [1] "eolid"
#> attr(,"pageid")
#> [1] "1061758"
#> attr(,"provider")
#> [1] "EOL Dynamic Hierarchy"
#> attr(,"match")
#> [1] "found"
#> attr(,"multiple_matches")
#> [1] TRUE
#> attr(,"pattern_match")
#> [1] FALSE
#> attr(,"uri")
#> [1] "https://eol.org/pages/1061758/"
#> 
#> attr(,"class")
#> [1] "ids"

So the url in the attributes uses the pageid, not the taxonid. Make sense?

1 Like

#3

Yes, makes perfectly sense. Unfortunately, we stored the EOL id return by get_ids() in Postgres instead of the page ID, so I lost track of the list attributes. I should maybe stored the page ID which is more useful to exploit EOL ressources.

0 Likes

#4

We did just add the page id in a recent version of taxize, so its possible you didn’t see it before b/c it wasn’t there.

0 Likes