Jennifer Smith

Cat Scat DNA

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 Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL Discussion Group":

    @Yan Wong: For historical reasons, we have two paths for info from IUCN...one for the status field at the top of the overview, and the other for the content on the details tab. I think the latter has the most up-to-date data even for the status field and we should look into getting rid of the former collection to avoid confusion.

    over 1 year ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL Discussion Group":

    @Yan Wong: The vast majority of species on the planet are not covered by the IUCN (nor are they likely to be). The IUCN site suggests some 65,000 species have been assessed http://www.iucnredlist.org/about/summary-statistics (see Fig. 2). EOL has two IUCN lists (why?), the largest http://eol.org/collections/309 has 63097 taxa.

    over 1 year ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL Discussion Group":

    @Cyndy Parr: Thanks a lot. I've joined the API community now. Is there any reason when I go to http://eol.org/api/docs/pages/1.0 and run the default test search but with IUCN=true, I don't get any IUCN data? I thought that every species had an IUCN classification?

    over 1 year ago

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

    over 1 year ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL Discussion Group":

    @Yan Wong: Vernacular names data often comes to EOL dirty (or we mangle it, not sure which yet). Any curator can fix it by going to the common names tab such as http://eol.org/pages/328450/names/common_names (I fixed Mus musculus. Though I don't know the best French name I picked the one that had the most sources). If you regularly get scientific names as vernaculars, you might want to design your program to go back and get another vernacular. There are often other options in each language. Also, I invite you to join our API community. http://eol.org/communities/121/newsfeed

    over 1 year ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL Discussion Group":

    @Yan Wong: Maps as images are a frustrating problem. I'm manually collecting examples in this collection: http://eol.org/collections/23389 . The problem is that often our providers can't tell us that they are maps. In other cases we just don't have the time to go back to providers and revise the exports. Someone could probably write code to automatically flag possible maps based on image or caption characteristics. Google Summer of Code project, anyone?

    over 1 year ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL Discussion Group":

    By the way, I'm no expert in French, but surely this can't be a correct "vernacular name" returned by the pages API: { "vernacularName": "Mus musculus", "language": "fr", "eol_preferred": true },

    over 1 year ago

  • Profile picture of Yan Wong who took this action.
    Yan Wong joined the community "EOL Discussion Group".

    over 1 year ago

  • Profile picture of Yan Wong who took this action.

    Yan Wong commented on "EOL Discussion Group":

    I'm trying to automatically scrape images of organisms for http://www.onezoom.org/ . Some of the images associated with species are distribution maps (e.g. http://eol.org/data_objects/14840166), and I'm getting some of these in my downloads. Is there a system for identifying and flagging these up as maps rather than organism images? Also, I have some automated scripts to get images & construct image attribution lines from a large file of species names, if anyone is interested.

    over 1 year ago

  • Profile picture of [account deleted] who took this action.

    [account deleted] commented on "EOL Education Innovation Challenge Community":

    This comment was deleted.

    over 1 year ago • deleted: over 1 year ago

  • Profile picture of Anne Thessen who took this action.

    Anne Thessen commented on "EOL API Discussion Group":

    @Patrick Leary: I don't particularly need xml. I have been playing around with the json most of today, but I'm not having much luck there either. I can load the json okay (I think) but it doesn't want to recognize any of the nested dictionaries and dictionaries.

    over 1 year ago

  • Profile picture of Anne Thessen who took this action.

    Anne Thessen commented on "EOL API Discussion Group":

    @Roderic Page: Interesting that the tags in the xml you link to is different from what the API returned to me for another species....

    over 1 year ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Patrick Leary: JSON FTW ;)

    over 1 year ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Anne Thessen: I'm tempted to ask why you want to consume XML, which is a truly hideous format. EOL also outputs JSON, which is much nicer to work with.

    But since that's probably not the answer you're looking I've posted some code here: https://gist.github.com/rdmpage/5143326 It's in PHP (I kick it old skool) but it may help. I think there are two issues that you might be facing. The first is that I don't think 'response/taxon/dataObject/dc:description' is a field that exists, at least not in the example I quickly looked at (e.g., http://bit.ly/ZFfx8r ). The second is that you'll need to declare the default namespace ("http://www.eol.org/transfer/content/1.0") and add this to your XPath queries. For example, if you add 'eol':'http://www.eol.org/transfer/content/1.0' to the namespace map, and insert the "eol" prefix in your XPath query (e.g., "/eol:response/eol:dataObject/eol:dataObjectID"), things should work.

    If a service provides a choice between JSON and XML, JSON is almost always going to be the easier choice to use. XML is overkill in most cases, and a pain to work with. Hope this helps.

    over 1 year ago

  • Profile picture of Patrick Leary who took this action.

    Patrick Leary commented on "EOL API Discussion Group":

    @Anne Thessen: Hi Anne. If you continue to have troubles with XML and you do not need URIs and namespaces, then you could try the JSON response format http://eol.org/api/pages/1.json?details=1 . I am not a Python developer, but a quick search brought up http://docs.python.org/2/library/json.html which gives examples of how to decode JSON. If you can fetch the JSON result then pass it to json.loads, that might be easier to work with.

    over 1 year ago

  • Profile picture of Anne Thessen who took this action.

    Anne Thessen commented on "EOL API Discussion Group":

    @Roderic Page: Thanks for the suggestion. When I use the purl URI I lose the complaints about the dc:prefix, but now it doesn't pick up anything. I'll keep pounding away at it, but if you've got a bit of code working I'd really appreciate it if you would send it along. Thanks!

    over 1 year ago

  • Profile picture of Roderic Page who took this action.

    Roderic Page commented on "EOL API Discussion Group":

    @Anne Thessen: Anne, any reason you are using "http://dublincore.org/documents/dces" as the namespace for Dublin Core? The EOL API uses "http://purl.org/dc/elements/1.1/" for the Dublin Core namespace, which AFAIK is the current namespace URI. If you use a different namespace URI the XML parser is likely to fail to recognise terms from that namespace.

    over 1 year ago

  • Profile picture of Anne Thessen who took this action.

    Anne Thessen commented on "EOL API Discussion Group":

    Hi I'm new to this community. I have a question about parsing the xml output from the API. I'm using python to pick out the bits I need, but it doesn't seem to like the dc: prefix. I've tried to define it using namespaces, but it is still not happy. Has anyone else run into this problem? Below is what I'm doing. Any advice is appreciated. import xml.etree.ElementTree as ET nsmap = {'dc':'http://dublincore.org/documents/dces'} tree = ET.parse('test.xml') identifier = tree.findtext('response/taxon/dataObject/dc:identifier', namespace=nsmap) description = tree.findtext('response/taxon/dataObject/dc:description', namespace=nsmap) print (identifier, description)

    over 1 year ago

  • Profile picture of Cyndy Parr who took this action.

    Cyndy Parr commented on "EOL Discussion Group":

    @Bart C.: We're working on a better way to upload a batch of taxa into a collection. But there is a way you can do this right now -- use the spreadsheet upload method as if you are adding content to EOL. Then you can copy to a "fresh" collection so you can easily add and subtract new pages from there. Feel free to contact Jen Hammock who can help you.

    over 1 year ago

  • Profile picture of Bart C. who took this action.

    Bart C. commented on "EOL Discussion Group":

    Would it be possible to construct and submit a list of species you want to add to a collection via a spreadsheet? I am a member of group of naturalists that want to establish fauna lists for our working area. We want to publish this on our website. A link to an EOL collection would be perfect to update annotations instantly, without bothering our webmaster too much and have additional information about those species one click away for our visitors. Adding hundreds of species one by one to a collection and adding annotations and references via the EOL one by one is a bit too much.

    over 1 year ago • edited: over 1 year ago