#
Data Model
#
Technical Support: Data Model
This page describes the example domain model used in the Technical Support demo repository. Use it as inspiration for how to think about entities, relationships, and searchable fields.
#
Example entities
- Device: product/device names
- Part: parts associated with devices, with manufacturer metadata
- Manufacturer: normalized manufacturer entity (useful for navigation and filtering)
- SupportCase: a case/ticket with summary, content, status, and timestamp
- SupportCaseMessage: parsed messages extracted from case conversations
- Status: normalized status entity (useful for shared facets)
#
Example relationships
Device -> HasPart -> PartPart -> HasManufacturer -> ManufacturerSupportCase -> ForDevice -> DeviceSupportCase -> HasStatus -> StatusSupportCase -> HasMessage -> SupportCaseMessage
#
Why this model works well
- It supports entity-centric navigation (device/manufacturer pages).
- It supports graph-constrained search (search within a manufacturer/device).
- It separates attributes (properties) from entities (nodes) where navigation/faceting matters.
#
Cross-links to product docs
- Modeling guidance: Schema Design
- Querying patterns: Graph Query Language