D2.11 Master Data Management

Grant Agreement 101079792, RESILIENCE PPP Master Data Management Title of Deliverable: Master Data Management Deliverable Number: D2.11 Type of Data: Report Lead Beneficiary: KU Leuven Publishing Status Public Last Revision Date: 26/05/2025 by: Marte DE LEEW Verification Date: 31/05/2025 by: Francesca CADEDDU Approval Date: [DD/MM/YYYY] by: [Name] Document Name: RESILIENCE_WP2_D2.11_Master_Data_Management _01.00 _FINAL Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 2 Change History Author(s) Name Beneficiary Role Marte De Leeuw KU Leuven Data Unit Lead, WP Member Roxanne Wyns KU Leuven WP Member Distribution List Name Beneficiary Role All All All Version Number Date Status Name Summary of Main Changes 00.01 20/02/2025 WORKING Working Version 00.02 22/05/2025 DRAFT First Draft Minor revisions 00.03 26/05/2025 DRAFT Final Draft Minor revisions 01.00 30/05/2025 FINAL Final Version Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 3 Table of Contents 1 Executive Summary ...................................................................................................................... 8 2 Introduction ................................................................................................................................ 10 3 Data Dictionary ........................................................................................................................... 12 3.1 Purpose ............................................................................................................................................ 12 3.2 Landscape Analysis & Desk Study .................................................................................................... 12 3.3 Key Concepts ................................................................................................................................... 13 3.3.1 Definitions .............................................................................................................................................. 14 3.3.2 Overview Matrix ..................................................................................................................................... 15 3.4 Catalogue of Resources ................................................................................................................... 17 3.4.1 (Controlled) Vocabularies ....................................................................................................................... 17 3.4.2 Thesauri .................................................................................................................................................. 18 3.4.3 Ontologies .............................................................................................................................................. 18 3.4.4 Metadata Schemes ................................................................................................................................. 19 3.5 Other Resources .............................................................................................................................. 20 4 Interoperability within SSH and beyond ..................................................................................... 23 4.1 The European Open Science Cloud (EOSC) and its first EU Node.................................................... 23 4.2 SSHOC and the SSH Open Marketplace ........................................................................................... 24 4.3 Interoperability Frameworks ........................................................................................................... 25 4.4 The Cross Domain Interoperability Framework (CDIF) .................................................................... 27 4.5 Positioning RESILIENCE in the European Landscape ....................................................................... 28 5 Service Dictionary ....................................................................................................................... 30 5.1 Guiding Principles ............................................................................................................................ 30 5.2 Development Process ...................................................................................................................... 31 5.3 Service Description Template (SDT) ................................................................................................ 34 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 4 5.3.1 From Pilot to Working Version ............................................................................................................... 34 5.3.2 Current Version ...................................................................................................................................... 34 5.4 RESILIENCE Services Readiness Level (RSRL) Scale .......................................................................... 37 5.4.1 Adapting the Scale .................................................................................................................................. 37 5.4.2 Application of the RSRL Scale ................................................................................................................. 38 5.5 Next Steps ........................................................................................................................................ 39 6 ReIReSearch ................................................................................................................................ 41 6.1 History ............................................................................................................................................. 41 6.2 Data Flow ......................................................................................................................................... 42 6.3 Data Level ........................................................................................................................................ 43 6.3.1 Interoperability ....................................................................................................................................... 43 6.3.2 Ontology ................................................................................................................................................. 43 6.4 Service Level .................................................................................................................................... 44 6.4.1 Alignment with the Strategy Strategy .................................................................................................... 44 6.4.2 Implementation of the Service Dictionary.............................................................................................. 44 6.5 Future Plans ..................................................................................................................................... 45 7 Conclusion ................................................................................................................................... 46 8 Annex .......................................................................................................................................... 47 8.1 Resource List .................................................................................................................................... 47 8.2 ReIReSearch Application Profile ...................................................................................................... 49 8.2.1 Introduction ............................................................................................................................................ 49 8.2.2 Scheme CreativeWork - https://schema.org/CreativeWork .................................................................. 49 8.2.3 Scheme Organization - https://schema.org/Organization ..................................................................... 72 8.2.4 Scheme Place - https://schema.org/Place ............................................................................................. 76 8.3 Old Service Description Template ................................................................................................... 80 8.4 Current Service Description Template ............................................................................................ 83 8.5 RSRL Scale Examples ........................................................................................................................ 86 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 5 9 Reference Documents ................................................................................................................ 88 List of Figures Figure 1: Data Flow .................................................................................................................................... 42 List of Tables Table 1: Overview Matrix ............................................................................................................................ 16 Table 2: (Controlled) Vocabularies .............................................................................................................. 17 Table 3: Thesauri ........................................................................................................................................ 18 Table 4: Ontologies .................................................................................................................................... 19 Table 5: Metadata schemes ....................................................................................................................... 20 Table 6: Interoperability frameworks examples .......................................................................................... 27 Table 7: Main information fields the Science Cluster service description should include ............................. 33 Table 8: Minimum fields ............................................................................................................................. 35 Table 9: Preferred fields ............................................................................................................................. 36 Table 10: Adapted SRL scale ...................................................................................................................... 38 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 6 Acronyms Acronym Full Form BoD Board of Directors CDIF Cross Domain Interoperability Framework DH Digital Humanities DMP Data Management Plan DOI Digital Object Identifier EOSC European Open Science Cloud ESFRI European Strategy Forum on Research Infrastructures FAIR Findable, Accessible, Interoperable, Reusable GLAM Sector including galleries, libraries, archives, and museums IF Interoperability Framework IP Implementation Phase ITSERR Research Infrastructure ITSERR (Italian Strengthening of the ESFRI RI RESILIENCE) MDM Master Data Management ODRL Open Digital Rights Language OS Open Science PID Persistent Identifier PPP Preparatory Phase Project RDM Research Data Management ReIReSearch RESILIENCE’s unified discovery platform RI Research Infrastructure RS Religious Studies RSRL RESILIENCE Service Readiness Level Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 7 SDT Service Description Template SSHOC Social Sciences and Humanities Open Cloud STEM Domain including science, technology, engineering, and mathematics TNA Transnational Access TRL Technology Readiness Level WU Data Working Unit Data Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 8 1 Executive Summary This deliverable outlines the Master Data Management of RESILIENCE, aiming to enhance interoperability, discoverability, and usability of research data and services across the community of the study of religion. RESILIENCE establishes a robust Reference Data Architecture through a comprehensive Data Dictionary and Service Dictionary, facilitating seamless data exchange and clear service descriptions. The Data Dictionary provides a common terminology framework necessary for effective communication and interoperability among diverse research information systems. Through a detailed landscape analysis, RESILIENCE identified essential vocabularies, thesauri, ontologies, and metadata schemas that are crucial for ensuring FAIR (Findable, Accessible, Interoperable, Reusable) principles within the community. Key resources such as Schema.org, CIDOC CRM, and the SSHOC Marketplace standards have been leveraged to avoid duplication and ensure compatibility. Interoperability is further strengthened by adopting established frameworks such as the EOSC Interoperability Framework or the Cross Domain Interoperability Framework (CDIF). Their implementation facilitates data and service integration within broader European infrastructures, reinforcing RESILIENCE’s position as an important contributor to the European research landscape. Both a general overview and more details regarding its implementation are provided. The Service Dictionary complements the Data Dictionary by standardizing service descriptions, thereby improving transparency and accessibility. RESILIENCE’s streamlined Service Description Template (SDT), aligned with EOSC and SSHOC guidelines, ensures that service providers within the academic and GLAM sectors can clearly articulate service capabilities. The tailored RESILIENCE Service Readiness Level (RSRL) scale further supports service providers in self-assessing maturity, fostering sustainable and reliable service delivery. Using the online discovery platform ReIReSearch as a key example, this deliverable demonstrates practical implementation of the interoperability principles. As one of RESILIENCE’s core services built upon the Schema.org application profile, it illustrates the effective integration and harmonization of diverse metadata, on top of providing an accessible and valuable discovery platform for researchers. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 9 By systematically developing these foundational elements, RESILIENCE ensures that research data and services are effectively managed, highly interoperable, and sustainably maintained, supporting the ongoing growth and impact of the study of religion. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 16 Concept Definition Structure Purpose Vocabulary Curated list of terms with no hierarchy or relationships. Flat or enumerated list; may or may not be maintained formally. Represent the knowledge within a domain, provide clarity and ensure consistent terminology Controlled Vocabulary A vocabulary with clear governance and management practices. Concepts are organized into a simple hierarchical structure of broader and narrower meanings (eg. taxonomy) The added governance & persistent identifiers prevent ambiguity and enable machine validation. Thesaurus Controlled vocabulary enhanced by hierarchical and associative semantic relationships. Network or graph of concepts with (non-)hierarchical & associative relations. Powerful searching & semantic expansion; Consistent use of terms related to the same concepts. Ontology Rich, logically structured vocabularies for detailed semantic interoperability. A network of interconnected concepts with hierarchical and/or associative relationships, described following strict rules. Rich interoperability, reasoning and semantic data integration Metadata Schema Structured guidelines specifying metadata elements and their use. May be expressed in XML‑Schema, JSON‑Schema, etc. Ensure metadata records share the same structure, so it is machine-readable and interoperable. Table 1: Overview Matrix Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 17 3.4 Catalogue of Resources Below follows an overview of (controlled) vocabularies, thesauri, ontologies and metadata schemes, including a link to their webpage, their relevance to the community of the study of religion, and the project(s) they are a result of or used by. This overview is by no means complete but should provide the reader with a good idea of some important resources out there. In time these lists will be further expanded with often used resources by the community. 3.4.1 (Controlled) Vocabularies Name Project Link Relevance RDMT CODATA https://vocabs.ard c.edu.au/viewById /685 Research Data Management Terminology; Curated set of ~345 RDM terms with stable URIs and definitions but no hierarchical semantics beyond “is‑a term”. ICONCLASS codes https://iconclass.o rg/help/basics A classification system for cultural content, focused on artworks, iconography, and visual motifs. It is widely used in libraries, museums, and digital humanities projects to index, retrieve, and analyze images based on subject matter. EOSC Resource Categories EOSC https://eoscfuture .eu/eoscresourcecatalogue/ Published as a SKOS ConceptScheme listing Super‑, Sub‑ & Category levels for the EOSC Portal; terms are maintained but relations are simple broader/narrower taxonomic links. TaDiRAH ATRIUM https://vocabs.dar iah.eu/tadirah/en/ In this vocabulary you can find activity terms that can be used by Digital Humanities projects to tag research methods. DPC Glossary DPC https://www.dpco nline.org/handbo ok/glossary A glossary created by the Digital Preservation Coalition as a guide to their Digital Preservation Handbook. It offers a working set of definitions and acronyms used throughout the Handbook and their website. Table 2: (Controlled) Vocabularies Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 18 3.4.2 Thesauri Name Project Link Relevance ELSST CESSDA https://thesauri.cess da.eu/elsst-5/en/ Has a “Religion and belief” branch where you can find multilingual terms for social‑science datasets about religion. UNESCO Thesaurus UNESCO https://vocabularies. unesco.org/browser/t hesaurus/en/ Thesaurus that for example describes hierarchical religion concepts (e.g., Religious architecture → Temples) Getty TGN Getty https://www.getty.e du/research/tools/vo cabularies/tgn/ Thesaurus of Geographic Names; links holy sites (Mecoca, Lourdes, Bodh Gaya) to broader regions. History and Sciences of Religions CNRS https://loterre.istex.f r/4V5/en/ Controlled vocabulary used for indexing bibliographical records for the "History and Sciences of Religions" FRANCIS database. Table 3: Thesauri 3.4.3 Ontologies Name Project Link Relevance SSHOCro SSHOC https://zenodo.o rg/records/67717 57#.Yrr05xBz0o SSHOCro proposes an ontological model and RDF schema to be used as a top-level ontology for organising knowledge and information found distributed across various primary sources of information in the SSHOC. CIDOC CRM SSHOCro, DARIAH https://cidoccrm.org/ Ontology specific for Cultural Heritage and mainly used by museums or heritage projects like ARIADNE. It is often used as a base for other ontologies such as the SSHOCro or GoTriple Ontology. It also has useful extensions such as the CRMtext for describing ancient documents. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 19 Name Project Link Relevance BIBFRAME BIBFRAME https://www.loc. gov/bibframe/ BIBFRAME provides a foundation for the future of bibliographic description, both on the web, and in the broader networked world that is grounded in Linked Data techniques. A major focus of the initiative is to determine a transition path for the MARC 21 formats while preserving a robust data exchange that has supported resource sharing and cataloging cost savings in recent decades. SKOS W3C SKOS Simple Knowledge Organization System - home page Both a standard and an OWL Ontology that lets you encode concepts, labels and mapping links. It is used for expressing controlled vocabularies. TRIPLE GoTriple https://www.got riple.eu/ GoTriple is an innovative multilingual discovery platform for the social sciences and humanities (SSH). It provides one of the central access points for discovering and reusing research artefacts that are relevant to the wide variety of disciplines under the umbrella domain of SSH Table 4: Ontologies 3.4.4 Metadata Schemes Name Project Link Relevance DCAT (Dublin Core) https://www.dub lincore.org/ Widely used in SSH for metadata description, providing a standardized yet simple schema beneficial for cataloguing religious studies resources and datasets. TEI DARIAH, CLARIN https://tei-c.org/ Crucial for text encoding, especially historical, literary, or linguistic sources prominent in religious studies. Essential for digital editions and manuscripts. Schema.org CDIF, ReIReSearch https://schema.o rg/ Especially useful for web-based discoverability of diverse research resources. Its flexible structure is widely applicable to varied SSH resources. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 20 Name Project Link Relevance EDM Europeana; ERIHS https://pro.euro peana.eu/page/e dmdocumentation Key metadata schema for cultural heritage collections, relevant for religious studies involving artifacts, images, and multimedia cultural heritage items. Component Metadata Infrastructure CLARIN https://www.clar in.eu/content/c mdicomponentmetadatainfrastructure Primarily for linguistic resources, enabling detailed, flexible metadata description, valuable for corpus linguistics within religious texts and historical language resources. DDI Codebook and Lifecycle https://ddiallianc e.org/Specificati on/ Standard for describing survey and observational data within SSH, beneficial for managing qualitative and quantitative data collections in religious and social studies research. MODS https://www.loc. gov/standards/m ods/ Highly applicable to library and archival cataloguing, supporting granular bibliographic description of texts crucial for comprehensive religious studies research. EAD https://www.loc. gov/ead/ Encoded Archival Description is used for archival collections, providing a detailed descriptive standard essential for historical and archival materials common in the study of religion. DataCite https://datacite. org/ Provides persistent identifiers (DOIs) and standard metadata for datasets, significantly enhancing the discoverability and reusability of SSH research outputs. Table 5: Metadata schemes 3.5 Other Resources While the previous sections covered the most relevant controlled vocabularies, thesauri, ontologies, and metadata schemes, numerous additional resources exist that might be beneficial for specific research needs within the study of religion or the broader SSH community. Below is a curated list of recommended platforms and tools where further relevant resources, vocabularies, or standards can be explored. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 21 SSH Open Marketplace Vocabularies: ● Comprehensive list of vocabularies, formats, and ontologies relevant to Social Sciences and Humanities. ● https://vocabs.sshopencloud.eu/browse/en/ Getty Research Institute Vocabularies: ● Trusted vocabularies extensively used for art, iconography, cultural heritage, and related fields. ● https://www.getty.edu/research/tools/vocabularies/index.html CESSDA Vocabulary Service ● Controlled vocabularies tailored for data archiving and social sciences RDM. ● https://www.cessda.eu/Tools/Vocabulary-Service BARTOC (Basel Register of Thesauri, Ontologies & Classifications) ● Comprehensive registry of vocabularies and metadata schemes across numerous disciplines, valuable for exploring and identifying standards used globally. ● https://bartoc.org/ GoTriple Vocabulary ● Multilingual vocabularies specifically targeted to the needs of the Social Sciences and Humanities, including the study of religion. ● https://www.gotriple.eu/ Library of Congress Linked Data Service ● Authority control and linked data service that includes detailed entries, such as the concept of "Religion," suitable for precise metadata tagging. ● https://id.loc.gov/authorities/subjects/sh85112549.html RDM Controlled Vocabularies Research Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 22 ● Overview and in-depth guidance on controlled vocabularies specific to research data management practices. ● https://rdmkit.elixir-europe.org/vocabularies Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 23 4 Interoperability within SSH and beyond In RESILIENCE’S Service Strategy 5 nine core guiding principles are outlined, one of which is its integration within the wider European landscape of Research Infrastructures (RIs). To facilitate this, it is important to focus on interoperability, a concept that is at the forefront of many projects and infrastructures being built right now since this is crucial for realizing true Open Science and adhering to the FAIR (Findable, Accessible, Interoperable, Reusable) principles. Those principles aim to make research data and related resources easy to find, access, combine, and use, which is particularly important for multidisciplinary research - such as the study of religion - that spans across different domains and infrastructures, addressing some of the biggest societal challenges. However, the practical implementation of FAIR principles often lags behind due to organizational, legal, and cultural barriers, as well as the lack of standardized data and metadata exchange practices. Despite the availability of modern information technology and the tools needed to build the desired research infrastructure, the resources are not always provided in a reusable manner, hindering efficient data sharing and integration. To overcome these challenges, it is essential to provide detailed and rich metadata in standardized formats that are meaningful to users and their systems. Machine-actionability is a key enabler for FAIR implementation, as it allows for automation and scalability, reducing the time and effort required for data preparation and integration. By publishing an extensive Data Management Plan 6 RESILIENCE aims to provide its community with a guide and resources on good practices around FAIR data, helping to mitigate the negative impacts of emerging technologies like large language models (LLMs) and artificial intelligence (AI), while enhancing their positive potential. 4.1 The European Open Science Cloud (EOSC) and its first EU Node The European Open Science Cloud (EOSC) ecosystem builds on existing infrastructure and services supported by the European Commission (EC), Member States and Associated countries, and research 5 “RESILIENCE services should be integrated into the wider SSH and EOSC ecosystem” - D2.1 Service Preparation and Implementation Strategy: https://doi.org/10.5281/zenodo.14269781, 6 D2.4 Data Management Plan: https://doi.org/10.5281/zenodo.13939110 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 24 communities 7 . Its participants have been working diligently on developing an interoperability framework. Key features of the EOSC include: ● Interoperability Framework: Ensures seamless data sharing and processing across national and disciplinary boundaries. ● Rules of Participation: Establishes guidelines for service providers and users to ensure compliance and quality. ● Federated Architecture: Promotes a decentralized approach, allowing various nodes to contribute to the overall infrastructure. The EOSC Federation Build up phase 8 , which kicked off in March of 2025, will further enhance and specify the above. As the Federation develops, RESILIENCE will closely monitor new or updated outputs such as the EOSC Federation Handbook, to ensure future compliance. 9 As outlined in D2.1, our service strategy aligns with the EOSCs principles by promoting open access, interoperability, and the use of FAIR (Findable, Accessible, Interoperable, Reusable) data principles. Through targeted cooperation with SSHOC, RESILIENCE can benefit from shared expertise, reducing the redundancy of efforts and enhancing efficiency in service delivery and metadata standardization. 4.2 SSHOC and the SSH Open Marketplace In the past few years, the ESFRI landscape has moved towards a more ‘cluster-like’ collaboration of thematic RI, leading to the development of the Social Sciences and Humanities Open Cloud (SSHOC). Since the study of religion falls within the SSH domain, ensuring interoperability with them through the SSH Open Marketplace is paramount. This is why we are actively engaging with SSHOC through, for example, the first strategic Pillar “Sharing Data, Tools and Workflows” 10 . RESILIENCE’s active engagement with the SSH Open Marketplace will ensure 7 https://eosc.eu/partnership/ 8 https://eosc.eu/eosc-about/building-the-eosc-federation 9 https://eosc.eu/eosc-about/building-the-eosc-federation/eosc-federation-handbook/ 10 https://sshopencloud.eu/news/sshoc-2025-updates. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 25 robust alignment with EOSC standards and facilitate the seamless discoverability and interoperability of its services across SSH disciplines. The OSCARS Projects 11 (Open Science Clusters’ Action for Research and Society) is a four-year Horizon Europe project, which aims to foster the uptake of Open Science in Europe by mapping and where possible consolidating the achievements of world-class European research infrastructures on the ESFRI roadmap and beyond into lasting interdisciplinary FAIR data services, tools and working practices. In December 2024, they published a report 12 which focuses on the mapping, creation, refinement, and exploitation of a Services and Data Sources Portfolio. In this report they consider the different starting points of the involved Science Clusters, one of which is the SSHOC. 4.3 Interoperability Frameworks European Research Infrastructures (RIs) live or die by their ability to let heterogeneous systems “speak the same language”. An interoperability framework provides that lingua franca: a shared set of policies, standards and implementation patterns that make data, services and workflows understandable and actionable across organisational, national and disciplinary borders. For RESILIENCE—with partners spread over several countries and holding very different types of religious‑studies materials—this is not a luxury but a prerequisite. Without an agreed framework, curated corpora of Syriac manuscripts, a sociological survey on contemporary pilgrimages and a digital 3‑D model of a medieval synagogue remain isolated assets; with one, they become mutually discoverable, citable and reusable in new, mixed‑method research. The need is particularly acute in the Social Sciences and Humanities (SSH) since, unlike many STEM domains, its data lacks universally adopted schemas; terminology varies with language, tradition and school. Religious‑studies scholarship amplifies that diversity because it routinely crosses into sociology, archaeology, architecture, psychology, classical and modern languages, literary studies and more. An interoperability framework therefore acts as the connective tissue that lets an archaeologist’s stratigraphic dataset be joined with a corpus‑linguistic analysis of liturgical texts, or allows climate historians to query 11 https://oscars-project.eu/science-clusters 12 OSCARS D2.1 Clusters’ Services and Data Source Portfolios: https://doi.org/10.5281/zenodo.14269781 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 32 refine the template, the EOSC Provider Platform was examined. The EOSC Resource Profile and Data Source Profiles 17 were compared with the SSH Open Marketplace metadata guidelines to enhance understanding of resource information collection and description. After several consultations with WU Data and RESILIENCE partners, it was decided to adopt EOSC profiles for developing information collection templates. This decision led to the creation of multiple iterations of service analysis templates, which were tested and refined to produce a practical and comprehensive template, along with detailed instructions and guidelines. After the first round of collecting in-kind services, which resulted in detailed information on 14 community services, feedback from partners taught us that the first version of the SDT was too complex and exhaustive, resulting in frustration by those who had to fill it out. One of the difficulties encountered was the diversity in fields and more specifically the high number of fields that was sometimes present or even required, which is a problem other RIs and European projects have struggled with as well. An additional desk study was carried out to learn how others dealt with this problem. The work carried out by the OSCARS proved particularly useful. The following paragraph and table is an extract from their deliverable D2.1 Clusters’ Services and Data Sources Portfolios 18 : “The best way to describe the portfolio resources was naturally one of the first questions discussed as part of the WP2 work. Some “generic” information was easily identified. In particular, by considering the v4.00 of the EOSC Resource Profiles, we identified the metadata descriptors listed in Tab. 2 as mandatory in any service and data sources cataloguing efforts, while some of them led to discussion, as their use leads to open questions.” 17 https://wiki.eoscfuture.eu/display/PUBLIC/B.+v4.00+EOSC+Resource+Profile https://wiki.eoscfuture.eu/display/PUBLIC/D.+v4.00+EOSC+Data+Source+Profile 18 https://zenodo.org/records/14881627 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 33 Table 7: Main information fields the Science Cluster service description should include Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 34 5.3 Service Description Template (SDT) 5.3.1 From Pilot to Working Version As mentioned before, the first version of our SDT was an exact copy of the Resource Profile from the by now decommissioned EOSC Open Marketplace. However, as you can see in the example provided in the annex, partner feedback after the first collection round showed that many fields—e.g. Multimedia and Use case— were left blank by almost all providers, proving they added burden without value. Since some of the consortium partners also offer technical services, we couldn’t simply take out all the more specific fields which is why a lightweight “minimum–preferred–technical–optional” rule was adopted: ● Minimum (M) – 12 fields mandatory for catalogue inclusion (Name, Resource Provider, Webpage, EOSC category, S/TRL, etc.). ● Preferred (P) – 8 fields that enrich discovery but are not gating (Tag, Geographic Location, Terms of Use). ● Technical (T) – Fields that only have to be filled out when the service is of a technical nature. ● Optional (O) – Everything else has dropped or moved to a future ‘enhanced’ tier, especially in regards to the more technical services. This pruning cut the template from 42 to 20 fields, slashing average completion time by more than half and aligning with OSCARS’ mandatory-only approach. 5.3.2 Current Version After the Data Unit carried out the rework of the RESILIENCE SDT, based on the experiences from the first collection round, we landed on a new and improved list of mandatory, preferred and optional metadata. Table 6-1 lists only the Minimum attributes, while table 6-2 shows an overview of the Preferred ones; the full schema, including technical & optional attributes and code-lists sit in the Annex 8.4. Minimum Fields (M) Field Description Type Example ID Unique Identifier within the RESILIENCE platform; this is Unique Identifier ? Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 35 Field Description Type Example assigned by the RI Name Human-Readable Label String ReIReSearch Resource Organisation The name of the organisation that manages or delivers the service, or that coordinates the Service delivery in a federated scenario. ? LIBIS - KU Leuven Webpage Persistent Link (or Webpage) of the Service or its information Persistent Link https://reiresearch.eu/ Description String ReIReSearch is an online discovery platform where disparate digital resources and databases are searchable in a unified and standardized way. Category The type of Service; e.g. Data Analysis, Scholarly Communication Pre-defined list Access Type The way a user can access the Service (Remote, Physical, etc.) Pre-defined List Virtual Order Type Whether the service is fully open access, partly, restricted, etc. Pre-defined List Open Access Language The language in which the Service is provided ? English RSRL or TRL See Section on RSRL Integer Range 1-9 S9 - Established / Trusted Contact The email address or form through which a contact person can be reached for questions Email or Formlink Helpdesk Information The web address where the Helpdesk details are provided Webpage/Link https://reiresearch.helpdocsi te.com/ Table 8: Minimum fields Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 36 Preferred Fields (P) Field Name Description Type Example Sub Category A more detailed categorisation of the type of Service; e.g. Data Analysis: Machine Learning, Scholarly Communication: Assessment Pre-defined List Access Mode Eligibility/criteria for granting access to users (excellence-based, free-conditionally, etc.) String Account is only possible for people with a KU Leuven account Access Process Information on the access or ordering (if paying service) process. String or Link https://reiresearch.eu/#/eula Access Policy Information about the access policies that apply. String or Link https://reiresearch.eu/#/eula Target Users Type of users that the Service is intended for; e.g. researchers, librarians, citizen scientists, etc. String Researchers, Librarians Tags Keywords associated to the Service to simplify search by relevant keywords String Geographical Location Where the Service is hosted String Leuven Terms of Use Webpage or explanation describing the rules, conditions and usage policy which one must agree to abide by in order to use the Service. String or Link https://reiresearch.eu/#/eula User Manual Link to the Resource user manual and documentation. Link https://reiresearch.helpdocsi te.com/ Table 9: Preferred fields Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 37 5.4 RESILIENCE Services Readiness Level (RSRL) Scale In alignment with RESILIENCE’s guiding principles, we ensure that our services maintain a high level of maturity, supported by a robust infrastructure and a dedicated support team. This guarantees that resources remain Findable, Accessible, Interoperable, and Reusable (FAIR). The RESILIENCE Services Readiness Level (RSRL) scale is employed to assess the maturity of services, ensuring that users have access to reliable and sustainable tools and is based on the (S/)TRL scale that is widely used within a plethora of businesses and projects (e.g.: EOSC, DARIAH,...). 5.4.1 Adapting the Scale Most of our service providers originate from the academic and GLAM sector within the Social Sciences and Humanities (SSH), encompassing among others libraries, archives, and researchers. Since the TRL scale was originally designed for technical services 19 , its terminology is highly technical which poses a challenge for our service providers who are not all well-versed in technical terminologies such as "system prototype demonstration in operational environment," which is the qualification for TRL 7. To facilitate a clearer understanding, the WU Data has composed a list of SSH-specific explanations for this scale, enabling providers to accurately assess the maturity and readiness level of their services. To ensure alignment with other SSH RIs such as DARIAH, we made sure to map our scale exactly to the TRL one. ● Red = Theoretical, in Preparation ● Orange = Demo ● Yellow = Pilot Version, Limited Production ● Green = Public Release, Operational SRL Plain Description Typical Evidence Example S1 – Idea You can explain the concept on paper, but no code or workflow exists yet. One-pager, slide deck. A professor sketches an annotated digital edition she would like to build. 19 https://wiki.ni4os.eu/index.php/Technology_Readiness_Level Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 38 S2 – Concept outlined Key functions are described; basic feasibility checked; no users yet. Short requirements doc, draft data model. Same professor drafts a MARC-XML profile for her manuscripts. S3 – Feasibility prototype A rudimentary demo runs on a laptop; shows the core feature to colleagues. GitHub repo, screenshots. Doctoral student codes a prototype Jupyter notebook that classifies hymn lyrics. S4 – Lab prototype Prototype is stable enough to be tested by invited colleagues; feedback loop open. Test report from 35 peers. The notebook is put on Binder and three students try it. S5 – Pilot (limited public) Service is reachable on the internet, advertised as beta; documentation draft exists. Public URL, readme, contact email. The manuscript portal runs on the university server; Access on request. S6 – Community pilot ≥ 20 external users; bug tracker active; privacy / IPR statements drafted. Usage stats, helpdesk log. Notebook turned into a small MOOC with 30 attendees. S7 – Operational Open to everyone; SLA or ToU* light (“best effort”); user guide and helpdesk active. Stable URL, versioned releases, uptime metrics. Searchable via platforms (eg: ReIReSearch); Helpdesk via form or e-mail S8 – Managed service Formal SLA or MoU signed; backups, monitoring, sustainability plan for ≥3 years. SLA, Terms of Use or Policies available; DMP. Institution IT takes over hosting; Annual review S9 – Established / trusted Proven track-record of ≥ 3 years at SRL 8; cited or reused by third parties Citations, audit certificate. Portal included in (inter)national registry; DOIs minted for datasets. Table 10: Adapted SRL scale 5.4.2 Application of the RSRL Scale For services to be included in the RESILIENCE Service Catalogue, they must meet a minimum RSRL of 7, indicating that the service is well-developed and ready for operational use. This requirement ensures that the services are not only accessible and usable at the time of onboarding but also sustainable in the long term. Additionally, clear documentation and a helpdesk must be available to assist users with technical and Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 39 usability issues, ensuring that the resources are mature and reliable. This approach allows RESILIENCE to offer high-quality services to the community while maintaining transparency about the readiness and experimental nature of innovative tools. Practical illustrations of every RSRL maturity stage are provided in Annex 8.5 which maps three contrasting services—a digital research platform (ReIReSearch), a capacity-building course (“Training on AI Tools”), and a physical digitisation facility (KU Leuven’s Book Heritage Lab)—across the nine-level scale. These examples allow prospective providers to benchmark their own service proposals against clearly defined, disciplinespecific milestones. Regarding the assignment of a RSRL level to a service, the following steps need to be taken: ● Providers self-assess based on the clarification table in the previous section and the examples provided in Annex 8.5; the Data Unit verifies plausibility. ● When a record changes RSRL, date stamps need to be added and history kept ● Services < S4 appear only in a “sandbox” tab visible to consortium login. The Data Unit remains the steward of the SDT and RSRL scale; minor textual clarifications will be released annually with updates of the D2.2 User Services Catalogue. 5.5 Next Steps Short term (by Sept 2025) 1. Publish the current SDT and SRL poster on Zenodo with a DOI; cite it in partner guidance. 2. On-board the remaining legacy services (≥ 10) using the new template. 3. Launch a one-page online form (MS Forms or LimeSurvey) that mirrors the Mandatory 12 fields. Medium term (2026) 4. Offer three “service metadata sessions” at partner institutions to raise completion quality. 5. Implement an SRL change log column in the catalogue spreadsheet; add a monthly reminder to providers whose services are still < 4. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 40 Long term (2027 and beyond) 6. Introduce enhanced (optional) metadata tier for technical services—only after ≥ 50 % of providers request it. 7. Expose RESILIENCE services in JSON-LD so that EOSC or SSHOC can harvest directly. 8. Explore Handbook from the EOSC Federation and the new Rules of Participation for EOSC EU Nodes once they are finalised. 9. Hand over catalogue stewardship from the PPP/IP Data Unit to the permanent RESILIENCE ERIC service team. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 41 6 ReIReSearch One of RESILIENCE's core services is ReIReSearch, an online discovery platform. It federates heterogeneous metadata supplied by partner institutions, harmonises it through a light‑weight application profile based on Schema.org, validates it for quality and exposes it through an intuitive search interface backed by Elasticsearch. Because of its importance within our infrastructure and its proven stability and interoperability, we use it as an example to base future developments and integrations on. 6.1 History ReIReSearch was first developed back in 2019 when RESILIENCE’s predecessor, the Horizon 2020 ReIReS Project first started. It addresses the growing need of scholars in the study of religion to discover more data, regardless of location, with one platform where disparate digital resources and databases are searchable in a unified and standardised way. It brings together metadata from different collection holders or data providers who can have the metadata of their relevant collections included in the platform. At the start of the PPP, it was decided to onboard ReIReSearch as a core RESILIENCE service. As a consequence, it was rebranded to fit the RESILIENCE branding (cf. to D2.1 Service strategy: “an in-kind contribution can become a core service …”). It serves as a prime example due to Schema.org being its underlying vocabulary as this is one of the most common and often used vocabulary within the SSH and can easily be adapted towards a project or researcher’s needs. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 48 ● Frontini, F., Gamba, F., Monachini, M., Broeder, D., Tijdens, K., & Vipavc Brvar, I. (2021). D3.9 Report on Ontology and Vocabulary Collection and Publication. Zenodo. https://doi.org/10.5281/zenodo.5913485 ● Georgiadis, H., Blaszczynska, M., & Maryl, M. (2023). TRIPLE Deliverable: D2.4 Report on Identification and Creation of New Vocabularies. Zenodo. https://zenodo.org/records/7539922 ● Meghini, C., Benassi, L., Galeotti, M., Bartalesi, V., Concordia, C., Castillejo, M., Calvo Simal, C., Andreassi, E., & Striova, J. (2020). E-RIHS PP D8.1 Catalogue of E-RIHS Resources and Services. Zenodo. https://zenodo.org/records/4002040 ● Richards, J., Felicetti, A., Meghini, C., & Theodoridou, M. (2022). D4.4 – Final Report on Ontology Implementation. Zenodo. https://zenodo.org/records/7636720 ● Romary, L., Riondet, C., Tadjou, L., Sotiropoulou, S., & Seillier, D. (2019). PARTHENOS D4.4 Report on Standardization – Final. Zenodo. https://zenodo.org/records/2607014 ● Tsouloucha, E., Kritsotaki, A., Bekiari, C., & Theodoridou, M. (2021). D4.19 Mapping of Two Indicative Selected Standards to the SSHOCro. Zenodo. https://zenodo.org/records/4457496 Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 49 8.2 ReIReSearch Application Profile 8.2.1 Introduction The ReIReSearch application profile was developed during the ReIReS project 24 and is based on the Schema.org vocabulary 25 . Not the entire Schema.org vocabulary is supported. The ReIReSearch application profile is limited to a subset of types and properties according to what information is applicable to the community. Current supported classes and subclasses include: CreativeWork with subclasses Article, Book, PublicationIssue, PublicationVolume. The classes MediaObject, Person, Organization, Place and Event are also defined and supported though they are usually created by the system on import based on the metadata provided (e.g. dc:creator will be mapped to the ‘Name’ property of the Schema.org class ‘Person’). In time the application profile can be extended with new classes and properties for inclusion of other data types. For the integration of data in ReIReSearch, there are mandatory, recommended and optional metadata elements. The supported classes (the “record types”, referred to as “Things” in Schema.org) and properties are listed below. The following information is included for each element: - Schema.org property including link to the Schema.org property page - the definition of that property - the scheme it belongs to (i.e. CreativeWork, MediaObject, Person, Organization, Place and Event) - common name for the data element (e.g. author, title, publication date …) - the class and subclasses it applies to - expected values/data type (e.g. text, a numerical value, a URL ....) - status (i.e. M - mandatory, R - recommended, O - optional) 8.2.2 Scheme CreativeWork - https://schema.org/CreativeWork Property identifier M Definition The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. Scheme CreativeWork 24 D6.2 Integrated metadata model (https://reires.eu/wpcontent/uploads/2019/04/ReIReS_Deliverable_6.2_v04.00.pdf) 25 https://schema.org/ Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 50 Used for Identifier (a meaningful ID besides a unique record identifier) Class & Subclasses Thing Values expected Text, URL license (Created by system if not provided by partner.) M Definition A license document that applies to this content, typically indicated by URL. Scheme CreativeWork Used for Work license Class & Subclasses CreativeWork Values expected URL name M Definition The name of the item. Scheme CreativeWork Used for Title Class & Subclasses Thing Values expected Text provider M Definition The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller. Scheme CreativeWork (system element) Used for Data provider Class & Subclasses CreativeWork Values expected Person, Organization sdDatePublished M Definition Indicates the date on which the current structured data was generated / published. Typically used alongside sdPublisher Scheme CreativeWork (system element) Used for Record publication date Class & Subclasses CreativeWork Values expected Date sdLicense M Definition A license document that applies to this structured data, typically indicated by URL. Scheme CreativeWork (system element) Used for Record license Class & Subclasses CreativeWork Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 51 Values expected URL sdPublisher M Definition Indicates the party responsible for generating and publishing the current structured data markup, typically in cases where the structured data is derived automatically from existing published content but published on a different site. For example, student projects and open data initiatives often re-publish existing content with more explicitly structured metadata. The sdPublisher property helps make such practices more explicit. Scheme CreativeWork (system element) Used for Record publisher Class & Subclasses CreativeWork Values expected Organization url M Definition URL of the item. Scheme CreativeWork (system element) Used for Persistent ReIReSearch link Class & Subclasses Thing Values expected URL additionalType R Definition An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally. Scheme CreativeWork Used for Type Class & Subclasses Thing Values expected URL alternateName R Definition An alias for the item. Scheme CreativeWork Used for Other title Class & Subclasses Thing Values expected Text associatedMedia R Definition A media object that encodes this CreativeWork. This property is a synonym for encoding. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 52 Scheme CreativeWork Used for Media Class & Subclasses CreativeWork Values expected MediaObject > Allowed subtypes are ImageObject, VideoObject, SoundObject, DataDownload author R Definition HTML 5 provides a special mechanism for indicating authorship via the rel tag. That is equivalent to this and may be used interchangeably. Scheme CreativeWork Used for Author Class & Subclasses CreativeWork Values expected Person, Organization creator R Definition The creator/author of this CreativeWork. This is the same as the Author property for CreativeWork. Scheme CreativeWork Used for Creator Class & Subclasses CreativeWork Values expected Person, Organization contributor R Definition A secondary contributor to the CreativeWork or Event. Scheme CreativeWork Used for Contributor Class & Subclasses CreativeWork Values expected Person, Organization dateCreated R Definition The date on which the CreativeWork was created or the item was added to a DataFeed. Scheme CreativeWork Used for Creation/Publication date Class & Subclasses CreativeWork Values expected Date, DateTime datePublished R Definition Date of first broadcast/publication. Scheme CreativeWork Used for Publication date Class & Subclasses CreativeWork Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 53 Values expected Date description R Definition A description of the item. Scheme CreativeWork Used for Description Class & Subclasses Thing Values expected Text editor R Definition Specifies the Person who edited the CreativeWork. Scheme CreativeWork Used for Editor Class & Subclasses CreativeWork Values expected Person genre R Definition Genre of the creative work, broadcast channel or group. Scheme CreativeWork Used for Discipline/Classification Class & Subclasses CreativeWork Values expected Text, URL hasPart R Definition Indicates an item or CreativeWork that is part of this item, or CreativeWork (in some sense). Inverse-property: isPartOf. Scheme CreativeWork Used for Has part Class & Subclasses CreativeWork Values expected CreativeWork inLanguage R Definition The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage. Scheme CreativeWork Used for Language Class & Subclasses CreativeWork Values expected Language, Text isbn R Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 54 Definition The ISBN of the book. Scheme CreativeWork Used for ISBN Class & Subclasses CreativeWork, Book Values expected Text isPartOf R Definition Indicates an item or CreativeWork that this item, or CreativeWork (in some sense), is part of. Inverse-property: hasPart. Scheme CreativeWork Used for Is part of Class & Subclasses CreativeWork Values expected CreativeWork, Collection issn R Definition The International Standard Serial Number (ISSN) that identifies this serial publication. You can repeat this property to identify different formats of, or the linking ISSN (ISSN-L) for, this serial publication. Scheme CreativeWork Used for ISSN Class & Subclasses CreativeWork, CreativeWorkSeries Values expected Text issueNumber R Definition Identifies the issue of publication; for example, "iii" or "2". Scheme CreativeWork Used for Issue number Class & Subclasses CreativeWork, PublicationIssue Values expected Integer, Text keywords R Definition Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas. Scheme CreativeWork Used for Keywords Class & Subclasses CreativeWork Values expected Text locationCreated R Definition The location where the CreativeWork was created, which may not be the same as the location depicted in the CreativeWork. Scheme CreativeWork Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 55 Used for Place of creation/publication Class & Subclasses CreativeWork Values expected Place pagination R Definition Any description of pages that is not separated into pageStart and pageEnd; for example, "1-6, 9, 55" or "10-12, 46-49". Scheme CreativeWork Used for Pagination Class & Subclasses CreativeWork, Article, PublicationIssue, PublicationVolume Values expected Text publisher R Definition The publisher of the creative work. Scheme CreativeWork Used for Publisher Class & Subclasses CreativeWork Values expected Person, Organization sameAs R Definition URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website. Scheme CreativeWork Used for Source record Class & Subclasses Thing Values expected URL volumeNumber R Definition Identifies the volume of publication or multi-part work; for example, "iii" or "2". Scheme CreativeWork Used for Volume number Class & Subclasses CreativeWork, PublicationVolume Values expected Integer, Text about O Definition The subject matter of the content. Inverse-property: subjectOf. Scheme CreativeWork Used for Subject Class & Subclasses CreativeWork Values expected Thing Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 56 articleBody O Definition The actual body of the article. Scheme CreativeWork Used for Full text/Transcription/Annotation Class & Subclasses CreativeWork, Article Values expected Text bookEdition O Definition The edition of the book. Scheme CreativeWork Used for Edition Class & Subclasses CreativeWork, Book Values expected Text contentLocation O Definition The location depicted or described in the content. For example, the location in a photograph or painting. E.g.: The Church at Auvers by Vincent van Gogh depicts a church in Auvers-sur-Oise, but was created in Saint-Rémy-de-Provence. Scheme CreativeWork Used for Subject: Location Class & Subclasses CreativeWork Values expected Place copyrightHolder O Definition The party holding the legal copyright to the CreativeWork. Scheme CreativeWork Used for Copyright holder Class & Subclasses CreativeWork Values expected Person, Organization copyrightYear O Definition The year during which the claimed copyright for the CreativeWork was first asserted. Scheme CreativeWork Used for Copyright year Class & Subclasses CreativeWork Values expected Number dataset O Definition A dataset contained in this catalog. Inverse property: includedInDataCatalog. Scheme CreativeWork Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 57 Used for Has datasets Class & Subclasses CreativeWork Values expected Dataset distribution O Definition A downloadable form of this dataset, at a specific location, in a specific format. Scheme CreativeWork Used for Data download Class & Subclasses CreativeWork, Dataset Values expected DataDownload endDate O Definition The end date and time of the item (in ISO 8601 date format). Scheme CreativeWork Used for Publication date - end of series Class & Subclasses CreativeWork, CreativeWorkSeries Values expected Date, DateTime illustrator O Definition The illustrator of the book. Scheme CreativeWork Used for Illustrator Class & Subclasses CreativeWork, Book Values expected Person itemReviewed O Definition The item that is being reviewed/rated. Scheme CreativeWork Used for Item reviewed Class & Subclasses CreativeWork Values expected Thing material O Definition A material that something is made from, e.g. leather, wool, cotton, paper. Scheme CreativeWork Used for Material Class & Subclasses CreativeWork Values expected Text, URL mentions O Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 64 Class & Subclasses MediaObject Values expected Text, URL sourceOrganization O Definition The Organization on whose behalf the creator was working. Scheme MediaObject Used for Affiliated organisation Class & Subclasses CreativeWork Values expected Organization text O Definition The textual content of this CreativeWork. Scheme MediaObject Used for Full text/Transcription/Annotation Class & Subclasses CreativeWork Values expected Text thumbnailUrl O Definition A thumbnail image relevant to the Thing. Scheme MediaObject Used for Thumbnail Class & Subclasses CreativeWork Values expected URL transcript O Definition If this MediaObject is an AudioObject or VideoObject, the transcript of that object. Scheme MediaObject Used for Transcript Class & Subclasses CreativeWork, AudioObject, VideoObject Values expected Text 1.1.2 Scheme Person - https://schema.org/Person identifier [Created by system if not provided by partner] M Definition The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details. Scheme Person Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 65 Used for Identifier Class & Subclasses Thing Values expected Text, URL name M Definition The name of the item. Scheme Person Used for Full name Class & Subclasses Thing Values expected Text provider M Definition The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller. Scheme Person (system element) Used for Data provider Class & Subclasses Extension Values expected Person, Organization sdDatePublished M Definition Indicates the date on which the current structured data was generated / published. Typically used alongside sdPublisher Scheme Person (system element) Used for Record publication date Class & Subclasses Extension Values expected Date sdLicense M Definition A license document that applies to this structured data, typically indicated by URL. Scheme Person (system element) Used for Record license Class & Subclasses Extension Values expected URL sdPublisher M Definition Indicates the party responsible for generating and publishing the current structured data markup, typically in cases where the structured data is derived automatically from existing published content but published on a different site. For example, student projects and open data initiatives often re-publish existing content with more explicitly structured metadata. The sdPublisher property helps make such practices more explicit. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 66 Scheme Person (system element) Used for Record publisher Class & Subclasses Extension Values expected Organization url M Definition URL of the item. Scheme Person (system element) Used for Persistent ReIReS link Class & Subclasses Thing Values expected URL alternateName R Definition An alias for the item. Scheme Person Used for Alternate name Class & Subclasses Thing Values expected Text birthDate R Definition Date of birth. Scheme Person Used for Date of birth Class & Subclasses Person Values expected Date birthPlace R Definition The place where the person was born. Scheme Person Used for Birth place Class & Subclasses Person Values expected Place deathDate R Definition Date of death. Scheme Person Used for Date of death Class & Subclasses Person Values expected Date Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 67 deathPlace R Definition The place where the person died. Scheme Person Used for Death place Class & Subclasses Person Values expected Place description R Definition A description of the item. Scheme Person Used for Description Class & Subclasses Thing Values expected Text familyName R Definition Family name. In the U.S., the last name of a Person. This can be used along with givenName instead of the name property. Scheme Person Used for Family name Class & Subclasses Person Values expected Text givenName R Definition Given name. In the U.S., the first name of a Person. This can be used along with familyName instead of the name property. Scheme Person Used for Given name Class & Subclasses Person Values expected Text nationality R Definition Nationality of the person. Scheme Person Used for Nationality Class & Subclasses Person Values expected Country sameAs R Definition URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website. Scheme Person Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 68 Used for Source record Class & Subclasses Thing Values expected URL additionalName O Definition An additional name for a Person, can be used for a middle name. Scheme Person Used for Additional name Class & Subclasses Person Values expected Text affiliation O Definition An organization that this person is affiliated with. For example, a school/university, a club, or a team. Scheme Person Used for Affiliation Class & Subclasses Person Values expected Organization alumniOf O Definition An organization that the person is an alumni of. Scheme Person Used for Alumni Class & Subclasses Person Values expected Organization, EducationalOrganization children O Definition A child of the person. Scheme Person Used for Child Class & Subclasses Person Values expected Person colleague O Definition A colleague of the person. Scheme Person Used for Colleague Class & Subclasses Person Values expected Person, URL follows O Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 69 Definition The most generic uni-directional social relation. Scheme Person Used for Follows Class & Subclasses Person Values expected Person funder O Definition A person or organization that supports (sponsors) something through some kind of financial contribution. Scheme Person Used for Funder Class & Subclasses Person Values expected Person, Organization gender O Definition Gender of the person. While http://schema.org/Male and http://schema.org/Female may be used, text strings are also acceptable for people who do not identify as a binary gender. Scheme Person Used for Gender Class & Subclasses Person Values expected GenderType, Text hasOccupation O Definition The Person's occupation. For past professions, use Role for expressing dates. Scheme Person Used for Occupation Class & Subclasses Person Values expected Occupation honorificPrefix O Definition An honorific prefix preceding a Person's name such as Dr/Mrs/Mr. Scheme Person Used for Honorific prefix Class & Subclasses Person Values expected Text honorificSuffix O Definition An honorific suffix preceding a Person's name such as M.D. /PhD/MSCSW. Scheme Person Used for Honorific suffix Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 70 Class & Subclasses Person Values expected Text image O Definition An image of the item. This can be a URL or a fully described ImageObject. Scheme Person Used for Image Class & Subclasses Thing Values expected ImageObject, URL jobTitle O Definition The job title of the person (for example, Financial Manager). Scheme Person Used for Job title Class & Subclasses Person Values expected Text knows O Definition The most generic bi-directional social/work relation. Scheme Person Used for Knows Class & Subclasses Person Values expected Person memberOf O Definition An Organization to which this Person or Organization belongs. Inverse property: member. Scheme Person Used for Membership Class & Subclasses Person Values expected Organization parent O Definition A parent of this person. Scheme Person Used for Parent Class & Subclasses Person Values expected Person relatedTo O Definition The most generic familial relation. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 71 Scheme Person Used for Family Class & Subclasses Person Values expected Person sibling O Definition A sibling of the person. Scheme Person Used for Sibling Class & Subclasses Person Values expected Person sponsor O Definition A person or organization that supports a thing through a pledge, promise, or financial contribution. e.g. a sponsor of a Medical Study or a corporate sponsor of an event. Scheme Person Used for Sponsor Class & Subclasses Person Values expected Person, Organization spouse O Definition The person's spouse. Scheme Person Used for Spouse Class & Subclasses Person Values expected Person subjectOf O Definition A CreativeWork or Event about this Thing. Inverse property: about. Scheme Person Used for Subject of Class & Subclasses Thing Values expected CreativeWork, Event worksFor O Definition Organizations that the person works for. Scheme Person Used for Employer Class & Subclasses Person Values expected Organization Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 72 8.2.3 Scheme Organization - https://schema.org/Organization identifier [Created by system if not provided by partner] M Definition The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details. Scheme Organization Used for Identifier Class & Subclasses Thing Values expected Text, URL name M Definition The name of the item. Scheme Organization Used for Name Class & Subclasses Thing Values expected Text provider M Definition The service provider, service operator, or service performer; the goods producer. Another party (a seller) may offer those services or goods on behalf of the provider. A provider may also serve as the seller. Scheme Organization (system element) Used for Data provider Class & Subclasses Extension Values expected Person, Organization sdDatePublished M Definition Indicates the date on which the current structured data was generated / published. Typically used alongside sdPublisher Scheme Organization (system element) Used for Record publication date Class & Subclasses Extension Values expected Date sdLicense M Definition A license document that applies to this structured data, typically indicated by URL. Scheme Organization (system element) Used for Record license Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 73 Class & Subclasses Extension Values expected URL sdPublisher M Definition Indicates the party responsible for generating and publishing the current structured data markup, typically in cases where the structured data is derived automatically from existing published content but published on a different site. For example, student projects and open data initiatives often re-publish existing content with more explicitly structured metadata. The sdPublisher property helps make such practices more explicit. Scheme Organization (system element) Used for Record publisher Class & Subclasses Extension Values expected Organization url M Definition URL of the item. Scheme Organization (system element) Used for Persistent ReIReS link Class & Subclasses Thing Values expected URL alternateName R Definition An alias for the item. Scheme Organization Used for Alternate name Class & Subclasses Thing Values expected Text description R Definition A description of the item. Scheme Organization Used for Description Class & Subclasses Thing Values expected Text sameAs R Definition URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website. Scheme Organization Used for Source record Class & Subclasses Thing Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 80 8.3 Old Service Description Template Grey cells indicate attributes removed from the current SDT because either none of the 14 pilot services populated them or they have been deemed irrelevant by the Data Unit. 1. Basic Information ID Name Ecotheology course Abbreviation Ecotheology course Resource Organisation Volos Academy for Theological Studies Resource Providers Webpage https://churchgoesgreen.acadimia.org/ 2. Marketing Information Description The blog "Green Orthodoxy: The Orthodox Church facing climate change" is an initiative of the Volos Academy of Theological Studies within the "Green Orthodoxy and parallel actions" program implemented in collaboration with WWF Greece. It aspires to publish and republish topical texts-interventions by theologians and also specialist scientists, news and information on the activity of the Orthodox Churches in environmental matters, as well as informative notes, videos, images on the latest developments regarding relevant issues at the national level, European as well as global news (always with reference to the source). Tagline We publish and republish timely texts-interventions by theologians and also specialist scientists, news and information about the activity of the Orthodox Churches in environmental matters. Logo https://churchgoesgreen.acadimia.org/wpcontent/uploads/2023/07/acadimia_logo_gr.png Multimedia Use case 3. Classification Information Scientific Domain Humanities Scientific Subdomain Philosophy, ethics and religion Category Data Storage Subcategory Archive; Digital preservation Category Scholarly Communication Subcategory Writing; Publication Category Education & Training Subcategory Online Courses; Open Registration Courses; Inhouse Courses; Training Tool; Training Platform Target Users Researchers; Research groups; Students; Access Type Physical; Remote; Virtual;Mail-in Access Mode Free; Peer-reviewed; Paid Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 81 Tags Rename to keywords (like clusters) & will be added by RESILIENCE teams afterwards 4. Geographical and Language Availability Information Geographical Availability World Language Greek, English, French 5. Resource Location Information Resource Geographic Location 6. Contact Information => for internal use only Main Contact/Resource Owner Public Contact Helpdesk 7. Maturity Information Technology Readiness Level 1 - basic principles observed Life Cycle Status Already answered by RSRL Certifications Standards Open Source Technologies Version Last Update Change Log 8. Dependencies Information Required Resources Has become a ‘Technical’ field named ‘Dependencies’ Related Resources Related Platforms Catalogue 9. Attribution Information Funding Body Funding Program Grant/Project Name 10. Management Information Helpdesk Page User Manual Terms Of Use Privacy Policy Access Policy Resource Level Training Information Has become a ‘Technical’ only field Status Monitoring Maintenance 11. Access and Order Information Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 82 Order Type Open Access Order 12. Financial Information Payment Model Pricing For a Data/Technical Resource: 13. Data Source Policies Submission policy URL Preservation policy URL Version control Persistent Identity Systems - Research Data Persistent Identity Systems - Research Software Persistent Identity Systems - Research Literature Persistent Identity Systems - Other research products 14. Data Source Content Jurisdiction Research Infrastructure Data Source Classification Scientific Database Research Product Types Research Data => Specifically related to OpenAIRE so not relevant Thematic Yes 15. Research Product Policies Research Product Licensing Research Product Access Policy Open access 16. Research Product Metadata Research Product Metadata Licensing Research Product Metadata Access Policy Open access Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 83 8.4 Current Service Description Template Optional Fields (O) Field Description Type Example (ReIReSearch) Abbreviation Abbreviation of the Service Name String ReIReSearch (Extra) Resource Providers The name(s) of (all) the other Provider(s) involved in managing or delivering the Service. String Tagline Short catchphrase for marketing and advertising purposes. It will be usually displayed close to the Service name and should refer to the main value or purpose of the Service. String Religious Studies Discovery Environment Logo Link to the logo/visual identity of the Service. The logo will be visible at the Portal. If there is no specific logo for the Service the logo of the Provider may be used. URL or File https://s3.us-east1.amazonaws.com/twdesk/i/166024/doclogo/944 0366d-e35a-44cb-af1dd00b6e7b8252.jpeg Scientific Domain(s) The branch of science, scientific discipline that is related to the Service. Pre-filled list Humanities Scientific Subdomain(s) The subbranch of science, scientific subdiscipline that is related to the Service. Pre-filled list Philosophy, Ethics & Religion Geographical Availability Locations where the Service is offered. String World Contact Phone Number Phone number of the Service’s contact person or a generic email of the Provider to be displayed publicly at the portal. Phone number +32 16 32 22 66 Funding Body Name or webpage of the funding body that supported the development and/or operation of the Service. String or URL European Commission Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 84 Field Description Type Example (ReIReSearch) Funding Program Name or webpage of the funding program that supported the development and/or operation of the Service. String or URL Horizon 2020 Grant/Project Name Name or webpage of the project that supported the development and/or operation of the Service. String or URL RESILIENCE - https://www.resilience-ri.eu Helpdesk Email The email to ask more information from the Provider about this Service; can be the same as the contact email Email address [email protected] Helpdesk Phone The phone number to ask more information from the Provider about this Service; can be the same as the contact phone number. Phone number +32 16 32 22 66 User Manual Link to the Service user manual and documentation; can be the same as the helpdesk docs. URL https://reiresearch.helpdocs ite.com/ Technical Fields (T) Field Description Type Example TRL The TRL according to the official TRL Scale Integer 1-9 7 Privacy Policy Link to the privacy policy applicable to the Service. String or URL https://reiresearch.eu/#/eul a Training Information Webpage to training information on the Service. URL https://reiresearch.helpdoc site.com/ Dependencies List of other resources or software required to use this Service. String Version If data versioning is supported: version of the Service that is in force. String Change Log Summary of the Service features updated from the previous version. String or URL Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 85 Field Description Type Example Jurisdiction The type of geographical jurisdiction that defines the user group. Pre-defined List Research Infrastructure Data Source Classification The specific type of the data source. Pre-defined List Scientific Database Thematic Boolean value specifying if the data source is dedicated to a given discipline or is instead discipline agnostic Boolean True Research Product Licensing Licenses under which the research products contained within the data sources can be made available. Repositories can allow a license to be defined for each research product, while for scientific databases the database is typically provided under a single license. String or URL https://reiresearch.eu/#/eul a Research Product Access Policy Same as Product Licensing String or URL Open access Research Product Metadata Licensing Metadata Policy for information describing items in the repository: Access and re-use of metadata String or URL https://reiresearch.eu/#/eul a Research Product Metadata Access Policy Same as Research Product Metadata Licensing String or URL Open access Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 86 8.5 RSRL Scale Examples RSRL Online Platform – ReIReSearch Training – On AI Tools Physical Service – Book Heritage Lab S1 – Idea Vision paper describes a unified discovery interface for religious‑studies data; no code written, data model only sketched. Concept note lists learning objectives and AI tools (eg: OCR, LLM prompt‑engineering); no material prepared yet. White‑paper outlines need for a specialised book‑heritage conservation facility; space and equipment only identified on paper. S2 – Concept outlined High‑level architecture and metadata mapping drafted; basic feasibility confirmed with KU Leuven IT; still no users. Draft syllabus and session outline produced; pilot slide‑deck created; feasibility (time, software licences) checked. Floor‑plan, equipment list and workflow diagram created; health & safety and cost estimates reviewed; no external users. S3 – Feasibility Prototype Rudimentary demo runs locally on a laptop with dummy records; code pushed to a private GitHub repo. Internal ½‑day trial delivered to a few colleagues using sample datasets; feedback collected; materials in shared (private) drive. One work‑bench fitted with trial equipment (e.g., non‑destructive spectrometer); curator tests procedure on sample volume. S4 – Lab Prototype Prototype deployed on dev server; limited amount of real records ingested; 3–5 invited colleagues test search & give feedback. Full training dry‑run (at least 5 participants) held; draft training material and exercise datasets shared; post‑session survey analysed. Partial lab operational (two key instruments installed); invited specialists run test treatments; risk‑assessment updated. S5 – Pilot (limited public) Beta version reachable at a public URL; signup on request; draft user docs online. Beta training advertised internally; 10+ researchers attend; training material and slide‑deck downloadable; dedicated contact e‑mail. Limited external access by application; booking form published; draft user manual and pricing model circulated. Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 87 S6 – Community Pilot Beta version available to external users; user docs and helpdesk email public; privacy & access policies published. Course opened to externals (eg: RESILIENCE nodes); 25+ attendees across 3 sessions; feedback tracker and code‑of‑conduct online. Open call results in ≥ 5 external projects; safety protocols signed; basic KPI dashboard (users, hours, failures) maintained. S7 – Operational Open public launch; stable URL, versioned releases, 99 % uptime target; searchable via RESILIENCE catalogue; helpdesk that’s smoothly run. Scheduled regularly or bookable on demand (online & onsite); certified trainers; FAQ & helpdesk online. Equipment bookable through online system; SOPs approved; accredited staff on duty; first formal Service‑Level Appendix signed. S8 – Managed Service Formal MoU with LIBIS & IT; automated backups, monitoring & 3‑year sustainability plan. Institutional QA process, peer‑reviewed training material, micro‑credential certificates; multi‑year funding line secured. Framework SLA with KU Leuven; preventive‑maintenance contracts, calibrated instruments; budget earmarked for 3+ years. S9 – Established / Trusted ≥ 3 years at S8; indexed by EOSC/SSHOC; cited in peer‑reviewed articles; DOIs minted for harvested datasets. Track‑record of ≥ 3 years; > 500 alumni; recognised in European training catalogues; evaluations show sustained impact. ≥ 3 years of uninterrupted service; referenced in conservation guidelines & scholarly publications; Document Title: D2.11 Master Data Management Status: FINAL Version: 01.00 88 9 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 — HORIZON INFRA-2021-DEV-02 R2 03/09/2024 D2.4 Data Management Plan R3 29/03/2024 D2.1 Services Preparation and Implementation Strategy R4 29/05/2024 D2.2 User Services Catalogue version 01.00