Demographics Database Enhancement?

Dearest Friends--

We're wanting to explore the world of enhancing our database to feature various points of demographic information that we don't presently track--like ethnicity for example--and I'm wondering if anyone how folks might have achieved more specialized or specific demographics tracking in Tessitura. Are you utilizing an outside company? Internal teams of coders? Creatively using features already in the box?

Thank you for your thoughts on this!

Brian Jones

Parents
  • Former Member
    Former Member $organization

    My experience has been that organizations typically use Attributes to handle information like this. Attributes give you a lot of features to segment the patrons after the data is entered in the system (i.e. through list criteria).  

    If the organization is purchasing this kind of information from an outside source, they would usually come to me (the DBA) to have the entire data set imported into the appropriate attributes en masse.  This is fairly straightforward assuming that the Tessitura customer number is attached to the data returned from the outside source.

    The other channel I've seen the data collected is usually from students enrolled in a school with the organization.  The information is fille dout on the enrollment form and then the users manually enter the attribute values as part of the enrollment process in Tessitura.

    Unless you have some very customized usages in mind for this data, I think Attributes are the best place to store them in Tessitura.

Reply
  • Former Member
    Former Member $organization

    My experience has been that organizations typically use Attributes to handle information like this. Attributes give you a lot of features to segment the patrons after the data is entered in the system (i.e. through list criteria).  

    If the organization is purchasing this kind of information from an outside source, they would usually come to me (the DBA) to have the entire data set imported into the appropriate attributes en masse.  This is fairly straightforward assuming that the Tessitura customer number is attached to the data returned from the outside source.

    The other channel I've seen the data collected is usually from students enrolled in a school with the organization.  The information is fille dout on the enrollment form and then the users manually enter the attribute values as part of the enrollment process in Tessitura.

    Unless you have some very customized usages in mind for this data, I think Attributes are the best place to store them in Tessitura.

Children
No Data