14932
Reporter: mdoering
Assignee: mdoering
Type: NewFeature
Summary: Interpret dc:references as a link
Priority: Critical
Resolution: Fixed
Status: Resolved
Created: 2014-01-24 11:26:28.776
Updated: 2014-05-19 15:48:01.389
Resolved: 2014-05-19 15:48:01.357
Description: verbatim dc:references is used to provide a link back to the "home details page of an occurrence or checklist record. We need to interpret this link and make it available in the Occurrence class as it is very important for a publisher to see a link back to his website if it exists and was provided.
In CLB we currently interpret dc:references (and the older now deprecated dc:source) to become an Identifier record of type URL. Does this make sense or do we rather like to have a new List property in the Occurrence (and NameUsage) class?]]>
Author: mdoering@gbif.org
Created: 2014-05-15 15:33:11.13
Updated: 2014-05-15 15:34:03.402
Question is how we like to store such a link in Occurrence.
Option A) Similar to CLB right now we can use List identifiers with IdentifierType=URL.
Option B) add a new URI references property to Occurrence
Option C) add a new list of a new Link class with URI and title as properties
I would go with either A or B as I can see us getting multiple links in the long term.
[~trobertson@gbif.org] what do you think?
Author: kbraak@gbif.org
Created: 2014-05-15 15:52:50.356
Updated: 2014-05-15 15:52:50.356
Are there cases when we get multiple links now? The standard doesn't accommodate multiple links, so it would seem: http://rs.tdwg.org/dwc/terms/#dcterms:references For this reason, I'd lean to B.
Author: mdoering@gbif.org
Comment: For simplicity we decided today after scrum to use a single URI references property as we are not yet aware of any dataset having multiple links per occurrence.
Created: 2014-05-19 12:04:17.575
Updated: 2014-05-19 12:04:17.575