Cause to Pause

As a rule, I like things that work and play well with together. It’s no secret we are an ACS shop. A big part of that is the support department, the other is the tie in between their online member offering (AccessACS) and their web CMS (siteExtend). As a CMS, siteExtend is the easiest I have worked with because of the way the back end is laid out. Everything is listed in a series of “cabinets” or “managers”. There’s one for content, one for media, one for channels, etc. The handling of local and global CSS and JS files is the easiest I have worked with so far. It’s a nice piece, but where they really shine is in the linkage with AccessACS. You can read about how we used that to streamline our Elder meetings and reduce paper costs here.

This is all driven from your local database. If you have a group, it doesn’t matter what the group is, you can create a private “channel” on your website that you can then populate with various information. How does it look? It looks like this:

As you can see, it is pretty easy to set up the private channel. Once you create a new small group, activity, class, etc. and do an upload, it will automatically become available within Extend. In this case, anyone who is a member of the Activity Group Leadership>Current Elders and Staff can log into the private channel. Once they are removed from that group, such as an elder rolling off their term, their login will no longer work for that channel. You can go all the way down to the “fourth element” in an activity group, which in this example would have been Leadership>Current Elders and Staff>Hospitality Commission>Fall Festival Committee>Chairperson. Yes, you can get that “granular”. You can also create a channel that is as wide as available to anyone with an AccessACS login. No matter what group they are in – or not in.

When churches talk about integration between our websites and our groups, we generally think “How can I get a list of groups on my site.” which results in some type of iframe or “finder” device. But, if you are going to use your site as more than a “digital brochure”, and there are content pieces that you don’t want to  out and around….or worse yet – PRINT. How are you going to do that? There is some information that your members or regular attenders may want to see, but it really wouldn’t be appropriate for a visitor or someone checking your church out. How would you do that? Could you set up a channel or a whole group of channels tied to logins in less than a minute?

ps. We did set up a wiki site for our budget and controlled the login via Extend.

Better late than never.

A little over a week ago the annual ACS Technologies convention took place in Louisville, Ky. Here’s some of my random thoughts:

1. IT Roundtable. Dean Lisenby always hosts this. This year it was opened to non-ACS customers. Guess what, we all have the same problems. Treading the line between “equipping for ministry” and “letting them do whatever they want”, between “securing the resources we have been entrusted with” and “hampering ministry”. That is what makes CITRT so valuable. Join it today.

   Lot of discussion on Google apps and who “owns” the data. If a staff person uses their personal Gmail account and leaves, gets hit by a bus, etc. then what? If you don’t provide easy tools, they will just find their own and guess what – you end up supporting them anyway.
   If you do “go Google” do you “go all the way and ditch Office” or use a combination approach?

   Darryl Hunter was there, as was Jason Powell and a host of GCC folks including Kem Meyer. Funny how when she spoke all the keyboards went silent.
   I am guessing there was somewhere around 45-50 people in the room.

2. For the conference itself, it was supposed to be completely different than previous years. And different it was. Each morning and afternoon there were three main sessions taught by teams made up of ACS users. Not employees. These classes changed the focus from “you can do ‘x’” to “here’s what we did, what worked, where the holes were and how we overcame them….or didn’t”. Instead of having someone who knew the software, but happens to volunteer in their church, – or used to work in a church; you have someone who still lives and breathes the same environment you do every day and but happens to use some of the same tools. Subtle shift, but big perception change. As big as going from “theoretical” to “practical”.
3. There was also a “main stage” in the display area that had the equivalent of “live 10 minute infomercials” to show the “what you can do” aspect. I give those presenters a lot of credit. That had to be tough as people would basically just walk by, but I was able to catch the ones I needed to and it helped.
4. There seemed to be less ACS staff there, but a lot more interaction. The set-up was less “convention/trade-show booth-y” and more circular.

My personal takeaways:

1. I picked up a lot more information on topics I had been over before. Stewardship and Communications strategy were the two big ones.
2. I left with some serious projects I would like to get moving on. Done right, it will probably keep us busy for about three years. One of which may be MobileCause or some other form of mass text messaging.
3. This was a much better format. It is hard to quantify “interaction” without a lot of surveys etc. but from a customer standpoint it was definitely higher.

The big one:

Monvee
Multiple keynotes this year, including from John Ortberg and the founders of Monvee. Monvee officially “came out of beta” the day before the convention.
(continue reading…)

A few months back I wrote this post on the ACS/Outlook plugin that pulls your member data and calendar events into Outlook. There’s also this video on how an event goes from inception in AccessACS to someone’s Outlook calendar and phone.

If you were wondering if the plugin works with Outlook 2010 (beta), the answer is “yes”. (I know, it’s just a series of API calls, it should continue to work.) The only hitch in the git-a-long so far is Outlook does not seem to maintain login id creds. when you close it. Next time you open Outlook, you will need to enter your username and password into the add-in section.

Too bad Google‘s calendar synch returns the “only works with Outlook 2003 or 2007″ error.  Totally kills the last step in the process for me…