Ask Idealware: Integrating with Raiser's Edge
Michael asks: We're in the midst of pricing out a fairly complex integrated system which is likely to include Raiser's Edge. We'd like to be able to integrate Raiser's Edge with a legal case management system, to be able to easily pull together mailing lists from both systems. I've heard that it's difficult and expensive to integrate Raiser's Edge, but our developer thinks that the database doesn't look too bad. Are we missing something? Are there fees or complications that we're not considering?
Steve Birnbaum of Jacobson Consulting Applications, Inc., a consulting firm that helps clients select, use, and integrate software including Raiser's Edge, says:
In general, successful integrations balance business needs against complexity. It is important to minimize dual entry and to provide complete and accurate information in all systems, but the more data points you integrate, the more complicated and expensive the project. Also, consider your capability to support the integration over the long-term. Software changes on either side, so programming never ends. If you don't have the technical expertise in-house, make sure that your integration provider offers a service contract that guarantees functionality after system upgrades. This is a marriage, not a fling.
Technically, there are some specific issues when dealing with The Raiser's Edge® (RE). You can develop a methodology based on standard RE imports, which are part of the front-end of the application. This approach lacks elegance, but it works and it is covered under Blackbaud technical support. Legally developing a fully-automated integration requires the purchase of the Blackbaud API. Writing directly to the back-end of the software without the API may violate the terms of your service agreement. If you do pay the $15,000 for the API, make sure that a good intellectual property attorney reviews the API contract (all software contracts actually), as it seems to indicate that Blackbaud retains ownership of all intellectual property created using the toolset.
I would recommend using extreme caution when working with developers unfamiliar with the technology and company; we have seen many organizations get burned this way. Good luck.
The Ask Idealware posts take on some of the questions that you send us at ask@idealware.org. Have a great option to suggest for this question? Hate our responses? Help us out by entering your own answer as a comment below.
Permalink  
![]()
1 Comments:
I would have to disagree with some Steve's comments. I have many years experience of developing customizations for integrating The Raiser's Edge with different software packages.
There is no requirement to purchase the API module from Blackbaud. It is quite feasible to create a customization that integrates RE with another package by creating a plug-in. This plug-in has to be started from within RE but that is the only real limitation. With the API you are able to have real time integration or scheduled integration but if this is not a requirement then running the integration on demand as a plug-in is a lot cheaper than paying for the API.
As far as I am aware all intellectual property rights of software that runs against an API in the same way as a programming language (whether this is Blackbaud's, Microsoft's, Sun's, etc) is based on the code written not the API itself. (Having said that I am not a lawyer and laws and interpretation of laws vary between states and countries).
If Blackbaud write a customization for you they will invariably retain the rights to the code (I have not encountered an example where they have released the source code of the customization to the client).
Others, including myself release the code as part of the overall solution so that if you need to make a change in the future you are not bound to the original developer.
David
Post a Comment
<< Home