I’ve been thinkin’ about it, readin’ about it, and talkin’ about it for a while, as has Rosemary Arnesen, our esteemed and visionary Director of UMW Libraries. In the wake of launching our faculty aggregation interface, we are looking to expand faculty metadata to include their research publications. This is a technical challenge within the current paradigm of commercial journal publishing, but not insurmountable.
There is no one “feed” or aggregation of the multiplicity of journals to which one could type a faculty member’s name and get all of their publications. Current library subscriptions, and their online feeds, are all independent. Proprietary systems and faculty names, spellings, are not predictable across these systems. This necessitates what is referred to as a mediated or curated data layer: Faculty self-reporting of publications with links to their online versions.
As our librarian posited, some type of feed from our FAAR reports may serve nicely to begin to capture publications as they are reported on by faculty without adding yet ANOTHER interface that faculty need to enter to aggregate their data. As long as a feed exists, we can capture it in the faculty aggregation layer, and I am very excited to work towards this during the coming year.
The current academic research publishing environment is shifting under our feet, and it’s all to the better. I say this while being married to a neuroscientist who was published earlier this year in the Journal Nature, with all the prestige that comes with it. I am painfully (read PAINfully) aware of what it means to his career to have such a feather in his cap, and what he needed to do to get this done.
But I despair at a model where the blood, sweat, and tears of a person as earnest as my husband, and as our UMW faculty, is bought and sold in order to be legitimized by a commercial brand’s imprimatur. This is not the same conversation as “Wikipedia will solve everything” and I’m not talking about doing away with peer review — I’m talking about academics and their peers really owning the content and the conversation, not giving it all away to large publishing houses.
Conversations about open journals are happening more and more, and places like UMW are well-positioned for this conversation. On the library front, SUNY just cancelled its exorbitantly expensive subscription to the ACS journal archive in favor of aggregating from other less expensive sources. The costliness of access to commercial journals to resource-strapped libraries cannot be overstated. Open access journals are growing in number, and, should the quality of research therein meet consistent standards and rigor, these journals will pick up steam in terms of legitimacy, just as the commercial journals have.
I would love to see UMW, with its forward-thinking approach to online publishing, consider our own in-house peer-reviewed, open, online journal. We have the Aubade literary magazine and we should begin to consider aggregation and tagging there. “Metamorphosis” is a COPLAC journal of outstanding student research work, but why doesn’t UMW create its own flagship student research online journal as a virtual (and longer-term, cumulative) partner to the Student Research Creativity Day? As part of our digital initiatives, we have talked about an online repository. I believe this notion of a journal needs to be part and parcel of this conversation. Let’s not just deposit our work, let’s bring it to life with peer review, online commentary, student citations, the works.
I guess, all this is to say, isn’t the university itself, writ large, not a legitimizer of scholarly research in its own right?
(Still, it was WAY cool that my husband was the first neuroscientist at UVa to get published in the Journal Nature — part of me may always be old school). Notwithstanding, Curtiss Mayfield has something to say to you:
Our intrepid CIO, Justin Webb, has far too much common sense for his own good. He’ll never make it in this town.
Seriously, Justin and I were here together in 2008 for the coming of Sharepoint (before he was CIO). He and I slogged through the implementation of that baby over an 18-month period that felt like it would never end. It gave birth to a bouncing baby EagleNet.
Since November of 2009, EagleNet has been our University’s portal. “Portal” is one of those words that sounded SO sexy in 2003, but by the time we got to Sharepoint, we had seen the communications, training, and maintenance headaches that portals can bring. The dream of aggregating communications based on ERP data about a person’s role is a good one. The problem is, the companies that deal with data should be told to, “Drop the mouse. Put your hands in the air. Back away from the UI.” (and no one will get hurt).
Sharepoint is one of those nifty all-in-one tools that aggregates, collaborates, authenticates, productivity-ates, and gets-us-cute-prom-dates. It’s another of those motherships that promises all things wonderful.
The best thing about motherships is that they are, out of the box, pretty robust and sturdy. The trouble with motherships is that they are very, very hard to steer. That makes them GREAT for corporate environments with few differentiating factors within internal audiences. A single, sturdy, homely UI works okay in that mediocre kinda way when you stick with a vanilla installation and provision using the delivered tools.
But higher ed audiences are nothing if not idiosyncratic — not just within a University, but between universities. Student populations can be undergraduate, residential, international, non-traditional, in any number of major programs. And that is just one audience group. Throughout the year, each of these many audiences requires a clear way to get to information.
So the object was to use Sharepoint as a layer of targeted communications over the portal, essentially mimicking what we had with Luminis, providing single sign-on to our Banner SSB for students in the bargain. This involved a LOT of customization, including some pretty complicated code for maintaining a Banner session within the Sharepoint authentication scheme. The developer who did this (no longer with UMW) was truly a genius in getting this to work. But, not everyone has a genius on staff.
Bottom line: We twisted Sharepoint into a pretzel to make it do what it’s doing. And here’s what it’s doing:
Complicating getting directly to Banner SSB,
Delivering 3 widgets of targeted/authenticated information for the new incoming student, useful for 3 months out of the year, and too complicated to manage to allow for distributed content authorship, so content management stays within IT.
Delivering about 9 widgets of personalized information from Banner SSB to all audiences.
Hosting unused personal pages, called “MySites,” for all students, faculty, and staff.
Delivering a collection of about 80 or so collaboration sites, of which a handful are being used actively.
Serving as a pretty spiffy scalable reporting tools platform.
Other than the last two bullet points (in bold above), EagleNet doing very little for all the development and maintenance costs, not to mention the development and testing work involved every time Banner or Sharepoint is upgraded. Well, Banner SSB has an all new interface called Cascade, and Sharepoint is moving from 2007 to 2010. Time to commit to hiring more .NET programming skill for more customization and retooling of this enormously complicated environment for little UI benefit, or cut bait.
Then there is mobile. Delivering itty-bitty widgets of information just doesn’t cut it in a mobile UI. On mobile, you want to get the info, and get out, because, let’s face it, you’re driving.
Snide remarks aside, I would argue that this notion of having a web-based UI that provides pertinent GROUP and PERSONAL messages and data is a viable one. So, how to extricate that essentially sound idea from a UI that was developed in service to the infrastructure, rather than the user? I thought you’d NEVER ask.
Aggregate targeted web content from posts throughout the university Multi-network environment using RSS feeds, FeedWordPress, and our own Cross-Site Featured Posts plugin.
Deliver Banner Web Services (already doing that) to WordPress based on AD authentication (already doing that, too). That allows the viewing of targeted (WordPress aggregated) and personal (Banner Web Services) content upon login.
A flexible, accessible, responsive, mobile-friendly UI that leverages skills on staff AND within a broad WordPress community
No more Rube Goldberg authentication code in .NET that needs to be retooled every time Microsoft or Ellucian decides to improve on their products, dragging their clunky, afterthought UI’s along for the ride.
Banner screens break out from frames and use standard form layout, minimizing re-styling and customization.
IT concentrates on security, authentication, hosting and data delivery.
The Web team concentrates on aggregation and UI.
University Relations and the rest of the University continue to deliver content to their stakeholders through WordPress, as they are already.
Open standards, application-agnostic methods for authentication and session maintenance that could potentially apply to any number of apps and aggregation layers in the future.
Complex, compulsory, EagleNet portal layer is replaced by an opt-in Sharepoint installation that continues to support its core functionality: internal collaboration and reporting tools.
No more supporting thousands of abandoned, hard to manage “MySites”. UMW Blogs and a Domain of One’s Own are, after all, the most useful personal web publishing platforms we have in-house, and the internet is lousy with cheap or free personal web publishing environments that people can share with the WORLD, not just internally, as MySites do.
I know this is a lot to swallow in words. I have a way to illustrate these changes in simple pictures but, for now, I’ll leave it at the above. I’m pretty jazzed — it’s so nice to be around so long that you can break the stuff you helped to build, and build it better. Also nice to have Justin Webb as a CIO who is interested in solving problems, minimizing costs, being willing to kill a darling or two in support of the UMW mission in the bargain. Justin Webb (IT champion of the Domain of One’s Own) is an unsung hero — oh, and a Mary Washington alum, by the way.
The joy of being at UMW for so long is that knowledge of the institution becomes so granular, layered, and subtle, that you can begin to delve below the surface and pick apart how to make it all work. The UMW website has been an iterative laboratory of ideas for me, barring a 3 1/2-year period where a re-org moved the website to a different office. Each redesign I’ve embarked on– 2003, 2004, 2006, and 2010–has been done with more than the goal of a design facelift. At each stage, I’ve tried to join together messages about the University in a coherent whole, doing the best I can with the resources and tools available.
Barring 2004, which was largely a cosmetic and URL update for the purposes of our name change from “Mary Washington College” to “University of Mary Washington”, each re-design has included upgrades to authoring and site management tools to expand content management of the public site to areas deep within the institution. By 2007, when I handed the site over for maintenance to the new Webmaster, we had 210 web administrators on the academic and administrative sides with nearly ALL using a single look and feel in a single system. Not to brag, but, I don’t see a lot of Universities achieving that.
What seemed impressive to my contemporaries at other institutions was the consistent look and feel at all levels. But, in all honesty, although that was the agenda from the powers that be, it was not MY agenda. I wanted to build a culture of awareness for each user to feel like a responsible steward of public information given our role as a public institution. I evolved into this way of thinking after having the privilege of participating in interminable Thursday-morning DoIT meetings with the likes of Chip German, Gardner Campbell, Martha Burtis, and Jim Groom.
Enter UMW Blogs and WordPress, and a new way of web authoring at UMW, moved the “node” of information from the department to the person. What resulted was amazing open conversation on all the remarkable disciplines at this rich jewel of a liberal arts and science university. By 2008, the institution had the courage to link to UMW Blogs from its home page. But this was just dipping our toes in the water of truly exposing what was happening on our campus.
When I returned to my role as Webmaster, and later Director of Web Communications, in July 2010, the institution was once again poised for a redesign. But, redesign with all this rich groundwork already laid would have to reach to an even higher purpose: to turn an exposition of an IDEALIZED UMW to a public conversation with the REAL UMW.
The fact is, UMW Blogs is the most effective web tool for telling the world about what is really happening with teaching and learning here — our core mission. It’s more powerful than any beautiful and easy-to-navigate website can deliver. Through WordPress, FeedPress, and Banner web services, we are finally building a public web presence that is flexible and PERMEABLE. The goal: to expose real-time academic activity as THE driver to make anyone interested in coming to a place that graduates 21st century critical thinkers who can compete in the global information economy. Martha Burtis characterized this as (paraphrasing): “Not online learning, but learning online.”
Over the next few months, please look for the rollout of the following features on UMW public site to enable just that to begin earnest:
Banner Web Services Plugin:Through a core plugin, we are developing a way to consume real-time public data from our Banner systems. Banner data standards for departments, faculty, courses, and disciplines are essentially built into the taxonomy of the WordPress networks, enabling aggregation of information from many points to many different locations. Thanks to Enterprise Application Services for creating all of those nifty web services for us!
Faculty Professional Pages: Each faculty member will be able to write their own online bio (proofreading still available), publish and aggregate all of their blogs and social media to a single web page on the PUBLIC WEBSITE, and have their current courses and department affiliations, including any UMW Blogs related to current courses, automagically appear on the same page. A sample faculty member will look like this:
Majors, Minors, Courses of Study: Banner data enables aggregation of catalogue data, blogs, videos, news releases, faculty, and social bookmarks for each discipline. Each discipline’s feed is controlled by that department. This gives a real-time snapshot of what’s happening at UMW in that discipline right now, as the department wants to showcase how it teaches within the discipline. It also gives an apples-to-apples, in-depth look at all disciplines in one place, looking something like this:
FeedWordPress: With all of the above in place, DTLT will work in a standalone installation of FeedWordPress to curate, slice, dice and combine feeds for consumption anywhere on the UMW Multi-Network from UMW Blogs sites, and back.
University Taxonomy: We’ve played with this a bit, and have a version of it in place on the Document repository, but we have not institutionalized or developed a final UMW Taxonomy tool that all sites and blogs can use to categorize their content so that it can be aggregated with other content on the site. How this plays out under the hood is unknown. We will need faculty and staff input on what those taxonomies should be.
If you are still reading, I thank you for hanging in with me. This thinking began in 2008, and this actual development has been going on in our office for months now. Jim Groom’s post last week gave me the kick in the pants I needed to start writing about it in more concrete terms. He’s useful that way
Oh, and yes, Curtiss and I would be happy to put together developer and user documentation once the lion’s share of this work is complete. Curtiss Grymala has released all of his UMW plugins to the WordPress codex, and we thoroughly support the culture of open source development.
Faculty Academy, for those who did not take the time to go, was really exceptional this year. It’s grown so much more open and interesting in its development over the past decade, and the DTLT crew deserve so much credit. For two days, i was immersed in a group of people who are undaunted by doing things in a new way. There were no claims of “but you can’t do that in higher education.” The feeling is that everything is on the table, up for grabs, and everyone has a creative voice in the process. They even let me lead a couple of discussions, which shows how fast and loose they are playing it
The relative dearth of technology resources at UMW, compared with larger research institutions, is a double-edged sword. At a larger research institution with decentralized technology budgets and infrastructures, UMW would not have had to come up with UMW Blogs on a “sandbox” outsourced host. We would not have to develop an interactive map and mobile web presence using low-cost and free open source tools — we could have simply bought all of that, along with the vendor lockin that comes along with it.
This never-say-die attitude about the democratic nature of technology, the web, and now the physical world and “maker” culture, is at the heart of what it means to be at UMW. I left those two days reeling with ideas about how to do more with less, and how to help others do the same.
But the ultimate clash of cultures for me was my subsequent attendance at UVa’s final exercises on Sunday. It was not actual attendance because the crowd was so big I could not get a seat, and I saw it live streaming from a ballroom (when my kids were not dragging me to some open space to play lacrosse). Their speaker was Katie Couric, a UVa graduate. Her speech was not only sophomoric (talking about getting drunk as an undergrad and forgetting the tailgating parties, yuk, yuk), it was self-referential to the point of embarrassment. Katie, apparently, was a Delta Delta Delta, which I thought was Revenge of the Nerds, until I remembered that it was Lambda Lambda Lambda. The Deltas were in Animal House. UVa can afford a visit by a national TV celebrity reliving her sorority days with her fellow Delta Delta Delta sisters!
UMW, on the other hand, is not so fortunate. Not only does it eschew the “greek life,” but has to settle for speeches by non-tv-celebrity-visionaries like Guilia Forsythe, Grant Potter, and David Darts. I give you the following comparison, and leave you to parse the qualitative difference between the great minds and the great budgets:
After watching Jim Groom’s talk on DS106 and open education, I started to think about all the energy that went into re-thinking what is possible on umw.edu, and all the potential that we now have.
For now, lots of activity is swirling about responding to a stream of complaints, fixing bad links, improving server performance, making navigational adjustments for our internal users, getting folks used to “thinking” in WordPress, documentation, training: essentially housecleaning. These things are important. I’ve learned one thing in the past 11 years at UMW: As much as the institution may want the Web site to be primarily a marketing piece for external audiences, it has become so much more to our internal audiences, and we owe them basic functionality before we move on to the cooler things ahead. Balancing those two things is not a science, and involves a willingness to be flexible and to respond to user need, to keep a cool head, to admit mistakes, and sometimes to kill our darlings. There are a few darlings strewn alongside the road right now, and that’s to be expected.
Jim’s talk brought back to me many reasons why I wanted to do build the foundation of the new UMW Web site in the way we did it: No big corporate vendor-interloper, open source tools, working in ways that people already work and think, paying attention to the Web as an academic space, building a community of ideas. As with any iterative process such as this, spiraling back and forth between the initial idea and its execution, and you see that every decision that you’ve made actually potentiates the next decision, then you know you’re on to something. And complaints and fixes notwithstanding, we are onto something. So, what next?
So much is next that I get giddy just thinking about it. But I’m most excited about building a core piece of the Transparent University environment: showing the world what it is like be a part of the various disciplines at UMW.
Currently, as with most higher education web sites, we have kind of a dry list of academic disciplines that link to the various department sites. From an information perspective, it’s bare bones. It does not communicate a compelling argument for studying THAT discipline at THIS institution. If we are communicating that we are Great Minds, a list doesn’t cut it. We need something more. We need to expose our community of ideas, and invite participation.
The traditional student recruitment model on the Web involves a lot of showmanship: cool design, perhaps some video, twitter, facebook, maybe some student blogs, for the resource-rich, some interactive flashy stuff. The trouble is that this type of thing is largely expository rather than participatory. Playing with a canned “immersive experience” on your own is not quite the same as being in community. Enabling people to ask a question of the admissions office on facebook or twitter is a start. But, the activities and the flavor of the institution cannot be embodied within our admissions office alone, as amazing as those folks are. A simple list of faculty with their areas of expertise (the Media Resource Guide) is a great tool, but again it’s not compelling in and of itself.
We have an embarrassment of riches at UMW with regard to online, easily-accessible, and aggregation-ready academic content. UMW Blogs unchained the higher thinking of this institution from the shackles of the LMS and, on a minute-by-minute basis, exposes our student and faculty activity to the world. What UMW.EDU needs is a way to aggregate all that good stuff, along with data from the Media Resource Guide, maybe some Banner data on courses, catalog information, social media, and all that stuff into a meaningful environment that fosters scholarly discussion and invites the world — of which the prospective student is a part — into the conversation.
Over the years, we have talked about this notion of allowing the prospective student into the UMW experience prior to their actually plunking down the deposit. Our technology, heavily dependent on student system data, was always a stumbling block: Students cannot have access to the portal or any online system until they are in the student system, which doesn’t happen until the deposit is paid. So, if we are going to rely on our systems to allow students into the UMW experience as a recruiting or “yield” tool, it can’t get there from here.
But if there’s anything that UMW Blogs has taught us is that we don’t need to let a little thing like an ERP system stand in the way of letting the world know how cool it is to study with the Great Minds at UMW. We have enough out there right now that we can shape its delivery in such a way that, for instance, a student in New Jersey who is really interested in communications just may join DS106 because they saw it in the mashup “Communications” site on umw.edu. That kind of magical connection can’t be bottled in a costly flash application — it’s real connection with real people where the technology takes a back seat in service to human need, not the other way around.
The branding effort for the new Web site, with all the fancy graphics, was, to me, only a start. The real UMW experience is not one of unlimited resources, a pristine campus, or dazzling residence halls. It’s the people, the Great Minds, students included. Who would not want to belong to this club? It’s where all the cool kids go.