CiviCRM is a great solution for non-profits looking to integrate their fundraising, event, membership, grant and email management systems. JMA Consulting is a leader in developing extensions and core contributions for CiviCRM.
CiviCRM provides a great solution for our Non-Profit customers. And as a big proponent of software with no per user fees, no recurring subscription costs, and an open eco-system, I absolutely love what CiviCRM offers for our customers.
ISBA is an international non-profit society with members from all over the world. We have sections that represent different scientific areas and chapters that represent different regions of the world. Civi Member powers our membership system! We use CiviEvent for Conference and Workship registration, and utilize CiviPetition for creating new sections to our society through member petitions. We are epxloring how CiviGrants can be used to track our travel awards and look forward to features for integrating accounting and finance. As a growing non-profit CiviCRM plays a major role in managing our membership system!
The CiviCRM community is a fantastic resource of developers, end users and system implementors. We believe whole heartedly in the power of open source communities such as CiviCRM to make things happen that wouldn't come into being in a purely profit-driven setting.
CiviCRM brings continuity and coordination into our ever-growing company and database. By tracking the activities of our constituents, we can better serve them. By better serving our constituents, we can focus more on our mission: Developing young people into magnificent human beings through participation in the performing arts.
When implementing CiviCRM in our organisation, we got for the first time a complete overview of all our contacts, mailing lists, partners, members in one tool. You do not need to be a database genius to use it on a daily basis, and my colleagues have embraced the tool due to the easy and user-friendly interface. It meets all our needs as a contact management system and as a mail manager. I am sure that we will start using more of its components in the future.
CiviCRM is helping us serve member-based community organizing groups across the
U.S. to keep better track of their events, fundraising, and membership data. It's helping our community to aim higher in terms of what kind of questions they should be asking and what kind of data they should be collecting. We chose CiviCRM because it's the best all-around tool to do what our groups need, AND because it's open source.
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.