Issue
There was confusion around the location name provided in the form header and the name for the site details. The location name comes from the data provider. It is used as an id by most data providers so it is not subject to change.
The name for the site details is open to be defined by the user and may serve to offer clarification regarding the location name if the location is not a comprehensible value to the user. This is illustrated in the example below:
Solution
To communicate to the user that the information in the form header is coming from a different source than the metadata details available for editing,
I removed the Site Type from the header (since that is determined by the metadata)
Added a tool tip explaining the source of the info in the form header
Next Steps
We could change the help text for the site details name to clarify its purpose. Currently it is 'Name of location' which is confusing since it conflates the name and location
61
Issue There was confusion around the location name provided in the form header and the name for the site details. The location name comes from the data provider. It is used as an id by most data providers so it is not subject to change.
The name for the site details is open to be defined by the user and may serve to offer clarification regarding the location name if the location is not a comprehensible value to the user. This is illustrated in the example below:
Solution To communicate to the user that the information in the form header is coming from a different source than the metadata details available for editing,
Next Steps We could change the help text for the site details name to clarify its purpose. Currently it is 'Name of location' which is confusing since it conflates the
nameandlocation