department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

FL: Pull in and display operationalHoursSpecialInstructions for Vet Centers #18911

Open mmiddaugh opened 3 years ago

mmiddaugh commented 3 years ago

Issue Description

VAST administrators have included a new operationalHoursSpecialInstructions field that is now in Lighthouse.

operational status

There are 4 possible options that could be concatenated from VAST:

Field may contain one or more of the options above. If more than one is sent, all will be displayed.

Similar contents already baked into the Vet Center detail page front end ![image](https://user-images.githubusercontent.com/55411834/105557726-1e834280-5cca-11eb-8a1a-4fce7f3a9cec.png) NOTE: Current language in VAST is not Veteran friendly but we will work with Jessica Schiefer to improve and standardize the wording for Vet Centers. Changing it in VAST will automatically update the front end. This impacts VHA only : VAMCs and Vet Centers --- ## Tasks - [ ] Keep hardcoded language for now and put this on a flipper - [ ] Pull in `operationalHoursSpecialInstructions` field language - [ ] Replace existing detail page language with language from field ## Acceptance Criteria - [ ] Language displayed on Vet Center detail page matches language from `operationalHoursSpecialInstructions` field - [ ] If more than one option is sent, all display. - [ ] If null value - nothing displays - [ ] Existing functionality does not change in Production until flag changes - [ ] Ensure formatting of value(s) is correct (no pipes, etc) ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)
mmiddaugh commented 3 years ago

If data has pipes - will need to ask Lighthouse to clean data (rather than cleaning it on our side)

davidconlon commented 3 years ago

@davidconlon needs to work with Jessica Schieffer about this first for Vet Centers.

mmiddaugh commented 3 years ago

Blocked by need to scrub data formatting (pipes)