Pages

Thursday, March 21, 2013

Definitions: Archives and Institutional Repositories

Photo credit: Aureusbay
I’m wondering if anyone out there has any particular insights into the varying mission and functions of an archive versus an institutional repository. I thought I had a very clear idea in my head about what an institutional repository is, or at least its purpose. However, when I began to discuss this with my university’s archivist, her response was, “We already have an institutional repository—it’s called the archive!” This stumped me a bit. I don’t think they are the same thing, but it has been difficult to articulate the key differences.

After doing a little bit of research (Google was spectacularly unhelpful in this particular case) and some further discussions with our archivist, I have some coherent thoughts forming. I think archives and institutional repositories have related, but distinct purposes, which inform their policies and practices around content, preservation, and access.

Content
University archives collect a couple different kinds of content, including administrative records and materials relating to the history and accomplishments of the university and its members. While there may be legally required collections policies on administrative records, universities and their archivists generally have a fair amount of discretion when it comes to what to collect. Finally, in most institutions the archives were created in a pre-digital era, many of the objects in the archive were and continue to be physical. The shift to digital means a couple thing, one that archive catalogs are more likely to be online (just as with libraries), and two that archives must develop new policies for preserving objects that were “born digital”.

Institutional repositories collect the intellectual and scholarly output of a university. This may mean works published elsewhere, informally published works, grey literature, or work not formerly published. It is harder to make universal statements about what does or does not belong in an IR, because universities seem to use them different, however best fits their needs. I’ve seen examples of IR software that contain image collections and audio/visual collections. I would like to say that most of the materials in IR are “born digital”, but I’ve seen IRs that have digitized versions of old campus blueprints—something that seems more like an archival object to me.

Preservation or Access?
My crude, simplistic assessment of the major difference between archives and institutional repositories is that archives are more concerned with preservation and IRs are primarily about providing access. The two are clearly not mutually exclusive, in fact, one could ask what the point of preservation would be if not to provide future access, but that is just the librarian in me. However, when I look at the policies, practices, and opinions from these two communities, archivists and scholarly communication folks, this seems to be the key difference. 

The work of archivists is to ensure the long-term preservation of objects, often physical objects that are irreplaceable. They are concerned with original object, accession order, and provenance. While online archive catalogs have enabled more access points for searching and finding documents, archival cataloging is chiefly concerned with office of origin and date of creation. Compare this to library catalogs, even prior to the move online library catalogs still provided access points for author, title, and subject. 

In my mind institutional repositories are inextricably related to the open access movement. While they may serve the related purpose of preserving scholarship, their chief purpose is to provide access to that work. Scholars and librarians have advocated and created IRs in explicit opposition to disturbing trends in the scholarly publishing industry. 

What do you think? Are there other important differences between archives and institutional repositories? Or am I trying to create false distinctions between two things that are really the same?

Thursday, January 10, 2013

The e-books is dead! Long live the e-book!

Photo credit: cehwiedel
As quick as we are to declare the death of print and the ascendancy of the e-book, it seems that we are quicker to rush to the gallows of the e-book the moment sales begin to falter.  Or at least that's what I got from Nicholas Carr's most recent review of the state of e-books: "Don't Burn Your Books--Print Is Here to Stay." 

Carr takes a look at some of the recent Pew surveys about e-reading habits, and sales figures for popular e-readers and concludes that readers have decided their Kindles are only good for hiding copies of Fifty Shades of Grey, and that really they'd rather be playing video games on their tablets, or guiltily sniffing the ink between two hard covers of a Pulitzer Prize winner.

While he's not totally wrong, I think that his arguments largely miss the point of why we should care about whether people read a digital or a print text. What's worse, his article reeks of a snobbery that is frankly unhelpful when we talk about the reading public.  Really, what we should be concerned about is not how folks are consuming texts, or whether they're reading the "right" texts--but whether folks are reading at all, and getting anything out of what they read (be that information, titillation, enlightenment, connection, empathy, or thrills).

Based on the sales of genre fiction versus literary fiction and non-fiction, Carr points out something that several Bookaneers presented on and blogged about back in 2010 (please don't watch the video of our conference presentation, because it's embarrassing, just know that it's there): that we read differently for different purposes, and that reading for information and reading for narrative require different technologies (see also Freeda's post about ideal e-books for academic reading).

While Carr chalks up the popularity of genre fiction in e-book format to the shame that he expects readers to feel about "the kind of light entertainments that have traditionally been sold in supermarkets and airports," I would attribute it instead to the addictiveness of  the only novels that most people are reading.  Romance novel addicts will tell you that they read them as fast as they can get them, and if the Amazon marketplace is closer than the supermarket, then they're going to read even more, even faster. Furthermore, even if readers wanted to read things like, say, textbooks on their e-readers, they can't, because the makers of both e-readers and e-books have utterly failed to adapt their technologies to anything other than linear, narrative reading.

There is a consistent conflation in Carr's piece between e-readers and e-books, and it makes for a muddied analysis.  It makes perfect sense to me that e-readers will disappear as single-use technologies when tablets have become their equal in portability and readability and their superior in versatility.  But just because we're not buying Kindles anymore that doesn't mean that we will be reading any fewer digital texts, or any more print texts.

True, paper books are a real pleasure to read.  The codex, as a technology, has had hundreds of years to adapt perfectly to our hands; our eyes; and the way that our brains access, interpret, and recall information.  There are many good reasons why we should keep reading books in print, but until we face the fact that digital texts will coexist with, and perhaps supplant printed texts, we can't focus our energy on what really matters: getting texts (digital or print) that suit our reading habits and needs.  Who cares whether e-reader manufacturers are making or losing money on our reading (because that's what these past 5 years of e-reader boosterism really comes down to, right?)?  What we should care about is getting high-quality, abundant, low-cost, accessible reading materials into our own hands and the hands of our students.

Thursday, December 20, 2012

A Domain of One's Own and Info/Tech Literacies

Give every student a domain name and web hosting, and let freedom ring!

Although Jim Groom, Director of the Learning Technologies at the University of Mary Washington, probably wouldn't like that wording, that is the gist of his recent pilot project, A Domain of One's Own.

He recently gave an interview for the Chronicle's Tech Therapy blog in which he described the project and its motivations. Have a listen, if it sounds like it might tickle one of your fancies.

So, quick aside: I had this idea to write a post about digital subjectivity in relation to this project, and I was set straight (rightfully) by Althea. Here's how the conversation went:

Me: Hey, I'm thinking of writing a post on subjectivity.
Althea: Ahahahahahahahaahhahahahaha..ahah. heheh. heh... hmm?

Not really. Althea is too nice to laugh that much in my face, but I know she was laughing inside. But, the upshot is this: I think librarians should be interested in what might be called "digital subjectivity." So, let's talk about that sometime. Maybe even write some posts about it!

Okay, back to our regularly scheduled programming...

Recently, I've been working with a librarian here at UW Bothell to think about the relationship between information literacy (the standard bearer of library instruction) and technological literacy, an ill-defined (perhaps undefinable) set of literacies that are related to information literacy. Although what it means to be technologically literate is as difficult to define and describe as what it means to be to informationally literate, we must forge ahead and do something, despite the definitional problems.

I like the ethos of UMW's pilot project: set up a space and let the students and faculty have the openness to do what they want.

Many would quickly retort: "Ahhhh! What if they don't know what to do!?"

The truth is that learning is struggling, puzzling, feeling the anxiety of not knowing what you don't know. I think the scariness of openness (a term I haven't defined, but so it goes...) is something to work with, rather than something to avoid. When you see someone achieve some success in relation to a research problem (information literacy) or a technology problem (technology literacy), you see them achieving some level of empowerment. But, when we set up systems in libraries and across the university that reduce the fear of the open unknown, we also reduce the possibilities of success and empowerment. There is nothing so effective at reducing someone to powerlessness than a system that never challenges them. Ask any high achieving student in a middling classroom.

In the end, whether you work as a technologist or a librarian, much of your job is becoming a collaborator on all sorts of projects. As we move forward with these projects, we might do well to take some advice from UMW's project and set the bar high, challenge people and then work our asses off to help them achieve success.