CSL Collaborative Workspace

Beta testing Open Atrium (on IIS6!) for intranet collaborative workspace. Here's the stock homepage. I'll give you more info/screenshots later. We're liking it so far!

Flow of Info Through Our Web2.0/Web Presence

"Scooping" myself

So I realized that I'm always breathless with anticipation & entirely too quiet about my big plans for web projects. And I realized that I do this despite my professed philosophy of openness and communication. Often, it's just that I'm too busy. Sometimes I'll admit that I'm also afraid that I might not be able to make the big project work, so I hesitate to mention it or to mention it until I have a stronger feel for how successful and/or rapid its implementation may be.

But I also recognize that as you decrease centralization of an organization's structure, you need to increase communication. That's the only way to keep folks working together as harmoniously as possible. That's a huge transition from a strictly hierarchical way of organizing people. Another key to a decentralized power structure is that everyone on the "team" is working toward the same goal. There's an implicit and explicit trust there. We're not decentralized, but we're transitioning to a much less centralized structure than we've ever been in before. It can be very empowering & productive. But a challenge... I can only imagine (no, I really can't) what it's like for my boss... at what point do you have to create boundaries & ensure that there are structures to keep folks working together? Fortunately, these questions are way above my level...

Anyhow, I've been violating my ideals by not at least mentioning some of the things I've been working on this year:

• put the Conservation Connection website live (using Drupal platform)
• fixing up the database-backed page that pulls in legislative histories & normalizing it so that there is an entry for each segment of committee testimony pages, so that when they are digitized, an URL can be assigned to each one (the database was created with all of the committees' pages in one big chunk of info in just 1 column, even when they were for different committees (e.g., Housing: 233-255, 1500-1501, 1700-1799; Public Safety: 511-525, 302, 677-680) )
  
• getting the WPA art project site live / ready for primetime (on customized Wordpress platform, using a mashup with a mysql database to list artworks from our database & with Flickr streams (as long as the folks uploading our Flickr photos tag the photos with the artists' name, our Wordpress pulls the photos with those tags into the biography page for each artist)
• updating the stylesheet for the cslib.org site & updating its homepage (rolled live end of August) for some usability improvements, added a few services for/by audience navigational pages
• getting the Web2.0 interest group going. It's almost intimidating to get all of that brainpower/firepower into the room & to empower them/unleash them! We've put together a fan page for our place of work, a Twitter stream, and the reference librarians have begun a live chat service. A woman who works in our digitization area & is a guru of scanning, GIS, and myriad technologies, as well as being a scholar in African-American history (she's going to school at one of the state universities right now), had the great idea to tweet sections of our Wyllys papers that refer to Connecticut's 17th-century witchcraft trials - one tweet every day for the month of October. It was awesome! Nicely done. Another Web2.0 group member who is perpetually in fast forward & is really good about advancing the organizational mission as much as possible at all times learned so much and did so much that she's become our FB fan page admin for us, effectively. I'd set up just a fairly straightforward page, with a couple of search boxes and a few RSS feeds, but she really refined everything, added so much, even insisted on getting our Meebo live chat with a reference librarian widget incorporated. I'd have given up on that one a lot quicker, if I'd even have thought of it in the first place! So my colleagues do rock. That's the upside.
  
  Then there is the hard work of trying to get multiple folks to share the responsibility of new services, while doing so in a way that is team-oriented & remembers the vision of the overall web presence. For example, reminding them not to skip the blog (that they also have authoring rights to) that is the authoritative news stream for the library (not to mention that it populates both our news page & our home page). For purposes of searching & coherence, I want everyone to think that the blog is the first stop for publicizing new services/projects from us. If they've set up the connection in Wordpress, moreover, posting to the blog will automatically tweet out for them and - without them taking any extra steps - anything that appears on our news blog feeds into the Facebook fan page (our blog is featured in the fan page's Notes, so automatically gets imported in). I should add that anytime our folks put a status update on the Facebook fan page, it tweets out to our Twitter stream (we've set up that interaction). I think everything's now all working/playing together well and soon we'll get everyone to remember to start at the blog in most cases, and work their way out.
  
  
• Finally, getting us ready to go with the Drupal migration (creating the presentation that I'll publicize on Slideshare as soon as I cite some of the diagrams I borrowed from various brilliant UX folks... even though w/o my narration, it won't be that exciting or obvious... I hope it won't anyway...); creating a collaborative workspace that we're beta-ing (I'll have to put the details/how tos on the blog, since I may be one of the only people whose had to try to get it to work on an IIS6 server... used FastCGI, what a challenge to get everything going w/o destroying the Mediawiki install... did I mention that we run a Mediawiki-based internal wiki for the reference librarians to share information to answer frequently asked questions) on OpenAtrium, a Drupal-based intranet product that we're having a lot of fun with; and trying to flesh out audiences, use cases, subject areas/categories, plus how to do the content migration teams...

Tomorrow AM, I'll show the reference folks how they may want to take advantage of Wordpress' categories so that we can broaden the scope of our news blog to produce topic-specific RSS feeds, such as genealogy. It'll start laying groundwork for moving to Drupal.

What a tangled web we weave: integrating the web presence

Back in March of last year - trying to explain the management issues that arise with increasing web presence compexity - I drew up a diagram of MPOW's online ecosystem. (See the diagram to the left). No longer 100% accurate (in fact, our web presence has gotten even more complex with the addition of an institutional Facebook fan page & Twitter stream), it nonetheless gives you a little taste of the components I take into account when imagining the next iteration of our website (and larger web presence). One of the ppl I follow on Twitter led me to this great post about "Untangling the Library Systems Environment" today.

As I try to create a presentation that I hope will explain to my colleagues why we're moving onto a Drupal-based site, one of the things that I keep envisioning is the ways in which it can help us to (if we implement it as successfully as I hope we will) integrate our online environment. We no longer want the end-user to make their way through the fragmented, incoherent experience that our disparate online systems create. We want our users to have a sense of our library (which they arrive at via our organization's website) as the place where they can find x, y, and z. We don't want them to have to think about the fact that x came from our catalog, y came from our digital collections, and z came from a database that we'd created. Yes, we want them to be able to track down items in our physical collection, to link to images and documents from our collection that have been digitized, and to find information from that database. But no, we don't want them to have to know what the back-end looks like in order to get what they want.

Collection Development & Cataloging - old skool?

Just a quick one since I have some "homework" to do for my Drupal Fundys class...

I've been taking a look at the Twitter streams for #il2009 & #libcamp09 (the unconference held in Monterey before Internet Librarians began - preconference for IL happens today, then we have a few days of Internet Librarians goodness to keep an eye on) & saw this gem from @RachelsVoice (retweeted from others) "RT @pjbent: RT @civillibrarian: "end user selected books circ six times more than staff selected books" (@sabram)! Wow. #il2009 #libcamp09"

Now last week I had a post-NELA supper with a couple of my fav (granted I have a lot of those) colleagues & one of them talked about an automated user-based collection development system that her consortium of academic libraries is starting up. I was so impressed. For the longest time, I've wondered why we don't just hand over the reins to the users when it comes to collection development (for the most part... granted, reference may require librarian / subject matter expertise as guidance). So I'm glad to hear that some libraries are finally doing this.

In a similar vein, don't forget that some of our leading edge public libraries now recognize that having staff members with "cataloging" expertise is no longer a requirement. With the many high-quality bib records out there, why do so many libraries seek out catalogers? There are institutions/organizations and contexts in which cataloging expertise is needed - but in many libraries, the highest and most pressing technical knowledge needs they have are related to computer and telecommunications technology. I know, I know - that scares librarians because it displaces a library-specific skillset with a more general skillset, but that's the reality today and the faster libraries get on-board with this reality, the less likely they are to disappear.

Your Web Presence: An Ecosystem

A successful web presence, in my mind, has a lot of aspects. It may be built of many small pieces, seemingly unrelated systems. But they must be pulled together and presented with some coherence born of user-centered design. The question you should be asking in building (or rebuilding) that web presence is: What are your users' current needs/wants/expectations and anticipated needs/wants/expectations?

I've been reading the title - Information Architecture - from the always-excellent O'Reilly series. Information architecture is an important topic these days. (A nice tutorial on designing/redesigning your website, the process of putting together an information architecture was published on Webmonkey last year.)

IA is a concept that librarians should feel especially comfortable with, since it relates to the organization of information (this definition from the Utah Education Network:

A description or design specification for how information should be treated and organized. In web design, the term describes the organization of online content into categories and the creation of an interface for displaying those categories.

Just as a house requires blueprints in order for construction to go well, a website needs information architecture for a library to build a coherent, easy-to-navigate site. But more than that - you have a whole web presence these days. Your web presence is no longer just a simple site, it's now an ecosystem.

Here's where it gets tricky - with Web2.0 tools, staff are empowered to create bits of what will eventually become a part of your library's web presence (and to do so very quickly and painlessly). This can be great, in many ways. Because web2.0 technology is so easy to use, however, people may not have given much thought to where their work fits into the larger vision of the website or organization. When people randomly build on lean-tos, suddenly the blueprint is no longer 100% accurate and the building itself may lose its integrity.

With Web2.0 options like wikis and blogs, we have to understand why staff members are tacking onto the web presence with third-party tools. Is it possible that some work needs to be done on the workflow of regular web content creation processes to make it easier for staff to publish using the website? Is the website the better vehicle for what they want to publish? Do they understand enough to use the appropriate tool for this issue they're working on? Were they solving a problem that another web content team or author was already working on addressing? Is everyone communicating and collaborating in the creation of aspects of the web presence? Does the "webmaster" know what staff members are planning when it comes to web efforts and can they envision how it would fit into the architecture of their web presence?

In all too many libraries, there is no dedicated "webmaster" or even "systems librarian" planning, building, maintaining, and upgrading the website or the content management system it may be built upon. In those libraries, it's possible that the only one who's creating aspects of the web presence on the fly is the person who also serves as webmaster part-time. If it's just a question of one web author, there will be no problem with coordination. That person is operating from their own unified vision of the organization's web presence. But when you're working in a larger organization, the rules change. The more decentralization there is, the more communication and collaboration there MUST be for your web presence to be successful.

On the flip side - serving as the dedicated webmaster for MPOW - I know that I don't always communicate as well as I should. I have a whole lot in my brain - a lot of plans, information architecture, and ideas - but it doesn't all always end up communicated to everyone who needs to know it. As a result, sometimes we get our signals crossed. Someone creates a bit of Web2.0 wonderfulness & then I try to figure out whether or not to wedge it into our existing web presence & if so, how. I hate the concept of saying "no" to a bit of content that someone has enthusiastically put together, but if it really doesn't fit or meet users' needs, as webmaster, my role is to serve the larger vision, not to serve the individual staff member/creator's need for that bit of Web2.0 wonderfulness to be publicized and congratulated. It's not about the needs of the librarians - it's about the needs of the users.

Usually, I rely on RSS to help me pull things together. I can include some portion of blog postings that are mounted on external servers by integrating them into the body of our web pages (I've used the old ByteScout ASP script & more often the RSS2js java script). But even this, if unplanned and unchecked long enough, can become unwieldy. Sometimes, subsections of MPOW don't want their stuff glommed into the larger news feed. But if they talk with me, I can help them to understand both the pros and cons of the situation & ways we might achieve what they're seeking. For example, it may just be a matter of adding in a tag to their blog postings on a specific topic. If they add such a tag, I can script on the RSS feed of posts with that tag.

All of the confusion that can arise, all of the integration issues that suddenly appear when staff become more Web2.0-literate remind us that the web presence can be a complex entity -- even an ecosystem -- unto itself. In order for the organization to achieve its larger goals & to appear coherent & memorable to end users, the organization needs a coordinator. That coordinator has to ensure the communication, collaboration, and management of the larger vision. They have to build the information architecture of the site and all of its components. They also have to pull together the many pieces of their web presence that are not built into the single system that serves the website itself. In addition, they have to view the bits of the web presence that are seen by patrons as being one and the same as the library's website (such as the catalog, commercial databases, blog(s), digital collections and so on).

Event-a-licious for Library2.0 Folks

Hi everyone, too busy to slow down & post properly, but LITA Forum begins in earnest today (preconference yesterday). Of course, I'm not there, but I'll be monitoring it from afar via the Twitter hashtag #litaforum. I'll try adding in a search link for this Twitter stream (otherwise, go to Twitter.com & seasrch on #litaforum).

Also, don't forget that NELA (New England Library Association Conference) is coming to Hartford the week after next (Oct. 18, 19, 20 in Hartford at our fancy new convention center, which is worth a view in and of itself (our new Science Center is open right next door)... other sites to see nearby include the lovely state Capitol building, the State Library/Supreme Court building across the way from it (not open to the public on Mondays, I'm afraid, but call ahead & we could probably find a way to let some librarians in!), the Wadsworth Atheneum (with world-class artwork from Dali, Monet, Connecticut impressionists, the Hudson River school of artists, and modern masters whose work I entirely do NOT understand), the Mark Twain House, the old State House, and the Harriet Beecher Stowe house... we also have some nice restaurants and bars downtown these days...)

There are others, too... the famous & wonderful Internet Librarians' Conference in Monterey - Oct. 26-28th. (no, not going to that one either... my credit cards are still stretched from last year's Computers In Libraries & traveling to DrupalCamp in Georgia). I'll watch that from afar via Twitter, etc., too.

Fortunately, WebJunction's been kind enough to offer some great webinars lately, for those of us for whom travel is unlikely. "Building a Digital Branch", with David Lee King was last week (a recent posting from him on connecting the physical library to the digital is worth viewing), then I watched part of the "Digital Reference Summit" this week. Oh, and an aside, David Lee King has a quick & interesting post on "What's a Content Curator?" Take a look if you get a chance...

DrupalCamp Atlanta

http://www.drupalcampatlanta.com/
See some of the presentations from the event on Slideshare
Just want to know what Drupal is? View this video or read about the Drupal web content management system at the Drupal.org site

I missed last February’s DrupalCamp in NYC, but we weren’t looking at Drupal with any certainty that we would migrate our web presence to that platform. Since then, we’ve decided to embark on such a migration.

Why? Because Drupal is modular, extensible, flexible, social, has a huge community of developers (increasingly, library-specific developers, a la John Blyberg, who developed the SOPAC module for Drupal) who share their work and allow others to build upon it. Plus, it’s free… well, free as far as the costs of software licensing go. The investment in Drupal is one of time and expertise. But the good news is that Drupal is a content management framework designed not only to grow a web site/system, but to grow expertise.

I think that’s what’s most remarkable about Drupal. Plenty of us starting off with Drupal find its eccentricities – how you have to learn to think to work with its back-end – a bit maddening. It isn’t the most intuitive of systems to begin working with. But what tool that offers sophistication and scaling really is? What is remarkable is how Drupal began by creating a community of developers and how it recruits new ones all the time -- teaching them, bringing them up through the ranks until there are more and more Drupal developers. Drupal allows many levels of mastery and encourages collaboration. It does so through its open, non-proprietary, and modular nature. And - the more skilled you get at working with Drupal, the better your Drupal system becomes. So, with Drupal, you’re growing a system while you grow a community of system developers who will build, maintain, and extend the system.

The importance of Drupal Users’ Groups, such as the one in Atlanta that hosted the DrupalCamp I attended this past Saturday, underscores the importance of community in the world of Drupal. I needed to get a jumpstart into Drupal development and learning from other Drupal users – of all levels – was the perfect place to start. It’s not only easier for me to learn from others face-to-face, but I find it reassuring. I see the brilliant Drupal developers & then realize that they are human, that they, too, began with the same basic questions and confusion. They, too, sought advice from others in the Drupal community and – in finding it – were able to grow their skills until they became the Drupal gurus they are today.

So, what did I learn? Well, I learned only what I was ready to absorb & at my level, perhaps, that isn’t too much. But the salient “aha”s for me included:

1. How to install CCK and other modules correctly, despite the fact that every time I’ve installed Drupal, the installation has seemed to lack the location I was supposed to use to house those modules (so, in fact, CCK and similar non-core modules belong in the sites/all folder, but under a modules subfolder, which doesn’t exist upon the installation of Drupal (or hasn’t existed the couple of times I’ve tried installing Drupal) – so you create a modules subfolder in the sites/all folder, then you put your new module, such as CCK under it. (and yes, CCK WILL show up as a module for you if you instead install CCK under the modules folder that isn’t under sites/all/ but then, when you upgrade your core Drupal code, these non-core modules will be deleted out… anything in sites/all/modules will not…so USE the sites/all-based modules folder!))
2. That I could use the Acquia release of Drupal (http://acquia.com/products-services/acquia-drupal) as a way of automatically having a number of extra modules and goodies that are proven to work and play well with one another installed along with the core module and/or that I could use the Acquia Drupal-Apache-Mysql-Php stack instead of the Bitnami one I’ve been using to have it all installed from one package, including the Acquia-added goodies (http://acquia.com/downloads)
3. That I’m not too low-level to participate in the Drupal community – everyone has to start somewhere & everyone plays a role – you matter to Drupal – participate! (But don’t worry if you happen to run across someone in the Drupal community who is socially backwards and behaves like a jerk… just ignore them, jerks are everywhere online, even among Drupalers…) – per Addison Berry (http://www.lullabot.com/about/addison-berry & her blog = http://rocktreesky.com/). Drupal is not run by a hierarchical organization, nor is the world of Drupal a meritocracy. Drupal is a “do-ocracy” instead. Just do it! Even if it’s not the best/perfect. The point is that you did it. (You will get better, but if you’ve done it, that alone gives you karma in the Drupal community. So that’s why developers at every level should participate in Drupal.)
4. That I should begin lurking in IRC chat (old skool!) - http://drupal.org/irc - and following the Issues queue - http://drupal.org/project/issues/drupal
5. We’ll have to watch the development of Drupal 7 to see if it’s worth implementing on 7 or 6, given that the code freeze has begun - http://drupal.org/node/578446 … the issue of whether or not to deploy on 7 is that some modules are still not upgraded to 6 yet and it will take a while for module updates to cascade… We’ll have to give this one some thought since we’re still planning our migration, rather than already having installed any code for our new site (see code freeze slides/plan (PDF) from DrupalCon at http://drupal.org/files/drupal-7-code-freeze-plan.pdf)
6. That many pros use third-party hosts, but that a hosting provider’s shared server could be problematic performance – at the very least, you’ll probably want a virtual private server… even better, a dedicated server
7. That speed can be an issue & that I could corrupt my db if I leave the PHP.INI memory setting too high (leading to the “white screen of death” related to PHP & MySQL) – that most use a PHP accelerator like APC - http://en.wikipedia.org/wiki/PHP_accelerator
8. That another performance issue can relate to too many files needing to be loaded for the end-user from far-off servers… that if you’re image/multimedia-file-heavy, you might want to have those resources/assets in the cloud (e.g., via AmazonS3, EC2, or Rackspace cloud servers) & only the php executables and core Drupal files on your primary web server … concept of CDN – Content Delivery Network popped up in a number of sessions - http://en.wikipedia.org/wiki/Content_delivery_network
9. That you should always (ASAP!) load the updates to any/all of your Drupal installation – both the core code & the modules – simply because of the security issues that continually come up… and that you can and should delete out install and other basic text files that have info that can help a hacker get into your site (these files are not needed after installation) – see http://drupal.org/node/244642
10. Drupal is starting to become “the thing” in libraries – seriously. I talked with one pro Drupal developer who’d been hired by a Midwestern library to do their website… another person is working with libraries in South Africa to deploy what sounds like a joint catalog
    
11. But that the larger pro web/Drupal developer community doesn’t always realize what’s going on in libraries… several people I spoke to who were working on library-related Drupal projects had not heard of John Blyberg’s SOPAC (the Social OPAC module) & was surprised to learn that a library developer had put together a module for Drupal…. Another developer hadn’t heard of LibraryThing… do we need to put out a primer for IT folks/general web developers to offer them insight into library system needs?
12. That maybe we need to recruit web developer pros into our field… or lure them back. What we need in libraries is a stronger crop of systems librarians/web developers to challenge all of us to higher levels… There are more high-level library-specific IT folks now than there has ever been in the field, I’d daresay. But we need even more. [As a not-so-tangential aside, why do so many libraries still insist on assuming that “technical services” (cataloging) people can automatically be turned into IT specialists? It seems like these days that it's more the exception than the rule that someone who is so good at defining differences and absolutes -- at following strict rulesets, such as AACR2 (http://en.wikipedia.org/wiki/AACR2) or even its upcoming replacement RDA (to be released, Nov. 2009?) (http://www.rda-jsc.org/rda.html) -- has enough of a holistic perspective to integrate disparate resources into a user-centered web presence. I’m not saying that it doesn’t happen, but I’m saying that the assumption that the progression would be from cataloger to IT specialist is no more valid than assuming that any other type of librarian could be automatically moved into a systems role.] But the bottom line is that library web developers should be at the same level as other web developers if we want libraries to keep up technologically. If we can’t do it ourselves, we should hire/recruit and yes, even outsource with web developers, as needed. One presenter at DrupalCamp was a library school student, but as enthusiastic a Drupal developer as she is, she doesn’t work in libraries right now (though I tried to convince her to do so!)…
13. The key factors why Drupal projects fail: (A) Not having gotten the goals out on the table / worked out clearly with key stakeholders early on… by goals, we don’t mean the system’s functional details, either, we mean, overall, what do we need and want the system to do. This early goal-setting was KEY to avoiding scope creep. Focusing on what they wanted to achieve out of the project; (B) no accountability / 3rd-party reporting structure/project manager is built into the project. Ongoing project audits make a difference. They keep projects from going off schedule/being abandoned. (C) [This one was the strongest correlation.] If more than 90% of the Drupal modules did not work as expected or failed to meet the users’ requirements, the projects ran into schedule problems and experienced scope creep. So this means that a lack of understanding of which modules are needed to get your plan to done, the project will be in trouble. This argues for a need for Drupal expertise/experience (or sharing with others who have Drupal expertise), as well as research on, and understanding of, the modules. (D) If the non-developers didn’t understand Drupal, the projects went off-track. Projects completed on-time, without scope creep are built by developers working with technical project managers and stakeholders who “get” Drupal. (E) Larger projects (more than 1,500 pages) were highly unlikely to meet schedule, cost, and performance objectives. (F) internally developed projects get higher marks than those done via third-party vendors, which the presenter thought must have been a biased result/anomaly, because it seemed counter-intuitive, so she only mentioned this finding in answering another question (I think she may be pursuing more research into this). The background of this preso (done by the person who was an MLS student) – by Julia Kulla-Mader – she’d surveyed 25+ Drupal content administrators, back-end administrators, back-end integrators, theme developers, and code developers. (see her preso on Slideshare at http://www.slideshare.net/JuliaKM/why-do-drupal-projects-fail-evaluating-success-factors-and-when-to-use-drupal). She identified the possible flaws in her study as: the survey being slightly biased in favor of programmers, that fewer than 30 people took the survey, that survey participants were self-selected, that there was a lack of historical data (were they talking about projects using Drupal v. 5 or 6, e.g.?), and that the questions were not required.
    She used several concepts to describe the success/failure of a project:
    (a) Was all or part of the initial project (as planned) abandoned? Using this criteria, 80% of projects failed… [whether or not it was simply a single module that they decided not to deploy or a larger problem wasn’t specified… in another preso about migrating an older website to Drupal, the developer said that the migration was not necessarily a good time to introduce new functionality to your website…] She did point out that almost everyone who took the survey completed at least part of the initial project plan – total abandonment rate was very low/nil [didn’t get an exact stat here]
    (b) Was the total cost of the project within what was outlined in the project’s budget? [60% were within budget]
    (c) Was the project on schedule? [close to 50% were completed on schedule]
    (d) Did new features make up less than 15% of the deployment? [hmmm… see my notes on point (a) …]
    In sum, the key things to ask yourself before starting a Drupal project are:
    - Can you devote the time to setting project goals? For each stakeholder, what would success look like to them?
    - Can you build accountability into your project? (auditing, project manager/accountability person who is not the designer or developer checking deliverables against milestones)
    - Do you have experience evaluating modules against user requirements?
    - Do non-developers on the project have Drupal experience (even before you come up with systems specifications)?
    - How big is the project?
    A final note, from another session on migrating a legacy website to Drupal – 2 important things you should do during your migration project:
    (1) Break down the task into small, manageable steps
    (2) Document what works along the way (crucial for Drupal!!!!)
    

BTW, My raw notes are in Google docs. If you want a copy, reply to this post & I’ll post/send/share them.

All this and I got a cool t-shirt, too ($ went to support Atlanta Drupal Users' Group)! I should also point out that this was what I consider to be a very well-run event. They held it on the lovely campus of Kennesaw State University. They had excellent signage & kept most sessions in the same building (the only hitches for me were some room issues / reassignments for sessions and the fact that I have NO sense of direction paired with a lack of post-lunch coffee… but I did find a vending machine that offered an espresso). Another sign the event was well-run - Dunkin Donuts coffee & donuts at the start of the session & nice box lunch – all complementary.

Corporate sponsors who helped to underwrite the camp included: Mediacurrent, Matrix, Acquia, MailChimp, AutoTrader.com, Volacci.com (Drupal Search Engine Marketing), A Small Orange (web hosting), Microsoft, and CMS Website Services