Add a new comment
-
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?
-
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). -
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.
-
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?
-
Michael Wunderli added the German common name "Rotwolf" to "Canis lupus rufus Audubon and Bachman, 1851.".
-
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?
-
Stefan Phalagorn Bergström joined the community "EOL Curators".
-
Katja Schulz added "Pomponia imperatoria" to the collection "Taxon Concept Management Tasks Completed".
-
Cyndy Parr commented on "Vashon Island Biodiversity":
@Tim DiChiara, PhD: Here's a possibility -- where the image is missing it may be that there's a better page for you to include. For example, I thought Pacific Geoduck should have an image. I found out by reading the page that many people (including some of our providers) confuse Panopea generosa with P. abrupta, which is extinct. So you'll want to swap that out in your collection.
-
Tim DiChiara, PhD commented on "Vashon Island Biodiversity":
@Cyndy Parr: Hi Cyndy: Yes, so far EOL has had what I've been looking for...mostly. I think EOL is great, but I was surprised that it didn't have ALL the species in the collection, considering that there's nothing much exotic or rare in there. Anyway, thanks for checking it out and let me know if you find anything... Thanks! --Tim
-
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.
-
Cyndy Parr commented on "Vashon Island Biodiversity":
Wow, EOL has photos of almost everything in your collection! Would be great to fill in the gaps. I'll go looking in Flickr to see if we can invite some of the missing ones.
-
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?
-
-
Jennifer Hammock added "Malaysian Dead Leaf Mantis Deroplatys lobata threat display" to the collection "lolz".
-
Jennifer Hammock added "Nolidae>Earias paralella? IMG7789" to the collection "lolz".
-
Katja Schulz added "Lajonkairia lajonkairii (Payraudeau, 1826)" to the collection "Taxon Concept Management Tasks Completed".
-
Katja Schulz added "Crassula" to the collection "Taxon Concept Management Tasks Completed".
-
Katja Schulz added "Crassula" to the collection "Homonyms on EOL".
-
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?
