You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, you should be able to cite that paper as [@s2id:6c1779a0c6791609987b6481428022a39a9baadd] (using the full SHA hash s2id) or as [@s2id:59877838] (using the Semantic Scholar Corpus ID number).
You're right, thanks for re-opening. The Semantic Scholar lookup (as a network request) is actually succeeding, but the citation plugin currently quits if there is no corresponding DOI. (S2 lookups for papers with DOIs should work.) I'll leave this open until we decide if/how we want to handle the creation of CSL-JSON citation objects from S2 data alone.
I've run into some papers I want to cite that don't seem to have DOIs (ex: https://www.semanticscholar.org/paper/The-Grail-System-Implementation-Ellis-Heafner/6c1779a0c6791609987b6481428022a39a9baadd). It looks like Semantic Scholar still has data on these papers accessible through its API. But I think Living Papers ultimately always looks up data via DOI.
Is it practical to use Semantic Scholar when DOIs aren't available? Or are we relying on a lot of DOI-specific machinery?
(Naturally, I could always just get a BibTeX citation and put it into my document by hand. Just curious about automation!)
The text was updated successfully, but these errors were encountered: