404 response for "my-metadata" by metadata child issues

[SeanBerrieHRI]

What components are related to the issue?

Metadata Records

Which FDP are you using?

No response

Version

1.8.2

What happened?

Description:
Caused by a non-existing Dataset Series linked to a Dataset. Here is a dataset that tries to retrieve a Dataset Series that doens’t exist in Graphdb.

Actual:
Because the Dataset Series doens’t exist, it leads to issues creating an overview with the data retrieved from the endpoint to use for the “my-metadata” page.

Expected:
Overview of all the metadata stored within my environment.

I wasn’t able to replicate this issue in my local environment. I have tried to replicate the issue by creating a Dataset Series on the Dataset and saving it as draft, and by deleting/editing the child Dataset Series. Both didn’t result in this issue. I’m assuming it’s an issue caused from uploading the dummy data without an existing Dataset Series or possibly somehow caused by deleting or editing specific fields in a connected Dataset Series of a Dataset. This issue is also not specifically related to just Dataset Series, because this issue also occurs in another enivronment by a Dataset that can't be found.

Relevant log output

[dennisvang]

Hi @SeanBerrieHRI thanks for the detailed description.

Unfortunately, without knowing the relevant details of your FDP configuration, in terms of metadata-schemas and resource definitions, there's not much we can say about this.

I understand from your description that you were unable to reproduce the issue.
Nevertheless, a minimal reproducible example, extending the default FDP configuration from our compose repo, would be very helpful. In this case a persistent stack would probably be an appropriate starting point: https://github.com/FAIRDataTeam/compose/tree/master/fdp/persistent/v1

[kburger]

Minimal reproducable example:

1. load the compose stack at https://github.com/FAIRDataTeam/compose/tree/master/fdp/persistent/v1
2. update the default Catalog shape to include the following property:

sh:property [
    sh:path dcat:dataset ;
    sh:nodeKind sh:IRI ;
    dash:editor dash:URIEditor ;
  ]

3. for happy flow:
   a. create a catalog without filling in the new dataset field
   b. navigate to My Metadata
   c. observe a tree with one catalog node
4. for reproducible example:
   a. create a catalog and fill in the newly added dataset property with a random url
   b. navigate to My Metadata
   c. observe a 404

[dennisvang]

Thanks @kburger, using your MRE I was able to reproduce the issue.

The 404 also arises if you try to view the details of the catalog from step 4 (instead of "My Metadata").

The underlying problem is that the FDP expects the URI (the object of dcat:dataset) to represent a resource that exists in its triple store.

Of course this should be communicated in a useful way, instead of the status 404.

[dennisvang]

This is where the problem arises:

FAIRDataPoint/src/main/java/nl/dtls/fairdatapoint/api/controller/metadata/GenericController.java

Line 198 in 72bc9bd

final Metadata childState = metadataStateService.get(i(childUri.stringValue()));

and then

FAIRDataPoint/src/main/java/nl/dtls/fairdatapoint/service/metadata/state/MetadataStateService.java

Line 67 in 72bc9bd

throw new ResourceNotFoundException(format(MSG_NOT_FOUND, metadataUri));