Publish incoming links

[tokejepsen]

Goal

To populate the incoming_links property on an asset version.

Motivation

Populating incoming_links property of an asset version, would result in a dependency graph. This means users can start traversing the dependency graph and make informed decisions.
Practical features could include; status updates, clean up, sending assets with all their dependencies. It has to be said that I'm not suggesting to implement these features, because they are pipeline specific, only publishing more data about an asset version for better decision making.

This could be implemented in individual pipelines, but I would say that it is generic enough to be implemented into this repository. Also there are some necessary changes to be made to this repository to be able to publish the incoming_links property.

Solution

Ftrack API part of the solution can be found here; http://ftrack-python-api.rtd.ftrack.com/en/stable/example/entity_links.html.

The idea is to populate all asset versions that gets published, with dependency links to all assets in the scene.
For this repository the solution would entail a collector and changes to the integrator.

The collector would gather all assets in a scene. This has to be application specific, because traversing the scene requires the applications api.

The changes to the integrator are to add the property. Initial tests revealed that it isn't just an easy populating of the property, but query method needs modifying to allow for lists.

[mkolar]

I like this. We have long term plans to start using ftrack dependencies, but haven't gotten around to it yet.