New VAMC System: VA Manila (test flight for the runbook)

[jilladams]

Acceptance criteria

Information needed from Product / VHA DM

• [x] The plain language name for the VAMC system. This should follow the pattern: Manila VA Clinic
• [x] Which VISN is this system in? 21

Create a new menu through config PR [Drupal Engineer]

• [x] Add a new Menu in a non-prod environment - https://prod.cms.va.gov/admin/structure/menu/manage/manila-va-clinic
  • [ ] Title = VAMC system plain language name
  • [ ] Administrative summary = VISN 21 | va.gov/plain-language-name
• [x] Enable the new menu in the Menu Settings for these Content types
  • [x] event
  • [ ] event_listing
  • [ ] health service listing
  • [ ] leadership listing
  • [ ] locations listing
  • [ ] news release - no menu settings available as Manila content creator / publisher
  • [ ] news release listing
  • [ ] publication listing
  • [ ] staff profile - no menu settings available as Manila content creator / publisher
  • [ ] story - no menu settings available as Manila content creator / publisher
  • [ ] story listing
  • [ ] VAMC operating status
  • [ ] VAMC billing and insurance
  • [ ] VAMC facility
  • [ ] VAMC system
  • [ ] VAMC medical records office
  • [ ] VAMC system policies page
  • [ ] VAMC register for care -
  • [ ] VAMC VA police
  • [ ] VAMC detail page - as Manila editor in Tugboat, Manila VA Clinic is not present in the list of menu options
• [x] Export the config file and create a PR to merge it into the va.gov-cms repo https://github.com/department-of-veterans-affairs/va.gov-cms/pull/19193

Create initial VAMC System Drupal entities [CMS helpdesk or Sitewide team]

• [x] Add a new Term in the Sections taxonomy - https://prod.cms.va.gov/section/vha/vamc-facilities/manila-va-clinic
  • [x] Nest the term under VHA > VAMC Facilities > VISN ##
  • [x] Name = VAMC system plain language name
  • [ ] As you create all the subsequent Drupal entities, assign them to this Section
• [x] Add a VAMC System - https://prod.cms.va.gov/manila-va-system
  • [ ] Fill out all required fields
    • [x] Meta description = placeholder?
    • [x] Banner image = placeholder?
    • [x] GovDelivery ID(s) = placeholder?
    • [x] Menu settings > Menu link title = VAMC system plain language name
    • [x] Menu settings > Parent link = <VAMC system plain language name>
    • [x] System menu = VAMC system plain language name

Create one copy of each of these hardened VAMC content types [CMS helpdesk or Sitewide team]

• [ ] Parent link = <VAMC system plain language name> -- need to revisit / remember if Manila needs these
  • [ ] VAMC System Billing and Insurance - https://prod.cms.va.gov/manila-va-clinic/billing-and-insurance
  • [ ] VAMC System Medical Records Office - https://prod.cms.va.gov/manila-va-clinic-system-node/medical-records-office
  • [ ] VAMC System Operating Status - https://prod.cms.va.gov/manila-va-clinic-system-node/operating-status
  • [ ] VAMC System Register for Care - https://prod.cms.va.gov/manila-va-clinic-system-node/register-for-care
• [ ] Parent link = SERVICES AND LOCATIONS
  • [ ] Health Services List - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services
  • [ ] VAMC System Locations List - N/A for Manila
• [ ] Parent link = NEWS AND EVENTS
  • [ ] Events List - https://prod.cms.va.gov/manila-va-clinic-system-node/events
  • [ ] News Releases List - https://prod.cms.va.gov/manila-va-clinic-system-node/news-releases
  • [ ] Stories List - https://prod.cms.va.gov/manila-va-clinic-system-node/stories
• [ ] Parent link = ABOUT VA [REGION NAME]
  • [ ] Leadership List (will need to be moved later) = https://prod.cms.va.gov/leadership
  • [ ] VAMC System Policies Page - https://prod.cms.va.gov/manila-va-clinic-system-node/policies
  • [ ] VAMC System VA Police page - https://prod.cms.va.gov/manila-va-clinic-system-node/va-police

Clone (from where?) these semi-hardened VAMC detail pages [CMS helpdesk or Sitewide team]

• [ ] Parent link = <VAMC system plain language name>
  • [ ] Make an appointment - https://prod.cms.va.gov/make-an-appointment
  • [ ] Pharmacy - https://prod.cms.va.gov/pharmacy
• [ ] Parent link = SERVICES AND LOCATIONS / Health Services List
  • [ ] Caregiver support
  • [ ] Homeless Veteran care - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/homeless-veteran-care
  • [ ] LGBT Veteran care - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/lgbtq-veteran-care
  • [ ] Mental health care - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/mental-health-care
  • [ ] Minority Veteran care - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/minority-veteran-care
  • [ ] Patient advocates - https://prod.cms.va.gov/patient-advocates
  • [ ] Returning service members - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/returning-service-member-care
  • [ ] Suicide prevention - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/suicide-prevention
  • [ ] Women Veteran care - https://prod.cms.va.gov/manila-va-clinic-system-node/health-services/women-veteran-care
• [ ] Parent link = ABOUT VA [REGION NAME]
  • [x] About us - https://prod.cms.va.gov/manila-va-system/about-us
  • [x] Programs - https://prod.cms.va.gov/manila-va-system/programs
  • [ ] Research - https://prod.cms.va.gov/research
  • [ ] Work with us - https://prod.cms.va.gov/work-with-us
  • [ ] Contact us - https://prod.cms.va.gov/contact-us-0
• [ ] Parent link = ABOUT VA [REGION NAME] / About us
  • [ ] Mission and vision - https://prod.cms.va.gov/about-us/mission-and-vision
  • [ ] History - https://prod.cms.va.gov/about-us/history
  • [ ] Performance - https://prod.cms.va.gov/performance
• [ ] Parent link = ABOUT VA [REGION NAME] / Work with us
  • [ ] Jobs and careers - https://prod.cms.va.gov/work-with-us/jobs-and-careers
  • [ ] Internships and fellowships - https://prod.cms.va.gov/work-with-us/internships-and-fellowships
  • [ ] Volunteer or donate. - https://prod.cms.va.gov/work-with-us/volunteer-or-donate
  • [ ] Doing business with us - https://prod.cms.va.gov/work-with-us/doing-business-with-us

Find any existing VAMC facilities that belong to this system [CMS helpdesk or Sitewide team]

• [x] Set them to the appropriate Section - https://prod.cms.va.gov/manila-va-clinic
• [ ] Set their Parent link settings to SERVICES AND LOCATIONS / Locations -- ?? Doesn't exist on this facility

Menu configuration and clean up [CMS helpdesk or Sitewide team]

• [ ] Go to Content / Menus
• [ ] Find the relevant menu and select edit menu
• [ ] Ensure all menu links are nested in the proper place
• [ ] Set some menu links to disabled
• [ ] Consult VAMC sitemap in sharepoint for menu settings
• [ ] Enable the menu in Menu Breadcrumbs module - 9/19: not done in prod yet. should it be?
• [ ] Update CONTENT BUILD FILE with the menu

User set up [CMS helpdesk]

• [x] Create users if need / assign users to the appropriate section [link to KB article] - https://cms-efaris8nl6pxlah9ngsycnqtlqfhe99t.ci.cms.va.gov/user/2199?check_logged_in=1

VAMC editor tasks

• [ ] Complete training if they haven't already
• [ ] Do all the things listed VA Medical Centers (VAMCs) KB
• [ ] Do we have an editor facing checklist for content entry / tasks that gate publishing like we do for VBA?
• [ ] Confirm when ready to publish

Launch tasks

• [ ] Lighthouse coordination for service push?
• [ ] Redirects?
• [ ] Comms, change management?

[jilladams]

Manila section & content in it: https://prod.cms.va.gov/admin/content?title=Manila&type=All&moderation_state=All&owner=1187

[jilladams]

Questions that may affect Manila:

1. Menus: there are content types shown where the menu should be added, but if I'm a Content creator / publisher for the Manila section, I don't see menu options on those content types at all. Do we need to make the menu / content type relationship if the relevant editors can expose things to the menu anyway? Or is that bc Admin should be doing the menu pieces? This may need a runbook edit as well.

2. Other Programs pages use the path /system/programs. This one was set to auto, /programs. I updated it to https://prod.cms.va.gov/manila-va-system/programs, but we need to change if that's not right.

3. I noted the links that were in use for many of these pages. Should the runbook include updating them to use the correct system slug? Or we expect the editor to do that?

4. Can @davidmpickett help confirm the IA for the menu, based on content strategy? https://prod.cms.va.gov/admin/structure/menu/manage/manila-va-clinic - it seems to have been strategically built the way it is , but I have questions about why some things are where they are, so not 100% sure on status of that part of the checklist

Runbook edits / danglers to be addressed in #15264

5. "Set some menu links to disabled " - why? which ones? Can we get more granular for the runbook?

6. " Enable the menu in Menu Breadcrumbs module - 9/19: not done in prod yet for Manila. should it be?

7. "Update CONTENT BUILD FILE with the menu" -- ??

8. "Create users if need / assign users to the appropriate section [link to KB article]" - need to find the KB if it exists, or write a ticket to make one if it doesn't

9. UPdate "Do all the things listed here" to "Do all the things listed in the VA Medical Centers (VAMCs) Knowledge base article

10. "Do we have an editor facing checklist for content entry / tasks that gate publishing like we do for VBA?" - answer this and update in the runbook

11. For VBA we broke out the new runbook from the launch runbook. I think these steps belong in a Launch runbook, otherwise you have the "new system" runbook hanging out for a zillion years while Editor creates content. But is that a bad idea? We should check with Michelle & Helpdesk.

[davidmpickett]

1. Menus: there are content types shown where the menu should be added, but if I'm a Content creator / publisher for the Manila section, I don't see menu options on those content types at all. Do we need to make the menu / content type relationship if the relevant editors can expose things to the menu anyway? Or is that bc Admin should be doing the menu pieces? This may need a runbook edit as well.

I was also confused why we enabled have Menu settings on these content types. However, all other VAMC system menus are enabled. In lieu of strong evidence that it is a problem, I opted for consistency with previous systems. If it ain't broke, don't fix it mentality.

• [ ] news release - no menu settings available as Manila content creator / publisher
• [ ] staff profile - no menu settings available as Manila content creator / publisher
• [ ] story - no menu settings available as Manila content creator / publisher

[davidmpickett]

2. Other Programs pages use the path /system/programs. This one was set to auto, /programs. I updated it to https://prod.cms.va.gov/manila-va-system/programs, but we need to change if that's not right.

Good catch! I wasn't sure if the Programs page should automatically get the correct alias, but wasn't because of other things not being fully configured. But looking at some other Program pages, they do seem to be manually over-riden, so the runbook should relfect that step.

[davidmpickett]

• [ ] VAMC detail page - as Manila editor in Tugboat, Manila VA Clinic is not present in the list of menu options

I think that will be resolved by this ticket: https://github.com/department-of-veterans-affairs/va.gov-cms/issues/19199

[davidmpickett]

4. Can @davidmpickett help confirm the IA for the menu, based on content strategy? https://prod.cms.va.gov/admin/structure/menu/manage/manila-va-clinic - it seems to have been strategically built the way it is , but I have questions about why some things are where they are, so not 100% sure on status of that part of the checklist

The source of truth for this is the Manila sitemap in sharepoint. Happy to explain why this differs from the general Sitemap of a VAMC system in sharepoint.

[davidmpickett]

3. I noted the links that were in use for many of these pages. Should the runbook include updating them to use the correct system slug? Or we expect the editor to do that?

I think by this you mean things like how the Women Veteran Care page has links to the Mental health care and Patient Advocate pages? And those links are still pointing to the Pacific Islands system I copied the pages from?

Even if we expect the editor to do it, might be good to add to editor steps in the runbook. At very least, a good thing for the change management

[davidmpickett]

6. " Enable the menu in Menu Breadcrumbs module - 9/19: not done in prod yet for Manila. should it be?

Yup, it's listed in the overflowticket https://github.com/department-of-veterans-affairs/va.gov-cms/issues/19270