Activity for Chaomei Chen
-
Chaomei Chen posted a comment on discussion General Discussion
Dear Andrej, Your interpretation is essentially correct. Candidates with ties will be all considered qualified unless you break ties with additional parameters such as the e threshold in Project Properties. For example, if you set e = 2, CiteSpace will exclude papers with citations below this threshold.
-
Which version? Uninstall it. Remove the folder User/xxx/.citespace, then install it again.
-
Thank you Marcos.
-
I have just added a blog to demonstrate the steps of exporting Scopus data to CSV. I hope it helps. https://citespace.podia.com/blog/48cc06cd-a615-45e8-9eb4-fcbaff26c424
-
The format of your CSV file is different from what I downloaded from Scopus back in Feb 2025. Scopus may have changed it, although the Feb version was more reliable. Your CSV file also has a few rows messed up. See attached. You should either remove or fix them. RIS exports from Scopus have some problems in the past. CiteSpace temporarily suspends the conversion of RIS exports from Scopus until the issues are fixed.
-
If the node type is references, make sure your data indeed contains references.
-
Most likely your local network is restricted.
-
Have you tried the version released on December 27, 2024?
-
Yes, it is possible as ties are allowed and top 50 distinct values are used to select qualified items. Thus each year there can be more than 50 qualified items.
-
Prepocess your data with Data > WoS > Duplicate Removal. Then try again.
-
The value at <i, j=""> is the co-occurring strength in cosin of i and j.</i,>
-
An adjacency matrix is represented in two files when you export it from CiteSpace. For example, if you have a 561-node network, you will get two files: network561x561.txt and network561x561Labels.txt. Depending on what you need, most of the information is accessible through the interactive visualization in CiteSpace. Of course, you can do whatever you need with these exported files. Node names are in the labels file, like this, i.e., 561 lines: SHAH B, 1997, SUDAAN USERS MANUAL, V0, P0 IMM NAT SERV,...
-
I will double check.
-
CR = Cited References. Here is what it looks like. It is essential if you choose References as the Note Type. CR Angbazo L, 1997, J BANK FINANC, V21, P55, DOI 10.1016/S0378-4266(96)00025-8 Athanasoglou P.P., 2008, INT FIN MARKETS I MO, V18, P121 Berger AN, 2013, J FINANC ECON, V109, P146, DOI 10.1016/j.jfineco.2013.02.008 Berger AN, 2009, J FINANC SERV RES, V35, P99, DOI 10.1007/s10693-008-0050-7 Biau G, 2016, TEST-SPAIN, V25, P197, DOI 10.1007/s11749-016-0481-7 Bolt W, 2012, J BANK FINANC, V36,...
-
The issue with the Scopus author has been resolved in the Advanced version 6.3.R3. Should be available in the next Basic version soon.
-
Do you have a screenshot of the first few lines of the exceptions? I suspect it may be caused by some irregularities in the data. If the problem remains, email me more details along with the dataset, I will take a close look.
-
The two links below should be helpful: https://support.apple.com/guide/mac-help/apple-cant-check-app-for-malicious-software-mchleab3a043/mac https://iboysoft.com/howto/apple-cannot-check-it-for-malicious-software.html
-
Your pic2 shows the problem: SQL Query Error: OS errno 13 - Permission denied It tries to create a file under /Users/chunlingyu/.citespace but permission was denied.
-
The new version posted today should fix the issue (Built date: 3/22/2024).
-
Thanks for letting me know. A new version will be available soon, including this fix.
-
I've double-checked it and it downloads fine. Have you tried different browser, e.g., Chrome? Please use the citespace.podia.com to communicate. It will hopefully get my attention quicker.
-
I have some issues about upgrade new version and other issues
-
Dear Mojtaba, You should be able to download the new Advanced version from citespace.podia.com using the same way as you did last time. Generally speaking, the newer version should be more reliable and accurate. Discrepancies between different versions may be due to improved processing capabilities of the newer version as well as possible changes of the default settings. You can also leave your comments on the citespace.podia.com site.
-
Time slicing Error
-
This is due to your insufficient data: the CR field is missing.
-
Can you attach the original data file from scopus? Which version of CiteSpace did you use? Basic or Advanced?
-
Thanks for drawing my attention. Let me check.
-
It is nothing unusual to have nodes with 0 betweenness centrality. It is perfectly fine. Check the definition of betweenness centrality.
-
Open the CSV file in Notepad++. If you see UFT-8-BOM at the bottom right corner, remove the BOM as follows: Go to the Encoding menu, select UTF-8 and save the file.
-
At the beginning of your CSV file, there is "", which is known as a Byte Order Mark (BOM). See the attached image. 6.2.R6 (Advanced) released today (11/26/2023) can take care of this programmatically, but you can mannually remove it with a text editor.
-
You probably missed the step to convert the CSV to a tab-delimited format before running the CSV converter. Attached is the converted and duplicates removed file.
-
See FAQ 4.7. Your setting is not the same: e=1.0 vs e=2.0. It is also possible to see some minor differences between different versions due to internal changes.
-
Use the All in One function and adjust the Threshold under the Node Labels (By Cluster). This will show labels of top 2 nodes from each cluster. Most likely your top 10 will appear in several clusters.
-
If Scopus is your source, use the CSV export. Do not use the RIS export for now.
-
Use the CSV export instead from Scopus. Then convert it in CiteSpace. Currently, the RIS export from Scopus seems broken.
-
CiteSpace gives 3 most common reasons along with this message. As it turns out, your data file does not contain the necessary data to process, which is reason #1. The CR field is necessary for the default node type of References, but it is completely missing from your data file. The problem is due to how you export records from the Web of Science. Check 5:24 in the video below. It's been a while but it is close enough for you to follow through: https://youtu.be/D75An6DqsfA?si=gSTqS7Q2abesJSFX
-
Try the latest version. It shows the largest 10 connected components by default.
-
Sometimes characters in a DOI may cause a problematic URL used in the KML file. Check for any more specific error messages. Correct them with a text editor. Then try again.
-
I have checked a couple of your data files. It seems they don't include cited references. That would explain it because of missing data. Make sure when you export from Scopus you select all the available fields for export.
-
You didn't do anything wrong. By default, CiteSpace shows clusters on the largest connected component only. If you want to see more clusters, use the menu Filters and adjust the setting for Show the Largest k Connnected Components, then repeat the process to refresh the display.
-
Check FAQ 3.5. You need to configure JVM to take advantage of your 16G.
-
It could be your locale. Check FAQ on how to modify JVM parameters. If you want to send me your data files, I can take a look at it for you.
-
Try this procedure: All in One (K) > timeline view and let me know what you get.
-
Try 6.2.R1 and see how it goes.
-
Thanks for the detailed information. Please try 6.2.R1. If you still have the same problem, send me these data files and I will look at them closely.
-
Please try the latest version. If there are still issues, you may provide the data file for me to take a close look.
-
See FAQ 3.2: https://citespace.podia.com/faq
-
There are two issues with your data file: 1. the file has the utf8 BOM encoding, which includes invisible utf chars () at the beginning of the file. To fix it, open the file with notepadd++ and save it as pure utf-8. 2. the EF field ends differently from the Scopus export I have. I have made it compatiable now in 6.1.R6. You can download it later today.
-
If you have installed Java separately, uninstall it (if you don't need it for other apps). Then install CiteSpace again, which contains Java 17.
-
If you have installed Java separately, uninstall it (if you don't need it by other apps). Then install CiteSpace again, which contains Java 17.
-
Thanks for your suggestion. I am making the following changes: 1. Add a new function to generate a template alias file, containing all the nodes in two columns separated by a tab. The file name is template_citespace.alias. 2. Visualize the network as usual, then generate the template from menu: Export > Nodes: Generate an Alias Template 3. Users can modify the template file as a plain text in Notepad++ or as a TSV file in Excel and save it as citespace.alias for CiteSpace to use. 4. Modify the template...
-
Thanks for your suggestion. I am making the following changes: 1. Add a new function to generate a template alias file, containing all the nodes in two columns separated by a tab. The file name is template_citespace.alias. 2. Visualize the network as usual, then generate the template from menu: Export > Nodes: Generate an Alias Template 3. Users can modify the template file as a plain text in Notepad++ or as a TSV file in Excel and save it as citespace.alias for CiteSpace to use. 4. Modify the template...
-
There was a minor issue. The fix will appear in the next version. In the meantime, see attached for the converted file.
-
If you can provide the original data files from Scopus, I will take a look as soon as I can.
-
Among other things, headings of some of the fields have changed in the data format, e.g., "Titles" used to be "Title". I have updated it and will be included in the next release. In the meantime, export the data in RIS from scopus and use the RIS converter.
-
Glad to hear it. Thanks for sharing your solution.
-
See FAQ 3.2 https://citespace.podia.com/faq
-
CiteSpace adds UNKNOWN if the author is missing. You can exclude it. Right click on the node and select exclude.
-
I tested your RIS files. No problem. A few things you can try. First, uninstall your Java 8. Then use the installer msi (assuming you are on Windows); if not, use dmg for mac. They contain java 17 so you don't need to install Java separately. Try this and let me know if you still have the problem.
-
It runs fine on my computer, including one of the data files provided by a user above. So I need to narrow down where the problem is? What is your locale, i.e., country and language? Is it on Windows 10？Do you have another version of Java on your computer? What is the full path of your folder with data files?
-
Converting Scopus data does not need the database. The following instructions are from the CiteSpace interface. RIS is preferred and update to date, whereas CSV is a secondary alternative and a revision is probably due. If you have multiple RIS files, perhaps you can try to divide and conquer and narrow down to problematic files and then share those with me Usage Step 1: Download data from Scopus Select all fields and save search results to the RIS format to a folder on your computer. You may also...
-
I tested the data files attached above, but didn't see this error. If any of you can repeat this error, please let me know.
-
That was a bug fixed in the most recent Advanced version. The fix should be released with the Basic version in a week or so.
-
For a cited reference, its year of publication is used. For a keyword, the first year of appearance is used.
-
Scopus exported one bodyless field, which caused the problem. When you export, you should select ALL the fields available. It should be fine with the Advanced version. I will update the Basic version in 1-2 weeks.
-
See FAQ: https://citespace.podia.com/faq
-
As it turns out, your files do not contain any cited references. See attached for converted files. You can use them with CiteSpace, but your options are limited because your data miss cited references, the most important part of the data. Typically, you search in Scopus and export multiple records to a single file. One record per file is okay, but for what is worth it would be a good idea to export cited references from Scopus.
-
I need more specific information. Check the cmd window and let me know what is shown there.
-
It looks your new files contain some ill-formatted data, e.g., a field without any value. I can filter out this type of data, but I haven't seen it with my test data, so not sure which fields may have this type of problems. If you can send me a sample file that was failed, I can take a close look.
-
Thanks for letting me know. Glad you resolved it.
-
You should do some homework on xmx to understand how it is supposed to behave.
-
right-click on the application > show package contents > app > modify the cfg file
-
Use the msi file.
-
Your setup is probably not quite right. I just converted your file without seeing any issues. See attached.
-
只要说明是CiteSpace的界面就可以。稿件接受以后可否分享文章？
-
The above post was out of date. The 2022 way is to download the dmg file for mac.
-
我一直建议用references为分析单位，作者为单位太空泛。 具体你的问题：考虑作者和机构同时用。
-
你把数据文件夹放在Desktop或My Documents之外的地方。路径里不包括这两个即可。
-
Here is the converted file.
-
I've just tested your ris file with 6.1.R2 Basic Built 7/4/2022. It runs smoothly with an accuracy of 98%. See attached: the converted file and the visual.
-
If you download the zip file, you can modify the batch file to optimize JVM parameters. The installer is limited to use 65-75% of your RAM.
-
I'm posting a new version 6.1.R2 Built 6/20/2022. Cluster labels should be more readable. See attached for example.
-
I will add these two to my to-do list. For the gml case, what was the original data source, WoS? Can you find the error message and the corresponding lines in the gml file?
-
Attached is the converted file from yours using the same version. I will see if it needs more tweaks.
-
It needs an update. I have just uploaded a new version (built 5/19/2022). That should work.
-
Yes, now I release CiteSpace at two levels: a Basic version and an Advanced version. The Basic version is a much simplified but sufficient set of functions with a focus on the fundamental document co-citation analysis. I strongly encourage new users to work with this simplified version and get familiar with the basics before moving on to other types of more complex analyses, which are now grouped in the Advanced version. The Advanced version is bundled with my ebook How to Use CiteSpace. I notice...
-
Liam, please email me (cc345@drexel.edu) with your email.
-
I think I found the problem. WoS uses an extra layer of grouping on top of the original comma separated fields for references with Chinese origin (maybe other non-English languages as well). Here is one example: [杜傲 Du Ao], 2020, [生态学报, Acta Ecologica Sinica], V40, P7231 I will make a new version available for this over the weekend.
-
I have checked your data files. The duplicate identified in 6.1.R2 is indeed a duplicate from WoS (see the side-by-side comparison of the two records). They have the same DOI, but different UT. I've updated CiteSpace Advanced. You can try it. You may want to select all the available document types on the Duplicate Removal, i.e. Ariticle, Review, Editorial, Letter, and Proceedings. Book Reviews are excluded.
-
Thanks for checking. Could you share with me the following data files: 1. the original data 2. the one processed by 5.8.R3 3. the one processed by 6.1.R2 I will look into this.
-
Your supervisor's login can access all updates.
-
Issue with downloading cited refs from dimensions through citespace
-
The issue has been fixed in verions of 6.1.R1 and 6.1.R2 with built dates 4/4/2022 onwards.
-
The current version uses WoS categories only. Are you using 6.1.R1?
-
Thanks for your suggestions. Just added Save as PDF in 6.1.R1. SVG will be added in next version.
-
I will check this as well.
-
Thanks for letting me know. I will check this.
1 >
