Tracking Naming Opportunities using Program Name?

Hi,

One of our consortium organizations has a Name A Seat campaign under way, and is looking for the best (preferably non-custom) way to track this in Tessitura.

It's not unusual for a donor to purchase multiple seat naming opportunities (in honor of several other people). We had tried using the Program Name to track this, with a Program Type of Name A Seat, but you can't have duplicate rows of the same Program Type. 

Another option we looked at was using Attributes, which could then be pulled via a list/output set - but the Attribute Value has a 30-character limit, which is way too short.

How have others handled this? As I said, we would prefer not to get too custom, since we have limited tech resources.

Thanks!

Stacey Voigt

Database Manager
Santa Barbara Center for the Performing Arts
(805)899-3000 x128
svoigt@granadasb.org

Parents
  • Hi Stacey,

     

    You might be able to configure CSIs to do this.  There’s nothing that says you can’t have multiple CSIs of the same type-  the name could go in the notes section of the csi.  CSIs are easy to report on with the standard reports.  And if you’re etching names on seats, you could close the CSI once the job was done, helping you keep tabs on what’s where in the process. 

     

    Cheers,

    Kathleen

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Stacey Voigt
    Sent: Friday, July 17, 2015 1:25 PM
    To: Kathleen Smith
    Subject: [Tessitura Development Forum] Tracking Naming Opportunities using Program Name?

     

    Hi,

    One of our consortium organizations has a Name A Seat campaign under way, and is looking for the best (preferably non-custom) way to track this in Tessitura.

    It's not unusual for a donor to purchase multiple seat naming opportunities (in honor of several other people). We had tried using the Program Name to track this, with a Program Type of Name A Seat, but you can't have duplicate rows of the same Program Type. 

    Another option we looked at was using Attributes, which could then be pulled via a list/output set - but the Attribute Value has a 30-character limit, which is way too short.

    How have others handled this? As I said, we would prefer not to get too custom, since we have limited tech resources.

    Thanks!

    Stacey Voigt

    Database Manager
    Santa Barbara Center for the Performing Arts
    (805)899-3000 x128
    svoigt@granadasb.org




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!

Reply
  • Hi Stacey,

     

    You might be able to configure CSIs to do this.  There’s nothing that says you can’t have multiple CSIs of the same type-  the name could go in the notes section of the csi.  CSIs are easy to report on with the standard reports.  And if you’re etching names on seats, you could close the CSI once the job was done, helping you keep tabs on what’s where in the process. 

     

    Cheers,

    Kathleen

     

    From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Stacey Voigt
    Sent: Friday, July 17, 2015 1:25 PM
    To: Kathleen Smith
    Subject: [Tessitura Development Forum] Tracking Naming Opportunities using Program Name?

     

    Hi,

    One of our consortium organizations has a Name A Seat campaign under way, and is looking for the best (preferably non-custom) way to track this in Tessitura.

    It's not unusual for a donor to purchase multiple seat naming opportunities (in honor of several other people). We had tried using the Program Name to track this, with a Program Type of Name A Seat, but you can't have duplicate rows of the same Program Type. 

    Another option we looked at was using Attributes, which could then be pulled via a list/output set - but the Attribute Value has a 30-character limit, which is way too short.

    How have others handled this? As I said, we would prefer not to get too custom, since we have limited tech resources.

    Thanks!

    Stacey Voigt

    Database Manager
    Santa Barbara Center for the Performing Arts
    (805)899-3000 x128
    svoigt@granadasb.org




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!

Children
No Data