#xitter

@LibSkrat Wow. *genuflects*

@AlexJLucier If you are using Crossref Metadata Search, we are aware it is struggling. We are trying to contain a botnet at the moment and hope CRMDS will back to normal soon. If it is any consolation, we're developing trust issues too.

Interested in building open scholarly infrastructure? We’re hiring a senior developer: https://www.crossref.org/jobs/2020-09-07-senior-software-developer/

@stuartayeates @CrossrefOrg @ORCID_Org Oops. That to be fixed. But note that the Crossref REST API (which you should be using if you are doing anything automated), *does* support ORCIDs expressed as URIs.

http://api.crossref.org/works?filter=orcid:https://orcid.org/0000-0003-1809-1062&select=title

@clayson_peter @CrossrefOrg Tnx. And GS shows 804. So @CrossrefOrg reply is stands. Typical pattern… PM looks at subset of content. GS looks at superset (including 12 versions of same doc).