sovity / edc-ui

Connector UI for the sovity EDC Community Edition.
https://sovity.de/en/connect-to-data-space-en/
Apache License 2.0
32 stars 13 forks source link

Display log for Asset updates #827

Open ip312 opened 5 months ago

ip312 commented 5 months ago

Feature Request

Description

As a user of sovity's connector (both is data provider and data consumer persona) I want to see the updates that were made to an asset So that I have the best "contextualized" understanding about the Asset; especially how it evolved over time.

Feedback from customer (part of the original feature request)

With the EDC 7.. we have the possibility to edit assets, which is very useful and user-friendly. However, the user has no way of tracking later when the changes were made. All asset changes (create, update, delete) should be logged within the EDC. There is currently no requirement to keep the complete change history and versions.

Solution Design and Work Breakdown

Goal: Enhance the asset dialog pop-up when user clicks on an asset card such that user can access logs about the asset (when it was created, when it was modified, etc.).

### Tasks
- [ ] UI/UX Design
- [ ] Implementation
- [ ] User Acceptance Test (UAT)
tmberthold commented 5 months ago

Hello and Thank You for reaching out to us! I'll forward it internally and our team will let you know when there's any news.

jkbquabeck commented 5 months ago

Hello @ip312, you state there would be no requirement to keep the complete change history and versions. As a version history for asset meta data is something new, I do not see why this would be a bug. Please add this to the list of requested features if this functionality is desired.

AbdullahMuk commented 1 week ago

@ip312 Thank you for raising this gap for improvement.

We are designing a suitable solution that we aim to implement in the next months (a more accurate timeline will be communicated at a later stage.)

PS: I have taken the liberty to update the original context of this issue so that it helps us work efficiently on a solution. The versioning history functionality on GitHub ensures that the original request can still be accessed.