You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a curator, I want the Concept Display to reflect the preferred English name so that a synonym can be preferred without changing the FSN.
Use case
A curator moves the English preferred flag from an FSN to an English synonym while editing a concept.
Requirements
Model concept.display separately from concept.fsn.
concept.display must be the English name marked as preferred.
concept.fsn must be the English name with type FULLY_SPECIFIED, regardless of its preferred flag.
Allow the English preferred name to be either an FSN or a synonym.
Preserve exactly one preferred name per locale.
Do not force the English FSN to be preferred during validation or save.
Preserve each name's type, identity, and preferred flag in the OCL write payload.
For a new concept with only a Display, create an English FULLY_SPECIFIED name marked as preferred.
Derive Display and FSN from names for detailed concepts.
Route FSN-focused worklist items to the Names section, not the Display header.
Acceptance criteria
Given an English FSN with preferred=false and an English synonym with preferred=true, when the concept is validated, then validation does not report multiple preferred names.
Given an English synonym marked as preferred, when the concept is displayed, then the header shows that synonym as Display.
Given an English synonym marked as preferred, when the concept is saved, then the FSN remains preferred=false and the synonym remains preferred=true.
Given a new concept with only Display entered, when it is saved, then one English FSN marked as preferred is created.
Given two preferred names in the same locale, when the concept is validated, then validation reports the duplicate preferred-name error.
Given a worklist item focused on an FSN, when the concept editor opens, then the Names section is highlighted.
More details (collapsible)
Context
The previous behavior treated the header Display as the preferred English FSN. Moving the preferred flag from the FSN to a synonym caused validation and the save payload to recreate the FSN as preferred, resulting in two preferred English names.
For detailed concepts, the names collection is authoritative. Raw API Display is only used for partial search results that do not include names.
User story
As a curator, I want the Concept Display to reflect the preferred English name so that a synonym can be preferred without changing the FSN.
Use case
A curator moves the English preferred flag from an FSN to an English synonym while editing a concept.
Requirements
concept.displayseparately fromconcept.fsn.concept.displaymust be the English name marked as preferred.concept.fsnmust be the English name with typeFULLY_SPECIFIED, regardless of its preferred flag.FULLY_SPECIFIEDname marked as preferred.namesfor detailed concepts.Acceptance criteria
preferred=falseand an English synonym withpreferred=true, when the concept is validated, then validation does not report multiple preferred names.preferred=falseand the synonym remainspreferred=true.More details (collapsible)
Context
The previous behavior treated the header Display as the preferred English FSN. Moving the preferred flag from the FSN to a synonym caused validation and the save payload to recreate the FSN as preferred, resulting in two preferred English names.
For detailed concepts, the names collection is authoritative. Raw API Display is only used for partial search results that do not include names.