Identifying (and suppressing) Artists in Tess

Kim,

We had only just begun the process of identifying current and former dancers in our database at Tulsa Ballet before I left; our process was going to be to assign either an Attribute or Constituent for "Tulsa Ballet Dancer" so that these people could be pulled into Lists via those criteria. From there, we would be able to suppress them from Extractions or otherwise identify them so that they wouldn't be solicited in Development mailings.

Thank you,

Brian

Hi Kim,

We use constituencies for this. We have Musician, Former Musician, as well as Guest Artist, and our School of Music faculty and staff. Having the option to use the date can show the transition from current to former, and since it pops up in our header customer service staff can easily tell that the musician should get comp tickets or a discount. We also keep track of staff and former staff like this.

Let me know if you have questions.

Ann

Hi, Kim:

We use a bunch of attributes to identify singers who are in our productions but not chorus members. "Artist in Opera Season" is one such keyword, and "2018 Season" is its key value for our current season. This is added to all singers, directors, choreographers, fight directors, etc., associated with our mainstage productions. We also identify singers by voice (Soprano, Mezzo-Soprano, Tenor, etc.), FGO debut year and role, home state/country ("From" data for programs), and type (Young Artist, Stage Director, Principal, etc.)  I have a scheduled procedure that looks for these attributes and adds a constituency of "Artist" (if it doesn't already exist in the account).

We haven't been too good about tying chorus members to our organization in Tessitura data, but my preferred method of doing this would be to create an affiliation to our Chorus account, with beginning and end dates. That is how we handle members of our Young Artist program, who are here for a season or two. They get a scheduled-procedure-generated constituency of "YA" when the affiliation is created, and that constituency is deleted, and they get a constituency of "YAF," when the affiliation is inactivated.

I add attributes when I add singers/directors/designers to a production or performance in the Ticketing Setup module.

Lucie
Florida Grand Opera

We track actors (constituency = ACT), creative team folks (CRE), teaching artists (TAS), etc., etc., by the above constituencies, all of which are activated/inactivated by the presence/absence of affiliations (of analogous types), with the Guthrie, and (particularly for ACTs and CREs) an association with a current or future production*.

When either the affiliation end-dates, or there is no current/future production associated with that person, the const inactivates and access to comps (via Box Office or web) goes away. There are a lot of moving parts, but this is generally working well for us.

(* This "association" is tracked in a custom tab created in 2009-2010 which stores these relationships for all of Guthrie history, >=1963.)