Living document with an overview of metadata repositories and their features.
If you are looking for a repository which provides support for a specific schema only you might have also a look at the Metadata Standards Catalogs:
There you might find a repository tailored for your specific needs.
AIMS – Applying Interoperable Metadata Standards
Introduction
A platform for creating and sharing metadata schemas for better research data management in engineering. Implementing a modular metadata concept with a focus keeping interoperability while allowing highly specific description of metadata. In addition to a repository for subject-specific application profiles for subsequent use, it also provides a generator for their creation and improvement based on controlled vocabularies. These are supplemented by a repository in which validated metadata records corresponding to the application profiles can be published. Researchers can access all content on the platform via a central search function and easily reuse relevant content. The core idea of AIMS is to provide low-threshold access for an improved metadata management. Technically build around RDF and SHACL based application profiles also with a focus on interoperability with existing standards, interfaces and semantic technologies.
Datasheet
Status: 16.06.2021
Homepage | www.aims-projekt.de |
Description | About AIMS |
Code | - |
Communities | --- |
Version | - |
Features
Status: 16.06.2021
Supported Schema(s) | --- | All schemas with supported format |
Supported Format(s) | RDF, SHACL | Export as JSON, RDF/XML etc. |
Interface(s) | REST, GUI | OAI-PMH planned |
Open Source | planned | - |
License | MIT | |
Versioning | planned | - |
AAI | planned | |
External Storage | - | |
Referencable | planned |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 16.06.2021
- Metadata Repository only one part of a bigger platform.
- Focus on UI and related backend for user-friendly metadata schema creation, re-use and sharing implemented as RDF SHACL application profiles.
- Extensive API for integration in scientific workflows to track metadata during data creation and analysis.
Functionality
Status: 16.06.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | + | RDF, SHACL |
Update Schema | + | |
Validate Schema | + | |
Ingest Metadata | + | |
Update Metadata | ||
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | + | |
Persistent Identifier | + | via external service |
Remarks
- Focus on usability and low-threshold access.
- Compatibility with existing standards and terminologies.
- Accessible to other applications via SPARQL endpoints.
CKAN
Introduction
CKAN is a tool for making open data websites. It helps you manage and publish collections of data. It is used by national and local governments, research institutions, and other organizations who collect a lot of data. (https://docs.ckan.org/en/2.9/user-guide.html)
Datasheet
Status: 14.06.2022
Homepage | https://ckan.org |
Description | https://ckan.org/features |
Code | https://github.com/ckan/ckan |
Communities | --- |
Version | 2.9.5 (released on 19.01.2022) |
Features
Status: 08.06.2021
Supported Schema(s) | internal | |
Supported Format(s) | --- | |
Interface(s) | HTTP | REST like |
Open Source | yes | |
License | AGPL | GNU Affero General Public License |
Versioning | yes | history |
AAI | yes | user/group management |
External Storage | yes | via extensions |
Referencable | DOI | via extension |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 08.06.2021
- Creation of a federated network of data portals which share data between each other.
- Create data-visualisation views and expose data as line, bar and pie charts.
- Advanced geospatial features, covering data preview, search, and discovery.
Functionality
Status: 08.06.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | supports an own proprietary format |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | as data |
Update Metadata | + | |
Validate Metadata | (+) | via 'scheming' plugin |
Search by ... | ||
... Administrative MD | + | |
... Content | (+) | via 'DataStore' plugin |
Persistent Identifier | + | via extension |
Remarks
Higly customizable via extensions.
Cordra
Introduction
Highly configurable software for managing digital objects at scale.
Datasheet
Status: 14.06.2022
Homepage | https://www.cordra.org/ |
Description | https://www.cordra.org/cordra.html |
Code | https://gitlab.com/cnri/cordra |
Communities | --- |
Version | 2.4.0 (released on 21.02.2022) |
Features
Status: 19.05.2021
Supported Schema(s) | any | only predefined ones |
Supported Format(s) | JSON Schema | |
Interface(s) | REST | +DOIP + IRP |
Open Source | yes | code is open available but no open development |
License | Cordra License Agreement | |
Versioning | yes | simple object versioning (kind of a history) |
AAI | yes | JWT, HTTP Basic Auth |
External Storage | yes | configurable, mandatory for distributed systems |
Referencable | yes | internal & external via IRP interface |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
- Scalable infrastructure (allows load balancing)
- Referencing one schema from another
- Online editor for creating metadata documents (may not work with references)
- Validates supplied information against one or more pre-defined JSON schemas, and stores them as digital objects
- adoptable via hooks
- e.g. validation
- Highly configurable
- DOIP (Digital Object Interface Protocol) support
- IRP (Identifier/Resolution Protocol) support
- Indexing (via configured service (e.g. solr, elasticsearch, ...)
- OAI-PMH (!?) (via Metadata Translation) Proof-of-concept
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | (+) | must be configured |
Update Schema | (+) | overwrites the previous version |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | overwrites document (create a version in beforehand to prevent loss of 'old' document (experimental)) |
Validate Metadata | + | via hooks |
Search by ... | ||
... Administrative MD | + | |
... Content | + | via external service |
Persistent Identifier | + | via external service |
Remarks
Optimized for handling NoSQL information. Integrates popular storage and indexing solutions, and presents a unified interface. Provides configurable hooks to validate and update information at various stages of a digital object lifecycle.
Coscine
Introduction
Coscine is an integration platform for research data. It simplifies metadata management, project member management, and allows to conveniently archive research data.
Datasheet
Status: 16.06.2021
Homepage | https://coscine.pages.rwth-aachen.de/docs/public/pages/en/ |
Description | https://coscine.pages.rwth-aachen.de/docs/public/pages/en/about/ |
Code | https://git.rwth-aachen.de/coscine |
Communities | --- |
Features
Status: 16.06.2021
Supported Schema(s) | --- | All schemas with supported format |
Supported Format(s) | RDF, SHACL | |
Interface(s) | REST, GUI | |
Open Source | yes | https://git.rwth-aachen.de/coscine |
License | MIT | |
Versioning | yes | Usage of PROV |
AAI | yes | |
External Storage | yes | |
Referencable | yes | PID for resources and projects |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 16.06.2021
- Has a UI which can generate form elements based on RDF SHACL application profiles
- Interaction with a multitude of storage providers
- Provides access to its own version of S3 storage, called "RDS"
Functionality
Status: 16.06.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | + | RDF, SHACL |
Update Schema | + | |
Validate Schema | (+) | Syntax check |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | (+) | Planned |
Persistent Identifier | + |
Remarks
- Strong emphasis on following the FAIR principles
- Focus on collaborative work
- Uncomplicated data access
DSpace
Introduction
The software of choice for academic, non-profit & commercial organizations building open digital repositories
Datasheet
Status: 14.06.2022
Homepage | https://duraspace.org/dspace/ |
Description | https://duraspace.org/dspace/about/ |
Code | https://github.com/DSpace/DSpace |
Communities | --- |
Version | 7.2.1 (released on 01.04.2022) |
Features
Status: 21.05.2021
Supported Schema(s) | DC | extendible: e.g.: MARC, MODS could be easily integrated |
Supported Format(s) | all file types | but file type for schemas: XML |
Interface(s) | Web UI | REST API (planned for DSpace 7) |
Open Source | yes | |
License | BSD License | |
Versioning | ??? | no information found |
AAI | yes | "stack" of authentication methods / support for users/groups |
External Storage | yes | Amazon S3 or via referencing |
Referencable | yes | supports handle & bitstream 'persistent' identifiers |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 21.05.2021
- Supports preservation / curation
- Used by many sites
Functionality
Status: 21.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | buld in XML schemas (DC, ...) |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | technical, rights, preservation, structural, and behavioral metadata |
... Content | - | |
Persistent Identifier | + |
Remarks
- Not only a metadata repository.
- It allows to store (XML) metadata next to your digital objects.
- Ingest via 'DSpace Simple Archiv Format' contains
- DC metadata (xml)
- metadata (xml) linked to a registered schema (DSpace Metadata Schema Registry) via prefix
- content
Fedora
Introduction
Fedora is the flexible, modular, open source repository platform with native linked data support.
Datasheet
Status: 14.06.2022
Homepage | https://duraspace.org/fedora/ |
Description | https://duraspace.org/fedora/about/ |
Code | https://github.com/fcrepo/fcrepo/ |
Communities | --- |
Version | 6.2.0 (released on 03.06.2022) |
Features
Status: 17.05.2021
Supported Schema(s) | ... | |
Supported Format(s) | any | RDF and Linked Data / Recommendations from different communities. |
Interface(s) | REST / RDF | |
Open Source | yes | |
License | Apache 2.0 | |
Versioning | yes | Memento protocol |
AAI | yes | support for ACLs, ServletContainerAuthenticatingRealm and WebACAuthorizingRealm. |
External Storage | yes | empty binary as placeholder |
Referencable | yes | support for external PID Minter |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
- no limits regarding file types
- no limits for file size
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | history |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | + | via transform service (has to be configured manually) |
Persistent Identifier | + |
Remarks
- Extendable architecture
- Support for Linked Data
- Preservation ready
- Update to new version (beta status 05/2021) (coming soon)
GeRDI - Generic Research Data Infrastructure
Introduction
The GeRDI project deals with the development of a Generic Research Data Infrastructure (GeRDI). The aim is to enable all scientists in Germany, especially those who hold only small amounts of data, to store, share and re-use research data across disciplines.
Datasheet
Status: 19.05.2021
Homepage | https://www.gerdi-project.eu/ |
Description | https://www.gerdi-project.eu/about-gerdi/ |
Code | https://github.com/gerdi-project/ |
Communities | Digital Humanities, Microscopy and Bioinformatics, ... |
Version |
Features
Status: 19.05.2021
Supported Schema(s) | --- | |
Supported Format(s) | any | |
Interface(s) | Web | |
Open Source | --- | |
License | --- | |
Versioning | --- | |
AAI | yes | Login via website |
External Storage | yes | supports different sites |
Referencable | yes | implemented by connected repositories |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
Analyze data on HPC systems via Jupyter Hub.
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | only predefined schemas |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | + | transformation to DataCite |
Persistent Identifier | + | via connected repo |
Remarks
Supports FAIR DO
Invenio RDM
Introduction
InvenioRDM - a repository/document management platform.
Datasheet
Status: 14.06.2022
Homepage | https://invenio-software.org/ |
Description | https://invenio-software.org/about/ |
Code | https://github.com/inveniosoftware/invenio-app-rdm |
Communities | --- |
Version | 9.0.3 (released on 09.06.2022) |
Features
Status: 19.05.2021
Supported Schema(s) | any | |
Supported Format(s) | JSONSchema | |
Interface(s) | REST | |
Open Source | yes | |
License | MIT | |
Versioning | ||
AAI | yes | internal? |
External Storage | yes | Amazon S3 |
Referencable | yes | ISBN10, DOI, Handle, URN, PUBMED, ... |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
- extendible by (own) plugins
- search via elasticsearch (you have to define mappings manually)
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | - | |
Persistent Identifier | + |
Remarks
- On heavy development
- Invenio RDM: New release in summer 2021
- Scalable (100+ million records)
- Available as docker image
Invenio Instances
- CERN Open Data
- INSPIRE
- Zenodo
- B2Share
- DESY PUBDB
- European XFEL
- ...
Metacat
Introduction
Metacat, a metadata service to make data and metadata easy to discover, process and manage. Metacat supports many datasources as backend.
Datasheet
Status: 14.06.2022
Homepage | https://knb.ecoinformatics.org/knb/docs/ |
Description | https://knb.ecoinformatics.org/knb/docs/intro.html |
Code | https://github.com/NCEAS/metacat |
Communities | DataONE |
Version | 2.18.0 (released on 19.05.2022) |
Features
Status: 15.02.2022
Supported Schema(s) | DTD | |
Supported Format(s) | XML | |
Interface(s) | REST/Thrift interface | several implementations are available |
Open Source | yes | |
License | GPL 2.0 | |
Versioning | yes | history of documents |
AAI | yes | internal password file or LDAP |
External Storage | yes | supports many storage systems as backend. (Amazon S3 (via Hive), Druid, Elasticsearch, Redshift, Snowflake and MySQL) |
Referencable | yes | DOI |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 25.02.2022
- Support OAI-PMH (oai_dc, EML)
Functionality
Status: 15.02.2022
Function | Supported | Remarks |
---|---|---|
Register Schema | o | Store DTD(s) as package |
Update Schema | o | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | provide DTD(s)/package |
Search by ... | ||
... Administrative MD | + | filter |
... Content | + | pathquery (similar to XPath) |
since version 2.1 SOLR is used for indexing (DataONE out of the box but also own documents by configuration) | ||
Persistent Identifier | + | DOI using the EZID service |
Remarks
At a higher level, Metacat features can be categorized as follows:
- Data abstraction and interoperability
- Business and user-defined metadata storage
- Data discovery
- Data change auditing and notifications
- Hive metastore optimizations
MetaStore
Introduction
MetaStore is a metadata repository for managing millions of metadata documents. MetaStore supports communities with their specific schemas (XSD, JSON Schema).
Datasheet
Status: 14.06.2022
Homepage | --- |
Description | https://github.com/kit-data-manager/metastore2#readme |
Code | https://github.com/kit-data-manager/metastore2 |
Communities | --- |
Version | 1.0.0 (released on 29.03.2022) |
Features
Status: 17.05.2021
Supported Schema(s) | --- | All schemas with supported format |
Supported Format(s) | XSD, JSON Schema | |
Interface(s) | REST, GUI | GUI (coming soon) |
Open Source | yes | gitHub |
License | Apache 2.0 | |
Versioning | yes | Only simple versioning. Works like a history. |
AAI | yes | Authorization for documents based on roles. (JWT) |
External Storage | no | Linking via URLs could be possible but not implemented yet. |
Referencable | yes | Status: Referencable via PID(coming soon) or persistent URL. |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 17.05.2021
MetaStore consists of two parts:
- Metadata Repository for managing metadata documents
- Schema Registry for registering schema documents
Metadata Repository
- Up to million of documents (tested with 10 M metadata documents)
- Automatic validation during ingest
- High throughput, high performance (ingest & access)
- Live interaction / online handling and manipulation of metadata documents for data of ongoing research
Schema Registry
- Registering schema documents (XSD, JSON Schema)
- Supports arbitrary number of user-defined metadata schemas
- Supports different versions of a metadata schema
Functionality
Status: 17.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | + | JSON Schema, XSD |
Update Schema | + | |
Validate Schema | + | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | (+) | coming soon via enhanced service |
Persistent Identifier | + | via external service |
Remarks
Enhanced services
- Metadata Standards Catalog
- Human readable description for finding appropriate schema
- Direct access to schema via MetaStore.
- Metadata Explorer (Outlook)
- Exploring metadata by content
- Metadata Editor (coming soon)
- Update schema/documents online
- Authentication Server
- If a separate authentication service is to be set up.
MyCoRe
Introduction
MyCoRe is a framework for presentation and management of digital content. It enables the creation of own applications, i.e. repositories, bibliographies and digital libraries.
Datasheet
Status: 01.06.2022
Homepage | https://www.mycore.de |
Description | https://www.mycore.de/filecollection/MyCoRe_datasheet.pdf |
Code | https://github.com/MyCoRe-Org/mycore |
Communities | --- |
Version | LTS 2021.06 (released on 29.09.2021) |
Features
Status: 17.05.2022
Supported Schema(s) | DC, MODS, LIDO, EAD, TEI, MEI, METS | XML used internally, allows integration of custom schemas |
Supported Format(s) | any | |
Interface(s) | OAI-PMH, SWORD, REST, IIIF API | https://www.mycore.de/documentation/interfaces/ |
Open Source | yes | GitHub |
License | GPL v3 | |
Versioning | yes | optional |
AAI | yes | LDAP, Shibboleth |
External Storage | yes | PostgreSQL, MySQL, Oracle, IBM DB2, HSQLDB |
Referencable | DOI, URN, PURL |
Additional Features
Status: 01.06.2022
The MyCoRe framework
- supports the creation of static and dynamic web pages.
- includes an image viewer which supports several formats (i.e. jpeg, png, tiff, pdf, epub).
- enables creation of a sitemap which conforms to the Google Sitemap protocol.
- provides the relevant data to use the DFG Viewer.
- supports various classification systems, such as DDC, PACS, MeSH, vocabularies for publication and document types (DINI, DCMI) as well as languages (ISO 639.2). It is possible to browse and edit classifications.
Functionality
Status: 31.05.2022
Function | Supported | Remarks |
---|---|---|
Register Schema | + | |
Update Schema | ||
Validate Schema | + | |
Ingest Metadata | + | automated metadata extraction possible for jpeg, mp3 and pdf files |
Update Metadata | + | |
Validate Metadata | ||
Search by ... | ||
... Administrative MD | + | |
... Content | + | |
Persistent Identifier | + |
Remarks
MyCoRe uses the Apache Commons Virtual File System. Files can be stored locally or on remote servers.
MyCoRe follows a yearly release cycle: new LTS versions get released in September, with developer previews between major versions.
Open Science Framework (OSF)
Introduction
You may use OSF as a long-term data repository, electronic lab notebook, or as the collaboration tool for your team’s research.
Datasheet
Status: 17.05.2021
Homepage | https://www.cos.io |
Description | https://www.cos.io/products/osf |
Code | https://github.com/CenterForOpenScience/ |
Communities | no limits |
Version | 19.31.0 (released on 08.11.2019) |
Features
Status: 17.05.2021
Supported Schema(s) | --- | no built-in support |
Supported Format(s) | no limits | |
Interface(s) | REST /JSON:API v1.0 | https://developer.osf.io/#tag/General-Usage |
Open Source | yes | gitHub |
License | Apache 2.0 | |
Versioning | yes | Each file has a history (until you delete it) |
AAI | yes | Token Auth & OAuth |
External Storage | yes | Amazon S3, Bitbucket, Box, Dataverse, Dropbox, ... |
Referencable | DOI | Supports creation of DOIs. |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 17.05.2021
OSF may be used to manage your entire project from one place.
As a collaboration tool, OSF helps research teams work on projects privately or make the entire project publicly accessible for broad dissemination. As a workflow system, OSF enables connections to the many products researchers already use, streamlining their process and increasing efficiency.
Functionality
Status: 17.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | as part of the payload |
Update Metadata | + | creates a new version |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | - | |
Persistent Identifier | + |
Remarks
- Up to 50GB free public storage (5GB private storage)
- Extendable by Addons
- At least one server is located in Germany
Zenodo
Introduction
Free software suite enabling own digital library or document repositories built on top of Invenio.
Datasheet
Status: 21.05.2021
Homepage | https://zenodo.org/ |
Description | https://about.zenodo.org/ |
Code | https://github.com/zenodo/zenodo |
Communities | --- |
Version | --- |
Features
Status: 21.05.2021
Supported Schema(s) | --- | |
Supported Format(s) | --- | |
Interface(s) | REST | |
Open Source | yes | |
License | GPL 2.0 | |
Versioning | yes | supports also DOI versioning |
AAI | yes | ORCID, gitHub, local account |
External Storage | --- | |
Referencable | yes | DOI |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 21.05.2021
Service is free for everybody with some limits.
- file size < 50GB per dataset
- data stored at CERN Data Center -> long term preservation
Functionality
Status: 21.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | as data |
Update Metadata | + | |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | - | |
Persistent Identifier | + |
Remarks
Repository for any kind of digital objects. CERN Data Center guarantees a high reliability.
AIMS – Applying Interoperable Metadata Standards
Introduction
A platform for creating and sharing metadata schemas for better research data management in engineering. Implementing a modular metadata concept with a focus keeping interoperability while allowing highly specific description of metadata. In addition to a repository for subject-specific application profiles for subsequent use, it also provides a generator for their creation and improvement based on controlled vocabularies. These are supplemented by a repository in which validated metadata records corresponding to the application profiles can be published. Researchers can access all content on the platform via a central search function and easily reuse relevant content. The core idea of AIMS is to provide low-threshold access for an improved metadata management. Technically build around RDF and SHACL based application profiles also with a focus on interoperability with existing standards, interfaces and semantic technologies.
Datasheet
Status: 16.06.2021
Homepage | www.aims-projekt.de |
Description | About AIMS |
Code | - |
Communities | --- |
Version | - |
Features
Status: 16.06.2021
Supported Schema(s) | --- | All schemas with supported format |
Supported Format(s) | RDF, SHACL | Export as JSON, RDF/XML etc. |
Interface(s) | REST, GUI | OAI-PMH planned |
Open Source | planned | - |
License | MIT | |
Versioning | planned | - |
AAI | planned | |
External Storage | - | |
Referencable | planned |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 16.06.2021
- Metadata Repository only one part of a bigger platform.
- Focus on UI and related backend for user-friendly metadata schema creation, re-use and sharing implemented as RDF SHACL application profiles.
- Extensive API for integration in scientific workflows to track metadata during data creation and analysis.
Functionality
Status: 16.06.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | + | RDF, SHACL |
Update Schema | + | |
Validate Schema | + | |
Ingest Metadata | + | |
Update Metadata | ||
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | + | |
Persistent Identifier | + | via external service |
Remarks
- Focus on usability and low-threshold access.
- Compatibility with existing standards and terminologies.
- Accessible to other applications via SPARQL endpoints.
CKAN
Introduction
CKAN is a tool for making open data websites. It helps you manage and publish collections of data. It is used by national and local governments, research institutions, and other organizations who collect a lot of data. (https://docs.ckan.org/en/2.9/user-guide.html)
Datasheet
Status: 14.06.2022
Homepage | https://ckan.org |
Description | https://ckan.org/features |
Code | https://github.com/ckan/ckan |
Communities | --- |
Version | 2.9.5 (released on 19.01.2022) |
Features
Status: 08.06.2021
Supported Schema(s) | internal | |
Supported Format(s) | --- | |
Interface(s) | HTTP | REST like |
Open Source | yes | |
License | AGPL | GNU Affero General Public License |
Versioning | yes | history |
AAI | yes | user/group management |
External Storage | yes | via extensions |
Referencable | DOI | via extension |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 08.06.2021
- Creation of a federated network of data portals which share data between each other.
- Create data-visualisation views and expose data as line, bar and pie charts.
- Advanced geospatial features, covering data preview, search, and discovery.
Functionality
Status: 08.06.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | supports an own proprietary format |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | as data |
Update Metadata | + | |
Validate Metadata | (+) | via 'scheming' plugin |
Search by ... | ||
... Administrative MD | + | |
... Content | (+) | via 'DataStore' plugin |
Persistent Identifier | + | via extension |
Remarks
Higly customizable via extensions.
Cordra
Introduction
Highly configurable software for managing digital objects at scale.
Datasheet
Status: 14.06.2022
Homepage | https://www.cordra.org/ |
Description | https://www.cordra.org/cordra.html |
Code | https://gitlab.com/cnri/cordra |
Communities | --- |
Version | 2.4.0 (released on 21.02.2022) |
Features
Status: 19.05.2021
Supported Schema(s) | any | only predefined ones |
Supported Format(s) | JSON Schema | |
Interface(s) | REST | +DOIP + IRP |
Open Source | yes | code is open available but no open development |
License | Cordra License Agreement | |
Versioning | yes | simple object versioning (kind of a history) |
AAI | yes | JWT, HTTP Basic Auth |
External Storage | yes | configurable, mandatory for distributed systems |
Referencable | yes | internal & external via IRP interface |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
- Scalable infrastructure (allows load balancing)
- Referencing one schema from another
- Online editor for creating metadata documents (may not work with references)
- Validates supplied information against one or more pre-defined JSON schemas, and stores them as digital objects
- adoptable via hooks
- e.g. validation
- Highly configurable
- DOIP (Digital Object Interface Protocol) support
- IRP (Identifier/Resolution Protocol) support
- Indexing (via configured service (e.g. solr, elasticsearch, ...)
- OAI-PMH (!?) (via Metadata Translation) Proof-of-concept
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | (+) | must be configured |
Update Schema | (+) | overwrites the previous version |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | overwrites document (create a version in beforehand to prevent loss of 'old' document (experimental)) |
Validate Metadata | + | via hooks |
Search by ... | ||
... Administrative MD | + | |
... Content | + | via external service |
Persistent Identifier | + | via external service |
Remarks
Optimized for handling NoSQL information. Integrates popular storage and indexing solutions, and presents a unified interface. Provides configurable hooks to validate and update information at various stages of a digital object lifecycle.
Coscine
Introduction
Coscine is an integration platform for research data. It simplifies metadata management, project member management, and allows to conveniently archive research data.
Datasheet
Status: 16.06.2021
Homepage | https://coscine.pages.rwth-aachen.de/docs/public/pages/en/ |
Description | https://coscine.pages.rwth-aachen.de/docs/public/pages/en/about/ |
Code | https://git.rwth-aachen.de/coscine |
Communities | --- |
Features
Status: 16.06.2021
Supported Schema(s) | --- | All schemas with supported format |
Supported Format(s) | RDF, SHACL | |
Interface(s) | REST, GUI | |
Open Source | yes | https://git.rwth-aachen.de/coscine |
License | MIT | |
Versioning | yes | Usage of PROV |
AAI | yes | |
External Storage | yes | |
Referencable | yes | PID for resources and projects |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 16.06.2021
- Has a UI which can generate form elements based on RDF SHACL application profiles
- Interaction with a multitude of storage providers
- Provides access to its own version of S3 storage, called "RDS"
Functionality
Status: 16.06.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | + | RDF, SHACL |
Update Schema | + | |
Validate Schema | (+) | Syntax check |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | (+) | Planned |
Persistent Identifier | + |
Remarks
- Strong emphasis on following the FAIR principles
- Focus on collaborative work
- Uncomplicated data access
DSpace
Introduction
The software of choice for academic, non-profit & commercial organizations building open digital repositories
Datasheet
Status: 14.06.2022
Homepage | https://duraspace.org/dspace/ |
Description | https://duraspace.org/dspace/about/ |
Code | https://github.com/DSpace/DSpace |
Communities | --- |
Version | 7.2.1 (released on 01.04.2022) |
Features
Status: 21.05.2021
Supported Schema(s) | DC | extendible: e.g.: MARC, MODS could be easily integrated |
Supported Format(s) | all file types | but file type for schemas: XML |
Interface(s) | Web UI | REST API (planned for DSpace 7) |
Open Source | yes | |
License | BSD License | |
Versioning | ??? | no information found |
AAI | yes | "stack" of authentication methods / support for users/groups |
External Storage | yes | Amazon S3 or via referencing |
Referencable | yes | supports handle & bitstream 'persistent' identifiers |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 21.05.2021
- Supports preservation / curation
- Used by many sites
Functionality
Status: 21.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | buld in XML schemas (DC, ...) |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | technical, rights, preservation, structural, and behavioral metadata |
... Content | - | |
Persistent Identifier | + |
Remarks
- Not only a metadata repository.
- It allows to store (XML) metadata next to your digital objects.
- Ingest via 'DSpace Simple Archiv Format' contains
- DC metadata (xml)
- metadata (xml) linked to a registered schema (DSpace Metadata Schema Registry) via prefix
- content
Fedora
Introduction
Fedora is the flexible, modular, open source repository platform with native linked data support.
Datasheet
Status: 14.06.2022
Homepage | https://duraspace.org/fedora/ |
Description | https://duraspace.org/fedora/about/ |
Code | https://github.com/fcrepo/fcrepo/ |
Communities | --- |
Version | 6.2.0 (released on 03.06.2022) |
Features
Status: 17.05.2021
Supported Schema(s) | ... | |
Supported Format(s) | any | RDF and Linked Data / Recommendations from different communities. |
Interface(s) | REST / RDF | |
Open Source | yes | |
License | Apache 2.0 | |
Versioning | yes | Memento protocol |
AAI | yes | support for ACLs, ServletContainerAuthenticatingRealm and WebACAuthorizingRealm. |
External Storage | yes | empty binary as placeholder |
Referencable | yes | support for external PID Minter |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
- no limits regarding file types
- no limits for file size
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | history |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | + | via transform service (has to be configured manually) |
Persistent Identifier | + |
Remarks
- Extendable architecture
- Support for Linked Data
- Preservation ready
- Update to new version (beta status 05/2021) (coming soon)
GeRDI - Generic Research Data Infrastructure
Introduction
The GeRDI project deals with the development of a Generic Research Data Infrastructure (GeRDI). The aim is to enable all scientists in Germany, especially those who hold only small amounts of data, to store, share and re-use research data across disciplines.
Datasheet
Status: 19.05.2021
Homepage | https://www.gerdi-project.eu/ |
Description | https://www.gerdi-project.eu/about-gerdi/ |
Code | https://github.com/gerdi-project/ |
Communities | Digital Humanities, Microscopy and Bioinformatics, ... |
Version |
Features
Status: 19.05.2021
Supported Schema(s) | --- | |
Supported Format(s) | any | |
Interface(s) | Web | |
Open Source | --- | |
License | --- | |
Versioning | --- | |
AAI | yes | Login via website |
External Storage | yes | supports different sites |
Referencable | yes | implemented by connected repositories |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
Analyze data on HPC systems via Jupyter Hub.
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | only predefined schemas |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | + | transformation to DataCite |
Persistent Identifier | + | via connected repo |
Remarks
Supports FAIR DO
Invenio RDM
Introduction
InvenioRDM - a repository/document management platform.
Datasheet
Status: 14.06.2022
Homepage | https://invenio-software.org/ |
Description | https://invenio-software.org/about/ |
Code | https://github.com/inveniosoftware/invenio-app-rdm |
Communities | --- |
Version | 9.0.3 (released on 09.06.2022) |
Features
Status: 19.05.2021
Supported Schema(s) | any | |
Supported Format(s) | JSONSchema | |
Interface(s) | REST | |
Open Source | yes | |
License | MIT | |
Versioning | ||
AAI | yes | internal? |
External Storage | yes | Amazon S3 |
Referencable | yes | ISBN10, DOI, Handle, URN, PUBMED, ... |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 19.05.2021
- extendible by (own) plugins
- search via elasticsearch (you have to define mappings manually)
Functionality
Status: 19.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | - | |
Persistent Identifier | + |
Remarks
- On heavy development
- Invenio RDM: New release in summer 2021
- Scalable (100+ million records)
- Available as docker image
Invenio Instances
- CERN Open Data
- INSPIRE
- Zenodo
- B2Share
- DESY PUBDB
- European XFEL
- ...
Metacat
Introduction
Metacat, a metadata service to make data and metadata easy to discover, process and manage. Metacat supports many datasources as backend.
Datasheet
Status: 14.06.2022
Homepage | https://knb.ecoinformatics.org/knb/docs/ |
Description | https://knb.ecoinformatics.org/knb/docs/intro.html |
Code | https://github.com/NCEAS/metacat |
Communities | DataONE |
Version | 2.18.0 (released on 19.05.2022) |
Features
Status: 15.02.2022
Supported Schema(s) | DTD | |
Supported Format(s) | XML | |
Interface(s) | REST/Thrift interface | several implementations are available |
Open Source | yes | |
License | GPL 2.0 | |
Versioning | yes | history of documents |
AAI | yes | internal password file or LDAP |
External Storage | yes | supports many storage systems as backend. (Amazon S3 (via Hive), Druid, Elasticsearch, Redshift, Snowflake and MySQL) |
Referencable | yes | DOI |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 25.02.2022
- Support OAI-PMH (oai_dc, EML)
Functionality
Status: 15.02.2022
Function | Supported | Remarks |
---|---|---|
Register Schema | o | Store DTD(s) as package |
Update Schema | o | |
Validate Schema | - | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | provide DTD(s)/package |
Search by ... | ||
... Administrative MD | + | filter |
... Content | + | pathquery (similar to XPath) |
since version 2.1 SOLR is used for indexing (DataONE out of the box but also own documents by configuration) | ||
Persistent Identifier | + | DOI using the EZID service |
Remarks
At a higher level, Metacat features can be categorized as follows:
- Data abstraction and interoperability
- Business and user-defined metadata storage
- Data discovery
- Data change auditing and notifications
- Hive metastore optimizations
MetaStore
Introduction
MetaStore is a metadata repository for managing millions of metadata documents. MetaStore supports communities with their specific schemas (XSD, JSON Schema).
Datasheet
Status: 14.06.2022
Homepage | --- |
Description | https://github.com/kit-data-manager/metastore2#readme |
Code | https://github.com/kit-data-manager/metastore2 |
Communities | --- |
Version | 1.0.0 (released on 29.03.2022) |
Features
Status: 17.05.2021
Supported Schema(s) | --- | All schemas with supported format |
Supported Format(s) | XSD, JSON Schema | |
Interface(s) | REST, GUI | GUI (coming soon) |
Open Source | yes | gitHub |
License | Apache 2.0 | |
Versioning | yes | Only simple versioning. Works like a history. |
AAI | yes | Authorization for documents based on roles. (JWT) |
External Storage | no | Linking via URLs could be possible but not implemented yet. |
Referencable | yes | Status: Referencable via PID(coming soon) or persistent URL. |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 17.05.2021
MetaStore consists of two parts:
- Metadata Repository for managing metadata documents
- Schema Registry for registering schema documents
Metadata Repository
- Up to million of documents (tested with 10 M metadata documents)
- Automatic validation during ingest
- High throughput, high performance (ingest & access)
- Live interaction / online handling and manipulation of metadata documents for data of ongoing research
Schema Registry
- Registering schema documents (XSD, JSON Schema)
- Supports arbitrary number of user-defined metadata schemas
- Supports different versions of a metadata schema
Functionality
Status: 17.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | + | JSON Schema, XSD |
Update Schema | + | |
Validate Schema | + | |
Ingest Metadata | + | |
Update Metadata | + | |
Validate Metadata | + | |
Search by ... | ||
... Administrative MD | + | |
... Content | (+) | coming soon via enhanced service |
Persistent Identifier | + | via external service |
Remarks
Enhanced services
- Metadata Standards Catalog
- Human readable description for finding appropriate schema
- Direct access to schema via MetaStore.
- Metadata Explorer (Outlook)
- Exploring metadata by content
- Metadata Editor (coming soon)
- Update schema/documents online
- Authentication Server
- If a separate authentication service is to be set up.
Open Science Framework (OSF)
Introduction
You may use OSF as a long-term data repository, electronic lab notebook, or as the collaboration tool for your team’s research.
Datasheet
Status: 17.05.2021
Homepage | https://www.cos.io |
Description | https://www.cos.io/products/osf |
Code | https://github.com/CenterForOpenScience/ |
Communities | no limits |
Version | 19.31.0 (released on 08.11.2019) |
Features
Status: 17.05.2021
Supported Schema(s) | --- | no built-in support |
Supported Format(s) | no limits | |
Interface(s) | REST /JSON:API v1.0 | https://developer.osf.io/#tag/General-Usage |
Open Source | yes | gitHub |
License | Apache 2.0 | |
Versioning | yes | Each file has a history (until you delete it) |
AAI | yes | Token Auth & OAuth |
External Storage | yes | Amazon S3, Bitbucket, Box, Dataverse, Dropbox, ... |
Referencable | DOI | Supports creation of DOIs. |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 17.05.2021
OSF may be used to manage your entire project from one place.
As a collaboration tool, OSF helps research teams work on projects privately or make the entire project publicly accessible for broad dissemination. As a workflow system, OSF enables connections to the many products researchers already use, streamlining their process and increasing efficiency.
Functionality
Status: 17.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | as part of the payload |
Update Metadata | + | creates a new version |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | - | |
Persistent Identifier | + |
Remarks
- Up to 50GB free public storage (5GB private storage)
- Extendable by Addons
- At least one server is located in Germany
Zenodo
Introduction
Free software suite enabling own digital library or document repositories built on top of Invenio.
Datasheet
Status: 21.05.2021
Homepage | https://zenodo.org/ |
Description | https://about.zenodo.org/ |
Code | https://github.com/zenodo/zenodo |
Communities | --- |
Version | --- |
Features
Status: 21.05.2021
Supported Schema(s) | --- | |
Supported Format(s) | --- | |
Interface(s) | REST | |
Open Source | yes | |
License | GPL 2.0 | |
Versioning | yes | supports also DOI versioning |
AAI | yes | ORCID, gitHub, local account |
External Storage | --- | |
Referencable | yes | DOI |
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Additional Features
Status: 21.05.2021
Service is free for everybody with some limits.
- file size < 50GB per dataset
- data stored at CERN Data Center -> long term preservation
Functionality
Status: 21.05.2021
Function | Supported | Remarks |
---|---|---|
Register Schema | - | |
Update Schema | - | |
Validate Schema | - | |
Ingest Metadata | + | as data |
Update Metadata | + | |
Validate Metadata | - | |
Search by ... | ||
... Administrative MD | + | |
... Content | - | |
Persistent Identifier | + |
Remarks
Repository for any kind of digital objects. CERN Data Center guarantees a high reliability.
Evaluation Matrix
Status: 15.02.2022
Function | AIMS | Ckan | Cordra | Coscine | DSpace | Fedora | Gerdi | Invenio | MetaStore | MyCoRe | OSF | Zenodo |
---|---|---|---|---|---|---|---|---|---|---|---|---|
Register Schema | + | - | (+)1 | + | - | - | - | - | + | + | - | - |
Update Schema | + | - | (+)2 | + | - | - | - | - | + | - | - | |
Validate Schema | (+)3 | - | - | (+)3 | - | - | - | - | + | + | - | - |
Ingest Metadata | + | + | + | + | + | + | + | + | + | + | + | + |
Update Metadata | + | + | + | + | + | + | + | + | + | + | + | |
Validate Metadata | + | (+)4 | + | + | - | - | + | - | + | - | - | |
Search by ... | ||||||||||||
... Administrative MD | + | + | + | + | + | + | + | + | + | + | + | + |
... Content | (+)5 | + | (+)6 | - | + | + | - | (+)7 | + | - | - | |
Persistent Identifier | (+) | + | + | + | + | + | + | + | +8 | + | + | + |
For more detailed information please use the links in the table header.
Description
- Register Schema:
- Support for arbitrary schemas of a specific format (e.g. JSON Schema, XSD)
- The schema should at least be referencable by a unique identifier.
- Update Schema:
- Possibility to
- work on different versions of a schema
- adapt schemas over time
- Possibility to
- Validate Schema:
- Check schema for correct syntax
- Ingest Metadata:
- Store metadata (document) in repository
- Ideally with previous validation
- Store metadata (document) in repository
- Update Metadata:
- Possibility to update already ingested metadata (documents).
- Validate Metadata:
- Possibility to validate documents on the basis of registered schemas.
- Search by Administrative MD:
- Search documents by their metadata (e.g. ingest date, ingester, ...)
- Search by Content:
- Search documents by their content
- Persistent Identifier:
- Support for Persistent Identifiers (e.g. DOI, Handle)
Footnotes
Support for arbitrary (JSON Schema) via configuration only (-> restricted to administrators)
Manually by administrators
Syntax check
Via 'scheming' plugin with a rudimentary schema format
Via 'DataStore' plugin (supports SQL queries)
Planned
Via enhanced service
PID via enhanced service