1. ORCID2SCOPUS2ORCID First steps

2. Scopus / Orcid integration Two steps Agile – using a wizard, “side-mounted” onto Scopus (to be delivered asap) Dedicated API – SCORCID – Q4, forms the foundation of the relationship going forward

3. From ORCID registration form and profile......... fetch ID, profile and publication list from Scopus

4. using the purpose-built wizard to find the profile(s) containing users’ work... using the purpose-built wizard to find the profile(s) containing users’ work

5. ... check their contents and correct if necessary

6. Data sent to Orcid

7. SCORCID Dedicated API Delivered later this year, probably to coincide with next release of Orcid Same functionality as Wizard, but provides for growth, baked into Scopus

8. Things that happened along the way XML schema updated, but not with # Found missing fields in schema Documentation could be better Or is it a case of RTFM? Is the M, F enough? Case studies, sample code, yes please We will support the tech group Active Github issues being discussed