Docs
Smart attributes
Your filenames already are a database. These are its columns.
KESSEL_DANDELION_010_ANI_RB_v014.c4d — you read project, asset, shot, stage, artist, version without thinking. Plaza reads the same thing and turns each part into a live, filterable, read-only column. Nothing is written to your files; rename the file and the columns update.
What gets detected
| Column | From | Example |
|---|---|---|
| Version | v + digits, v01.08 minor versions too | v014 → 14 — and current vs superseded within its family |
| Stage | a token from your editable stage dictionary | ANI → Animation, with its pipeline color |
| Owner | 2–4 initials after the stage | RB → a colored chip |
| Shot | shot/scene codes, including bare numbers | 010 |
Version status is the quiet hero: within a family of …_v012 / _v013 / _v014, Plaza knows which one is current and marks the rest superseded — the end of eyeballing a sorted list to find the latest.
Teaching Plaza your convention
Open Planning ▸ Manage ▸ Smart attributes. The bench shows a real filename from your project dissected live: each detected part is highlighted, and clicking a part teaches the parser what that position means. The stage dictionary is fully editable — your tokens, your labels, your colors — and the separator is per-project. Files that don't match the schema are collected in one place with an assisted Rename… that suggests a conforming name.
No convention? Turn Smart attributes off and Plaza is still a tagging, planning and moodboard layer. If you'd like to adopt one, the pattern that parses best is [Project_]Asset_Stage_Owner_vNNN.ext — one separator, version last, zero-padded.