Issue 12512

Species page: Overview section: inconsistent use of case

Reporter: kbraak
Assignee: kbraak
Type: Bug
Summary: Species page: Overview section: inconsistent use of case
Environment: Firefox 17.0.1 Mac OS X
Priority: Trivial
Resolution: Fixed
Status: Closed
Created: 2012-12-06 18:10:08.931
Updated: 2013-08-29 14:44:54.45
Resolved: 2012-12-21 14:23:11.092
Description: There is an inconsistent use of case in the Overview Section of the Species page (see screenshot). For example:

Taxonomic Status

accepted (lower case)

Extinction Status

Extinct (First letter capitalized)


marine (lower case)

I would recommend using one case or the other, not alternating. ]]>

Attachment Screen Shot 2012-12-06 at 6.06.15 PM.png

Attachment Screen Shot 2012-12-19 at 5.04.27 PM.png

Created: 2012-12-19 17:05:31.584
Updated: 2012-12-19 17:05:31.584
I noticed that for Taxonomic status, the default value is "UNKNOWN".

This bring up another question []. Do we want to standardize default unknown values? "UNKNOWN", "Unknown", "unknown"?

Our currently uses a mixture of "Unknown and unknown", and across other portal pages a mixture of "UNKNOWN", "Unknown", "unknown" is applied in no particularly consistent way.

Since the field title is already given in UPPER CASE, e.g. TAXONOMIC STATUS, I think it's overkill having the values also in upper case. I suggest we capitalize the first letter only. In this way, it would look like:

Heterotypic synonym of Oxytropis jacquinii Bunge

Created: 2012-12-20 10:34:25.253
Updated: 2012-12-20 10:34:25.253
Yes, this needs to be addressed.
There are various reasons I think that need to be tackled differently:

a) in case of all upper case names it is very likely that we expose an enum name directly without looking it up in the resource bundle. This needs to be fixed on the template and new entries added to the bundle if needed

b) Extinct stems from a fixed name in the templates: ${usage.isExtinct()?string("Extinct","Living")} Ideally this should come from the bundle.

c) some terms might come from the data - in that case we have not much control, though we *could* Capitalize the values via freemarker.

Comment: Good progress made in The work extends beyond just the species overview section. 
Created: 2012-12-20 17:02:44.571
Updated: 2012-12-20 17:02:44.571

Created: 2012-12-21 14:23:11.124
Updated: 2012-12-21 14:23:11.124
I won't add an UNKNOWN entry to the resource bundles for threat status or establishment means. These enums are shown by themselves with no header title, so it would be weird to see UNKNOWN on its own, without adding some title and thus changing the design.

I believe enum values to be displayed in our templates in a consistent manner now, and the resource bundle to consistently capitalize the first letter for enum values and free text values (where applicable).

Closing issue.