[Fiware-developer-experience] Restaurant Context design for Orion

[Alvaro del Castillo]

Hi!

El lun, 06-07-2015 a las 13:53 +0100, Pablo Fernández Moniz escribió:
> Hi!
> 
> 
> Trying to help, here is our opinion
> 

Thanks!

> 
> Since recommendations or reviews are persistent information and not
> context information, we believe that using Orion Context Broker may
> not be the best approach.
> 
> 
> In our opinion, probably the simplest option is to store the data
> directly in a DB and access it using a custom REST API like:
> 
> 
> http://<host>/addRecommendation/ [post]
> body 
> [
>     {
>       "restaurant" : "ElBulli",
>       "Quality" : "5",
>       "Price" : "3",
>       "Text" : "Great place for ....."
>     },
> ...
>  ]
> 
> 
> --
> http://<host>/getRecommendation/ElBulli [get]
> Response
> {
>  "restaurant": "ElBulli",
>  "recommendations":[
>   {
>       "Quality" : "5",
>       "Price" : "3",
>       "Text" : "Great place for ....."
>   },
>   {
>       "Quality" : "5",
>       "Price" : "4",
>       "Text" : "Great place for ....."
>   },
>   .....
>  ]
> }
> 
> 
> 
> If we want to force to use Orion, an approach could be to insert the
> last recommendation as context and use another GE to retrieve
> historical data:

Great! This is the same approach we were thinking.

> 
> 
>       * We don't have experience using STH but we think that we could
>         use it and ask for all recommendations of a particular
>         restaurant in a specified time, or ask for the sum of elements
>         and make an average of reviews.
>       * We could use Cosmos and it may be interesting if we think that
>         recommendations are Big Data. The problem could be that create
>         an instance of Cosmos is not easy.

In then current approach, we using Cygnus for storing the history. We
have used CKAN and MySQL as backend.

> By the way. ULPGC team prepared a small system to publish data stored
> in PosgreSQL DB using CKAN. It may be useful at any time. If we need
> it, just ask for it
> 

Hmmm, I think PosgreSQL is not a natural tech for Orion+Cygnus stack.
But is is good to have this work in mind. Thanks!

Cheers

> 
> 
> 
> Kind regards,
> 
> 
> ULPGC Team
> 
> 2015-07-06 10:09 GMT+01:00 Alvaro del Castillo <acs at bitergia.com>:
>         Hi all!
>         
>         In restaurants we need to store recommendations. In Orion we
>         will store
>         the context information (name, address ...) but this changing
>         (and
>         growing) information, recommendations, how should be managed
>         in Orion?
>         
>         An approach could be to store the last recommendation in
>         context
>         information (orion) and the history of recommendations, to be
>         stored in
>         MySQL (for example) using cygnus.
>         
>         Thoughts? Should we move this kind of questions to
>         stackoverflow?
>         
>         Cheers
>         --
>         Alvaro del Castillo San Félix
>         acs at bitergia.com - Chief Technical Officer (CTO)
>         http://www.bitergia.com
>         "Software metrics for your peace of mind"
>         
>         
>         _______________________________________________
>         Fiware-developer-experience mailing list
>         Fiware-developer-experience at lists.fiware.org
>         https://lists.fiware.org/listinfo/fiware-developer-experience
> 
> 
> 
> 
> -- 
> 
> Pablo Fernández Moniz
> 
> GIT Analyst
> 
> 
> Web    Linkedin   Twitter
> 


-- 
Alvaro del Castillo San Félix
acs at bitergia.com - Chief Technical Officer (CTO)
http://www.bitergia.com
"Software metrics for your peace of mind"