Thank you for contacting me. Please note that I live in the GMT+3 time zone - responses might be delayed by this.
This topic has 2 replies, 2 voices, and was last updated 21 hours, 59 minutes ago by 
.
-
Posts
-
-
Hi and thanks in advance for your timely support. I recently switched from having lots of genre-based rules truing to fetch concerts worldwide to 6 regional rules. This is working smoothly in terms of pulling concerts from different countries with less API calls, but we are forced to assign genres (and post in the relevant category) with a script which is not 100% reliable.
Attached are a screenshot of 1 of the rules and the snippet function that currently tries to detect the genre.
Would you have a different configuration to suggest?
Thanks again.
Leopoldo -
Hello,
Thanks for the detailed explanation.
I think the current setup makes sense, but the weak point is Ticketmaster’s metadata consistency, not really your script. Different countries and organizers classify events very differently, so even a solid fallback matcher will sometimes get it wrong.
That said, since Tmomatic already exposes Ticketmaster’s own classification fields like %%item_classification_genre%% and %%item_classification_subgenre%%, I’d probably simplify the setup and use those directly instead of relying on post-import detection logic. Those values should generally be more reliable.
Your current code is actually very good as a normalization fallback, but using the native classification data directly should reduce mismatches.
Let me know if this helped.
Regards,
CodeRevolution -
-
You must be logged in to reply to this topic.