Academic Librarianship’s Future Strengths?
In my first job after college, as a manager at a small nonprofit, I was taught to use the euphemism “future strengths.” For instance, when I conducted performance reviews, my colleagues would often mention punctuality as one of their future strengths. We also used dozens of other terms that ate at my newly minted English-major heart. And yet they seemed to work. People who went out of their way to rationalize tardiness when they thought it was being met with disappointment seemed eager—albeit in a jaded, we-both-know-what-this-means way—to claim punctuality as a future strength.
Thatâ€™s one danger in talking about disappointment: people sometimes take it the wrong way, as attack rather than encouragement. A second danger is that people might think youâ€™re down on them or the topic at handâ€”that when I talk about the areas of academic librarianship I wish were different, people will think Iâ€™m down on libraries or librarians, which couldnâ€™t be further from the truth. I think weâ€™re great, and I think we have the motivation and the resources to address every item on the following list, provided enough of us agree that they should be addressed.
My greatest concern in listing future strengths is that itâ€™s often seen as presumptuous. Please understand that I donâ€™t want academic librarianship to conform to my grand vision (I donâ€™t have one) and I donâ€™t believe the people responsible for the status quo made mistakes (Iâ€™m sure they made rational decisions based on what they knew at the time). Iâ€™m publishing my list of future strengths not because I have evidence that sharing them will be useful, but because I havenâ€™t yet found any evidence that it wonâ€™t be. Sometimes you put something out there not because you know youâ€™re right, but because itâ€™s a good way to find out that youâ€™re not.
I suspect that many of you will react to my disappointments and my ideas for turning them into future strength with some variant of, â€œWell, itâ€™s a little more complicated than that.â€ Maybe it is. Then again, perhaps for one or two of them, it doesnâ€™t have to be.
We donâ€™t own our serial collections
Not owning our serials, all on its own, would be enough to qualify as my number one disappointment. Even though Iâ€™m developing a better grasp of the financial considerations involved, itâ€™s still pretty hard for me to believe that we donâ€™t own such important components of our collection. Whatâ€™s even harder to believe is that we donâ€™t control our own indexes. But the most troubling aspect of all is that we appear to be dead set on repeating this process with our books. While Peter Brantley has said it better than I can (see â€œGoogle and the Booksâ€ and â€œGoogle Books: A Reprise with Clarityâ€), he seems to be more circumspect than I am regarding the secrecy that every â€œGoogle Libraryâ€ has agreed to maintain. If your library is legally enjoined from divulging which books it has digitized, or the financial details of its Google contract, or anything else at all about its involvement with this project, then your library is â€œcorruptâ€ in the sense that Lawrence Lessig has begun using the term.
Fortunately, we appear to be making progress. Harvardâ€™s recent announcement was encouraging, Peter Suberâ€™s Open Access News seems to document a dozen small victories daily, Brewster Kahle is fighting the power, and itâ€™s not as if our profession is indifferent to the situation in scholarly communications. And yet, well, let me put it this way: how many of us still read and publish in journals that lock away our ideas like so many Rapunzels?
We donâ€™t know our own history
Iâ€™ve already devoted one ACRLog post to this topic and it will likely be the topic of a future post as well, so instead of belaboring the point, Iâ€™ll give you an anecdote and a pretty picture. From Edward A. Goedeken:
Like the farmer in the movie Field of Dreams, Louis Shores always believed that if he could build it, they would comeâ€”and they did. In 1961, little more than a decade after Shores, Wayne Shirley, and Carl Milam founded the American Library History Round Table (ALHRT) in 1947, the indefatigable Shores was ready to host the first Library History Seminar at Florida State University. From that humble beginning (only sixteen library historians attended the 1961 meeting), the seminars have flourished. Over the years the number of attendees has steadily increased, with recent seminars attracting scholars from all corners of the globe to share their affection for library history.
We are now up to eleven seminars and 199 presentations. Five of these presentations have been about academic librarianship.
Sources: Library History Seminars I-IX compiled by Goedeken and presented in tabular form. I categorized presentations from the following two seminars on my own and offer no assurance that my decisions match Goedeken’s scheme. Here are the lists of presentations at Library History Seminar X and Library History Seminary XI (see also: Library Trends, Volume 55, Number 3, Winter 2007).
While it’s still enough of a future strength to make the list, Iâ€™m optimistic about the OPAC. NC State, Koha, Evergreen, VuFind, Fac-Back-OPAC, WorldCat, LibraryThing, Aquabrowser, the Open Library, and the last proprietary ILS vendors standing, are making inroads. That said, your OPAC is broken if it:
- Doesnâ€™t offer faceted browsing;
- Doesnâ€™t include federated search that retrieves relevant results from your entire collection (e.g. monographs, serials, other media, special collections);
- Doesnâ€™t have a permanent, clean URL for every item in your collection;
- Doesnâ€™t produce that URL in a way that shows up in Google/Yahoo/MSN/Ask, etc.;
- Doesnâ€™t offer useful feeds (e.g. new material, sorted by subject);
- Requires that your constituents get trained in order to use it effectively.
Citations are at the slide rule stage
Iâ€™m still surprised by how many software programs there are for organizing references. Some are open source and some are proprietary, some work directly with the ILS and some live within the browser. All of them do their best to work with the major citation styles, and a few try to work with others.
I suppose itâ€™s nice to have a lot of options, but Iâ€™d feel better about the situation if I thought I was making a choice among citation systems that work really well. Unfortunately, I donâ€™t think thatâ€™s the case, though I donâ€™t blame the software. I think the fault lies in the specifications, which still seem to reflect pre-digital thinking not just in their formatting, but in their licensing and distribution: at the libraries where I work, I share citation specifications with one student at a time in book form. How nice would it be if we had a single, open specification that was developed specifically to help us automate the citation process?
I have more to say about the potential uses for a human and machine-readable, open citation format, but Iâ€™ll save these thoughts for another post. For now, Iâ€™ll end with my suggestion for what an open citation format might be called: Op. cit.