Duplicate Registrations

Jody Johnson

Hello, 



We have a TeamRaiser event set up for people to do independent fundraising. Right now TeamRaiser's only allow a constituent to register one time. But as some individuals may do multiple events in a year, do you have any suggestions on how we can get mulitple registrations for the same constituent?

Brian Mucha

As far as I know there is no getting around the unique name and email requirement.



So you could have them use different names (Pat and Patty) for each record, but that might risk inadvertant constituent record merging.



Or if they are using certain email providers such as gmail they can create unique email addresses for themselves. For example, brianmucha@gmail.com and brianpmucha+anything@gmail.com both will be delivered to me. Gmail ignores the + and everything after it, but to Luminate they are both different and unique.



No great solutions here, but we are trying to do something with Teamraiser that it was not designed for.



We also get the same event over multiple years, so you have to disband the team and remove the participant's old registration in order to 'reset' fundraising (and then rebuild what they had on their old pages!)

 

Noah Cooper

What some of the organizations I've worked with have done when setting up a DIY program is create one TeamRaiser per type of page someone might create, rather than using participation types to accomplish this. For example, they might have a "DIY" blueprint, with a "DIY - Birthday" TeamRaiser, a "DIY - Wedding" TeamRaiser, etc. underneath it. Then, on some regular schedule, let's say every 6 months, they create new copies of each of the TeamRaisers and close the old ones. This should handle the majority of uses cases, except for the case were a single person needs to create two of the same kind of page in a 6-month window (something that shouldn't happen for things like birthdays and weddings).

Chris Cynar

Hi Jody,



The one registration restriction is going to only apply to a single event, meaning that while I can't register for the same one twice I would have no issues signing up for a different event later that year.  What I normally see clients do is just create additional events that are independent of the first.  I could then sign up for a Spring event, while also registering and participating in the Fall.  Each event will have it's own progress meters, donations, etc, and can then be compared against one another for reporting.  To make creation of these even easier I recommend using the Blueprint system to make a generic template, which can then be used to make copies you can later customize.  By linking these events you can even allow returning teams or participants to speed up the registration process.



Hopefully this will help generate some ideas for your future events.  If you have any questions about how to implement some of the features I discussed please don't hesitate to open a case and reach out to Support.  We'd be happy to help!



Regards,



Chris Cynar

Luminate Support

 

Brian Mucha

Noah Cooper:

Then, on some regular schedule, let's say every 6 months, they create new copies of each of the TeamRaisers and close the old ones. This should handle the majority of uses cases, except for the case were a single person needs to create two of the same kind of page in a 6-month window (something that shouldn't happen for things like birthdays and weddings).

That can be harder to do that it sounds. Our DIY TR has a few longer running events that don't end on a single nice schedule. So you wind up with both the previous and new TR running at once, until the previous one's events peter out. Edit: And of course of the events don't really end in a detectable way, they just stop getting activity.



Edit 2: There was a session about using TR as Personal Fundraising a few BBCons back, and there was a long discussion about making new instances periodically versus keeping the same instance and removing old participants and teams. Neither way is perfect and both ways had advocates.



Edit 3: One thing that bit us was fair market value and fundraisiers couching the donation to their event as a 'ticket' to a dinner or something. I have a thread or two regarding that here somewhere. (The FMV is teamraiser wide, so participants can't do this sort of thing or the donation receipts are inaccurate as far as tax deductable value goes. The newish ecommerce in teamraiser feature was the fix for us, by making the tickets into ecom items. Takes manual intervention though, like much with doing DIY.)



PS - Chris' post referred to 'events' but he really meant the Teamraiser itself, and not your 'event' (which are actually teams or participants within your Do-It-Yourself TR.)

 

Jody Johnson

Thanks for all the suggestions. We thought we would have to create separate TeamRaiser's, but were hoping not to.