Cecily, We've done an even lower tech tune-up to accommodate matching gifts. When it arrives, we credit the match to the original donor (since this doesn't impact the accounting system) which bumps them up on our annual giving lists. In the Pay Memo field we note the expectation of a gift, "First half of annual campaign commitment" and ultimately, "Second half of ....". We also have a field in the Payments file to use for each donor called Donor's Agent to store the name of the associated resource and a name record for that resource that has notes, but no payments recorded. Cumbersome, but that seems to cover all the different perspectives that we might approach the database with in searching for information. We call these gifts "contributions" and keep it simple. Melinda Artz Archie Bray Foundation for the Ceramic Arts
Carl Paulsen wrote: > Cecily, > > I haven't tried to create a "soft" credit attached to the ebase payments > file, but I've done something somewhat similar for a ticketing > function. In that case I duplicated the Payments file, renamed it and > reworked that file (and a relationship or two) to meet my client's > needs. A similar change for soft credits would take some work, and > you'd need to be careful, but I don't think it would be too difficult to > create a small amount of new functionality. The biggest obstacle, I'd > think, would be specifying just what functionality you need. > > Alternatively, and perhaps more simply, you could create a new value > (e.g. MatchingGift) in the Pay For field in the Payments file and create > a new set of relationships with the Names file that draw on this new Pay > For field value. This/these relationship/s could drive new summary > fields that could be used for purposes you've mentioned (like totalling > last year gifts including matches). Bear in mind here that it's > relationships and how they are defined in ebase that control many of the > payment summaries you use in ebase. You may also need to modify the > relationship keys for some of the other payments relationships to make > sure the payments entered as MatchingGift don't end up in the giving > totals, but even that shouldn't be too hard if you have some Filemaker > familiarity. > > Carl > > Cecily Clemons wrote: > > > > Part 1.1 Type: Plain Text (text/plain) > > Encoding: 7bit > > -- > Carl Paulsen > New Hampshire Rivers Council > 54 Portsmouth Street > Concord, NH 03301 > 603-228-6472 > 603-228-0423 Fax > [EMAIL PROTECTED] > > ------------------ > Reminder to each recipient: To change your list account preferences, go to > http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email >address you used to subscribe to the ebase support list:: [EMAIL PROTECTED] > > To unsubscribe send a blank email to [EMAIL PROTECTED] > --------------------------------------------------------------------- > ebase - Relationship Management for Nonprofits, http://www.ebase.org > ---------------------------------------------------------------------
begin:vcard n:Artz;Melinda tel;fax:406/443-0934 tel;work:406/443-3502 x-mozilla-html:FALSE url:www.archiebray.org org:Archie Bray Foundation adr:;;2915 Country Club Ave;Helena;Mt;59602;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Office Manager fn:Melinda Artz end:vcard
------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
