This is a WordPress plugin for displaying data from the public scope of multiple ORCID profiles on pages, posts, and sites. It's a successor to ORCID Data Block. It does not require registering or authenticating an ORCID account. The only requirement is a valid 16-digit ORCID iD.
This work is funded by the ORCID Global Participation Fund.
- Provides a Gutenberg block in the WordPress block editor that allows users to
- specify which sections are shown from their ORCID profiles
- specify which items are shown within sections
- Allows different ORCID profiles to be used in multiple blocks on the same post/page/site
- Info will remain automatically up-to-date with ORCID
- All languages currently supported by ORCID will be supported (in progress)
- Accessible to those with disabilities
The following details information that’s available within the plugin according to each section’s record type. Each detail is listed in the order as it appears under each record. If any of this information is not supplied for a record in ORCID, it will not appear for that record in the plugin.
- Name
- Given Names
- Family Name
- Credit Name
- Other Names
- Biographical Information
- Websites & social links
- Role Title
- Organization Name
- Department Name
- Organization Address
- City
- Region
- Country
- Dates
- Start Date
- End Date
- School or Organization Name
- Degree
- School or Organization Address
- City
- Region
- Country
- Dates
- Start Date
- End Date
- Role Title
- Organization Name
- Department Name
- Organization Address
- City
- Region
- Country
- Dates
- Start Date
- End Date
- Title
- Organization Name
- Type
- Dates
- Start Date
- End Date
- Digital Object Identifier (DOI)
- Role Title
- Organization Name
- Department Name
- Organization Address
- City
- Region
- Country
- Dates
- Start Date
- End Date
- Role Title
- Organization Name
- Department Name
- Organization Address
- City
- Region
- Country
- Dates
- Start Date
- End Date
- Organization Name
- Role Title
- Department Name
- Review Location Address
- City
- Region
- Country
- Digital Object Identifier (DOI)
- Uniform Resource Locator (URL)
- International Standard Serial Number (ISSN)
- Review Source
- Completion Date
- Role Title
- Organization Name
- Department Name
- Organization Address
- City
- Region
- Country
- Digital Object Identifier (DOI)
- Dates
- Start Date
- End Date
- Organization Name
- Role Title
- Digital Object Identifier (DOI)
- Organization Address
- City
- Region
- Country
- Dates
- Start Date
- End Date
- Work Title
- Work Subtitle
- Journal Title
- Work Type
- Publication Date
- Digital Object Identifier (DOI)
- Visit this plugin's Releases page on GitHub:
- Download the zip file of the latest stable release.
- Visit the admin area of your WordPress installation.
- On the Plugins screen, click the "Add New Plugin" button.
- Click the "Upload Plugin" button.
- Choose the zip file that was previously downloaded.
- Click the "Install Now" button.
- Make sure the plugin is activated on your WordPress installation.
- This can be done on the Plugins screen.
- In a Gutenberg block editor, add a new block.
- There are multiple ways to add blocks.
- Search "ORCID Data Block 2" in the block browser and select it.
- Enter an ORCID iD in the plugin's inspector controls.
- An ORCID iD can be found on a user's ORCID record page.
- Make customizations in the plugin's inspector controls.
- Customize which sections are shown.
- Customize which items within sections are shown.
- Save as a draft or publish.
- Node Package Manager (npm)
- A WordPress installation
- A Docker-managed installation is recommended
- Clone this repository into the
pluginsdirectory of your WordPress installation. - In a command-line, navigate to the directory of this plugin.
- Install dependencies with
npm i. - Create the build directory and files with
npm run build.
- Fork a new branch from the
mainbranch. - Make changes to your forked branch.
- Submit changes by opening a pull request on the Pull requests page:
- Include a description of your changes in the pull request comment.
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
Examples of behavior that contributes to creating a positive environment include:
- Using welcoming and inclusive language Being respectful of differing
- viewpoints and experiences Gracefully accepting constructive criticism
- Focusing on what is best for the community Showing empathy towards other
- community members
Examples of unacceptable behavior by participants include:
- The use of sexualized language or imagery and unwelcome sexual attention or advances
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment Publishing others' private information, such as
- a physical or electronic address, without explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq