The reason I post these is because 1) I think they might be helpful resources, and 2) you can get a feeling for what I’m working on, or thinking about (or wishing for.) For instance, the reason there are so many links about Amazon is that we are now beginning a project that uses amazon in earnest, with some others possibly on the way.
Although it’s not often used in nonprofit settings, the Drupal module (or, more correctly, a large suite of modules) called “Ubercart” is a pretty amazing tool if you need to create a shopping cart system. We’ve implemented it for organizations that want to sell fees for events, sell items, and take donations. It doesn’t have many of the strengths of CiviCRM, but it has a lot of useful features if you want to sell things, or combine selling things with taking donations, memberships and selling event tickets.
A while back, I’d heard of the Ubercore initiative – a group of developers working to bring Ubercart to Drupal 7 (there was quite a delay between the release of Drupal 6 and the availability of Ubercart for Drupal 6.) That initiative is now called “Drupal Commerce. (other site here.)” It is basically meant to be a rewrite of Ubercart for Drupal 7. It looks to be something to watch. Gregory Heller of CivicActions wrote an interesting conceptual piece on the integration of Drupal Commerce and CiviCRM that’s worth a read. (By the way, there is a module done by DharmaTech that integrates CiviCRM and the current Ubercart.)
Tagged as:
civicrm,
CMS,
drupal,
drupal7,
ubercart
You don’t hear me talking much about social media. One of the reasons is that there are a number of really good bloggers out there who know the field far better than I’ll ever be able to. I would argue that Beth Kanter is the best social media blogger there is in the nonprofit space. Her careful writing about the strengths and weaknesses of social media, the in-depth knowledge of strategy and approach, her on-the-cutting-edge understanding of trends and issues and how they relate to the work that nonprofits are doing has been an incredibly important resource to the sector. If someone asks me about social media, I just say “ask Beth!”
And, it’s her birthday! A big bunch of us are blogging today to talk about what she’s contributed, and also to let people know about the charity she’s been working with for a while, now, the Sharing Foundation. She’d like folks to donate in honor of her birthday.
Beth, thanks for the expertise and intelligence you’ve lent to the nonprofit sector for quite some time now! And thanks in advance for all the great upcoming posts in 2010 and beyond that will help me sound intelligent when I talk about social media. :-)
It’s taken me a while to write this blog post, mostly because I have been working hard at various things (like building a business and building new websites.) This is the last installment in my CRM/CMS integration series, that started almost a year ago (wow!) And I’m skipping Joomla/Salesforce Integration because there isn’t any publicly available documentation or code about the integration that PICnet did with Joomla and Salesforce, called J!Salesforce. [update: see Ryan's comment below.]
So what is the state of Drupal/Salesforce Integration? It’s not as mature as the Plone/Salesforce integration, for sure, but it is coming along nicely. There are several contributed modules:
- salesforce – main module, with API, node, and user integration possibilities. This module provides the basic salesforce API connection (via SOAP), and includes field mapping, and basic import/export
- sf_webform – Makes integration with webforms in Drupal fairly easy. Web-to-lead is quite nice and flexible with this module.
- uc_salesforce – Provides integration with ubercart orders
- parser-salesforce – Integration with FeedAPI – pulling data from salesforce into drupal nodes via FeedAPI (I hope to start maintaining this module)
- sf_import – Import Salesforce objects into Drupal nodes (will be folded into the main salesforce module)
All of these modules are in alpha or beta, although I know for a fact that some of them (or versions of them) are working in production sites. There are a fair number of bugs that need to be fixed before there is a stable release. There are a bunch of outstanding issues that need a lot of work (like caching, for instance). There are two other modules that are related, but don’t use the main salesforce api module – one for ubercart, and one for web-to-lead (called salesforcewebform). That module has a stable release, but only provides the ability to integrate between Webforms and leads, not other objects.
Right now, the salesforce module allows for integration of contact, lead and campaign objects only. so that’s another big area that could use some work.
There is a good screencast done by one of the folks (Jeff Miccolis from Development Seed) who has worked a lot on this project.
I’d say that in a year, we’ll have a good solid module release, providing lots of features for integration between Drupal and Salesforce.com.
Tagged as:
CMS,
CRM,
drupal,
integration,
nptech,
salesforce
One of the great things about the nonprofit technology field is the collection of nonprofit organizations that provide what is often called “Intermediary” services to other nonprofits: information and resources that help nonprofit organizations do the work they do in the world, by helping them make good technology decisions.
I’ve been involved in one way or another with a number of these intermediary organizations. One of them, Idealware, is an organization whose goal is to provide the sector with unbiased, analytically developed reviews and information about software that nonprofits use in their everyday work. This is incredibly important stuff, and it’s darned hard work – I know, I’ve been involved in doing a bit of research for Idealware.
If we don’t have this sort of research in our sector, nonprofits won’t have the kind of analytical approach to software available – it is much needed. As you might imagine, funding this sort of work doesn’t come easy – they need our help to be able to continue to provide great research.
Tagged as:
idealware,
nptech
I’m warning you – this is snarky.
I was only vaguely following the brou-ha-ha over Causes leaving Myspace. Only vaguely because I don’t really keep close track of the goings on in the Social Networking space: it’s not my passion. I use them a lot, both for work as well as for personal use. I know they are becoming an increasingly important tool for nonprofits in communicating with their constituents, and so I do keep them in my peripheral vision, for sure.
Anyway, in reading the varied reactions to this news, I had to just sigh, and then get annoyed. Sigh because of what feels to me to be the wasted energy that the nonprofit sector has spent over many years, using, hawking, and supporting proprietary tools and companies. Annoyed because it seems the nptech community hasn’t figured this out, even being hit over the head with this over, and over, and over again.
Make no mistake about it – Causes is a for profit company, and they are making what is, I’d bet, a decision based entirely on economics. If you’ve read any of the gloomy news from Silicon Valley, this is just the beginning. Social ventures will not be immune to the blowing winds of economic distress.
If we keep building our nonprofit toolsets on proprietary software and for-profit web services, even if they are free (for now) we are going to be bit by this over and over again. The only way we’re going to get out of this cycle is to channel this energy and resources into open software (including “open” source apps for proprietary web services), open standards, and open networks – things no one can take away.
I love to write blog entries about successful open source efforts – like CiviCRM, or the amazing stuff people are doing in the mobile space. Writing blog entries about for-profit web vendors that make economic decisions that hurt nonprofits because we depend on them too much is just not fun.
Tagged as:
nptech,
opensource,
openstandards,
socialnetworks
Yesterday, I spent the day in Manhattan, at the UNICEF building, with a bunch of folks passionate about the technology in mobile phones, and the ways to use that technology for good. I’ve been a very long time cell phone user (had one since 1998), but I haven’t been involved in implementing a mobile system for an organization, so I had a lot to learn.
The place to find reports on what happend is on the wiki. Also, check out the twitter stream for the #omc09 hashtag.
I was especially interested in the issue of mobile data collection. (I was so interested, I facilitated a session.) And, even more specifically, I’m interested in how to leverage CiviCRM and mobile devices for a range of interesting applications. There are a number of ways to get data from mobile phones into a CRM – and all have advantages and disadvantages, depending on a lot of things.
- Globally, what you can basically depend on is SMS. Smartphones haven’t made it into most of the developing world, nor have 3G networks. So how do you get SMS data into a database system like CiviCRM? You need an SMS gateway, and systems such as RapidSMS to gather data
- Use J2ME to write applications for mobile phones, and send the data via SMS to a central database.
- A tool such as EpiCollect, which is an Android app.
- A slimmed-down, simplified webform to be used on mobile browsers.
One thing that would facilitate this would be a more robust API system in CiviCRM – access to the data via REST or JSON, which would allow CiviCRM to talk with some of the tools out there like Mesh4X.
I learned a ton. Thanks to MobileActive.org and the Open Mobile Consortium for a fabulous event.
Tagged as:
civicrm,
CRM,
Mobile,
nptech,
opensource
