Collections

What is a Collection?

A Collection is a reusable schema that specifies:

• What fields a resource should have (e.g. name, image, number, color).

• What type of value each field should accept (text, image, color, boolean, etc.).

• How the data is organized and referenced across your project.

For example:

• A "Player" collection might include:
  → Name (text)
  → Role (text)
  → Photo (image)
  → Age (number)

• A "Team" collection might include:
  → Team Name (text)
  → Logo (image)
  → Primary Color (color)
  → Players (nested collection of type "Player")

Nested Collections

Collections can include other collections.
This is perfect for hierarchical data. For example:

• A Team collection can reference a Player collection as a nested field.

• This allows Quadraviz to treat each player inside the team as an individual dynamic object with its own fields.

  When using nested collections, make sure to create the child collections first (e.g., Player) before creating the parent collection (e.g., Team). This ensures you can link them properly during setup.

Why Use Collections?

• Consistency: Every resource created from a collection follows the same structure.

• Efficiency: Build once, reuse many times. Collections let you create structured, scalable data quickly.

• Dynamic Binding: Collections power Smart Inputs, letting you bind structured data to animations without writing a line of code.

How it Works in Practice

1. Create a collection (e.g. Caster, Map, Sponsor, Match Info).

2. Add the required nested categories to the list.

3. Add the fields you need.

4. Use that collection to create multiple resources of the same type.

5. Plug those resources into your live graphics using Smart Inputs.

Example of a Match Info collection