Custom Datasink Config (JSON) and Custom Transfer Process Request (JSON) options

[epanagou-ubitech]

Hello community!

What is the difference between the Custom Datasink Config (JSON) and Custom Transfer Process Request (JSON) choices when transfering an asset and if possible, could you point to some example JSON files we could use?

We have tried the JSONs we found in the following resources:

1. https://github.com/sovity/edc-extensions/blob/main/docs/getting-started/documentation/parameterized_assets.md
2. Support Parameterized HttpData Transfers #105 (comment)

However, in the case of

• Custom Datasink Config (JSON): We got the error DataAddress builder missing Type property.
• Custom Transfer Process Request (JSON): We got the error null value in column "connector_address" violates not-null constraint.

Finally, is there an advantage to using one of these options instead of the REST-API Endpoint option?

Thank you in advance!

[richardtreier]

Hello, this is indeed a bug, and will be fixed in future releases.

Fixed in #455

[epanagou-ubitech]

Thank you for the quick response!

Regarding the differences between the Custom Datasink Config (JSON) and Custom Transfer Process Request (JSON) options, is there documentation we could refer to? Also, is there an advantage to using one of these options instead of the default REST-API Endpoint option?

[richardtreier]

Consuming and providing Parameterized HTTP data offers is supported through our UI by now. You should be able to click "Show HTTP Datasource Parameterization" in the transfer dialog, which will allow you to provide overrides.

---

When trying out a data sink type that is not available via the UI with a custom backend, one might want to use the Custom Datasink Config (JSON) to initiate the transfer process, e.g.:

{
    "properties": {
        "type": "HttpData",
        "baseUrl": "https: //my-data-sink/",
        "method": "POST"
    }
}

---

However, when one also wants to pass parameters to the providing connector or play around with the detailed configuration of EDC transfer processes, one would use the Custom Transfer Process Request (JSON) option, e.g.:

{
    "protocol": "ids-multipart",
    "assetId": "this-will-be-overriden-by-the-ui",
    "contractId": "this-will-be-overriden-by-the-ui",
    "dataDestination": {
        "properties": {
            "type": "HttpData",
            "baseUrl": "https: //my-data-sink/",
            "method": "POST"
        }
    },
    "properties": {
        "pathSegments": "12345/some-resource/6890",
        "queryParams": "a=b&c=d"
    },
    "transferType": {
        "contentType": "application/octet-stream",
        "isFinite": true
    },
    "managedResources": false,
    "connectorAddress": "this-will-be-overriden-by-the-ui--but-is-broken-right-now-as-said-above",
    "connectorId": "consumer"
}

Notice, how above you only had to provide the dataDestination, while below you can provide most fields of the transfer process request. It is meant as a quick way to test transfer process initiations and parameters without having to deal with authentication as the UI is already handling authentication.

[epanagou-ubitech]

Thank you very much!