<figure><img src="image_1.png" /></figure>

HAL
open science

# D 4.1 - Gap Analysis of DARIAH Research Infrastructure

Stefan Buddenbohm, Raisa Barthauer

► To cite this version:

Stefan Buddenbohm, Raisa Barthauer. D 4.1 - Gap Analysis of DARIAH Research Infrastructure. [Research Report] DARIAH. 2017, pp.36. hal-01663594v2

HAL Id: hal-01663594

https://hal.science/hal-01663594v2

Submitted on 29 Jan 2018

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_2.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
<figure><img src="image_3.png" /></figure>

D4.1 Gap Analysis of DARIAH Research Infrastructure

DESIR

DARIAH ERIC Sustainability Refined

INFRADEV-03-2016-2017 - Individual support to ESFRI and other world-class research infrastructures

Grant Agreement no.: 731081

Date: 01-12-2017

Version: 0.5

<figure><img src="image_4.png" /></figure>

DESIR has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 731081
<table><tr><td>Grant Agreement no.:</td><td>731081</td></tr><tr><td>Programme:</td><td>Horizon 2020</td></tr><tr><td>Project acronym:</td><td>DESIR</td></tr><tr><td>Project full title:</td><td>DARIAH-ERIC Sustainability Refined</td></tr><tr><td>Partners:</td><td>DIGITAL RESEARCH INFRASTRUCTURE FOR THE ARTS AND HUMANITIES<br>GEORG-AUGUST-UNIVERSITAET GOETTINGEN STIFTUNG OEFFENTLICHEN RECHTS<br>UNIVERSITEIT GENT<br>UNIWERSYTET WARSZAWSKI<br>FACULDADE DE CIÊNCIAS SOCIAIS E HUMANAS DA UNIVERSIDADE NOVA DE LISBOA<br>CENTAR ZA DIGITALNE HUMANISTICKE NAUKE<br>GOTTFRIED WILHELM LEIBNIZ UNIVERSITAET HANNOVER<br>INSTITUT NATIONAL DE RECHERCHE EN INFORMATIQUE ET AUTOMATIQUE<br>KING'S COLLEGE LONDON<br>UNIVERSITY OF GLASGOW<br>KNIHOVNA AV CR V. V. I.<br>HELSINGIN YLIOPISTO<br>SIB INSTITUT SUISSE DE BIOINFORMATIQUE<br>UNIVERSIDAD NACIONAL DE EDUCACIÓN A DISTANCIA<br>UNIVERSITY OF HAIFA<br>UNIVERSITY OF NEUCHATEL</td></tr><tr><td>Topic:</td><td>INFRADEV-03-2016-2017</td></tr><tr><td>Project Start Date:</td><td>01-01-2017</td></tr><tr><td>Project Duration:</td><td>36 months</td></tr><tr><td>Title of the document:</td><td>D4.1 Gap Analysis of DARIAH Research Infrastructure</td></tr><tr><td>Work Package title:</td><td>WP4 Technology</td></tr><tr><td>Estimated delivery date:</td><td>December 2017</td></tr><tr><td>Lead Beneficiary:</td><td>UGOE-SUB</td></tr><tr><td>Author(s):</td><td>Stefan Buddenbohm (buddenbohm@sub.uni-goettingen.de)</td></tr></table>
<table><tr><td></td><td>Raisa Barthauer (barthauer@sub.uni-goettingen.de)</td></tr><tr><td>Quality Assessor(s):</td><td>Claudio Leone (leone@sub.uni-goettingen.de)<br>Yoann Moranville (yoann.moranville@dariah.eu)</td></tr><tr><td>Keywords:</td><td>DARIAH, research infrastructure, sustainability, technology, gap analysis,<br>demonstrators, visualisation, scholarly content management</td></tr></table>

Revision history

<table><thead><tr><td>Version</td><td>Date</td><td>Author</td><td>Beneficiary</td><td>Description</td></tr></thead><tbody><tr><td>0.1</td><td>30.06.2017</td><td>Stefan Buddenbohm</td><td>UGOE-SUB</td><td>First draft prepared for the F2F on July 11th in Hanover</td></tr><tr><td>0.2</td><td>20.10.2017</td><td>Stefan Buddenbohm</td><td>UGOE-SUB</td><td>Second draft based on the results from the F2F; Partner descriptions, completion of inventory, diagrams</td></tr><tr><td>0.3</td><td>10.11.2017</td><td>Raisa Barthauer</td><td>UGOE-SUB</td><td>Diagrams</td></tr><tr><td>0.4</td><td>17.11.2017</td><td>Stefan Buddenbohm</td><td>UGOE-SUB</td><td>Discussion of report at WP F2F on November 21st in Berlin</td></tr><tr><td>0.5</td><td>1.12.2017</td><td>Stefan Buddenbohm</td><td>UGOE-SUB</td><td>Completion of report and final feedback round with DESIR consortium</td></tr><tr><td>0.6</td><td>14.12.2017</td><td>All partners</td><td>All partners</td><td>Global checking</td></tr><tr><td>1.0</td><td>15.12.2017</td><td></td><td></td><td>Submission</td></tr></tbody></table>
Executive Summary

DESIR (DARIAH ERIC Sustainability Refined) work package 4 Technology contributes to DARIAH's long-term sustainability by technologically enhancing DARIAH's research infrastructure and services. To this end four new and innovative technology areas – entity-based search, scholarly content management, text analytic services and visualisation – shall shape DARIAH's profile.

The present document forms a prerequisite for the aforementioned objective and conducts
for that reason a gap analysis of the current DARIAH infrastructure, concentrating on four
areas: text analytic services, scholarly content management, entity-based search and
visualisation. The competencies and resources of the three technology partners in this work
package correspond to these four areas. The conceptual models - as proposal for the
identified gaps - are subject to later deliverables in the project, but in the course of
undertaking the gap analysis already first impressions of possible conceptual models are
apparent and will be presented here. The concept of the gap analysis in this context means
not only to identify missing tools or services in the DARIAH infrastructure landscape but also
to recognize potential for enhancement with already existing tools and services.
<table><thead><tr><th colspan="3">Nature of the deliverable</th></tr></thead><tbody><tr><td>✓</td><td>R</td><td>Document, report</td></tr><tr><td></td><td>DEM</td><td>Demonstrator, pilot, prototype</td></tr><tr><td></td><td>DEC</td><td>Websites, patent filings, videos, etc.</td></tr><tr><td></td><td>OTHER</td><td></td></tr></tbody></table><table><thead><tr><th colspan="3">Dissemination level</th></tr></thead><tbody><tr><td>✓</td><td>P</td><td>Public</td></tr><tr><td></td><td>CO</td><td>Confidential only for members of the consortium (including the Commission Services)</td></tr><tr><td></td><td>EU-RES</td><td>Classified Information: RESTREINT UE (Commission Decision 2005/444/EC)</td></tr><tr><td></td><td>EU-CON</td><td>Classified Information: CONFIDENTIEL UE (Commission Decision 2005/444/EC)</td></tr><tr><td></td><td>EU-SEC</td><td>Classified Information: SECRET UE (Commission Decision 2005/444/EC)</td></tr></tbody></table>

## Disclaimer

DESIR has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No 731081. This publication reflects the views only of the author, and the Commission cannot be held responsible for any use which may be made of the information contained therein.
## Table of Contents

<table><tr><td>Revision history</td><td>3</td></tr><tr><td>Executive Summary</td><td>4</td></tr><tr><td>Disclaimer</td><td>5</td></tr><tr><td>Table of Contents</td><td>6</td></tr><tr><td>1 Introduction and scope of the report</td><td>7</td></tr><tr><td>2 Technology partners in WP4</td><td>8</td></tr><tr><td>2.1 Applied technologies among the technology partners</td><td>9</td></tr><tr><td>2.2 Service roles among the technology partners</td><td>11</td></tr><tr><td>3 Partial catalogue of services and tools within DARIAH</td><td>14</td></tr><tr><td>3.1 Existing cataloguing activities within DARIAH</td><td>14</td></tr><tr><td>3.2 Inventory of DARIAH activities in four areas</td><td>16</td></tr><tr><td>4 Interpretation</td><td>28</td></tr><tr><td>4.1 Methodology</td><td>28</td></tr><tr><td>4.2 Interpretation of findings</td><td>29</td></tr><tr><td>5 Conclusions</td><td>32</td></tr><tr><td>6 Register of tables and figures</td><td>35</td></tr><tr><td>7 Sources</td><td>36</td></tr></table>
# 1 Introduction and scope of the report

> "Presently, there exists a vast library of tools, services, software [...]. One of the principal aims of DARIAH is to promote and facilitate the re-use of such materials, in order to accelerate new research, enable a more responsive and open publishing environment for humanities data, allow collaborations to be concluded more efficiently, with the overall goal of supporting not just digital services and complex digital objects in arts and humanities research but to broaden and deepen the adoption of digital methods and digital workflows amongst humanities scholars."

This overall mission statement of DARIAH - the Digital Research Infrastructure for the Arts and Humanities<fnref n="2" /> - is also guiding the DESIR project.

Against this background the aim of work package 4 and the document at hand is twofold: first and foremost an inventory of the current DARIAH infrastructure according to four specific areas will be compiled. These areas include entity-based search, scholarly content management, text-analytic services and visualisation. This structured overview represents the current status quo not only in terms of general infrastructure but also in terms of individual tools, services or software, being provided or maintained by DARIAH.

The inventory should ideally cover in this context all national branch activities – e.g. DARIAH-DE or DARIAH-FR – and includes also DARIAH-EU resp. the DARIAH ERIC<fnref n="3" /> as supranational administration umbrella for all DARIAH activities. Nevertheless our gap analysis<fnref n="4" /> will only result in a fragmentary picture of all existing activities, also because it is not necessary in this respective context. On the one hand this is connected to the by now huge bandwidth of European DARIAH activities and the steady expansion in terms of participating countries, community growth or differentiating services and resources. On the other hand there is currently no overarching inventory or registry, although there are several inventories on a national level. The upcoming DARIAH market place could possibly be some kind of central information hub for services, tools and resources - at least for the in-kind contributions of the partner countries and will be marked in the subsequent chapter. With regard to the description of work this fragmentary picture shouldn't be a problem as the main outcome of this work package shall be conceptual models with potential of contributing to the DARIAH landscape.

Secondly the resulting DARIAH inventory will undergo a gap analysis with respect to technology specialisations on side of the DESIR technology partners. The gap analysis will

<footnote n="1">¹ Baillot, Mertens, Romary (2016), p. 153</footnote>

<footnote n="2">² http://www.dariah.eu/</footnote>

<footnote n="3">³ European Research Infrastructure Consortium</footnote>

<footnote n="4">⁴ The term gap analysis in the context of this document is not to be confused with the gap analysis in an economic sense, see https://en.wikipedia.org/wiki/Gap_analysis. Gap in our sense means gap in terms of infrastructure, services or resources.</footnote>
focus on four main areas which have been predetermined by the description of work for the DESIR project:

* entity-based search,

* scholarly content management,

* text-analytic services and

* visualisation.

The document at hand should not only identify gaps in the DARIAH inventory but rather explore possibilities to close the gaps. This step will be detailed subject of the subsequent deliverable D4.2 Conceptual Models. D4.2 has to present conceptual modules for the identified gaps with respect to the aforementioned four areas. The further process of work package 4 will subject the conceptual models to a code-sprint, validate them, and prepare a proof-of-concept.

## 2 Technology partners in WP4

The following table provides a short overview on the involved partners in this work package. It has to be seen in relation to the subsequent tables in this paper which form an additional information basis for the gap analysis.

<table><caption>Table 1: Technology partners in DESIR WP4</caption><thead><tr><td>Institution</td><td>Short description, focus of work</td><td>Employed technologies</td><td>Roles</td><td>Example</td></tr></thead><tbody><tr><td>UGOE-SUB Göttingen State and University Library, Research & Development Department</td><td>RDD: Develops new infrastructure services for research; largest R&D library in Germany; 2016: 15 FTE; 14 third-party funded projects; over 80% third-party funding; founded in 2002<br>Research data centres: collecting, enriching, curating and preserving data<br>Virtual research environments: collaborative data creation; processing and analysis</td><td>Java (web services); Javascript (Jquery, Ractive); RDF (esp. TGForms); existdb; elasticsearch; Maven; Jenkins; Puppet; Tomcat; public and private git repositories</td><td>developer (maintainer, provider)</td><td>TextGrid VRE and repository for scholarly editions; XML-TEI; Java-Backend; Eclipse-based Frontend for all OS; developed since 2005;<br>https://fontane-nb.dariah.eu<br>http://bdn-edition.de/<br>http://www.mayawoerterbuch.de</td></tr><tr><td>ICM Interdisciplinary Centre for Mathematical and Computational Modelling, University of Warsaw</td><td>Basic unit of the university; leading HPC and R&D centre in Poland; provides research infrastructure within ICT and HPC; interdisciplinary research; applied</td><td>C/C++; Fortran; Java(Web, Desktop); Scala; Python; JavaScript; R; GitHub; GitLab; SVN; Redmine; Jenkins; Maven; Apache/Tomcat; Hadoop ecosystem;</td><td>developer maintainer provider</td><td>VisNow - a generic visualization framework<br>http://visnow.icm.edu.pl</td></tr></tbody></table>
<table><thead><tr><th></th><th>mathematics; computational sciences and data science</th><th>multiple DB engines</th><th></th><th></th></tr></thead><tbody><tr><td>INRIA<br>Institut national de recherche en informatique et en automatique represented by the ALMAnaCH team (Automatic Language Modelling and Analysis & Computational Humanities)</td><td>INRIA is the French institute for computer science and applied mathematics; it promotes "scientific excellence for technology transfer and society"; divided in various research centres; no major policies in terms of software sustainability or applied technologies; only a centralised repository on GitLab is provided; development approach depends on specific team; open software; hosted externally</td><td>Java; Python; Javascript (jQuery, angularjs); Elasticsearch; lucene; mysql; Machine learning toolkits; NLP libraries; Maven; travis/jenkins; git; Json; XML (mostly TEI); XSLT</td><td>developer maintainer</td><td>(N)ERD - a (Named) entity recognition and disambiguation service:<br><a href="http://nerd.huma-num.fr">http://nerd.huma-num.fr</a><br><a href="http://github.com/kermitt2/nerd">http://github.com/kermitt2/nerd</a><br><br>GROBID - Generation Of Bibliographic Data<br><a href="http://github.com/kermitt2/grobid">http://github.com/kermitt2/grobid</a><br><a href="http://github.com/kermitt2/grobid-ner">http://github.com/kermitt2/grobid-ner</a><br><a href="http://github.com/kermitt2/grobid-quantities">http://github.com/kermitt2/grobid-quantities</a></td></tr><tr><td>L3S<br>at the University of Hanover</td><td>Research interests of L3S: web science (Twitter, Wikipedia, etc.); Big Data (Hadoop, Spark, etc.); Text Mining; NLP; Data Mining; Machine Learning; Crowdsourcing; applied technologies and methods depend on the respective project, there is no mandatory standard procedure</td><td>Java, Maven, Hadoop, Spark, (Scala), Python, Tomcat, MySQL, git, SVN, Jenkins, Weka, RapidMiner, Eclipse, IntelliJ, NLP libraries</td><td>developer maintainer provider</td><td>BibSonomy - a social bookmarking system for web links and literature references<br><a href="http://www.bibsonomy.org/">http://www.bibsonomy.org/</a></td></tr></tbody></table>

As extension of the preceding information compilation we prepared an overview on the partners' applied workflows and technologies in order to better understand the course of the work in work package 4. By this we are able to evaluate the DARIAH inventory right from the start with the available resources and competencies in mind as preparatory work for the collection of ideas for conceptual models or demonstrators.

## 2.1 Applied technologies among the technology partners

The following table lists the applied development, maintenance and provisioning technologies amongst the partners in WP4. This information can be useful to assess compatibilities or synergies in the development of the conceptual models.
<table><caption>Table 2: Applied technologies among the DESIR technology partners in WP4</caption><thead><tr><td>Question</td><td>ICM</td><td>INRIA</td><td>L3S</td><td>UGOE-SUB (RDD)</td></tr></thead><tbody><tr><td>What workflows or methods do you employ? (Agile/Scrum vs. Waterfall, DevOps vs. HandOff, Git-Flow, etc.)</td><td>Agile/Scrum-like/Hand Off/git-flow</td><td>N/A</td><td>git-flow</td><td>Git-flow, some devops</td></tr><tr><td>What programming languages do you use? Which framework?</td><td>Java, C/C++, Python, Scala</td><td>Java, Javascript, Python</td><td>Java, JavaScript, Python, Scala, PHP</td><td>Java, Javascript (JQuery, Ractive), HTML, PHP, Python, C, C++, C#</td></tr><tr><td>Where and how do you host your code?</td><td>Github, GitLab (private+public)</td><td>Github, GitLab</td><td>Bitbucket & GitHub (public code), GitLab (internal code)</td><td>GitHub (for public code), GitHub (for internal code), Openprojects (internal+public)</td></tr><tr><td>Are you applying automated testing (unit/ integration)? If yes, which tools?</td><td>Yes: Jenkins, Gitlab-CI</td><td>Yes (Travis/CircleCI) we also use codeCov and coveralls</td><td>Yes (Jenkins) - only for BibSonomy</td><td>Yes Jenkins, also Gitlab-CI and some Travis</td></tr><tr><td>Are you applying (formalised) code review?</td><td>Yes (some projects, e.g. VisNow)</td><td>No</td><td>No (Yes for BibSonomy)</td><td>No</td></tr><tr><td>In which way do you document your code?</td><td>Javadoc formalised in code review (VisNow).</td><td>Comments (however not always a shared approach)</td><td>Eclipse settings enforcing comments</td><td>Javadoc, sometimes just comments, in part with Sphinx</td></tr><tr><td>Where do you operate the systems?</td><td>Own HPC Centre</td><td>Inria research center server</td><td>Dedicated/computing centre server rooms in Hannover, Kassel and Würzburg</td><td>GWDG (local computing center)</td></tr><tr><td>How do you provide systems? Openstack/ VMWare/ Bare Metal</td><td>Bare Metal/ VMWare/KVM</td><td>Our team has some dedicated Bare Metal servers.</td><td>Bare Metal</td><td>VMWare for important Services, Openstack, Some test systems on KVM on Bare Metal</td></tr><tr><td>Do you use configuration management? (in ITIL sense or tools like puppet/ chef/ ansible)</td><td>Yes: SVN, Salt, Ansible, Puppet</td><td>The ALMAnaCH team has 5 servers. There are dedicated teams doing some basic maintenance. The rest is manual work. The servers are usually allocated for demos and heavy processing.</td><td>No (config in RCS)</td><td>Yes: Puppet, No ITIL</td></tr><tr><td>How do you document systems and their state?</td><td>Wiki, Nagios, Icing2</td><td>In a PAD, servers are usually not shared among many people.</td><td>Wiki, Nagios</td><td>Wiki, Nagios</td></tr><tr><td>Do you use tools for time series analytics / metrics?</td><td>Yes: MRTG, Munin, Zabbix</td><td>No</td><td>No</td><td>Yes: Grafana for Telegraf Data</td></tr><tr><td>Web/Usage Analytics</td><td>Yes: Piwik, Other</td><td>No</td><td>Awstats, Piwik</td><td>Piwik</td></tr></tbody></table>
## 2.2 Service roles among the technology partners

The table below collects some meta-information on the roles of the technology partners. Aim of this paragraph is to be able to evaluate the yet to come conceptual models in a strategic perspective. Context: it is not uncommon that service are being developed by an institution and that the same institution subsequently takes further care of the service, be it as service provider, maintainer or in a developer role. As long as the institution already fulfils all of these roles, this may be unproblematic. In practice many institutions are unhappy with the maintainer and provider role but fulfil them given that there is no regulating policy available for this issue.

<table><caption>Table 3: Service roles among technology partners in DESIR WP4 (self assessment)</caption><thead><tr><td>In which service roles do you see your institution?</td><td>ICM</td><td>INRIA</td><td>L3S</td><td>UGOE-SUB</td></tr></thead><tbody><tr><td>Researcher</td><td>X<sup>5</sup></td><td>X</td><td>X</td><td>X</td></tr><tr><td>Developer</td><td>X</td><td>X</td><td>X</td><td>X</td></tr><tr><td>Maintainer</td><td>X</td><td></td><td></td><td></td></tr><tr><td>Provider</td><td>X</td><td></td><td></td><td></td></tr></tbody></table>

<figure><img src="image_5.png" /><figcaption>Figure 1: Service roles of technology partners in DESIR</figcaption></figure>

<footnote n="5">⁵ X = applies.</footnote>
The abovementioned diagram has to be read with some scepticism as with one exception – ICM – all partners envisage themselves not in the service provider role. Partly and motivated by the development and further support for certain services a partner might be sliding into a maintainer and/or provider role but usually don’t take this role. Read with a certain degree of sincerity one can assume that all partner institutions see their focus on research and research-related development activities. Maintenance and provision comes inevitably here and there into effect but is clearly not seen as work focus and is always dependent on the available funding resources. This leads to certain consequences for the development of digital services and resources, mainly in terms of standardisation and documentation.

## 2.3 Current services or software among the technology partners

<table><caption>Table 4: Development and service competencies among the technology partners in DESIR WP4</caption><thead><tr><td>Service</td><td>Partner</td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualisation</td><td>Other</td></tr></thead><tbody><tr><td>https://www.bibsonomy.org/</td><td>L3S</td><td>Social Bookmarking</td><td>X<sup>6</sup></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://git.l3s.uni-hannover.de/</td><td>L3S</td><td>Code hosting/issue tracking</td><td></td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://nerd.huma-num.fr</td><td>INRIA</td><td>Data extraction</td><td></td><td></td><td>X</td><td></td><td></td></tr><tr><td>https://github.com/helgeho/ArchiveSpark</td><td>L3S</td><td>Data extraction</td><td>X</td><td></td><td>X</td><td></td><td></td></tr><tr><td>http://scrapers.bibsonomy.org/</td><td>L3S</td><td>Data extraction</td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://traces1.saclay.inria.fr/traces1</td><td>INRIA</td><td>Metadata conversion</td><td></td><td>X</td><td>X</td><td>X</td><td></td></tr><tr><td>https://hal.archives-ouvertes.fr/DARIAH</td><td>INRIA</td><td>Publication repository</td><td></td><td>X</td><td></td><td>X</td><td></td></tr><tr><td>http://traces1.saclay.inria.fr/inria/</td><td>INRIA</td><td>Repository analytics</td><td>X</td><td>X</td><td></td><td>X</td><td>X</td></tr><tr><td>https://textgridrep.org/en/</td><td>UGOE-SUB</td><td>Research data repository</td><td></td><td>X</td><td></td><td>X</td><td>X</td></tr><tr><td>https://de.dariah.eu/repository</td><td>UGOE-SUB</td><td>Research data repository</td><td></td><td>X</td><td></td><td>X</td><td>X</td></tr><tr><td>https://textgrid.de/</td><td>UGOE-SUB</td><td>Virtual research environment</td><td></td><td>X</td><td></td><td>X</td><td></td></tr></tbody></table>

<footnote n="6">⁶ X = applies</footnote>
<table><caption>Figure 2: Services and software among the technology partners in DESIR WP4</caption><tr><td>https://visnow.icm.edu.pl/</td><td>ICM</td><td>Data visualisation</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://remotevis.icm.edu.pl/ (non-public)</td><td>ICM</td><td>Desktop cloud visualization</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://cermine.ceon.pl/</td><td>ICM</td><td>Data extraction</td><td>X</td><td>X</td><td>X</td><td></td></tr><tr><td>http://comac.ceon.pl</td><td>ICM</td><td>Bibliography analytics</td><td></td><td>X</td><td></td><td>X</td></tr><tr><td>https://repod.pon.edu.pl</td><td>ICM</td><td>Research data repository</td><td></td><td>X</td><td></td><td>X</td></tr><tr><td>http://repozytorium.ceon.pl</td><td>ICM</td><td>Publication repository</td><td></td><td>X</td><td></td><td></td></tr><tr><td>http://bibliotekanauki.ceon.pl</td><td>ICM</td><td>Journal platform</td><td></td><td>X</td><td></td><td></td></tr><tr><td>http://otworzksiazke.pl</td><td>ICM</td><td>Book platform</td><td></td><td>X</td><td></td><td></td></tr><tr><td colspan="3">= 19 services</td><td>4</td><td>14</td><td>4</td><td>9</td><td>5</td></tr></table>

<figure><img src="image_6.png" /></figure>

<figure><img src="image_7.png" /></figure>
The aforementioned diagram shows a quite even distribution of services and tools along the four categories suggested by DESIR's description of work. As a fifth category non applicable services and tools have been added as they complete the partners' inventory. The underlying n=services/tools falls short with 12 but one may recognise focal points in the development of services relevant for scholarly content management and visualisation of data. To relativise the picture even more, the distribution of services along the categories reflects the specific work package partners, hence the results are not surprising.

## 3 Partial catalogue of services and tools within DARIAH

### 3.1 Existing cataloguing activities within DARIAH

DESIR stands for DARIAH ERIC Sustainability Refined and is – similar to Humanities at Scale<fnref n="7" /> (HaS) – an offspring project of DARIAH and therefore closely embedded in the DARIAH-ERIC and DARIAH-EU context. Out of context of the DARIAH-ERIC at least four main missions can be deducted<fnref n="8" />, which guide the objectives of DESIR:

* Identify infrastructural needs of scholarly communities and provide help to fulfil those needs;

* Coordinate national contributions in establishing sustainable digital services for the arts and humanities;

* Contribute to the establishment of national infrastructure roadmaps;

* Participate in setting up the European agenda for infrastructures in Europe.

DESIR addresses the sustainability question for several kinds of activities, infrastructures or services originating from the DARIAH context and it is not the first project working on this question. Different from developing new resources or infrastructural components, DESIR is exploring opportunities to employ already existing resources (independent from DARIAH) as means to sustain certain infrastructure components and services. Within the context of HaS the DESIR work package 4 Technology and the actual deliverable 4.1 Gap Analysis are two activities that should be considered more thoroughly in this context:

* DARIAH (In-kind) contribution tool<fnref n="9" /> (see figure 3): the in-kind contribution tool has been an activity within the aforementioned HaS project's work package 5. Under the lead of DANS a ReactJS based interface has been developed which provides the user access to a database containing and allowing the assessment of the in-kind contributions of the national DARIAH partners to the DARIAH ERIC, basically an inventory. Not all of these in-kind contributions come in terms of infrastructure or

<footnote n="7">⁷ Project website for Humanities at Scale: http://has.dariah.eu/</footnote>

<footnote n="8">⁸ Baillot, Mertens, Romary (2016), p. 152</footnote>

<footnote n="9">⁹ A provisional development instance of the In-kind contribution tool is available here: https://dariah-beta.dans.knaw.nl/data/contrib/filter, the technical documentation may be found here: https://dans-labs.github.io/dariah/ and the user manuals on Github here: https://github.com/Dans-labs/dariah/wiki</footnote>
user oriented services but a considerable subset which is likely to be of interest within this context. There are plans to implement a DARIAH Hallmark for some of these resources. Possibly this concept and particularly the underlying criteria are also of interest in our context.

* **DARIAH Marketplace:** the launch of the Marketplace is planned for 2018. It will be "a central, easy-entry place for humanists seeking support for all kinds of digital aspects of their research. [...] It will contain a collection of software, tools, services, datasets, publication repositories and learning and training material and will establish visibility for them."<fnref n="10" /> It is planned that the abovementioned DARIAH (in kind) contribution tool feeds into the DARIAH Marketplace. Not all of the listed resources are of interest in the context. Generally DARIAH differentiates resources between services and activities, under which such diverse activities such as events, software development or consulting may be subsumed.<fnref n="11" /> Relevant for the gap analysis are in this regard mainly the services, more precisely (data) hosting services, (processing) services and support services.

<figure><img src="image_8.png" /><figcaption>Figure 3: The DARIAH In-Kind Contribution tool (as of November 2017)</figcaption></figure>

<footnote n="10">¹⁰ Frank Fischer, Jennifer Edmond (2017): Towards the DARIAH Marketplace - Position Paper. (only internally available) but also presented in a talk at the DARIAH Innovation Forum on November 2nd 2017 in Aarhus, Denmark: http://conferences.au.dk/dariah2017/preliminary-program/</footnote>

<footnote n="11">¹¹ Humanities at Scale, Lisa de Leeuw, Dirk Roorda (2017), p. 14</footnote>
Other relevant activities in this context include the DARIAH-IT Registry<fnref n="12" />, the Joint Resource Registry<fnref n="13" /> of PARTHENOS or the overhauled new website of DARIAH-EU, which also contains an overview of tools and services<fnref n="14" />, and the DARIAH-DE list of tools and services<fnref n="15" />. This document considers these sources, particularly the DARIAH-DE list of tools and services and the DARIAH in-kind contribution tool. Nevertheless it has to be clear that the aforementioned activities follow a different scope than work package 5 of DESIR, which is particularly interested in identifying gaps to be closed by the current DESIR partners.
An interesting resource beyond the scope of DARIAH (as the above described initiatives except for PARTHENOS) can be found with TERESAH. TERESAH stands for Tools E-Registry for E-Social Science, Arts and Humanities and is the result of an DASISH<fnref n="16" /> effort and currently under further development by the already mentioned Humanities at Scale project. A new metadata schema has been developed and has been implemented into an own instance of TERESAH<fnref n="17" />. It is a cross-community tools and knowledge registry aimed at researchers in the social sciences and humanities. It is of particular interest with its distributed approach as it crawls its data from different sources (e.g. community-driven websites) and aggregates them in a re-usable way, for instance in various RDF representations<fnref n="18" />. Although TERESAH presents an interesting example from a technological point of view in this context, its scope lays beyond the DARIAH resources which should be inventoried here.

## 3.2 Inventory of DARIAH activities in four areas

The following section provides an overview of the current infrastructure and service offerings of DARIAH according to the four areas: entity-based search, scholarly content management, text-analytic services and visualisation. As mentioned before, this deliverable is not tasked with the preparation of a comprehensive inventory but is said to focus on certain areas.

In the following step this inventory will be screened for gaps – or rather potentials – for contributions by the technological partners in DESIR. The table presents publicly offered services such as desktop applications, web applications, mobile applications and APIs, basically in the sense of service as the DARIAH (in kind) contribution tool understands them: (data) hosting service, (processing) service, support service and access to resources. The services may be aimed at basic infrastructure requirements, scholarly collaboration, conducting of research and user services. Where possible, the services are linked with a URL.

<footnote n="12">¹² http://it.dariah.eu/registro/en/</footnote>

<footnote n="13">¹³ http://www.parthenos-project.eu/Download/Deliverables/D5.2_Report_on design_Joint Resource Registry.pdf</footnote>

<footnote n="14">¹⁴ https://www-dev.dariah.eu/what-we-provide/tools-list/</footnote>

<footnote n="15">¹⁵ https://de.dariah.eu/list-services which will respectively be included in the DARIAH-EU Marketplace</footnote>

<footnote n="16">¹⁶ http://dasish.eu/</footnote>

<footnote n="17">¹⁷ http://teresah.dariah.eu/</footnote>

<footnote n="18">¹⁸ See here http://teresah.dariah.eu/about/rdf</footnote>
The listed resources focus on services, tools and software instead of content. Therefore publication and research data repositories or digital editions are intentionally left out. This selection is not always possible, this is why some degree databases have been incorporated in the inventory. Again: an exhaustive inventory of all available DH resources within DARIAH will be only within reach with the upcoming marketplace.

Also the reliability of the collected information has to be considered. Information on websites regarding the status of a service are often unclear. Is it still being developed, is it a productive service being used, is the service discontinued and just present for documentation purpose? To address this issue a column has been added in the table, displaying the maintenance status of the services. An x in this column indicates that from the information on the website we assume that the service is still active to some degree.

So far the following sources have been investigated for services<fnref n="19" />:

* **DARIAH-DE:** https://de.dariah.eu/list-services contains a comprehensive list of available services and tools that qualify for production use. As DARIAH-DE passed through two funding phases and is now in the midst of the third funding phase and paid considerable effort to the sustainability of the created infrastructure, the overview - nearly a service catalogue - on the DARIAH-DE website is a reliable portfolio of available and functional services. A comprehensive - although in German language - overview of the service portfolio can be found in Kálmán, Kong, Schwardmann (2016).<fnref n="20" />

* **DARIAH-EU:** the website http://dariah.eu/ gives currently only a glimpse overview of the resources that have been developed within the national branches of DARIAH. Even the relaunched website<fnref n="21" /> of DARIAH-EU will only be able to offer a complete overview once the DARIAH Marketplace will be launched. The reasoning behind the DARIAH Marketplace and the according In-Kind-Contribution Tool is described a bit more in the previous chapter.

* **DARIAH-IT:** http://it.dariah.eu/sito/strumenti/ showcases a broad collection of resources being developed in humanities-related research contexts in Italy. The relation to DARIAH is more or less loose which makes it difficult to identify services that are functional and accessible beyond a funded project period. Beyond this, it remains unclear along which criteria the resources have been selected or whether they are up to date. Therefore only a small assortment has been selected for the inventory below and still the listed resources have to be considered with caution.

<footnote n="19">¹⁹ As of September 2017.</footnote>

<footnote n="20">²⁰ Kálmán, Kong, Schwardmann (2016), p. 234ff.</footnote>

<footnote n="21">²¹ https://www-dev.dariah.eu/what-we-provide/tools-list/ as preliminary development instance.</footnote>
* DARIAH-GR: the website of Greek DARIAH branch http://www.dyas-net.gr/ contains a list of Greek humanities-related tools and services. As long as the resources seem to be available in English they have been considered for our inventory.

* DARIAH-BE: the website of DARIAH-BE http://be.dariah.eu/services-overview offers a comprehensive list of tools and services for digital scholarship in the arts and humanities in Belgium. Although it is not clear along which criteria the resources have been selected, the listed resources give the impression to be more or less functional and available.

* DARIAH-AT: http://www.digital-humanities.at/de/dha/projects the Austrian DH resources reveal a strong emphasis on digital editions or other content-focussed resources. Only a few of them are considered in the inventory below although they make the impression of being functional and accessible on a beyond-project base. Another feature of the Austrian resources is the CLARIN provenance. Services with a clear CLARIN provenance haven't been considered in the inventory.

* DARIAH-FR & Huma-Num: http://www.huma-num.fr/services-et-outils Huma-Num serves as a gathering point for humanities-related French research services. Huma-num mission is to ensure the preservation of the scientific heritage of the laboratories and to reduce recurrent costs by pooling an infrastructure by co-managing and sharing tools, instruments and data management systems. Huma-num is also part of the DARIAH organisation providing their infrastructure for european projects.

* CLARIAH-NL: https://www.clariah.nl/en/ The Common Lab Research Infrastructure for the Arts and Humanities is not a national DARIAH branch as DARIAH-DE or DARIAH-BE but can be explained with the strong CLARIN uptake in the Netherlands. CLARIAH-NL offers a distributed infrastructure for the humanities and social sciences. Different from the national DARIAH websites above, CLARIAH doesn't offer list or registry of tools and services on its website.

* For Switzerland, the ASSH has open a German webpage for DARIAH announcements: http://www.sagw.ch/sagw/laufende-projekte/dariah.html

The aforementioned list of resources is by no means complete but may be sufficient for an overview of the available services to deduct focal points or gaps.
<table><caption>Table 5: DARIAH inventory according to the four DESIR DoW categories</caption><thead><tr><td>Service<sup>22</sup></td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualization</td><td>Other category (not covered by DoW)</td><td>Main-tained or applicable<sup>23</sup></td></tr></thead><tbody><tr><td>https://de.dariah.eu/gnd-service</td><td>Authority files</td><td>X<sup>24</sup></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/aai</td><td>AAI</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://www.zotero.org/groups/113737/doing_digital_humanities - a_dariah_bibliography</td><td>Bibliography</td><td></td><td>X</td><td></td><td>X</td><td></td><td>X</td></tr><tr><td>http://dhd-blog.org/</td><td>Blog</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://hypotheses.org/</td><td>Blog</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://www.youtube.com/channel/UCScSbG7XjiXbZVgilEpoPkw</td><td>Content, YouTube</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://www.oercommons.org/groups/dariah/229/</td><td>content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/en/cloudshare</td><td>Cloud/ File sharing</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://sourceforge.net/projects/meise/</td><td>Data analysis</td><td></td><td>X</td><td></td><td>X</td><td></td><td>(X)</td></tr><tr><td>https://de.dariah.eu/topics</td><td>Data analysis</td><td>X</td><td>X</td><td>X</td><td>X</td><td></td><td>(X)</td></tr><tr><td>https://de.dariah.eu/digivoy</td><td>Data analysis</td><td></td><td></td><td>X</td><td>X</td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/mysql-datenbankhosting</td><td>Database</td><td></td><td></td><td></td><td></td><td>X</td><td>(X)</td></tr><tr><td>https://pdrprod.bbaw.de/wiki/doku.php?id=e:start</td><td>Database, Research Data Repository</td><td></td><td>X</td><td>X</td><td>X</td><td></td><td></td></tr></tbody></table>

<footnote n="22">22 Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="23">23 Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>

<footnote n="24">24 X = applies; (X) = could apply</footnote>
<table><thead><tr><td>Service<sup>25</sup></td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualisation</td><td>Other category (not covered by DoW)</td><td>Main-tained or applicable<sup>26</sup></td></tr></thead><tbody><tr><td>https://de.dariah.eu/pnd-service</td><td>Database, Research Data Repository</td><td></td><td>X</td><td>X</td><td>X</td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/jenkins</td><td>Developer tools for CI workflows</td><td></td><td></td><td></td><td></td><td>X</td><td></td></tr><tr><td>https://de.dariah.eu/etherpad</td><td>Etherpad</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://de.dariah.eu/geobrowser</td><td>Geovisualisation</td><td></td><td>X</td><td></td><td>X</td><td>X</td><td>X</td></tr><tr><td>https://de.dariah.eu/basisinfrastruktur-helpdesk</td><td>Helpdesk</td><td></td><td></td><td></td><td></td><td>X</td><td>(X)</td></tr><tr><td>https://de.dariah.eu/mailinglisten</td><td>List servers</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://colreg.de.dariah.eu/colreg/</td><td>Metadata, Research Data</td><td></td><td>X</td><td></td><td></td><td>X</td><td></td></tr><tr><td>https://de.dariah.eu/cosmotool</td><td>Data analysis</td><td>X</td><td></td><td>X</td><td>X</td><td></td><td></td></tr><tr><td>https://schereg.de.dariah.eu/schereg/registry/</td><td>Metadata conversion</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://tadirah.dariah.eu/vocab/index.php</td><td>Metadata conversion, Thesaurus management</td><td>X</td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>https://de.dariah.eu/monitoring</td><td>Monitoring</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://de.dariah.eu/conedakor</td><td>Network visualisation, Research Data Repository</td><td>X</td><td>X</td><td></td><td></td><td></td><td></td></tr></tbody></table>

<footnote n="25">25 Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="26">26 Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>
<table><thead><tr><td>Service<sup>27</sup></td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualisation</td><td>Other category (not covered by DoW)</td><td>Main-tained or applicable<sup>28</sup></td></tr></thead><tbody><tr><td>https://de.dariah.eu/datasheet-editor</td><td>Metadata conversion, Geospatial visualisation</td><td></td><td></td><td></td><td>X</td><td>X</td><td>X</td></tr><tr><td>https://de.dariah.eu/dkprowrapper</td><td>NLP tools</td><td></td><td></td><td>X</td><td></td><td></td><td>X</td></tr><tr><td>https://www.gwdg.de/de/application-services /persistent-identifier-pid</td><td>PID service</td><td></td><td></td><td></td><td></td><td>X</td><td>(X)</td></tr><tr><td>https://de.dariah.eu/persistent-identifiers</td><td>PID service</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://projects.gwdg.de/</td><td>Project management</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://redmine.acdh.oecaw.ac.at/</td><td>Project management</td><td></td><td></td><td></td><td></td><td>X</td><td>(X)</td></tr><tr><td>http://calenda.org/</td><td>Public calendar</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://de.dariah.eu/repository</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/publikator</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://books.openedition.org/</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://textgridrep.org/en/</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://www.revues.org/</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://hal.archives-ouvertes.fr/DARIAH</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://www.rechercheisidore.fr/apropos</td><td>Repository, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr></tbody></table>

<footnote n="27">27 Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="28">28 Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>
<table><thead><tr><td>Service<sup>29</sup></td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualisation</td><td>Other category (not covered by DoW)</td><td>Maintained or applicable<sup>30</sup></td></tr></thead><tbody><tr><td>https://de.dariah.eu/generische-suche</td><td>Search</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/survey-provisioning</td><td>Survey provisioning</td><td></td><td></td><td></td><td></td><td>X</td><td>(X)</td></tr><tr><td>https://registries.clarin-dariah.eu/courses/courses/</td><td>Teaching, content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>https://de.dariah.eu/getty-service</td><td>Thesaurus management</td><td>X</td><td></td><td></td><td></td><td></td><td>(X)</td></tr><tr><td>https://de.dariah.eu/hosting-umgebung</td><td>Virtual machines/ web hosting</td><td></td><td></td><td></td><td></td><td>X</td><td>(X)</td></tr><tr><td>https://de.dariah.eu/virtuelle-maschinen</td><td>Virtual machines/ web hosting</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>https://textgrid.de/en/</td><td>VRE<sup>31</sup></td><td></td><td>X</td><td>X</td><td></td><td></td><td>X</td></tr><tr><td>http://www.cendari.eu/</td><td>VRE</td><td></td><td>X</td><td>X</td><td></td><td></td><td>X</td></tr><tr><td>https://wiki.de.dariah.eu/display/DARIAH/Home</td><td>Wiki/ Collaborative platforms</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>http://www.mirabileweb.it/</td><td>Content, knowledge management system</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://www.lexicon.unisi.it/public/</td><td>Content, Data analysis</td><td></td><td></td><td>X</td><td></td><td></td><td>(X)</td></tr><tr><td>https://sourceforge.net/projects/evt-project/</td><td>Visualisation</td><td></td><td></td><td></td><td>X</td><td></td><td>X</td></tr><tr><td>https://www.idem.garr.it/</td><td>AAI</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr></tbody></table>

<footnote n="29">29 Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="30">30 Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>

<footnote n="31">31 Virtual Research Environment</footnote>
<table><thead><tr><td>Service<sup>32</sup></td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualisation</td><td>Other category (not covered by DoW)</td><td>Main-tained or applicable<sup>33</sup></td></tr></thead><tbody><tr><td>http://elearning.enea.it/?lang=en</td><td>Teaching</td><td></td><td>X</td><td></td><td></td><td></td><td></td></tr><tr><td>http://www.afs.enea.it/project/tigris/ASTEC.php</td><td>VRE</td><td></td><td></td><td></td><td>X</td><td></td><td></td></tr><tr><td>http://www.evalita.it/2011/tasks/dependency_parsing</td><td>NLP tool</td><td></td><td></td><td>X</td><td></td><td></td><td>X</td></tr><tr><td>http://www.daphnet.org/index_de.html</td><td>VRE</td><td></td><td>X</td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>http://www.languagelibrary.eu/owl/simple/</td><td>Linked data, data analysis</td><td>X</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>http://trame.fefonlus.it/trame/index.html</td><td>VRE</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://vcg.isti.cnr.it/3dhop/</td><td>Visualisation</td><td></td><td></td><td></td><td>X</td><td></td><td>X</td></tr><tr><td>http://vcg.isti.cnr.it/vcglib/</td><td>Visualisation</td><td></td><td></td><td></td><td>X</td><td></td><td>X</td></tr><tr><td>http://www.meshlab.net/</td><td>Visualisation</td><td></td><td></td><td></td><td>X</td><td></td><td>(X)</td></tr><tr><td>http://www.cophilab.eu:8080/CoPhiLabPortal/web/guest/home</td><td>Data analysis</td><td>X</td><td></td><td></td><td></td><td>X</td><td></td></tr><tr><td>http://claviusontheweb.it/</td><td>VRE</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://www.italianlp.it/demo/linguistic-annotation-tool/</td><td>NLP</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://www.corpusitaliano.it/preview/en/index.html</td><td>Content, repository</td><td></td><td>X</td><td></td><td></td><td></td><td></td></tr><tr><td>http://www.italianlp.it/demo/read-it/</td><td>NLP</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr></tbody></table>

<footnote n="32">32 Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="33">33 Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>
<table><thead><tr><td>Service<fnref n="34" /></td><td>Tags</td><td>Entity-based search</td><td>Scholarly content management</td><td>Text-analytic services</td><td>Visualisation</td><td>Other category (not covered by DoW)</td><td>Maintained or applicable<fnref n="35" /></td></tr></thead><tbody><tr><td>http://www.italianlp.it/demo/t2k-text-to-kno wledge/</td><td>NLP</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://registries.dyas-net.gr/en</td><td>Content</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://be.dariah.eu/project/database-byzantin e-book-epigrams-dbbe</td><td>Content, database</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://be.dariah.eu/project/database-souther n-dutch-dialects-dsdd</td><td>Content, database</td><td></td><td>X</td><td></td><td></td><td></td><td>(X)</td></tr><tr><td>https://www.immibel.arch.be/virtualresearch environment</td><td>VRE</td><td></td><td></td><td></td><td></td><td>X</td><td>X</td></tr><tr><td>http://www.mamluk.ugent.be/Prosopograph y</td><td>Content, database</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://be.dariah.eu/project/ramses-online</td><td>Content, database, corpus</td><td></td><td>X</td><td></td><td></td><td></td><td>X</td></tr><tr><td>http://www.tic.ugent.be/</td><td>VRE</td><td></td><td></td><td>X</td><td></td><td>X</td><td>X</td></tr><tr><td>http://be.dariah.eu/project/dariah-vl-virtual-re search-environment-service-infrastructure-vr e-si</td><td>VRE</td><td></td><td></td><td></td><td></td><td>X</td><td></td></tr><tr><td>https://transkribus.eu/Transkribus/</td><td>Data analysis</td><td></td><td></td><td>X</td><td></td><td>X</td><td>X</td></tr><tr><td>http://www.digital-humanities.at/de/dha/s-pr oject/read-recognition-and-enrichment-archiv al-documents</td><td>VRE</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://www.digital-humanities.at/de/dha/s-pr oject/medcon</td><td>VRE, network analysis</td><td></td><td></td><td>X</td><td></td><td></td><td></td></tr><tr><td>http://www.digital-humanities.at/de/dha/s-pr oject/mapping-historical-networks-apis</td><td>VRE, content</td><td></td><td></td><td>X</td><td>X</td><td></td><td></td></tr><tr><td>http://www.digital-humanities.at/de/dha/s-pr oject/gams</td><td>Content, VRE</td><td></td><td>X</td><td></td><td></td><td></td><td></td></tr></tbody></table>

<footnote n="34">³⁴ Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="35">³⁵ Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>
<table><thead><tr><th>Service<sup>36</sup></th><th>Tags</th><th>Entity-based search</th><th>Scholarly content management</th><th>Text-analytic services</th><th>Visualisation</th><th>Other category (not covered by DoW)</th><th>Maintained or applicable<sup>37</sup></th></tr></thead><tbody><tr><td>http://www.digital-humanities.at/de/dha/s-pr object/dixit</td><td>Content, Teaching</td><td></td><td>X</td><td></td><td></td><td></td><td></td></tr><tr><td>http://www.digital-humanities.at/de/dha/s-pr object/puzzle-4d</td><td>Content, Visualisation</td><td></td><td>X</td><td></td><td>X</td><td></td><td></td></tr><tr><td>SUMS: 82</td><td>110</td><td>8</td><td>37</td><td>21</td><td>16</td><td>27</td><td>46</td></tr></tbody></table>

It is important to keep in mind, that the inventory is fragmentary. The reasons for have been explained above and are related to the situation in DARIAH that in 2017 - the time of writing - the marketplace is not yet available. There is no comprehensive overview on the DARIAH landscape. For this reason, the fragmentary inventory may be better understood as indication for specific competencies or centers of gravity. The large presence of scholarly content-related services may indicate such a center of gravity. The analysis of the figures follows below.

The table below is an aggregated facet of the inventory above. It groups all 110 services into three categories: infrastructure, research, and communication. The finding is – not surprisingly – that most DARIAH activities can be related more or less directly to research services.

<table><caption>Table 6: DARIAH inventory according to three aggregated categories</caption><thead><tr><th>Service category</th><th>Quantity</th><th>Infrastructure</th><th>Research</th><th>Communication</th></tr></thead><tbody><tr><td>AAI</td><td>2</td><td>2</td><td></td><td></td></tr><tr><td>Authority files</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>Bibliography</td><td>1</td><td></td><td>1</td><td></td></tr><tr><td>Cloud/ File sharing</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>Content (tutorial, teaching, blog)</td><td>27</td><td></td><td>27</td><td></td></tr><tr><td>Data analysis</td><td>8</td><td></td><td>8</td><td></td></tr></tbody></table>

<footnote n="36">³⁶ Service is defined according to D5.2 DARIAH (in kind) contribution tool as (Data) hosting service, (processing) service, support service and access to resources.</footnote>

<footnote n="37">³⁷ Maintained or applicable is to understood as qualitative criteria in this regard. A service was recognized as maintained or applicable only if the hosting website appeared to be up to date.</footnote>
<table><thead><tr><td>Service category</td><td>Quantity</td><td>Infrastructure</td><td>Research</td><td>Communication</td></tr></thead><tbody><tr><td>Database</td><td>7</td><td>7</td><td></td><td></td></tr><tr><td>Developer tool</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>Etherpad</td><td>1</td><td></td><td></td><td>1</td></tr><tr><td>Geospatial visualisation</td><td>2</td><td></td><td>2</td><td></td></tr><tr><td>Helpdesk</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>List server</td><td>1</td><td></td><td></td><td>1</td></tr><tr><td>Metadata conversion</td><td>4</td><td></td><td>4</td><td></td></tr><tr><td>Monitoring</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>NLP tool</td><td>5</td><td></td><td>5</td><td></td></tr><tr><td>PID service</td><td>2</td><td>2</td><td></td><td></td></tr><tr><td>Project management</td><td>2</td><td></td><td></td><td>2</td></tr><tr><td>Public calendar</td><td>1</td><td></td><td></td><td>1</td></tr><tr><td>Research data or publication repository</td><td>12</td><td></td><td>12</td><td></td></tr><tr><td>Search</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>Survey provisioning</td><td>1</td><td>1</td><td></td><td></td></tr><tr><td>Thesaurus management</td><td>2</td><td></td><td>2</td><td></td></tr><tr><td>Virtual machines/ web hosting</td><td>2</td><td>2</td><td></td><td></td></tr><tr><td>Virtual research environment</td><td>13</td><td></td><td>13</td><td></td></tr><tr><td>Visualisation</td><td>6</td><td></td><td>6</td><td></td></tr><tr><td>Wiki</td><td>1</td><td></td><td></td><td>1</td></tr><tr><td>Corpus</td><td>1</td><td></td><td>1</td><td></td></tr><tr><td>Knowledge Management System</td><td>1</td><td></td><td>1</td><td></td></tr></tbody></table>
<table><caption>Table 7: DARIAH inventory according to four DARIAH Virtual Competence Centers<fnref n="38" /></caption><thead><tr><th>Service category</th><th>Quantity</th><th>Infrastructure</th><th>Research</th><th>Communication</th></tr></thead><tbody><tr><td>Linked Data</td><td>1</td><td></td><td>1</td><td></td></tr><tr><td>Network analysis</td><td>1</td><td></td><td>1</td><td></td></tr><tr><td>SUM</td><td>110</td><td>20</td><td>84</td><td>6</td></tr></tbody></table>

<table><thead><tr><th>Service category</th><th>Quantity</th><th>VCC1: e-Infrastructure</th><th>VCC2: Research and Education Liaison</th><th>VCC3: Scholarly Content Management</th><th>VCC4: Advocacy, Impact, Outreach</th></tr></thead><tbody><tr><td>AAI</td><td>2</td><td>2</td><td></td><td></td><td></td></tr><tr><td>Authority files</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Bibliography</td><td>1</td><td></td><td></td><td>1</td><td></td></tr><tr><td>Cloud/ File sharing</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Content (tutorial, teaching, blog)</td><td>27</td><td></td><td></td><td>27</td><td></td></tr><tr><td>Data analysis</td><td>8</td><td>8</td><td></td><td></td><td></td></tr><tr><td>Database</td><td>7</td><td>7</td><td></td><td></td><td></td></tr><tr><td>Developer tool</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Etherpad</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Geospatial visualisation</td><td>2</td><td>2</td><td></td><td></td><td></td></tr><tr><td>Helpdesk</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>List server</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Metadata conversion</td><td>4</td><td>4</td><td></td><td></td><td></td></tr><tr><td>Monitoring</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>NLP tool</td><td>5</td><td>5</td><td></td><td></td><td></td></tr><tr><td>PID service</td><td>2</td><td>2</td><td></td><td></td><td></td></tr><tr><td>Project management</td><td>2</td><td>2</td><td></td><td></td><td></td></tr><tr><td>Public calendar</td><td>1</td><td></td><td></td><td></td><td>1</td></tr></tbody></table>

<footnote n="38">³⁸ https://www.dariah.eu/activities/competence-centers-list/</footnote>
<table><thead><tr><td>Service category</td><td>Quantity</td><td>VCC1: e-Infrastructure</td><td>VCC2: Research and Education Liaison</td><td>VCC3: Scholarly Content Management</td><td>VCC4: Advocacy, Impact, Outreach</td></tr></thead><tbody><tr><td>Research data or publication repository<sup>39</sup></td><td>12</td><td></td><td></td><td>12</td><td>12</td></tr><tr><td>Search</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Survey provisioning</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Thesaurus management</td><td>2</td><td></td><td></td><td>2</td><td></td></tr><tr><td>Virtual machines/ web hosting</td><td>2</td><td>2</td><td></td><td></td><td></td></tr><tr><td>Virtual research environment</td><td>13</td><td>13</td><td></td><td></td><td></td></tr><tr><td>Visualisation</td><td>6</td><td>6</td><td></td><td></td><td></td></tr><tr><td>Wiki</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Corpus</td><td>1</td><td></td><td></td><td>1</td><td></td></tr><tr><td>Knowledge Management System</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Linked Data</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>Network analysis</td><td>1</td><td>1</td><td></td><td></td><td></td></tr><tr><td>SUM</td><td>110</td><td>66</td><td>0</td><td>43</td><td>13</td></tr></tbody></table>

# 4 Interpretation

## 4.1 Methodology

Before an interpretation of the above standing findings is possible, the concept of the gap analysis has to be defined according to the present context.

First of all we don't conduct a gap analysis in the conventional sense, known from the economic sphere. In this sense a gap analysis is aimed at identifying sales or revenue gaps in a certain market or for certain products or services. The gap analysis takes into account the resources of the economic undertaking, usually a company, and relates them to the market segment in terms of customers, purchasing power or other factors.

A gap analysis in our context can be understood in the verbatim sense. The DARIAH landscape is mapped with focus on services, tools and resources and in the next step browsed for gaps. Correctly a gap can only be identified with consideration of the user requirements as they form the pattern which has to be filled or addressed with services and

<footnote n="39">39 Repositories are listed in two VCCs.</footnote>
resources. Clearly this hasn't been done in this document. It would have been impossible to
gather the user requirements of the current DARIAH user base. This could be subject to a
larger undertaking, which is not possible and not within the scope of this work package.
So one has to consider, that the aforementioned inventory of DARIAH's services and
resources is fragmentary and represents a snapshot of the situation in autumn 2017. It has
been compiled with regard to the requirements of the DESIR project, therefore focussing on
four categories - entity-based search, text-analytic services, scholarly content management
and visualisation. The inventory indicates centres of gravity of DARIAH in terms of services
and resources. Areas with a lesser accumulation of services – for instance entity-based
search – can be identified but one cannot inevitably deduct a gap from this. The gaps will be
later defined in another, more indirect manner: with look at the DARIAH inventory the
technology partners in WP4 draft ideas for possible innovative services and resources. As
long as the idea for a service meets a potential demand in the DARIAH community and is
coincidentally innovative and functional it addresses a gap in the sense of this work package.
The analysis of the current DARIAH service portfolio leads to the following conclusions,
which may be later used as basis for discussion of the conceptual models.

4.2 Interpretation of findings

DARIAH's services and resources concentrate on research related services. To a lesser
degree services may be associated to infrastructure and communication (compare figure 4
below). These three categories come as an alternative facet to the four categories from
DESIR's description of work. Although the gain of knowledge may be minor the result
underpins the orientation of DARIAH as research infrastructure.

Interestingly the communication related share of services is the smallest one, which may be
based on the already sufficient availability of (free or commercial) communication tools. It is
clear that research infrastructure initiatives can't compete with the established and
widely-used tools as Skype, forums, messengers, e-mail.

A different facet becomes possible when arranging the services along the DARIAH VCCs. The DARIAH Virtual Competency Centers<fnref n="40" /> function as an umbrella structure to coordinate and promote DARIAH activities along four headlines: VCC1 -e-Infrastructure; VCC2-Research and Education Liaison; VCC3 -Scholarly Content Management Advocacy and VCC4 -Impact and Outreach. These categories differ a little bit from the infrastructural or technological view of the DESIR DoW but nevertheless the focus of DARIAH as research infrastructure becomes clear with 43 services relevant for scholarly content management (VCC3) and 66 services relevant for e-Infrastructure (VCC1).

<footnote n="40">⁴⁰ https://www.dariah.eu/activities/competence-centers-list/</footnote>
<figure><img src="image_9.png" /><figcaption>Figure 5: DARIAH inventory according to four DARIAH Virtual Competence Centers</figcaption></figure>

<figure><img src="image_10.png" /></figure>
A different picture emerges with look at the four DESIR DoW categories: most services are related to scholarly content management (37) and text-analytic services (21) and to a lesser degree to visualisation (16) and entity-based search (8). This may indicate that the DARIAH portfolio has the broadest portfolio in the area of scholarly content management and to a lesser degree in the field of entity-based search. It is likely that the conceptual models that will be developed in the course of the work package may reflect this distribution in one way or another. One can deduct from this that the number of only 8 entity-based search-services represent a gap. Again: a real gap could only be identified with regard to the user requirements. As long as the user requirements are met by the available services, this may be sufficient and there would be no need for developing further services. This can't be claimed with the available material. Another claim, which is more sustainable, could be to assume more possible connecting points with the available 37 services in scholarly content management or 21 services in text-analytic services. Therefore one could justify conceptual models in these areas as more connections seem possible.

<figure><img src="image_11.png" /><figcaption>Figure 6: Service<sup>41</sup> categories according to Description of Work</figcaption></figure>

It may also be worthwhile to note that some services (27) could not be associated with any of the categories. This possibly bears the potential for conceptual models beyond the four DESIR categories, something which is not excluded by the project's description of work.

<footnote n="41">41 Please note that the total of 82 services partly apply to more than one category, therefore a total of 110 is counted.</footnote>
This grouping of services disguises the broad range of service forms (30) - illustrated in figure 7 - that have been found. DARIAH as research infrastructure offers a wide array of services, which makes it difficult to identify large gaps - as it will be explained later. Figure 7 clearly indicates a focus on content related services (27) such as blogs, repositories, tutorials or teaching material, but one has to consider that only a subset of them may relate to scholarly content as required in the description of work. The second largest group (13) is constituted by virtual research environments and research data repositories, whereby the term virtual research environment is quite broad. Aside from data analysis (8), visualisation tools (6), databases (7), NLP tools (5) or Metadata conversion (4) the other tag categories are represented a lot less.

<figure><img src="image_12.png" /><figcaption>Figure 7: Frequency of services in DARIAH</figcaption></figure>

# 5 Conclusions

What implications for the work package and particularly the conceptual models can be drawn from the gap analysis?

As a reminder: the gap analysis is tasked with identifying gaps in the current DARIAH service landscape and shall deduct from the findings ideas for conceptual models that may
contribute to the DARIAH service portfolio and address specific demands from the user base. We have to admit that within the current situation of DARIAH - no central registry available until the DARIAH Marketplace will be launched in 2018 and a quite motley landscape of national DARIAH-related websites - and the resources at hand in this WP the results have to have a fragmentary character.

Also the broad range of services among the DARIAH partners - this is a finding of the gap analysis - makes it very difficult to identify major gaps, at least with the possible methodology for this report. A gap analysis should map the available services on the complete user requirements, something which is not possible within this DESIR work package.

But the inventory and its analysis allow to identify centres of gravity in DARIAH in relation to the other service categories. We have found that a bulk of the DARIAH services focus on scholarly content management and text-analytic services. But this may not be a surprising finding for a humanities-scoped research infrastructure. In both of these categories the services concentrate on content-related services like repositories, tutorials, blogs or other forms of content and on virtual research environments and data analysis tools.

The inventory also indicates areas where DARIAH is only represented with lesser services and resources, a finding that could be understood as a gap but doesn't have to be. It could also be interpreted the other way round: areas with considerably more services and resources offer more potential connection points for new ideas. This is true for entity-based search- and visualisation-related services. And it may also be true, that an area with only a few services available is already covered in a quite satisfying way for the users, so that there is no additional demand. But this can't be supported by our facts, actually.

A finding true for all services is that the development of services is to a large part research oriented and not intended to be offered on terms of a sustainable provision and as a service for the community. This is reflected by the column in table 5, which indicates that 46 out of 82 seem to be maintained or currently available. But this finding is on relatively unsure footing and would deserve a further analysis. The evaluation of services according to their maintenance and availability status is on the feature list for the DARIAH Marketplace as this is an important function for the users.

With look at the following steps in work package 4 Technology, the gap analysis suggests that for each category a few ideas should be drafted, especially paying attention to scholarly content-management and text-analytic services. The gap analysis indicates no real gap in an infrastructural sense, which is a good finding, but may not be helpful in pointing a direction for the conceptual models. DESIR takes into account the current DARIAH service landscape and intends to improve the available approaches. For this end, it will be important to relate the partners' competencies to DARIAH, which is already being underway with involving the
technology partners from the very beginning in this work package. This involvement is reflected in this document with chapter 2, describing the technology partners' resources and competencies.
# 6 Register of tables and figures

## Tables

<table><tr><td>Table 1: Technology partners in DESIR WP4</td><td>8</td></tr><tr><td>Table 2: Applied technologies among the DESIR technology partners in WP4</td><td>10</td></tr><tr><td>Table 3: Service roles among technology partners in DESIR WP4 (self assessment)</td><td>11</td></tr><tr><td>Table 4: Development and service competencies among the technology partners in DESIR WP4</td><td>12</td></tr><tr><td>Table 5: DARIAH inventory according to the four DESIR DoW categories</td><td>19</td></tr><tr><td>Table 6: DARIAH inventory according to three aggregated categories</td><td>25</td></tr><tr><td>Table 7: DARIAH inventory according to four DARIAH Virtual Competence Centers</td><td>27</td></tr></table>

## Figures

<table><tr><td>Figure 1: Service roles of technology partners in DESIR</td><td>11</td></tr><tr><td>Figure 2: Services and software among the technology partners in DESIR WP4</td><td>13</td></tr><tr><td>Figure 3: The DARIAH In-Kind Contribution tool (as of November 2017)</td><td>15</td></tr><tr><td>Figure 4: Services according to the categories research, infrastructure and communication</td><td>30</td></tr><tr><td>Figure 5: DARIAH inventory according to four DARIAH Virtual Competence Centers</td><td>30</td></tr><tr><td>Figure 6: Service categories according to Description of Work</td><td>31</td></tr><tr><td>Figure 7: Frequency of services in DARIAH</td><td>32</td></tr></table>
# 7 Sources

Anne Baillot, Mike Mertens and Laurent Romary (2016): Data Fluidity in DARIAH - Pushing the Agenda Forward. In: DARIAH-DE - Digitalität in den Geistes- und Kulturwissenschaften am Beispiel der digitalen Forschungsinfrastruktur DARIAH-DE. Bibliothek Forschung und Praxis (2016), 40(2): pp. 151-164. DOI [http://dx.doi.org/10.1515/bfp-2016-0039](http://dx.doi.org/10.1515/bfp-2016-0039)

HUMANITIES AT SCALE, Dirk Roorda (2017): DARIAH Contribution Tool. Development instance provisionally available under: [https://dariah-beta.dans.knaw.nl/data/contrib/filter](https://dariah-beta.dans.knaw.nl/data/contrib/filter), technical documentation under: [https://dans-labs.github.io/dariah/](https://dans-labs.github.io/dariah/) and user documentation under: [https://github.com/Dans-labs/dariah/wiki/Help](https://github.com/Dans-labs/dariah/wiki/Help) (Project Deliverable)

HUMANITIES AT SCALE, Lisa de Leeuw, Dirk Roorda (2017): D5.2 - DARIAH Space for inkind Contributions. (Confidential only for members of the consortium). (Project Deliverable)

Frank Fischer, Jennifer Edmond (2017): Towards the DARIAH Marketplace - Position Paper. [http://conferences.au.dk/dariah2017/program/](http://conferences.au.dk/dariah2017/program/) (not a published version available at time of writing)

PARTHENOS, Nicola Aloia, Leonardo Candela, Franca Debole, Luca Frosini Matteo Lorenzini Pasquale Pagano (2017): D5.2 - Design of the Joint Resource Registry. URL: [http://www.parthenos-project.eu/Download/Deliverables/D5.2_Report_on design_Joint Registry.pdf](http://www.parthenos-project.eu/Download/Deliverables/D5.2_Report_on design_Joint Registry.pdf) (Project Deliverable)

Tibor Kálmán, Xi Kong and Ulrich Schwardmann (2016): Die digitale Forschungsinfrastruktur DARIAH-DE: Angebots palette für die Geistes- und Kulturwissenschaften. In: DARIAH-DE - Digitalität in den Geistes- und Kulturwissenschaften am Beispiel der digitalen Forschungsinfrastruktur DARIAH-DE. Bibliothek Forschung und Praxis (2016), 40(2): pp. 234-243. DOI [https://doi.org/10.1515/bfp-2016-0041](https://doi.org/10.1515/bfp-2016-0041)