I want to include the ticketing keyword in t_keyword and I'm getting stuck on the parameters. Basically we want to be able to select all customers who bought a ticket to a performance with a particular keyword. Can anyone help?
You can write your weighting procedure to do whatever you want it to do, but the tricky part would be linking credits to interests. Normally an interest is also a keyword, so you set it up once, add the keyword to performances, and then you have an easy link between performances and interests. To use credits, you will have to set up the credits up twice, once as credits and once as interests. To link the credits to the interests you would have to either add the interest keywords to the performances, or handle the matching in the weighting code. Handling the matching in the code might be a bit cumbersome, though. I think you would have to get much more specific, saying credit a corresponds to keyword a. While if you are using keywords, you could be more general and say find the keywords on the performances a constituent bought and increment the weight on those interests. You don’t have to be specific because the keywords and interests are the same thing.
To sum up, there is extra work involved for someone. Either extra performance setup to apply the credit keywords to the performances or extra coding work to map the keywords to interests. The extra setup work is probably simpler and more dynamic (i.e. you won’t need new coding whenever you add new artists), so that’s what I’d go with.
Hope that makes sense and helps.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Thanks that is helpful. We now realize however that the entire list of Interests appears in patrons' accounts whether or not they are selected or weighted. Given that there are 100s of artists, conductors and composers associated with performances across our seasons, that would be an unwieldy number of Interests to weed through for patrons or frontline employees. I suppose we would need to go with more general Interests to preclude this - or figure out a way to only display selected Interests that are weighted.