Searching for a large number of Constituents at once?

In response to your question looking for NOVEL solutions.

I’ve not had this issue to deal with. But given the challenge I might try a Knime (www.knime.org) workflow. There are a bunch of fuzzy matching options built into this Open Source solution. You should be able to read from all the data sources in question and write back to the database directly, or build a table in the format that can be used by the Import utility. Within Knime there are tools for creating web interfaces and active learning input. That said this on the extreme novel end of the spectrum and would not be a quick learn. Let me know if you pursue this direction. I would be interested in helping a bit.

--Tom Brown
Business Analytics mgr

Brooklyn Academy of Music BAM
Peter J. Sharp Building
30 Lafayette Ave
Brooklyn, NY 11217

www.BAM.org

Tbrown@bam.org
718-724-8135



On Mon, Jul 4, 2016 at 9:31 AM, Nick Reilingh wrote:

I'm right now researching and developing a pretty heavyweight solution to this problem and am very curious what kinds of custom solutions people have come up with already.

My approach thus far has been problematic, but better than the alternative of manually searching each constituent. In our environment, we use a Tessitura attribute to match up records from the foreign database. The procedure I have now involves loading the foreign dataset into a local table in tessitura, then running a series of scripts to identify matches that already exist on the attribute value, or matches that DID exist but have been broken by merges in one or both systems (aargh), and finally potential matches on email, address/name, etc. What I don't yet have is an interface to easily approve or refuse those potential matches—basically what I am looking to develop.

I think you can do a lot of this with the constituent import utility as you suggest, but I want more control over finding duplicates (searching multiple addresses on each side of the import, for example).

Anyone else have a novel approach to dealing with the problem of overlap/matchup between a foreign database and Tessi?
From: Rog Hildreth
Sent: 7/4/2016 5:50:21 AM

So I need to see essentially take a smaller database from another department and see which of them are on our Tessitura. Any tips on how to do this without having to search one-by-one? My best idea so far is to make an import file and run Constituent Import in "Review Mode", then look for duplicates. Has anyone got a better way? We're not necessarily going to import those we don't have - the other department just want to see the crossover.

Cheers,
Rog



This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!

In response to your question looking for NOVEL solutions.

I’ve not had this issue to deal with. But given the challenge I might try a Knime (www.knime.org) workflow. There are a bunch of fuzzy matching options built into this Open Source solution. You should be able to read from all the data sources in question and write back to the database directly, or build a table in the format that can be used by the Import utility. Within Knime there are tools for creating web interfaces and active learning input. That said this on the extreme novel end of the spectrum and would not be a quick learn. Let me know if you pursue this direction. I would be interested in helping a bit.

--Tom Brown
Business Analytics mgr

Brooklyn Academy of Music BAM
Peter J. Sharp Building
30 Lafayette Ave
Brooklyn, NY 11217

www.BAM.org

Tbrown@bam.org
718-724-8135



On Mon, Jul 4, 2016 at 9:31 AM, Nick Reilingh wrote:

I'm right now researching and developing a pretty heavyweight solution to this problem and am very curious what kinds of custom solutions people have come up with already.

My approach thus far has been problematic, but better than the alternative of manually searching each constituent. In our environment, we use a Tessitura attribute to match up records from the foreign database. The procedure I have now involves loading the foreign dataset into a local table in tessitura, then running a series of scripts to identify matches that already exist on the attribute value, or matches that DID exist but have been broken by merges in one or both systems (aargh), and finally potential matches on email, address/name, etc. What I don't yet have is an interface to easily approve or refuse those potential matches—basically what I am looking to develop.

I think you can do a lot of this with the constituent import utility as you suggest, but I want more control over finding duplicates (searching multiple addresses on each side of the import, for example).

Anyone else have a novel approach to dealing with the problem of overlap/matchup between a foreign database and Tessi?
From: Rog Hildreth
Sent: 7/4/2016 5:50:21 AM

So I need to see essentially take a smaller database from another department and see which of them are on our Tessitura. Any tips on how to do this without having to search one-by-one? My best idea so far is to make an import file and run Constituent Import in "Review Mode", then look for duplicates. Has anyone got a better way? We're not necessarily going to import those we don't have - the other department just want to see the crossover.

Cheers,
Rog



This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing 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!