Issue 14623

Implement the display of verbatim fields (in groups) on occ detail page

14623
Reporter: omeyn
Assignee: kbraak
Type: SubTask
Summary: Implement the display of verbatim fields (in groups) on occ detail page
Description: This should include all core fields (including those which may be interpreted in the near future). As a test case build a mock, fully populated occurrence to be returned by the occ-ws for a special key. This will be a temporary thing until the new hbase schema is in place.
Priority: Major
Resolution: Fixed
Status: Resolved
Created: 2014-01-13 14:41:08.486
Updated: 2014-02-05 09:59:39.604
Resolved: 2014-02-05 09:59:39.558


Author: kbraak@gbif.org
Created: 2014-01-23 11:10:21.221
Updated: 2014-01-23 11:10:21.221
        
See first version of extended occurrence detail page at /occurrence/-1000000000

I tried to preserve the layout of the original page. The important terms/interpreted terms are shown at the top of each article/block. Verbatim terms follow immediately below in blocks entitled "Additional (Group) terms".

1) In the "Location" article, we need to revise which interpreted fields get shown if we show a map, and if we don't show a map.

2) The "Source details" article is composed of both record-level and occurrence group terms. Maybe we should separate record level and occurrence group terms into 2 separate articles.

3) The "Identification details" article is composed of both identification and taxon group terms. Maybe we should separate identification and taxon group terms into 2 separate articles.

4) The "Collection details" article is composed of event group terms. The name collection could be misleading. Maybe we should rename it to Event?

5) The "Citation and licensing" article now contains the record level term "rights". It could also be extended to contain "rightsHolder", "accessRights", and "bibliographicCitation". It seems more suitable to display these terms here, instead of under "Source details"
    


Author: kbraak@gbif.org
Created: 2014-01-23 11:23:02.294
Updated: 2014-01-23 11:23:17.648
        
Thanks [~mdoering@gbif.org] for your comments over Skype. I have transferred the feedback into follow-up actions below. I kindly ask you to also review the considerations 1-5 above.

Follow up actions:

1) Remove "OccurrenceID" label from the header, use just the id itself.

2) In Location, add the accuracy to the actual altitude or depth by using  +/-
E.g. ALTITUDE
1.000m +/- 10

3) Remove all the additional headings

4) Remove all taxon group terms (further discussion needed)

5) Remove sections resource relationship and measurement and facts, since they will become lists.

6) Try to fix the term labels using properties.
E.g. EARLIESTAGEORLOWESTSTAGE
 should be
EARLIEST AGE OR LOWEST STAGE
    


Author: mdoering@gbif.org
Created: 2014-01-23 12:02:34.935
Updated: 2014-01-23 12:03:23.012
        
Looking into the terms in more details I suggest to regroup terms into blocks in the following order:

HEADER:
Remove OccurrenceID header and replace modified date with eventDate excl time so it becomes:

{{urn:catalog:MVZ:Mammals:88}}
{{Human Observation of Caracara cheriway (Jacquin, 1784) on 23.01.2014 from eBird dataset}}

Source
 ids, coll/instCode/ID, datasetName/ID, BasisOfRecord, DISPOSITION, PREPARATIONS , OTHERCATALOGNUMBERS
 Plus show all identifiers from the List identifiers

Location
 as it is + all other location terms.

Identification
 as is plus all terms from Additional identification terms. Remove the entire "Additional taxon terms" section with all its terms as its been interpreted into the backbone. These terms should only be visible in the verbatim page. Only term to add here is INDIVIDUALID

Occurrence
 as additional occurrences + all terms from Additional Event terms + establishment means, sex, life stage

Media (new section)
 will become an image gallery at some stage similar to the species images. For now just put here:
 ASSOCIATEDMEDIA and List media

Geology
 as is

Relations
 this block should show the relations List

Measurements and Facts
 this block should show the facts List

Miscellaneous
 information held within, DATAGENERALIZATIONS, dynamic props, ASSOCIATEDSEQUENCES, ASSOCIATEDREFERENCES

    


Author: kbraak@gbif.org
Created: 2014-01-23 13:50:10.092
Updated: 2014-01-23 13:50:10.092
        
Thanks for your suggestions. I like them, and will prepare a new version.

2 outstanding points remain in my mind though:

1) In the "Location" article, we need to revise which interpreted fields get shown if we show a map, and if we don't show a map.

For example, if we show a map, do we want to show continent, country, stateOrProvince, waterBody? These are all interpreted terms now. Currently if we show a map, we show the locality, and exclude the others.

2) The "Citation and licensing" article now contains the record level term "rights". It could also be extended to contain "rightsHolder", "accessRights", and "bibliographicCitation". It seems more suitable to display these terms here, instead of under "Source details"


    


Author: mdoering@gbif.org
Comment: Both good points I agree with. Guess there is no need to show the country & continent, but maybe island, islandgroup and waterbody makes still sense? Im not sure if its extremely clear for everyone what country, state, county or municipality a location is in even if we show the map. For a species we do show the entire classification, maybe for a location too? Im rather indifferent on that point. Do as you like best for now
Created: 2014-01-23 16:27:02.071
Updated: 2014-01-23 16:27:02.071


Author: kbraak@gbif.org
Created: 2014-01-27 15:30:35.289
Updated: 2014-01-27 15:30:35.289
        
Another version is ready for comment at http://appdev.gbif.org/occurrence/-1000000000

All suggestions are incorporated, except the miscellaneous section. I find with so many occurrence terms, there is no intuitive way of dividing them into a miscellaneous block. There are terms from DwC groups flying around the page, and we are deviating from the DwC grouping more and more.

In the Location block, I have decided that when we show a map, we should also show all the properties we interpret: Continent, Country, StateProvince, WaterBody, in addition to county and locality. This gives the whole picture of the location as we interpret it.

In the Citation and licensing block, I have decided to show the record citation (DwC bibliographicCitation) instead of the dataset citation if it's present. Otherwise, the dataset citation and default citation are shown. In addition, I have added the access rights, rights, and rights holder to the block.

The media, relations, and facts sections are obviously not styled. And there are decisions about how to handle verbatim and interpreted ids on extensions, such as occurrencId and relatedOccurrenceId on OccurrenceRelation. 
    


Author: mdoering@gbif.org
Created: 2014-01-28 09:01:25.805
Updated: 2014-01-28 09:31:05.826
        
Well done Kyle. Still I'd like to see a few improvements:

General style: I would avoid the 2 equal column layout, definitely not mix them in one block. Try to arrange fields so that smaller ones are on the right, larger ones left. We show IDs usually on the right.

To be clear what Im referring to I will call a header title (e.g. collectionCode) plus value field a "header group" lacking any better name right now. Details:

LOCATION:
 - avoid the left block next to the map to be larger than the map, use a scrollbar just in case
- show first the locality and next the geo classification without waterbody concatenated into one header group maybe to save space?
- group all footprint terms and all georeference fields. Maybe create just one Footprint and one Georeferencing header group and arrange data nicely underneath?
- MUNICIPALITY is part of the geo classification below county
- show island and island group with waterbody next to geo classification in its own header group?

SOURCE DETAILS:
- dc:type needs to be next to BoR, maybe even under the one title
- show collectionCode and ID in one header group, similar institution code/ID with the code and ID being one a distinct line
- should we interpret DYNAMICPROPERTIES?

IDENTIFICATION:
- css box bug (bad divs?)
- remove line
- move identification id, qualifier & verification status to the right, they are allways short
- keep remarks and reference on the left as they might be large


OCCURRENCE:
- PREPARATIONS is in source already (its about the specimen, so belongs to source/collection not here)
- rearrange entire block into larger left and smaller right column. Event date stuff could be on the right for example. Also ids and individual count.

Ill do lower blocks later ...

    


Author: kbraak@gbif.org
Created: 2014-01-28 17:25:04.267
Updated: 2014-01-28 17:25:04.267
        
Thanks Markus. I have incorporated the above comments into another version (remember to refresh): http://appdev.gbif.org/occurrence/-1000000000

I think it's difficult to interpret dynamic properties, and it's fine to leave it as a string for now.

This is the commit: https://github.com/gbif/portal-web/commit/aca79b7ef7bedbc34e217ed7f8548783276cde69

There are some other verbatim terms we could remove from the page, but I kept them there for completeness.

Please let me know if the changes are to your liking, and your suggestions for lower blocks. 
    


Author: mdoering@gbif.org
Created: 2014-01-29 23:26:20.33
Updated: 2014-01-29 23:40:21.202
        
A big improvement, but there is still a lot of whitespace and it's not simple to find the information you are looking for as it's still lacking structure I think.

Can you try to show the geo and island classification simmilar to the taxonomic classification in one group on the left larger column?
For example like this (only if any of the terms exists of course):

{noformat}
GEOGRAPHIC CLASSIFICATION
North America > United Kingdom > California > Los Lagos > Holzminden

ISLANDS
Isla Victoria > Above Lake Aloha
{noformat}

And then only keep the water body where it is now. 
    


Author: mdoering@gbif.org
Created: 2014-01-29 23:28:12.644
Updated: 2014-01-29 23:28:27.68
        
Type status and typified name can be merged into one group:
{noformat}
TYPE STATUS
Holotype of Caracara cheriway (Jacquin, 1784)
{noformat}
    


Author: mdoering@gbif.org
Created: 2014-01-29 23:34:22.447
Updated: 2014-01-29 23:34:22.447
        
In Identification block remove most of the IDENTIFICATION prefixes of the terms. Its redundant cause they are in that block.
Show references and then remarks last.

The date and identified by can be combined as:
{noformat}
IDENTIFIED
29.01.2014 by John Smith
{noformat}

The IDENTIFICATION QUALIFIER should somehow be next to the identified species, not sure how that best fits and we gotta look int actual data I suspect. I would propose to add it behind the name in brackets for now like this:

{noformat}
IDENTIFIED AS SPECIES
Caracara cheriway (Jacquin, 1784)  [aff. agrifolia var. oxyadenia]
{noformat}
    


Author: mdoering@gbif.org
Created: 2014-01-29 23:36:55.795
Updated: 2014-01-29 23:40:01.155
        
In Occurrence details also combine event date and recording person like above:

{noformat}
RECORDED
29.01.2014 23:10:33 by Jane Smith
{noformat}

If there is time given in addition or any other event date info add it into the same block if possible. At least show them next to each other

*Remarks* I would always show last in every block
    


Author: mdoering@gbif.org
Comment: For the *geological stratigraphic classification* we gotta see how that gets interpreted ultimately. Until then I suggest to again show a classification similar to the taxonomy for all the earliest/latest terms. See http://en.wikipedia.org/wiki/Geologic_time_scale#Terminology for ordering
Created: 2014-01-29 23:39:30.036
Updated: 2014-01-29 23:39:50.915


Author: mdoering@gbif.org
Created: 2014-01-29 23:43:18.85
Updated: 2014-01-29 23:43:18.85
        
Also please verify that *empty blocks are hidden* and still look reasonable with little content:
http://appdev.gbif.org/occurrence/6
    


Author: kbraak@gbif.org
Created: 2014-01-30 18:49:49.287
Updated: 2014-01-30 18:51:51.908
        
Another version is ready for you at http://appdev.gbif.org/occurrence/-1000000000

More work is needed to clean up the Freemarker template, ensure empty blocks are hidden, show images in the media block (currently commented out), and adding a title to the Continent vocabulary. 
    


Author: mdoering@gbif.org
Created: 2014-01-30 21:54:26.176
Updated: 2014-01-30 21:54:26.176
        
Much nicer, your patience is very much appreciated Kyle and I think we're getting rewarded!

Just two, small & last comments:

1) Can we remove the dividing lines underneath the map and maybe even let the right column be just one large column?

2) The geological classification still has huge term names and is not shown as a classification. How about copying the taxonomic classification on the right side from the species pages? http://appdev.gbif.org/species/2480985
That might actually also be nicer for the geographic classification, maybe you wanna give it a try?

For geology just use the geo time alone like this:
{noformat}
EON      Phanerozoic / Proterozoic
ERA      Cenozoic / Mesozoic
PERIOD   Neogene / Quaternary
EPOCH    Ibexian Series / Pleistocene
AGE      Skullrockian / Boreal

BIOSTRATIGRAPHIC ZONE
N. Atlantic Conodont / Midcontinent Condonot
{noformat}

    


Author: kbraak@gbif.org
Created: 2014-01-31 11:41:22.594
Updated: 2014-01-31 11:41:22.594
        
My pleasure. I have implemented these 2 changes, see http://appdev.gbif.org/occurrence/-1000000000

The Location right column is still broken up into 2 parts, with the 1st part containing the terms that relate to the map, and the 2nd part (lower) containing the additional Location/geospatial IDs, etc.
    


Author: kbraak@gbif.org
Created: 2014-02-03 14:08:58.221
Updated: 2014-02-03 14:08:58.221
        
A new version including the reorganization of the Georeferenced verbatim terms is available for comment: http://appdev.gbif.org/occurrence/-1000000000

Additionally, a title has since been added to the Continent vocabulary, and cleanup of the Freemarker template was also done by making use of macros.

Still outstanding on this issue, is to make sure empty blocks don't show.
    


Author: mdoering@gbif.org
Comment: pretty sweet now! If the empty blocks are working this is definitely good to be closed now!
Created: 2014-02-03 22:03:19.715
Updated: 2014-02-03 22:03:19.715


Author: kbraak@gbif.org
Created: 2014-02-05 09:59:39.601
Updated: 2014-02-05 09:59:39.601
        
Empty blocks no longer show.

Closing issue as fixed.