Skip to content
Snippets Groups Projects
Select Git revision
  • f1a3f7c616731a08797d7f18189b22513ffd879e
  • master default protected
  • replication_test
  • dev protected
  • release-1.10 protected
  • release-1.9 protected
  • 551-init-broker-service-permissions
  • 549-test-oai-pmh
  • 545-saving-multiple-times-breaks-pid-metadata
  • 499-standalone-compute-service-2
  • 539-load-tests
  • hotfix/helm-chart
  • luca_ba_new_interface
  • 534-bug-when-adding-access-to-user-that-is-not-registered-at-dashboard-service
  • release-1.8 protected
  • 533-integrate-semantic-recommendation
  • feature/openshift
  • 518-spark-doesn-t-map-the-headers-correct
  • 485-fixity-checks
  • 530-various-schema-problems-with-subsets
  • release-1.7 protected
  • v1.10.2 protected
  • v1.10.1 protected
  • v1.10.0-rc13 protected
  • v1.10.0-rc12 protected
  • v1.10.0-rc11 protected
  • v1.10.0-rc10 protected
  • v1.10.0-rc9 protected
  • v1.10.0-rc8 protected
  • v1.10.0-rc7 protected
  • v1.10.0-rc6 protected
  • v1.10.0-rc5 protected
  • v1.10.0-rc4 protected
  • v1.10.0-rc3 protected
  • v1.10.0-rc2 protected
  • v1.10.0rc1 protected
  • v1.10.0rc0 protected
  • v1.10.0 protected
  • v1.9.3 protected
  • v1.9.2 protected
  • v1.9.2-rc0 protected
41 results

.docs

  • Clone with SSH
  • Clone with HTTPS
  • Martin Weise's avatar
    Martin Weise authored
    82bb3d59
    History
    author: Martin Weise
    hide:
    - navigation
    social:
      cards_layout_options:
        title: Documentation that simply works

    Problem Statement

    Digital repositories see themselves more frequently encountered with the problem of making databases accessible in their collection. Challenges revolve around organizing, searching and retrieving content stored within databases and constitute a major technical burden as their internal representation greatly differs from static documents most digital repositories are designed for.

    Application Areas

    We present a database repository system that allows researchers to ingest data into a central, versioned repository through common interfaces, provides efficient access to arbitrary subsets of data even when the underlying data store is evolving, allows reproducing of query results and supports findable-, accessible-, interoperable- and reusable data.

    Features

    Built-in search

    DBRepo makes your dataset searchable without extra effort: most metadata is generated automatically for data in your databases. The fast and powerful OpenSearch database allows a fast retrieval of any information. Adding semantic mapping through a suggestion-feature, allows machines to properly understand the context of your data. Learn more.

    Citable datasets

    Adopting the recommendations of the RDA-WGDC, arbitrary subsets can be precisely, persistently identified using system-versioned tables of MariaDB and the DataCite schema for minting DOIs. External systems i.e. metadata harvesters (OpenAIRE, Google Datasets) can access these datasets through OAI-PMH, JSON-LD and FAIR Signposting protocols. Learn more.

    Powerful API for Data Scientists

    With our strongly typed Python Library, Data Scientists can import, export and work with data from Jupyter Notebook or Python script, optionally using Pandas DataFrames. For example: the AMQP API Client can collect continuous data from edge devices like sensors and store them asynchronous in DBRepo. Learn more.

    Cloud Native

    Our lightweight Helm chart allows for installations on any cloud provider or private-cloud setting that has an underlying PV storage provider. DBRepo can be installed from the Artifacthub repository. Databases are managed as MariaDB Galera Cluster with high degree of availability ensuring your data is always accessible. Learn more.

    More Information