Archive for February, 2006

28 Februarii 2006

Things I can’t ask Lorcan Dempsey

OCLC Connexion will export MARC records to Dublin Core, but it won’t ingest records from Dublin Core. Is that right? It seems to be.

I know, I know, granularity and non-specificity and all that good stuff. But Connexion can’t even make a best guess? Or provide some sort of customizable import template?

My IR is eventually going to start taking in electronic theses and dissertations. MPOW wants them in the catalogue. This should be simple—point Connexion at OAI-PMH URL for the ETD collection, harvest (with Connexion feeding the IR the date of last harvest), enhance resulting records by hand, end of story. Heck, if I could just figure out some format that Connexion would eat that, um, isn’t straight-up MARC, I’d do the rest myself, so I would. (I’d even produce MARCXML, and from me that’s a concession, as I loathe clunky, junky MARCXML with a fiery passion.)

Casey Bisson’s point about library standards hemming us in? I’m really, really feeling it right now. We can’t even translate our own standards to our own standards!

(For readers wanting to try this at home: there’s a way. It just only works on Windows. Grrrrr.)

And I’m being completely unfair to Lorcan Dempsey and OCLC. I actually did ask this one, and the answer was “we’re working on it.” I’m just grumpy this week. Ignore me.

Holst: or, the music of words

That Gustav Holst, he was a sharp guy. And he cared about words as well as music.

A section of “The Hymn of Jesus” was giving me fits, switching back and forth between 5/4 and 5/2. I just wasn’t coping. And then it was pointed out to us at rehearsal that this was a mini-Socratic-drama, Chorus 2 firing urgent queries at Chorus 1 for reply.

And suddenly it fell into place for me. Chorus 1 and Chorus 2 trade ten beats back and forth, call-and-response style, only Chorus 2’s line divides into two groups of five beats (two measures of 5/4), and Chorus 1’s into five groups of two beats (one measure of 5/2).

It’s insanely clever. Chorus 2’s five-beat measures sound off-kilter, unbalanced, worried. “I have no resting place!” they cry, and they sure sound like it. Whereas Chorus 1 emits a steady stream of calm, straightforward half-notes: “I have the earth, and I have heaven.” The emotional impact of the words is all there in the music.

Put that way, I find that I can deal with the rapid-fire time-signature changes. Though the single measure of 4/2 amidst 3/2 at “We praise thee, O Father” gets me every damn time still; I persist in coming in a beat early. Eh, well, this is why there are rehearsals.

Second breakfast?

When I knew for sure that I’d landed the job I now occupy, I went looking around for Things To Do. You know, fun stuff. I found the Fairfax Choral Society (beware loud music clip) and clicked over to their calendar page.

Wow! Cool! They’re doing the Lord of the Rings orchestral suite!

Oh. Damn. They’ve already done the Lord of the Rings orchestral suite.

Well, I didn’t hold it against them that they didn’t wait for me—and that turns out to be just as well, because WE MIGHT HAVE A CHANCE TO DO IT AGAIN!!! and I’m all squee-y and excited at the prospect.

Think good thoughts. I really want to do this one!

27 Februarii 2006

Librarian résumés

I got a bunch of files for the repository today from a faculty member. Of course the filenames were a mess. So I wrote a little Python haxie to fix them—lowercase everything, take out special characters, replace spaces and dots (except for the dot separating filename from extension) with underscores.

No big deal. I write little haxies like this—well, honestly, not as often as I did in my conversion-peasant days, and it shows because I have to look up pieces of the Python library I used to know cold, but I do still write them. They’re ugly and nasty and they don’t handle edge cases well and I’d never release them to the wild, but they get the job done faster than I could do it by hand. That’s what they’re for.

The other day I saw a résumé where a little haxie such as this was given major props in the applicant’s cover letter. And what’s more, people were impressed!

I never in all my born days would have thought of that. I just bung Python in under “skills” and let it go.

Just goes to show—well, I don’t know what, honestly. That libraries are under-coder-ed, certainly.

Throw your own spaghetti

Some guest librarians are coming in on Friday. They’re interested in institutional repositories, which means me. So I got to spend an hour this morning (and yes yes yes I had other things to do, I very much did) answering their questions about IRs.

I’ve done this for a number of librarians now. Surveys, exploratory interviews, random email, you name it. The same question invariably comes up: “How do I get stuff for the IR?”

I am a nice person. (Well, I like to think I am. I recognize that opinions differ on this point, however.) I like to share things. I especially like to share the answers to tough questions. If I had the answer for this one? The magic bullet? The never-fail recipe for How To Attract Content to a Digital Repository?

I would have shared it already. Truly.

I haven’t shared it, therefore I don’t have it. QED. Stevan Harnad has an answer; go ask him about it. My paraphrase of his answer is “Make IR deposit mandatory!” Sure, that’s a magic-bullet answer—if you have that kind of power. I don’t, and neither do the librarians asking me this question.

Sometimes, in inimitable reference-librarian fashion, I have to answer the question they want answered rather than the question they asked. Sometimes they’re asking, “How can I fill the IR without extra librarian work?” Simple answer: you can’t. That’s what most libraries with IRs have been trying to do, and it flat-out does not work. I have an obvious bias toward this answer, so don’t trust me—go out and try to find a counterexample.

Either the librarians are going to be depositing stuff, or they’re going to be marketing to faculty so that faculty deposit stuff, or (most likely) both. Over time, this answer may change. I hope so, because even I get tired of saying the same old things to new faculty faces. But I’m not counting on it; some things tip, some things don’t, and I have no idea whether or when IRs will tip.

Sometimes they’re asking “How can I make faculty deposit?” Same answer: you can’t. You don’t control faculty behavior. That leaves you some choices: you can lobby the people who do control faculty behavior, you can dangle carrots in front of faculty, you can take it out of faculty hands, you can build on what faculty are already doing, or you can hope for serendipity. I’m doing all of these things, to varying degrees, and if you look at the (sparse, admittedly) literature, I think you’ll find that most suggested strategies fall into one of these areas. (I don’t know how many people will admit to the last strategy I listed. I only know it’s been a vital one for me!)

Sometimes they’re asking “How do I justify my IR’s existence, if it’s not attracting stuff?” I’ll tell you: I don’t know. My job hangs off this question, and I still don’t know what the right answer is. For master’s and Ph.D institutions, electronic theses and dissertations may be the right answer. For some institutions, Special Collections has the answer. Some institutions don’t have an answer, and very possibly they shouldn’t be running an IR.

I’ll tell you this, though: if you’re trying to answer this question now, you’re almost certainly too soon. “Word is starting to get out,” someone kindly said to me today. My very first “MARS Pathfinder” finally sent me items for his collection last week; I got them into the IR today. I’ve been here seven and a half months; word is just starting to get out, and seeds I planted months ago are just starting to sprout. If you’re expecting immediate results, you shouldn’t be in this business; it takes patience, fortitude, and persistence.

If you’re trying to justify the existence of an IR that no librarian time is dedicated to—well, honestly, why did you start one if you didn’t intend to commit to it? Dump it and go do something else, or make a commitment. I’m sorry if that sounds angry, but I truly do get annoyed at times. I’ve got skin in this game, thank you; I’ve predicated my career on it, fully aware that I may have bet my stash on the wrong horse. If you believe in IRs, you’ll have to add some skin of your own. That’s just how the game works right now.

Yes, committing to an IR is a stab in the dark; nothing I say can make it any less a risk. No, it may not pan out. Yes, if it doesn’t pan out someone will accuse you of wasting all those librarian-hours. If you’re so risk-averse that that’s a problem, don’t start a bloody IR; dump the problem on a consortium or something.

My crystal ball says that a good chunk of the IRs currently in existence are going to fold, mostly for lack of commitment. My fellow repository rats need to be ready for that, because when it happens our institutions are likely to ask us what our value is. I don’t have a one-size-fits-all answer, though I’ve got an answer for myself. If you’re a repository rat, better get working on your own answer.

What all this grumpiness amounts to is, I am still throwing spaghetti at the wall like a mad thing. I don’t know and can’t tell you which strands will stick where you are. If you want to do this, throw your own spaghetti, and then let’s get together and talk about what stuck.

26 Februarii 2006

Octavia Butler

Octavia Butler died unexpectedly today.

I know nothing of her save her writing, so I don’t even know where I should direct condolences.

But what a loss to people who read!

25 Februarii 2006

Meeting of the mind

Michael Edmonds of the Wisconsin Historical Society taught me a grounded, ethics-minded, useful “introduction to libraries” class a couple years ago. One of the first things he addressed was the demographics of librarianship.

No surprises. We’re pasty-faced white. We’re women. We’re heinously educated. We’re pretty well-off. (And yes, I resemble all those remarks.) And—we’re managers, especially once we get a few years’ experience under our belts.

Oh.

I don’t think mine was the only face that fell. I don’t quite recall, though.

I am not cut out to manage. I’m just not. That doesn’t mean I’m incapable of it; it just means I have to learn how owing to lack of native talent. I’ve had both negative and positive examples in what for lack of a better word I will call my career, so with any luck at all I’ll be able to avoid the worst excesses of my bad bosses while remembering what made my good ones good.

And I could have worse opportunities to dip my toes in the water. This is a time-limited (very!) task force with a relatively clear mission (as these things go) and good spadework already accomplished. I’ve one person on the group who is an unabashed me-backer, and the rest are at worst neutral toward me. I’d really actively have to screw this one up to fail, and I shall endeavor not to.

In that spirit, the list of meeting-management links sent me by the LazyWeb (thanks, Norm, Alice, Greg, Chris, Joy, Elaine, and Steve):

24 Februarii 2006

The latest verse

New Librarian has not one, but two interviews scheduled. I’m guessing the cover-letter makeover did its job. She has also applied for a conference scholarship and is working on an online portfolio, sprucing up her web skills in so doing.

I confess to a sneaking desire to slap her father silly, however. One of her interviews is with a community college, the other a regional four-year school with a decent research program. “Why would you ever take a job at a community college as opposed to a research institution?” he is reported to have asked.

Well, gosh. Because the working conditions are better? Because the job is more varied and interesting? Because the people are nicer? Because the area is nicer? Because the area is cheaper? I can think of dozens of reasons.

Prestige of institution? Is honestly pretty darn low on my list of job-appeal factors, and to do New Librarian credit, it doesn’t seem to be high on hers either.

So that’s the latest verse in the saga.

Learning experience

It’s a learning experience. A learning experience. I need to keep telling myself that. LEARNING. EXPERIENCE.

Y’all know those committees you hate going to meetings of? Well, I’ve just been asked to chair one. You heard me. Not “serve on.” “Chair.” If the meetings suck? It’s my fault.

The particular task force I will be chairing will lay the groundwork for our library system’s communications and branding, on- and off-line. Not a small undertaking. And several of the people on this task force are over my head in the hierarchy, so it’s kinda important for me to get this meeting stuff right—or at least not screw it up too badly.

Learning experience. Learning experience. Learning experience. Okay. Whew. Breathing again. Some people have public-speaking issues; I have management issues.

Thank goodness for the systems-design course I took in library school. (Hear that, y’all libschoolers? Good things do come out of library school!) Without that I’d not have the least idea how to get a plan going. As it is, I’m whomping up a Gantt chart and thinking through the first meeting agenda.

Ack, I’m gonna hafta chair meetings! But I never—

LEARNING. EXPERIENCE.

If you know of a smart, no-BS guide to effective meeting management, now would be a really good time to send me the citation information.

23 Februarii 2006

Latest in dspace-devel

Work proceeds apace on the modularization plugin/add-on mechanism (sorry, long day) plans, but consensus exists that they are gumming up the release schedule, so expect to see DSpace 1.4 without them.

Exactly what will be in DSpace 1.4 is still to some extent up in the air; the lead programmers are reviewing patches.

On the UI front, the Manakin group, which is developing an XML-based, customizable-by-collection UI, has formalized its existence as far as a Sourceforge page and a mailing list. The current issue is Manakin’s interaction with parts of the dspace.cfg file, especially those parts that govern what metadata is displayed for a given item.

DSpace’s lead developers are hoping to form further Manakin-like working groups to hammer at specific parts of DSpace. Desired workspaces include: the data model, modularization, rewriting the Browse subsystem, the messaging system, and unit testing.

The SRW server for DSpace doesn’t work for the current stable version (1.3.2). It’s being worked on.

The Researcher Pages patch is also running into 1.3.2 troubles, since it is currently designed to work with the unstable DSpace in development. It is at present unclear whether the patch developers will expend additional effort on 1.3.2, so if you have an investment, you need to speak up now.