# Scope of the call

<div id="bkmrk-"></div>##### <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Main goals of the call: Leverage potential in the academic research data landscape</span></span>

<span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB"><span style="background-color: rgb(255, 255, 255);">Dealing with data in research contexts is as important as it is challenging. In many cases, good data practices encounter missing processes, lacking awareness and cultures to be sustainable, viable and impactful. </span>While there have been some substantial public investments in digitalization and data infrastructures in the last years, there are often the human resources missing to fully capitalize on these investments. However, in many cases, good ideas cannot be realized because money and attention are missing. Most universities and research institutions have also developed digitalization and data strategies which need to be implemented via concrete projects and undertakings.</span></span>

<span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB"> This call, thus, also aims to **support institutions in their strategic capacity**. In this context, it is crucial that applications developed are not one-offs, but need to be maintained and developed beyond the project duration. </span></span>

- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Projects should engage with current needs in the promotion of good data practices in a defined context as **"executable applications" for data in research**. "Applications" should be understood widely as, e.g., </span></span>transferable use cases, software prototypes, modelling, information/data models (metadata, schema definitions and ontologies), data environments.  
    <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB"> "Executable" means that the applications developed should be easily integrated into code or software environments in due course (either in existing or future data environments or workflows). They should be transferable and scalable.</span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Projects should provide applications delivering <span style="background-color: rgb(255, 255, 255);">**useful services to research,** either by rendering existing data processes more efficient or by providing tools that allow for new approaches. The outcomes of the projects shall support data collection for research and the further use of research data, however, should not be tied to a specific research project </span></span></span>but be of wider relevance, also supporting interoperability.<span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB"><span style="background-color: rgb(255, 255, 255);"> </span></span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Projects can tackle research data related challenges in **any scientific area**, i.e., are not limited to computer science. However, the nature of the projects requires the integration of IT competences into the projects. </span></span>

##### <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">What is the purpose of the applications developed?</span></span>

<span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">The purpose of the applications should be directed towards supporting research activities with/for data in a broad sense. It may connect to other tasks such as teaching, administration or third mission, but the focus should be on the development of applications for research activities. </span></span>

##### <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">What should be the output of the project?</span></span>

<span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">WWTF asks for "code" rather than text, training or talking: The output should be concrete applications in the form of use cases, best practices, data sandboxes etc. and should include code, (information) models, ontologies, application prototypes and alike. These applications - based on their code-like nature - should have the potential to be implemented in data environments/workflows in a seamless manner. The potential for transferability and scalability is an important criterion for selection. </span></span>

##### <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Activities that do not count as output</span></span>

<span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Activities and outputs listed below are **<span style="text-decoration: underline;">not </span>**<span style="text-decoration: underline;">eligible for funding</span>: </span></span>

- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">The production of primary research data </span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">The </span></span><span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">preparation of existing data sets for secondary / further use by other researchers. However, concrete data sets may serve as use cases for broader applications</span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">The creation of a network as a sole output</span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Training and education activities as the sole output</span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">The procurement and installation of hardware </span></span>
- <span style="background-color: rgb(255, 255, 255);"><span lang="EN-GB">Purely text-based outputs such as strategy papers or guidelines</span></span>

##### <span lang="EN-US">Defining (a) potential user group(s)</span>

<span lang="EN-US">Projects need to define (a) potential user group(s) of the application developed. Projects should have benefits for wider user groups beyond the context of the project. These user groups can be located within the own institution or across institutions. Applications can also target disciplinary communities independent of institutional settings. </span>

##### <span lang="EN-US">Sustainability and impact</span>

<span lang="EN-US">Proposals need to define how the applications developed can be consolidated/maintained and further developed beyond the lifespan of the project itself. Projects should also define how their project links to institutional data / digitalization strategies as well as (potentially) to inter-university activities. </span>

##### <span lang="EN-US">Dissemination and exploitation strategies</span>

<span lang="EN-US">Proposals should define in what ways their outputs should be shared, be it either open or in form of licensing (monetarization). Keep in mind that WWTF prefers open science / open data approaches according to the FAIR principles, however, monetarization strategies might be justified in the context of specific projects. </span>

<span lang="EN-US">Applicants need to present a dissemination plan and strategy. </span>

##### Project team

The project team may include academic researchers, and/or data stewards, IT- or administrative personnel, and/or relevant user groups. The PI&amp;C must not necessarily be a scientist.