Bug
Order significant on import of existing topics
Issue description
When existing topics are imported, the order is significant in getting all the information imported.
Here is the exact scenario:
* Let's assume there is three subjects in the store: a, b, c.
* In the topic map M which is imported these subjects are called (a,1), 2, 3.
* Subject (a,1) has a name N1 which is scoped by 2.
* Since Subject (a,1) is already known in the store, the information from M is added immediately. The name N1 is posted to (a,1) with the scope 2, but 2 does not exist yet, so the scoping statement is no stored.
_Legend:
(a,1) means that the proxy knows of two ways of referring to its subject: a and 1._
Developer comments
I changed the newchildren method in Topic_map.php, so that no matter whether or not a topic is known, the first thing that happens is that a stripped version of the topic (without names and occurrences) is put or posted to the store. This way the identity statements are imported first. Then after all associations have been created, all topics are put again. Only in the last step the names for the known items are created and therefore all the scoping information on the names is created correctly.
I created a test case for this issue and ran regression tests on the server.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.