Include a parameter in Normalized FareNet table to identify the real search initiated by user vs other fare points collected with different date variations

[maddy-at-work]

This parameter would be useful to do User Behaviour Analysis like route popularity, popular departure dates, popular site edition etc

[BigDataKatha]

We still want all fares in the Normalized FareNet table in case we need to query if certain fares shown in the airModules were actually captured from the airline IBE. @madhura-everymundo, please add any other use cases.

[danielsan]

Isn't farenetId there for that reason?

[maddy-at-work]

FarenetID gets duplicated in normalized table. Ex. During a route search for fly-dates X, if we were assigned dataCoreId1 and if script also captures pricings for other fly-dates, say X+1, X+2, every fare point/row in the normalized table has dataCoreId1. Hence we are looking for a parameter to identify the fare point X, initiated by the user. Best, *Madhura Selvarajan* Data Integrity - Data Analyst EVERY *MUNDO*25 SE 2nd Ave., Suite 900 Miami, FL 33131 USA main:+1 (305) 375-0045 <(305)%20375-0045> mobile: +1 (774) 701-2643 <(774)%701-2643> www.everymundo.com The information and any attachments contained in this email may contain confidential and/or privileged information and is intended solely for the use of the intended named recipient(s). Any disclosure or dissemination in whatever form, by another other than the intended recipient is strictly prohibited. If you have received this transmission in error, please contact the sender and destroy this message and any attachments. Thank you.

…

On Tue, Apr 16, 2019 at 3:53 PM Daniel Santana ***@***.***> wrote: Isn't *farenetId* there for that reason? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AaxQ-pGNYhrCLXljV5onJ066S9yEvSskks5vhipMgaJpZM4cEfRj> .