Configurable Metadata Taxonomy and Multi-Level Application
Done
#3395
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.
Acceptance Criteria
- Given metadata taxonomies are maintained, when administrators update taxonomies, then updates can be added without schema breakage.
- Given evolving business needs, when taxonomy changes occur, then existing content remains manageable.
- Given content at multiple structural levels, when metadata is applied, then level-specific metadata is supported.
- #Feature test
- Validate that meta data can be applied on object level
- Validate that meta data can be applied on version level
Digital-First Information Model (Recipe mgmt.)
Test
#3390
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.
Acceptance Criteria
- Given content is modeled for digital delivery, when users assemble outputs, then topic-level delivery is supported.
- Given metadata-driven use cases, when content is queried, then model structures support precise retrieval.
- Given publication and digital needs coexist, when workflows run, then both modes can be supported.
- #Feature test
- Set different type of meta data on topic level
- Create recipe and recipe nodes with meta data critera
- Validate that topics with correct meta data are shown in the recipes
- Add a facet in a recipe and validate that the topics are correctly filtered
Filtered Publishing (Release manager)
Approved
#3402
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.
Acceptance Criteria
- Given profiling and filtering rules are configured, when outputs are generated, then only matching content is included.
- Given variable-driven terms are defined, when variants are produced, then variable substitutions are correct.
- Given complex product hierarchies, when selection criteria are applied, then output scope reflects chosen configuration.
- Given a release references specific versions, when publishing runs, then the configured version-selection rules are applied consistently.
Metadata-Preserved Publishing (Release manager)
Approved
#3400
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.
Acceptance Criteria
- Given content is published, when output are created, then associated metadata is included.
- Given downstream systems parse metadata, when content is ingested, then identifiers and classification attributes are usable.