Skilirium

Recognises attributes held as name-value rows

K-507 · Skill knobit · Activity: Derive the logical data model · Competence: Data modelling

An entity whose rows are name-value pairs holding what should be attributes. Each property loses its type, domain, optionality and relationships, and nothing stops two rows giving the same property two values. A specific form of row 30.

Can AI do this?

Not tested yet

No AI benchmark covers this knobit yet. New results are announced in the Can AI Do the Job? newsletter.

What it looks like in practice

Expected result: The name-value entity and the properties that should be typed attributes

How it is assessed: Flags the deficient case and passes the acceptable one. Deficient: Account Property (Account, Property Name, Property Value), with account status, interest rate type and overdraft limit all as Text Acceptable: Explicit attributes on Account or its subtypes (rows 16, 19). If the properties are open-ended by business decision (a product catalogue where the business adds product features weekly), record that with a waiver, and keep a Property Definition entity holding each property's type, unit and value set

Also known as: Attributes held as data (EAV) (logical model)

Related knobits

Builds on

All 56 knobits of Derive the logical data model.

Source: Review checklist 05-logical, row 7; Karwin, Entity-Attribute-Value; Fagin 1981