[WEB4LIB] SFX and WilsonWeb

[Abbott, Bruce]

I agree that with the other posters who point out the shortcomings of the
linking.

My biggest gripe, however, is that the administrator has to choose from
selections of online providers, and, at least for us, the choices do not
give us an easy choice.  InfoTrac is not in the same group as LINK and
ScienceDirect.  Which should we choose?  It doesn't seem possible to
personalize the providers for your library.  This means that there will be
providers listed in your WilsonLink which are not licensed by your
institution.

Bruce Abbott
Assistant Director for Library Systems and Electronic Resources
LSUHSC Library 
433 Bolivar St.
New Orleans, LA 70112

babbot at lsuhsc.edu
504-568-6103 (voice)
504-568-7718 (fax)

-----Original Message-----
From: Kenneth R. Irwin [mailto:kirwin at wittenberg.edu]
Sent: Wednesday, January 08, 2003 8:29 AM
To: Multiple recipients of list
Subject: [WEB4LIB] SFX and WilsonWeb


Hi folks,

Is anyone using the SFX capabilities of the new WilsonWeb interface?

As nearly as I can tell, the *outgoing* SFX functionality (from WilsonWeb 
to content from other vendors) is really lame: it seems to link only on the 
database level and not the article level; and unless you host your own SFX 
server, you don't have much control over what databases you link to. (It's 
weird and complicated; I'll not try to explain it here.)

If you have had a different experience (able to link on the article level, 
or able to tailor the outgoing links to databases you have locally), I'd 
really like to hear about it. I'd like to believe that no one would have 
implemented a system as bad as this one seems to me. I hope it's because 
I'm over-looking something.

Also, is anyone using their local openURL-product-of-choice to link *to* 
WilsonWeb fulltext? I'd like to hear about that too.

Thanks,
Ken

Ken Irwin
kirwin at wittenberg.edu
Reference/Electronic Resources Librarian        (937) 327-7594
Thomas Library, Wittenberg University




*********************************************************************
Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
*********************************************************************