As we looked at how we would upgrade all of our Drupal 6 sites to Drupal 7 we realized we had a big problem. Big as in over a thousand individual Drupal sites. We have become the victim of our own success in that we made it too easy to create new Drupal sites whenever we received a request, without first asking if a new site was really necessary. Drupal itself scales very well. It can handle much bigger sites than we currently have. By creating so many smaller sites we were actually making it harder for people to get around on our pages because larger sites became fragmented with no global navigation between the various units. It also made it harder for people to share data across sites, which caused unnecessary duplication of data input. Finally it created a lot of administrative overhead for CWS to keep this many sites upgraded.

We made it a strategic direction for Drupal 7 to begin consolidating as many small sites into their parent units as possible. We knew the first issue we would have to face is how to divide up the authoring responsibilities while maintaining ownership for different parts of a site. It turns out one of the reasons we currently have so many sites is because different people are responsible for content creation and wanted to make sure other people would not be able to modify their work. While this problem could easily be solved by just getting some agreements between the various authors on a larger site, we wanted to be able to assure people that we could prevent this possibility through Drupal permissions. We also knew that people wanted the ability for their sites to have some distinctiveness. While all of our Drupal sites adhere to the branding guidelines set forth by Web Communications, there is still room for sites to provide certain characteristics unique to their department or unit. We set out to find a solution for this.

What we came up with is a Drupal module called “Organic Groups”. The organic part does not mean that the groups were grown with abundant amounts of compost, but rather that they are flexible enough so that groups can be configured in a variety of different ways. For example we knew that colleges would need to build groups for their schools, departments, and programs whereas administrative sites would have a variety of working units that will need groups. After some testing we were confident that the Organic Groups module was going to suit our needs and so we started the work of communicating with people about our plan, and get some sites on board.

Central Web Services is a devision of Media Services which is in turn part of Information Services. There are a number of other units under IS including Enterprise Computing Services, Network Servies, and Technology Support services. When we began the task of updating the IS site using Drupal 7 it was agreed that we would consolidate a number of separate websites into the IS site using Organic Groups. The IS site is organized around the services that we provide. Each service is a group. Each group is also part of a service category. We are still in the process of converting all of this to Organic Groups but it looks like its going to work very well.

On the academic side of things we also have been working with the College of Liberal Arts to upgrade and consolidate their sites. We currently have the parent college site in Drupal 7 and are working with them to migrate the departments one a time from the old Drupal 6 sites. For a college the groups map nicely to departments which group into schools. Each department can have it’s own set of rotating features, highlights, directory listing etc. The department and school name also show up as the site name along with the college. Departments can have their own content editors, or and editor can work for several departments. There can also be college wide editors who can help with all of the departments if that is the way they want it.

Department name becomes the main site name, while the College and School names are combined above, with each linking to its respective front page.

Once we have completed CLA and IS we will begin working with other departments to consolidate and upgrade sites to Drupal 7 at an accelerated pace. The end result will be better websites for everybody.

It all started with a simple question, “Can CWS help us build a website that our student body can use to vote with in our April elections?”

The question, posed by ASOSU Organizing Coordinator, Drew Desilet, came to CWS in mid-February.  “When it came time to look at building or buying a new voting system for the student government elections, it was clear we had two options. We could choose to buy an outside product that came pre-made to someone else’s standards and needs, or we could work with our own CWS partners on campus to build us something to suit our needs.” he explains.

It should be clearly understood that the delivery of a complex, finished website or web application within a two-month timespan is a mighty tall order.  Additionally, there were a few tricky specifications that the site needed to meet, one of which includes the ability to limit the voting population to a specific segment of the OSU community, namely, Corvallis campus students.

Ultimately, the answer given to ASOSU was “Yes, we can.”

It did take a few extraordinary elements to get it up and running on such a short time-line, though:

• Great customers who provided exceptionally clear specifications
• A rockstar programmer who didn’t miss a step from the beginning to the end of the project
• A diligent project manager who smoothly coordinated all those extra things that threaten to derail a web-development project
• The OSU Drupal profile, combined with the Election module, a special contributed module that can be found at drupal.org

“We’re very pleased with the way this project played out.” states Jean Waters, CWS project manager.  “Using the Election module really helped us get this project up and out in such a short time.  In fact, there are still some really nice features that came with it that we haven’t even had a chance to fully examine yet.”

The Election module is based on a new Drupal 7 concept known as “Entity”.  This is still a fairly new concept to the Drupal team here at CWS, but team member Ricky Middaugh was up to the task. “It was a unique challenge, having to work on something in Drupal that I didn’t know a lot about.” comments Middaugh.  “But I’m really pleased that we were able to provide something useful to OSU.”

And the ASOSU provisioned gift just keeps on giving, explains Jos Accapadi, Associate Director of CWS. “Thanks to ASOSU’s willingness to experiment with us, the groundwork has been done, and now we’ll be able to quickly spin up sites for other political organizations here on campus.”

Desilet agrees. “We’re already working with CWS to make system improvements for future years – mobile capability, streamlined candidate entry, candidate profile pages, and a few other minor changes – the voting system has worked out very well for our needs in the ASOSU, and it’s our hope and plan to continue using it for years to come. It’s a system other groups on the OSU campus, or really even the entire Drupal user base, can use for a voting system in the future. It would be nice to see this used across the university for any type of voting, and make it as common to ONID users as BlackBoard is now, or Gmail is to come.”

The new voting site has already passed the Primary election test, during the week of April 9th – 12th.  “So far we’ve had 2,118 voters run through the system without any hiccups of which to speak. Modifications for us between our first Primary election and our General election were minor, and largely administrative based. Therefore the tool the students will use will look and feel the same as the first time they used it just weeks before, however it will work even better for us as election administrators.” says Desilet.

The site will be ready for use for the General election, starting Sunday, April 21st, at 10 p.m. and running through April 26th.  Voting will be open to Corvallis campus students.  To get there, just go to http://asosu.oregonstate.edu/elections and click the big vote button.

So let’s talk Drupal 7, and some bits and bytes about Drupal in general.  Central Web Services maintains a central Drupal installation.  Like any piece of software, it has multiple versions.  Drupal 5, 6, 7, and 8 which is in development.  The CWS stable version is Drupal 6.  Drupal 5 is no longer supported.  Right now we are getting numerous requests for Drupal 7.

We want to let you all know that we are actively working to get Drupal 7 tested, documented, and functional for the needs of OSU.  Well, why can’t I just get it now, it’s just a download, you ask?  The answer is, while if you were hosting on your own ISP this would be the case, the OSU infrastructure is such that we have to ensure security, reliability as well as integrations with other solutions, such as authentication, themes and modules in use by OSU CWS Drupal sites.  We have a number of concurrent activities happening to make progress toward rolling this out for the University, including actively working on the theme necessary for Drupal 7 (yes we have to rewrite the theme to work for new Drupal versions).  This is in partnership with the rock-star team over in Web Communications.

Now more importantly, what we are trying to do with Drupal 7 is reduce our site footprint and number of individual sites.  Can you believe we have over 400 sites?  That becomes a maintenance and support headache.  With Drupal 7, there will be a new feature called Organic Groups.  This will allow us to have a smaller subset of sites, and areas and departments within the same site but still allow the finer grained control that some of you desire.  With Organic Groups, you will be able to take control of the portion of the site that is your relevant content, and have control so others cannot access that portion of the site as a Drupal administrator to modify something in error.  This is where we want to go and what makes sense for Oregon State University.

So when will this be done?  With Organic Groups, we are in the pilot stage with Information Services, and then we are going to ensure we have it done right by piloting the College of Liberal Arts.  Doing this we will ensure we understand the technology well enough to teach, document, and support it going forward so people are not left out on their own to figure things out.

Individual main colleges in working with Web Communications can look at Drupal 7 with the Doug Fir Theme (the theme that we have available for Drupal 7), and then incorporate changes for Organic Groups as we roll that out.  Science and Liberal Arts main college sites are already in Drupal 7.

Departments however, we will not be rolling out with Drupal 7 at this time, as they are to be incorporated into Organic Groups, working with your colleges, once we roll out Organic Groups.

For those sites that are in Drupal 6 and want to look like the main college sites that are using Drupal 7 Doug Fir, we are working on a version of Doug Fir for Drupal 6.

What is Doug Fir?  So besides being an evergreen confier species, Doug Fir is an OSU responsive Drupal theme.  This means that the site resizes depending on the device that you are on.  Liberal Arts is a good site to see using this theme.

For us it is imperative that we do this right and do not add to the overhead and support it would take to enable OSU.  This is why you might hear us say that we are not providing Drupal 7 to individual sites at this time.

Our rough timeline as of now is:

• Spring and Summer to test and roll out Organic Groups.
• Winter:  Migrate Drupal 6 sites to Drupal 7
• 2014 Drupal 6 moves to maintenance fixes only
• 2015 End of Life (EOL) Drupal 6

With all of this we are re-architecting the infrastructure, and then we will have Drupal 8 on the Horizon.

We hope this information helps you to be aware of the progress we are making.