Skip to main content

Help

Understanding custom fields

Updated October 2026

Collectd ships no fixed schema. You decide what each item records, and those decisions become the form you fill in, the columns you sort by, and the details visitors see on each item in your public gallery.

Two rules govern the editor: a collection needs at least one field before it will save, and one Text field carries the primary title.

The primary title

A primary title can only live on a Text field. Set it with the crown icon on any text field, and move it later the same way. One field holds it at a time.

The primary title is the item's name on its card, in list rows and search results, in gallery headers and in the browser tab. Choose the piece of data that identifies the item on its own, such as a comic title, a card name or an album name.

A primary title stays public. You cannot turn Private on for it, because the gallery has no other label for the item.

The ten field types

TypeUse it forReach for something else when
TextTitles, names, artists, set namesThe value runs to several lines (Textbox) or comes from a fixed list (Dropdown)
TextboxDescriptions, condition notes, provenanceThe value fits on one line (Text)
NumberQuantity, page count, edition numberYou are recording money (Price) or a year (Year)
DropdownCondition, publisher, format, rarity, platformThe value is free text (Text) or a plain yes/no (Yes/No)
Yes/NoGraded, sealed, complete in box, autographedThere are more than two answers (Dropdown)
DatePurchase date, release date, grading dateYou care about the year alone (Year)
PriceValue, purchase price, market priceThe number is not money (Number). Holds one of ten currencies, chosen per field
RatingYour own score, out of 3, 5 or 10The number is objective (Number or Dropdown)
YearRelease year, publication yearYou need the full date (Date)
MeasurementDimensions and weightThe number carries no unit (Number). You name the units, such as cm, in and kg

Set the type when you add the field. It cannot change afterwards. Labels, order, required state stay editable, so changing a type means removing the field and adding a new one.

Designing the schema

  • Start with three to five fields. Add the rest once items exist and you know what you keep looking up.
  • Make identifying fields required. Item name, issue number and year hold the record together. Leave notes and ratings optional.
  • Name fields the way a collector talks. “Issue #” beats “issue_number”, and the label shows on the public gallery.
  • Use Dropdown for fixed sets. Conditions, publishers and platforms stay consistent, and dropdown values drive gallery filtering.
  • Order for the card view. Item cards show the first four fields, so put identifying data at the top.
  • Mark a field private when it holds something you track for yourself, such as a purchase price or a storage location. Private fields stay out of the public gallery.

Free holds ten fields per collection. Pro holds forty.

Schemas by collectible

CollectibleA schema that works
ComicsName (Text, primary), Issue # (Number), Publisher (Dropdown), Year, Condition (Dropdown), Value (Price), Notes (Textbox)
Trading cardsCard Name (Text, primary), Set (Dropdown), Card # (Text), Rarity (Dropdown), Foil (Yes/No), Condition (Dropdown), Value (Price)
VinylAlbum (Text, primary), Artist (Text), Year, Label (Dropdown), Pressing (Text), Media Condition (Dropdown), Sleeve Condition (Dropdown), RPM (Dropdown: 33, 45, 78)
Video gamesTitle (Text, primary), Platform (Dropdown), Region (Dropdown: NTSC, PAL, JPN), Complete in box (Yes/No), Condition (Dropdown), Purchase Date (Date)
BooksTitle (Text, primary), Author (Text), ISBN (Text), Format (Dropdown: Hardcover, Paperback, eBook), Genre (Dropdown), Year, Rating
Action figuresName (Text, primary), Line (Text), Manufacturer (Dropdown), Scale (Dropdown), Boxed (Yes/No), Release Year (Year), Value (Price)

Start from any of these, then edit the fields to match your shelf.

Start a collection and the editor opens with the Fields panel, where the schema takes shape.