![](/s/cache/13/6d/136d9254a6abfafcccbb319f84b9a802.png)
0
Fixed
parsing of url from mendeley does not consider multiple urls
Hi Christian
I discovered a subtle issue with the parsing of url that are retrieved through the mendeley api
If there are multiple urls stored with mendeley, bibase is creating a single url by concatenating the urls, rendering them unusable. Example :
http://dx.plos.org/10.1371/journal.pone.0086427%20... for http://www.mendeley.com/c/6115948791/p/14667/garde...
Can I suggest to look for "http://" and either delete all entries after the first or make multiple links? Alternatively, I think mendeley stores them in the url field of bibtex files separated by a space.
Thanks!
I discovered a subtle issue with the parsing of url that are retrieved through the mendeley api
If there are multiple urls stored with mendeley, bibase is creating a single url by concatenating the urls, rendering them unusable. Example :
http://dx.plos.org/10.1371/journal.pone.0086427%20... for http://www.mendeley.com/c/6115948791/p/14667/garde...
Can I suggest to look for "http://" and either delete all entries after the first or make multiple links? Alternatively, I think mendeley stores them in the url field of bibtex files separated by a space.
Thanks!
Answer
![](/s/cache/9f/de/9fde3bc085968e81d3666d4e5b0a4a4c.png)
0
Answer
Fixed
Christian Fritz 10 years ago
Thanks for reporting. This is fixed now. You may need to update your cache for it to show up (using the &nocache=1 link you got when creating your bibbase page, or by making a small change to your library and then reloading your bibbase page).
![](/s/cache/9f/de/9fde3bc085968e81d3666d4e5b0a4a4c.png)
Answer
Fixed
Thanks for reporting. This is fixed now. You may need to update your cache for it to show up (using the &nocache=1 link you got when creating your bibbase page, or by making a small change to your library and then reloading your bibbase page).
Customer support service by UserEcho