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

[Pablo Fernández Moniz]

Hi!

Our point of view thinking about the front end.

Regarding data access from the front end, and store it in Orion, we checked
in this
<http://stackoverflow.com/questions/31047422/filter-querycontext-with-attribute-value-in-orion-context-broker>
reply from Fermín in stackoverflow that retrieving entities by filtering
attributes is, currently, not possible in Orion. Do you think that it
should be a problem for us?

A possible solutions should be:

 - to make IDs of composite type in order to give information about the
associated restaurant and customer.  This way we can filter again using the
ID field. Example of Review id: { "id": "Review-890_jmcantera_Res-5678",
...}.

 - to bring all the entites to the front end and filter them via
javascript, which is a brute force approach and may not be very elegant.

We also wanted to ask if it is already decided the data/queries that we
want to retrieve from the app front end, in order to have more clear how we
will work and focus on the front end requirements.

KR,

ULPGC team




2015-07-06 14:59 GMT+01:00 Alvaro del Castillo <acs at bitergia.com>:

> Hi!
>
> El lun, 06-07-2015 a las 13:11 +0000, JOSE MANUEL CANTERA FONSECA
> escribió:
> > Responding in an empty emails as I didn’t realise I was not subscribed
> > to the list
> >
> >
> > I think customer reviews are part of the context information to be
> > stored in Orion. But reviews are entities associated to both customers
> > and restaurants. So we will have something like what is proposed below
>
> Good approach, context information, but not from a restaurant entity,
> but from a specific entity: reviews. Not sure if we are forcing orion
> usage a bit, but it is a developer guide app for it, so it could be ok.
>
> >
> >
> > By the way Alvaro, please provide a first draft of the data models to
> > be used. I would like to review them before we start coding
>
> We are playing with the code to load the data in Orion, in an flexible
> approach so the model could be changed later. Give us one-two days
> before having a first data model.
>
> Cheers!
>
>
> >
> >
> > ----
> >
> >
> > Restaurant
> >
> >
> > {
> >    id: “Res-5678”,
> >    name: “Casa Pepa”,
> >    average_score: {
> >      “place”: 7,
> >      “service”: 8,
> >      “food”: 5
> >    },
> >   “location”: xxxx
> > }
> >
> >
> > Review
> >
> > {
> >    “id”: “Review-890”,
> >    “author”: “jmcantera”,
> >   “subject”: “Res-5678”,
> >   “creationDate”, “xxxx”,
> >   “score”: {
> >   }
> > }
> >
> >
> > Customer
> >
> >
> > {
> >   “id”: “jmcantera”,
> >    “name”: “Jose Manuel Cantera”
> > }
> >
> >
> > ______________________________________________________________________
> >
> > Este mensaje y sus adjuntos se dirigen exclusivamente a su
> > destinatario, puede contener información privilegiada o confidencial y
> > es para uso exclusivo de la persona o entidad de destino. Si no es
> > usted. el destinatario indicado, queda notificado de que la lectura,
> > utilización, divulgación y/o copia sin autorización puede estar
> > prohibida en virtud de la legislación vigente. Si ha recibido este
> > mensaje por error, le rogamos que nos lo comunique inmediatamente por
> > esta misma vía y proceda a su destrucción.
> >
> > The information contained in this transmission is privileged and
> > confidential information intended only for the use of the individual
> > or entity named above. If the reader of this message is not the
> > intended recipient, you are hereby notified that any dissemination,
> > distribution or copying of this communication is strictly prohibited.
> > If you have received this transmission in error, do not read it.
> > Please immediately reply to the sender that you have received this
> > communication in error and then delete it.
> >
> > Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> > destinatário, pode conter informação privilegiada ou confidencial e é
> > para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> > senhoria o destinatário indicado, fica notificado de que a leitura,
> > utilização, divulgação e/ou cópia sem autorização pode estar proibida
> > em virtude da legislação vigente. Se recebeu esta mensagem por erro,
> > rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> > proceda a sua destruição
> > _______________________________________________
> > Fiware-developer-experience mailing list
> > Fiware-developer-experience at lists.fiware.org
> > https://lists.fiware.org/listinfo/fiware-developer-experience
>
>
> --
> 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 <http://www.pablofm.com>    Linkedin
<http://www.linkedin.com/in/pablofernandezmoniz/>   Twitter
<http://www.twitter.com/monizpablo>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-developer-experience/attachments/20150707/4e1ee575/attachment.html>