Patrick Leary

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 Jonathan Ray who took this action.

    Jonathan Ray commented on "EOL API Discussion Group":

    @Jeff Holmes: yes by starting with a photo taken and trying to find that match on EOL, and in turn using that to find the species name for example. For the confusion, as I am also trying to still work out the kinks on what I'm hoping to accomplish.

    about 2 years ago

  • Profile picture of Jeff Holmes who took this action.

    Jeff Holmes commented on "EOL API Discussion Group":

    @Jonathan Ray: I'm still confused if you are starting with a photo from somewhere else and are trying to find a match on EOL or if you are trying to find a photo based on a species name or something more like that...

    about 2 years ago

  • Profile picture of Nathan Wilson who took this action.

    Nathan Wilson commented on "EOL API Discussion Group":

    How is the image getting into EOL or how are are you finding the image in question?

    about 2 years ago

  • Profile picture of Jonathan Ray who took this action.

    Jonathan Ray commented on "EOL API Discussion Group":

    This is where, I guess you could say I am having writers block. Or up for suggestions on trying to get the EOL API to be used in a way that I am hoping. I would want to match the photo, with my own identifier (or even image upload) that would match that paticular photo or return similiar options. I am hoping to learn more about your API on hopes of using it in java, for app cability. I am starting to look into this as a hobby, outside of my tech life, and any help/suggestions would be highly welcomed. Thanks.

    about 2 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Jonathan Ray: I was sloppy, what I really meant was, how would you want to match the picture. Using your own identifier? Your own image URL? Either could be consistent with the approach that Nathan is talking about.

    about 2 years ago

  • Profile picture of Jeff Holmes who took this action.

    Jeff Holmes commented on "EOL API Discussion Group":

    @Jonathan Ray: I'm interested in this topic as well. Can you say a little more about what you mean by matching? What data are you starting with?

    about 2 years ago

  • Profile picture of Nathan Wilson who took this action.

    Nathan Wilson commented on "EOL API Discussion Group":

    The only approach I've found for doing this with the current API is to use the collection API to get a list of the photos provided by a content partner. It's a bit ugly, but there's enough information there to figure out the needed calls to the data_object API call.
    I'm interested in your use case. The most important case we've come up with is providing content partners a way to get deep links into EOL. This suggest a large batch lookup for all the content for a partner would be more efficient than a picture by picture lookup using, for example, the unique id provided by a given content partner.
    In our existing ticket tracking system, I've already requested:
    - A single (possibly paginated) API call that returns all the information a content partner needs to connect their pages to the appropriate EOL pages. In this case having the returned by the data_object API call added to the collection API call would be sufficient, but having the unique id provided by the content partner would be better (parsing URLs is ugly).
    - Include in the collection API the data_object URL rather than just the EOL data_object id (gives EOL the ability to change the URL).
    - An API call for discovering a content partner's collection (currently you have to look it up by hand and hard code it).

    about 2 years ago • edited: about 2 years ago

  • Profile picture of Jonathan Ray who took this action.

    Jonathan Ray commented on "EOL API Discussion Group":

    Well I was thinking of matching the picture and then parsing the data, maybe not actually retrieving the photo itself but the data of the matched picture, but down the line actually rwtieving like a thumbnail of the matched picture may prove beneficial. Thanks.

    about 2 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Jonathan Ray: I think it is somewhat difficult to do this, as to use the data_objects method you need to know either the EOL DataObject version ID or a 16 character GUID, neither of which you can get without inspecting the XML for a page on which that photo appears. I could be wrong about this, but if I'm right this is a good suggestion for API improvement. How would you want to retrieve the photo?

    about 2 years ago

  • Profile picture of Jonathan Ray who took this action.

    Jonathan Ray commented on "EOL API Discussion Group":

    Is it possible to use the EOL API to match a particular photo sent in, in order to the parse xml data about said picture?

    about 2 years ago

  • Profile picture of cuttersgoose who took this action.

    cuttersgoose commented on "Pomatomus saltatrix (Linnaeus, 1766)":

    Beautiful!

    about 2 years ago

  • Profile picture of Katja Schulz who took this action.

    Katja Schulz commented on "EOL Curators":

    @Michael Wunderli: If you find a source that has information about these spiders, we can try to engage them as a content partner. They would have to be willing to release their content under a creative commons license, though. In this particular example, we could grab (i.e., copy & paste manually) the original description from BHL along with a few anatomical drawings for this species (could be uploaded through our Rapid Response LifeDesk). Unfortunately, there was no habitus drawing in the original description. For many of these species it may be difficult to get anything beyond the original description, and many may never have been illustrated fully.

    about 2 years ago

  • Profile picture of Michael Wunderli who took this action.

    Michael Wunderli commented on "EOL Curators":

    @Katja Schulz: What i meant was that for exaple here: http://eol.org/pages/1181577/details This species for example is present but has no pictures and no detail information. That was the case with most species I found on that website. Is there something we can do about that?

    about 2 years ago

  • Profile picture of Katja Schulz who took this action.
    Katja Schulz added "Crassula" to the collection "Homonyms on EOL".

    about 2 years ago

  • Profile picture of Katja Schulz who took this action.

    Katja Schulz commented on "EOL Curators":

    @Michael Wunderli: All the Haploclastus species are here: http://eol.org/pages/111544/overview Or is that not what you meant?

    about 2 years ago

  • Profile picture of Michael Wunderli who took this action.

    Michael Wunderli commented on "EOL Curators":

    Check out this website, non of the species shown there are present in the eol data. http://www.exoticfauna.com/tarantulabibliography/Haploclastus.html

    about 2 years ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on Patrick Leary's newsfeed:

    This comment was deleted.

    about 2 years ago • deleted: about 2 years ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on Patrick Leary's newsfeed:

    This comment was deleted.

    about 2 years ago • deleted: about 2 years ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL API Discussion Group":

    @Bob Corrigan: Thanks Bob. If you are referring to the thumbnail sizes, I worked out that two of the "proportional" sizes are labelled _98_68 and _580_360. I'd still be interested to know what the 3rd available size is.

    about 2 years ago • edited: about 2 years ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL API Discussion Group":

    @Cyndy Parr: Thanks Cyndy. I'm absolutely sure it used to return both 12132222 and 1057290 before, but as you say, it only returns 1057290 now, so the problem has magically resolved itself! Thanks.

    about 2 years ago