ORCID was founded on values of openness and collaboration. In order to ensure we are able to deliver the most value to our researchers and the organizations that support them, we rely on community-wide collaboration to guide us in developing new features and functionality for the ORCID Registry, APIs, and websites.
ORCID welcomes feedback and participation from anyone in our community interested in contributing to the development of ORCID Registry and APIs.
Once you get familiar with your own record and start using it to save time with a number of administrative tasks in your career (i.e., submitting manuscripts to journals, applying for funding,) we welcome you to share your suggestions on how to improve the ORCID registry in a few different ways:
- First, read about our mission.
- Tweet us, using the hashtag #ORCIDfeedback,
- Join the ORCID API users mailing list,
- Email us,
- Share your ideas in our Product Interest Group,
- Participate in Working Groups, or
- Tell us in person at events!
Track our progress
Once bugs are reported and new features are requested, we decide which ones to put on our roadmap (find out more about how we decide here.) We have several public Trello boards for everyone to follow our progress:
- What we are working on now: Our Current Development Trello board, which has always been publicly available, shows what we are working on now.
- What’s on the horizon: Our Product Roadmap Trello board, launched in 2019, shows what we have committed to implement in the future.
- UI Improvements: Our User Feedback Trello board is focused on the development of our User Interface based on community feedback (UI).
- Community feedback from members and integrators: Our Member and Integrator Feedback Trello board captures feedback from the community that could assist in others in their own successful integrations.
For developers: contribute technically to ORCID
- Meet our open source contributors.
- Build integrations using the ORCID APIs.
- Join the ORCID API users mailing list,
- Review the latest code on GitHub.
- Review our technical documentation on GitHub.
- Create a GitHub issue to discuss contributing bug/feature patches.
- See what is on our current development board.