Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Enabler:Knowage
Description
I forward this to the tech-help inbox as to make sure that a ticket
is created and assigned to Jose Manuel and Alessandro.
Document
Juanjo Hierro
Chief Technology Officer
juanjose.hierro@fiware.org <juanjose.hierro@fiware.org>
www.linkedin.com/in/jhierro <https://www.linkedin.com/in/jhierro>
Twitter: @fiware <https://twitter.com/fiware> @JuanjoHierro
<https://twitter.com/JuanjoHierro>
-------- Forwarded Message --------
Subject: Fiware & FASHION CLOUD
Date: Tue, 3 Apr 2018 10:21:16 +0200
From: Martin Brücher <martin.bruecher@fashion.cloud>
To: Juanjo Hierro <juanjose.hierro@fiware.org>, José Manuel Cantera
<josemanuel.cantera@fiware.org>, Portosa Alessandro
<Alessandro.Portosa@eng.it>, Davide Zerbetto <davide.zerbetto@eng.it>
CC: Florian Klemt <florian.klemt@fashion.cloud>
Good morning everyone,
I hope you guys had a great Easter holiday.
We would like to ask you for a consolidated feedback on our suggested
Fiware implementation.
Florian sent an email on March 27th and José confirmed the setup on the
same day. Florian also had a call with the Knowage team to get their
advice and during the call our setup was confirmed.
Now Davide wrote another mail on March 29th saying that he sees some
issues with the Knowage implementation. However it doesn't really
contain a concrete advice what we can improve.
Therefore we'd be very happy if you could confirm the setup as soon as
possible or otherwise provide detailed specification what you expect so
that we can present a proper solution on Friday.
Thanks a lot in advance and have a great week!
Best regards
Martin
_____
On our side looks good. ccing Alessandro.
Please send us an invitation for the checkpoint on April 6th.
Best
> On 27 Mar 2018, at 12:37, Florian Klemt <florian.klemt@fashion.cloud
> <florian.klemt@fashion.cloud>> wrote:
>
> Hello everyone,
>
> thanks again for the chance to present our implementation ofFiwarein
> the FASHION CLOUD application. To make sure that we will meet your
> expectations for the final assessment, we present our proposed
> implementation:
>
> * Our core Business Intelligence and Data Analytics Service will be
> solely based onFiwaretechnologies
> * Our Application will publish relevant events to the Orion Context
> Broker. Following Events will be implemented for the final assessment:
> o a new user signed up
> o a new file was shared on the Platform
> o a file was downloaded by a user
> o a file was deleted by the owner
> * Since our main use case is to enable users to share Fashion
> related data/files, these are the most relevant events in our system
> * We will connect Knowage with the Context Broker to be able to
> visualize data in real time. To do that we will connect Cygnus to
> Orion in order to persist the data in a MySQL database. This MySQL
> database will then be the data source for Knowage. This setup was
> recommended to us in a previous technical call
> * We will configure Knowage to use the MySQL data source that get
> automatically updated as soon as new events are broadcast by Orion
> * We will set up a dashboard to visualize the incoming data
> * All of this will deployed to production servers and integrated in
> our production application
>
>
> We will also share a vision of our roadmap for the FASHION CLOUD BI
> and Analytics Service: After we have successfully set up the Data
> Dashboard and customized it to our needs, the plan is to extend this
> system to get real time notifications of certain events or event
> constellations. To be able to do that we plan to integrate the Complex
> Event Processing GE (CEP) to allow us to analyze the generated data in
> real time. The foundation that we lay now will be the basis for the
> future development of our Analytics Service. We are more than happy to
> share this development in blog posts or other means to support other
> teams to buid a similar monitoring setup.
>
> Please let us know if this meets your expectations.
>
> Thanks you very much and best regards,
> Martin & Florian
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
Replied by email to martin.bruecher@fashion.cloud, florian.klemt@fashion.cloud, josemanuel.cantera@fiware.org, juanjose.hierro@fiware.org, Alessandro.Portosa@eng.it:
Dear Martin
your proposed implementation seems fine, except the part with Orion Context Broker, Knowage and MySQL.
As already stated, you can use MySQL and Knowage for hystorical analyses, not for real-time analyses. If you want to display real-time data coming from the Orion Context Broker, you have to retrieve data directly from Orion Context Broker by a NGSI dataset in Knowage (Florian should know how to do that, in any case documentation is here: https://knowage.readthedocs.io/en/latest/user/NGSI/README/index.html) and display it into a Knowage cockpit.
My concern I tried to explain to you in my last email was about the usage of the Orion Context Broker: there was only 1 entity defined! therefore I thought it was a poor usage and your application not "context-aware".
The more your application can get meaningful information from real-time data, the more your application is "context-aware"; therefore I suggested Florian to define many more entities in the Orion Context Broker and to exploit them properly (displaying it in Knowage or implementing some business logic).
Hope this helps
Best regards
Davide