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
Currently, we have a setup where we have a single master set of metadata files (eg. a csv of encounter types) that is shared across multiple countries. It is often requested that in each country, the actual name attached to the metadata (eg. encounter_type.name) be in the default locale used in that country. This is useful, for example, when reports are run directly against the database and the encounter_type.name is pulled in. It is also useful if there are areas of the UI that do not use the localized display correctly.
Proposed Changes
One idea is to allow one to specify that the name and/or description of a given metadata row should be set based on the display in the default context locale.
The text was updated successfully, but these errors were encountered:
Context
Currently, we have a setup where we have a single master set of metadata files (eg. a csv of encounter types) that is shared across multiple countries. It is often requested that in each country, the actual name attached to the metadata (eg.
encounter_type.name
) be in the default locale used in that country. This is useful, for example, when reports are run directly against the database and theencounter_type.name
is pulled in. It is also useful if there are areas of the UI that do not use the localized display correctly.Proposed Changes
One idea is to allow one to specify that the name and/or description of a given metadata row should be set based on the display in the default context locale.
The text was updated successfully, but these errors were encountered: