[deepamehta-users] Address Model in DM Webclient

Juergen Neumann j.neumann at junes.eu
Wed Feb 25 17:55:43 CET 2015

Hi Jörg, 

thanks, I will try it. Is there a way to check through the REST API what
kind of AssocType is currently defined between AddressEntry and
AddressType. I ould like to implement an automatic check to see if I can
use the ref_ID or not.

Thank you very much in advance!


Am Montag, den 23.02.2015, 14:11 +0100 schrieb Jörg Richter:
> Hi JuergeN,
> oh, that's cool you have implemented an address equality check already!
> Yes, for your import-via-REST use case you can change that association (between the Address Entry and Address types) to Aggregation Definition. It will work. Just put the ref_id: or ref_uri: prefix in your POST request to refer to an existing Address topic. The Address topics will be shared between several Persons then.
> Also editing a Person in the detail panel will work. Just be aware of semantic side-effects: editing one person's address will change the address for all involved persons as well. (Possibly you have to reload to clear the browser cache in order to see the effect.) In case you want deliberately avoid that side effect you can delete the Aggregation (between the Address Entry and the Address) before editing a particular Person. In the detail panel you can then enter a new independent Address for that Person.
> Cheers,
> Jörg
> On Feb 21, 2015, at 19:03, Juergen Neumann wrote:
> > Hi Jörg,
> > 
> > I understand the general apsect of the specific issue. In my case I want
> > to create new persons via the REST API. I have implemented a check if an
> > address topic alread exists. If so, I want to reassign this very address
> > to the newly created person. 
> > 
> > So my question is, if I change the assoc type from composition def to
> > aggregation def for the entire address, will it break anyting (in the
> > webclient) or can I just try it, to see how it goes ...
> > 
> > Thx,
> > 
> > JuergeN 

More information about the users mailing list