SebastianOpriel
commented
3 months ago Subscription: Cron-triggered
- [ ] UI: Start Interval Based Data Transfer
- [ ] Either custom DB Entity
- [ ] or custom Transfer Type (but how do we prevent them from being handed to the DP)
- [ ] Needs to support full range of transfer types
- [ ] Opportunity: Clean / aggregate old transfers
- [ ] Quartz: Dynamic Schedules
- [ ] Restart after Connector Startup
Subscription: On update notify
- [ ] Architecture
- [ ] Note: Catena had a custom notification endpoint, maybe re-use that?
- [ ] Idea: Receive calls "onUpdate"
- [ ] Would require same tables as previous solution
- [ ] SUM: Opportunity: "Persistable Data Sinks", could be managed as such, would require CRUD UI
- [ ] List Endpoint
- [ ] List UI
- [ ] Delete Dialog
- [ ] Delete Endpoint
- [ ] Create Endpoint
- [ ] Create Form
- [ ] Selection in Transfer Dialog
- [ ] Flag: Supports Update Push. Display for assets, Create in Form, Add to API Wrapper
- [ ] Source: Flag data as updated action, as button for assets, API Wrapper endpoint, UI: Button in UI on provider side on the asset
- [ ] Notification receiving, automated transferring: Custom DB Table, these are not "transfers" but transfer plans. Create transfers
Feature Request
https://github.com/Mobility-Data-Space/MDS-Project/issues/65
Business value
How does this tie into the current product?
After successful contract negotiation the consumer intends to consume data. Among current functionalities he have a possibility to "subscribe" for a data offer. For this subscription he can choose between push and pull methods. If "push" is selected he shall get data immediately after the data are available on the provider side. If "pull" is selected he can define a request frequency. More than one subscription per offer shall be allowed. Subscriptions shall be represented as list and be manageable within the connector.
Outlook
TBD
(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?
User stories
As consumer I want to have a possibility to subscribe for the push delivery to make my service more efficient and avoid any time delay. As provider I want to understand the push subscription to ensure the data delivery from the backend without any time delay. As consumer I want to have a possibility to subscribe for the continuous pull delivery and define the request frequency. More than one subscription per data offer is allowed. As consumer I want to see all subscirptions as manageable list to have possibility to delete, edit request frequency etc.
(For sovity Team to complete) Solution Proposal and Work Breakdown
--------------- MDS format for initial inspection---------- https://github.com/Mobility-Data-Space/MDS-Project/issues/65
Background
Problem statement
If a consumer currently wants to retrieve data continuously and not just once, he has to write and deploy his own script for this purpose. Furthermore the consumer has no possibility to use push mechanism, which is absolutely crucial for alert massegaes such as driver on wrong side of highway .
Customer perspective
The consumer needs this functionality to be able to implement real use cases using .
Business value
Proposed solution
Description of the feature
After successful contract negotiation the consumer intends to consume data. Among current functionalities he have a possibility to "subscribe" for a data offer. For this subscription he can choose between push and pull methods. If "push" is selected he shall get data immediately after the data are available on the provider side. If "pull" is selected he can define a request frequency. More than one subscription per offer shall be allowed. Subscriptions shall be represented as list and be manageable within the connector.
Dependencies
Not Known
Suggested visual realization
TBD
Challenges
TBD
User stories
As consumer I want to have a possibility to subscribe for the push delivery to make my service more efficient and avoid any time delay. As provider I want to understand the push subscription to ensure the data delivery from the backend without any time delay. As consumer I want to have a possibility to subscribe for the continuous pull delivery and define the request frequency. More than one subscription per data offer is allowed. As consumer I want to see all subscirptions as manageable list to have possibility to delete, edit request frequency etc.
Outlook
TBD