VAMC services are showing too much of the service term on node view.

[swirtSJW]

Describe the defect

When I visit a VAMC Facility Health Service I see too much data related to the selected service

The same is true for system services.

To Reproduce

Steps to reproduce the behavior:

1. Go to '/columbia-south-carolina-health-care/locations/anderson-va-clinic/addiction-and-substance-use-care'
2. See under the "Service name and description" there are bunch of other fields from the service term that should not be showing.

AC / Expected behavior

• [ ] on VAMC system service nodes I should not see these.
• [ ] On VAMC facility service nodes I should only see the appropriate VAMC description or Lovell description and fields in green
• [ ] should appear in a tooltip like VBA services

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here. Reach out to the Product Managers to determine if it should be escalated as critical (prevents users from accomplishing their work with no known workaround and needs to be addressed within 2 business days).

Desktop (please complete the following information if relevant, or delete)

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Labels

(You can delete this section once it's complete)

• [x] Issue type (red) (defaults to "Defect")
• [ ] CMS subsystem (green)
• [ ] CMS practice area (blue)
• [x] CMS workstream (orange) (not needed for bug tickets)
• [ ] CMS-supported product (black)

Team

Please check the team(s) that will do this work.

• [ ] CMS Team
• [ ] Public Websites
• [x] Facilities
• [ ] User support
• [ ] Accelerated Publishing

[davidmpickett]

I fell down some pretty deep rabbit holes trying to understand this today. Some things I learned which may or may not help narrow down the issue:

1) The VAMC Facility Health service node.view display is referencing the VAMC System Health Service as a Rendered Entity with the Teaser View Mode. So the root problem can't be on VAMC Facility Health Service, it's inheriting this issue from VAMC System Health Service.

2) The VAMC Facility Health Service in turn is referencing the "Service Name" (field_service_name_and_descripti) and displaying that as a rendered entity with the Default View Mode. I thought it might be as simple as updating that View Mode to fix this, but my attempts to do that didn't seem to bear any fruit.

3) I traced the source back even further to the vha_health_service_taxonomy View, and spent some time fiddling with Displays within the View etc to try and figure something out, but was out of my depth at that point. Views are complicated

[davidmpickett]

Still not sure if I'm getting anywhere near the root of the issue, but I did learn why this isn't an issue on Vet Center Facility Services, because they don't use the Rendered Entity approach, they just are pulling in the service title

[davidmpickett]

Proposed solution:

1. Create a new Taxonomy Term View Mode (admin/structure/display-modes/view/add/taxonomy_term).
2. Update the Display of VA Services and under Custom Display Settings enable the View Mode you just made (admin/structure/taxonomy/manage/health_care_service_taxonomy/overview/display)
3. Switch to the new tab that just appeared and move all the unwanted fields to disabled
4. Update the VAMC System Service Default and Teaser displays to have Service Name be Rendered this new View Mode instead of Default

1

2

3

4

[davidmpickett]

Example of end result

[davidmpickett]

Proof of concept on tugboat attached to this PR: https://github.com/department-of-veterans-affairs/va.gov-cms/pull/15609

[xiongjaneg]

Question: Does this only apply to VAMCs?

Christian is not seeing it on Vet Centers.

[Agile6MSkinner]

From what I can see here, we're not even close to being able to point this. Moving it to the backlog.