Streamlining the Process to Archive a Closed VAMC Facility #16140
Labels
Facilities
Facilities products (VAMC, Vet Center, etc)
Knowledge Base
[CMS feature] Knowledge Base
Needs refining
Issue status
sitewide
Technical debt
User support
Workstream: The customer journey of CMS users, from onboarding to support services, etc.
User Story or Problem Statement
As a VAMC editor who has had a facility within my system shut down, I am a bit overwhelmed by the steps involved in the facility archival process.
The current process listed in the Knowledge Base article "How to archive a closed facility" is tailored to VAMC editors whose closed facility has not yet been reported to VAST.
However, if I've already been informed that my facility was removed from VAST / the Facilities API (typically through Help Desk correspondence after the facility was reported as "Removed From Source" within the Flagged Content listing), then the rest of the steps seem like a lengthy wall of text, and I'm unsure why I need to do anything else on my end.
I would like this process to be streamlined for maximum efficiency to cut down on the amount of steps that VAMC editors need to perform on their end, and to reduce back-and-forth comms between VAMC editors, the CMS Helpdesk, and the Facilities engineering team.
Description or Additional Context
See current article: https://prod.cms.va.gov/help/vamc/about-locations-content-for-vamcs/how-to-archive-a-closed-facility
Ideas for streamlining this process:
Steps that can likely be completed by the Facilities engineers / Drupal admins:
Steps that can likely be removed altogether:
Proposed draft written by @stefaniefgray after Flagged Facilities check-in on 11/15/23: https://docs.google.com/document/d/1ln_kZ7qdgfl0VlNm2kXKMxTb7tEdKjCOHGTJk0toyHQ/edit?usp=sharing
Steps for Implementation
Acceptance Criteria
Team
Please check the team(s) that will do this work.
The text was updated successfully, but these errors were encountered: