Shelley Keith

This is the message I just sent my brand new social media student worker. I’ve given him some time to get used to the office, read some great social media resources, watch useful videos and talk theory with me while getting to know the personality style we use here. Now, time for him to get his ass to work.

You are ready young Padawan. Time to get your work on.

Daily Tasks:

1. Be on Facebook SAU page responding/interacting/uploading. Find answers to questions if possible. Refer users to appropriate offices if necessary. Keep upcoming events up to date. Review other Facebook pages and come up with ideas for things we can do with ours.
   1. Goals: greater FB interaction with all audiences; a regular and constant presence.
2. Check Twitter for questions/comments to answer/respond to or retweet appropriate content from those we follow. Review our list of followers for people we should be following, review their lists, etc. Build an interactive community of related Twitter users. Keep the SAU Twitter list up-to-date. Consider new, creative, funny (yet appropriate) Twitter lists.
3. Daily review of We Are SAU. Check for group creation, unanswered questions. Write blog posts explaining new features, welcome and help new users. Propose ideas for ways to boost users and user activity including content and features. Follow users on Twitter when they post their Twitter names. Suggest design improvements.
4. Check MySpace for activity and begin reconnecting with users there.
5. Check H drive daily for new photos to add to Flickr & Facebook with as much descriptive information as possible. Review related press releases for ideas.
6. Begin reviewing Flickr photos and adding titles, descriptions and keyword tags as appropriate/possible. Tweet awesome photos. Establish “friends” whenever Twitter/Facebook/etc users post Flickr photos.
7. Make sure each new YouTube video is posted to Facebook, Twitter, We Are SAU and MySpace. Propose ideas for new videos.
8. Forever uphold the core value: Han shot first.
9. Propose ideas…all ideas.
10. Other duties as assigned.
11. Notice: scoping virtual hotties is not on this list.

Before I launch full-steam into the BuddyPress socNet project I’m putting together some relevant research to support various features. One thing I’m trying to learn is how many institutions offer faculty and staff a blogging vehicle within the confines of University provided services. To that end, here’s my quick poll on LinkedIn. I appreciate all those who take a moment and respond. I’ll post the results here.

So I’ve gone into my WPMU project a little and briefly mentioned the BuddyPress university community site currently in process. Now I’d like to touch upon how these projects plus existing social media tools can be used to support online education initiatives at my university.

Today, we’re really just scratching the surface of online/distance education. Last summer we released a completely new distance ed support site that essentially offers some step-by step registration help, links to campus resources, and FAQ info. It’s not a distance learning recruiting tool or a hand-holding retention piece, but it is progress.

The existing distance ed site is in WP, so the migration to WPMU won’t be much of a stretch. The big bonus here is going to be the opportunity to get more of the faculty currently teaching distance classes involved in the day to day distribution of the information given to distance students/prospects. The act of migrating will allow me the chance to sit down with the committee again and pitch the use of Twitter, Google Calendar and the university community site (for starters). I’ll also get to dig into some WPMU only plugins and features that may help bring the University into this century.

The BuddyPress community site could see heavy use as a support/retention tool for the academic side. I’ve already seen incredible interest in using the groups feature to fill gaps in available campus services, specifically for non-traditional students. This group doesn’t operate the way traditional students do, and therefore aren’t able to make a standard campus group work (nobody can nail down a time for meetings). An online group will give this demographic the opportunity to interact and get to know each other on their own time. Similarly, distance learning students are literally all over the map. They get very little interaction from campus outside Blackboard and the generic swarm of student email, so an online group could bring them together for, at very least, moral support.

Another campus initiative I find myself involved with is the Staff Development committee. The purpose is as advertised, to find ways to offer a variety of support and training to the staff. We’re all over-worked, so getting a large group of staff together for regular face-to-face training is impractical. It’s been left to me to find ways to offer online professional development opportunities that don’t cost much anything. The intention is to send a bi-weekly email newsletter containing, among other things, links to a tutorial or video considered helpful to our staff. All hail YouTube.

The combination of the WPMU (with the customizable universal dashboard plugin) and BuddyPress projects will also allow me, as sole web staffer, to support and assist my faculty and distance staff by letting me introduce useful sharing tools like Google docs, Slideshare, Twitter, social bookmarking and a huge list of great YouTube tutorials…all with no budget.

Inspirational links:

• How to create and RSS-enabled micro-blog with Twitter
• How to use Google calendar
• Twitter in plain English
• Social Bookmarking in plain English

So I’m going to talk a little more about the overall plan, expected plugin use, and managing some of the known hurdles.

The homepage:

In the last post, I mentioned my homepage issue. The current homepage is housed at www on a Windows box. I currently expect I’ll do a permanent redirect to the default WPMU blog for just the default.php page. One of the reasons is Featured Content Gallery. This plugin gives me an easy way to do something I’ve long been hounded for, linked images and movement, without Flash. I hate Flash. It’s deeply personal. I’ve tried to implement SmoothGallery, the script that spawned FCG, but it’s got javascript errors in IE7 and I just can’t get past it.

An issue I have with FCG and a WPMU homepage is that I’ll need the gallery to show images for and link to various places all over the collective University site. It appears that I’ve found an answer with Redirect, a WP plugin that simply redirects the user to a different URL based on the content of a custom field. This, plus an automatic post expiration plugin such as Post Expirator or Auto Delete Posts could go a long way toward filling my need and making the daily cleanup/maintenance fairly painless.

Calendaring:

I recently implemented Google Calendar campus wide. It’s been a positive experience, but getting upcoming events to display on plain php pages the way I want them has been a challenge. The RSS feeds can be questionable. Luckily, there are WP plugins that do great things with iCal feeds. Specifically, AmR iCal Events List appears to have promise. I’ll be able to widget an upcoming events feed onto the homepage and be done with it.

Additionally, since our Google Calendar setup has included a lot of separate calendars for different departments merged into various configurations, I’ll be able to use the plugin for many lovely department specific feeds. It also merges multiple iCal feeds…very handy indeed.

Misc:

• I’ll use one of a variety of RSS widgets to feed “news” & a text widget or two to manage static content. Site search will utilize our existing Google Custom Search and I’ll feed Google the new urls with a sitemap plugin.
• Moving the sites back onto the University network means I may actually be able to get the LDAP plugin working…wouldn’t that be a slice of awesome? Today, since we’re running separate WP installs, we’ve got separate logins for each.
• Universal header/footer plugins exist for WPMU that will alleviate the current php include thing I’m doing and allow me to manage the files within the admin AND use WP tags in them.
• I can have customized universal dashboards for all site admins. So, for example, I can push links to the video tutorials we’re working on directly to the people who need them.
• Universal update capability means no more 3 days of single install upgrading.

I’m working on 2 simultaneous project using WPMU. One is a BuddyPress implementation for the “university community” project. The other is using WPMU as CMS for an entire institution. This is what I’m going to briefly address here… I’ll also be documenting the process along the way.

Where we were:

When I took over 4 years ago the University web presence was 16k+ disjointed static pages using html “templates” with FrontPage as the software of choice. Various departmental staff were occasionally getting online and updating information. The result was a set of template files (images and all) for each department, broken links, and outdated Word and PDF documents where site managers had downloaded copies from another department into their site content rather than just pointing to the appropriate place. Though, in their defense, with every file being named XYZ-form-2005.ext it wouldn’t have mattered if they’d pointed to the right place, so what was the point? Oh yes, and until me there was NO dedicated web staff…nada.

From then until now:

There have been a couple of versions of things since then. I initially brought everything together using .asp includes for a quick and dirty unified template, installed a document repository to organize all of the .doc, .pdf, .xls, etc. documents together in one place, and took content control away from the departments. I needed to get a grasp on what was really out there, what was really needed, and do *something*  while I researched more long-term solutions.

As is usually the situation in reactive institutions like mine, something happened that spurred a change. We had an orientation program come into being that was going to require a LOT of site updates. I chose to put that site in WordPress so I could train the appropriate staff to make the updates and free myself from the day to day responsibility. It worked beautifully…and someone found out. Long story short, I’ve been putting new departmental site builds in WP for a year and it’s been very well accepted. Most of the departmental staff again responsible for their site content have been very happy, easily trained, and not required much additional hand-holding. I’ve done software updates and the occasional support call…not bad. I did this knowing it was an interim step and I was essentially putting our site content in an exportable format for whatever CMS we chose in the future.

The problems:

First, our internal systems weren’t WP friendly for a variety of reasons. We’re a Windows shop with limited resources, pretty crappy bandwidth and no real PHP/MySql expertise available to us. This led me to buy external hosting for testing purposes which ended up hosting the majority of our web presence when the WP wave hit. It wasn’t intended to go that way, but it did. Our IT dept. has been very gracious about it, but the director has always wanted these sites moved back on campus…and back onto the .edu.

Second, I’m running individual WP installs. When I started this WPMU wasn’t ready and couldn’t do what I needed it to do…or at least I wasn’t ready to figure it out completely.

Third, our .edu has to point to our primary Win server for a variety of reasons. There are still legacy .asp apps out there that serve a purpose, as well as a lot of /directories that can’t just disappear. Today the homepage and a few other key pages site on this machine, with links out to the rest of the site. IIS on this machine also does a whole lotta virtual directory redirecting.

The plan:

In the last couple of years significant upgrades have been made to our IT infrastructure. We’ve upgraded our bandwidth, bolstered IT staff, setup virtual servers, and generally improved our ability to adequately serve and support the site(s). Today we’re in process of setting up a Linux virtual server, MySql server, and a duplicate test space upon which to install, test, and manage WMPU as a full CMS for the University.

The install will be on a subdomain, web.saumag.edu, with each site on a directory, web.saumag.edu/communications. I’ve been struggling with the state of the homepage, as there are some things I could much more easily achieve with WP, but a Windows install isn’t really the best option.  I’m seriously thinking of making the primary WPMU blog the homepage, and just setting a permanent redirect on the Win box default.php page. This will only affect the “home” page while allowing the random .asp pages and faculty site directories to function normally.

Next step:

I expect I’ll be installing WPMU in the next week or so, as soon as I get the access and go-ahead from ITS. I’ll post when I know how that goes.