CiviCRM is making a huge difference to how we operate and process our interactions with volunteers, donors, service users and supporters. We work across all modules and are seeing increasing contact and reducing time-intensive processes, whilst all the time improving relationships.
We are committed to open source as an effective means of building shared community resources and CiviCRM is an awesome, exciting and inspiring demonstration of the effectiveness of this approach. We are grateful for all the work done so far in enabling us to have this incredible resource made affordable and available, and looking forward to participating in the CiviCRM community.
I am trying to build a stronger End-user community withing CiviCRM to increase cooperation among non-profits using CiviCRM in similar ways. Going to CiviCON and being a part of the community at the conference has made me want to make the End-user community more robust. I think the open-source and non-profit focused nature of CiviCRM lends itself to strong community building as is an aspect of CiviCRM that is exciting!
CiviCRM helps the organizations we support to do what they have to do! At CiviCooP we assist our customers with implementing and using CiviCRM. This includes functional support, training, project management, data migration, customization, system integration, helpdesk support and hosting. We are based in The Netherlands.
Our customers are mainly non-profits, varying from larger organizations continuously improving the way CiviCRM supports them to smaller organizations using the core functionality and perhaps contributing to a Make It Happen. We have been active in the CiviCRM community since 2009. CiviCRM is all about community, sharing and producing together. We truly believe that one and one can be three!
As users since 2007, we have watched CiviCRM grow right alongside of us. Our growth as an organization, our ability to serve our members and donors and our ability to support, protect and preserve the amazing system of state parks and historic sites through Georgia is directly tied to the growth of CiviCRM.
CiviCRM allows us to bring all benefits and capabilities of a large commercial CRM and
donor management system to medium and large non-profits at a fraction of the cost. CiviCRM also allows smaller non-profits to benefit from an integrated solution for donor management, events, bulk email, etc. substantially increasing their effectiveness as compared to managing a variety of nonintegrated software and spreadsheets. Thanks to a strong CiviCRM community, CiviCRM’s functionality continues to advance and CiviCRM’s market continues to grow rapidly.
We recently had one of our groups report that merging data was resulting in data loss. Specifically, when they merged two records, they noticed that the contribution records on the record that was deleted were not carried over to the record that remained.
I investigated and found the culprit: we were missing a foreign key constraint between the contribution table and the contact table. In fact, we were missing a lot of foreign key constraints in this database.
The ability to create petitions in CiviCRM was a tremendous move forward for people using CiviCRM for political organizing. The petitions feature took another step forward with the Petition Email extension, that allows copies of your petition to be automatically sent by email to a given target. However, the holy grail of e-advocacy was still just out of reach: automatically sending your petition to the petition signer's elected official.
When generating mailing labels, CiviCRM users have the option of choosing the address to be used (e.g. you can select "Primary," "Home" or "Work") depending on where you want to reach your contacts.
CiviMail, however, does not provide this option. Instead, CiviMail automatically chooses the address for each contact - a process we can only control on a contact-by-contact basis by setting the "Bulk Mail" or "Primary" flags for each individual contact.
Have you ever completed a training a wondered whether usage of your CiviCRM database changed as a result? Have you ever wondered who were the major database users in your organization and who might need more prodding?
With the 4.3 upgrade, the Progressive Technology Project has made a number of important steps toward breaking out our work into pieces that others can use on their sites. This blog will begin a series of (hopefully) weekly blogs outlining new functionality that others can use.
Our first blog features the civicrm_petition_email Drupal module. Thanks to the hard work of agh1, a Drupal 6 version of the module is available (https://github.com/agh1/civicrm_petition_email). We just finished porting it to Drupal 7.
Progressive Technology Project has released a new Drupal module called CiviCRM Cicero that integrates with the Cicero service from Azavea. If you are using CiviCRM with Drupal, you can now add legislative district and more information to your database.
Last spring I started working on a Drupal module that would keep CiviCRM contacts in sync with Salsa contacts. I did a lot of the work on it and then, upon joining PTP's staff, the project unfortunately fell to the bottom of my stack.