# Overview ## Glossary Use this glossary as a reference when working with data modeling, product structures, workflows, and integrations. Each term is written to be concise, consistent, and easy to understand. Where relevant, follow links to deeper documentation. *** ### How to use this page * **New to Struct PIM?** Start with *Product*, *Attribute*, and *Product Structure* * **Working with data modeling?** Focus on *Attributes*, *Data Model*, and *Segmentation* * **Working with integrations?** See *API*, *Webhook*, and *Import/Export* *** ## Core Data Model These concepts define how data is structured in Struct PIM. *** #### **Attribute** A field used to store data (e.g. text, number, media, reference). Attributes are the fundamental building blocks of all entities. *See also:* [Product](#product), [Variant](#variant), [Data Model](#data-model) *** #### **Attribute Type** Defines the format and behavior of an attribute (e.g. text, number, boolean, media, reference, complex). *** #### **Attribute Group** A visual grouping of attributes used to organize fields in the interface. *** #### **Attribute Scope** A logical grouping of attributes used for specific contexts such as channels, APIs, or integrations. *** #### **Complex Attribute** An attribute composed of multiple sub-attributes, allowing structured data within a single field. *** #### **List Attribute** An attribute that can contain multiple entries (rows), each following a defined structure. *** #### **Global List** A reusable set of predefined values (e.g. colors, brands) used in selection fields. *** #### **Global List Value** An individual value within a global list. *** ## Products & Structure These concepts define how product data is organized. *** #### **Product** The primary entity representing an item. Contains shared information such as name, description, and general attributes. *See also:* [Variant](#variant), [Product Structure](#product-structure) *** #### **Variant** A variation of a product (e.g. size, color). Variants inherit shared data from the product and contain variation-specific information. *** #### **Variant Group** A grouping of related variants used to organize complex product setups. *** #### **Product Structure** Defines how products and variants are built, including layout, sections, and assigned attributes. {% hint style="info" %} Think of this as the *blueprint* for your product data. {% endhint %} *** #### **Product Model** Defines which attributes apply to a product and how they are organized. *** #### **Variant Model** Defines which attributes apply specifically to variants. *** #### **Variant Group Model** Defines which attributes apply specifically to variant groups. *** #### **Variation Definition** Specifies which attributes differentiate variants (e.g. size, color). *** #### **Identifier** A unique value used to identify a product, variant group, category or variant (e.g. SKU). *** ## Organization & Classification These concepts help organize and group data. *** #### **Catalogue** A collection of products grouped for a specific purpose, such as a market or channel. *** #### **Category** A classification used to organize products. *** #### **Primary Category** The main category assigned to a product. Can determine which category-specific attributes apply. *** ## Data Management These concepts define how data is handled across contexts. *** #### **Localization** The ability to store values per language or region. *** #### **Segmentation** The ability to define data variations across dimensions such as markets or channels. *** #### **Enrichment** The process of improving and completing product data. *** #### **Enrichment Insights** Tools used to measure data completeness and quality. *** #### **Data Model** The overall structure of how data is defined and related in Struct PIM. {% hint style="info" %} Includes attributes, entities, and relationships. {% endhint %} *** ## Workflow & Automation These concepts control processes and automation. *** #### **Workflow** A defined process used to manage tasks and data progression. *** #### **Task** A unit of work assigned to users within a workflow. *** #### **Business Rule** An automated rule that triggers actions based on conditions. *** #### **Notification** A system-generated message informing users about events or required actions. *** ## Integration & Data Flow These concepts describe how Struct PIM connects with other systems. *** #### **API (Application Programming Interface)** A programmatic interface used to interact with Struct PIM. *** #### **Webhook** A mechanism that sends real-time updates to external systems when changes occur. *** #### **Import** A process for bulk creating or updating data. *** #### **Export / Publication** The process of distributing product data to external systems or channels. *** #### **Messaging** Infrastructure used for reliable communication between Struct PIM and external systems. *** ## UI & System Features These are key features in the user interface. *** #### **Dashboard** A customizable interface for monitoring data, workflows, and tasks. *** #### **Search** Tools for finding and filtering entities using queries and filters. *** #### **Saved Search** A stored search configuration that can be reused. *** #### **Changelog** A record of changes made in the system over time. *** #### **Revision** A stored version of data used for tracking history. *** ## Media & Assets These concepts define how digital files such as images, videos, and documents are managed in Struct PIM. *** #### **Media** The module used to store, manage, and organize all digital assets in Struct PIM. Media acts as a central hub and single source of truth for files used across products and workflows. *** #### **Asset** An individual file stored in Struct PIM, such as an image, video, or document. Assets are managed within the Media module and can be reused across multiple entities. *** #### **Media Library** The complete collection of all assets available in Struct PIM. *** #### **Asset Folder** A container used to organize assets into a hierarchical structure. Asset folders help structure large collections of assets and improve overview. *** #### **Asset Tag** A label assigned to an asset to improve searchability and organization. Tags provide a flexible way to group assets across folders. *** #### **Media Link** A connection between an asset and another entity (e.g. product or variant). Defines how an asset is used in a specific context. *** #### **Asset Usage** Describes the purpose of an asset when linked to an entity (e.g. product image or document). *** #### **Hotspot** An interactive point placed on an asset (typically an image) that links to additional information. Used to enrich visual content with context. *** #### **Asset Type** Defines which attributes apply to assets and how asset data is organized. *** ## User & System Management These concepts define access and configuration. *** #### **User Management** Administration of users, roles, and access. *** #### **Permissions** Rules that define what users can view and modify. *** #### **Settings** Configuration options that control system behavior. *** ## Related documentation * [API Reference](/api-reference/introduction.md) * [Tutorials](/tutorials/overview.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.struct.com/glossary/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.