When we designed our on-set database app, the biggest feature we looked toward was ShotGrid integration. We never once got Setellite’s to work during our time with that software, so doing it right mattered to us, and making it straightforward for the average wrangler, whose ShotGrid experience is usually minimal or non-existent.
Getting data to vendors at the end of a show was often a nightmare. Our wranglers would lack the knowledge or the time to get it over in an acceptable format, and different vendors have different expectations. Sending over a cleaned up CSV was always the norm.
Sending it straight to ShotGrid instead, with the ability to link records to a shot, means that when plate delivery happens the vendor has everything they need in one place. No cross referencing, no rebuilding data in ShotGrid.
Setup is simple. You enable a custom entity of your choice and give it a name (we like Onset Data), set up a basic API admin script, and you’re ready for ingest. Less than a minute on the ShotGrid side.
Full showcase and walkthrough on YouTube: https://www.youtube.com/watch?v=JlWrUgugjbI
Promotional showcase cut: https://www.youtube.com/shorts/9-6aJ0JE_ws
For the ShotGrid people receiving this data, I’d like to know whether this workflow actually suits you and whether you’d improve anything about it.