Content modeling for Manila Outpatient Clinic

[davidmpickett]

User Story or Problem Statement

The Manila Outpatient Clinic doesn't fit the standard model of VAMC systems. This ticket will explore how we might use existing content types in Drupal to meet the needs of Manila, or whether we need to build something from scratch.

Dave's proposal

BLUF - It's a VAMC site but a facility IS the system

We'll use the existing VAMC infrastructure, but need to make a few adjustments to how the VAMC system and VAMC facility are treated. Mostly can be handled via menu settings in Drupal config, but will likely need a little finessing.

The plan

1. Generally follow the new VAMC system runbook
2. Put the Manila VA clinic facility at the root of a Manila VA clinic site via Menu configuration
3. Don't have a Locations list or a typical VAMC system FE page (a VAMC system will still need to exist in Drupal)

Details

• Mural diagrams
• Sitemap on Sharepoint

Drupal notes

• I was mostly able to do this already as a proof of concept on Tugboat
• Need to make the VAMC system un-publishable (do we do this already for lovell?)
• Aliases, breadcrumbs, title tags? Any logic tied to VAMC system, vs Menu?
• VAMC Menu custom access needs to be figured out
• I wasn't able to get the convenient sidebar menu in Drupal to work. Maybe the VAMC system needs to be the root for that to work?

FE notes

• Something about the Get Updates box seems to be connected to VAMC system node. Will require investigation
• Are there other places where queries or templates are using the VAMC system as source of truth?

Stakeholder / SME notes

• Questions and decisions about which pages are needed can be logged in the sharepoint sitemap
• Ditto hardened vs unhardened direction for Top Task pages

Acceptance Criteria

• [x] Content models are documented
• [x] Content models are shared with Product, Engineering, Stakeholders and CAIA for feasibility review

[jilladams]

From VHA DM:

Manila will need the following elements for their page: health services, events, news releases, stories, about us, policies, work with us, contact us, address phone number, clinical hours, prepare for your visit, veteran satisfaction-wait times data (if available)

[davidmpickett]

Today I futzed around in a Tugboat to test out how feasible making a facility the root of a VAMC menu is. Looks promising

[davidmpickett]

Huzzah! Successful proof of concept for making a VAMC Facility be the root of a VAMC website rather than the VAMC system. I spun up a tugboat and have successfully built a frontend for a Manila VA Clinic. I just copied a few subpages to the menu from Lovell in order to prove that nav and breadcrumbs would behave correctly

[davidmpickett]

End of sprint update:

• I would say this is more than halfway complete
• I have already iterated through a basic model & did some tech feasibility
• Shared my progress in UX sync last week
• Remaining step is a more formal documentation of the proposed solution so that it can be reviewed

[davidmpickett]

Today's update. In preparation for building out the full sitemap for Manila, I combined some Excel formulas I have created in previous IA tickets to create a generalize IA generator tool. Basically I can now type in a small number of sentence case phrases and it will automatically generate the H1, Breadcrumbs, URL, & Title tag.

IA Generator in Sharepoint

Input

• L1 title = Manila VA Clinic
• L2 title = Medical records office

Output

• H1 = Medical records office
• Breadcrumb = VA.gov home > Manila VA Clinic > Medical records office
• URL = va.gov/manila-va-clinic/medical-records-office/
• Title Tag = Medical Records Office | Manila VA Clinic | Veterans Affairs

[davidmpickett]

Manila VA Clinic - Sitemap.xlsx Static copy for convenience

[davidmpickett]

Shared in slack for async review. Will talk through in UX sync on Thursday

[davidmpickett]

Shared update in slack

[jilladams]

@Agile6MSkinner to schedule story mapping for follow up. Closing!