dojson: keywords from magpie should not be sent to legacy

inspirehep / inspire-next

The INSPIRE repo.

https://inspirehep.net

GNU General Public License v3.0

59 stars 69 forks source link

dojson: keywords from magpie should not be sent to legacy #2146

Closed michamos closed 7 years ago

michamos commented 7 years ago

keywords guessed by magpie end up in 653 instead of 695: https://inspirehep.net/search?ln=en&p=653%3Amagpie&of=hb&action_search=Search&sf=earliestdate&so=d.

EDIT by @kaplun: we should not send them back to legacy.

kaplun commented 7 years ago

This is a feature rather than a bug. It has been pointed out today at standup that magpie keywords are actually serving a different purpose than bibclassify keywords (discoverability of similar topics, Vs. exact search).

Since we should not change the behavior on legacy it's better not to send magpie keywords back to legacy at all..

michamos commented 7 years ago

fixed by #2217