Open davidmpickett opened 2 months ago
@davidmpickett Are the same AC tasks needed to update the title case changes for Veterans Pension and VR&E or just for the name update to Military service records?
@omahane @dsasser - Would we need to do the bulk renaming for just a capitalization change? Or is Drupal agnostic to label case?
@davidmpickett I don't see in this ticket what we are changing from and to. Could you update the ticket with this?
Also, if we're making changes to the labels, which filter down into the service name itself, we should do a bulk edit. It's not hard and can be done in the UI.
@davidmpickett I don't see in this ticket what we are changing from and to. Could you update the ticket with this?
Updated with a before and after table. Two of them are just capitalization changes, whereas the other one would be adding a word. @mmiddaugh and I weren't sure if changing capitalization needed the bulk update steps or not.
Thanks, @davidmpickett. Honestly, I think the front-end won't need it at all for any of these changes. But if we want Drupal and the FE to be aligned, it's best to do the bulk edit.
Which Taxonomy is this term for?
VA services taxonomy
Link to existing terms
https://prod.cms.va.gov/health-care/military-records https://prod.cms.va.gov/health-care/veterans-pension https://prod.cms.va.gov/health-care/veteran-readiness-and-employment-programs
Term changes
Rationale for updating this term
CAIA feedback in https://github.com/department-of-veterans-affairs/va.gov-team/issues/74390
Which products will this term impact?
VAMCs, Vet Centers, VBA Regional Office
Have stakeholders from impacted products been consulted?
No
Acceptance Criteria