Why has the occurrence ID stopped being a link back to the RBGE data (DOI)?

15596
Reporter: feedback bot
Type: Task
Summary: Why has the occurrence ID stopped being a link back to the RBGE data (DOI)?
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2014-05-08 12:14:52.464
Updated: 2015-03-02 16:10:18.314
Resolved: 2015-03-02 16:10:18.292
        
        
Description: Dear GBIF,

As manager of the RBGE data in GBIF I am upset that the functionality that we once had in GBIF that allowed us to "link back" to a DOI and therefore the current RBGE data has now disappeared.

This link back to our data went a long way in appeasing our internal "doubters" who were critical of us putting our data out to aggregators. I could show them that the users could get back to our data seamlessly for  up-to-date verifications, see that edits had been acted upon, obtain more collection details, etc.

I worry that removing this functionality may come to cause us a problems in the future especially as other aggregators continue to provide it.

Yours,

Robert Cubey

*Reporter*: Robert Cubey
*E-mail*: [mailto:r.cubey@rbge.org.uk]]]>
    

Author: ahahn@gbif.org
Comment: Clarification of further detail taken up via email  by [~trobertson@gbif.org]
Created: 2014-05-08 13:14:52.043
Updated: 2014-05-08 13:14:52.043

Author: trobertson@gbif.org
Created: 2014-05-08 17:47:59.689
Updated: 2014-05-08 17:47:59.689
        
After email clarification, what is missing is that the occurrenceID is not clickable.

We should consider making all things that are obviously URLs clickable (open in a new tab) but specifically the occurrenceID should be 
    

Author: mdoering@gbif.org
Comment: We had similar discussion with Gregor Hagedorn and others about mixing the functionality of linking back to a record "homepage" and a globally unique id. We then concluded it is best to keep those functions separate and if the occurrenceID is also the link back it should simply be published both as occurrenceID *and* dc:references. Instead of overloading occurrenceID I still think this is a cleaner approach and would ask RBGE to update their mappings?
Created: 2014-05-12 10:14:31.996
Updated: 2014-05-12 10:14:31.996

Author: kbraak@gbif.org
Comment: +1 to Markus' suggestion, no overloading occurrenceID and using dc:references when appropriate
Created: 2014-05-12 15:47:03.936
Updated: 2014-05-12 15:47:03.936

Author: mdoering@gbif.org
Created: 2014-05-19 15:36:51.152
Updated: 2014-05-19 15:40:34.3
        
Implementing a clickable occurrenceID link in the main body, not the header. But we should still recommend to use dc:references in addition to put an http address into occurrenceID

https://github.com/gbif/portal-web/commit/ce9a6590aeb799f9dde88370bb1fb47e6249838f