D2.2 IPSP Database_approved by the European Commission

This report provides a documentation of the dataset of Institutional Publishing Service Providers (IPSP) who responded to the 2023 DIAMAS survey. This 'IPSP database' is openly accessible as a dataset on Zenodo with a CC0 licence. The survey's aim was to map the current landscape of IPSPs in the European Research Area (ERA). The IPSP Scoping Report defines an Institutional Publishing Service Provider as a service unit that provides services to authors and publishers for institutional academic publishing. These services may be provided by the institutional publisher itself (in which case the institutional publisher is also the IPSP) or by other entities inside or outside the institution.

The final IPSP dataset, which this documentation accompanies contains completed and nearly completed surveys where respondents authorised the DIAMAS project to include that information. The design of the DIAMAS survey is fully discussed in the forthcoming Landscape Report (D2.3). This yielded a total of 704 responses included in the IPSP dataset. 44 IPSPs did not give permission to display their name or URL and were removed. Further cleaning yielded a final set of 651 IPSPs. Data from Turkey will be added at a later stage. Further checking led to the correction of nine IPSP names. IPSP names are rendered in various languages. All IPSP URLs were tested with a Google Apps script, resulting in changes to 149 URLs, and the removal of three that did not resolve. IPSPs were further subdivided into ERA regions: Eastern Europe, Northern Europe, Southern Europe, Western Europe, Northern Africa, and Southwest Asia. IPSP responses from outside the ERA are out of scope for the report but included in the dataset in the region 'rest of the world'.

Cleaning the IPSP database provided some important insights for the development of the IPSP registry: a publicly available registry of IPSPs who have authorized the DIAMAS project to use their information. The IPSP Registry will store and publish IPSP profile data in a structured and searchable manner. Lessons learned were that IPSP names should refer to the service and not to individuals; the IPSP Registry will have to contain the IPSP's name in its native language as well as in English; the IPSP's authority will have to be checked; contact emails and unambiguous URLs will have to be established in some cases. A number of instructions appeared to be ambiguous for survey respondents, and respondents did not always correctly self-identify as Institutional Publisher (IP) or Service Provider (SP).

The dataset provides the groundwork for the IPSP Registry to be built in WP4, identifying the IPSP profile details, delineating specifications for the platform hosting the registry, and allowing for a communication strategy to invite IPSPs to update their profile.