Production Tracking with Kitsu
Kitsu Components
Department
The departments used for the Heirloom project are listed below :
Warning
This section has been redacted.
Tasks Types
The task types used for the Heirloom project are listed below :
Warning
This section has been redacted.
Tasks Status
The task statuses used for the Heirloom project are listed below :
| Task Status | Status Code | Description |
|---|---|---|
| Input | INPUT | Set during Ingestion once animatics is uploaded to animatic2d column |
| Yet to Start | YTS | Set by Kitsu Automation once previous dependencies are published |
| Work in Progress | WIP | Set by Pipeline Manager Tool once artist opens the task file for first time |
| Waiting for Approval | WFA | Informs the supervisor that task is ready for review |
| Supervisor Retake | RTK_SUP | Supervisor has given feedback to artist |
| Supervisor Approved | OK_SUP | Task file is approved by supervisor, ready to send to director for review |
| Director Retake | RTK_DIR | Director has given feedback to artist |
| Director Approved | OK_DIR | Director has approved the shot |
| Approved | APP | Task file is approved, ready for publishing |
| Published | PUB | Task file is published and uploaded to server |
| On Hold | HOLD | Task is put on hold |
| Canceled | CAN | Task is canceled |
NOTE :
1 . During ingestion, animatics for each episode is uploaded to Kitsu and task status for animatic2d is set to INPUT
2 . In Heirloom project, the status for particular tasks are dynamically set to YTS
using Kitsu Automation. Check the Input/Output linking document for more details.
Tip
Click here to know more about how we integrate Kitsu API with Python.
Links
Explore the following sections to learn more: