Show new DwC terms on Occurrence Detail page

18491
Reporter: kbraak
Type: Improvement
Summary: Show new DwC terms on Occurrence Detail page
Priority: Unassessed
Resolution: Fixed
Status: Closed
Created: 2016-05-23 18:37:27.824
Updated: 2017-10-10 16:01:56.209
Resolved: 2017-10-10 16:01:56.194
        
Description: See [here|https://github.com/gbif/ipt/blob/master/v2.3-spec.md#new-terms] for a list of all DwC terms that were recently added.

Why add these new terms to the Occurrence Detail page?

Because currently users can only see information in these new terms by viewing the Verbatim Occurrence Detail page.

Below is the list of new terms that need to be added to the Occurrence Detail page, in order to make it more visible.

*dc:license* needs to be shown (this term replaced dc:rights, see POR-3111 for more info on support for dc:rights being removed, and POR-3113 for more information on how dc:license will be populated)

*dwc:organismQuantity* & *dwc:organismQuantityType* need to be displayed as a pair, in the same section as *dwc:individualCount*. This allows abundance measurements to be given, e.g. "15" & "percentageCoverage". The values for *dwc:organismQuantityType* should come from http://rs.gbif.org/vocabulary/gbif/quantity_type_2015-07-10.xml and should be interpreted in the future, see POR-3114. The following record from a butterfly monitoring dataset demonstrates how these fields get can be populated: http://www.gbif.org/occurrence/1265249025/verbatim

*dwc:sampleSizeValue* & *dwc:sampleSizeUnit* need to be displayed as a pair with other Event related terms, close to *dwc:samplingEffort*. This allows the sample size of the event to be displayed, e.g. "15" & "square_metre". The values for *dwc:sampleSizeUnit* should come from http://rs.gbif.org/vocabulary/gbif/unit_of_measurement_2015-07-10.xml and should be interpreted in the future, see POR-3115. The following record from a butterfly monitoring dataset demonstrates how these fields get can be populated: http://www.gbif.org/occurrence/1265249025/verbatim

*dwc:parentEventID* needs to be displayed with other Event related terms, close to *dwc:eventID*. Ideally both *dwc:parentEventID* and *dwc:eventID* will resolve some day to their own event page, see POR-3094.

*organismName*, *dwc:organismRemarks*, *dwc:organismID*, *dwc:organismScope*, *dwc:associatedOrganisms* need to be displayed with other Occurrence related fields. The following record from a bird tracking dataset demonstrates how some of these fields can be populated: http://www.gbif.org/occurrence/1209955474/verbatim]]>
    

Author: kbraak@gbif.org
Comment: Some organism terms belong to unknown namespace due to POR-2796 and thus cannot be displayed. See http://api.gbif.org/v1/occurrence/1209955474/verbatim
Created: 2016-06-14 14:38:59.043
Updated: 2016-06-14 14:39:17.949

Author: kbraak@gbif.org
Created: 2016-06-14 14:49:52.251
Updated: 2016-06-14 14:49:52.251
        
New terms now shown on occurrence detail page with [this commit|https://github.com/gbif/portal-web/commit/77a21bc2d2b9d2493361b122cdf99bcea7955b75] provided that they are interpreted to the correct namespace (see comment above about POR-2796).

[~ahahn@gbif.org] please note dc:rights will still be shown on the page until we decide how to handle record-level licensing.

[~hoefft] please ensure these new terms are also shown on the reengineered occurrence detail page. Thanks.
    

Author: hoefft
Created: 2016-06-15 16:08:47.475
Updated: 2016-06-15 16:08:47.475
        
the terms are shown on the new portal.

But we could consider more smarts to highlight fields depending on occurrence features. To do that probably we would most likely need to interpret the incoming data in the API though. Take quantity and such. To float this data to the top it needs to be fairly controlled I would say.

[~kbraak@gbif.org] please decide if this closes the issue - or it is a requirement that it has a more prominent position. If so we should discuss what we need to get there. A start could be to analyse the data we have.
    

Author: kbraak@gbif.org
Created: 2016-06-15 16:21:59.943
Updated: 2016-06-15 16:21:59.943
        
Thanks Morten. I think the implementation in the new portal satisfies this issue. POR-2796 is still blocking some new terms from showing though, so let's keep it open until that gets fixed.