<div>On Wed, Jul 20, 2011 at 17:02, Martin Klapetek <<a href="mailto:martin.klapetek@gmail.com">martin.klapetek@gmail.com</a>> wrote:</div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Btw. when reading the PIMO guide [3], it says on page 31 to copy all identifiers. Do I understand it correctly that it should copy all identifiers from new NCO:PersonContact into PIMO:Person (and should I do that too)? This seems like an unnecessary data duplication. <br>
identifiers:<br>Copying the email addresses and other identifiers to the pimo:Person will help you identifying arbitrary data. Given you have some new data coming into the system, you may want to check if its already known.<br>
("is this "Dirk" guy someone we know?). This is the "Check identifiers" step In Section 11.1 on page 30, where you check if you find a Pimo:Person that represents the resource you are working with.<br>
This is why it would be good to copy all identifiers over to the pimo:Person, to speed up lookups later. <br>its data duplication, but it doesn't matter. The key point here is: you want to be veeery quick when identifying if any new data does mean something to you. And optimizing this read-accesses is always good. Say you read 100 emails a day, roughly 10.000 a year. Quickly checking them against the 1000 contacts you have is nicer if the identifying information is all in one place (that would be the pimo:Persons). </blockquote>
<div><br></div><div>Actually after giving it some thought, it is not a good idea to copy data into PIMO:Person. Imagine a use case, where you accidentally merge NCO:PersonContact with PIMO:Person, which is not supposed to be there. Then it's very hard and problematic to un-merge it. If you add it just as a grounding occurence, it's easy to just remove this relation.</div>
<div><br></div><div>Or is there any good way how the un-merge can be done?</div>