Recipe Management - Frontend

## Story Statement As an integration consumer, I want published content to include associated metadata so that downstream systems can identify, filter, and process content correctly. ## Business Value - Improves content filtering and precision in delivery channels. - Supports scalable taxonomy management across products. - Increases downstream automation through richer metadata context.

## Story Statement As a metadata manager, I want configurable metadata taxonomies (domains and values) and multi-level metadata assignment so that taxonomies can evolve and be applied consistently across recipe, topic, and element levels. ## Business Value - Improves content filtering and precision in delivery channels. - Supports scalable taxonomy management across products. - Increases downstream automation through richer metadata context.

## Story Statement As a IA, I want to apply profiles and classifications to content and recipes so that each output variant matches the intended product configuration. ## Business Value - Improves publishing throughput and release predictability. - Reduces output defects across variants and formats. - Strengthens downstream readiness with consistent publish artifacts.

## Story Statement As a digital delivery lead, I want a topic-based information model so that content can be delivered dynamically instead of being constrained by publication-only workflows. ## Business Value - Enables digital-first delivery beyond publication-centric workflows. - Improves content discoverability and targeted delivery. - Supports scalable reuse through topic-based architecture.

Description Platform Status: partially implemented PPT Status: Roadmap MVP: Yes Must Have: Priority 1 (A) Notes What do they want in detail. If we have an object, that has classification metadata, where we publish it needs to receives an id denoting the origin of the topic. In the future potentially include related metadata. For fully dynamic delivery metadata is needed. Possible, applying invisible character to published PDF for metadata tagging Figures get hidden GUIDs on publication

Description Supports DITA authoring formats; DITA-OT implementation pending. Platform Status: partially implemented PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Notes DITA OT Not implemented yet Format implemented Is your DITA-OT out of the box or configure and customised. Currently authoring in DITA, don't want a different format. Product Owner Notes Not implemented DITA-OT Notes: DITA OT not implemented yet; implemented format; clarify OT configuration; maintain DITA authoring.

Description Platform Status: supported PPT Status: Yes MVP: Yes Must Have: Priority 1 (A) Use Case Brands, models, audience, VIN or salescodes, ID, any future needs. Current Challenges Metadata setup in current tool is managed by multiple teams and (depending on the data) can be tied to a deployment. Notes by classification metadata and profiles Profiling, classification, domains, metadata Hierarchical structures: Apply content based on taxonomical structure Produt family->Product->Version. Mapping VIN numbers to metadata filters handled externally Given a list of feature codes (w. description) and they map VIN to feature codes.

Description Platform Status: supported PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Notes Challenge here would be migration Have to use the engineering handling, clunky. Product Owner Notes Recipes need to be implemented.

Description Platform Status: partially supported PPT Status: Partly MVP: Yes Must Have: Priority 1 (A) Use Case For example selection of conditions to produce manuals with different engine or transmission types, brands, models, etc. Notes this is profiling, we have not discussed variables - Tobias variables are used for marketing terms, differs between brans. How would one variable look like in a title? - Matthew How variables look in a title of an object. Complex conditions, "profile" conditions. NOT: Apply to Sweden & Norway, you are only ever interested in one facet at a time. Faceting: Profile and inline profiling Product Owner Notes Inline profiling and recipes need to be implemented to fully validate functionality