Using a token for VAMC System Locations List Meta description

[omahane]

Description

The Meta description field in VAMC System Locations List uses customized text. This differs from the tokenized approach we use for Vet Centers. It also means that in the event of a system name change that the Meta description field needs to manually changed. Lastly, it means that this field needs to be reviewed for outdated content.

An alternative would be to make the Meta description a token, using the Related office or health care system (field_office) field and other language that uses information from the system, perhaps using the following pattern:

"[node:field_office] system locations, address, hours of operations, and health care services provided."

While this is by far the most common pattern, it is not the only one currently in this field. Pittsburgh differs with the following:

• "VA Pittsburgh Healthcare System has eight facilities. Our two medical centers are located at University Drive in Oakland and at H. John Heinz III in O’Hara Township. Our other six locations are community-based outpatient clinics."

Meta tag configuration screenshot

Acceptance Criteria

• [ ] The meta description in the of a VAMC System Locations List uses a token.
• [ ] The Meta description field of VAMC System Locations List is removed.

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [ ] Public Websites
• [x] Facilities
• [ ] User support

[jilladams]

Related slack thread: https://dsva.slack.com/archives/C0FQSS30V/p1680009593245629

[kmariepat-cityfriends]

Decision: we want this to be hardened