Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

what is local system that export metadata( EPD, local data management system, Molgenis, Beacon? XNAT (health ri repository, img2catalog)

Introduction

The option to expose your metadata from an institute local system, available in your institute, allows for the closest link between the source data and the public metadata. The responsibility for maintaining the metadata is kept at the source, be it software or people.

This approach requires a system that already incorporates this behaviour, or deep knowledge of the source system and the availability of software engineering capacity to extend the functionality of the system.

Explanation

The platforms/systems used in your institute should allow extensions to expose the metadata of existing source data. If the system is closed or the vendor is not able to add this behaviour, an alternative approach could be the https://health-ri.atlassian.net/wiki/spaces/FSD/pages/edit-v2/292519963?draftShareId=3e2fb8f1-0cba-4f12-a724-d664f2b9bf2c.

MOLGENIS implementation of the FDP extension.

MOLGENIS partly supports the FAIR(Findable, Accessible, Interoperable, and Re-usable) principles. FDP is implemented in MOLGENIS EMX2 in compliance with the latest v1.1 specification of FAIR Data Point available at specs.fairdatapoint.org.

Setup and configuration

The easiest way to enable FDP in MOLGENIS EMX2 is by choosing ‘FAIR_DATA_HUB’ as a template for your database. This will add three tables that will define the content of your FAIR Data Point: Catalog, Dataset and Distribution. Loading the ‘FAIR_DATA_HUB’ template including the example data will result in a fully operational FAIR Data Point. The example data can be used as a reference on how to enter data into the system. It can be safely removed or replaced.

Before the FDP can be used, log in as the admin user and visit your FDP at <server>/api/fdp. This will add a database setting called FAIR Data Point root metadata to the schema that enables your FDP. This setting contains a piece of RDF/TTL that is part of your FDP root endpoint which is fully customizable. Here, you can change the information about your FDP such as title, publisher, contact point and language. To make changes, go to your FDP-enabling schema, go to Settings, Advanced settings, and click the Edit button for FAIR Data Point root metadata.

After setting up these tables, this is how its contents are translated to the FDP structure:

  • Each Dataset contains a reference to one or multiple Catalogs via the belongsToCatalog field.

    • These references can also be viewed in the referred-to Catalogs via the dataset field.

  • Each Distribution contains a reference to one or multiple Datasets via the belongsToDataset field.

    • These references can also be viewed in the referred-to Datasets via the distribution field.

pros/cons

Pro

  • Responsibility of maintenance lies closest to the owner(s) of the source material

Con

  • Requires extension of existing tooling

Next steps

copy/link to https://health-ri.atlassian.net/wiki/spaces/FSD/pages/279183386/3.+Exposing+metadata#%3Acheck_mark%3A--Next-steps

  • No labels