I've never had this kind of problem. Even working with 200,000 documents and selecting titles and abstract.

What version of VOS are you using?

How many RAM has your computer?

Can you send me the Scopus files, or unless part of it, to test it?

I started to use VOS two weeks ago and didn't experience any problems with WoS files. I use version 1.5.7 and the file is quite small: 371 documents. I tried with both text and CVS export of abstracts and titles from Scopus. The problem was that in some runs only 6 terms were extracted and on some others I ve got the run time error. To which email adress can I send you the file.

To [email protected]

I will try to test it now

The problem is the format in which you are downloading the data from Scopus.

On time you have the results of your query, you have to select all the records and export them in CSV (excel format) and select "al available information" in the option "Choose the information to export". The result must be a file with the format similar to the attached file, that works in VOs without problem.

Thanks I will try again

Keep me inform if ti works, please.

Unfortunately not, now I get the Java run time error 278 (null pointer). I will verify my RAM and install the latest Java version

Peter, have you try to run the file that I attached to know if it works?

Benjamin your file worked. For the moment I solved the problem so that I copied the abstracts into the WoS file  - form there it worked fine. Seems that I have problems with some java setting, the technicians are still working on it

Actually the problem occurs if I open the download file, When I directly copy the file from the download folder to another folder and than use iit in VosViewer than everything  works perfectly

i also have problems when i try to use CSV file with vosviewer (scopus only). It works fine for WOS but i couldnt use the CSV file for scopus. It mentioned that there are some error in line num 9. do i need to update my java too?

I'm having the same problem of you Marlissa. When I try to import the .csv file in VosViewer it appears this message:

Error while reading scopus file .....(line 10) incorrect number of columns.

I attached here a print screen of the message error .

I did not open the file in excel before trying to import it.

Can anybody help me please? Peter Kokol Benjamín Vargas-Quesada

Cibele which fields did you select when exporting the file? If you also selected Funding data, this can sometimes be a problem. Can you please send me the file to [email protected] or you can also sen me the search string

Hi Peter, Peter Kokol

You were right, the problem was I was also selecting Funding Data. Now everything works fine!

Thanks a lot for the tip

Good afternoon, I have a problem "Error while reading scopus file ..... (line 8) incorrect number of columns." I am working with a Windows 10, I put it in txt and csv file.

Hi Camilo, take a look at what options you've selected once you're in the site of Scopus. You may not select the funding data.

Hello Cibele, the data I acquire are topics related to one specific and I try to porbar with different program options but still does not work.

Camilo, which version of VOSviewer are you using?

Dear Kokol

I am getting the same problem as per attached screenshot.

Looking Forward

Regards

Hi All

The solution in my case was to deselect from the CSV export panel all the Funding details. Give it a go and let me know if it works.

Good luck

I extract the information from Scopus in format (.ris) and go through the process in the VOSviewer.

I still encounter problems when exporting Scopus files. After some research I found that records where papers have no page numbers sometimes cause problems, and we have to get rid of them. That is a bit tricky, because if you edit the file in Excel it become unusable in Vosviewer. So you have to get rid of such records directly in the search string (fortunately its quite rare and normally no more than one record per 2000 records). In such a case I use Advanced search and extend the string with AND NOT TITLE(“title of the paper”). To get the paper title you have to use the line number reported by Vosviewer in its error report You have to subtract one (1) from that number a locate the record with that number in the papers harvested by your original search string. Than you have to copy and paste the paper title in the extension string described above and add that string to your original search string. Its sound a bit complicated, but its quite easy after you tried this procedure once and it solved all my problems.

Relatedly, I have problem using Scopus files in VOSviewer. To be more specific, I downloaded every paper as csv file and i tried to do bibliographic coupling. Unfortunately, the cited references may have some differences in format and, as a result, every such paper has many duplicates, but each one has only 1 citation from the sample. Have you experienced such a problem?

Andreas, you have to export all the papers as one csv file (you have to check the box "References" in the export user interface)

Unfortunately, this is not possible because they do not meet the same search criteria. Therefore, I have exported individual files. This process was workable with Web of Science in a previous circumstance, I am wondering if i am missing something related to Scopus configurations.

I would sugest that you use one search string where you combine all search strings used into one: serach string 1 OR serach string 2 OR .... If you have some other search limitations than you have to use advanced search and cobine the strings there

could you please tell what should I do in that kind of situation Peter Kokol ?

Ther could be many reasons, but I suspect that you didnt check all the needed boxes in the Export window. The other possiblity is that you didnt select Scopus files in the VosViewer

Peter Kokol , thank you. I found the solution before you sent that message. And the problem was in that since I study in Russia websites on may laptop are in Russian mostly. I downloaded the data in Russian but the VOS itself is in English, that's why it couldn't read it.