-
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
Draft content spec for VBA Facility content type #13130
Comments
@kmariepat-cityfriends The following fields are not accounted for in the design:
|
@kmariepat-cityfriends With the exception of the parent office, it seems like we should be definitely surfacing the others ^^ Parent office I am not sure if that means anything to Veterans. We'd have to consult with RO personell to see if they think it is important. |
@swirtSJW @omahane thank you for the guidance and info. I have a meeting with RO managers next week so I will ask there, after confirming with Dave C. that I can, FWIW I think this makes sense too. Also I will let @thejordanwood know to add representation of those fields in her design |
This already came up in both rounds of research. The Parent Office field is relevant for Satellite Offices because Veterans have an understanding that the Regional Offices tend to be one stop shops. In speaking to Public Contact Staff, we also learned that having that relationship is important for issue escalation.
In #13510 there is conversation around exactly where we would show the Parent Regional Office on Satellite Office pages. Possibly at top of "Other nearby VA locations" or might need a separate header but still be in that vicinity |
@davidmpickett @swirtSJW "Other nearby VA Locations" is one section of the VBA Facility design. A relevant example is here I know the locations_listing and vet_center_locations_listing have field_office that relates the listing to the facility. What's not clear to me is how the "Other nearby Vet Centers" works. Given that this is similar to the VBA design, I am unclear by what means these will be connected. |
This is an outstanding product direction question that @kmariepat-cityfriends and @mmiddaugh are aware of . Not sure if this is going to be manually populated or automagically determined. For now, fill out fields that you can without knowing the exact implementation (e.g. we know it will be an entity reference, cardinality will probably be capped at 3-5) and leave comments in the stakeholder notes column about need for direction. |
@davidmpickett The artifact has been updated to the extent I can do so. |
@swirtSJW Could you take a look at this? I'd like your feedback/input. |
I put this in Slack but adding here for better tracking: The only issue I am seeing so far and clarifying are the Required: yes? Now when we flip it so that CMS is the source of truth for VBA, then we would have unlock those fields AND make them required |
@davidmpickett This is ready for your review/sign-off. |
@kmariepat-cityfriends This is ready to close. |
One note on the doc still has a question about facility status. I created this issue to help refine that particular piece #14546 |
Description
AS A Drupal engineer,
I WANT a technical design document
SO THAT there is nothing ambiguous about the implementation requirements.
AS A PO, CMS team member or stakeholder
I WANT to see a detailed content spec
SO THAT I can review the design before implementation
Example artifact
Supporting documents
Artifact
Drupal Content Spec VBA Facility content type
Acceptance Criteria
The text was updated successfully, but these errors were encountered: