Service locations render in confusing ways when no name is provided.

[ryguyk]

Description

Service locations (for both health services and non-clinical services) render in interesting ways when no name is provided, particularly when multiple service locations exist at a single facility.

Here is an example from production (as it stands currently) with multiple service locations at a single facility:

And, with annotations:

Here is the same data as it will appear with the new logic for displaying service location address (or, in this case, not displaying service location address when "use facility address" box is checked. see #7339):

Acceptance Criteria

On the front end, there should likely be some default header in the case when no name is provided for a service location. This would have two major outcomes:

1. Would provide visual separation for a service location (so information like hours don't appear to be a continuation of a previous location).
2. Would dictate that all headers (e.g. "Hours") are the same header level (i.e. h5) for all locations.

It was first discussed whether this name field should be required in the CMS, but this feels less than desirable in the scenario where there is only one service location at a given facility, and this scenario seems like it's the rule more than the exception. This led to the idea that a FE default might be a good solution, at least temporarily. It would be temporary if it is decided that the best solution is some extended CMS logic that would potentially require names for service locations if, for example, multiple locations exist. It would otherwise be permanent.

https://dsva.slack.com/archives/CT4GZBM8F/p1640632587107500?thread_ts=1640631116.105000&cid=CT4GZBM8F

[mmiddaugh]

Related: Design for Facility health service #34635

[xiongjaneg]

@davidmpickett To review for current state and what elements of this no longer apply

[davidmpickett]

All situations referenced in this ticket have newer more specific tickets addressing them

• Conditionally display "Location" header on Service Location templates #17414
• Consider: Conditionally require field_clinic_name on Service Location Address #17380
• Implement UX recommendations to Service Location Address paragraph type #17488
• SPIKE: Propose content model for task-oriented Service Location header on VAMC facility services #17490