Hope this reply isn’t too dark. Apologies. It’s just the nature of our struggle
I have not been able to provide an effective notification system using Shotgun:
- we don’t use desktop, so it’s “keep your browser open” (which is too much to do)
- not everyone opens up Shotgun, some, never
- all Inboxes are at 99+
- email is the ‘single source of truth’
- nobody has taken the steps to ensure that desktop notifications are enabled
- I have to physically go to each desk to show them
- it stops after a while, and rinse-repeat, and hence, it’s unreliable
Another problem is the unsatisfied need to have the notifications triggered by systems outside the realm of Shotgun, or, that the notifications are controlled by logic outside – so – in effect – the notifications need to be cross-system.
Specific example: the batch queuing system (farm) is not connected to Shotgun currently, and is an important contributor to events. Redis does the pub-sub’s for the farm.
The point I’m making is that unless all your production systems are completely tied to Shotgun you can’t get effective, real time notifications – at least you can’t convince crews that it’s a Killer App – the only thing that makes productions willing to change to a new way-of-doing-things.
Notifications have to be managed by a cross-systems aggregator, eg. redis, or rabbitmq… or hooks… or…? It’s all too alpha at this stage.
I’m looking into Shotgun-trigger nodes for n8n – meaning, Shotgun will end up being slaved to some other “event management.”
Also tried exercising Mattermost (in liu of Slack) but I’m not convinced anybody wants yet-another-communication-collaboration-system. After all…
I hate email… it’s Shotgun Kryptonite.
This all ties back to… One needs a Production Single Source of Truth
Looking forward to more wisdom from others on this topic! Happy Friday.