
Match & Deliver Programme
With this programme we are building on the OA Switchboard’s commitment to get publishers’ authoritative publication metadata to the right institution, every time. Among others, it aims to improve how free-text author affiliations are matched to the correct ROR ID. This will enable P1 messages to be delivered more accurately to the appropriate recipient(s) and more comprehensively to all relevant participants, helping research institutions better connect people, funding, research outputs, and organisations.
This page is the central reference for this initiative: what changed and what it means for you. If you have any questions, please contact OA Switchboard Support.
What we improved so far
Over the past years we conducted systematic analyses with partner institutions and consortia, publishers, and parties engaged in ROR-matching. These deep-dive investigations helped us to identify root causes, including for incorrectly delivered P1-messages, and for DOIs present in publisher reports that were not always appearing in OA Switchboard participant accounts.
As shared in our newsletters and discussed in our Client Advisory Board and Advisory Group meetings, addressing these issues has been the first priority as part of iteration 2026/#1 of our 2026 development roadmap. This included improved ROR matching and more generic improvements to deliver more and better P1 messages.
Improved ROR ID matching in OA Switchboard
We have implemented the improved ROR matching strategy for author affiliations for selected publishers, refined the input data we use, and adjusted how we interpret the results. We are now successfully using the new single-search strategy announced by ROR in December 2025. Read all about the "New Affiliation Matching Strategy in the ROR API".
"Not for me"
If you receive a P1 message that does not belong to your institution, click the not-for-me button in your OA Switchboard dashboard at the P1-message level to indicate that you received a P1 message in error and that the ROR ID matching may be incorrect. We will investigate the issue and work with the publisher and the ROR to improve matching accuracy going forward.
By reporting these cases, you contribute to a continuous improvement process that helps enhance matching quality and keeps pace with emerging standards and evolving industry practices.
Find information on how to use the not-for-me button here.

Publisher data resubmission
In-scope publishers are resubmitting all 2025 and year-to-date 2026 data so the improvements also apply to these previous publications. The resubmission is being carried out in phases over Q3 2026.
This means you will receive new P1 messages for articles you may already have notifications for, or you will receive P1 messages for articles published in the past that you never received a P1 message for yet. This is expected and intentional: the new messages deliver more accurately to the appropriate recipient(s) and more comprehensively to all relevant participants.
Why improvements require a publisher data resubmission
OA Switchboard is a metadata exchange hub. Improvements to logic in the hub only take effect on new messages. When a publisher sends a P1 message, the hub processes it in real time: it routes that message to the correct accounts. This happens once, at the moment the P1 message passes through. Messages that were processed under earlier rules remain as they were, unless the data is resubmitted and a new P1 message generated.
What you want to be aware of
You may notice an increase in the number of P1 messages you receive and more detail in the coverage of PIDs in your P1 messages. This is a positive change: it means better connecting people, funding, research outputs, and organisations.
Email alert pause
If you receive P1 notifications via email and would prefer not to receive individual alerts during the resubmission period, we can temporarily pause your email alerts at your request - contact support@oaswitchboard.org.
Automated workflows
If your institution receives P1 messages via webhook or API into a repository or CRIS, or ingest P1 email notifications into your systems, please review your ingestion rules to ensure the new P1 messages for older DOIs are handled appropriately and it can handle the volume. If your workflow auto-accepts messages, you may wish to temporarily adjust this to review the incoming data. Contact support@oaswitchboard.org if you need guidance.
How to get a clean view of your data after the resubmission
As improvements to logic in the hub only take effect on new messages, we advise you to always only consider the last P1-message for a certain DOI.
If you’re using automatic ingestion into your systems, make sure new P1-messages for the same DOI are taken into account, and ideally check if there are changes in the underlying metadata.
Should you access reports via your OA Switchboard dashboard, use the article report. It shows one row per unique DOI, using only the latest P1 message. If a P1 message has been resubmitted, the article report automatically shows the latest version. This is the simplest way to get a clean, deduplicated view of your data. See our tutorial on how to generate an article report.