Oh Those Messy Sources!

Hi everyone!

Our souces are, in a word, messy! Ticketing struggles to find them. I'm pushing to standardize with formal naming conventions.  I've yet to find one that works across all departments.

We frequently have 12+ promo codes running simultaneously for a single production (across many) and track with fine detail between subs and single tickets.

Has anyone come up with a spectacular format you would be willing to share? Perhaps there's documentation I've missed?

I'm considering a seperate Excel document though it seems counterintuitive!

Many thanks for sharing!

Michelle

 

 

 

 

 

Parents
  • Although I never got time to finish it I had started working on a Custom Screen in Perfroamnce Information to pull through all the information for that perormance that Box Office need on a single screen.

    This was to include offers and promo codes - sql for that is here

    select
           appeal_name=a.description,
           s.source_name,
           o.source_no,
           w.promo_code,
           o.terms,
           price_type=pt.description,
           o.start_dt,
           o.end_dt

    from t_mos_offers o (NOLOCK)
    join t_perf p (NOLOCK) on o.perf_no=p.perf_no
    join tr_price_type pt (NOLOCK) on o.price_type=pt.id
    join tr_mos m (NOLOCK) on o.mos=m.id
    left join tr_web_source_no w (NOLOCK) on o.source_no=w.source_no
    join tx_appeal_media_type s (NOLOCK) on o.source_no=s.source_no
    join t_appeal a (NOLOCK) on s.appeal_no=a.appeal_no
    where o.perf_no=@perf_no
    order by o.start_dt desc, o.end_dt

    This never happened only because I got caught up in the web project and didn;t have time. 

    The alternative that was used was that we got Confluence and Jira from Atlassian (free for non-profits) and used Confluence as an Intranet for Box Office and Jira as a way of processing the requests for new offers.

    Mark

Reply
  • Although I never got time to finish it I had started working on a Custom Screen in Perfroamnce Information to pull through all the information for that perormance that Box Office need on a single screen.

    This was to include offers and promo codes - sql for that is here

    select
           appeal_name=a.description,
           s.source_name,
           o.source_no,
           w.promo_code,
           o.terms,
           price_type=pt.description,
           o.start_dt,
           o.end_dt

    from t_mos_offers o (NOLOCK)
    join t_perf p (NOLOCK) on o.perf_no=p.perf_no
    join tr_price_type pt (NOLOCK) on o.price_type=pt.id
    join tr_mos m (NOLOCK) on o.mos=m.id
    left join tr_web_source_no w (NOLOCK) on o.source_no=w.source_no
    join tx_appeal_media_type s (NOLOCK) on o.source_no=s.source_no
    join t_appeal a (NOLOCK) on s.appeal_no=a.appeal_no
    where o.perf_no=@perf_no
    order by o.start_dt desc, o.end_dt

    This never happened only because I got caught up in the web project and didn;t have time. 

    The alternative that was used was that we got Confluence and Jira from Atlassian (free for non-profits) and used Confluence as an Intranet for Box Office and Jira as a way of processing the requests for new offers.

    Mark

Children
No Data