Attribute Library

The Attribute Library is Actualog’s shared dictionary of reusable product characteristics.
It lets you define an attribute once (meaning, type, units, allowed values, translations) and then link it to many categories—so product data stays consistent across catalogs, partners, and integrations.

Why it matters

A well-governed attribute library is the backbone of industrial PIM/MDM because it enables:

• One meaning, everywhere
  The same attribute (e.g., Weight, Nominal voltage, Ingress protection) behaves identically in every category that uses it.

• Comparable data at scale
  When multiple categories share the same attribute definition, users can filter, compare, and validate products reliably.

• Fewer duplicates and less “Excel entropy”
  You avoid having ten slightly different versions of the same attribute (e.g., Weight, Net weight, Weight (kg)), which breaks search and integrations.

• Stronger governance and quality control
  Data types, ranges, tolerance rules, unit rules, and value domains are enforced consistently in UI, imports, and APIs.

• Multilingual consistency
  A library attribute has one controlled meaning with multilingual labels and synonyms—so translations don’t drift between categories.

• Better discovery and faceted navigation
  Library attributes are the natural source for facets and filters (because they are standardized, typed, and reusable).

• Integration-ready master data
  Shared definitions reduce mapping effort when exchanging product data with ERP/MDM/eProcurement and industry catalogs.

Typical library attributes (examples)

Library attributes are usually cross-category and reusable, such as:

• Physical properties: Weight, Length, Width, Height, Volume, Density
• Performance: Nominal power, Voltage, Current, Pressure rating, Temperature range
• Materials & construction: Material, Coating, Insulation type, Protection class (IP)
• Compliance & standards: Standard/Norm, Certificate type, Hazard class (where relevant)
• Commercial/logistics: Country of origin, Packaging unit, Warranty period
• Identity & classification: Brand, Manufacturer part number (MPN), Model, Series

(Use category-specific attributes only when the meaning is truly unique to one product class.)

Library attribute vs category-specific (contextual) attribute

Use a Library Attribute when:

• the same characteristic is meaningful in multiple categories,
• you want the same units/values/rules everywhere,
• you expect the attribute to become a common filter/facet.

Use a Contextual Attribute when:

• the characteristic is valid only in one narrow category,
• the meaning changes across categories,
• or the attribute is experimental and not ready for reuse.

Governance and lifecycle (how the library stays clean)

Actualog treats library attributes as governed assets:

• Single definition, controlled change
  Updates to a library attribute (definition, units, value list, constraints) are tracked and applied consistently to every category that uses it.

• Safe evolution
  Attributes can be refined without breaking existing product data through controlled updates, audit history, and (where enabled) lifecycle states such as Draft / Approved / Deprecated.

• Standards alignment (where applicable)
  Library attributes can be aligned with external property dictionaries and standards to improve interoperability and reduce downstream mapping.

What this enables long-term

When your attribute library is strong, you can scale faster:

• build new categories quickly by reusing proven attribute templates,
• publish catalogs that are consistently searchable and comparable,
• accelerate imports and partner onboarding,
• and apply AI-assisted enrichment and data-quality checks safely—because the underlying attribute semantics are stable.