Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine content model for displaying VA Police contact information per facility when there are multiple numbers per system #16415

Closed
4 tasks done
xiongjaneg opened this issue Dec 13, 2023 · 9 comments
Assignees
Labels
Content CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide VAMC police transparency Sub-product of VAMC VAMC CMS managed product owned by Facilities team

Comments

@xiongjaneg
Copy link
Contributor

xiongjaneg commented Dec 13, 2023

User Story or Problem Statement

In #16335 for VA Police MMVP, only one number will be displayed on the VAMC system VA Police page. This will be the number of the first facility listed on each system's web page.

Ten systems were identified that had more than one contact number per system, usually varying across two or three facilities. For MVP, when a VAMC system has more than one contact number (because of different numbers for different facilities), we want to display those multiple contact numbers.

Acceptance Criteria

  • Options for content model are documented
  • Options are reviewed with engineering (may be included in UX Sync)
  • Options are reviewed with product (may be included in UX Sync)
  • Subsequent ticket is stubbed or PM is tagged to stub ticket

Path forward = Option 2

@xiongjaneg xiongjaneg added Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status labels Dec 13, 2023
@xiongjaneg xiongjaneg changed the title Display VA Police contact information per facility in cases where there are multiple numbers per system Display VA Police contact information per facility when there are multiple numbers per system Dec 13, 2023
@xiongjaneg xiongjaneg added VAMC CMS managed product owned by Facilities team Content CMS team practice area VAMC police transparency Sub-product of VAMC labels Dec 13, 2023
@davidmpickett davidmpickett changed the title Display VA Police contact information per facility when there are multiple numbers per system Determine content model for displaying VA Police contact information per facility when there are multiple numbers per system Dec 14, 2023
@davidmpickett davidmpickett self-assigned this Dec 19, 2023
@davidmpickett davidmpickett removed the Needs refining Issue status label Dec 19, 2023
@mmiddaugh
Copy link
Contributor

@davidmpickett VHA Law Enforcement Services are interested in moving toward CMS as source of truth for contact information if it makes sense to make these fields editable sooner than later

@davidmpickett
Copy link
Contributor

@davidmpickett
Copy link
Contributor

@mmiddaugh @xiongjaneg
For scoping my work on this, do you want me to just look at moving from 1 phone number per system -> 1 phone number per facility? Or should I also account for the future state of having potentially multiple types of phone numbers at each level?

For instance, the CSV we received had a whole column for phone numbers for Police Chiefs in addition to the Ops Phone Number column we migrated into Drupal (there was also a column for Fax numbers)

@davidmpickett
Copy link
Contributor

Will need to kick the tires on this a bit with @swirtSJW and @aklausmeier before doing a full write-up of pros and cons, but here's a first draft:

@mmiddaugh
Copy link
Contributor

For scoping my work on this, do you want me to just look at moving from 1 phone number per system -> 1 phone number per facility? Or should I also account for the future state of having potentially multiple types of phone numbers at each level?

I'd suggest accounting for the future state - even if we break it into now and later pieces. This might include

  • more than one phone number at a system/facility level (I'm not sure about including Police Chief numbers but I recall the VA Police stakeholders mentioning there might be local/facility level emergency contact numbers and can foresee the option of displaying both a system level number and a facility level number.)
  • option for PAOs to add/edit existing

@swirtSJW
Copy link
Contributor

swirtSJW commented Jan 3, 2024

Great work laying out the options @davidmpickett
The lift of option 1 and option 2 are nearly the same, so for the same lift I like the power / benefit / existing pattern of option 2.

Option 3 is an easy lift but flawed by the likely potential of disconnected data. (not being able to associate the number with a facility)

@xiongjaneg
Copy link
Contributor Author

xiongjaneg commented Jan 4, 2024

@davidmpickett Got a use case for option 2 that came in through help desk: VA Greater Los Angeles has extra contact info in their old police detail page that they were concerned about not being able to put in the standard police page

@davidmpickett
Copy link
Contributor

Discussed in UX sync on 1/4/2024

  • Decided: Needs to be at the facility level, we already anticipated editor involvement, so this points to Option 2, using the VAMC Facility Non-Clinical Service.
  • Contact csv: we don't know if there are other consumers of that. Michelle to work on confirming.

I will work on stubbing out the subsequent tickets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content CMS team practice area Facilities Facilities products (VAMC, Vet Center, etc) sitewide VAMC police transparency Sub-product of VAMC VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

5 participants