Creating an Asset or Elements Project/Database in shotgun and accessing through other projects

I built an element library using Shotgun back in 2013 for a collection of practical elements (a few thousand.) Been working fine for six years.

I made Version entities for the element proxy.

Artists enjoy searching use the nice animated thumbnails. They chose to put them in about a dozen categories (aka Sequence entity). They can make tags to help find them too.

Drag-n-drop works nicely into Nuke.

I made a submission dialog in RV to allow creating new elements, along with metadata (eg. standardized tags.)

Proxies are all built on the farm and uploaded.

We have never seen any need to make anything fancier, eg.:

  • to overcome the cross-Project barrier (never has been an issue, and frankly, it’s better to be isolated!)
  • asset heredity (the path to the EXRs are sufficient)
  • update notifications
  • revisions (just make a new element, just change status on the ugly one in case it was used)
  • Tasks (planned, but never implemented.)
9 Likes