An entry schema defines the structure of entries for a tag. It decides which fields an entry should contain, how those fields are shown, and which information can be collected over time.

Profile blocks are best for information that belongs directly on the public profile. Entry schemas are best for repeatable records, such as maintenance logs, inspections, reports, notes, or service history.

What a schema defines

• Fields: the pieces of information each entry can contain, such as text, numbers, dates, links, images, icons, or yes/no values.
• Labels: the names shown to users when they create, edit, or view an entry.
• Required fields: fields that must be filled in before an entry can be saved.
• Overview fields: selected fields that can appear in entry lists or summaries to make records easier to scan.
• Layout: the arrangement of fields when entries are displayed or edited.

Common examples

• A maintenance schema might include date, mileage or operating hours, work performed, cost, notes, and images.
• An inspection schema might include date, result, inspector name, condition notes, and photos.
• A pet record schema might include visit date, vet name, treatment, medication, and follow-up notes.
• An inventory schema might include status, location, check-out date, responsible person, and remarks.

Draft schema and active schema

Zwyn can separate a draft schema from the active schema. The active schema is used for current entries. A draft lets owners prepare schema changes before publishing them.