Implement forwarding of the Content Type Header through the EDC Data Plane #865
Labels
kind/enhancement
New feature or request
scope/ce
sovity's Open Source Community Edition
scope/mds
related to MDS
status/blocked/needs-product
requires input from product owner
task/analyze
Need for investigation
Feature Request
Description
A clear and concise description of what the customer wants to happen.
Which Areas Would Be Affected?
e.g., DPF, CI, build, transfer, etc.
Why Is the Feature Desired?
What problems does that user face that existing functionalities do solve?
How does this tie into the current product?
Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new innovative ideas?
(For sovity Team to complete) Stakeholders
Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature?
(For sovity Team to complete) Solution Proposal and Work Breakdown
Tasks
-----------------MDS Format for quick inspection-------------
https://github.com/Mobility-Data-Space/MDS-Project/issues/74
Already analyzed in https://github.com/sovity/PMO-Software/issues/694
Background
Problem statement
Currently the EDC has a known bug which prevent the transition of the content type from the provider data source to the consumer. This shall be fixed.
Customer perspective
Nevertheless it would be more comfortable to have an optional posiibility to set the content type from the UI, the metadata field exists already.
Business value
TBD
Proposed solution
Description of the feature
If the metadata asset field "content type" is set, this shall be passed with the data to the data consumer.
Dependencies
PR already exists
Suggested visual realization
n/a
Challenges
not Known
User stories
As Data Provider I want to set the content type in the Connector UI to give the consumer mire information about my data.
Outlook
TBD
The text was updated successfully, but these errors were encountered: