How to get asset details on catalog request

[SebastianOpriel]

We are currently struggeling with changes to the catalog endpoint responses. Previously we were able to get all asset information from a ContractOffer via getAssets() method, now only containing an assetId with method getAssetId().

In a catalog browser on consumer side, we want to visualize all asset offerings incl. details. The current idea would be to get the catalog of a provider and fetch each's asset information with a separate call to getAsset endpoint. I assume, this is not the intended way. Have you any recommendation?

[ndr-brt]

In a DCAT catalog, the Dataset structure (that refers to a single Asset in the EDC domain) should contain all the Asset properties., please take a look at this Sample, in which the Catalog contains for example the edc:contenttype property, that was part of the asset created on the provider.

the getAsset endpoint is on the management side and it should not be accessed outside the owner organization.

[SebastianOpriel]

Thanks for your quick reply and the explanation!

[SebastianOpriel]

@ndr-brt One more question: Our EDC returns an array of datasets,

{
  "@id": "478a07bb-4df0-471e-aabe-c6d47558b329",
  "@type": "dcat:Catalog",
  "dcat:dataset": [
    {
    "@id": "test-1.0",
    "@type": "dcat:Dataset",
    ...

while the linked document returns an object

{
  "@id": "31f6d748-d35b-4dec-9e34-d141fd17b458",
  "@type": "dcat:Catalog",
  "dcat:dataset": {
    "@id": "assetId",
    "@type": "dcat:Dataset",
    ...

Is the linked document correct? Thus, we shall expect for parsing the DCAT an object, if none or just one dataset is available, and otherwise an array?

[SebastianOpriel]

While it is here also an array: https://github.com/International-Data-Spaces-Association/ids-specification/blob/2546b7806bc7c69e23b24944ea75ebdc3e44d197/catalog/message/catalog.json#L19C8-L19C20

[ndr-brt]

This is because how the json-ld compaction is configured: ref. #3323

[SebastianOpriel]

Oh thanks :-) I understand, that we always can expect an array (in the future).