introduction
...
📌 Introduction
If your local system doesn’t support the feature to directly expose metadata, you can use the following approach as an alternative. Instead of utilizing the https://health-ri.atlassian.net/wiki/spaces/FSD/pages/edit-v2/292880393?draftShareId=a11733bc-5522-448c-aeae-527390b75106 option approach, this puts method involves conducting automated exports from your institute’s local system through a script or workflow. By doing so, the export logic is moved outside of the source application.
This approach requires the knowledge of a data steward in collaboration with the local IT department.
...
🧠 Explanation /
...
Approach
The source data we want to export is contained stored within an a specific application used within the institute. An automated export will require access to the underlying data, for example through an API or direct database (read) access.Link to example application: To automate the export process, we need to access the raw data that lies beneath this application. This can typically be done either by accessing the data through an API provided by the application, or by directly connecting to the database where the data is stored (read access). This allows us to retrieve the data automatically without manual intervention.
Img2Catalog application
An example application that allows automatic export from your local system to FAIR data point is img2catalog, a registration tool developed by Health-RI, which simplifies the registration of image datasets. This tool queries an XNAT instance and generates DCAT-AP 3.0 metadata.
It can register image collections directly at Health-RI FAIR Data Point, as well as at a local FDP that can then be linked to the national health data catalog.
For details regarding installation and use, see https://github.com/health-ri/img2catalog
...
⚖️ Pros /
...
Cons
Pro
Close to the source material
Con
Requires frequent execution
Next steps
copy/link to https://health-ri.atlassian.net/wiki/spaces/FSD/pages/279183386/3.+Exposing+metadata#%3Acheck_mark%3A--Next-steps Pros
Automated exports of data reduce the need for manual entry. Manual input is more error-prone, more labor-intensive and less future-proof
Cons
Requires technical expertise,
If the underlying data structure or API endpoints change, this may cause disruptions in the export script or workflow.
Next steps
If you have an FDP and compliant metadata (Metadata mapping ) within your FDP, the data can be harvested by the National Catalogue. For this step, please contact servicedesk@health-ri.nl .