• Replies 3 replies
  • Subscribers 338 subscribers
  • Views 82 views
  • Users 0 members are here
Related

QAS Batch and Cleaning T_ADDRESS

Matthew Hodge
$organization

Hi,

I'd be keen to hear from anybody who uses QAS Batch to clean their data. It's pretty straightforward for data we're exporting in, but how do people use it to clean up their data already in Tessitura. What are the exact steps you use?

Do you clean up the address table in segments? Do you export it as a file and then re-import it? Given that the data is changing in the address table is changing all the time, I just wanted to make sure that I run it as carefully as possible.

  • $organization

    Hi Matthew.

     

    We are going through a process of putting all our existing data through QAS, using an ODBC connection.

     

    Unfortunately, there isn’t a straight forward way to do this.

     

    Our site has over 700,000 records so we are doing it in batches of 10,000 records.

     

    We have put very specific rules over how we are identifying a ‘valid’ address, so some of it is manual.

     

    I can send you a document that we’ve been following to get this done.  We use it, also, to push our weekly feeds from other parties, through the QAS process.

     

    Hope this helps!

     

    Anna Duric
    System Application Administrator, Ticketing & CRM
    the Arts Centre

    T + 61 3 9281 8464
    F + 61 3 9281 8282
    M   0419 928 184
    E   anna-maria.duric@theartscentre.com.au
    W  http://www.theartscentre.com.au

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matthew Hodge
    Sent: Thursday, 19 May 2011 12:07
    To: Anna-Maria Duric
    Subject: [Tessitura Technical Forum] QAS Batch and Cleaning T_ADDRESS

     

    Hi,

    I'd be keen to hear from anybody who uses QAS Batch to clean their data. It's pretty straightforward for data we're exporting in, but how do people use it to clean up their data already in Tessitura. What are the exact steps you use?

    Do you clean up the address table in segments? Do you export it as a file and then re-import it? Given that the data is changing in the address table is changing all the time, I just wanted to make sure that I run it as carefully as possible.




    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!

     
    Please consider the environment before printing this e-mail.

    ___________________________________________________
     
    The information in this electronic mail is privileged
    and confidential, intended only for use of the individual
    or entity named.  If you are not the intended recipient,
    any dissemination, copying or use of the information is
    strictly prohibited.  If you have received this transmission
    in error please delete it immediately from your system
    and inform us by email on     info@theartscentre.com.au
    ____________________________________________________
  • $organization

    Hi Matthew,

    We use QAS Batch to clean Tessitura address data on a weekly basis.

    The QAS Batch tool did not have enough flexibility for configuration to meet our address data entry rules, or to allow us to select only certain address record AND initial testing indicated that querying the t_address table directly was detrimental to database performance, so I designed QAS Export and Import stored procedures.

    The Export is pretty simple, it excludes certain addresses based on our business rules, addresses that have already been cleaned by QAS, junk addresses, vanity addresses etc.  It also records a datetime stamp for use later in the Import.  We control which addresses are included in the Export with parameters for List, Addresses updated from/to, Inactive and Address Type.  We save the output as a text file.

    We then clean the addresses in QAS Batch, and commit changes back to the text file.

    The QAS Import stored procedure then applies formatting that fixes some QAS inconsistencies, and does error checking, the main aspect being addresses that have been updated in the database since Export (referencing the datetime stamp), before updating the cleaned addresses in the database.

    If you are interested I would be happy to share our QAS Export and Import procedures.  I have configured the Export so it can be run from the client.  At this stage the Import is run in a SQL query only.

    Cheers

    Kim

     

     

  • $organization in reply to Kim Lee

    Hi Matthew

    We recently got QAS Batch and have done a couple of tests to export existing records out of Tessitura, run them through QAS Batch and import the data. We have been using the NCOA Utility to be the link between Tessitura and QAS. Weve only been testing but it does seem to be working very well.

    Let me know if you need more info.

     

    Mark