Greenstone integration

When my puppy was just a few months old, we got a silly little card from our vet saying that "everyday is a new adventure." In spite of how corny this sounds, such is the same for a librarian trying to plan their first digital library project.

My project, I feel, has really taken on the shape and direction that I was initially lacking ever since our Director of Academic Computing suggested that whatever I choose should dovetail into Sakai. Whether we use Sakai or not is almost moot, at this point -- the real idea here is that our systems should be wide open and able to "talk" to our other systems. AC is working on that on their end; likewise, we should too.

So... I just learned yesterday about Greenstone's ability to integrate with DSpace. Apparently, you can develop in Greenstone and then transfer your collections and metadata to DSpace rather easily, and vice versa. You can use Greenstone as the frontend for DSpace, or you can scrap it entirely.

We are still looking for our "quick and dirty" UI to mount our collections soon -- This is looking like a highly likely route.

Further reading:

Computer Science Thesis from Virginia Tech, outlining an open XML schema for DSpace

And the prize goes to... DSpace!

At long last, I have settled on developing DSpace for La Salle. Everytime that I talk repositories to faculty, they want to start throwing teaching materials into it. I found an interesting paper that talks about the possible integrations of DSpace with Sakai, an alternative to Blackboard which I was asked to find out how my systems may integrate with. Also, I saw a posting yesterday that Fedora and DSpace have recently decided to try to identify some areas to work together. We still don't feel confident that we could develop Fedora here without a programmer, but we feel good about DSpace being within our skillsets. I still have a crush on Fedora, and would welcome the intersection of the two systems to allow me more opportunity to play with that system as well.

I had originally not considered DSpace, as I always thought that it was just for ETDs. People are using it differently than that, and as I started demoing CONTENTdm and asking users about their experiences, I started getting pointed to DSpace more and more, given our desire to manage diverse scholarly materials and didactic resources. The dealsealer was seeing how Australian National University migrated from CONTENTdm into DSpace and came up with something what I would be looking to create for our Special Collections: http://anulib.anu.edu.au/subjects/ap/digilib/.

We're still early enough in our digitization game here that I don't want to end up locking us into a proprietary database without getting a greater sense of the digital directions of the campus. The openness of the code and flexibility of metadata input/output will set us up for optimum interoperability with future systems. Also, DSpace runs on Dublin Core, which is far from intimidating, but also allows input of METS, which I think should allow for a fun challenge.

Now the preservation question... OCLC's digital archive service is still looking pretty good, as they are reasonably priced compared to other services. I also may be looking at using the money that I save on software acquisition to mount an argument for Sun Microsystems' Honeycomb or something along those lines. It is too onorous to throw manual digital preservation administration and data backup on top of a librarian's other duties -- Therefore, all redundancies and reporting will be automated and/or outsourced so that it is done efficiently and effectively.

Non-use of ContentDM and other sites

One software that we are looking at is ContentDM, which is a great software for accessioning and displaying digital assets. It is clear, easy to use, and can pretty much work right out of the box. I have yet to come across any librarian who really dislikes the software. The one comment that I have heard, however, is that no one really uses the site. So why go through the effort of digitization if no one is really using the software? Digitization is anything but cheap -- Between licenses and staff, a digitization project can easily cost tens of thousands of dollars.

Cornell, too, published a report evaluating the non-use of D-Space at their university. The whole report can be found at http://www.dlib.org/dlib/march07/davis/03davis.html. Part of the reason for non-use is that each discipline already has mechanisms for publication of materials in place and that their DSpace is additional, operating outside the sphere of traditional avenues.

Librarians are dreaming up these wonderful digital repositories, and companies are creating awesome software packages to host them, but is it all just Library Science laboratory work? How can digital initiatives be made more relevant and integrative into the academic sphere? Blackboard and other class content management and presentation software systems are thriving, because students and faculty have to go to them for class materials. It almost makes sense to grow a repository as attached to Blackboard, as people are already there.

I see now why ArtStor has taken off so well in the academic art realm -- Faculty can direct their students to the repository, add to the population of the image collection, sort and create their presentations and pretty much base classes out of there. I don't know if ContentDM can offer similar flexibility, or if the collections that we are speaking of digitizing have as much relevance to the coursework as would images of art for art history classes.

But it could.

And with careful planning, maybe it will?