I made a feeble joke over at Walt’s blog to the effect that he must have been extra hard-up for material for this issue of Cites and Insights (PDF). CavLec eats a shocking proportion of the pagecount.
Without opining as to the veracity, insight, or other value of my blogging, it might be worthwhile to think for a moment about how a one-horse blog by an otherwise undistinguished repository-rat (think about that, think hard; in what way have I distinguished myself in my profession other than CavLec?) became one of the open web’s top voices on institutional repositories. I don’t think it’s as simple as “Walt and I are friends,” though I won’t deny that plays a role.
Point one, mine is just about the only voice like mine out here. Stevan Harnad does not count, as he is not running one of these things. Ditto Peter Suber. Ditto Jan Velterop, who comes at open access from a different angle entirely. There’s Les Carr, but that only happened recently. There was almost Leslie Johnston, but bless her, she got out of this field while the getting was good.
We’re not talking. We’re not organizing. (The OA publishers are, but we’re not.) Even those of us who are talking are talking hardly more than happytalk. I don’t know how much more clear I can possibly make it: green open access as she is practiced (rather than merely opined about) has a severe morale problem. When I asked NISO to make me proud of what I do, I wasn’t kidding.
A talk I had with a SLIS professor and a doctoral candidate the other week brought home even more strongly something I point out in Roach Motel: repository labor is invisible. Just ten minutes or less per article, chortle the archievangelists; the software is free and easy to set up and Just Runs, and that’s all there is to it!
Yeah. What am I here for, again? But at least it helps explain the dearth of ratly voices. Why would we think anyone would listen?
There’s obvious rhetorical use to making these claims about institutional repositories. They just happen to be claims that devalue me and all my analogues at other institutions. This doesn’t seem to bother the archievangelists and other Big Thinkers much; in fact, some of them are perfectly happy to do explicit devaluing themselves (see Roach Motel for a couple of examples), which has led to certain plaints of mine. Yet another explanation for the dearth of ratly voices. Why do I want to talk to people who despise me? Cui bono?
Certain types of labor in this field are even more invisible than deposit labor. Systems administration (”it just runs!”) and design labor, certainly. Rights-clearance labor, which is picky, demanding work notable for its total lack of clarity. Consider also that there are two or three types of it: clearing rights from faculty members for mediated deposit, clearing rights from publishers, and explaining the whole Creative Commons thing. I have yet to meet a faculty member who intuitively understands that the license is an agreement between faculty member and repository/institution, while Creative Commons is an agreement offered by the faculty member to the general public. “Why do I have to sign the license if I put a CC license on it?” I get that a lot.
Labor theorists should be having a field day with this. We, the open-access movement, demanded free labor from faculty, on the weak excuse that it wasn’t much free labor. They didn’t pony up. When they didn’t, we lashed together some rationalizations for why they should, ranging from “citation impact” to various variations on “productivity measurement.” They were unimpressed. At that point, our reactions diverged. Some of us, the Ohio States and Oregons of the world, decided we’d have to put in the work ourselves: mediated deposit. The rest of us figured that the labor could stay invisible if it became forced instead of voluntary labor: mandates. The whole bit about mandates being forced labor, and not a repo-rat in existence in a position to force labor out of faculty, never seemed to occur to anyone. (Except me. But I was trained by Greg Downey.)
The Harvard decision, looked at in this light, leaves a troubling question open: What’s going to happen when Harvard arts and sciences faculty realize they’ve imposed a labor requirement on themselves? I’m not at all sure they have realized that, and some of the “permission mandate” talk being thrown around muddies the waters further. For the record, the Harvard policy is not just a permission mandate; it requires that faculty get their articles to the Provost’s office. Somehow. We don’t know anything about the “how” yet… but to my mind, that may be the key factor in the policy’s success or failure. If faculty think they’re putting too much work into this—worse, if they’re right—I wouldn’t give the policy survival odds past two years.
Do I need to say that slapping up a DSpace install and requiring faculty to use it would be the death-knell for this policy? I hope not. I expect I do need to say it, though. Harvard faculty didn’t sign on to do five screens of metadata, an upload, and a click-through license per publication, folks. That’s work, that is. The simple fact is that DSpace has heretofore been extraordinarily disrespectful of its users’ time: browsers, searchers, depositors, community and collection maintainers, all the way up to system administrators. I plan to defend this assertion in a later posting, but for now, take my word for it, and understand that it becomes a serious backlash-inducer in a forced-labor context.
Verily I say unto you: Harvard’s Provost’s office, library, and IT division had better be hard at work on citation-retrieval automation, automation that involves as little faculty labor as possible. And verily I say unto anyone who wants a mandate like Harvard’s that they’d better do likewise. And verily I say unto everyone that we (as a field) are so far from being adequately automated as to scare me.
Labor. Follow the labor, and you see the cracks in the green-open-access system. Follow the silence, the lack of voice, and you see how those cracks have been allowed to happen—and grow.