Importing Archtics Information into Impresario

Hey All,

I also posted this in Ticketing but think this MAY be a better place for it:

I am trying to import our existing Archtics information (that has already been collected into a central repository, so the data is not coming directly from Archtics) into Impresario via a series of scripts. The place that's giving me the most issue is getting our unconventional Event structure (each Event is a single Event, there are no strings of performances of a specific work that happen on a regular occasion) first into T_INVENTORY and then into the rest of the tables T_TITLE, T_PRODUCTION, etc.

We have worked out a way to fit the two disparate sources but the code that I have created is not working the way I want it to. It doesn't loop properly, and doesn't increment the inv_no the way that it needs to (even using the AP_GET_NEXTID_FUNCTION procedure)

Once the above is successful, I can pull over the ticket and package information (which works, incidentally, it's the performance information that’s the issue).

One thing to note, we don't sell tickets through Tessitura, we use it for Development, and are doing this to be able to attach the Archtics ticketing information to the appropriate donors.

Has anyone out there in Tessyland been through this process or is in the middle of it? Any help would be GREATLY appreciated!

Thanks,

Jamy

Parents
  • Perhaps if you include some of your code we could help you with the looping problem.

    So even though you’re not selling tickets in tessitura, you’re pulling in full orders for your legacy data? Are you planning on continuing to do this periodically to stay up-to-date? Might I ask how many years of legacy data you’ll be importing? We recently implemented Tessi and imported 10 years of historical ticket purchase data, but only used the ticket history table to do so, which doesn’t require the full production elements structure exist for each historical performance. Your project sounds much more ambitious.

    You mentioned ID increments — you don’t necessarily have to use AP_GET_NEXTID as long as you update the T_NEXT_ID table properly, but you’re right that it’s tricky in this case since all inventory element tables (T_TITLE/PRODUCTION/PROD_SEASON/PERF) share IDs with the T_INVENTORY table. 
    --
    Nick Reilingh
    Box Office Manager
    (845) 758-7948

    On Jul 1, 2014, at 5:06 PM, Jamy Sweet <bounce-jamysweet4309@tessituranetwork.com> wrote:

    Hey All,

    I also posted this in Ticketing but think this MAY be a better place for it:

    I am trying to import our existing Archtics information (that has already been collected into a central repository, so the data is not coming directly from Archtics) into Impresario via a series of scripts. The place that's giving me the most issue is getting our unconventional Event structure (each Event is a single Event, there are no strings of performances of a specific work that happen on a regular occasion) first into T_INVENTORY and then into the rest of the tables T_TITLE, T_PRODUCTION, etc.

    We have worked out a way to fit the two disparate sources but the code that I have created is not working the way I want it to. It doesn't loop properly, and doesn't increment the inv_no the way that it needs to (even using the AP_GET_NEXTID_FUNCTION procedure)

    Once the above is successful, I can pull over the ticket and package information (which works, incidentally, it's the performance information that’s the issue).

    One thing to note, we don't sell tickets through Tessitura, we use it for Development, and are doing this to be able to attach the Archtics ticketing information to the appropriate donors.

    Has anyone out there in Tessyland been through this process or is in the middle of it? Any help would be GREATLY appreciated!

    Thanks,

    Jamy




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • Perhaps if you include some of your code we could help you with the looping problem.

    So even though you’re not selling tickets in tessitura, you’re pulling in full orders for your legacy data? Are you planning on continuing to do this periodically to stay up-to-date? Might I ask how many years of legacy data you’ll be importing? We recently implemented Tessi and imported 10 years of historical ticket purchase data, but only used the ticket history table to do so, which doesn’t require the full production elements structure exist for each historical performance. Your project sounds much more ambitious.

    You mentioned ID increments — you don’t necessarily have to use AP_GET_NEXTID as long as you update the T_NEXT_ID table properly, but you’re right that it’s tricky in this case since all inventory element tables (T_TITLE/PRODUCTION/PROD_SEASON/PERF) share IDs with the T_INVENTORY table. 
    --
    Nick Reilingh
    Box Office Manager
    (845) 758-7948

    On Jul 1, 2014, at 5:06 PM, Jamy Sweet <bounce-jamysweet4309@tessituranetwork.com> wrote:

    Hey All,

    I also posted this in Ticketing but think this MAY be a better place for it:

    I am trying to import our existing Archtics information (that has already been collected into a central repository, so the data is not coming directly from Archtics) into Impresario via a series of scripts. The place that's giving me the most issue is getting our unconventional Event structure (each Event is a single Event, there are no strings of performances of a specific work that happen on a regular occasion) first into T_INVENTORY and then into the rest of the tables T_TITLE, T_PRODUCTION, etc.

    We have worked out a way to fit the two disparate sources but the code that I have created is not working the way I want it to. It doesn't loop properly, and doesn't increment the inv_no the way that it needs to (even using the AP_GET_NEXTID_FUNCTION procedure)

    Once the above is successful, I can pull over the ticket and package information (which works, incidentally, it's the performance information that’s the issue).

    One thing to note, we don't sell tickets through Tessitura, we use it for Development, and are doing this to be able to attach the Archtics ticketing information to the appropriate donors.

    Has anyone out there in Tessyland been through this process or is in the middle of it? Any help would be GREATLY appreciated!

    Thanks,

    Jamy




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
  • Hi Nick,

    First, thanks for your response, it is definitely the information we need to get this done. I will send you the scripts I have I been working with to your above email to see if you have any insight on my current path.

    You are correct regarding our pulling in full orders of legacy data. We will be pulling it periodically, via a nightly job, so that it is currently up-to-date as of the day before. We will be importing data back to 2008 (that’s when we first went online with the Archtics system) initially.

    As far as just importing the ticket purchase data the way you mention above, I had that already completed and working, but one of my colleagues decided they wanted to able to report on performance information as well (see that mention of the T-STATS implementation, below).

    We need this data pulled in for two purposes:

    1.       We want to be able to tie ticket purchases to our donors (we will do this via their Archtics ID from the T_KEYWORD table). This has a host of applications for us, one of which is the opportunity to know where a patron is located in one of our venues during an event  so that a Major Gift Officer can follow-up with them

    2.       We are going to be installing T-STATS and want to be able to report on performance and ticketing data


    So, are you saying that if I add some code to increment the value in the T_NEXT_ID table, then I don’t have to use AP_GET_NEXTID? I am using a temp table that then inserts into T_INVENTORY for each inventory type, once they have all been added. This will all make more sense hopefully once you see my code.

    Thank you again for your help Nick, I really appreciate!

    Jamy