Relationships Visualizer - Frontend

Title: Create and manage topic-to-topic relationships in CCMS Story Statement:As a Content Engineer, I want to create and maintain links between topics (including many-to-many and reciprocal links), so that related content is explicitly connected and discoverable in the CCMS Business Value: Restores/modernizes relationship-table capability. Improves navigation and reuse across related topics. Reduces manual tracking of topic relationships.

## Story Statement As a content strategist, I want content to be easily reusable across products and platforms so that we can publish consistent information without manual copying. ## Business Value - Lowers authoring cost through higher content reuse. - Improves consistency across platforms and product lines. - Reduces translation cost of duplicated / similar content. - Shortens time-to-publish for updates and variants.

Description Platform Status: in roadmap PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Use Case Do not have to create copies to reuse, for example Current Challenges Currently if marketing changes the term "Accuterminal" to "varioterminal", tech info has to create a "save as" copy and find everywhere version A was originally used and replace it with verison B. Not an affective way to manage content. We could update the title to varioterminal, but the topic name and content holder would still be "accuterminal". Likewise, if we went ahead and changed the topic "name" and content holder, it would change all previous versions - essentially no version control. Requires new content each time which makes managing reuse difficult. Product Owner Notes Need UX and front end

Description Platform Status: PPT Status: MVP: Yes Must Have: Priority 1 (A) Use Case Many topics link to each other or relate. Is this capability possible (link from topic A to B and E and then back to A) Current Challenges Loss of relationship table functionality with PTC WC.

Description Supports component search; regex/xPath; semantic match during editing; future relationship visualiser. Platform Status: partially implemented PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Use Case Does the system support viewing a list of reusable content in the content repository? Current Challenges We can search products for for "name" of the object (essentially the title only) but we cannot search by applied metadata or terms within the topics. For example, we want to search to see if anything has been written about the cab for Fendt 700 because it will be reused in a JAX built product. Or we want to search for anything related to tier4f engines to update a safety step. Notes Superusers xPath or Regex? Not focus on too much. Currently implemented While editing, return a semantically similar component. Should be based on what the user is adding to the topic Admonition, or other sub-topic-component Future implementation Relationship visualiser Query for reusable components based on context What is being written (admonition) Which product Which meta-data filters are applied to the current topic Very XML editor dependant. Product Owner Notes Need UX and front end Notes: Context match; reusable component query; filters; XML editor dependent.