Asset Properties need to be persisted on the consumer side

[richardtreier]

Feature Request

Description

Right now we cant show asset properties for consuming contract agreements or transfer processes.

This is bad, because our parameterization hints can't be shown, the endpoint documentation can't be shown, etc., which is all very annoying.

The Core EDC has said this is not a bug to them, as they expect connectors to crawl periodically all connectors of the data space which we consider harmful (n²).

Solution Proposal and Work Breakdown

• Check if in edc 0.1.x the contract negotiation table contains the asset or not.
• If not:
  • Add JooQ to edc-extensions
  • Add a custom table to persist foreign assets, I recommend JSONB for the asset properties. And also add a "lastRefreshedAt".
  • These foreign assets need to be keyed by the connector endpoint + the asset id
• Add a custom API wrapper endpoint that starts a contract negotiation. That one also contains the asset properties. Unless an EDC Event will actually re-fetch the asset. Assets cannot be fetched as such, as only contract offers can be fetched. These might be restricted by n-times usage or other similar things. So we persist the "last known asset properties" when initiating a negotiation.
• The transfer endpoint and contract agreement endpoints should show these asset properties for consuming contracts.
• Update the UI to use the new negotiation endpoint.

[bearn01d]

@richardtreier Is there a rough timeline for this issue to be addressed?