In reply to
@csarven @CrossrefOrg @ORCID_Org Well, at moment, with exception of diff representations and generated elements like blank nodes, CiteBy counts, etc, Crossref doesn’t modify pub data. But… 1/n
In reply to
@csarven @CrossrefOrg @ORCID_Org Well, at moment, with exception of diff representations and generated elements like blank nodes, CiteBy counts, etc, Crossref doesn’t modify pub data. But… 1/n
In reply to
@csarven @CrossrefOrg These are blank nodes. You could ask publisher to deposit direct relationships. Other option is to make works in your @ORCID_Org record public do that people can follow DOI->ORCID->WebID.
In reply to
@arfon @_inundata @jenniferlin15 @CrossrefOrg is certainly not emoji-compatible. I hang my head in shame.
In reply to
@arfon @_inundata @jenniferlin15 *and* @CrossrefOrg API/ Search cannot find the item using emoji. I have reported bug: https://github.com/CrossRef/rest-api-doc/issues/423
In reply to
@arfon @_inundata @jenniferlin15 What’s more- @CrossrefOrg seem to only have *one* DOI with an emoji in the title or abstract. We really are a conservative industry. https://api.crossref.org/works/10.7146/pas.v29i72.19771