Changes between Initial Version and Version 1 of Ticket #1089

Timestamp:

2012-02-29 19:28:20 (12 years ago)

Author:

jeroens

Comment:

There are a few ways to do this:

Allow the current name field to contain multiple names separated by a supposedly unused character such as '|'. Controls that display and edit names will have to deal with the 'split names'. This requires no changes to the core but places a big burden on the UI.

Handle this at core level, where input/output objects are populated with one of possible names. This is easier from the UI point of view but will not allow users to easily edit different names. This UI limitation is unacceptable.

Add an secondary index to name variables. This requires database changes and changes to all UI objects. The 'current display name' index can be selected through the UI style guide; from the UI point of view this is the easiest solution but the most work in the Core.

Ticket #1089 – Description

initial	v1
1		It would be easier to present a model to audiences from different languages if fleets, groups and possibly other data could be displayed using different names, such as common names, scientific names, Spanish names, etc.
	1	It would help to present a model to audiences from different languages if fleets, groups and possibly other entities could have multiple names such as common names, scientific names, Spanish names, etc. The user interface should have a way to choose what name to display.