UNmerging records

Hi all -

We've run into an icky situation here in which someone in the Box Office scheduled a merge for a number of institutional records which should not have been merged.  I need to know if there is a way of UNdoing this.

Any advice that other organizations have in terms of safeguards that they have put in place to prevent merges that shouldn't happen would also be appreciated.

Thanks!

 

-Lisa

Parents
  • Ken,

    Thanks so much! I always forget to go prowling through the Files sections – you’ve got quite a lot of good resources there.

    I like the idea behind the Association; this is something we could definitely use (I envision it being useful for father/son who share a name, for example). It would be great to have a less broad level of merge-blocking than the all-encompassing Void Merge.

     

     

    Best,

     

    Stacey

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwain
    Sent: Tuesday, December 01, 2015 8:08 PM
    To: Stacey Voigt
    Subject: Re: [Tessitura Technical Forum] UNmerging records

     

    Hi Stace

    The objects that support our merging solutions are stored in my files here.

    When I looked at them, I realised that they were pretty old versions (pre-v11), so I've updated the major ones, including LP_VALIDATE_CUST_MERGE, but I don't guarantee that they're all current versions - although I don't think the others have changed - anyway, should give you the general idea.

    The other notable protective device that we've added since this thread is an Association (UCSS Do Not Merge) which blocks a pair of constituents from being merged into each other, without blocking either of them from being merged with other constituent records. 

    Ken

    From: Stacey Voigt <bounce-staceyvoigt1752@tessituranetwork.com>
    Sent: 12/1/2015 3:32:48 PM

    Resurrecting this old thread as I look for solutions to some of our more tangled merge issues...

    Ken, would you be willing to share your version of LP_VALIDATE_CUST_MERGE with me? That ranking routine sounds like a useful addition to our safeguards.

     

    Stacey Voigt
    Consortium Services Manager
    Santa Barbara Center for the Performing Arts
    svoigt@granadasb.org




    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
  • Ken,

    Thanks so much! I always forget to go prowling through the Files sections – you’ve got quite a lot of good resources there.

    I like the idea behind the Association; this is something we could definitely use (I envision it being useful for father/son who share a name, for example). It would be great to have a less broad level of merge-blocking than the all-encompassing Void Merge.

     

     

    Best,

     

    Stacey

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwain
    Sent: Tuesday, December 01, 2015 8:08 PM
    To: Stacey Voigt
    Subject: Re: [Tessitura Technical Forum] UNmerging records

     

    Hi Stace

    The objects that support our merging solutions are stored in my files here.

    When I looked at them, I realised that they were pretty old versions (pre-v11), so I've updated the major ones, including LP_VALIDATE_CUST_MERGE, but I don't guarantee that they're all current versions - although I don't think the others have changed - anyway, should give you the general idea.

    The other notable protective device that we've added since this thread is an Association (UCSS Do Not Merge) which blocks a pair of constituents from being merged into each other, without blocking either of them from being merged with other constituent records. 

    Ken

    From: Stacey Voigt <bounce-staceyvoigt1752@tessituranetwork.com>
    Sent: 12/1/2015 3:32:48 PM

    Resurrecting this old thread as I look for solutions to some of our more tangled merge issues...

    Ken, would you be willing to share your version of LP_VALIDATE_CUST_MERGE with me? That ranking routine sounds like a useful addition to our safeguards.

     

    Stacey Voigt
    Consortium Services Manager
    Santa Barbara Center for the Performing Arts
    svoigt@granadasb.org




    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
No Data