informatics-dev
commented
11 years ago Comment by Dimitrios Koureas
Dear Rich,
It seems that this is an issue from EOL side. However I assign this to dev team to further investigate
Closed informatics-dev closed 10 years ago
informatics-dev
commented
11 years ago Comment by Dimitrios Koureas
Dear Rich,
It seems that this is an issue from EOL side. However I assign this to dev team to further investigate
informatics-dev
commented
10 years ago Comment by Simon Rycroft
The XML being returned by EOL is not valid. I will add a tweak to our code to work around this, although that won't go live till later today/tomorrow.
informatics-dev
commented
10 years ago Comment by Richard James Burkmar
I now get a response from EOL, but the response does not appear to be parsed by Scratchpads properly. The attached images - Scratch1, scratch2 and scratch3 - demonstrate the workflow and the outcome. I have tried this for the EOL search 'acari' (as demonstrated in the images) and 'araneae' with the same result.
informatics-dev
commented
10 years ago Comment by Dimitrios Koureas
Tried on master platform. The TCS-EOL import does not return now errors but neither does taxa. The classification is not being updated at all.
informatics-dev
commented
10 years ago Comment by Simon Rycroft
I'm afraid the XML EOL is returning is invalid in so many places. This needs to be fixed at EOL's end. I have tweeted them https://twitter.com/scratchpads/status/377761860822388737 , feel free to voice further concern there.
informatics-dev
commented
10 years ago Comment by Simon Rycroft
EOL are looking into this https://twitter.com/eol/status/378576693369532416
informatics-dev
commented
10 years ago Comment by Simon Rycroft
EOL have now fixed the issue at their end. Please re-open this issue if you continue to have any problems.
Description:
When I click on import and select the 'TCS (Encyclopedia of Life taxonomy import provider)' I get the message 'The EOL classification service (http://services.eol.org/lifedesk/service.php) does not appear to be running. Please try again later.'
This first occurred towards the end of last week and I thought that it might be a temporary problem, but I've tried it four or five times since then and always the same message.
Attachments: