Veezoo

Module 4 · Lecture 4.5

Links & Power Features

Links, HTML tags, custom units, and ordinal sorting: display settings that change what users see, never the value underneath.

Small display settings decide how finished a Knowledge Graph feels. This lecture covers four of them, each set on a single field in Studio: turning a website attribute into a clickable link, restyling a field with an HTML tag, defining a custom unit so long numbers read at a glance, and giving values with a natural order the right sort.

One rule ties all four together. They change what users see, never the value underneath.

Key points

  • extends: url marks a string attribute as a URL, and Veezoo maps that link onto the parent class.
  • The website column then drops out of the answer, because the customer name itself carries the link.
  • An html tag restyles how any field is displayed, for example showing email addresses in italics.
  • A custom unit is an object tagged kb.unit whose html rule reshapes the number, such as dividing by a thousand and adding a K.
  • Swapping a field's unit, from US dollars to thousands of US dollars, makes long figures readable at a glance.
  • By default a chart sorts by the value, so age groups come out ordered by sales rather than by age.
  • An ordinal class tagged kb.ordinal fixes that once every entity has a sort_id, and the order then holds in every visualisation.

Check your understanding

A customer's website is a string attribute, and you tag it with extends: url. What changes in the answers?

Sales use a custom unit that divides by a thousand, rounds, and shows "42K" instead of "42,180". What happens in a further calculation?

A chart of age groups comes out ordered by sales volume, but it should follow the ages. What do you set up?