From users-return-122-archive-asf-public=cust-asf.ponee.io@unomi.apache.org Sun Sep 8 06:22:34 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id E19D118062C for ; Sun, 8 Sep 2019 08:22:33 +0200 (CEST) Received: (qmail 92261 invoked by uid 500); 8 Sep 2019 06:22:35 -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 92252 invoked by uid 99); 8 Sep 2019 06:22:34 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Sep 2019 06:22:34 +0000 Received: from mail-ot1-f50.google.com (mail-ot1-f50.google.com [209.85.210.50]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id DD2385A53 for ; Sun, 8 Sep 2019 06:22:32 +0000 (UTC) Received: by mail-ot1-f50.google.com with SMTP id o101so9520025ota.8 for ; Sat, 07 Sep 2019 23:22:32 -0700 (PDT) X-Gm-Message-State: APjAAAUAWf9e14g0o2DiDHfhG7EicB0TUmeEjnM3/dGQtb4X1XPHDvod heZdYnhrmZ0sAwOwMXxG/w4uVmM2/JZxB0q6aGGgiw== X-Google-Smtp-Source: APXvYqzfgYhLkSU8Z+HiO0h/+HnVK69MjgVSvz2a5H6wUxfparJS9rRZ59OJHmKWKfUP+5S9oeVnz8TjvjlZvtpvpOc= X-Received: by 2002:a9d:6b97:: with SMTP id b23mr14767130otq.267.1567923752224; Sat, 07 Sep 2019 23:22:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Serge Huber Date: Sun, 8 Sep 2019 08:22:22 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CDP best practices To: users@unomi.apache.org Content-Type: multipart/alternative; boundary="000000000000495c95059204b2af" --000000000000495c95059204b2af Content-Type: text/plain; charset="UTF-8" Hello Jeroen, Thanks for the kind words about the project, they are highly appreciated. Sorry I couldn't answer earlier I've been very busy with the preparations for ApacheCon next week. Unomi has a "open" schema in terms of profiles and other objects. For example you can define profile properties and register them if you need to keep track of them but you could also set any property directly in the profile even without such a registration (registration is mostly useful when building UIs to query the list of available properties and metadata such as their type, etc...). For example, in my company's product based on Unomi (Jahia Marketing Factory), we can even define new properties using a UI. All that UI does is then call Unomi's REST API to register the properties. One thing you should be aware of: because of ElasticSearch restrictions, you cannot (currently) change the type of a property, so while developing you might have to reset your ElasticSearch data until you have the proper model. Apart from what we've done at my company I'm not aware of any other resources on this topic, but I'd love to know more about what you're trying to achieve so that I could answer your questions. Best regards, Serge... On Fri, Sep 6, 2019 at 3:51 PM Jeroen van der Wal wrote: > Dear Unomians, > > Thank you for sharing this nice piece of software with the world. We are > currently working with a retail customer where Unomi would be a perfect > candidate as the customer profiling engine. > > Reading through the documentation and the Oasis CDP spec gives us a good > overview of how we can put the Unomi to work. The biggest challenge we face > right now is building a good catalog of topics and profile attributes. Is > there any reference material on this subject? Maybe some sample > implementations? We would like to prevent re-inventing the wheel ;-) > > Many thanks, > > Jeroen van der Wal > Incode Amsterdam > +31 655874050 > --000000000000495c95059204b2af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Jeroen,=C2=A0

Thanks for the kind= words about the project, they are highly appreciated. Sorry I couldn't= answer=C2=A0earlier I've been very busy with the preparations for Apac= heCon next week.

Unomi has a "open" sche= ma in terms of profiles and other objects. For example you can define profi= le properties and register them if you need to keep track of them but you c= ould also set any property directly in the profile even without such a regi= stration (registration is mostly useful when building UIs to query the list= of available properties and metadata such as their type, etc...). For exam= ple, in my company's product based on Unomi (Jahia Marketing Factory), = we can even define new properties using a UI. All that UI does is then call= Unomi's REST API to register the properties.

= One thing you should be aware of: because=C2=A0of ElasticSearch restriction= s, you cannot (currently) change the type of a property, so while developin= g you might have to reset your ElasticSearch data until you have the proper= model.

Apart from what we've done at my compa= ny I'm not aware of any other resources on this topic, but I'd love= to know more about what you're trying to achieve so that I could answe= r your questions.

Best regards,
=C2=A0 S= erge...=C2=A0

On Fri, Sep 6, 2019 at 3:51 PM Jeroen van der Wal <jcvanderwal@apache.org> wrot= e:
Dear Unomians,

Thank you for sharing this nice piece= of software with the world. We are currently working with a retail custome= r where Unomi would be a perfect candidate as the customer profiling engine= .

Reading through the documentation and the Oasis = CDP spec gives us a good overview of how we can put the Unomi to work. The = biggest challenge=C2=A0we face right now is building a good catalog of topi= cs and profile attributes. Is there any reference material on this subject?= Maybe some sample implementations? We would like to prevent re-inventing t= he wheel ;-)

Many thanks,

Jeroen van der Wal
Incode=C2=A0Amsterdam
+31 6= 55874050
--000000000000495c95059204b2af--