Just a quick update to say that the 'de-dupe exception table' initiative is now funded for release 3.3. This will allow those poor souls struggling through a big de-dupe to mark some contacts as 'non-matches' and not have to wade through them every time.
This initiative was sponsored by
Creative Commons
Community Builders Australia Pty Ltd
Australian Greens
NES Alumni and Friends Nonprofit Partnership
Today is the last day of the Bristol code sprint, which was a great experience! Lots done, climbed the Cheddar Gorge and tasted Kurundś famous lamb.... I will also always remember it for finding out I was part of the API team :-)
On a serious level, it is a good idea to have a team of people that take care of the API's. And taking care I think involves:
A couple of blog entries back (http://civicrm.org/blogs/mbriney/contacts-erd-v31 to be precise) Matt Briney was kind enough to share the contacts ERD with us! I promised to put some more on. The entire CiviCRM ERD is too big and complex to be useful in this format, but I have just created one for the location point of view.
We are extending the 3.3 deadline to the 3rd of October to make one last push towards getting more of the initiatives into 3.3 and after that the focus will move to trying to get some more momentum for 3.4. Personally I would LOVE to see the dedupe exception table item get some funding. Anyone who has done deduping themselves will understand why!
I'm pleased to announce that the target for the first of the Civi-Make-it-Happen initiatives has been reached. We have raised $750 to fund enhancing the dedupe functionality to merge CMS user accounts when de-duping. Those of us who are familiar with the experience of clicking on each contact to see which one has a userID before clicking merge will be pleased to see this enhancement and grateful to those who donated.
Over the last year rayogram has worked with the New York State Senate to deploy a customized version of CiviCRM 3.2 for each Senate office. In the course of this work, we developed a custom theme for NYSS that leverages much of the template work that we did for the CiviCRM 3.2.
At September's meetup Kyle Jaster from Rayogram presented the newly released SimplyCivi Drupal theme, designed as a cleaner, more useful and user-friendly administration theme for CiviCRM.
Sometimes I get frustrated with CiviCRM. For all the great features there are problems / limitations that we seem to keep hitting. So, if lots of people want the same things added / fixed why aren’t they being fixed?
