Researcher visits or is directed to orcid.org and registers

for an ORCID ID

The researcher shares their ORCID ID with their employing institution, which adds employment information to their employee’s ORCID record.

The researcher applies for funding and shares their ORCID iD with the funder during the application process.

When the funding application succeeds, the funder registers a DOI for the grant, including metadata about related policies etc, and adds information about the award to the researcher’s ORCID record and captures RAiD for project and associated projects

Funders and employers should maintain lists of grants eligible for APC etc. support and capture ORCID IDs for eligible researchers wherever possible

The researcher checks the eligibility of publication venues for their work before submitting it to a journal and/or pre-print server

The researcher signs in to their ORCID account AND the employer requests permission to add information to the ORCID record AND the employer adds an employment affiliation to the ORCID record including its ROR

Funder requests ORCID ID AND researcher authenticates the ID AND funder requests permission to add information to the researcher’s ORCID record.

Funder adds a funding reference to the grantee’s ORCID record including grant DOI and the funder’s ROR AND institutions update RAiDs with grant DOIs

Upload/
deposit

The repository/server collects the researcher’s ORCID iD during article submission and queries the ORCID records for other PIDs and metadata.

Repository/server collects authenticated ORCID IDs for all authors/contributors AND queries ORCID record for associated PIDs AND resolves PIDs to gather necessary metadata

Repository/server provides a simple interface to help the researcher to confirm links between employment and funding information and the article being submitted

The repository/server registers a DOI for the
uploaded pre-print

Crossref /DataCite detect the researcher’s ORCID iD in the article metadata and automatically updates the researcher’s ORCID record with the article citation.

Researchers can either select information from the lists presented to them, or manually add information that is missing AND the repository/server adds any DOI(s) for grant(s) to item metadata.

PID providers to offer search and lookup tools to facilitate this process

ORCID IDs, ROR IDs etc. and licensing information are included in article metadata registered with Crossref

Authors grant Crossref permission to update their ORCID record AND publishers include ORCID IDs in article metadata sent to Crossref during DOI registration

The publisher collects the researcher’s ORCID iD during article submission and queries the ORCID records for other PIDs and metadata.

This requires the publisher to have an ORCID integration in their manuscript tracking system (MTS) AND the MTS will need to resolve the PIDs found in the ORCID record to expand the metadata available to the researcher and publisher at this point.

The publisher provides a simple interface to help the researcher to confirm links between employment and funding information and the article being submitted

The publisher harvests co-author names from RAiD records for project collaborators.

Publisher collects DOIs for pre-prints and any other previous versions of the article

The publisher looks up the funder’s open access policy, and what the terms of that policy are.

MTS displays information from ORCID records, and other data sources like the Crossref Grant ID data or the relevant organisation identifier registry AND Researchers either select information from the lists presented to them, or manually add information that is missing AND the publisher adds the DOI(s) for the grant(s) and RORs for affiliations to article metadata.

Publisher system queries RAiD registry either directly via author-provided RAiD or using submitting author’s ORCID ID

Query DOI registries for associated items using article metadata and author ORCID IDs

PID providers to offer search and lookup tools to facilitate this process

The publisher checks to see if the funder(s) or institution(s) linked to the submitted article are participating in a ‘read and publish’, transformative agreement or equivalent

The publisher (re)directs the article to the publishing options available which match the open access policy

Query grant ID metadata for policy terms either directly or via an enhanced SHERPA/FACT service.

Match ROR IDs for funder or employer or other affiliations AND grant DOIs to lists of participating organisations

EITHER query grant ID metadata for policy terms directly OR via an enhanced SHERPA/FACT service OR OA Switchboard as appropriate.

Author information (previous grants, outputs, data, etc.) shared with reviewers depending on open/blind peer review and in line with journal policies

Reviewer signs in to their ORCID account, publisher requests permission to read information from, and add information to, their ORCID record

Publisher system queries DOI registries and ORCID records for past co-authorships ROR to disambiguate reviewer and investigator affiliations AND RAiD for past collaborations AND editors check for COIs etc.

Publisher registers DOI for review report and includes DOI for article and ORCID ID for reviewer in metadata

Publisher system reuses existing data on grant awards and outputs associated with the author, reviewer(s) and
their organisation(s)

Add credit for the peer review to the reviewer’s
ORCID record

ORCID IDs, ROR IDs DOIs for previous versions and associated datasets etc. PLUS Licensing metadata are included in article metadata registered with Crossref

The publisher sends an invoice for publication charges to the employing institution or funder as appropriate, based on the eligibility checks already undertaken

ROR (used for affiliation) mapped to Ringgold (used for subs/payment management AND Funders should include APC payment guidance in grant metadata (e.g. if they pay directly, or if the cost of APCs is factored in to the grant and should be handled at the institutional level).

The publisher collects the researcher’s ORCID iD during article submission and queries the ORCID records for other PIDs and metadata.

This requires the publisher to have an ORCID integration in their manuscript tracking system (MTS) AND the MTS will need to resolve the PIDs found in the ORCID record to expand the metadata available to the researcher and publisher at this point.

The publisher provides a simple interface to help the researcher to confirm links between employment and funding information and the article being submitted

The publisher harvests co-author names from RAiD records for project collaborators.

Publisher collects DOIs for pre-prints and any other previous versions of the article

The publisher looks up the funder’s open access policy, and what the terms of that policy are.

MTS displays information from ORCID records, and other data sources like the Crossref Grant ID data or the relevant organisation identifier registry AND Researchers either select information from the lists presented to them, or manually add information that is missing AND the publisher adds the DOI(s) for the grant(s) and RORs for affiliations to article metadata.

Publisher system queries RAiD registry either directly via author-provided RAiD or using submitting author’s ORCID ID

Query DOI registries for associated items using article metadata and author ORCID IDs

PID providers to offer search and lookup tools to facilitate this process

The publisher checks to see if the funder(s) or institution(s) linked to the submitted article are participating in a ‘read and publish’, transformative agreement or equivalent

The publisher (re)directs the article to the publishing options available which match the open access policy AND/OR warns the researcher that publication in subscription journals may not meet the terms of the funder policy.

Query grant ID metadata for policy terms either directly or via an enhanced SHERPA/FACT service.

Match ROR IDs for funder or employer or other affiliations AND grant DOIs to lists of participating organisations

EITHER query grant ID metadata for policy terms directly OR via an enhanced SHERPA/FACT service OR OA Switchboard as appropriate.

Author information (previous grants, outputs, data, etc.) shared with reviewers depending on open/blind peer review and in line with journal policies

Reviewer signs in to their ORCID account, publisher requests permission to read information from, and add information to, their ORCID record

Publisher system queries DOI registries and ORCID records for past co-authorships ROR to disambiguate reviewer and investigator affiliations AND RAiD for past collaborations AND editors check for COIs etc.

Publisher registers DOI for review report and includes DOI for article and ORCID ID for reviewer in metadata

Publisher system reuses existing data on grant awards and outputs associated with the author, reviewer(s) and
their organisation(s)

Add credit for the peer review to the reviewer’s
ORCID record

The publisher registers a DOI for the accepted article and includes links to previous known versions in the metadata.

ORCID IDs, ROR IDs etc. are included in article metadata registered with Crossref AND DOIs for pre-prints/AAMs etc when available AND licensing information included in
DOI metadata

Post-publication

Article publication notifications sent to all organisations associated with all authors via OA Switchboard, Publications Router or other notification service

Services harvest PIDs from output metadata and from PID registries and channel notifications to participating organisations that offer a match

Crossref detects the researcher’s ORCID iD in the article metadata and automatically updates the researcher’s ORCID record with the article citation.

Funder and employing institutions’ systems are notified that the researcher has published a new article

Reporting systems at the funder and/or institution pull in complete metadata about the article, including the funding acknowledgement, and verify that the open access policy has been fully complied with.

Authors grant Crossref permission to update their ORCID record AND publishers include ORCID IDs in article metadata sent to Crossref during DOI registration

EITHER organisations use ORCID notifications for new changes to their researchers’ ORCID records OR they query their list of affiliated IDs periodically

Reporting systems harvest article metadata including PIDs and link to projects etc. AND check license information in article DOI metadata

Pre-print updates

Repository/server adds DOI for publisher’s Version of Record (VoR) to pre-print metadata

Metadata enriched with additional PID relationships from article metadata

Links made in third party systems between versions of outputs passed upstream and added to item metadata

Associated PIDs pulled in from VOR metadata OR added via lookup in repository interface

Links made in reporting platforms, publications management systems etc or in ORCID and RAiD records communicated as suggested updates to DOI registries

Repository deposit

The funder and employing institutions send a message to the researcher asking them to deposit their AAM in a

compliant repository.

Funder/employer systems respond to addition of new DOI in ORCID record at previous step

The researcher deposits their AAM and verifies the metadata that matches that of the publisher’s Version of Record (VoR).

The repository registers a DOI for the AAM and records it as a version of the VoR

Associated PIDs pulled in from VOR metadata OR added via lookup in repository interface AND metadata pulled in from ORCID to facilitate repository deposit

AAM DOI registered and link to VOR recorded in metadata AND if multiple repositories hold the AAM use ‘IsIdenticalTo’ relationship in metadata to link to any other known repository holdings to capture full reach of content

Reporting systems at the funder and/or institution pull in complete metadata about the article, including the funding acknowledgement, and verify that the open access policy has been fully complied with.

PIDs and metadata (including licensing information) harvested from repository feeds OR from PID registries

EITHER repositories use existing ORCID write permissions OR repository requests permission at deposit

Discovery and indexing

Content metadata distributed to abstracting and indexing systems, citation databases, aggregators, analytics

platforms etc.

Version DOIs linked and used for comprehensive metadata and interaction analysis

Publishers and repositories ensure retractions have

maximum reach

Content platforms register DOIs for errata and corrigenda AND include relationships to published versions in metadata AND update original publication metadata with link

to correction

Content in repositories and publisher platforms should deploy Crossmark in PDFs AND generate metadata that contains all the PIDs etc. associated with the

original publication