Our studio uses shotgun for external assetsmanagement and feedback across 4 mobile titles. We do monthly KPIs on vendor performance based on version interations on each task. This data is manually copied over to an Excel doc, which we use to have monthly talks on training or improvements. Is there a way to export these notes on versions and keep the tasks the versions are related to? Maybe in a .csv format?
Hey @Andrew_Knight—welcome to the forum!
I split this out to its own topic for @jonjones to reply and so it’s not stuck in that big thread.
Thank you, @johnny.duguid!
@Andrew_Knight, what information precisely are you wanting to export from Shotgun? There are a few ways to approach this. The first and simplest would be to set up a custom page showing off the fields you want to export, then clicking on the “More” button and then “Export CSV.” You can also do that via a URL:
The second option would be using a Production Insights widget to graph and format the Versions data you want, and exporting to CSV from that widget. More info here: https://www.shotgunsoftware.com/blog/shotgun-76-introduces-production-insights/
There’s also information in the Event Log that could be exported and pivoted off of to generate information, but it depends on what you’re looking for. Happy to follow up!
Great thanks for the information, I’ll look into these suggestions. We are using keywords in notes attached to versions for tracking on iterations.
I wrote a short linked in article on how the proccess I use. Looking for suggestions on an easier automated proccess
I read your article, and I’m impressed! Using keywords as the basis of that is really clever. Did you start from a master list you worked on with your art leads, or did that evolve over time?
If it’s keyword-based, you could create a custom page in Shotgun populated with Versions, using a page filter searching for keywords (and possibly date ranges? different vendors? different projects?) to populate the page with, including whatever other custom fields you’re using to provide context. From there, you could either manually export, or set up a periodic automated export into a spreadsheet you can work from. Using that exported spreadsheet as the source data for another sheet of calculations, graphs, and pivot tables could be one way to go.
Of course, I’m happy to talk about this in more detail offline if you’d like to go into more specifics.
BTW, are you attending SIGGRAPH Asia, by any chance? I’ll be there in Brisbane next week Mon-Weds.
Yeah that would be great! I loved the dashboards you had setup that you showed in the presentation. I haven’t dealt too much with custom dashboards, so any help on that when you have a moment would be great.
The keyword list evolved after taking with the leads about common themes that come up in past feedback, as well as the sign-off gates of specific assets. It evolves as certain keywords are addressed with more tutorials or documentation, where it doesn’t seem significant enough of an issue to track. Sometimes new keywords are added as a new procedures or feature is introduced to the game. It really helps narrow down where a vendor is struggling when you deal with thousands of effort days of work across multiple studios.
Unfortunately i wont be at SIGGRAPH due to workload at the studio. I usually really only have enough time to attend XDS in Vancouver.
Thank you very much! I’ve just reached out to you on LinkedIn – let’s connect there and set up a time to talk.
Clever! That’s a smart way of approaching the problem, especially at that scale. I especially appreciated the categorization and graphing of feedback types and trends over time – inspiring food for thought!