• Digital Humanities and Cultural Heritage
• Publicationsclose
• Other research productsclose
• Other ORP type close
• NARCIS close
• CLARIN close

The aim of this report is to present to its stakeholders (researchers, policy makers, cultural heritage institutions, research infrastructures, archives) a series of recommendations and guidelines about which policies to apply during and after their research or infrastructure work. “During their research work”, because policies on data and repositories guide the data creator to produce high quality data; “after their research work”, because policies on access and reuse help make the data more accessible and reusable. The research communities are: Archaeology, History, Language related studies and social sciences.

The CLARIN Concept Registry (clarin.eu/conceptregistry) is the place in the CLARIN Infrastructure where common and shared semantics of, but not limited to, linguistic concepts are defined. This is important to achieve semantic interoperability, and to overcome to a degree the diversity in data structures, either in metadata or linguistic resources, encountered within the infrastructure. Whereas in the past, CLARIN has been using the ISOcat registry for these purposes, nowadays this new registry is being used, as ISOcat turned out to have some serious drawbacks as far as its use in the CLARIN community is concerned. The main difference between the two semantic registries is that the CCR is a concept registry whereas ISOcat is a data category registry. In this paper we describe why the decision to switch to a concept registry has been made. We also describe the most important other characteristics of the new (Open)SKOS-based registry, as well as the management procedures used to prevent a recurrent proliferation of entries, as was the case with ISOcat.

The CLARIN research infrastructure aims to place language resources and services within easy reach of the humanities researchers. One of the measures to make access easy is to allow these researchers to access them using their home institutions credentials. However, the technology used for this makes it hard for services to make delegated call, i.e., a call on behalf of the researcher, to other services. In this paper several use cases, e.g., interaction with a researcher’s private workspace or protected resources, show how user delegation would enrich the capabilities of the infrastructure. To enable these use cases various technical solutions have been investigated and some of these have been used in pilot implementations of the use cases. This paper reports on the use cases, the research and the implementation experiences.

This article reports about the on-going work on a new version of the metadata framework Component Metadata Infrastructure (CMDI), central to the CLARIN infrastructure. Version 1.2 introduces a number of important changes based on the experience gathered in the last five years of intensive use of CMDI by the digital humanities community, addressing problems encountered, but also introducing new functionality. Next to the consolidation of the structure of the model and schema sanity, new means for lifecycle management have been introduced aimed at combatting the observed proliferation of components, new mechanism for use of external vocabularies will contribute to more consistent use of controlled values and cues for tools will allow improved presentation of the metadata records to the human users. The feature set has been frozen and approved, and the infrastructure is now entering a transition phase, in which all the tools and data need to be migrated to the new version.

This report was produced in the context of the project Data Service Infrastructure for the Social Sciences and Humanities (DASISH) work package 4.3 Convergence of Data Services. The goal has been to allow the selection and promotion of high-quality deposit services for researchers in the Social Sciences and Humanities (SSH) and to make suggestions for service improvements.

The aim of this task was to analyse and compare the different metadata strategies of CLARIN, DARIAH and CESSDA, and to identify possibilities of cross-fertilization to take profit from each other solutions where possible. To have a better understanding in which stages of the research lifecycle metadata comes to the fore, we looked at several research data lifecycles and business process models. However the current research data lifecycle models have the ‘static’ data object as basis, whereas metadata design , redesign, creation and management can continue to be ‘live’ issues within the research lifecycle. We therefore developed a metadata lifecycle based closely on familiar lifecycle models but extended to support the more dynamic metadata issues. To describe the metadata management of the different infrastructures we took a double approach. We looked on a more general level and outlined the policies and strategies regarding metadata of the three infrastructures. We evaluated these strategies on metadata qua lity issues with the Bruce and Hillmann criteria. On the other hand we looked with more detail how the work on metadata management is done by the individual data repositories. The infrastructures of CESSDA, CLARIN and DARIAH differ in visions, strategies and initiatives regarding metadata issues; similarly there is a difference in metadata management among the various repositories. Despite these differences, cross fertilisation by coordination on common lists of metadata elements, sharing of knowledge, and linking resources would leverage the overall metadata quality. Evaluation of the prototype of the joint CLARIN, DARIAH and CESSDA metadata portal endorses the opinion that more coordination is needed. Metadata quality must be discussed in relation to the activities for which they are used. We suggest that the infrastructures DARIAH and CLARIN prioritise future collaboration about standardisation efforts, which have already been in itialised in dialogue between the CLARIN Standards Committee and the DARIAH representatives. Similar initiatives could be established with CESSDA.