enable data downloads for the data spaces community

[pvgenuchten]

the data spaces community is in a process of adopting a range of standards for interactions with data resources. we can use these standards to share our data downloads within data spaces

DoD: understand/follow what standards are adopted by the data spaces community and understand if it puts new constraints on our infrastructure

[BerkvensNick]

@pvgenuchten, @DajanaSnopkova and @Somakanthan , the "Data export, download" component doesn't exist anymore in our current architecture (see updated architecture document and evaluation technical development first prototype, this has become part of the “Catalogue” (Download as is) and “Transformation and Harmonization” (Download interoperable metadata).
As we don't have a “Transformation and Harmonization” repository in our Soilwise github environment, WE is working in a repository in their own environment,

• can we rename this repository to "Transformation and Harmonization"?
• is this issue part of the "Transformation and Harmonization" component?

[Somakanthan]

@BerkvensNick The "Download interoperable metadata" is part of the “Transformation and Harmonization” component and is an integral part of Hale Studio. We have recorded a tutorial video on Soil Data Harmonisation with Hale Studio and will make it availale asap.

I'm ok to rename this repo. @pvgenuchten any preferences from your side?

[pvgenuchten]

Download data component could be an interesting component, considering the following use cases:

• if for a resource a transformation alignment is available, the service could apply the transformation as part of the download
• a download service could proxy a request to a wfs or file and apply a filter for the requested bounds, transform to the requested format or projection
• a download component could manage the login to the service (sso/basicauth) and request data from a protected service