FAQs

All frequently asked questions

How to sign up under a (national) consortium arrangement

Frequently Asked Questions

last updated: 31 March 2025

page created: 14 September 2020

Spotlight on Q.19. What is a P1-message?

1. What is the OA Switchboard initiative and how did it get started?

The OA Switchboard initiative is a global, not-for-profit collaboration between funders, institutions and publishers to provide essential infrastructure, standards and back office services to facilitate the fulfilment of open access strategies across business models, policies and agreements. The goal is to achieve a breakthrough in the transformation of the market such that Open Access is supported as the predominant model of publication.

Throughout 2020, a project (overseen by OASPA, funded through a sponsorship model) was run to prepare for the OA Switchboard to go live as an operational solution. Following a successful project, as of January 2021, the OA Switchboard moved to an operational stage with a sustainable governance structure and funding model.

2. How does the OA Switchboard work?

The OA Switchboard enables funders – institutions – publishers to send, receive and respond to a pre-defined set of standardised messages (i.c. sets of metadata) between them.
Or, via their dedicated partner’s system, if applicable.

OA Switchboard acts as a 'message 'hub' and is not responsible for the content in the messages*).

*) See clauses 2.2 and 2.4 in the General Terms & Conditions: The Participant has the discretion to include data and information in Messages and in response Messages that Participant sends via the OA Switchboard... For the avoidance of doubt, OAS doesn’t have and doesn’t claim any ownership to or responsibility for Messages, Message Content or Reports. This data is to be governed by Applicable Laws that are outside the scope of OAS’s responsibility with respect to providing the Services.

3. Where can I find technical details?

The repository and documentation can be found here: https://bitbucket.org/oaswitchboard/api/.

In the root there is a readme with the documentation. Here is a direct link: https://bitbucket.org/oaswitchboard/api/src/master/README.md.

An explanation of the data fields in the message structure can be found here:

https://bitbucket.org/oaswitchboard/api/src/master/messages/

API documentation for recipients of OA Switchboard messages:

This is not part of the OA Switchboard API, therefore it is not documented. When a message comes into the OA Switchboard, the hub can notify the participant/receiver either via:

a) email notification, or

b) a webhook

That webhook option means that the participant will have to create the webhook and share the URL with us.

(How to create a webhook? That is a question that should be asked to the developers at the receiving end. It is the generic way of doing push messaging via internet. See also https://en.wikipedia.org/wiki/Webhook. Technically speaking it is an HTTP POST of a JSON data package.

What does that JSON look like? It is an OA Switchboard message, JSON, explained here, samples here.)

4. Why open source?

The reasons we choose open source:

By design: open source software licenses promote collaboration and sharing.
By mechanism: open source is an essential mechanism for building transparency and (therefore) trust. Open source ensures that all parties can validate that there are neutral and ‘accurate’ assessment algorithms, providing a guarantee that the OA Switchboard can be validated as the neutral host and facilitator it aspires to be.
No vendor lock-in, guaranteed exit scenario.
Cost: free license model.
It brings future security because others can build on our work.

5. What parts in the OA Switchboard are open source?

The following software is developed for us by our tech partner, and delivered to us under and Open Source license (MIT):

Core (message hub & data store): Open source code, fully transparent. The (public) repository and documentation can be found here: https://bitbucket.org/oaswitchboard/api/
Web application (with User Interface): developed and released as part of the Open Source Pubsweet framework. Possibility to contribute via community owned/shared/joint development

The following parts are developed for us by our tech partner, and delivered to us under an Open Source license (MIT). Contributions made available to the community for use and further development:

Connectors: Open source code and (where possible) part of an Open Source project like OJS (plugin), etc. The possibility to contribute via community owned/shared/joint development. Connectors are here: https://bitbucket.org/oaswitchboard/api/src/master/connectors
Message structure standard: an explanation of the data fields in the message structure can be found here: https://bitbucket.org/oaswitchboard/api/src/master/messages

All source code produced by our tech partner for us, is delivered to Stichting OA Switchboard under an Open Source license. To run it, there is a dependency on AWS Platform-as-a-Service:

Platform-as-a-Service offered by AWS (Amazon Web Services) is not open source (e.g. API gateway, VPC, server environments, Lambda serverless runtime, messaging services including SQS/SNS/SES)
Database-as-a-Service offered by AWS is open source, PostgreSQL enabled as a managed database service

6. How is scalability ensured?

The core message hub is highly scalable, especially due to the use of AWS (Amazon Web Services) micro services. AWS is by far the largest cloud provider (hosting almost all large sites in the world), and is scalable and secure. That is exactly the reason why we decided (in coordination with our Tech Advisors and Steering Committee) to not develop this piece ourselves. The above visual shows the message lifecycle for sending a message through the OA Switchboard. The AWS API gateway is linked to a serverless – Lambda validation function that invokes an SQS queue. This is what AWS says about this:

By default, SQS support up to 300 messages per second.
Lambda functions with an Amazon SQS trigger can scale up 60 additional instances per minute to a maximum of 1,000 concurrent invocations.

That is over 1 million messages per hour. And that is the default. If more volume and guarantees are required then an SLA is available, however we don’t expect to need it.

7. How is security and privacy ensured? Part 1: Via technology

Right from the start in the MVP we’ve ensured security and privacy in the OA Switchboard:

One user (one account) per participant. Authorisation is required, always.
The Sandbox is for testing purposes. The PRODuction will be made available later.
We store message header (all) and message body (optional).
If a participant integrates directly onto the API AND stores their own messages, there is no need to store them at OA Switchboard. *)
If a participant uses the User Interface OR does not store their own messages, the OA Switchboard will store them. *)
Only participants sending & receiving a message can retrieve the message body. OA Switchboard staff cannot access a participant’s message body. Unauthorized access is logged.

*) Note that if stakeholder 1 sends a message to stakeholder 2, and for stakeholder 1 point 4 is applicable, and for stakeholder 2 point 5 is applicable, the messages sent by stakeholder 1 are stored in the OA Switchboard.

8. How is security and privacy ensured? Part 2: Via contracts

All participants in OA Switchboard sign the same Service Agreement. The OA Switchboard Terms & Conditions are an integral part of the Service Agreement signed by participants, and the Test Terms of Use signed for trials. The EU version can be found here, and the non-EU version is here.

Relevant clauses:

4.1 Wherever legally required under Applicable Data Protection Laws, Participant will obtain any necessary permissions and consents from individuals, to disclose their personal information.

4.4 In consideration of Participant receiving Message Content from other Clients and Reports, Participant shall respect all applicable agreements between Participant and other Clients relevant to the Message Content, including but not limited to arrangements regarding confidential information and commercial terms, and Participant shall comply with Applicable Data Protection Laws.

5.5 OAS does not have and does not claim to have any ownership of or legal interest in Message Content and Reports, and OAS shall not use Message Content and Reports for any other purpose than delivering the Services to Clients. OAS explicitly declares to not store Message Content or Reports for the purpose of creating a database or derivative products...

7. Neither Party may assign, novate or sub-contract any or all of its rights under the Service Agreement without the prior written consent of the other Party.

If a funder/institution works with a vendor for a workflow support solution, we add an annex to the OA Switchboard Service Agreement, to be signed by funder/institution, their vendor and OA Switchboard.

Annex #: Assignment/subcontracting

In addition to Clause 7:

1. Participant chooses to work with <name & full address>, incorporated in <country> under company number <number> (“name”), and wishes to subcontract any or all of its rights under this Agreement to <name>, and OAS hereby approves this. Participant remains liable to OAS under this Agreement for all Responsibilities of Participant (clause 4), despite any subcontracting, and ensures <name> is fully informed and has legally accepted responsibility for this.

2. <name> is not allowed to use Messages, Message Content or Reports sent by or delivered to Participant for any other purpose than specified by Participant or for the benefit of any entity other than the Participant, as described under this Agreement.

3. Any breach of this Agreement by <name> will be regarded as a breach by Participant, and may lead to termination of the Agreement.

Annex # to be signed by <name>: ...

9. What is a ‘certified integrator’?

A ‘certified integrator’ is a party that, on behalf of a primary stakeholder (a funder, an institution, or a publisher) technically integrates with the OA Switchboard API in the standard message structure. A party can request to be awarded the ‘certificate’, after which a formal assessment and check will be done, and a decision taken.

The certification process is described in our Code, and includes:

the integration is operational for minimal 2 institutions and/or 2 funders and/or 2 publishers
the integration is operational for minimal 2 month, with sufficient volume
all direct stakeholders in (Stichting) OA Switchboard satisfied

Certified integrators, when approved, will be listed on the OA Switchboard website (here) with a summary of the specific integration for each case.

10. Who can get an account in the OA Switchboard?

Funders, institutions and publishers with a contract.

11. Do I have to be an OASPA member to become a customer of the OA Switchboard?

No. However, a screening (led by OASPA), to ensure we preserve the integrity of scholarship, will be part of the process.

The screening process involves elements of the OASPA membership application process, however if a publisher does not yet meet all of the OASPA criteria it will not necessarily mean exclusion from becoming an OA Switchboard customer and obtaining an account. Reasons for failing the screening for the OA Switchboard could be related to concerns about editorial process, and publishing ethics or behaviour. Ultimately, it is an OASPA decision, and the reasons in case of rejection will be clearly communicated to the party concerned only.

12. Why do I need to sign a contract to get an account?

To secure privacy and security. See questions above.

13. What does it cost?

The OA Switchboard operates on a self-sustaining economic/business model, whereby the operational and development cost are supported by service fees (with transparent pricing) for participating funders, institutions and publishers. We charge fees for development and maintenance of the infrastructure, and for participants to exchange information and communicate. Pricing is transparent and we keep fees as low as possible to offer an affordable solution.

We can keep OA Switchboard participants’ fees low, because we’re open source, tightly managed for costs, and the load is shared between funders, institutions and publishers.

There is an annual fixed (tiered) subscription fee. Contracts are from January-December only (though, first time start can be any time), and invoicing takes place in January of the year concerned.

Tech support is provided for free, for those integrating with the OA Switchboard API in the standard message structure.

2025 LIST PRICES (excl. VAT)

PUBLISHERS

Very small: EUR 50 (fixed subscription fee)
Small: EUR 1,000 (fixed subscription fee)
Medium: EUR 2,500 (fixed subscription fee)
Large: EUR 5,000 (fixed subscription fee)
Very large: EUR 15,000 (fixed subscription fee)

Size of publisher is determined by total annual publishing revenue (Small = below €500,000; Medium = between €500,000 and €5,000,000; Large = between €5,000,000 and €100,000,000; Very large = above €100,000,000).

INSTITUTIONS

Small: EUR 500 (fixed subscription fee)
Medium: EUR 1,000 (fixed subscription fee)
Large: EUR 2,500 (fixed subscription fee)
Very large: EUR 10,000 (fixed subscription fee)

Size of institution is determined by total research output (Very large = above 5% of global research output).

CONSORTIA/COUNTRY DEALS

Pricing for institutional consortia and/or all institutions in one country is based on research output (number of articles published per annum), as a percentage of global research output.

FUNDERS*

Small: EUR 1,000 (fixed subscription fee)
Medium: EUR 2,500 (fixed subscription fee)
Large: EUR 5,000 (fixed subscription fee)
Very large: EUR 15,000 (fixed subscription fee)

Size of funder is determined by total research output (Very large = above 5% of global research output).

* This will only be relevant for those funders who want to have an account in the OA Switchboard

14. How can get I get involved?

Please see here.

15. How is sustainability ensured?

For 2021 and beyond we are building everything in accordance with our core principles, and operating with a governance structure and funding model that will ensure sustainability and preserve the goals of the OA Switchboard into the future:

Neutrality and independence are preserved (separation of control and economic interest, no shareholders).
We operate a lightweight not-for-profit collaboration between funders, institutions and publishers, whereby the entity is ‘collectively controlled’ and the cost structure is transparent.
Industry-wide representation and collaboration in developing open source solutions and services.
We operate on a self-sustaining economic/business model, whereby the operational and development cost are supported by service fees (with transparent pricing) for participating funders, institutions and funders.
We support all OA business models, policies and types of scholarly output (provided they preserve the integrity of scholarship).
We are an intermediary, and observe the researcher (author) proposition and interaction of funders, institutions and publishers.

Read more on why this is all important here.

16. What's on the development roadmap?

Please check here.

17. How do I sign up under a (national) consortium arrangement?

For almost all (national) consortium arrangements, the member-level service fee is covered by the consortium, but members do need to sign their own Service Agreement. Sometimes, the consortium and OA Switchboard have agreed a consortium-specific agreement template that has been reviewed and signed-off by the consortium.

Please contact support@oaswitchboard.org to get your consortium member agreement prepared for signing. Your account will be activated within a matter of days.

18. How can publishers connect to OA Switchboard?

Participating publishers have four options to connect to OA Switchboard to compose and send messages, which are visualised here and described below:

Option 1: Manual

Publisher (or their vendor) staff logs-in to the OA Switchboard, and enters data via de User Interface, supported by online forms, to manually compose and send messages. These publisher participants sign the standard OA Switchboard Service Agreement and pay the annual fee (invoiced via OA Switchboard). Support is included in the OA Switchboard fee and is provided by OA Switchboard support staff.

Option 2: Standard API

Publisher connects with the application programming interface (API) themselves to compose and send messages in the standard message structure. Publisher is responsible for any partner or hosting contracts and cost required to connect to OA Switchboard*). These publisher participants sign the standard OA Switchboard Service Agreement and pay the annual fee (invoiced via OA Switchboard). Tech support is included in the OA Switchboard fee and is provided by OA Switchboard tech partner (ELITEX).

*) See clause 4.7 in the General Terms & Conditions: Participant is solely responsible for configuring its systems and routers to connect to the OA Switchboard API, if applicable, and for bearing any cost associated with that.

Option 3: Entry level connection to API (OA Switchboard serviced)

Publisher connects to OA Switchboard via an entry level connection to the API, to compose and send messages. This is a low-barrier onboarding service**) to participating publishers, offered and serviced by OA Switchboard, to enable publishers to get started quickly with P1-messages only. This option is offered as an add-on to OA Switchboard participation. The OA Switchboard will take care (with their tech partner ELITEX) of establishing an OA Switchboard hosted solution, consisting of one connection (most likely the Jats-XML feed). After initial development, there is basic maintenance and support (e.g. upgrading once a year in case of P1-message schema updates). These publisher participants sign the standard OA Switchboard Service Agreement, with an Annex to cover the connection and AWS hosting. They pay the regular annual OA Switchboard fee, plus***) a one-off set up and annual service fee - all serviced and invoiced via OA Switchboard.

**) A publisher may outgrow this level sooner or later. For instance, when their own staff and systems are at some point ready to move to Standard API as described above in Option 2. Or, when they develop the desire to send richer P1-messages (e.g. add data from additional sources such as their editorial or e-commerce system), and/or want to engage in E1-E2 messages, and/or feel the need for a private datastore.

***) See clause 3.5 in the General Terms & Conditions: ...If additional support is required, Client can agree additional fee with OAS by a separate written fee agreement.

Option 4: Solution to connect to API (third party serviced)

Publisher connects with the application programming interface (API) via a third party solution to compose and send messages in the standard message structure. Publisher is responsible for the relationship and the contract with their service provider, and for cost required to connect to OA Switchboard*). These publisher participants sign the standard OA Switchboard Service Agreement and pay the annual fee (invoiced via OA Switchboard). Tech support for their third party service provider is included in the OA Switchboard fee and is provided by OA Switchboard tech partner (ELITEX).

It’s publisher choice what service provider to go with. OA Switchboard has 'certified integrators' and has recognised our first as 'trusted solution provider'.

19. What is a P1-message?

A P1-message is a set of metadata related to a specific article publication.

The basic idea is that a publication notification, a P1-message, is sent by the publisher immediately upon version of record publication, to relevant stakeholders in that published article. You can think of institutions in the authors’ affiliations and research funders who funded the underlying research.

If there is a publication funder, that is the one who picks up the applicable publication charges, this is the one who would be the primary recipient of the P1-message.

We also support cases where there is no ‘direct’ publication funder, for instance in case of non-APC based models, such as ‘diamond’.

See infographic here and here.

Watch tutorial on 'Why do I receive this P1-message?' here.

Reporting Made Easy infographic May2023.JPG

20. Which data fields are in a P1-message?

An explanation of the data fields in the message structure can be found here.

Watch tutorial on 'Which data fields are in a P1-message?' here.

21. Why do I receive this P1-message?

Watch tutorial on 'Why do I receive this P1-message?' here.

22. Is there an API on the receiving end of a P1-message?

There is an API which allows you to receive P1 historical messages. It has some limitations and configuration parameters. You can retrieve messages in chunks as the API implements pagination.

Note that this API isn't suitable for receiving real-time updates at high frequency (e.g., every 5 seconds), as it's resource-intensive and response times can be significant. If you need to keep your message list updated in real-time, you should use the webhook option instead.

For maximum flexibility, you can combine both methods - using webhooks for real-time updates and the API for historical data retrieval when needed.

For implementation details, please see the "GET /v2/messages" section in the documentation at: https://bitbucket.org/oaswitchboard/api/src/master/