-
Notifications
You must be signed in to change notification settings - Fork 70
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
Establish and enact VBA facility alias pattern #15155
Comments
Example of a really long path for a facility |
Per CAIA, namespacing request has been denied |
Closing as duplicate. #17351 will address the open question of how/where we cut the long names into condensed names. The condensed names will power H1/Breadcrumbs & URL |
Reopening this, because even without figuring out how we are snipping long names, the URL structure needs to be updated before staging review. |
Right now: NCA / VBA use the same pattern. Split them, please |
@jilladams @davidmpickett I'm going to check prod. While we can't publish VBA or NCA for now, I can check the alias patterns and make sure they are as we expect. |
VBA is now like Vet Center on Prod. And NCA is all by its lonesome. |
@davidmpickett to refine this ticket based on outcomes of #15752
User Story or Problem Statement
Currently VBAs have a pattern of [node:field_administration:entity:name]/locations/[node:title]
We need to update this schema to follow the recommendations out of #15752 that are documented here: https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/facilities/naming-schema#vba-benefits-facilities-naming-schema
BLOCKER: Need to confirm that #15752 (comment) comment has been addressed in documentation before we start work.Not a blocker for this ticket. This ticket will be scoped to just removing the Section/Location aspect of the URL so they are all [Node Title].Acceptance Criteria
The text was updated successfully, but these errors were encountered: