...
Solve “unable to get data” on existing metadata after a model upgrade
...
Catalog shape works after upgrading from default shape to v1 shape. Manual edit lets the user enter an identifier for the publisher.
dataset shape works after upgrading from default shape to v1 shape.
dist shape works after upgrading from default shape to v1 shape. Manual edit lets user add access url and media type.
Moving from v1 to v2(draft)
catalog v2-draft upgrade works
dataset v2-draft upgrade breaks. Modified is mandatory, which the user can fill in. There is an issue in the v2-draft model for Dataset, specifically on
dcat:distribution(see https://github.com/Health-RI/health-ri-metadata/blob/develop/Formalisation(shacl)/Core/PiecesShape/Dataset.ttl#L102-L105).distribution v2-draft upgrade works.
FDP
Date and DateTime errors when editing
...
| Code Block | ||
|---|---|---|
| ||
> use fdp
> db.metadata.deleteOne({ "uri": "<http://localhost/dataset/6dba4d3e-888a-4b8d-bacf-0fd322bef2f7>" }) |
Properties not showing in forms
Sometimes properties will not show when viewing or editing metadata. Possible causes are:
The property does not have a
dash:viewerordash:editordefined in the metadata schema. The solution is to update the property’s attributes in the appropriate metadata schema.Properties defined on a higher level in the hierarchy are not inherited in the extending classes. This seems to be a bug in the FDP reference implementation. An issue is filed in the FDP github repository, you can check on the progress there: https://github.com/FAIRDataTeam/FAIRDataPoint/issues/580
ELSI
Email address visibility
...