[ List Archives Home ] [ Thread index for 2008 ]
[ Date index for 2008 ]
[ Author index for 2008 ]
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
- Date: Fri, 12 Dec 2003 12:47:32 -0500
- From: François-Xavier Paré<fxpare@xxxxxxxxxx>
- Subject: Re: WebBridge
Mieko, Bernadette,
I think it is indeed possible to establish article-level links to sites
such as Wiley and ScienceDirect via CrossRef without losing the WAM
connection for off-campus users. At least, initial testing seems
promising. Here is what I have done:
1) Include the proxy in your syntax when linking to CrossRef. For
example, we use:
http://0-doi.crossref.org.mercury.concordia.ca/resolve?pid=<username:password>&aulast=#@AULAST#&issn=#@ISSN#&volume=#@VOLUME#&issue=#@ISSUE#&spage=#@SPAGE#&date=#@YEAR#
2) Add the following two entries to your WAM table:
*.crossref.org
*.doi.org
That way, when you move from whatever (proxied) origin to CrossRef to
your target (eg. Wiley or ScienceDirect), you will consistently stay in
WAM territory, so to speak. Therefore, it is not necessary for CrossRef
to transfer the proxy information per se; as long as you always stays
within sites that are included in your WAM table, all the links will be
proxied. Also, when you do add these URLs to the WAM table, I think you
need to restart the terminal called "WeBridge Resolution Server" (along
with the "WWW Server" and "Proxy Server" entries). I am not absolutely
sure about that last part, but some of the links seemed to magically
work after we restarted that terminal, so...
3) This should work for most targets that use CrossRef. However, every
resource seems to have a different method of handling incoming DOIs, so
you may need to adjust other entries in your WAM table. For example, we
used to have the following WAM entry for Wiley:
"*.interscience.wiley.com", which worked fine. But, as it turns out, you
need to have *.wiley.com in order to maintained a proxied link. This is
probably because Wiley uses another server (maybe
www.wiley.com/something...) to "resolve" incoming DOIs.
I can't guarantee that the above will work for any resource or in every
circumstance, as I haven't completed all of my testing yet. Still, so
far so good...
Have a nice day,
Francois-Xavier Pare
Web Services Librarian
Concordia University Libraries
Mieko Yamaguchi wrote:
>We don't subscribe to anything from Gale so I cannot help there.
>
>As far as I know neither Elsevier ScienceDirect nor Wiley InterScience
>supports OpenURL linking at the article level.
>
>What we have done is to become an affiliate member of CrossRef (there
>is no charge for libraries to become affiliates) and to use DOI to
>link at the article level via CrossRef. The syntax for DOI/CrossRef
>linking is available from CSDirect. Information about CrossRef is
>available from its website at
>
>http://www.crossref.org/
>
>DOI/CrossRef linking via WebBridge works well with one proviso.
>CrossRef works as a clearing house and when you send DOI metadata
>from WebBridge, CrossRef will direct you to the appropriate link.
>But since CrossRef does not send your proxy information DOI/CrossRef
>linking only works for on-campus users at present. Innovative is yet
>to develop the ability for WebBridge to receive an URL back from
>CrossRef and to add the proxy information before forwarding it to
>target resources.
>
>If any library with WebBridge or anyone thinking of acquiring it is
>interested in this facility, please let your Innovative contact know.
>They have said this facility would be developed but it is not currently
>planned for the next release. In the mean time we are using a third
>party gateway (SwetsWise) to provide article-level linking from
>WebBridge to ScienceDirect.
>
>Mieko
>
>On Thu, 4 Dec 2003, Bernadette Maria Houghton wrote:
>
>
>
>>We are currently in the process of setting up WebBridge, and I'd very much
>>appreciate it if somebody who has already been down that road could suggest
>>the correct URL syntax for article-level linking for the following -
>>
>>
>
>[snip]
>
>
>
>>ScienceDirect (currently only linking at journal level -
>><http://www.sciencedirect.com/science/journal/#@ISSN#/> )
>>
>>Wiley InterScience (currently only linkint at journal level) -
>><http://www3.interscience.wiley.com/cgi-bin/issn?DESCRIPTOR=PRINTISSN&VALUE=#@ISSN-HYPHEN#>
>>)
>>
>>
>
>
>
>>I also have Blackwell Synergy, EbscoHost, Ebsco EJS, Emerald and Swets
>>linking OK at the article level.
>>
>>Suggestions much appreciated.
>>
>>
>
>-----
>Mieko Yamaguchi m.yamaguchi@xxxxxxxxxx
>Technical Services Manager/System Coordinator +44 (0)1248 382970
>Main Library, University of Wales Bangor, UK +44 (0)1248 382979 (Fax)
>
>
>
>
>
>
>--
>This message was distributed through the Innovative Users Group INNOPAC list
>Public replies: INNOPAC@xxxxxxxxxx
>Update your subscription options: http://innopacusers.org/list/listinfo/innopac
>
>
>
>
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---