Skip to content

Items and item types

What every item has

  • refcode — permanent, globally unique, server-assigned
  • item_id — human-readable, yours to choose
  • type
  • date, name, description
  • creators
  • relationships
  • files
  • blocks

Only the refcode is guaranteed

Nearly every other field is optional, and instances differ in which ones are used in practice. Code that reads items should treat everything else as possibly absent.

The built-in types

Custom types from plugins

Your instance may define additional item types. They behave like the built-ins but carry extra fields specific to your group's workflow. See Extending item schemas.

Editing, duplicating and deleting

  • Editing metadata in place
  • Creating an item from an existing one
  • Batch creation
  • Deleting: who can, and what happens to the files