Presentation at the 2016 February ORCID Outreach Meeting in Canberra, Australia (15-16 February 2016)

2. WHO ARE THE AAF?
• Established 2009
• Shared service owned and operated by the Australian R&E Sector
• Vital part of the Australian eResearch infrastructure landscape
• 96 organisations and institutions
• Supporting teaching, learning and research

3. Roles and Responsibilities
in the Consortium

4. CONSORTIUM
LEAD

5.  Trusted national provider
 NFP
 Sustainable
 Flexible with our subscriber
base (undertake or support R&E)
 We are in the business of
identity management
 Part of a global group all doing
the same thing
WHY THE
AAF?

6.  More cost effective together than alone
 Coordinated approach to implementation
 Wide adoption to maximise communication
and benefits of ORCID
 Build sustainability, long term commitment
and investment
 Local support
WHY A
CONSORTIUM?

8. WHERE ARE WE NOW?
40 Australian institutions
36 Universities
Heart Research Institute, CSIRO, ARC & NHMRC

9. HOW THE CONSORTIUM WORKS
Agreement
Australian ORCID
Consortium
Governance
Model
Governance
Committee
Advisory Group
Members
+ +

11.  Manage the membership process with ORCID
 Manage and support the on-boarding of Consortium members
 Be the central technical support contact to all members (Level
1) and manage Level 2 escalation to ORCID
 Act as the primary contact between ORCID and the members
for membership enquiries
 Maintain Consortium documentation and technical
documentation repositories.
ROLE OF THE LEAD
Provide local support

12. ORCID’S ROLE
Provide the infrastructure
 Train the Consortium Lead tech staff
 Tier 2 incident resolution support
 Vet integrations and issue production API credentials
 Regular check-ins with the leader, assistance with planning on
boarding webinars, and development of a consortium FAQ
 Provision of a Consortium summary page
 Provide usage statistics

13. MEMBER’S ROLE
Undertake the implementation work
• Follow best practice (see members.orcid.org)
 Perform all development and testing work in ORCID Sandbox environment
and review integration with consortium tech lead ORCID
 Keep your member API credentials secure
 Communicate with your researcher users
 Provide notification to the Consortium Lead when launching an integration or
starting a drive to encourage user registration to enable coordination across
new releases.
 If over 30 000 researchers will be asked to register in a period of less than one
month, the Member should notify the Consortium Leader in writing at least 35
days in advance.

14. WHO CAN
JOIN

15. Institutions must be located in and organised under the laws
of Australia, these organisations include:
 higher education institutions
 non-profit organisations
 government research institutes and funding agencies.
contact orcid@aaf.edu.au
WHO CAN JOIN

16. WANT TO
KNOW
MORE?
www.aaf.edu.au/orcid
orcid@aaf.edu.au