At a recent conference for science editors I heard a lot of tech buzz words being thrown around—RSS, Wiki, blog, podcast. For that crowd, a lot of the concepts were new. After all, this group still focuses mostly on print journals and many of the editors remember vividly office systems sans computers.

Whatever your comfort zone, these technologies are here and as the public grows more Web savvy, they expect you to be up on the latest trends. One of my favorite parts of this new tech wave is that it’s relatively low impact on one’s budget. The Internet has in fact given Joe Public the keys to authorship through numerous free social networking and blogging sites. (They even let me on!) So, aside from the obvious commitment of time and creativity there’s no reason for you not to join the game.

Next question: What might a nonprofit use such tech for? (more…)

Considering people’s ever-shortening attention spans and given the shocking lack of grammar taught in public schools, it’s important to keep your writing straightforward to keep your readers on track. I didn’t do such a great job in that first sentence. We’ll have to see if I can rein in my verbose tendencies. This blog post is really to provide some top tips for writing for the Web. There are a few quirks when writing for the Web that are important to keep in mind.

• Consider your audience. You have people of all backgrounds and experiences surfing as equals. To accommodate this wide-spread audience, you’re going to want to write at about a ninth grade reading level or less. Newspapers generally follow this principle. They want their work to be as accessible as possible and so should you.
• Think about attention span. (again) As we continue on in our sound-byte driven, media overload world, people’s attention spans seem to shrink at a rate equivalent to the speed with which new toys for them to play with are developed. Not to be cynical or anything. What I’m trying to say is that you need to get to your point quickly. If you don’t capture attention quickly, your reader might surf on.
• Think about the mechanics of reading on screen. Depending on the machine a person is using, the screen size and thus the amount of text seen can vary widely. This is one of the reasons that long Faulkner-esque paragraphs don’t work well. Also, it’s really hard to follow visually as you scroll. Keep paragraphs shorter with a decent amount of space in between them.

(more…)

I’d love to see more folks taking advantage of our APIs. So, while driving home last night I thought to myself that it would be cool to start up a little open source API community where together we can post and modify samples in an open source format. So in just a few minutes today at lunch I was able to easily set up a Blackbaud community on Microsoft’s CodePlex.

I also uploaded a sample that demonstrates how to write a simple plugin using the Raiser’s Edge 7.81 and Visual Basic .NET 2005.
You can view the project page here.
(Note this sample will only work with RE 7.81 or later, since 7.81 ships with the required .NET 2.0 support files)

Did you know that Plugins do not require an API license to create? That’s right, grab this sample, play with it, make your own plugins and contribute them to the project/community! The only restriction I am making is I am putting all code under a Creative Commons License.

I’ll be up front with you, I probably won’t have much time to field direct questions on any code I post. Also, this isn’t officially suported Blackbaud product. That said, if you are looking for a place to learn more about using our extensive APIs and plugins, I hope this community will serve as a launch pad. I’ll upload more stuff when I get free time and inspiration. What I’d most like to see is what you come up with.

Now go buy that .NET book and start coding! Be sure to let me know if you’d like to contribute code or projects, I’ll add you to the open source team. Make something really cool and we may ask you to join the Blackbaud Product Development team

Shaun

We talk a lot about nonprofits using the social web to attract and engage donors, but the concepts trend more towards awareness than action. Using MySpace or YouTube to deliver your message to a broad audience is one thing - getting them to act is another.

That’s where SixDegrees.org, AOL Instant Messenger, and Network for Good come in. Someone had the brilliant idea to put these three ingredients into a giant Web 2.0 blender in the hopes of producing a tasty, social fundraising smoothie – and it looks like they have succeeded.

With Kevin Bacon as the natural pitchman, 6Degrees.org is asking donors to choose a nonprofit, then get 6 friends to give to the same organization. Network for Good is covering the online donations, while AOL’s MySpace equivalent AIM Pages handles the social aspect. The idea is to use a social network to form impromptu giving circles…got it?

(more…)

Friday I was walking through the Product Development department when the Director of Core Technologies, Paul Gibson, waved me into a developer’s cube. I could tell by the look on their faces that they had something cool to show me. They sure did.

Paul Crowder (the dev) has been working on implementing platform-level support for KPIs (Key Performance Indicators) in our upcoming Infinity application platform. KPIs will be featured throughout future applications built on the platform (Galileo, RE8, Bullseye etc.) Apologies for all the code names, we’ll cover those in a future post.

What are KPIs?

KPIs are quantifiable measurements that reflect the health of the organization. By quickly scanning an organization’s KPIs one should be able to get a solid idea on how things are tracking against the defined business goals. Some examples might be:

• Response Rate for a direct mail segment
• Number of gifts per day
• Avg days to close a major gift
• Gifts This Month
• Cost Per Dollar Raised

Those are just a few samples, but each one represents a single value that could be calculated and compared vs. an established goal.

Infinity’s KPI Platform

Editing a KPI Definition

Infinity’s base platform support provides the following for KPIs:

• A framework and UI for establishing, securing, and managing KPIs.
• A way to express a goal for a KPI.
• The ability to define warning and alert zones for a KPI as it progresses toward or deviates from it’s goal.
• An automated process to calculate KPI values and cache those values for quick rendering at a later time.
• A mechanism to back-calculate KPI values to establish historical trends.
• RSS support for KPI values so they can be monitored without running the application and logging in.
• A personal dashboard that can be customized by an end user to display the most important and relevant KPIs as the user sees fit.
• The ability to view the dashboard outside the application from any web browser without having to log in and navigate the application (assuming the user is authenticated).
• A stock set of KPI calculations “in the box”.
• Advanced support for creating custom KPIs using an open, extensible XML specification. (you’ll be hearing a lot about “specs” in the Infinity platform as I discuss it in future posts…)

(more…)