Just one day after arrving back from weeks of holidays I found myself in the train from Brummen (The Netherlands) to London for CiviCon 2011, of which we were proud Silver sponsors. We arrived in time, and it was great to meet my API friends Xavier Dutoit and Eileen McNaughton (who I had never met IRL) and Kurund Jalmi and Yashodha Chaku from the CiviCRM Core team.
Our customer De Goede Woning in Apeldoorn (The Netherlands) has formally gone live with CiviCRM as their customer information software. It is as far as I know the first Dutch social housing corporation to use CiviCRM.
We had a good CiviCRM meetup in Apeldoorn today, hosted by De Goede Woning. Willem Peters from qbset (http://www.qbset.nl) showed the first version of qbMobile, a native iPhone/Android app that he is developing for a specific customer.
Hi all,
as announced earlier the Location API is no longer with us in the API v3 version. It was a beast of an API, too smart for its own good and certainly to smart for the API team!
We have set a date for the next CiviCRM BeNeLux meetup: Friday 15 April 2011 in the afternoon. More details will follow, but we do expect a demo of the CiviCRM Mobile app (Android and iPhone) from qbSet.
We will also present the new feature on the upcoming 3.4 and 4.0 versions. If there is enough interest, we will focus on the new API v3.
Erik
De Goede Woning is the first Dutch housing corporation to start using CiviCRM, and they are in the middle of their implementation process, expecting to go live in March 2011. One of their main loves in CiviCRM is the functionality of CiviCase, which they will use quite extensively for the following processes:
For our project at De Goede Woning we have been developing a data synchronization process between CiviCRM and their main transaction system in Oracle (comparable with an ERP). Some data for a contact (first name, middle name, last name, gender and birth date), phones, emails and addresses will be common between the two, so a change, create or delete in CiviCRM will have to be synchronized with the main transaction system and vice versa.
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:
