Ken,
Thanks for the document – this is just the kind of thing we’re working to develop here.
As consortia go we are relatively de-centralized, and that’s reflected in the size of our team, which is why we’re trying to create a process that distributes the information and communications (and tasks!) This gives me some ideas though – good food for thought.
(I also always appreciate seeing other folks’ formats for user guides and procedures. There is so much information to convey and it’s nice to see how you’ve presented it)
Stacey
From: Tessitura Customer Service Forum [mailto:forums-cust.serv@tessituranetwork.com] On Behalf Of Ken McSwain Sent: Wednesday, March 04, 2015 2:34 PM To: Stacey Voigt Subject: Re: [Tessitura Customer Service Forum] Setting up CSIs to share between organizations (consortium)
Hi Stace
In the Sydney (UCSS) consortium, we have a process set up whereby when someone is alerted to a death or divorce, they create a CSI of a particular type, as well as marking the record and dealing with anything that org needs to do.
The consortium Application Support team (who have access to everybody's data) run a daily report to sweep up any new csi's of that type. Then they check the constituent, and add actions for any other consortium org that has touch on the constituent.. (There is a nominated human at each org who gets the action, and is responsible for tidying up the record). Once all those actions are marked as complete, the consortium support team does any final tidy-up needed ( eg inactivating deceased records or defunct households)
We've just been reviewing our process for this. I've put a copy of our new user guide in my files here, for your amusement.
Ken
From: Stacey Voigt <bounce-staceyvoigt1752@tessituranetwork.com> Sent: 3/4/2015 3:10:59 PM
Hello,
We are struggling a bit with getting our CSIs set up in a way that makes them work as a means of communication between our consortium organizations.
For example, when a user at organization A updates a constituent record (as in case of a death or divorce) we want key users at organizations B and C to become aware of this.
I've seen mention that other consortia are doing this and wonder if anyone would be willing to share the details?
Thank you!
Stacey Voigt Database Manager Santa Barbara Center for the Performing Arts (805)899-3000 x128 svoigt@granadasb.org
-- View this message online at http://www.tessituranetwork.com/Community/forums/p/13178/40982.aspx#40982 or reply to this message -- This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Customer Service Forum. You may reply to this message to post to the Customer Service forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Hi Stacey,
We set up CSIs for name/address changes to any constituent that has shared ownership. We don't email the owner organization. I understand that we used have a more hands off if it isn't your patron, but we have evolved to be more customer accomodating. Approval of the owner organzation is required for merges or VIPs. I also have a draft document waiting for consortium approval and would be happy to share as I borrowed a lot of it from Anna Duric at the Sydney Opera House.
Susan
Hi Susan,
Thanks for the input. I think this is the direction we're tending to go as well. If you're still up for sharing your draft document I would love to take a look!
Stacey Voigt Consortium Services Manager Santa Barbara Center for the Performing Arts svoigt@granadasb.org
Hey Stacey,
I will email to you.