Projects
The backbone of Pixwel — how a project contains assets, and how assets contain the files that get localized and delivered.
The backbone of Pixwel — how a project contains assets, and how assets contain the files that get localized and delivered.
Almost everything in Pixwel hangs off a three-level hierarchy: a project contains assets, and an asset contains files. Understanding this relationship makes the rest of the platform easier to follow.
graph TD
Studio["Studio"] --> Project["Project<br/><i>e.g. a film campaign</i>"]
Project -->|has many| Asset["Asset<br/><i>e.g. the US trailer</i>"]
Project -.->|logo & loose files| File["File"]
Asset -->|has many| File["File<br/><i>a localized / encoded rendition</i>"]
Asset -->|has many| Preview["Preview<br/><i>lightweight web playback</i>"]
Asset -->|original + translations| Translation["Translation<br/><i>subtitles, dialogue, graphics</i>"]
The individual pieces of creative within a project.
The real, downloadable deliverables of an asset.
The source-language text that localization is built from.
A project represents one campaign — typically a single film — and is owned by a studio. It’s the container everything else lives in.

A project holds:
| Relationship | Cardinality | Meaning |
|---|---|---|
| Studio → Project | one to many | A studio owns many projects |
| Project → Asset | one to many | A project contains many assets |
| Asset → File | one to many | An asset has many file renditions |
| Project → File | one to many | Files can also attach directly to a project |
| Asset → Preview | one to many | An asset has previews per language/revision |
| Asset → Translation | one to many | An asset has an OV plus localized translations |
The shape to remember: one project, many assets; one asset, many files — and each file is a specific localized or encoded version of its asset.
This page describes the concepts.