As part of the requirements for submitting a delivery to Feature Animation at Netflix (FAN), each submission will need to include a standardized CSV manifest file that provides additional metadata about each file in the submission. This data is necessary to enable the automatic ingestion of these files into the Feature Animation at Netflix (FAN) pipeline.
We suggest that the filename for each CSV manifest uses the following naming convention:
-
<project code>_<partner code>_YYYYMMDD_##.csv
-
Example: abc_xyz_20211006_01.csv
- This is saying ‘This first package was sent on October 6, 2021 from XYZ (Partner Code) on the show ABC (Show Code)’
-
Example: abc_xyz_20211006_01.csv
Per File CSV Field Summary
Below is a list of fields that each partner studio needs to fill out for each file in the submission. Fields marked with an R are required.
| Field Name | Example | Description | Required / Optional |
| Filename | ABC_9400_0100_lgt_v010.%04d.exr | The name of the file in the package. | R |
| Relative Path | ./lighting_review |
The path to the file relative to the root directory of the package. |
R |
| Link | 9400_0100 | The name of the FAN ShotGrid (SG) entity (i.e. asset, shot, sequence, episode) that should be used when linking the file in SG. | O |
| Task | lgt | The task name of the FAN ShotGrid task entity that should be used when linking the file. | O |
| Submitting For | REVIEW |
The file submission intent. Following are the standardized set of values to use for this field: REF - for reference only, not officially in progress at the partner studio |
O |
| Description | Addressed all lighting notes | The submission note for the file. | O |
| Partner Version | v010 | The partner studio version number. | O |
| Partner Entity ID | 13380293 | The unique entity ID that is associated with the file from the partner studio’s asset management. | O |
| Partner Artist | Jane Doe | The name of the artist at the partner studio who created the iteration. | O |
| Name | abc12345 | A user-defined field that allows for further disambiguation among like-files. | O |
| Start Frame* | 1001 | The first frame of a frame sequence. Required when sending an image sequence. | O |
| End Frame* | 1050 | The last frame of a frame sequence. Required when sending an image sequence. | O |
| Frame Step* | 2 | The frame increments between start and end frame of the frame sequence. Required when sending an image sequence. | O |
|
Deliver To Editorial |
Yes |
Identify files to send directly to Editorial. Accepted values are:
Yes - send this file to Editorial
No - do not send this file to Editorial
|
O |
* We support the use of the following syntax when specifying a padded 4 digit frame number:
-
%04d
-
e.g. ABC_9400_0100_lgt_v010.%04d.exr
-
Using the example data from the table (Start Frame 1001, End Frame 1050, Frame Step 2) - this filename will expand out to the following filenames: ABC_9400_0100_lgt_v010.1001.exr, ABC_9400_0100_lgt_v010.1003.exr, ABC_9400_0100_lgt_v010.1005.exr...ect.
-
Delivering To Editorial
All files marked as ‘Deliver To Editorial’ within a package will be organized and sent directly to the Netflix Animation Studio Editorial team on the show. If a delivery is made to Editorial, then Editorial-specific notifications will be sent out in addition to the regular delivery notifications. Delivery to Editorial is additive to the regular package delivery pipeline, so files sent to Editorial will also still be available in the original package.
Once the delivery has completed, a user is able to see which files were sent to Editorial by viewing the contents of the ‘Deliver To Editorial’ folder in Content Hub under the top level folder for the submission in the Workspace Shares.
Figure A
Sample CSV and Folder Structure
Below is an example of a package with its corresponding CSV manifest. The example shows what the CSV manifest should look like when specifying a set of movies in a folder (./MOV), a sequence of EXR frames in another folder (./EXR), and a PDF at the root level of a single delivery package (abc_xyz_20211006_01).
Figure B
Figure C
CSV Validation
Once your CSV manifest has been submitted it will be validated to ensure that all files listed in CSV are present in the delivery folder, all files have corresponding rows in the CSV, and that your package only contains a single CSV at the root level.
Should your CSV fail any of the validation checks the following will happen:
| Validation | Action |
| Not all the files listed in the CSV are present in the delivery folder. | The delivery will continue and an email notification will be sent to both the package recipients and sender informing them that there are missing files. |
| Not all the files have corresponding rows in the CSV. | The delivery will continue and an email notification will be sent to both the package recipients and sender informing them that there is missing metadata. |
| Your package contains more than one CSV at the root level. | The delivery will fail and an email notification will be sent to the package sender informing them that only one CSV manifest can be specified per submission. |