We are still validating which workflow will make more sense for our VFX pipeline, since it requires a CSV-like list to create the project hierarchy in our project management tool. Because of that I was considering sending this file to CSV ingest as well to optimise, but indeed that might be more trouble than its worth it, so now we are leaning towards rendering individual clips as you suggested.
The link you provided (CSV ingest) allows to ingest files, but I think it cannot be used to only add folders (or tasks) to the logical project hierarchy (as you already said).
There is also that PR which will allow to create the starting logical hierarchy (EDIT : I was wrong, in fact it creates folders on disk) :
.
But is there an already available way to add a list of assets (and ideally tasks) to the project hierarchy, without having to provide a file for each folder / task ?
It would be useful when producers say “ok, now we know the list of assets we will need to create for client, add their names to Ayon’s hierarchy”.
From on top of my head, I can’t remember if there’s a publish process that can be used for creating folders and tasks solely as most of them are associated with editorial publishing.
However, Can a simple python code do this trick for you?
Here’s a snippet that creates project hierarchy, Maybe one can extend it on their end to parse a CSV
As far as I know that PR creates additional work directires that maybe managed outside of AYON. e.g. a storage folder for any random files and artists may access such locations via environment variables.
You are right about that PR, I have edited my message above.
And thanks for the snippet that creates project hierarchy.
I wasn’t searching for a “publish” process to do it.
I somewhat recall someone speaking about a way to do this using the web GUI and some settings to create templates.
Found it, that’s scheduled for a future enhancement of the Overview :
Some of the addons mentioned on the pricing page are in alpha phase (available on demand for subscribers).
Batch Publisher (Batch Ingest Tools): It allows multiple products publishing and it tries to guess final product type either by configured mapping for regular expression match in file path or extenstion.
Didn’t test it myself yet but I don’t think it requires any csv files.