Issue 11641

Implement EOL link

Reporter: mdoering
Assignee: mdoering
Type: NewFeature
Summary: Implement EOL link
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-08-01 12:16:08.352
Updated: 2013-08-29 14:45:06.274
Resolved: 2012-08-28 10:46:03.332
Description: Currently the portal has a mock link, for example

According to we should be able to use the GBIF ids to link to EOL (assuming they have an up to date GBIF Backbone) if the GBIF Backbone was an accepted hierarchy provider:

Then we could do get the EOL id for Aves like this:{GBIF_PROVIDER_ID}?hierarchy_id=212

Still this would only be a webservice call and no direct html link.
We could implement the EOL link therefore either asynchroneously or store the EOL ids as nub usage identifiers in checklist bank and update them thru a separate process.

Alternatively, if we could get EOL as a dwca checklist we could treat it as a regular checklist which would be preferrable. To be discussed with EOL.]]>

Created: 2012-08-27 15:01:09.212
Updated: 2012-08-27 15:01:09.212
According to we are content provider ID 4. returns no results.

Indexing seems subject to stale data, so a dynamic approach sounds "better".

Why not simply do this for a first iteration:

Homonyms look understandable / acceptable:

Should we need to link "smarter" we could refine it in the future (perhaps we can search with a rank and a higher taxon).


Comment: Good idea as a start. Patrick promised me an official EOL dwca some weeks ago though which should then be our main route to know about EOL ids.
Created: 2012-08-27 18:50:07.602
Updated: 2012-08-27 18:50:07.602