Am 27.01.2011 19:47, schrieb noreply [Ludmila Marian]:
Hi!
============================================================================== OVERVIEW of task #19001: ============================================================================== Request from Jens: Integrate the WoS services to a maximum so that CERN users (and others with access to WoS), can easily access the WoS data (and thus, take advantage of the CERN WoS subscription). Getting the WoS data can be done using the Links Article Match Retrieval Service. What might be done: - We could start by adding a link to the detailed page of each record, and discuss after about integrating this data in the metadata of each record (e.g citation counts - comparing some citation counts between WoS and Inspire showed, in some cases, better numbers in Inspire, but (citing Jens) the Inspire data are not recognized outside of HEP, while WoS is considered as the authoritative source across all disciplines).
It seems not wise to integrate WoS Citation counts into the record as this data changes, sometimes freequently. Therefore it should be fetchted upon request. Using UT-code seems the procedure of choice as it restricts the number of requests necessary. It seems advisable to store UT-codes e.g. like 024 7_ $2ISI$0<utcode> for each record that is covered in WoS and where it is available. Then creation of queries against WoS are pretty simple as you can search for (UT=<$0>) obtaining one single record only.
- We will probably need to put in place a caching mechanism (some data is uploaded only once per week on their side, and the links need to be generated only once at the creation of a record). - We need to test the response time from their side as a first step.
Response time from WoS: slow to very slow. Reliability: depends upon load, sometimes frequent timeouts. (Sample: definitely representative with good statistics ;)
Based on this, we can know at which step this information should be requested (either at the creation of a record, or offline for the already submitted records, and in this case, keep the info in the database, or maybe the response time is very fast, and in this case, we can do the request online, at the display time).
For single records you can fetch the data upon request. You have to handle timeouts there as it isn't the most reliable service either. Therefore, it seems advisable enrich records by such data offline, unless you want to enable a "copy from wos" feature for record ingest. (For the latter it might be desirable to check out PUMA's bookmarklets which enable record feeding from quite a bunch of sites on the Net (cf. http://puma.uni-kassel.de/) -- Kind regards, Alexander Wagner Subject Specialist Central Library 52425 Juelich mail : [email protected] phone: +49 2461 61-1586 Fax : +49 2461 61-6103 http://www.fz-juelich.de/zb/mitarbeiter/fachinformation#wagner ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDirig Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
