Earlham has a host of online databases available to faculty and students via the Library’s Databases page . These resources are only available to Earlham users and only from the earlham internet ‘domain’ , ie from on campus (but by logging in to a ‘proxy server’ we can make them available from outside Earlham). This class of services is generally known as the ‘Deep Web’.
Many of the references you can find are available as full text. However, the procedure for finding and using this information can be hair raisingly complex with up to three different interfaces involved. Let’s look at an example search of the biggest database we have, Academic Search Premier (operated by EBSCO):
Everyone knows how to get to Google. You know you want to search an online database, but how do you find it in the Earlham web site?
The first thing we might be confused about is that page is not called ‘Academic Search Premier’ — this apparently is the name of the database itself — the site is ‘branded’ with the name EBSCO and has a green theme.
The interface we find is a lot more complex than Google’s and the tiny Database Help link does some work of explaining the whole system. But we don’t have time for all this, we just want to do a search. So we type in a unique name and get the first page of results:
and we click on the second title to get the citation.

What do we want to do with this? If it’s of any use in our course then we’d want to get it into Moodle. So we open up Moodle in a separate window and go to our course.
Now we’ve been told that many journals have full text with them. But this one doesn’t seem to do this. However, we vaguely remember a Librarian muttering something about SFX, so we click on the SFX button and a new window pops up (if we haven’t disabled pop-ups for earlham.edu).
Now there’s a new red page with “Ex Libris” and “SFX services for this record”. We may be wondering at this point what ‘SFX’ means. But we notice that there’s a GO for Full Text, a GO for ‘holding information’ (more librarian-speak mumbo jumbo…), and a GO under Reference.

So we GO with the Full Text, and voila, there it is in yet another new window. But how do we make this poem available for students? Do we expect them to know to click on SFX and then the GO with Project Muse Standard Collection? Perhaps not. But we notice that the article is available as a pdf so with a right-click on [access article in PDF] we can save the poem as an acrobat pdf file to our local drive and upload it into Moodle.

But what if we just wanted the URL to the full text in order to paste it in to our Moodle resource? Perhaps the ‘save link for course page, syllabus or notes’ in the SFX window is what we want. However, even though this is in bold red type and looks like a link to click on , it doesn’t work as a link. We have to click the GO button. Yet another window pops ups and this time it’s a selectable link in a text box.

But what a URL; look how long it is!
http://sfx.palni.edu:9003/sfx_ec?genre=article;issn=01612492;isbn=;title=Callaloo;title=Astral.; volume=28;issue=4;date=20050901;spage=894;sid=EBSCO%3Aaph;pid=%3C authors%3ESmith%2C%20Tracy%20K.%3C%2Fauthors%3E%3Cui%3E19776718%3C%2Fui%3E%3C date%3E20050901%3C%2Fdate%3E%3Cdb%3Eaph%3C%2Fdb%3E
Now we have to copy this and paste it in to the Moodle Location field instead of the EBSCO persistent link we used before.
It’s hard to justify complaints that students and faculty use Google to search for full text resources when executing the same process through the Academic Premier Database involves three different user interfaces in three separate windows and a multitude of user decisions and probably false starts. In this search there were three different ‘brands’ to muddy the waters — EBSCO, SFX, Project Muse — and a host of unfamiliar terminology — ‘persistent link’, ‘holding information’, and search terms mostly unfamiliar to non-librarians. Each of these interfaces had usability issues — for example, text that looked clickable but wasn’t a link, and URL which should be selectable and copyable in a single click but wasn’t. It was not clear which was the ‘best’ URL to use to point to the full text and when we finally discovered it the URL text string was so long and convoluted that it was easy to make a mistake in copying and pasting. One character missing or added breaks the URL.
In fact, the process of discovering and using full text resources via Earlham’s deep web facilities has not changed much in complexity since we used Dialog via dial-up modems 15 years ago. One could argue that it’s now more complex.
Posted by markp at March 3, 2006 12:34 PMI agree the number of interfaces and the prominent brand labels of database providers can make it a somewhat cumbersome process to identify relevant resources and then get to them in fulltext.
But isn’t it great that anyone can do it by themselves, with a little bit of poking around on the library pages. No intervention is required or memorization of commands.
Posted by: Sara Penhale at March 5, 2006 11:07 AM