Re: Ungava project: Search, browse, visualize catalog and article-level collections

From: Eric Lease Morgan <emorgan_at_nyob>
Date: Tue, 16 Oct 2007 11:26:26 -0400
To: NGC4LIB_at_listserv.nd.edu
On Oct 16, 2007, at 9:44 AM, Glen Newton - NRC/CNRC CISTI/ICIST
Research wrote:

> Ungava [1] is a Lucene-based test-bed for experimental, scalable
> search, browse and results visualization of library catalogs and
> article-level collections. The first release also includes an
> implementation of drill clouds [2] for search refinement, as well
> as using Simile's [3] Timeline for temporal visualization of
> search results and Exhibit for faceted interactions.
>
> Forthcoming collection instances:
>
>   - DOAJ: ~2900 journals, ~900 full-text, ~160k article
>   - BioMed Central: ~180 journals
>   - arxiv.org: 443,988 e-prints, metadata & full-text
>   - University of Denver Catalogue
>   - CERN Document Server: ~900k articles, ~360k fulltext
>
> [1] http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/
> Ungava
> [2] http://zzzoot.blogspot.com/2007/10/drill-clouds-for-search-
> refinement-id.html
> [3] http://simile.mit.edu/


Thank you for bringing this the list's attention, and there are to
things about the work I would like to highlight for subscribers.

First, the system seems to be built using existing tools "freely"
available on the Web. An individual was able to identify a technical
problem needing to be solved and then constructed a possible
solution. Open source software combined with the availability of
globally networked computers make such a process feasible. Such a
combination fosters innovation.

Second, and just as important in my mind, is the content of the
"catalog". It does (or will) include books as well as journal
articles. In the long run, I sincerely believe users will find such
an index to be more useful since it aggregates content into a single
place. Fewer bibliographic silos.

Kudos, and good luck.

P.S. Consider implementing an API against the index. For example,
consider the use of OpenSearch [1] and/or SRU [2]. Given an API: 1)
others could re-use your index in other venues, and 2) you would not
be married to any particular indexer/search engine.

[1] http://www.opensearch.org/
[2] http://www.loc.gov/standards/sru/

--
Eric Lease Morgan
University Libraries of Notre Dame
Received on Tue Oct 16 2007 - 11:47:22 EDT