D2.2 User Services Catalogue

Grant Agreement 101079792, RESILIENCE PPP D2.2 – User Services Catalogue Title of Deliverable: User Services Catalogue Deliverable Number: D2.2 Type of Data: Report Lead Beneficiary: KUL Publishing Status Public Last Revision Date: 27/11/2025 by: Marte De Leeuw Verification Date: 28/11/2025 by: Francesca Cadeddu Approval Date: [DD/MM/YYYY] by: [Name] Document Name: RESILIENCE_WP2_D2.2_UserServicesCatalogue_02.00_FINAL 1 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 Change History Version Number Date Status Name Summary of Main Changes 00.01 20/03/2024 DRAFT Initial Draft 00.02 30/04/2024 WORKING Working Version 00.03 21/05/2024 DRAFT First Revised Text 01.00 29/05/2024 FINAL Final Version 01.01 22/10/2025 WORKING Working Version 01.02 20/11/2025 DRAFT Draft Author(s) Name Beneficiary Role Marte De Leeuw KU Leuven WP2 Data Unit lead Roxanne Wyns KU Leuven Deputy director, WP2 Data Unit Lieneke Timpers KU Leuven WP2 member Dries Bosschaert KU Leuven WP2 lead Nyala Nauwelaerts KU Leuven WP2 member Alexandra Nusser INFAI WP2 member Distribution List Name Beneficiary Role All All 2 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 Table of Contents 1 Executive Summary....................................................................................................................6 2 Introduction...............................................................................................................................7 2.1 Purpose and Context........................................................................................................................7 2.2 Scope.............................................................................................................................................. 7 3 RESILIENCE Service Strategy......................................................................................................9 3.1 Guiding Principles............................................................................................................................9 3.2 A Service Catalogue Based on User Needs..................................................................................... 10 3.3 Usage of Digital Tools in the Study of Religion................................................................................11 3.4 The Diversity of the Study of Religion.............................................................................................13 3.5 Wider European context.................................................................................................................13 4 Core & Community Services.......................................................................................................15 4.1 The RESILIENCE Core Services...................................................................................................... 15 4.1.1 RESILIENCE Zenodo Community..........................................................................................16 4.1.2 ReIReSearch......................................................................................................................... 16 4.1.3 Trans-National Access (TNA).................................................................................................16 4.1.4 Training and Workshops........................................................................................................17 4.2 The RESILIENCE Community Services........................................................................................... 17 5 Implementation of the Service Dictionary...................................................................................19 5.1 The Service Description Template (SDT)........................................................................................ 19 5.1.1 At a Glance........................................................................................................................... 20 5.1.2 How to read the current Service Catalogue...........................................................................20 5.2 Categories and Activities............................................................................................................... 21 5.3 Access and Order Types................................................................................................................. 23 6 Onboarding of Services............................................................................................................. 25 6.1 Minimal Requirements...................................................................................................................25 6.2 RESILIENCE Service Level Readiness (RSRL)................................................................................. 25 6.3 Procedures for Onboarding............................................................................................................27 7 Next Steps...............................................................................................................................28 7.1 Integration with the SSHOC Open Marketplace............................................................................. 28 7.2 The HORTUS Platform...................................................................................................................30 7.3 Expanding / Improving the Catalogue.............................................................................................31 8 Conclusion............................................................................................................................... 32 9 Applicable Documents.............................................................................................................. 33 10 Reference Documents............................................................................................................. 34 3 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 List of Figures Figure 1: Supercategories & categories covered by Book Heritage Lab KU Leuven.................................... 22 List of Tables Table 1: Guiding Principles Implementation Measures............................................................................... 10 Table 2: Current Service Catalogue Metadata Fields.................................................................................. 21 Table 3: Access and Order Types Examples................................................................................................24 Table 4: Mapping Table SSHOC Metadata – RESILIENCE SDT...................................................................29 4 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 Acronyms Acronym Full Form AI Artificial Intelligence API Application Programming Interface BoD Board of Directors CESSDA Consortium of European Social Science Data Archives CLARIN Common Language Resources and Technology Infrastructure DARIAH Digital Research Infrastructure for the Arts and Humanities DOI Digital Object Identifier EOSC European Open Science Cloud ESFRI European Strategy Forum on Research Infrastructures FAIR Findable, Accessible, Interoperable, Reusable GenA General Assembly GLAM Galleries, Libraries, Archives, Museums HTR Handwritten Text Recognition IT Information Technology MDM Master Data Management OCR Optical Character Recognition OPERAS Open Scholarly Communication in the Social Sciences and Humanities OS Open Science OSCARS Open Science Clusters’ Action for Research & Society PPP Preparatory Phase Project RDM Research Data Management RSRL RESILIENCE Service Readiness Level RI Research Infrastructure RS Religious Studies SDT Service Description Template SSH Social Sciences and Humanities SSHOC Social Sciences and Humanities Open Cloud TNA Trans-National Access TRL Technology Readiness Level VRE Virtual Research Environment WP Work Package WU Data Working Unit Data 5 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 1 Executive Summary The D2.2 User Services Catalogue constitutes the first consolidated catalogue of services within RESILIENCE. It brings together an spreadsheet-based register of around 120 community (in-kind) services contributed by partners, each described through a concise Service Description Template (SDT) and supported by a living Service Dictionary that contains authoritative field definitions and controlled vocabularies. The catalogue is designed for clarity and ease of use: its accompanying legend (Service Dictionary, chapter 3) allows readers to interpret each column, distinguishing minimum from preferred fields for both discovery and data export. This deliverable operationalises the Service Strategy defined in RESILIENCE’s deliverable D2.1 by distinguishing Core Services from Community Services – the focus of the catalogue – and by introducing a governance model suited to a distributed research infrastructure. While Community Services are curated by partners and, in the next phase, National Nodes, the current Data Unit (future Service Office) is responsible for maintaining the SDT, controlled lists, and validation workflows. Quality, sustainability, and interoperability are enforced through minimal requirements and policies aligned with the D2.11 Master Data Management. Only services meeting a RESILIENCE Service Readiness Level (RSRL) of at least 7, and offering a stable landing page, helpdesk contact, and user documentation are listed publicly. The SDT follows the structure of the SSHOC Open Marketplace to ensure metadata compatibility, while the Service Dictionary preserves mappings between RESILIENCE and SSHOC fields, enabling seamless future federation with the EOSC EU Node. The onboarding process and the respective responsibilities for curation and maintenance are documented in full. Looking ahead, the next phase will focus on the operational implementation of the Service Catalogue: digitising the onboarding and quality-control processes, integrating the catalogue with the SSHOC Open Marketplace, publishing concise contributor and RSRL guidance alongside the Service Dictionary, and exposing the catalogue through the RESILIENCE HORTUS platform. Expansion through National Nodes will continue, accompanied by targeted RSRL elevation efforts to raise the maturity of selected high-value services. 6 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 2 Introduction 2.1 Purpose and Context In accordance with the Grant Agreement, Work Package 2 (WP2) was mandated to establish a User Service Catalogue that makes RESILIENCE services both findable and usable, and that lists only those services which have passed internal quality checks and are ready for operational use. This deliverable fulfills that objective by presenting a curated set of community services, described in a consistent manner and prepared for integration with the broader SSH and EOSC ecosystems.1 It also provides practical guidance on how to read the accompanying Excel catalogue, describes the onboarding workflow and governance, and refers readers to the living Service Dictionary for field definitions and controlled vocabularies. The D2.2 User Services Catalogue operationalises the framework set out in the D2.1 Services Preparation and Implementation Strategy2 and applies the metadata model developed in the D2.11 Master Data Management (MDM)3. Where D2.1 outlined the strategic principles of a distributed infrastructure—defining the distinction between Core and Community Services and the role of National Nodes—and D2.11 defined the Service Description Template (SDT), Service Readiness Level (RSRL), and metadata governance, the present deliverable translates those foundations into a concrete, export-ready catalogue. The catalogue is accompanied by a living Service Dictionary4, derived from Chapter 5 of D2.11 MDM. This dictionary is the authoritative reference for SDT field definitions, controlled vocabularies, and the adapted RSRL scale. It is the single source of truth for catalogue semantics and technical mappings. In case of divergence between D2.11 and the Dictionary, the latter takes precedence. 2.2 Scope The first two chapters of this deliverable outline the implementation context for RESILIENCE as a distributed research infrastructure where services are delivered primarily through partners and, in the 4 RESILIENCE Service Dictionary, https://doi.org/10.5281/zenodo.17741280 3 RESILIENCE PPP – D2.11 Master Data Management, https://doi.org/10.5281/zenodo.15599787 2 RESILIENCE PPP – D2.1 Service Preparation and Implementation Strategy, https://doi.org/10.5281/zenodo.16568333 1 GRANT AGREEMENT, Project: 101079792 — RESILIENCE PPP — HORIZON-INFRA-2021-DEV-02, Description of The Action (Part A), p.7. 7 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 future, National Nodes. In chapter 3, we explain the catalogue’s coverage, its emphasis on transparency and maturity, and the practical application of the Service Strategy’s nine guiding principles. It also outlines the discipline-specific needs of the study of religion and shows how interoperability with SSH/EOSC has guided design choices. Chapter 4 distinguishes Core Services from Community Services—the former summarised for completeness, the latter fully listed and described. Chapter 5 serves as a user guide to the catalogue, explaining its structure, metadata schema, and relationships to the D2.11 MDM and Service Dictionary. Chapter 6 defines minimal inclusion requirements and onboarding procedures, and Chapter 7 sets out next steps for digitisation, integration, and expansion of the catalogue. Together, these later chapters establish the operational basis for the RESILIENCE Service Catalogue and prepare it for federation with the SSHOC Open Marketplace and, ultimately, the EOSC EU Node. The accompanying Excel file is the authoritative listing for the current RESILIENCE Community Services. References in regards to the SDT point to the Service Dictionary (normative specification) and earlier deliverables (strategy and metadata design) to ensure traceability without repeating prior material. 8 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 3 RESILIENCE Service Strategy 3.1 Guiding Principles RESILIENCE’s service strategy — defined during the PPP (06/2022-05/2026) and documented in D2.1 — aims to deliver high-quality, sustainable, and transparent services that are findable and accessible, aligned with FAIR principles, and driven by user needs from the study-of-religion community. The catalogue is the central operational instrument to realise this strategy. Rather than re-stating theory, this deliverable applies it: it explains the metadata profile we use (SDT), the maturity requirements (RSRL), the onboarding workflow, and the governance that keeps records accurate and interoperable. The Service Catalogue is a curated, export-ready catalogue of community services. Each entry follows the streamlined SDT and is accompanied by the living Service Dictionary, which contains authoritative definitions and controlled vocabularies. This structure enhances discovery and reuse, supports federation with SSHOC / EOSC without the need for re-cataloguing, and ensures long-term transparency regarding service maturity. While the Data Unit manages the template, lists, and workflow, the partners (and future National Nodes) provide and maintain the community services. Implementation of the guiding principles defined in D2.1 has been achieved through specific measures: Guiding Principle Implementation 1. Expertise and Excellence Development of RSRL Scale; currently, only services reaching level 7 or higher are included. 2. Research output should be FAIR & sustainable Mandatory helpdesk or support contact; repositories rely on trusted, FAIR-compliant infrastructures identified in D2.4 Data Management Plan5. 3. Transparency Creation of the Data and Service Dictionary, clarifying SDT fields and illustrating the RSRL scale through examples. 4. Clear and concrete Service Description Standardised, concise descriptions following D2.11 guidelines; resulting in the living Service Dictionary accompanying the catalogue. 5. Stakeholder-driven Future expansion of community services will be coordinated by National Nodes based on our community’s needs. 6. Findable and accessible Persistent identifiers and a machine-readable SDT aligned with recognised ontologies. 5 RESILIENCE PPP – D2.4 Data Management Plan (DMP), https://doi.org/10.5281/zenodo.17224714 9 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 Our community’s specific user needs directly shaped the RESILIENCE Core Services, which are presented in the subsections below in the same order. 4.1.1 RESILIENCE Zenodo Community The RESILIENCE community on Zenodo9 for FAIR data publication. This general-purpose open repository allows researchers to deposit all research-related items, which are linked to a DOI and published under an open license. See the D2.4 Data Management Plan10 for more information. 4.1.2 ReIReSearch The online discovery platform ReIReSearch11 where disparate digital resources and databases are searchable in a unified and standardized way thanks to extensive metadata provided by partner institutions. The platform includes an intuitive search interface to search collections of manuscripts, documents, and rare books within the scope of the study of religion. See Chapter 6 of the D.11 Master Data Management Plan for more information. 4.1.3 Trans-National Access (TNA) The RESILIENCE TNA Programme12 offers physical and virtual access across national borders to the most significant tools and sources in those disciplines related to the study of religion. TNA offers support and expertise for research stays at so-called TNA Hosts13: European institutions and libraries that possess unique collections and expertise on the study of religion as a whole. This includes, but is not limited to, the sources and expertise needed to conduct research on the contemporary and historical study of the world’s major and minor religions, as well as new religious movements, secularization and non-religious worldviews, indigenous religions across the globe, and more. Its aim is to facilitate and foster easy access to sources, resources, expertise and services for researchers in the study of religion, while ensuring an efficient access workflow and a single-entry point via the RESILIENCE homepage and central helpdesk. This offer thus combines access to data of major European 13 TNA Host,; https://www.resilience-ri.eu/transnational-access-hosts/ 12 TNA Landing Page, https://www.resilience-ri.eu/tna_fellowship_programme/ 11 ReIReSearch, https://reiresearch.eu/#/ 10 RESILIENCE PPP D2.4 – Data Management Plan, https://zenodo.org/records/17224714 9 RESILIENCE Community on Zenodo, https://zenodo.org/communities/resilience/records?q=&l=list&p=1&s=10 16 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 research institutions together with access to a vast network of experts for the study of religion. RESILIENCE therefore aims to not only attract academic institutions, but also policy makers, religious institutions, and independent research institutes. In short, the role of the RESILIENCE TNA program is fundamentally a facilitating one, benefiting both host and recipient, and supported by RESILIENCE’s excellent professional network. See D2.5 TNA Services Management Plan14 for a full description of the programme. A report on the TNA activities of the RESILIENCE Preparatory Phase will be published on 30 April 2026. 4.1.4 Training and Workshops RESILIENCE is developing a user-centred training programme that focuses on providing courses that will bridge the gap between what is already available and what our users need. Training needs in the context of RESILIENCE and the study of religion focus on four key areas: 1. Training in already existing RESILIENCE Services such as TNA and ReIReSearch 2. Training in new skills emerging from unforeseen advancements in research and the digital humanities, irrespective of whether these are connected to RESILIENCE services or tools or not. 3. Training in Core Skills and Competences for the study of religion as a RESILIENCE service arising from expressed needs of our target audience. These include methodological competences in study of religion; ethical and cultural sensitivity and awareness; challenges of research in politically and religiously sensitive contexts, and more. 4. Training in Basic/Transversal Skills required for doing research in the field, such as IT and Digital skills, language skills, data management skills, computational skills, and more. More information can be found in the D2.6 Training Services Management Plan15. 4.2 The RESILIENCE Community Services Community services are in-kind contributions from consortium partners and their local networks, currently coordinated through the consortium partners and in the future via National Nodes. Partners or Nodes identify regional resources, build local consortia, and contribute services and expertise to the RI; they also 15 RESILIENCE PPP D2.6 – Training Services Management Plan, https://zenodo.org/records/16568496 14 RESILIENCE PPP D2.5 – TNA Services Management Plan, https://zenodo.org/records/17601848 17 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 align with other national SSH consortia (e.g., DARIAH, CLARIN, CESSDA) to avoid duplication and maximise reuse. Partners / Nodes have (and will) curate their own community services, request updates from providers, and notify changes in RSRL or Access conditions. The Data Unit (future service team) stewards the SDT and controlled lists, validates records for consistency, and maintains a change log aligned with batched updates. This split of responsibilities follows the distributed RI model set in D2.1. At publication, the catalogue contains 119 services across 14 partner institutions. By focusing on each partner’s strengths, we were able to compose an expansive and highly qualitative Service Catalogue, unique in the field of the study of religion. To illustrate the breadth of in-kind contributions, the following examples showcase partner strengths (non-exhaustive): - Ecole Pratique des Hautes Etudes: physical collections and on-site consultation workflows. - University of Münster and the Tübingen University Library: specialized information services for theology and the study of religion, and the data aggregator IxTheo. - Fondazione per le scienze religiose Giovanni XXIII: extensive archival resources and libraries on a wide range of RS sources and manuscripts. - Sofia University St. Kliment Ohridski: specialises in Bulgarian Medieval Written Heritage and offers access to Histdict and e-Medievalia, which are unique sets of digital tools that create new opportunities for Slavic and Byzantine studies. - Volos Academy for Theological Studies: scholarly expertise - University of Sarajevo: domain-specific datasets, tools, or archives. - University of Leuven: offers major ecclesiastical archives and digitisation services. 18 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 5 Implementation of the Service Dictionary The Master Data Management (D2.11) deliverable introduced the layered approach of a Data Dictionary and Service Dictionary to improve interoperability and discoverability across the RS community. The Service Dictionary, including the updated Service Description Template (SDT) provides the standard framework for describing every RESILIENCE service. Since then we have extracted this dictionary into a separate document that lives alongside the User Services Catalogue. Chapter 5 explains how those components are applied in practice within the catalogue and how the associated governance ensures consistency and reliability. To reduce the burden on service providers, the SDT evolved from a comprehensive, EOSC-profile-based pilot to a concise four-tier template – minimum, preferred, technical, and optional fields. This refinement, informed by partner feedback and the OSCARS benchmark16, reduced complexity while maintaining full interoperability. Detailed field definitions and code lists are maintained in the Service Dictionary, which prevails wherever wording diverges from D2.11. 5.1 The Service Description Template (SDT) After finalising the operational version of the SDT, partner services were collected following the nine guiding principles from the Service Strategy. The steps taken include: ● Collection of basic information of potentially interesting services from partners, regardless of TRL; only name, link, description and internal contact information was required at that point ● Once the customized RESILIENCE SRL Scale was finished, two one-pagers with its explanation and examples was distributed so partners could assign a level to their own services ● Based on those RSRL levels, the presence of a stable link, and helpdesk/customer support, services were selected to be included in the catalogue ● Afterwards followed the collection of additional minimum and preferred fields In the following sections, we apply the new SDT operationally to our current service catalogue Excel and clarify category and access types for end-users. 16 OSCARS D2.1 - Clusters' Services and Data Sources Portfolios, https://doi.org/10.5281/zenodo.14881627 19 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 5.1.1 At a Glance The different field types: ● Minimum (12 fields) – mandatory for catalogue inclusion: Name, Resource Organisation, Webpage Description, Category, Access Type, Order Type, Language, RSRL, Contact, Helpdesk information. ● Preferred (8 fields) – enrich discovery but are not gating: Sub-category, Access Mode, Access Process, Access Policy, Target Users, Tags, Geographical Location, Terms of Use / User Manual. ● Technical & Optional — applied only when relevant (e.g., versioning, dependencies, privacy policy); carried in the back-office but not required for inclusion. For the semantics and detailed explanation of the fields, see the Service Dictionary. The catalogue policy we have carried forward during the drafting of our service catalogue includes: services must meet RSRL ≥ 7, expose a stable link, and provide helpdesk/contact and terms of use. We have also implemented multiple controlled lists / vocabularies where possible to ensure FAIRness and interoperability. The full tables and definitions of those lists can be found in the Service Dictionary where they are maintained. 5.1.2 How to read the current Service Catalogue The accompanying Excel file lists each service as a single row with the SDT columns below. This legend describes the labels for each column. For full field definitions, examples, and the technical/optional attributes (e.g., dependencies, version, policy links), see the Service Dictionary. Column Name Data Type Remarks Name String Human-readable title Resource Organisation String Managing/delivering organisation (or coordinating node) Webpage URL Persistent URL to the service or its information page Description String 20 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 Column Name Data Type Remarks Access Type Controlled list Physical / Virtual / Hybrid Category Controlled list Applied by the Data Unit, based on the EOSC Resource Categories Order Type Controlled list (Fully) Open access / Restricted Access / Order Required Access Mode String Eligibility notes (eg: account only for students, institutional users only, excellence-based) Language Controlled list Languages the webpage is accessible in Target Users Controlled list Eg: researcher, student, citizen scientist,... RSRL Integer 1-9 Catalogue threshold is ≥ 7 Contact E-mail / URL Email or form URL Helpdesk E-mail / URL Email or form URL; plus helpdesk page if distinct. Table 2: Current Service Catalogue Metadata Fields 5.2 Categories and Activities To ensure interoperability with the broader SSH ecosystem, RESILIENCE classifies services using the EOSC Resource categories as the primary scheme and will in the future complement them with TaDiRAH activities to express methodological aspects. This choice builds directly on the alignment work described in D2.1 and D2.11 and follows a desk study of SSH RIs and e-infrastructures such as the EOSC EU Node Resource Hub17, DARIAH’s tools and services catalogue18, OPERAS Pathfinder and GoTriple platform19, and the CESSDA Research Directory20. Together, those two categorizations provide a shared, standards-based language for discovery across RESILIENCE and downstream platforms such as the SSH Open Marketplace. 20 https://www.cessda.eu/Resource-Directory 19 https://pathfinder.operas-eu.org/search/services 18 https://www.dariah.eu/tools-services/tools-and-services/ 17 https://open-science-cloud.ec.europa.eu/resources/all 21 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 The EOSC Resource categories21 supply a stable, widely used top-level classification for “what the service is” (e.g.: Data Source, Processing/Analysis Tool, Training, Scholarly Communication). Using EOSC categories keeps RESILIENCE catalogue records compatible with the profiles and practices consulted during D2.11’s template work and reduces custom mapping later. The TaDiRAH activities capture “what the service is used to do” in SSH workflows (e.g., Digitise, Curate, Annotate, Analyse, Visualise). TaDiRAH is already adopted across SSH (incl. SSHOC/SSH Open Marketplace), which makes our activity tagging intelligible to users coming from other RIs. It also provides our users with an additional way of filtering and searching through our services. Many of RESILIENCE’s community services span several areas. For example, the Book Heritage Lab provides access to Instrument & Equipment and Data and Material Analysis, as well as Education & Training and Consultancy & Support. Our approach permits multiple EOSC categories per record and several TaDiRAH activities, so users can discover a service via either its functional class or its workflow role. Figure 1: Supercategories & categories covered by Book Heritage Lab KU Leuven 21 https://wiki.eoscfuture.eu/display/PUBLIC/B.+v4.00+EOSC+Resource+Profile#B.v4.00EOSCResourceProfileResourceCategory 22 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 Implementation of those categories on physical services such as Archives that can only be visited in person proved an interesting challenge. Physical holdings are now modelled as Material Storage and Data Source with Access Type ‘Physical’. TaDiRAH activities can later on clarify the workflow touchpoints the service supports (e.g., Acquire, Digitise, Curate, Discover). Where an institution offers add-on services (e.g., Digitisation on demand, Scholarly consultation), they are currently added as additional categories to the same service but can in the future be recorded as separate services and linked via “Related Resources.” This would make discovery even clearer while reflecting real-world service bundles. Field semantics and examples are defined in the Service Dictionary. 5.3 Access and Order Types Where the Category/Activity fields answer what the service is and what it is used for, the Access Type and Order Type fields describe how users can reach and interact with a service. Together, they allow the catalogue to filter and compare services by availability and openness, ensuring transparency for both users and managers. They are mandatory elements in the Service Description Template and align with the EOSC and SSHOC metadata profiles. During SDT testing by the Data Unit, several partners interpreted the “access” fields as pertaining to “open access” and thus the introduction of a new “service type” label was proposed to indicate whether a service is physical or digital. To preserve interoperability with SSH-wide practices (including the SSH Open Marketplace) and former EOSC Portal conventions, RESILIENCE retained the EOSC-style Access Type / Order Type separation and clarified the associated Access Mode / Access Process fields. Using these predefined terms ensures consistent filtering across the catalogue and compatibility with EOSC metadata harvesting. The field definitions are maintained in the Service Dictionary. We distinguish between: ● Access Type (required): how users reach the service – Physical, Digital, Remote (Virtual), or a combination. ● Order Type (required): specifies under which conditions the service can be used; serves as the openness at a glance – (Fully) Open Access, Restricted Access, Order Required. ● Access Mode (preferred): eligibility criteria or constraints — account needed, institutional only, excellence-based, proposal required, etc. 23 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 ● Access Process (preferred): short text or URL describing the practical steps to request, book, or purchase access. To demonstrate the differences between the fields, a table with examples is provided: Service Access Type Order Type Access Mode Access Process ReIReSearch Digital Fully Open Access https://reiresearch. eu/#/eula NA Book Heritage Lab Physical Restricted Access, Order Required Proposal required; Institutional only for certain services Link to booking/request form Online Database Digital Open Access, Fully Open Access Account required for the API API key registrations page On-site archival consultation Physical Restricted Access Only accessible to researcher E-mail to ask for access Training on demand Remote Order Required Pre-booking required Online booking form Table 3: Access and Order Types Examples 24 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 6 Onboarding of Services 6.1 Minimal Requirements In line with the guiding principles of D2.1, RESILIENCE onboards only those services that meet a baseline level of maturity to ensure that all resources listed are reliable, sustainable, and FAIR. Our minimum inclusion requirements are: ● RSRL level of 7 or higher; ● Publicly available documentation describing how to access and use the service; ● An active helpdesk or monitored contact channel; ● Evidence of regular maintenance; ● A stable, resolvable landing page or URL. These requirements operationalise the PPP strategy and apply the SDT/RSRL framework introduced in D2.11 and outlined in the Service Dictionary.22 Both the RSRL self-assessment and questions pertaining to documentation and the helpdesk are essential elements in the service description, and play an important role in the procedures to be followed after a description has been submitted. A resource cannot be considered mature if any of the above requirements are not available. The Service Catalogue can, however, also contain innovative new services and tools that have a low technology/service readiness level if it offers potential users clear information on the experimental and possibly temporary nature of the service. By being transparent about the RSRL, RESILIENCE can offer innovative and experimental tools of value to the community without running the risk of low quality and limited availability of the service offering.23 6.2 RESILIENCE Service Level Readiness (RSRL) A key part of developing procedures for evaluating and onboarding in-kind/community services, has been the implementation of our own RESILIENCE Service Readiness Level. This has helped us focus on 23 RESILIENCE PPP D2.1 – Services Preparation and Implementation Strategy, https://doi.org/10.5281/zenodo.16568333 22 RESILIENCE Service Dictionary v1.0, chapter 5, p. 16 - 20, https://doi.org/10.5281/zenodo.17741280 ; RESILIENCE Service Readiness Level overview and examples, https://doi.org/10.5281/zenodo.17701369 25 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 8 Conclusion The User Services Catalogue marks a major milestone in RESILIENCE’s journey toward a sustainable, user-oriented research infrastructure. By consolidating community services through a harmonised metadata model and shared governance framework, it delivers both transparency and interoperability across the ‘study of religion’ community. Together with the Service Dictionary it provides the foundation for future integration with HORTUS, SSHOC and EOSC. In the next phase, RESILIENCE will focus on expanding the catalogue through its National Nodes, digitising onboarding and quality-control processes, and raising the maturity of high-value community services. These steps will ensure that the catalogue remains a living, authoritative resource – continuously evolving to reflect the diversity and excellence of the research services it represents. 32 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 9 Applicable Documents Applicable documents are documents from which all requirements must be fulfilled in the context of the Grant Agreement, although they are not repeated in the present document. ID Date Title/Reference R1 18/08/2022 GRANT AGREEMENT, Project: 101079792 — RESILIENCE PPP — HORIZONINFRA-2021-DEV-02 33 Document Title: D2.2 User Services Catalogue Status: FINAL Version: 02.00 10 Reference Documents Reference documents are intended to provide background and supplementary information. ID Date Title/Reference R1 18/08/2022 GRANT AGREEMENT, Project: 101079792 — RESILIENCE PPP — HORIZONINFRA-2021-DEV-02 R2 27/11/2025 RESILIENCE Service Dictionary v1.0 R3 30/5/2025 RESILIENCE PPP – D2.11 Master Data Management v1.0 R4 24/7/2025 RESILIENCE PPP – D2.1 Services Preparation and Implementation Strategy v3.0 R5 18/9/2025 RESILIENCE PPP – D2.4 Data Management Plan v1.1 34