The import function for Lens seems to work (I'm using this cvs2wos config file). It's sometimes slow. It took an hour on a dataset of about 50k rows - but it only dropped 3 rows and the results generally look quite ok to me. But so when I ask CiteSpace to build the network based one WoS-converted records, I keep getting this error: . Could the problem reside in the PD and PY fields ?
I would be very grateful if you could take a look at this, as it seems to me that Lens remains one of the most promising databases for performing the both macro- AND micro-scopic analyses you talk about.
Last edit: Stephan De Spiegeleire 2020-12-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Check the Project Properties:
Data Source: (x) Lens <= you need to check Lens instead of WoS, which is the default.
The speed is really controlled by the API rate set by Lens. This is a very common practice and a compromise.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It looks your data file does not contain cited references, which would explain the error message.
The configure file shows 31% of the records have cited references. I didn't see any apparent errors in the configuration. Here are some possible reasons: 1. Lens has changed their export format beyond the recognition, 2. the available references in the original form (Lens' IDs) failed to resolve to valid references, or 3. something else.
You can check the original export file from Lens and see if there are any cited references there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The import function for Lens seems to work (I'm using this cvs2wos config file). It's sometimes slow. It took an hour on a dataset of about 50k rows - but it only dropped 3 rows and the results generally look quite ok to me. But so when I ask CiteSpace to build the network based one WoS-converted records, I keep getting this error:
. Could the problem reside in the PD and PY fields
?
I would be very grateful if you could take a look at this, as it seems to me that Lens remains one of the most promising databases for performing the both macro- AND micro-scopic analyses you talk about.
Last edit: Stephan De Spiegeleire 2020-12-28
Check the Project Properties:
Data Source: (x) Lens <= you need to check Lens instead of WoS, which is the default.
The speed is really controlled by the API rate set by Lens. This is a very common practice and a compromise.
It looks your data file does not contain cited references, which would explain the error message.
The configure file shows 31% of the records have cited references. I didn't see any apparent errors in the configuration. Here are some possible reasons: 1. Lens has changed their export format beyond the recognition, 2. the available references in the original form (Lens' IDs) failed to resolve to valid references, or 3. something else.
You can check the original export file from Lens and see if there are any cited references there.
Oh it was...