1. The backend — Clean WordPress install, giving our researchers the ability for our folks to post their own content. They should not have to fight with the system.
2. The audience — Donors are our most important audience in this round. We have to be able to tell our story quickly — who we are, what we’re good at, and what we’ve done — to prove that we’re a good investment.
3. Show off our stuff — We have a lot of great research assets: reports, evidence narratives, briefs, datasets. Make it easy to connect those to people and to project. And make it easy for folks to access them.

Originally number three was me thinking about the best place to store our pubs. Adding them as separate WordPress posts did not feel right. Not robust enough. All sitting in folders by year and month. No no no. Then I thought I’d put them on the iSchool server in a folder called resources. Nope. Too rudimentary. Then I remembered: You are not the only person to have had this problem. Get on google and poke around. Do your homework. What I found is good, really good.

I started by looking for something that would play nice with WordPress, which led me to Joss Winn’s Displaying a dynamic publications list from a repository on a staff profile page.

This in turn tipped me off to the whole world of cloud repositories. Of course. Duh! There are people out there and all they do is manage collections: repositories. Increasingly digital ones. So… from here I found EPrints. Created by the School of Electronics & Computer Science at the University of Southampton, it appears to be a wonderful open-source application to manage, specifically, open-access repositories. They  have a cloud version and a version you install on your own server. (Did I mention that open research is important to us? Yeah. Well it is. Remember that.) So they are cool three ways:

1. They’re a little consulting shop in an academic department. I’ve worked for two of those. We can be friends.
2. They’ve created an open-source app to manage information.
3. They’re promoting open access.

Plus they were super super well reviewed in this overview by Neil Godfrey and this survey by the Repositories Support Project, an initiative of the UK’s Joint Information Systems Committee (JISC) to support the development and growth of a national repositories network. I called EPrints and they were super nice. (JISC, by way, also has a project called Dura, to embed institutional deposit into researchers’ academic workflow. Cooooool…)

MIT’s DSpace also looks pretty cool. IDRC uses it to manage their digital library. I’ll look into them before deciding. But my view with this sort of thing, increasingly, is this: Don’t spend months trying to find the perfect tool. Find a good-enough tool with an import/export feature and get to work!

In February 2010, JISC and Eduserv held Repositories and the Cloud, an event to discuss the policy and technical issues associated with cloud computing and the delivery of repository services in UK universitites. Adrian Stephenson took rocking-good videos. Watch a few to get an sense of what’s going on in this space. (Also note how they used TwapperKeeper to archive and summarize event-related tweets. More on social reporting.)

Okay, so what’s exciting about this and why should you care if you’re in development?

There are several massive repositories now, mostly stovepiped by donor (topic for another post). This has to stop. The model now should be aggregation. The open data model serves us well here: Standards are important. Build systems that can talk to each other and share with each other. Imagine if we could aggregate knowledge assets from a whole host of places.

So why should you care if you’re a development research group or consulting firm?

Or any organization that produces a lot of publications or digital assets? Ohhhh, here’s where it gets really exciting. Some ideas:

• People profiles that automatically update when you post new content to the repository. This is good good news for all you academics out there with beautiful long publications list. You’ll never have to update it again!
• Project descriptions that automatically display related research/project outputs, generated based on fields you’ve defined (see TASCHA’s draft of research project chunks).
• Track downloads of each asset (example).
• RSS feeds to display on various parts of your site.
• RSS feed to share with anyone else, so they can display your latest resources.

See where I’m going with this? Will keep you posted.

Of course social reporters can use add the #PCamp09 tag to their tweets, which are aggregated on front page of their website.

Great use of social media and attention to virtual participants: livestreaming video, twitter, skype. And of course great topic:

Democracy is a game in which we all make the rules. How do we make this serious game more inclusive, more fair, and more fun? Participation Camp will provide the spark for an explosion of sharing, experimentation, and collaboration around this question. Participants may attend a wide range of physical and virtual presentations (or deliver one themselves), compete in a conference-wide participation game, or roll up their sleeves in a hands-on workshop.

Example: At the 2007 Telelcentre Leaders Forum, before the Global Knowledge Partnership meeting in Kuala Lumpur, my team of telecentre.org Community Facilitators worked for many hours after a long day of sessions to capture everything. They never complained but it was hard for them to both participate in the Forum and document it. I was also concerned that they were missing out on valuable networking time. After the event, I spent days pulling everything together into a report. Not something I would have been able to do if not my full-time job. Here’s a video of them. (Karim, I don’t know what you’re saying in Arabic but it better be nice!)

OK, enough ranting. (BTW telecentre.org has seriously grown its team of Community Facilitators. Yay!)

The solution? Social Reporting. A way to think ahead and be clear about who owns the the documentation and followup task and what they need to do, while at the same time distributing it to event participants already using social media. Think of it as a mix of better documentation and crowdsourcing.

Make it easy for folks to share — figure out the tag for your event beforehand and publicize it like crazy. You’d be amazed how much information you can get from aggregating microblogs — add in some good blogposts and photos and you’re in business.

I learned about Social Reporting practices from Dave Wilcox. He and Bev Trayner have done some great thinking on this. They’ve created a wiki and a  Social Reporting Toolkit — one of the best-written guides I’ve read. Ever. (Yes, I actually read the whole thing. Can’t wait to use it.) And I see looking through Bev’s site that she’s been busy creating another guide: Learning activities: some communication tools for communities of practice events. Makes me think of some of Bellanet‘s wonderful work.

Final note: As the person who has had to dig though many a folder of unmarked photos (although less now, thanks Flickr + Creative Commons), I think it is important to extend empathy forward. This is the core principle of knowledge sharing; if you don’t document then your event does not exist for those who were not able to attend. And no one can learn from you. So I encourage the people I work with to add basic information to their artifacts — the outputs of documentation — that will enable others to contribute to the conversation and create materials about similar topics or issues. Explaining who or what is in the picture, why it’s important, and giving a sense of the context helps others immensely. This also means reccomending that participants use a Creative Commons license so others can build on their work.