Getting rid of duplicate contacts (Updated in 3.1.0)
I like clean data and so having many organization records with duplicate contacts drives me nuts. Deactivating a user doesn't delete them from the contacts, unfortunately. I would like to see a holding tank where we could move the duplicates so they don't clutter user information. In lieu of that, I'll have to create a dummy organization where I can store all the dupes.
Idea posted June 16, 2011 by Leslie Wozniak, Five Bridges Foundation
-
Erin commented
I just found a work around. The Z delete org I created had a Charity Check run so I could not delete the organization. I created another placeholder organization where I could transfer contacts and then delete organization and related contacts. Yay!
-
Erin commented
I too have done what Leslie has done. I really wish I could delete these though. This holding tank org (Z delete) where all these undeletable contacts are housed has a lot of contacts. The applications and organizations related to the contacts have been deleted. I just can't delete the individual contacts.
To provide some background. I am trying to delete old $0 grants. These grants funds were returned or I made a $0 grant to so we could receive a report but the real recipient was another org.
-
Chris Dahl commented
Hi all,
We're in the process of finishing our next release. One thing we are adding is better handling for deactivated contacts. Basically, as Leslie suggested, there will be a "holding tank" for them. On the Organization Summary, they will no longer display in the list of contacts, but in a separate list of "Inactive Contacts" that will be collapsed by default.
We are also working to improve the Registration process to help reduce the duplicate contacts that are frustrating for us as well as all of you.
This release should be in our DEMO environment in the next few weeks, and I'll try to email you when it's there.
Thanks again for the feedback and ideas
posted October 13, 2012 by Chris Dahl, Foundant Technologies
-
Chris Dahl commented
Thanks for the input.
I can see by the posting dates that this is a bit of an older thread - however, I'm pretty sure the problem is still relevant. We are looking at making some fairly big changes to how we manage and merge organizations, contacts, etc. We've also discussed better ways of handling deleted and deactivated users. One of the challenges around handling deactivated users is the fact that a user is still attached to applications, etc., so it's hard to just remove them from being visible within GLM.
At this point, we're just discussing things internally around better management of organizations and contacts (i.e. making it more clear who is the ED, etc.). However, it's an important topic and one we need to make improvements on not just for clients, but to enable some more strategic direction and flexibility in our system. It's a pretty high-priority item on our product backlog. Given the complexity, it's not something we expect to resolve in the near-term, but it is something that is in the works. You might check out the following Idea Lab item for something that is related ... Grantee organization able to see all of their grants...
Thanks
posted July 20, 2012 by Chris Dahl, Foundant Technologies
-
Ideas commented
I do the same thing as Leslie and have created a dummy Org. There are a couple of organizations that we've been making grants to for over 25 years, so there are a lot of duplicate and/or really obsolete contacts. It would be great to be able to delete contacts or at least delete the dummy organization. It would also be great if there were a way to merge duplicate contacts!
posted June 28, 2011 by Laura Mapp, Henry M. Jackson Foundation
-
Aaron Spevacek commented
One instance where this pops up is when an executive director is listed as an executive director and later becomes the primary user.
posted June 20, 2011 by Aaron Spevacek, Foundant Technologies
-
Ideas commented
Thank you for your comment Leslie. Sounds like I may need to investigate further. My impression was that contacts no longer associated with request should have the ability to be deleted. There are a few areas in GLM where it is apparent we need to better handle old or obsolete data. Great input!
posted June 16, 2011 by Raymond Burket, Foundant Technologies