Archive for September, 2006

29 Septembris 2006

Metadata mismatches

Well, DSpace has a gizmo that creates SFX links, but it’s not very elaborate, and it’s (duh) SFX-specific. So I built a more general OpenURL crosswalk. My test server now has what look to be pretty respectable COinS, but I’m having to trust other people to tell me if they’re really working correctly.

Somebody tell me when this “human vs. corporate author” thing got into the bibliographic mix, and why, because it is a pain in the posterior. OpenURL distinguishes them (au vs. corpau); Dublin Core (at least as it is implemented in DSpace) doesn’t.

I can imagine a heuristic that would mostly work. If it’s got a single comma in it, one that does not precede an abbreviation, it’s probably human. If it doesn’t have a comma, but it’s only one word long, it’s probably human (even one-word company names usually have an “Inc.” or something after them). Otherwise, it’s probably corporate.

Honestly? I wouldn’t have much confidence in that. Too many counter cases. As it is, though, all the corporate authors in DSpace (got govdocs? I do) are going to have to be erroneously coded as human authors.

Somebody tell me what the practical use of this distinction is, because right now I’m really not seeing it. “But OPACs do it” is bzzzt! not a good answer. Neither is “because MARC puts them in different fields/subfields.” Tell. Me. Why.

Grrrr. It has not been a good day for code.

28 Septembris 2006

The next DSpace hack

For extremely convoluted reasons having to do in part with this, I’m trying to figure out how to get DSpace to emit an OpenURL. It doesn’t look impossibly hard to accomplish (even for me), but if anyone’s done it already (even in another language than Java; I could use a sense of the correct DC-OpenURL crosswalk), I’m always happy to write less code.

Just sayin’, LazyWeb.

In passing, OpenURL would be a lot cooler if it had a lot more possible values for rft_genre. I’m surprised they missed that. It’s not like cataloguers and other metadata people only deal with books and articles!

27 Septembris 2006

All sysadminly

Today at work I upgraded Postgres to latest-stable, reinstalled DSpace from scratch, tested and resubmitted my patch for author/subject browsing, and tracked down a really amazingly obscure DSpace bug that had kept the test install from accepting any new items. (If you’re that interested? This is what I found out, and yes, I’ll probably fix it; it’s not a complicated bug, just very very obscure.)

JDBC is feeding me a lot of “LOG: unexpected EOF on client connection” messages, but since they don’t seem to do any actual harm, I’m not panicking about them. (But if anyone knows why that’s happening…)

I feel just appallingly sysadminly and stuff.

Other DSpace hackers

Since I get a fair amount of email whenever I post a DSpace hack, I do want to point out that I’m not the only DSpace hacker blogger in existence.

Terry’s Worklog has been posting some highly nifty DSpace hacks recently, and Ross Singer has also said a word or two.

Both of them are way older hands at this hacking thing than I am, and I want to see some of Terry’s experiments in particular make it back into DSpace proper.

26 Septembris 2006

Bullet to the electronic brain

My poor test install of DSpace never did act quite right after I messed up its database with the 1.4 upgrade, and today it just seized up and broke right down.

Given how much and how often I abused it, I’m surprised it lasted over a year. First thing I did on the job was installing DSpace on that server.

Eh, well, time for a fresh start. I’ve asked if I can upgrade Postgres while I’m at it.

At Tim Donohue’s suggestion, I’m working on an improvement for this hack that takes into account the configuration option for defining author and subject fields. I have the alteration done, but I don’t dare test it on the production server, and I can’t test it on the test server until it has a DSpace installation that works.

So, yeah, that new patch may be a couple days. Nobody was in a super hurry anyway, I’m sure.

25 Septembris 2006

A peek at Zotero

“So I noticed that Dan Cohen has a GMU email address,” a librarian friend of mine IMed me last week. “Know anything about Zotero?”

If you ask me, Zotero is the measure of how badly EndNote and RefWorks have failed the market. I’ve tried to use RefWorks. It’s a disaster. I tried to use EndNote lo these many years ago, and couldn’t get it so much as running.

By serendipity I had a chance to sit in on a Zotero demo five or six weeks ago. By the time Dan was done showing it off, my only question was “When can I have this, please?”

It’s not perfect. But it’s leaps and bounds better than RefWorks, I’ll tell you that. And it’s better than CiteULike, which I also tried to use and gave up on because entering citations was such a chore. And for its purpose, it’s also better than del.icio.us, which I use for some stuff I get via library databases for lack of a better way to keep track of them. (Zotero does tagging, and Zotero does storage. The thing is, Zotero does quite a bit more than that. del.icio.us doesn’t.)

For once, the hype isn’t overhyped. Zotero is a genuinely cool tool, built by a group of wicked-smart, frighteningly energetic people. Speaking of which, they’re hiring. I recommend them to job-seekers without hesitation.

Unyielding opposition?

The respectable T. Scott wishes librarians (among other OA advocates) would stop hitting out at scholarly societies:

Finally, I believe that the open access partisans, along with many of my librarian colleagues, have made a serious tactical mistake in placing ourselves in such unyielding opposition to the scientific societies. Those societies that have maintained their publishing programs as low-cost independent entities should be applauded by librarians, even when we disagree on the open access issues. The day that Marty Frank sells the APS publishing program to Elsevier because he doesn’t think he can successfully keep it alive on its own anymore is a day when we all lose.

I want to take this piece by piece.

To begin with, I don’t know many librarians who have expressed a specific stance about all scholarly societies, and especially not the subgroup of societies described above. In fact, I don’t know any; I’d appreciate some pointers. When I hit out at publishers on CavLec, for example, I typically use the coinage “Elseviley Verlag,” an amalgamation of the for-profit, non-scholarly-society publishers Elsevier, Wiley & Sons, and Springer Verlag. That coinage specifically excludes societies going it alone.

That said, I’m honestly hard-pressed to say that academic librarians as a whole should be well-disposed to scholarly societies as a whole. Scientific societies in particular have squandered a lot of library goodwill by roundly ignoring thirty years or more of the serials crisis. If they now want libraries to take their worries about open access seriously, they have some ground to make up.

Elseviley Verlag didn’t corner the journal market by building it. Elseviley Verlag cornered the journal market because a lot of societies sold out to them. They either didn’t notice or didn’t care that they were putting libraries over a barrel in the process. So (to be blunt and callous about it, more callous than I actually am) we should care that open access is putting them over a barrel why, exactly?

Moreover, when scholarly societies still in possession of publishing arms range themselves against FRPAA and other open-access initiatives, they’re getting in bed with Elsevier’s lobbyists as well as certain dubious sockpuppets. Color me unimpressed, especially since Elseviley Verlag’s Big Deal tactics have been responsible for squeezing society publishers as well as libraries out of plenty of money. Lie down with dogs…

I may be alone in this, but I’m also irked by one specific phrase I see in scholarly publishers’ contributions to the open-access debate: “subscription-funded activities.” I’ll make my stance as clear as I know how: libraries are not responsible for supporting society activities unrelated to the scholarly literature. Too many societies are treating subscription revenue not as fee-for-service, but as an entitlement. It’s not. If libraries can get the scholarly literature properly managed and disseminated in a more cost-effective fashion than the current system, we are right to pursue that; that’s our mission. I am entirely unmoved when I see societies getting upset about their “other subscription-funded activities.” Their other subscription-funded activities are fundamentally not my problem; nor is it my problem that societies placed all their financial eggs in the subscription basket.

If my stance, in T. Scott’s phrase, amounts to “placing [myself] in unyielding opposition to the scientific societies,” so be it. I don’t think it is; I think it no more than a reality check.

If scholarly societies can look beyond the actual cash libraries provide them, though, I think they will find that libraries have a lot of in-kind support to offer, and I’m saddened not to see that entering the discussion. A society that partners with a library to digitize and preserve back issues of its journal will likely require considerably less revenue to fund the digitization, and can offload preservation responsibilities entirely. A society that lets a library host its e-journal—current issues, back issues, any issues—may see a lot of its revenue needs associated with that journal fade into thin air. This is not pie-in-the-sky posturing. It’s possible now; several libraries are ready to take journals on board, and several larger libraries have digitization or publishing-services arms. So why aren’t societies beating down our doors? Why would the APS even consider selling to Elsevier, when it could partner with a library?

(In passing, much current discussion about “publishing cooperatives” bypasses libraries entirely. It’s stupid to overlook us, stupid to think of us merely as sources of cash. Academic libraries have all kinds of experience in the digital realm. We know how publishing works, too—admittedly, some of us more than others. We don’t just have money; we have infrastructure and expertise that should be factored into the equation. For more from me along these lines, wait for Rachel Singer Gordon’s upcoming essay collection Information Tomorrow.)

Finally, I think there’s a straw man lurking as regards scholarly societies that have not yet sold out, and still provide their wares at reasonable prices. They’re not the problem and never were. Nor, I think, are librarians in general averse to subscribing to their journals. To them I say: the open-access movement is not about you right now, so don’t panic. In the short- to medium-term, I honestly don’t care whether they go gold-OA or not.

I do care—I care a lot—when leaders of these societies oppose FRPAA, spread FUD and outright lies about open access (a quick skim of Open Access News provides quite a few examples of this), refuse to promote green-road OA to their memberships, ignore libraries and library concerns, and—worst of all—refuse to realize that letting open access take Elseviley Verlag down a peg or two is probably in their best interest, since Elseviley Verlag is substantially why libraries have had to cancel their subscriptions. There, if you will, is a “serious tactical mistake,” and not by libraries.

When the FUD stops, and when societies are ready to talk seriously to libraries about what we can offer besides wagonloads of cash, then I will be much readier to help societies with their legitimate concerns about the transition to open access.

21 Septembris 2006

Super-aquatic perambulation

I wrote a little squib on TechEssence the other day about the hiring of systems librarians. Of course I tossed in a bit about laundry-list job descriptions.

Check this one out. Just in case anybody thinks I make this stuff up…

My guess is they had a real powerhouse in that position before. That’s great and fine and wonderful. But lightning tends not to strike twice. “The search has been extended,” said the listserv email containing this posting. Gee, I wonder why.

Librarians rock, but we’re not superhuman.

20 Septembris 2006

Chill, people

Honest to Pete, you’d think a remedial-Java programming assignment was the end of the world, the way some of my classmates treat it.

Do I need to manage my buffer size to avoid the input file overflowing memory, asked somebody. Yeah, like the professor has time to sit there cackling at the carnage while twenty-odd student programs bring the JVM crashing down one after another. Puh-leeze. (And what is a guy who worries about buffer overflows doing in remedial Java, anyway?)

Then later they jawboned her into letting punctuation as well as whitespace be word delimiters. By that time I’d already turned my assignment in. Did I redo it? Did I hell. Sure, I could have. I have better things to do with my time, thanks.

Yesterday’s pop quiz was an exercise in how often we could be tripped up by sneaky little “features” of Java. I got all but one; not too shabby. We discussed Big-O algorithm analysis, which is conceptually rather nifty, but whose details (ugh, sigma notation, shoot me now) lead me to believe that a lot of “rigorous” software analysis boils down to not much more than the traditional Scientific Wild-Ass Guess.

There’s a guy in the class who will not stop staring at me. It’s not that I’m the only one with girl-cooties, either; there’s six other women in the room, not including the professor. Nor is it my stunning animal magnetism. I don’t have any. I’m the oldest and fattest woman in the room, and the homeliest to boot.

He just stares. I don’t get it. Maybe it’s that I don’t keep my mouth shut? Now that I think about it, mine is the only female voice I’ve heard in class (aside, again, from the professor’s). Eh, well, whatever. I just wish he’d cut it out.

18 Septembris 2006

Music for Royal Occasions

The next Fairfax Choral Society concert is “Music for Royal Occasions” with the Washington Symphonic Brass. (Logistics details here.) Unfortunately, I’ll have to sit this concert out; I agreed to the ETD 2006 conference not realizing that it conflicts with mandatory dress rehearsal (which turns out to be the day before the concert rather than the day of). My own stupid fault; I’ll take my lumps for it. I can still sit in on rehearsals, and I have been.

If you’re expecting pompous bombast from this one, given its title… well, yes, we’ve got that. Fortunately, that’s not all we’ve got. I’m quite looking forward to the concert openers by the Washington Brass, because there will always be a soft spot in my wizened ex-medievalist soul for Hildegard von Bingen.

Gabrieli’s In Ecclesiis is pleasant and gentle enough; we have some work to do to tune it, but we’ll get there. The Purcell pieces, written for Queen Mary’s funeral and shortly thereafter used for Purcell’s own, highlight Purcell’s talent for setting English text, English being a peculiarly horrible language to set music to.

Handel’s “Zadok the Priest” is… look, composers have their own styles, I get that. Handel, though, often feels to me as though he’s outright cribbing from himself. “Huh,” said my next-door neighbor at last rehearsal. “Doesn’t that feel like the Royal Fireworks music?” She hummed along with the piano, and sure enough… whereas I had already noted plenty of Messiah cribs. It’s bog-standard Handel. If you like Handel, you’ll like it. If you don’t, you can at least come up with a drinking game for the too-familiar-sounding bits.

(Could be worse. Purcell was good at setting English text. Handel wasn’t—no surprise, as English wasn’t his native language. This piece doesn’t have any embarrassing “All we like sheep” moments, at least.)

My only complaint about Ralph Vaughan Williams’ graceful “O Taste and See” is that it’s too short. As that is my standard complaint about Vaughan Williams, it can safely be ignored. Listen for this one, as it should be a program highlight if we find a good soloist.

The program’s incipient trainwreck is William Walton’s “Coronation Te Deum.” It’s a tough piece. I admit I don’t like it very much, not for its complexity and difficulty, but because a lot of the hard bits feel pointless—call-and-response that doesn’t work very well, silly rhythm tricks that don’t add anything to the text, bombastic fanfare accompaniment that feels like it has a different agenda altogether from the chorus’s.

I’ll gladly work hard for a piece that feels like good music. This doesn’t. This feels like Walton was trying far too hard to be Cool and Rad and Modern. Not that I won’t work hard anyway. It’s just a harder sell; I have to make myself sit down with my rehearsal CD. I’m tempted to check the music press of the time (it was written for Queen Elizabeth II’s coronation in 1953) to see if anyone reviewed this piece, and what they thought of it.

The real winner in this program is Tavener’s “Song for Athene,” which was sung for Princess Diana’s funeral. This is a wondrously spooky-ethereal piece that will make you shiver and sidle closer to the person next to you. It expresses deep pain without sensationalizing it, and offers hope without trivializing grief. I am deeply impressed with it, and I think (based on what we did with the Chilcott) that we have the chops to pull it off.

I do wonder a little about its placement in the program; it leads directly into the concert finale, the too-pompous-for-words Parry “I Was Glad.” I might have switched it with the Vaughan Williams, as a welcome antidote to Handel—but it’s not my program, and I’m no conductor anyway.

It’ll be a good show, if we can pull the Walton together.