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
We should use the configuration already present for the legacy webapp for the report page title. In the webconfig-model.xml excerpt below, this would be <title mainTitles="secondaryIdentifier|primaryIdentifier" numberOfMainTitlesToShow="1" subTitles="*organism.name*|[strain.identifier]" /> for BioEntity resulting in: Cc_08923Cajanus cajan[ICPL87119]
This is currently not exposed as a WS, so this requires work on the IM backend.
And the really weird thing is on my mines a Gene page shows Gene.strain.identifier rather than Gene.anything. The existing code seems to "discover" Gene.strain.identifier rather than Gene.primaryIdentifier, etc.
That's because the attributes ("symbol" "identifier" "primaryIdentifier" "secondaryIdentifier" "name" "title" "id") are tried in order for all summary fields, including those of referenced classes (strain in your case). Identifier ends up matching before primaryIdentifier.
Not sure if this implementation detail was intentional. I guess there's no scenario we'd want to use a value of a referenced class' attribute as the report page title, so it can't be? If so I can tweak the logic so this doesn't happen (can be included in next minor release soon to come).
We should use the configuration already present for the legacy webapp for the report page title. In the webconfig-model.xml excerpt below, this would be
<title mainTitles="secondaryIdentifier|primaryIdentifier" numberOfMainTitlesToShow="1" subTitles="*organism.name*|[strain.identifier]" />
forBioEntity
resulting in: Cc_08923 Cajanus cajan[ICPL87119]This is currently not exposed as a WS, so this requires work on the IM backend.
Thanks to @sammyjava for feedback.
The text was updated successfully, but these errors were encountered: