Showing posts with label federated search. Show all posts
Showing posts with label federated search. Show all posts

Wednesday, August 27, 2008

Widgetized Applications! (for most html based browsers)

Well I have been working on polishing some applications that are designed to make life easier here at the library. We found some active library widgets at Widgetbox and I decided to try and work with it. Here is an example of what I came up with:



Constructing the widget was a bit difficult at first as there were no real instructions on how to start. In effect an html based widget requires html and can also take javascript. There was an issue with the way some of the components interacted and it took a bit of tinkering with the scripting and code to get the widget working correctly.

The problems I experienced were related to the straight searching of the catalog. It required that I create a new window in the browser, shift the focus to the window, and load the page. Rather than using a normal form, action command. The code also required javascript for the construction of appropriate urls.

On the plus side hosted widgets localizes the location of files and allows for a singular location where everything for the construction of the file is located. Say for instance that someone came in as a freelancer and created widgets for us then we would know where they were located and could easily access the code. Which could have been a problem with flash, or flex based widgets.

Friday, June 20, 2008

Metalib and EBSCO Allow Many Databases to be Automated-Federated Searching

I just got back from SLA in Seattle, Washington and the conference was great! There are so many ideas that I have brought back and am planning on working with so I thought I would share some of them with you. The first is what Metalib and EBSCO allow us to accomplish, as librarians, when trying to create toolbar applications that search like Google.

When you run a search in Metalib for about 5-10 seconds a persistent URL will appear in the search box of your browser. You can do this for either individual databases, or the federated searches that Metalib provides. If you want to automate that search you need to copy it before it changes to a session URL. You can then of course automate it like I explain in this post.

The advantage here is that there are a large number of databases that Metalib can search through that use non-persistent URLs. The downside is that researchers may be used to specific interfaces. With the OU toolbars searches to a database that can only be accessed via Metalib use Metalib, but if the search box is left blank the toolbar goes to the native interface. Then through instruction I make sure to teach researchers which databases are wired for Metalib.

EBSCO has an option built into it where you can select multiple databases that you want to search. After running a search you can either check the persistent link to the search or add the search to your search folder (either is a persistent URL). When you select multiple databases you can extract a persistent search that covers many databases. So now we can set up searches for toolbars that are federated searches for EBSCO (for whichever databases you want to use).