Local file download feature

[avogadriholonix]

Hi.
In the previous DataspaceConnector UI app, there was the feature to download a file requested to an another connector through a contract agreement directly and locally, through the browser. For what is my experience this app offers the user two possibilities:

• push the file to an external rest api
• use an external datasink that has to be described through a json object (but I have not found the related documentation yet).

My question is the following: what is the easiest way for a user to have at his disposal the file in his pc, like the DataspaceConnector UI app?

Thank you in advance.

Roberto Avogadri

[SebastianOpriel]

Hi Robert,

thanks for your question. Indeed, we see the same necessity. As the new EDC Connector has no such feature built in, we are currently working on this for our Connector-as-a-Service - available for a low monthly fee. In case the CaaS shall grab your attention, please drop us a message at [email protected]. If you stick to the community edition or the Core EDC itself, I am afraid, that there is no such option yet.

Best Regards,
Sebastian

[avogadriholonix]

Dear Sebastian,
thank you for your prompt answer.
I would have a further question... In the case I would choose to push the file in an external rest api service through i.e. a POST, as the ui app user, how I could found out the filename reference needed to fulfill correctly the above mentioned call?
I seems that such information has not passed from the backend to the frontend to complete the POST call object.
Thank you again.

Roberto Avogadri

[richardtreier]

Hi Robert,

to answer your question, a Use Case Application would have to separately remember the asset consumed and guess an appropriate file name from that.

Data Transfers in the EDC are just exchanges of bytes.

All semantic logic will have to be handled by the use case application interpreting assets, contract definitions and using policies.

Best Regards,
Richard

[avogadriholonix]

Hi Richard. Thank you for your answer. I agree with you: I used the term "file" to simplify the example. My question could be how the front end user can fill the POST call object to intercept the streaming data delegated for instance to the http proxy in the backend. If I miss to write such information It seems that the backend can't complete the operation with en error related to a null reference. My hypothesis was that at a certain point a software layer complete the "POST" related object with such information, but It doesn't seem to work in such a manner. Could anyone give me an example on how to use such front-end functionality, please? Thank you in advance. Best regards, Roberto Avogadri

…

On Thu, Apr 27, 2023 at 1:13 PM Richard Treier ***@***.***> wrote: Hi Robert, to answer your question, a Use Case Application would have to separately remember the asset consumed and guess an appropriate file name from that. Data Transfers in the EDC are just exchanges of bytes. All semantic logic will have to be handled by the use case application interpreting assets, contract definitions and using policies. Best Regards, Richard — Reply to this email directly, view it on GitHub <#248 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWKSE7KY2SWLYYWSVGM4CF3XDJIGTANCNFSM6AAAAAAXNQIQGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[richardtreier]

Hi Robert,

there's currently no functionality in the vanilla EDC nor our Connector-as-a-Service to transform data. Data transformers are on our roadmap, but probably won't be available until later this year.

So currently one must develop a fully-fledged Use Case Application as an intermediary between the EDC and the target or source system.

For that we currently have work in progress on our own EDC API Wrapper with generated Java and TypeScript API Client Libraries for easier Use Case Application bootstrapping, which will included in our Community Editions. It is as mentioned still work in progress, but should be completed before we will have generic out-of-the-box Data Transforming, which will most likely be an Enterprise Edition feature.

Best Regards,
Richard

[avogadriholonix]

Hi Richard. Thank you very much for your answer. Best regards, Roberto Avogadri

…

On Thu, Apr 27, 2023 at 2:36 PM Richard Treier ***@***.***> wrote: Hi Robert, there's currently no functionality in the vanilla EDC nor our Connector-as-a-Service to transform data. Data transformers are on our roadmap, but probably won't be available until later this year. So currently one must develop a fully-fledged Use Case Application as an intermediary between the EDC and the target or source system. For that we currently have *work in progress* on our own EDC API Wrapper <https://github.com/sovity/edc-extensions/tree/main/extensions/wrapper/> with generated Java and TypeScript API Client Libraries for easier Use Case Application bootstrapping, which will included in our Community Editions. It is as mentioned still work in progress, but should be completed before we will have generic out-of-the-box Data Transforming, which will most likely be an Enterprise Edition feature. Best Regards, Richard — Reply to this email directly, view it on GitHub <#248 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWKSE7KG7BDUYTVY7YCZTE3XDJR4XANCNFSM6AAAAAAXNQIQGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>