[WEB4LIB] What about a non-full-text limiter?

[Dan Robinson]

Brian, you can do this in a search if you know how the limit to full text is created in the first place. If it is done by programming behind the scenes, you're probably out of luck. If the limit to full text is really just a precanned search, and you can see the actual search, just reverse it as a 'not' search.  Your database should also have a holdings display. Of course this all depends on whether your choice of databases has not been limited to full text only ones. In which case none of this applies. <grin>.   I'll put in a shameless plug and say that all of this is doable in our databases, except of course, the full text only ones. 

Dan Robinson
drobinson at hwwilson.com

> -----Original Message-----
> From: web4lib at webjunction.org
> [mailto:web4lib at webjunction.org]On Behalf Of Brian Mathews
> Sent: Thursday, August 05, 2004 7:58 PM
> To: Multiple recipients of list
> Subject: [WEB4LIB] What about a non-full-text limiter?
> 
> 
> 
> I wish that database vendors included a non-full-text 
> limiter. Sure, it is strategic to have the ability to filter 
> your results for full-text only, but what if you wanted a 
> list of items that are not available online?
> 
>  
> 
> A practical example: A patron is in a rush to find articles 
> for a paper due in two weeks. After looking through a 
> multitude of full-text titles, they realize that the paper is 
> going to require a visit to the actual library.
> 
>> ....................
>  
> 
> Of course, taking this further, it would be nice to be able 
> to measure the search results against the catalog (a la 
> WorldCat) to indicate local holdings. So in our scenario 
> here, the patron could run a search and collect all the 
> full-text articles, then limit the search to journals held in 
> the local library. And then, time permitting, could generate 
> a list of non-full text, non-locally held articles for ILL.
> 
>  
> 
> Something like that...
> 
>  
> 
> Brian
> 
> 
>
>