Thanks @mustafa_jafar for the pointers. I have come across a lot of these already, and yes pyblish would be the best way, but I guess I’m a bit stuck on how to correctly attach a file to the instance, though I see some code for that here but can’t tell if it’s up to date with latest changes as the thread still talks about OpenPype libraries:
And I have looked at the batch ingestion tool but as Fabia said it was built our their studios naming conventions, we have some specific needs for name tag/attributes in our product types for most publishes, plate ids, lods, layer ids, etc for plate, models, renders respectively in those examples, and so we’d like to add attributes at the studio level to products and then populate them in these sorts of batch ingest tools. (I’d also like to extend the publishing UIs at a later point to be able to do the same with additional dropdowns outside of Variant, but that’s for another time.)
I think as well I’m not sure on the best way to test this properly, given it needs a host, I was running snippets in the tray admin console but I understand that’s not in a host environment, so perhaps I have code that’s working and it just needs to be made into an addon and tested, I’d hoped there was a pre package method of testing code though. I can see there’s terminals, but I get a windows command prompt, and this is DCC agnostic so didn’t want to run it through a DCC to test.