Categories
Blueputto Categories are reusable taxonomies for classifying items across collections, managed centrally with colors, descriptions, and drag-and-drop ordering.
Grzegorz
Categories are Blueputto's reusable taxonomy for classifying item records. They help teams describe what an item is, what theme it belongs to, or how it should be grouped across Collections without changing the item's operational state.
That makes categories different from Statuses. A status tells users where an item currently is, such as in storage or on display. A category tells them how that item should be classified.
One taxonomy reused across many items
Categories are managed centrally in settings, then reused throughout the item workflow. A team can define labels such as Painting, Loan, Education, Furniture, or Textile once and apply them again and again across different collections.
Because categories are reusable, they work well for classifications that cut across ownership boundaries. One collection might group records by department, while categories still capture subject, material, or program type across the whole organization.
In the current implementation, each category includes:
a name,
a color,
an optional description,
and an explicit order.
Managed centrally, not collection by collection
The settings page is where teams create new categories, rename them, change colors, update descriptions, and reorder the full taxonomy with drag-and-drop.
That central management matters because categories should stay consistent. If every collection had to invent its own local category names, the taxonomy would fragment quickly and become harder to filter, compare, or maintain.
Deletion is also handled at the category level. If a category is removed later, Blueputto removes it from the items that use it, but the item records themselves remain intact.
Applied directly in everyday item editing
Categories become visible again inside the single-item page. In the current implementation, the item sidebar includes a searchable multi-select control for assigning categories to the current record.
That means the same centrally maintained taxonomy shows up directly where item work happens. Teams do not need a separate classification tool or a hidden metadata screen to use it.
This is also why categories work well with other structural features. A team can place an item in one collection, assign one status, attach several categories, and layer structured metadata through Data Models, all inside the same record.
