search

adsabs / bumblebee

🐝 Clever face for ADS
https://ui.adsabs.harvard.edu
GNU General Public License v2.0
38 stars 21 forks source link

Garbled rendering of records retrieved via execute_query #879

Open aaccomazzi opened 8 years ago

aaccomazzi commented 8 years ago

This seems to be an incorrect encoding problem, most likely in the underlying service rather than BB itself. Can be replicated by going to the "paper" search form (https://ui.adsabs.harvard.edu/#paper-form) and entering 2016arXiv160300906M in the bibcode field. You will see the problem in the encoding of the author names (and facets).

ehenneken commented 8 years ago

This also occurs when you export 2016arXiv160300906M from Classic to BBB. So, it seems to be related to whatever processes bigquery results and subsequently displays results. However, when a Classic library containing this record is imported into BBB, the author names are encoded correctly.

When 2016arXiv160300906M is exported for example together with 2016arXiv160400978T, the encoding is correct!

ehenneken commented 8 years ago

It is more complicated: when you export 2016arXiv160300906M together with 2016arXiv160400978T, the character encoding is correct in the results list. However, it is still incorrect in the author facet (and author filtering subsequently fails as a result)

The variable data in

https://github.com/adsabs/bumblebee/blob/master/src/js/components/query_mediator.js#L509

has the incorrectly encoded values in it...

It looks to me that execute_query from myads is returning unencoded (or incorrectly coded) data