Attributes are customizable pieces of metadata attached to properties, entrances, or units to capture specific information tailored to various operational requirements. They are organized within attribute groups, allowing structured and flexible data management that extends the core entity details.

Terminology

ER Diagram. `REFERENCED_ENTITY` can either be `Property`, `Entrance`, or `Unit`

AttributeGroupType (Static data): Defines available types for an AttributeGroup. For example, the type “Allgemein” (ID: 1) is a standard, unchanging group type used universally.
AttributeGroup: Logical grouping of multiple instances of AttributeValue attached to a specific property, entrance, or unit. Upon creation, an external ID can be supplied to link this group to your own internal identifiers.
Attribute (Static data): Defines the individual types of Attribute available within a certain AttributeGroupType. For example, the Attribute “MessdienstleisterID” (ID: 1437) represents a specific data point and is built into the platform.
AttributeValue: The actual value of the type Attribute within a defined AttributeGroup.

Usage

Attributes are created and managed via the API, enabling integration with external systems and flexible customization. They allow property management companies to store tailored information such as meter provider IDs, special notes, or other relevant metadata tied to the operational context.

Purpose

Attributes help to maintain a clean and adaptable data model by decoupling extended metadata from the main entity definitions. This allows for scalable and customer-specific extensions without complicating the core database schema.