From users-return-9-archive-asf-public=cust-asf.ponee.io@unomi.apache.org Thu Oct 11 15:54:08 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 369BD18064A for ; Thu, 11 Oct 2018 15:54:08 +0200 (CEST) Received: (qmail 83603 invoked by uid 500); 11 Oct 2018 13:54:07 -0000 Mailing-List: contact users-help@unomi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@unomi.apache.org Delivered-To: mailing list users@unomi.apache.org Received: (qmail 83593 invoked by uid 99); 11 Oct 2018 13:54:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Oct 2018 13:54:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E4E3EC06C0 for ; Thu, 11 Oct 2018 13:54:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.97 X-Spam-Level: * X-Spam-Status: No, score=1.97 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_DKIMWL_WL_MED=-0.01] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=mikeghen-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 4beNGULhHUYc for ; Thu, 11 Oct 2018 13:54:05 +0000 (UTC) Received: from mail-pf1-f170.google.com (mail-pf1-f170.google.com [209.85.210.170]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9D34B5F2A9 for ; Thu, 11 Oct 2018 13:54:04 +0000 (UTC) Received: by mail-pf1-f170.google.com with SMTP id f29-v6so4465777pff.5 for ; Thu, 11 Oct 2018 06:54:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mikeghen-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=ywmD+W5hDF/ey2XJ2iKSJQSLUUii550v64DN0M/RWyc=; b=hsTNgvST91w/pGZG+IGxqZw97d21X5wwK3t5/NZhJHkmAtQIa+EusWIIQ1zpk5TcpD 6LTozVEBDNdT6asRNlckmhP6+hf7fxCWq/uGYJAD2zgZ0GhgFM1rPbIQc0JA0PNF+RGQ xBFbr2J9c/vJdetoju0Yi1BbMlNt0GVEUsKtIrwr7/31EYSETbQkQypkBVDbyU3vPFgY Ixq2lwEe8dR3MiOjsrsADFvz5sD6ezaff7z2LL654ahne/ceIWAMZ4GLj654ww1Dpz0s UbceW5+eJl8lnVhLJrFvK4tL/OHBAjU7h6de7f+6g2N7wgE0LLNbTfGvM+mSS0H+j4sm wwQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ywmD+W5hDF/ey2XJ2iKSJQSLUUii550v64DN0M/RWyc=; b=Qz/NGrKsyB3XD9JPy+BYYeoSAZ/1//N/70Udj7O0K6+LGTZEm//vqE7jALbWebs2qs Ul1bstufipDCg/tQ4g+rxPiMj9eM7cqK6WvyG4Tvs3RAewGkGiGk51orslz6R7gxIe0j vn9KRnF0ssN+gxPXRp0yKD22xXJoZ1Pk5dfxv8nMY6HzowGSKoSVTOAWgp+ODEHzXk35 n/yLUSBtgB+bkwaMhPxqfsb9HgvL2Ye93DCJMYTecA18vSmm5r2cmaS7vO7dIt2PseO1 /Hhpqmw6n7ZuCjyRvEAx1jS7NlFejb9wFzQFNhvWtdC/RH7b6Y9DgUPreP7JqoBk/sd7 6j+g== X-Gm-Message-State: ABuFfohRxlLxm4HhSXgTEjFXeosTw6vOIKDrLk19X8O7VNRdhiADKJaX 1vzoLEMec9m8eep26uXaboVyQslqNfUzfsfljQpUYKKS X-Google-Smtp-Source: ACcGV61lUeB9aEhZ/0E8QJjiFD9uQfnoT/29z6TOp8lHPKeI85fYEuyZ7n5AMGWicVu2CaC0mUzjkHkcxnuJc9RpR6E= X-Received: by 2002:a62:41d6:: with SMTP id g83-v6mr1697128pfd.44.1539266042625; Thu, 11 Oct 2018 06:54:02 -0700 (PDT) MIME-Version: 1.0 From: Michael Ghen Date: Thu, 11 Oct 2018 09:53:51 -0400 Message-ID: Subject: Centralizing Customer Data in Unomi To: users@unomi.apache.org Content-Type: multipart/alternative; boundary="000000000000af9a960577f44d3a" --000000000000af9a960577f44d3a Content-Type: text/plain; charset="UTF-8" Hello, I have been exploring Unomi for a few weeks now and think it could help us centralize our customer data. I have a question about what the best way to map our customer data model to Unomi. I understand its elasticsearch on the backend which isn't a system I have a lot of experience, so I'm hoping for some recommendations. The information we have about our customers includes their household composition. For example, a customer is a 65 y/o male living with their wife, we have all the personal information for both people in the household. Another example is a 45 y/o female living with three children, we have all their information as well. We provide services to all the people in the household but there is always a "primary member" identified. My question is, how would these customers be modeled in Unomi? I just wondering what the best way to store the full households information would be given how Unomi works. We want to have actions and rules based on household attributes like "number of children" or "number of people over 65." When we perform actions, we need the name and birthdate of all the people in the household. Right now, we do all of this in Ruby on Rails and use a MySQL database. Respectfully, Mike --000000000000af9a960577f44d3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,=C2=A0

I have been exploring Unom= i for a few weeks now and think it could help us centralize our customer da= ta. I have a question about what the best way to map our customer data mode= l to Unomi. I understand its elasticsearch on the backend which isn't a= system I have a lot of experience, so I'm hoping for some recommendati= ons.

The information we have about our customers i= ncludes their=C2=A0household composition. For example, a customer is a 65 y= /o male living with their wife, we have all the personal information for bo= th people in the household. Another example is a 45 y/o female living with = three children, we have all their information as well.=C2=A0 We provide ser= vices to all the people in the household but there is always a "primar= y member" identified.=C2=A0=C2=A0

My question= is, how would these customers be modeled in Unomi? I just wondering what t= he best way to store the full households information would be given how Uno= mi works. We want to have actions and rules based on household attributes l= ike "number of children" or "number of people over 65."= When we perform actions, we need the name and birthdate of all the people = in the household.=C2=A0

Right now, we do all of th= is in Ruby on Rails and use a MySQL database.

Resp= ectfully,

Mike=C2=A0

--000000000000af9a960577f44d3a--