Advanced Search - Frontend

## Story Statement As an author, I want unified and advanced search for reusable content across author, phrase, keyword, and metadata criteria so that I can quickly locate the best existing content and avoid duplicate authoring. ## Business Value - Speeds authoring by reducing time spent finding content. - Increases reuse and lowers duplicate content creation. - Reduces translation cost of duplicated / similar content. - Improves consistency of terminology and technical guidance.

Description Platform Status: supported PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Current Challenges Toolset currently allows search by product context, name, number, last modified date, created on date, keyword, object type, and organization name Notes solved by last requirement, advanced search Product Owner Notes Need UX and front end

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.