Submission rules
Discogs But Everything catalogs identifiable entities — not personal possessions, condition notes, or one-off anecdotes.
What belongs in the catalog
A valid submission represents one of these:
- A unique model (e.g. PSP-1001, Sunbeam TA2200)
- A hardware revision (e.g. motherboard revision, firmware hardware rev)
- A software release (e.g. a specific OS build or game version)
- A production variant (e.g. region model, colorway SKU)
- A standardized modification (e.g. IPS screen kit for PSP — as its own entry when cataloged)
- An organization (manufacturer, publisher, standards body)
- A person (designer, engineer, public figure tied to a product)
- A place (factory, headquarters — when identifiable and relevant)
- A concept (product class, protocol, format)
- A material (when referenced by other items)
What does not belong
Do not submit an entry that only differs from an existing one by:
- Who owns it
- Scratches, dents, or cosmetic wear
- Serial number (unless defining a documented production batch variant)
- Age or purchase date
- Storage location
- Sentimental or personal value
Do not submit duplicates of existing entries. Search first, then submit edits or request a merge.
Field reference
ID required
Permanent lowercase identifier: letters, numbers, underscores only.
Examples: item_psp_1001_black, org_sony, material_stainless_steel
Edge cases: IDs cannot change after creation. Pick a stable, descriptive ID. Do not use spaces, hyphens, or uppercase.
Name required
Official or most precise name for this specific model, revision, or entity.
Example: PlayStation Portable (PSP-1001)
Edge cases: Include model number when it disambiguates. Do not append “my” or owner names.
Display name
Shorter label shown in lists and search results. Defaults to Name if omitted.
Example: Sony PSP-1001
Category / Subcategory
Category is required. Use consistent naming (e.g. Consumer Electronics → Handheld Game Console).
Organizations: Organization → Electronics Manufacturer
Materials: Material → Thermoplastic
Manufacturer ID
ID of an organization entry — not free-text company name.
Example: org_sony
Edge cases: Submit the organization first if it does not exist. Rebrandings may need separate org entries or clear revision notes in description.
Model / Series
Model: specific model code. Series: product family spanning multiple models.
Edge cases: A series alone is usually not enough for a product entry — submit the specific model variant.
Description
Neutral factual summary: what it is, what distinguishes it, region or market if relevant.
Not for: reviews, opinions, personal stories, pricing, or availability.
Production (released / discontinued / revision)
Dates as YYYY or YYYY-MM-DD. Revision labels factory or hardware revisions.
Edge cases: Leave discontinued empty if still in production. Revision is not a serial number.
Identifiers (UPC / EAN / part number)
Barcode or manufacturer part numbers when known. Leave blank if unknown — do not guess.
Edge cases: Region-specific UPCs may differ; note region in description if submitting a regional variant as its own entry.
Materials
Comma-separated item IDs of material entries.
Example: material_abs_plastic, material_polycarbonate
Edge cases: Avoid raw strings when a material entry exists or should exist.
Colors
Factory colorways for this variant. Comma-separated.
Example: Black, Ceramic White
Edge cases: Custom paint jobs are not catalog entries. A distinct SKU colorway may warrant its own item entry.
Common modifications
Well-known, repeatable mods the community recognizes — not your personal mod.
Example: IPS Display, USB-C Charging, Battery Expansion
Edge cases: If a mod is standardized enough to have its own identity, submit it as a separate modification entry and link via relationships.
Tags
Comma-separated keywords for search. Lowercase preferred.
Example: gaming, portable, retro, homebrew
Specifications (JSON)
Structured technical data as key-value pairs. View example
Edge cases: Use consistent units. Arrays allowed for multi-value specs (e.g. storage types).
Dimensions (JSON)
Physical measurements with units in keys. View example
Example keys: width_mm, height_mm, depth_mm, weight_g
Compatibility (JSON)
What works with this item — media formats, accessories, power requirements. View example
Edge cases: Prefer linking to catalog entries for accessories when they exist.
Related items (JSON)
Directional relationships. View example
Common keys: parent, variants, successor, predecessor
Edge cases: Multiple parents allowed. Circular references allowed. Use item IDs when targets exist; plain names only as placeholders until entries are created.
Images
Product photos, official press images, or clear identification photos. JPEG, PNG, GIF, or WebP only; max 5 MB each.
On edit: toggle visibility per image. Hidden images are kept but not shown on the public item page.
Not for: memes, unrelated images, or photos that only show personal wear.
Edge cases: Unlimited images per item. Prefer neutral backgrounds and accurate color representation.
Moderation
Member submissions and edits are reviewed before publication. Moderators may reject entries that violate these rules, merge duplicates, or request changes via rejection notes.