Collection
A Collection groups Items that share one field schema, one link-generation rule, one scan behavior, and one page template. It belongs to a team, and every Item belongs to exactly one Collection. In URL templates and conditions, the namespace for Collection values is stillcollection. — write {{collection.name}}, because collection.name returns an empty string with no
error. See What Is a Collection?.
Item
An Item is the individual record a Collection tracks: one machine, one room, one product, one extinguisher. What data it holds is decided by its Collection’s fields, and it can carry one or more Links. See What Is an Item? and Core Fields vs. Custom Fields.Link
A Link is a QRtub-managed URL, likeqrtub.com/r/x5fgd, that resolves to a destination. A QR
code is one way to encode it — an NFC tag or a typed address work the same way. Links belong
to the team rather than to a Collection, so any Link can be assigned to any Item the team
owns, or to nothing at all. See What a Link Is.
Page
A Page is the mobile screen a Link can open, holding one or more Destinations for the person scanning to choose from, and built in the Page Editor. A Link that skips the Page and redirects straight to a single Destination is in Direct Mode; a Link that opens a Page is in Page Mode. See Pages Overview and Direct Mode vs. Page Mode.Media
Media is the physical thing the QR code lives on — a vinyl sticker, an engraved plaque, a sign, an NFC chip — with a lifecycle of its own, often longer than the Item it is attached to. QRtub tracks production runs as print batches; it does not keep a per-code record of material, cost, or installation location. See What Is Media? and Print Batches.Related
- Creating Your First Link — these five in one worked example
- The Print-First Workflow — why printing before the data exists is normal here
- What Is a Destination? — where a scan actually ends up