EOL API Discussion Group

With growing interest in using the Encyclopedia of Life API (application programming interface), comes the need for an openly available place to ask and answer questions. This is the place.

The Newsfeed for this EOL Community gathers updates associated with the items belonging to its Managed Collections, including activities of its members and comments from other EOL users.

Add a new comment

Newsfeed

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Anthony Goddard: Great, it's working for me now. PS, love the RAAF avatar!

    over 4 years ago

  • Profile picture of Anthony Goddard who took this action.

    Anthony Goddard commented on "EOL API Discussion Group":

    @Roderic Page: Hi Rod, there were some timeout issues in our load balancers, they seem to have settled down now.

    over 4 years ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    The API is down (returning "Error 503 Service Unavailable"). Any idea when it will be up again...?

    over 4 years ago

  • Profile picture of Lisa Walley who took this action.
    Lisa Walley joined the community "EOL API Discussion Group".

    over 4 years ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    @Cyndy Parr: The DwC-A Media file has columns for Publisher, generic Contributor and Creator (can be assumed to be photographer for photos, author for text, etc.). So those fields can be used to provide multiple agents and can also accept semi-colon delimited lists of multiple names in each column.

    To get the precise role names and especially to include agent metadata such as the homepage, it is necessary to include the Agents file and include a semi-colon delimited list of AgentIDs in the Media file. This structure is not endorsed by the creators of the DwC archive as associating extensions with Media as opposed to Taxon breaks the star schema that the archives were intended to represent. EOL does allow references and agents associated with Media and I am happy to help a partner create such a archive with such associations.

    over 4 years ago • edited: over 4 years ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    @Cyndy Parr: The thumbnailURL is relevant for videos as well as other media types. For example see http://eol.org/api/data_objects/1.0/207f85a543f0d9a455e02ed5e42ce71c.json . This field contains the URL of a thumbnail hosted by EOL. The thumbnail will have been resized to meet the needs of our site design.

    Many of the thumbnails will have been supplied by our Content Partners but if we are able to create one automatically we will serve it using the same field. It is highly recommended that partners provide their own thumbnail if they have one so the frame can be representative of the video.

    over 4 years ago • edited: over 4 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    This comment was deleted.

    over 4 years ago • deleted: over 4 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Cyndy Parr: I mean, the AgentID field of media.txt?

    over 4 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    An API user is getting information about image objects and wants to format a Darwin Core Archive for resubmitting a slightly modified image that has all the appropriate metadata in the right DwC-A fields. He needs to know how to handle the two agents in a case like this: http://eol.org/api/data_objects/1.0/626e5d79f99332a6589d41b4896342bd


    There exist both a photographer and a provider. Where do these go in the Darwin Core Archive media.txt file? Does he have to make a separate agents.txt file and concatenate (with semi-colons) the identifiers in the AgentID field?

    over 4 years ago

  • Profile picture of Jennifer Smith who took this action.
    Jennifer Smith joined the community "EOL API Discussion Group".

    over 4 years ago

  • Profile picture of Brian Jacobs who took this action.
    Brian Jacobs joined the community "EOL API Discussion Group".

    over 4 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    Is "eolThumbnailURL" in the DataObject relevant for video? If so, is it only there if explicitly provided or can EOL generate it?

    over 4 years ago

  • Profile picture of Evan Alter who took this action.
    Evan Alter joined the community "EOL API Discussion Group".

    over 4 years ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Cyndy Parr: This is what I was trying to build earlier today http://iphylo.blogspot.co.uk/2012/06/using-zoomable-treemap-to-visualise.html. Partly inspired by a converstaion we had at the "birds of a feather" session at the first iEvoBio, when you talked about being able to visualise database coverage (at least, that's what I recall we talked about!).

    over 4 years ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Patrick Leary: Great, thanks for this. I'll look at grabbing a copy of the same CoL version you have. It's a pity CoL have made a mess of their identifiers. The internal ones are unstable across versions, the LSIDs have version-specific suffixes and tend to break.

    over 4 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Patrick Leary: We already have the GBIF ticket, Patrick, here https://jira.eol.org/browse/TAX-1198

    over 4 years ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    @Roderic Page: I just downloaded a version of the 2010 database provided in the second section on http://www.catalogueoflife.org/services/instructions.html, which is at http://4d4life.eu/downloads/CoLupdate_01062010_data.zip . The record_id 2322671 does refer to Papio in this version (with LSID urn:lsid:catalogueoflife.org:taxon:d7a1f584-29c1-102b-9a4a-00304854f820:col20100701), so EOL is representing the July 1st updated version of the 2010 Catalogue of Life. I'm not sure how many identifiers are different between the versions, but I tried Papio hamadryas: http://eol.org/api/search_by_provider/1.0/6873687.json?hierarchy_id=529 and found them to be consistent, but many higher taxa have different record_ids. I believe one problem we had with the CD version was there were no orders of Aves - a problem reflected in the published version: http://www.catalogueoflife.org/annual-checklist/2010/browse/tree/id/2243478. Exposing the GBIF classification and identifiers in the API is a good idea - I'll put in a ticket to capture it.

    over 4 years ago • edited: over 4 years ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Patrick Leary: Hi Patrick & Cyndy, thanks for chasing this up. Not sure how many versions of CoL exist for 2010, I'm using a copy that (I think) comes from the 2010 DVD (which has the same record_ids as the 2010 version that is online at http://www.catalogueoflife.org/annual-checklist/2010).

    The reason this became an issue is that I'm playing with a tool to visualise classifications and wanted a "simple" way to go from the CoL classification (which I'm displaying) to a taxon image from EOL. I'd assumed/hoped that I could do this via the EOL API , but because of the mismatch between CoL identifiers that I have and the ones in EOL I hit a brick wall and went back to simple text search (sigh).

    While you're adding stuff, the GBIF classification would be a big help -- add that, expose it via the API, and clients can start to build maps.

    over 4 years ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    Hi Rod - the label 2009 is indeed wrong and I have changed it to 2010. This was caused by different database entities having different labels (datasets vs hierarchies), resulting in this unfortunate error. I am trying to figure out precisely which version of COL 2010 we are representing. It looks like these records in our database were created on 2010-08-09, so I my best guess is this was the July 1st version of the 2010 Annual Checklist, and I am currently trying to find a copy of that version to confirm. The provider identifier does map to the 'record_id' column in the 'taxa' table in the COL dataset. Cyndy has been urging us to get the 2012 version indexed ASAP and I hope to have that in by the end of next week at the lastest. I will post an update later today if I am able to confirm which version of the 'Annual' checklist we are representing.

    over 4 years ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL API Discussion Group":

    @Roderic Page: I can't address most of this but I can say that the "2009" reference is erroneous on the site. Trying to get rid of it now. Have requested response to the rest by our informatics team.

    over 4 years ago