<p>Attending</p>

<p>OPENAIRE: N. Manola, P. Oliveira, Paolo Manghi</p>

<p>EOSC-hub: M. v. Sanden, C. Cacciari, T. Ferrari, G. Sipos, D. Scardaci, P. Weber, J. Reetz (remote)</p>

<p>DARIAH: P. Wieder, M. Martens</p>

<p>==&gt; Introduction to collaboration (Mark)</p>

<p>==&gt; DARIAH. Introduction at Compute and data level within EOSC</p>

<p>DARIAH: data production. How can it be linked to OPENAIRE? DARIAH repository: heavily involved in OpenAIRE, but repository is not OpenAIRE ready. End user tool: to search the repository and if they publish data goes to the repository to share it. Repository: 1 hosted in Germany for DARIAH / Digital Humanities (no discussion yet on national offering with national instances e.g. in France) --&gt; can national infrastructures can be shared at European level. So: identity one or two large platforms for the whole of DARIAH. Base technology CDSTAR (object store) for the EGI hosted service compliant</p>

<p>Natalia: linking at AAI level?</p>

<p>Mike: research dashboard. Platform for annotation, release annotation for reuse, only after production of article or book. Research object has to be released. Annotation is published with a timestamp.</p>

<p>Manghi: publicize workflow, data, VM before pbulication (continous publishing)</p>

<p>DARIAH publishes the data repository and gateway in the EOSC-hub marketplace, get processing. Diagram developed</p>

<p>- AAI integration</p>

<p>- use thematic analytics services (DARIAH gateway)</p>

<p>- find data, import, process, generate output</p>

<p>- publish output in DARIAH repository</p>

<p>- DARIAH repository is harvested by OpenAIRE</p>

<p>Marios: AppDB allows the definition of topologies (which can be organized as research objects as a bundle of data and VMs for example). Gergely: research object has elements of provenance etc. and it is broader</p>

<p>&nbsp;</p>