CiviCRM is a powerful and flexible tool for providing relationship data management and insight. Equally useful is the active user community that not only encourages contribution, but empowers it as well.
Worked with CiviCRM as core team developer for more than 2 years. Now we are working as a team and providing service with CiviCRM installation, customization and training. One thing about CiviCRM community is that it's very healthy and really helpful. It's really great that i am part of this community and we want to grow this more and more . Also whatever the problems we are facing there is a solution on forums, or we will get the proper guidelines to solve the issues. Big salute to the CiviCRMcommunity :)
We recommend and use CiviCRM with most of our clients, and have since 2005. It's got a fantastic collection of functionality that fits the needs of non-profit organization communications, and the CiviCRM community of developers and users is growing, broad, vibrant and responsive.
The best part? When I describe to potential new converts how all of their constituent relations (donations, membership, mass emails, etc.) can be managed with a single integrated, configurable tool, I can hear an incredible yearning at the other end of the phone.
As a small and dynamic organization, the power combined with flexibility that CiviCRM offers us was crucial for our choice in choosing to use it. With my organization having used CiviCRM for more than three years and myself for around two, we try to give back to the community in whatever small ways we can - since an active community is so important to ensure the further development of this great product.
CiviCRM helps us help non profits to do fantastic things with their data.
Being closely involved with the developers and documentation team on a daily basis ensures that we can give our clients the best and most up to date advice on how they can use CiviCRM to meet their needs.
The community provides excellent forum support, new ideas and feedback on suggestions. The CiviCRM software suits many use cases and allows us to support a large number of diverse UK voluntary sector organisations.
I find the engagement with our community of users to be intellectually stimulating
and rewarding. Seeing folks with expertise in a particular area step up and contribute their time and ideas to help improve the product is quite exciting. Every time I hear about a new interesting organization starting to use CiviCRM, I get a renewed sense of excitement about our work. The range of civic sector organizations currently using the software is quite amazing to me - from large international advocacy organizations to local performing arts troupes. I also really enjoy interacting with our international community - building friendships and getting to share culture (food, music, humor ....) with colleagues on every continent.
Civi empowers organizations to maintain the data of the people they serve on their terms. The community is welcoming, happy to share and eager to document. I know where to look or who to message, that is priceless.
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.