Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

odd zoom behaviour when using show_item parameter #44

Closed
paulmaxus opened this issue Nov 29, 2022 · 3 comments
Closed

odd zoom behaviour when using show_item parameter #44

paulmaxus opened this issue Nov 29, 2022 · 3 comments

Comments

@paulmaxus
Copy link

paulmaxus commented Nov 29, 2022

I've observed that when using the URL parameter show_item=x, the app zooms in on a node labeled y (x) instead of the node labeled x. I'm not familiar with the function levenSort, but it seems intuitively right to select the first item returned by the sort (line referenced below), so I'm wondering why I see the behaviour described above. The Levenshtein distance should be 0 for the exact match and I assumed sortedItems[0] would then return x.

const foundItem = sortedItems[0];

@neesjanvaneck
Copy link
Owner

@paulmaxus Could you please share an example that reproduces this issue? Thanks in advance!

@paulmaxus
Copy link
Author

paulmaxus commented Nov 29, 2022

@neesjanvaneck Yes, of course.
One example can be found in the citation network of journals example in the vosviewer docs.
When I use the parameter physical review the app zooms in on biophysical reviews instead on for instance physical review b which should have the smaller distance.

https://app.vosviewer.com/?json=https%3A%2F%2Fapp.vosviewer.com%2Fdata%2FCrossref_journal_citation_network_10000.json&show_item=physical%20review

--- EDIT

The better example is actually microbiology:

https://app.vosviewer.com/?json=https%3A%2F%2Fapp.vosviewer.com%2Fdata%2FCrossref_journal_citation_network_10000.json&show_item=microbiology

@neesjanvaneck
Copy link
Owner

Thanks again for reporting this issue @paulmaxus. I have fixed the issue in release 1.2.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants