...
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
triple store. Drop the graph of the resource that should be deleted.
| Code Block | ||
|---|---|---|
| ||
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.
| Code Block | ||
|---|---|---|
| ||
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.
| Code Block | ||
|---|---|---|
| ||
> use fdp
> db.metadata.deleteOne({ "uri": "<http://localhost/dataset/6dba4d3e-888a-4b8d-bacf-0fd322bef2f7>" }) |
ELSI
Email address visibility
...