Discovery: Usage Tab

[gracekretschmer-metrostar]

User Story or Problem Statement

Description or Additional Context

Look into opening up the usage tab to all editors to address the outdated content that goes out to editors. Right now, the usage tab is only available to admin and help desk have to support the editors. There may be opportunity to bring in the knowledge base.

Steps for Implementation

• [ ] Evaluate how and where the usage tab could be better use for supporting editors
• [ ] Investigate the risk of opening feature to VA editors
• [ ] UX review to ensure the feature is usable and useful for VA editors
• [ ] Update the knowledge base to allow VA editors to understand how to use the feature

Acceptance Criteria

• [ ] A plan of action on how to open the usage tab to editors.

### Tasks
- [ ] https://github.com/department-of-veterans-affairs/va.gov-cms/issues/18441

[ian-sears]

Use case: Editors needing to Archive a node, currently do not have a Broken Links mitigation tool. IF an Editor can be KB instructed to first remove Inbound links, less long-tail broken links are needed.

[gracekretschmer-metrostar]

Next steps: have this work get pulled into the Knowledge Base Redesign epic.

[MDomngz]

Drupal's background on the Usage Report tab -

Adds a "Usage" tab to content entities which shows editors all entities which reference the entity, including following up (recursively nested) Paragraphs

This helps editors find all back-references for the current node, and will handle any entity reference or entity reference revision field.

Includes a CSV export and JS-filterable columns

No configuration. Set the permission for roles who should see the 'usage' tab.

[gracekretschmer-metrostar]

Before implementation, @MDomngz wants to better understand the use case,