-
Notifications
You must be signed in to change notification settings - Fork 52
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
Redirect / Translator selection problem (DOI Resolver?) #48
Comments
hmm, tested it via curl, might have to do something with our environment... |
After a bit more testing, i found out that the reason might be similar to #49, except there is a different kind of redirect and testing is not restricted to ourselves. The problem occurs if you try to harvest the DOI URL instead of the URL mentioned above: Then you get this result: If you directly use the cambridge.org URL instead: You get the following result: Here you can see that the correct translator is chosen in the second case, and that e.g. tags have been parsed correctly. |
This is not related to #49, but rather to how translation server handles DOI URLs by looking them up in various metadata databases instead of fetching and translating the DOI resource directly. This is done since most of the time it produces more accurate metadata. |
We’re going to be fixing this, though — web translation should try the actual URL before it falls back to a DOI in the URL. |
Only happens for some websites, e.g.:
https://www.cambridge.org/core/journals/journal-of-law-and-religion/article/new-genealogy-of-religious-freedom/A76E3285DBD0EEF59A0EB82D4F4068E7
In Zotero you see the following tags (using Translator "Cambridge Core"):
Translation Server's returned JSON contains only an empty tags array.
The text was updated successfully, but these errors were encountered: