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

Fall back to "embedded metadata" if the DOI translator fails? #685

Closed
jonovik opened this issue Mar 6, 2014 · 1 comment
Closed

Fall back to "embedded metadata" if the DOI translator fails? #685

jonovik opened this issue Mar 6, 2014 · 1 comment

Comments

@jonovik
Copy link

jonovik commented Mar 6, 2014

Would it be possible for Zotero in Firefox to automatically try to "Save to Zotero using embedded metadata" if the DOI translator fails? For example, PeerJ PrePrints such as https://peerj.com/preprints/273 default to the translator based on DOI, but gives the following error:
"Could not save item. An error occurred while saving this item. Check Known Translator Issues for more information."

The PeerJ staff researched the matter and pointed me to a workaround: right-click the Zotero icon in the Firefox address bar and choose "Save to Zotero using embedded metadata". This worked perfectly -- abstract, pdf and all. (The preprint becomes an item of type "report" rather than "journal article", which does make sense.)

However, it would be helpful if this was the default. The same PeerJ person pointed to a recent open issue on trouble with DOI translation at #632. Maybe the "embedded metadata" workaround could be added as a fallback solution?

@aurimasv
Copy link
Contributor

aurimasv commented Mar 6, 2014

It's not really related to #632 (though that could sometimes help alleviate the issue), but we have discussed merging DOI and Embedded Metadata (and to a lesser extent COinS and unAPI) into a single translator. I opened up a ticket (#686) to steer discussion in that direction.

In general though, while we appreciate users reporting errors and potential solutions, you should be reporting them to the Zotero forums. The GitHub issue tracker is dedicated for developer use after bugs/issues are confirmed and it is clear that a solution is needed.

Closing this ticket. For technical discussion on this issue please post to #686. For non-technical discussion, please post to the forums.

@aurimasv aurimasv closed this as completed Mar 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants