Publications

Abstract

The Core Trustworthy Data Repository Requirements were developed by the DSA–WDS Partnership Working Group on Repository Audit and Certification, a Working Group (WG) of the Research Data Alliance . The goal of the effort was to create a set of harmonized common requirements for certification of repositories at the core level, drawing from criteria already put in place by the Data Seal of Approval (DSA: www.datasealofapproval.org) and the ICSU World Data System (ICSU-WDS: https://www.icsu-wds.org/services/certification). An additional goal of the project was to develop common procedures to be implemented by both DSA and ICSU-WDS. Ultimately, the DSA and ICSU-WDS plan to collaborate on a global framework for repository certification that moves from the core to the extended (nestor-Seal DIN 31644), to the formal (ISO 16363) level.

Abstract

This paper describes the development of a CLARIN-compatible repository solution that fulfils
both the long-term preservation requirements as well as the current day discoverability and usability
needs of an online data repository of language resources. The widely used Fedora Commons
open source repository framework, combined with the Islandora discovery layer, forms
the basis of the solution. On top of this existing solution, additional modules and tools are developed
to make it suitable for the types of data and metadata that are used by the participating
partners.

Abstract

Language resources are valuable assets, both for institutions and researchers. To safeguard these resources requirements for repository systems and data management have been specified by various branch organizations, e.g., CLARIN and the Data Seal of Approval. This paper describes these and some additional ones posed by the authors’ home institutions. And it shows how they are met by FLAT, to provide a new home for language resources. The basis of FLAT is formed by the Fedora Commons repository system. This repository system can meet many of the requirements out-of-the box, but still additional configuration and some development work is needed to meet the remaining ones, e.g., to add support for Handles and Component Metadata. This paper describes design decisions taken in the construction of FLAT’s system architecture via a mix-and-match strategy, with a preference for the reuse of existing solutions. FLAT is developed and used by the a Institute and The Language Archive, but is also freely available for anyone in need of a CLARIN-compliant repository for their language resources.

Abstract

Introduction Increasingly often research in the humanities is based on data. This change in attitude and research practice is driven to a large extent by the availability of small and cheap yet high-quality recording equipment (video cameras, audio recorders) as well as advances in information technology (faster networks, larger data storage, larger computation power, suitable software). In some institutes such as the Max Planck Institute for Psycholinguistics, already in the 90s a clear trend towards an all-digital domain could be identified, making use of state-of-the-art technology for research purposes. This change of habits was one of the reasons for the Volkswagen Foundation to establish the DoBeS program in 2000 with a clear focus on language documentation based on recordings as primary material.

Abstract

This chapter describes the challenges that modern digital language archives are faced with. One essential aspect of such an archive is to have a rich metadata catalog such that the archived resources can be easily discovered. The challenge of the archive is to obtain these rich metadata descriptions from the depositors without creating too much overhead for them. The rapid changes in storage technology, file formats and encoding standards make it difficult to build a long-lasting repository, therefore archives need to be set up in such a way that a straightforward and automated migration process to newer technology is possible whenever certain technology becomes obsolete. Other problems arise from the fact that there are many different groups of users of the archive, each of them with their own specific expectations and demands. Often conflicts exist between the requirements for different purposes of the archive, e.g. between long-term preservation of the data versus direct access to the resources via the web. The task of the archive is to come up with a technical solution that works well for most usage scenarios.