Skip to content
The home of development for the New Zealand ORCID Hub
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.keys common CA certificat for all environments... Jan 15, 2018
.travis Update Jan 15, 2018
archive create all directories via git repo Feb 14, 2019
conf consolidated attribute names... Jun 10, 2019
docs Merge pull request #692 from mohi7solanki/patch-1 May 28, 2019
gen-keys improved key generation... Feb 14, 2019
instance quickfix of sample configuration Mar 18, 2019
load_testing adjusted parameters... Aug 24, 2018
orcid_api Changes for ORCIDHUB-488; Adding ability for admins to add/delete/upd… May 14, 2019
orcid_api_v3 generated code with the config May 28, 2019
orcid_hub fixed form binding + cleaned up the code + a new entry goes at the top Jun 13, 2019
schemas swagger code generated with 3.0.8 swagger-generator May 27, 2019
tests Merge remote-tracking branch 'origin/prod' into ORCIDHUB-457 Jun 12, 2019
.conda.yml quickfix Jun 1, 2018
.coveragerc integreated V3... Jun 4, 2019
.coveralls.yml Code cleanup (#38) Apr 21, 2017
.deepsource.toml skip test sources... Jun 5, 2019
.dockerignore PosgtgreSQL bugfixes, rebuilt app image Feb 20, 2019
.editorconfig Orcidhub 361 (#598) Sep 28, 2018
.env.sample allow to expose the app ports Feb 14, 2019
.flake8 added property processing May 15, 2019
.gitattributes test git-attributes Jan 18, 2019
.gitignore Merge branch 'prod' into JG-install-docs-for-the-new-user May 7, 2019
.nojekyll perhaps we can use git pages... Nov 30, 2017
.readthedocs.yml try with conda Dec 1, 2017
.travis.yml reverted incorrect changes Jun 4, 2019
CNAME Create CNAME Nov 17, 2017
Dockerfile fixed Shibboleth installation and added testing form Exceptions Feb 12, 2019 Orcidhub 369 (#611) Oct 31, 2018
LICENSE Initial commit Feb 3, 2017 include swagger generated docs too Nov 28, 2017
Makefile added enqueuing of the record processing when the record gets updated... Apr 30, 2019 reverted incorrect changes Jun 4, 2019
README.rst fixed rst Mar 4, 2019
_config.yml Set theme jekyll-theme-minimal Nov 17, 2017
app.conf added section on the load testing... Aug 24, 2018
app.wsgi fixed pyflake8 Nov 17, 2017 Setting the visibilty to public if uploading file doesnt contain visi… Nov 20, 2017 Orcidhub 380 (#621) Nov 16, 2018
dev_requirements.txt integreated V3... Jun 4, 2019
docker-compose.yml added attribute mapping... Jun 10, 2019 suply DB URL for falsk command Feb 15, 2019 Code cleanup (#38) Apr 21, 2017 [skip ci] ... Nov 17, 2017
nginx.conf.sample Orcidhub 380 (#622) Nov 18, 2018 quickfix ... Sep 25, 2018 completed activete_all and reset_all and improved testing Apr 29, 2019
requirements.txt generated code with the config May 28, 2019
run-app quickfix: wrong SP domainname for prod... Apr 12, 2019 imroved formatting... Dec 4, 2017 fixed result_ttl and added more tests May 1, 2019
setup.cfg swagger code generated with 3.0.8 swagger-generator May 27, 2019 reverted incorrect changes Jun 4, 2019
tuakiri-metadata-cert.pem quickfix [skip ci] Jun 19, 2017
tuakiri-test-metadata-cert.pem Code cleanup (#38) Apr 21, 2017 V4 (#575) Aug 22, 2018

NZ-ORCID-Hub Build StatusCoverage StatusRTD Status

Work undertaken as part of the MBIE-led ORCID Working Group confirmed the view that New Zealand's research organisations exist in a wide range of sizes and ability to access IT support. As a consequence, the ability of organisations to respond to the ORCID Joint Statement of Principle that New Zealand adopt ORCID as the national researcher identifier also varied widely. In recognition that assisting all Consortia-eligible organisations to productively engage with ORCID would lead to national benefits, the Ministry has provided support for the development of the New Zealand ORCID Hub. As designed, the core function of the Hub is to provide all New Zealand ORCID Consortium members with the ability to make authoritative assertions of their relationship with researchers on the researcher's ORCID record, irrespective of their size or technical resource.

Throughout 2017 to June 2018, this project is being developed by a team at the University of Auckland under contract to the Royal Society of New Zealand. As the phenomena of small research organisations is not limited to New Zealand, it is a principle of the Hub's development that it be architected for use by the global ORCID community. To support this design principle, development is being pursued in as transparent a nature as possible, with the Hub itself being developed under the permissive MIT License.

The core development team at the University of Auckland consists of: jeff kennedy, Enterprise Architecture Manager; Radomirs Cirskis, ORCID Project Architect; and Roshan Pawar, ORCID Developer.

At this stage of the Hub's development it currently operates in two modes: Tuakiri-member organisation login; and file upload (typically associated with an email invitation for researchers with non-Tuakiri member organisations).

The Tuakiri login flow takes the information presented as part of the log in process and uses this to write a minimal affiliation of organisation, city, country and employment/education. The benefit of the Tuakiri-style is that the affiliation is written though researcher interaction, with anyone having credentials at a Tuakiri-member organisation able to initiate this process. This process is also very secure as the user's email and EPPN is authenticated as part of the exchange The File upload flow uses additional data provided by the organisation to write richer affiliations. If the user has already logged in with Tuakiri, the affiliation written replaces the minimal affiliation item. If the Hub has no record of the individual, an email invitation is sent asking permission to write to their ORCID record, with receipt of permission resulting in the record being updated. The advantage of this flow is that fewer user interactions are required, and the result is typically a richer affiliation. It's also the only way non-Tuakiri members have for interacting with the Hub. The disadvantage is that the ability of the user to receive the invitation is the only assurance of the user's identity. The Hub has been awarded the following Collect and Connect badges recognising it follows ORCID's recommendations for integrating with ORCID in these stages:


Consortium members who use the NZ ORCID Hub and who provide adequate communications to their users about what ORCID is, why its use is being encouraged within the organisation and how it is being used in the organisation’s internal systems are also eligible for these four badges.

For more information on the Hub's background and links to resources please visit the Hub page of the Royal Society Te Apārangi’s website.

Contact Details

Royal Society of New Zealand Phone: +64 (04) 472 7421 PO Box 598, Wellington 6140 New Zealand Email:

You can’t perform that action at this time.