You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streampipes.apache.org by Dominik Riemer <do...@bytefabrik.ai> on 2022/06/13 19:53:48 UTC
Improve organization of StreamPipes concepts in UI
Hi all,
currently, we have a lot of different views in the UI such as data streams, live dashboards and data views. These can all be defined independently. As we focus on the IIoT domain, I think it would be a nice feature for users to "assign" these concepts to real-world objects, e.g., plants or machines. For instance, it would be nice to create a "machine" and assign a live dashboard, corresponding data view and live data to this machine. This would improve the overall user experience as we could reuse well-known concepts in the different views instead of the currently unconnected views.
What do you think? I plan to start with a quick prototype of a representation for this which we can use for further refinement.
Cheers,
Dominik
Re: Improve organization of StreamPipes concepts in UI
Posted by Philipp Zehnder <ph...@bytefabrik.ai>.
Hi Dominik,
thank you.
I think that is a good solution.
How can I try this out locally?
Philipp
________________________________
Von: Dominik Riemer <ri...@apache.org>
Gesendet: Dienstag, Juni 14, 2022 9:59 PM
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: Re: AW: Improve organization of StreamPipes concepts in UI
Hi Philipp,
cool, I've just created an issue to track this feature.
I have created a simple model to represent assets such as machines and options to assign linked objects to an asset. My first prototype only contains an API without UI (which we can add later) and uses a generic CouchDB storage to persist such asset models.
I'll also create a wiki page where we can discuss data model requirements.
Cheers
Dominik
On 2022/06/13 20:06:38 Philipp Zehnder wrote:
> Hi Dominik,
>
> I like the idea.
> It would be great to model a machine and assign a dashboard or a data view to it.
>
> Where should we store this kind of information? Maybe we can reuse the API to store JSON objects in the couchdb.
> How could this API look like? I think to get started it is sufficient to support simple CRUD operations.
>
> Cheers,
> Philipp
>
>
> Von: Dominik Riemer <do...@bytefabrik.ai>
> Datum: Montag, 13. Juni 2022 um 21:54
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Improve organization of StreamPipes concepts in UI
> Hi all,
>
> currently, we have a lot of different views in the UI such as data streams, live dashboards and data views. These can all be defined independently. As we focus on the IIoT domain, I think it would be a nice feature for users to "assign" these concepts to real-world objects, e.g., plants or machines. For instance, it would be nice to create a "machine" and assign a live dashboard, corresponding data view and live data to this machine. This would improve the overall user experience as we could reuse well-known concepts in the different views instead of the currently unconnected views.
>
> What do you think? I plan to start with a quick prototype of a representation for this which we can use for further refinement.
>
> Cheers,
> Dominik
>
Re: AW: Improve organization of StreamPipes concepts in UI
Posted by Dominik Riemer <ri...@apache.org>.
Hi Philipp,
cool, I've just created an issue to track this feature.
I have created a simple model to represent assets such as machines and options to assign linked objects to an asset. My first prototype only contains an API without UI (which we can add later) and uses a generic CouchDB storage to persist such asset models.
I'll also create a wiki page where we can discuss data model requirements.
Cheers
Dominik
On 2022/06/13 20:06:38 Philipp Zehnder wrote:
> Hi Dominik,
>
> I like the idea.
> It would be great to model a machine and assign a dashboard or a data view to it.
>
> Where should we store this kind of information? Maybe we can reuse the API to store JSON objects in the couchdb.
> How could this API look like? I think to get started it is sufficient to support simple CRUD operations.
>
> Cheers,
> Philipp
>
>
> Von: Dominik Riemer <do...@bytefabrik.ai>
> Datum: Montag, 13. Juni 2022 um 21:54
> An: dev@streampipes.apache.org <de...@streampipes.apache.org>
> Betreff: Improve organization of StreamPipes concepts in UI
> Hi all,
>
> currently, we have a lot of different views in the UI such as data streams, live dashboards and data views. These can all be defined independently. As we focus on the IIoT domain, I think it would be a nice feature for users to "assign" these concepts to real-world objects, e.g., plants or machines. For instance, it would be nice to create a "machine" and assign a live dashboard, corresponding data view and live data to this machine. This would improve the overall user experience as we could reuse well-known concepts in the different views instead of the currently unconnected views.
>
> What do you think? I plan to start with a quick prototype of a representation for this which we can use for further refinement.
>
> Cheers,
> Dominik
>
AW: Improve organization of StreamPipes concepts in UI
Posted by Philipp Zehnder <ph...@bytefabrik.ai>.
Hi Dominik,
I like the idea.
It would be great to model a machine and assign a dashboard or a data view to it.
Where should we store this kind of information? Maybe we can reuse the API to store JSON objects in the couchdb.
How could this API look like? I think to get started it is sufficient to support simple CRUD operations.
Cheers,
Philipp
Von: Dominik Riemer <do...@bytefabrik.ai>
Datum: Montag, 13. Juni 2022 um 21:54
An: dev@streampipes.apache.org <de...@streampipes.apache.org>
Betreff: Improve organization of StreamPipes concepts in UI
Hi all,
currently, we have a lot of different views in the UI such as data streams, live dashboards and data views. These can all be defined independently. As we focus on the IIoT domain, I think it would be a nice feature for users to "assign" these concepts to real-world objects, e.g., plants or machines. For instance, it would be nice to create a "machine" and assign a live dashboard, corresponding data view and live data to this machine. This would improve the overall user experience as we could reuse well-known concepts in the different views instead of the currently unconnected views.
What do you think? I plan to start with a quick prototype of a representation for this which we can use for further refinement.
Cheers,
Dominik