Customization of TNEW regarding Registrations of children's camps and programs

Hi Michelle,

We do use TNEW for sign-ups to some of our educational events (typically lectures for grownups connected to our performances).  This is done without customization: just using Auxiliary Performances.  If you're just looking for simple inventory management and roster lists that's likely sufficient.  We have a more complicated  request in for scheduling attendance for school groups which can not be covered by Auxiliary Performances, but are still trying to work up a specification for that.

The one caution I have is that you'll want to be sensitive in how information gathered on minors is stored: they'll need to be flagged in some way so as to not be available to more internal users than necessary, and to be sure they are never accidentally swept up in marketing campaigns and the like.

--Gawain

I'm with Sara in wondering how others have managed with low resources

and with Gawain emphasizing the sensitive nature of minor's data. 

I have a background with a children's museum and brought a lot of awareness of the sensitivity of minor's data with me to Dallas Black Dance Theatre's Academy. Since I've been with DBDT, we scrupulously avoid creating separate accounts for minors due to so many rules that must be followed to segregate their information;  e.g. impossible to hide the general tab stuff in our consortium environment, and even a name in the system with our constituency could put a child at risk. The likelihood may be low, but the risk is high.  

We've made several stabs at getting custom screen(s), putting the minor's info on caretaker's account, to a consortium-agreed set of basic components with no success, either, This is not necessarily a failure of Tessitura, but more like a weakness when different orgs have different priorities.  Every org in our consortium that currently deals with minors has found their own work-around, so there's not a lot of demand for a consortium solution.  So my organization has, for now at least, settled with an outside vendor for class and workshop registrations. From there, we import caretaker basic info using an out of the box utility.  This is not ideal, but it's better than nothing, and it's definitely better the potential of a catastrophic leak of sensitive data through a box office or other non-specialized Tessitura user. 

I'm with Sara in wondering how others have managed with low resources

and with Gawain emphasizing the sensitive nature of minor's data. 

I have a background with a children's museum and brought a lot of awareness of the sensitivity of minor's data with me to Dallas Black Dance Theatre's Academy. Since I've been with DBDT, we scrupulously avoid creating separate accounts for minors due to so many rules that must be followed to segregate their information;  e.g. impossible to hide the general tab stuff in our consortium environment, and even a name in the system with our constituency could put a child at risk. The likelihood may be low, but the risk is high.  

We've made several stabs at getting custom screen(s), putting the minor's info on caretaker's account, to a consortium-agreed set of basic components with no success, either, This is not necessarily a failure of Tessitura, but more like a weakness when different orgs have different priorities.  Every org in our consortium that currently deals with minors has found their own work-around, so there's not a lot of demand for a consortium solution.  So my organization has, for now at least, settled with an outside vendor for class and workshop registrations. From there, we import caretaker basic info using an out of the box utility.  This is not ideal, but it's better than nothing, and it's definitely better the potential of a catastrophic leak of sensitive data through a box office or other non-specialized Tessitura user.