The EOL Profile Newsfeed contains comments left for its owner by other members, EOL Community invitations, and gathers updates associated with the items in the owner's EOL watch list.

Add a new comment

  • Profile picture of Kari Pihlaviita who took this action.

    Kari Pihlaviita added the Finnish common name "Vaeltajasimpukka" to "Dreissena polymorpha (Pallas, 1771)".

    8 months ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    Also, please don't forget that API discussions (and others) are happening here: http://eol.org/forums

    9 months ago

  • Profile picture of Barb Banbury who took this action.

    Barb Banbury commented on "EOL API Discussion Group":

    @Cyndy Parr: Thanks Cyndy, sounds great!

    9 months ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Barb Banbury: Hi Barb, we have a paper in preparation, hope to be submitting in the next few days. Will contact you offline.

    9 months ago

  • Profile picture of Barb Banbury who took this action.

    Barb Banbury commented on "EOL API Discussion Group":

    Is there a citation for the API we can use?

    10 months ago

  • Profile picture of eangeles92 who took this action.

    eangeles92 commented on "EOL API Discussion Group":

    Thanks for everyone's support, Im currently creating a interactive javascript tree of life using the eol api. I will post the link here once Im done with it. Thank you

    12 months ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    @eangeles92: Thanks to Yan there is a response to this question with code samples in our new forum http://eol.org/forums/3/topics/38 . It describes how to fetch data from the API as JSON and turning that into a PHP object that can be worked with

    about 1 year ago

  • Profile picture of cuttersgoose who took this action.

    cuttersgoose commented on "Alasmidonta varicosa (Lamarck, 1819)":

    Beautiful!

    about 1 year ago

  • Profile picture of eangeles92 who took this action.

    eangeles92 commented on "EOL API Discussion Group":

    How can I connect to the eol api? Im really confused on how to start, can I use php?

    about 1 year ago

  • Profile picture of Gaurav Vaidya who took this action.

    Gaurav Vaidya commented on "EOL API Discussion Group":

    @Cyndy Parr: That's exactly what I was looking for, thanks! I've moved my comment there.

    about 1 year ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Gaurav Vaidya: Hi Gaurav, this is a great suggestion for an API improvement (or maybe it is already possible, I'm not sure). We are starting to have extensive discussion about the API on the http://eol.org/forums so I recommend that we move the discussion there...to the API improvements thread probably.

    about 1 year ago

  • Profile picture of Gaurav Vaidya who took this action.

    Gaurav Vaidya commented on "EOL API Discussion Group":

    I can't figure out how to search the comments on here, so apologies if this has been asked before! I've just discovered that the EOL's '/pages' API call will return a list of synonyms for a given name; I just helped somebody use this to figure out the comprehensive list of names they'd want to search a database so that they don't miss out on data recorded against junior synonyms. Are there any plans to return a hierarchy name or id for the synonym so we can find out which hierarchy that synonymy information is coming from?

    about 1 year ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    @Barb Banbury: Hi Barb. The highest published page ID (today) is http://eol.org/pages/36680799/overview . I'm curious though how you intend to use this. As Nathan point out IDs are not meant to be used directly, and there are a tremendous number of redirect pages (most of which are never actually published before they are turned into redirects). Nathan suggested an API to return random pages which seems like a reasonable API method. But I'm not sure how reasonable an API to return the highest ID would be since it seems completely arbitrary. Perhaps you have some end goal which might be better approached with a different set of API methods that aren't so dependent on arbitrary page IDs?

    about 1 year ago

  • Profile picture of Nathan Wilson who took this action.

    Nathan Wilson commented on "EOL API Discussion Group":

    To be clear, there are expected to be a lot of redirects and there are some missing pages (mostly in the lower numbers). Currently the highest number I could find is 36680949. This means that only 1 in 27 ID numbers are not redirects or missing pages. My understanding is that this is because the data harvesting process creates a page whenever it sees a name that is in anyway different from anything it has seen in the past. There is then a process that figures out whether new names are most likely the same as some existing page. If it is then, it is turned into a redirect. However, the original number is maintained since there may have been an error in that process. In general it is not a great idea to deal directly with the ID numbers. However, there are circumstances where you pretty much have to. It would be helpful to know why you need the largest page number. For example, I needed it at one point since I wanted to create a list of truly random pages so I could test somethings about EOL. It would have served my purpose better if there was an API call to ask for a random set of pages.

    about 1 year ago

  • Profile picture of Barb Banbury who took this action.

    Barb Banbury commented on "EOL API Discussion Group":

    @Cyndy Parr: Thanks Cyndi, I will add it to the API suggestion page. I could use the largest page that doesn't redirect, but I could also just use the largest EOL taxon ID (which might save me searching by being able to ignore the page numbers and all the redirections). Either way, I just want to make sure that I have full taxonomic coverage for all the EOL pages.

    about 1 year ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Barb Banbury: I guess the question is what is the largest page number that doesn't redirect to a valid taxon concept page? Might be a good suggestion to add to the API Improvement thread here: http://eol.org/forums/2 .

    about 1 year ago

  • Profile picture of Barb Banbury who took this action.

    Barb Banbury commented on "EOL API Discussion Group":

    Is there any way to determine the largest eol ID number? For example, if I go to http://eol.org/pages/6000000/overview it takes me back to eol id 1086495. There seem to be a lot of duplicates and missing pages.

    about 1 year ago

  • Profile picture of Jonathan Ray who took this action.

    Jonathan Ray commented on "EOL API Discussion Group":

    Thanks for the suggestions. I'll look into it further, and hopefully the results will be worth it.

    about 1 year ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Roderic Page: People would be pretty good at the coarse matching (shrimp-like, bird, mold, flower) so I'm not sure it is helpful to have computer vision do that part. Definitely an area for research.

    about 1 year ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    If EOL already has the image then it should be straightforward to create a service to locate it (just match a hash of the image file). Google Images supports searching for images (go to http://www.google.co.uk/imghp and click on the camera icon in the search box). I've searched for EOL images and Google finds them (for example, chose an image from EOL, download it to your computer, then upload it to Google images and search for it). This answers the question "is this particular image in EOL?"). This question is obviously limited as it requires EOL to already have the image, but you could imagine that as more and more images end up in EOL (e.g., via Flicker and iNaturalist, and other contributors) the chances that an image you find on the web already exists in EOL will start to rise.

    The problem of finding an image "like" one you have is harder. Google supports this query as well, but seems to rely on matching images with similar distribution of colours, and so doesn't work terribly well. There are some useful posts on Stackoverflow about the general problem, e.g. http://stackoverflow.com/questions/843972/image-comparison-fast-algorithm and http://stackoverflow.com/questions/75891/algorithm-for-finding-similar-images.

    It strikes me that another way to tackle this question is to ask it in an other way, namely "what images would an organism generate if photographed?" For example, take a 3D model of an animal (the BBC has some which could be used as starting points), generate 2D photos of different aspects, then use something like template matching to try and classify images. Even a coarse classification (this matches a shrimp) might be a start.

    about 1 year ago • edited: about 1 year ago