Closed stefaniefgray closed 1 year ago
@jilladams @kmariepat-cityfriends Just got editor confirmation that this one and the linked redirect request are good to go!
@mmiddaugh We have a redirect in place to https://www.va.gov/col-gail-s-halvorsen-candy-bomber-vet-center created here: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13836
The problem is that I am reading the Common name guidance above in this ticket, and it doesn't fit the change:
If the new official name matches the pattern " Vet Center", update the common name to match
The problem is that the URL is based on the common name. So we're wondering whether the Common name should change, too. If so, should it change to "Col. Gail S. Halvorsen 'Candy Bomber' Veterans Center" or "Col. Gail S. Halvorsen 'Candy Bomber' Vet Center"?
If we change the Common name to "Col. Gail S. Halvorsen 'Candy Bomber' Veterans Center", we will need to change the redirect url to https://www.va.gov/col-gail-s-halvorsen-candy-bomber-veterans-center
Jessica (RCS) confirmed we should retain Provo Vet Center as the common name and URL.
We'll also need to add the "Also known as" text above the intro (similar to Prescott Vet Center). Do we need a separate issue for this @kmariepat-cityfriends @omahane?
Sounds good.
The "Also called the" is in this .liquid template: content-build/src/site/layouts/vet_center.drupal.liquid
That front-end language should, therefore, be programmatically generated during content build.
@stefaniefgray There's nothing else to do on this ticket, so I'm moving to QA.
Closing!
Vet Center, Outstation, Mobile Vet Center facility name change - Description
Vet Centers, Mobile Vet Centers, and Vet Center Oustations may all be subject to name changes in VAST. Not all steps apply to each type of facility -- please pay attention and make sure you've done the relevant steps based on facility type.
Intake
[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Facility flag
[x] Link to associated help desk ticket (if applicable) Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-5865
[x] Name of submitter (if applicable) Submitter: @stefaniefgray
[ ] If the submitter is an editor, send them links to any relevant KB articles for the Vet Center product. Let them know that facility changes can take between 75 days and 4 months after submitting a request, according to VAST administrators. KB articles:
[ ] Link to facility in production: Facility CMS link: https://prod.cms.va.gov/provo-vet-center Facility API ID: vc_0532V
Acceptance criteria
CMS help desk steps
Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag.
Redirect: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13836
CMS engineer steps - Vet Center only (not Outstation/MVC)
(Redirects deploy weekly on Wed. at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)
Drupal Admin steps (CMS Engineer or Help desk)
Help desk will complete these steps or escalate to request help from CMS engineering.
If a Mobile Vet Center or Outstation
If a Vet Center
For all types
Changed name
, and saves the node (with moderation state = published)CMS Help desk (wrap up)