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

Drupal: Update police page for MVP showing contact information and FAQs #16335

Closed
5 of 7 tasks
xiongjaneg opened this issue Dec 6, 2023 · 15 comments
Closed
5 of 7 tasks
Assignees
Labels
Drupal engineering 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 6, 2023

Description or Additional Context

In 12/6 sprint planning, it was decided that MVP for the police page would include:

  • system page listing police contact information for facilities in that system
    • based on what the data gives us to work with, this will likely be a phone field or use the phone paragraph with unlimited cardinality.
  • FAQs no change needed for this one.

This ticket is to update Drupal to include only that information for MVP.

Will go in two PRs

Acceptance Criteria

  • Contact list csv is formatted and cleaned up.
    • For contact number use the Telephone Ops column. One number per system for MVP.
    • API ID column is added.
  • Appropriate field is added to the VA Police content type
  • migration is written to populate all the system pages from the CSV (approach to be determined based on the csv structure.
@xiongjaneg xiongjaneg added Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status Drupal engineering CMS team practice area VAMC police transparency Sub-product of VAMC labels Dec 6, 2023
@swirtSJW
Copy link
Contributor

swirtSJW commented Dec 6, 2023

Estimated 5 based on assuming easy to conneect data in the csv. May need to be adjusted if the data turns out to be gnarly.

@xiongjaneg xiongjaneg removed the Needs refining Issue status label Dec 6, 2023
@swirtSJW
Copy link
Contributor

swirtSJW commented Dec 6, 2023

Discuss with @davidmpickett as to the field types for the data, keeping in mind two possibly opposing directions:

  • simple phone and title field
    • easiest to implement
    • easiest to sync up on subsequent migrations
    • easiest for FE to pull into their react data
  • phone number paragraph
    • syncing paragraphs in subsequent runs of a migration is challenging
    • pulling that data into the react data is a bit more challenging due to entity references.

@xiongjaneg
Copy link
Contributor Author

xiongjaneg commented Dec 6, 2023

@swirtSJW @omahane Example of contact info from Police
VAP Chief - Facility Contact List (12-5-2023).csv

Police guidance is to use the Telephone Ops number.

@davidmpickett
Copy link
Contributor

Have to pause for a couple meetings, but I'm almost done with an initial pass of assigning a VAMC System to every meaninful line from the CSV
va-gov-cms-vamc-facilities.csv

@davidmpickett
Copy link
Contributor

Took a first pass of cleaning up the CSV and indicating the most likely VAMC System and Facility ID string* for each line item. I also found any systems that have multiple line items are marked them as either good duplicate (aka there are multiple entries, but they all have the same phone number) or needs decision. Looks like there at 10 VAMC systems with multiple entries where we will need our police stakeholders to make a decision on which one to show for mmmVP

New Source of Truth for cleaned CSV

Static copy for convenience

@xiongjaneg
Copy link
Contributor Author

Will this need UX and a11y review?

@swirtSJW
Copy link
Contributor

swirtSJW commented Dec 7, 2023

Will this need UX and a11y review

@xiongjaneg Ideally yes, but given time frame and the fact that no editor will interact with this data in any way, I would say we could probably skip it for now.

@davidmpickett
Copy link
Contributor

@swirtSJW @omahane and I met today. We went back and forth on a simple phone field or the phone paragraph type, they both have pros and cons. Then Steve realized a technical consideration that might make the paragraph type not a meaningful option. But he needs to test a thing first

@swirtSJW
Copy link
Contributor

swirtSJW commented Dec 8, 2023

There is a bug... or maybe an unrecalled feature where external content it being inserted at the top of the page, despite the weighting showing that it should come after the title and field office.

image

Given the urgency of police AND that no editors will be in this for a long time, I am going to move on and not chase this bug down.

It is in the right spot for true admins, just not any other editors
image

@davidmpickett
Copy link
Contributor

Want to note that the bug is only on the Edit screen and not on Node view. If we took edit permissions away from Content Editor, Reviewer, Publisher (which we previously waffled on) on this content type, then that would prevent most editors from seeing this weirdness

@swirtSJW
Copy link
Contributor

The bug Dave mentions above is no more. Resolved.

@jilladams
Copy link
Contributor

FAQs already in place.
Migrations in progress, unblocked now. ETA for code review by ~Fri.

@swirtSJW
Copy link
Contributor

Updated upstream data and here is a copy to get into my space
police_system_contacts.csv

@swirtSJW
Copy link
Contributor

The final PR has been merged. We will just need to run the migration by hand after the code deploys today.

@swirtSJW
Copy link
Contributor

The contact migration has been run on prod and all is good
image

image

We can call this done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Drupal engineering 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

4 participants