Skip to content

Latest commit

 

History

History
92 lines (71 loc) · 5.03 KB

vamc-facilities-lovell.md

File metadata and controls

92 lines (71 loc) · 5.03 KB
Raw

Facilities - Lovell

  1. Overview
    1. Code locations
  2. Pages
  3. Menus
  4. Breadcrumbs
  5. Facilities
  6. List Pages

Overview

Lovell Federal health care is a unique situation were there are two different systems within an umbrella system.

  1. Lovell VA is for Veterans.
  2. Lovell TRICARE is for Dept of Defense.

The two different systems are run as separate website sections with some overlap.

To be clear, everything related to Lovell is tech debt because it does not follow any existing patterns. Every effort has been made to minimize the amount and location of the tech debt, but there is plenty of it both CMS and Content-Build.

Code locations

Pages

CMS

In the CMS, pages are either Clones or singles.

  • Clone: A CMS node that appears in both subsystems only differing by their path. A clone is any page with field_administration of "Lovell Federal health care" (tid: 347)
  • Single: A page that only appears in one or the other. Any page with a field_administration of "Lovell - TRICARE" (tid: 1039) OR "Lovell - VA" (tid: 1040)
  • Twins: Separate CMS nodes that have a non-identical counterpart in both subsystems. In the CMS a twin has no connection to its twin. It has no knowledge that the twin exists. So a twin is just a single, that has another similar single out there. Twin is a human construct, not a CMS construct.

Side note to correctly trigger processing of a Lovell - VA system page on content-build: 1. In GraphQL make sure you pull the fieldAdministration as:
fieldAdministration { entity { ... on TaxonomyTermAdministration { entityId name } } } 2. the entityId is the same as the tid above and will pull in the page as a single or clone or whichever process.

Content-Build

There are a set of steps that run during the content build. The order for these may not be reflected correctly here.

  1. Deep copy any node with a field administration of a clone, to become the TRICARE clones.
  2. Alter all paths of clones to reflect Lovell - TRICARE and Lovell - VA.
  3. Alter all titles of fieldOffice and fieldRegionPage for use in querying the menus
  4. Alterations to titles of some pages to match VA or TRICARE.
  5. Put the new TRICARE copies back in the pages data.

Menus

CMS

The menu lovell_federal_health_care is being used as the central menu for both VA and TRICARE. This was done to reduce the maintenance of two separate menus and trying to match the weight and shared items between them. An additional field 'field_menu_section' has been added to the lovell_federal_health_care menu. On node save, the field is set programmatically to either 'both', 'VA', or 'TRICARE' based on what was set on the node for field_administration.

Content-Build

The frontend approach to the menu involves the following:

  1. Grab lovell_federal_health_care menu (includes field_menu_section)

  2. Deep copy twice to make VA and TRICARE menus.

  3. Delete original menu.

  4. Lovell VA menu process (original menu)

    • Lovell VA items come in with right path. No processing needed.
    • Remove TRICARE items.
    • Alter all field_menu_section = both to set Lovell VA path.

  5. TRICARE menu process (the copy)

    • TRICARE items come in with right path. No processing needed.
    • Remove VA items.
    • Alter all field_menu_section = both to set TRICARE path.

Breadcrumbs

TBD

Facilities

Some Lovell facilities exist only in VA and some exist only in TRICARE. Only VA facility statuses and health services are pushed to the Facility API when they are changed. TRICARE facility data is not pushed, because those facilities do not exist in the Facility API. They were hand created and have no connection to the Facility API. Editing of data that normally comes from VAST will currently have to be performed by an admin, as the fields are locked down for everyone else.

List Pages

List pages for events, news releases, and stories operate on the concept that there are Lovell Lovell Federal Health Care list pages that provided any items that should appear in both VA and TRICARE. These pages themselves are not built on the FE, but are pulled into the separate VA and TRICARE list pages. This merging of the data happens on the FE and then the Federal page get removed from the data so that they do not get built.

Table of Contents