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 5 Next »

📌 Introduction

This page gathers known issues of the onboarding process and the reccomended solutions or work-arounds for the given issue. If the issue you are facing does not appear on the list here, please contact HRI service desk at servicedesk@health-ri.nl and we will assist you.

Upgrading your FDP shapes

By default, the FDP reference implementation ships with so-called default shapes out of the box, based on DCAT 2. To upgrade them to the Health-RI model, see below.

Upgrade to Health-RI model v1.0.0

  • https://github.com/Health-RI/health-ri-metadata/blob/v1.0.0/README.md

  • Log in as an admin user

  • Click on the profile button on the top right of the user interface, and navigate to metadata schemas

  • Select the Resource schema

    • In the v1.0.0 model, copy the contents of the Resource shape

    • In the FDP, paste the contents in the Form Definition area.

    • Click Save and release on the bottom of the page.

    • Enter a description to indicate the use of the v1.0.0 model.

    • Select an appropriate version number.

    • Click Release.

  • Repeat for Catalog, Dataset, Distribution, and DataService.

Solve “unable to get data” on existing metadata after a model upgrade

🚧 TODO describe steps in detail.

FDP

Date and DateTime errors when editing

From what we can gather, FDP client v1.17.x exhibits strange behaviour when creating or editing metadata fields with date or date-time values. The bug report describes the details. A workaround could be moving back to v1.16.3, which Radboud seems to be using without issues (needs to be confirmed).

Delete metadata when FDP client gives a error message

Verify the graph uri.

SELECT *
FROM <http://localhost/dataset/6dba4d3e-888a-4b8d-bacf-0fd322bef2f7>
{
    ?s ?p ?o
}

Drop the graph of the resource that should be deleted.

DROP GRAPH <http://localhost/dataset/6dba4d3e-888a-4b8d-bacf-0fd322bef2f7>

Delete the link from the parent resource to the (deleted) child resource. In the example below a dataset (child) is removed from the catalog (parent), therefore using the dcat:dataset relation.

DELETE DATA {
    <http://localhost/catalog/7918a701-b33f-4a96-a511-8c16117b21c8> <http://www.w3.org/ns/dcat#dataset> <http://localhost/dataset/6dba4d3e-888a-4b8d-bacf-0fd322bef2f7> .
}

mongo. Remove the metadata information from the metadata collection.

> use fdp
> db.metadata.deleteOne({ "uri": "<http://localhost/dataset/6dba4d3e-888a-4b8d-bacf-0fd322bef2f7>" })

ELSI

Email address visibility

Currently, creator and publisher identities are associated with an email-address. There are concerns about public visibility of PI email addresses. The current workaround is to use a departement email address until we know more about other options (e.g. hiding email behind a login).

  • No labels