Time zones for facility or facility service Hours, based on the Facility API data (pending Sitewide Content team decisions)

Background

User Story or Problem Statement

As a maintainer of facility data, I want the CMS to have access to the timezone data that is already in the FAPI data.

As a data integrity manager I want timezone to not have to be in a comment in an hours field.

Affected users and stakeholders

CMS_editors_of_X_product
Developers of Y teams

Change management triage

The change represented by this user story will:

[ ] Be a site-wide change to appearance or key functionality (such as log-in process)
[ ] Be a specific change that requires more than 30 minutes of work by a user to meet a publishing requirement
[ ] Remove a piece of functionality (such as restricting editing functions, or “hardening”)
[ ] Require action by some or all users by a specific deadline
[ ] Change the front end and be highly visible to the public

If you selected an item above, open a new issue using the change management template.

If you did not select an item above, update issues/PRs in GitHub but don’t plan for change management.

Hypothesis

A hypothesis may depend on a spike ticket to be completed.

We believe that _thissolution will achieve _thisoutcome. We'll know that to be true when this measurable outcome occurs.

Assumptions

(How will these assumptions be validated?)

Acceptance Criteria

[ ] Testable_Outcome_X
[ ] Testable_Outcome_Y
[ ] Testable_Outcome_Z
[ ] Requires KB article update

Design principles

Veteran-centered

[x] Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
[ ] Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
[ ] Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
[ ] Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

[ ] Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
[ ] Efficient: Remove distractions and create clear, straightforward paths to get the job done.
[ ] Approachable: Offer friendly guidance over authoritative instruction.
[ ] Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
[ ] Empowering: Provide clear information to help editors make decisions about their work.

Runbook

## Labels (You can delete this section once it's complete) - [x] Issue type (red) (defaults to "Epic") - [ ] CMS subsystem (green) - [ ] CMS practice area (blue) - [x] CMS workstream (orange) - [ ] CMS-supported product (black) ### CMS Team Please check the team(s) that will do this work. - [ ] `Platform CMS Team` - [ ] `Sitewide program` - [ ] `⭐️ Sitewide CMS` - [ ] `⭐️ Public websites` - [ ] `⭐️ Facilities` - [ ] `⭐️ User support`

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