Dear all, Can somebody comment on the role & purpose of "mergenode" in Resource Graphs.
In the documentation ( http://arches3.readthedocs.org/en/latest/arches-data/#resource-graphs ) it just says: mergenode: defines the upstream node that occurs one time (and only one > time) within a given resource instance. In most cases, that node is the one > that represents the resource itself. When inspecting an existing graph. e.g. ACTOR.E39 I can see that the mergenode depicts the root of "useful" sub-graphs, i.e. for PLACE, APPELATION and ARCHES_EVENT_PHASE. But what are actually the consequences of adding mergenodes - or leaving them out? Is it used and/or required for specifiying "required" and "unique" (""one time (and only one time)" ) ? (But this would mean, that only a SINGLE ARCHES_EVENT_PHASE can be assigned to a ACTOR, which seems odd ?) Why do some sub-graphs have a mergenode, while others just "merge" with the root-node of the whole Resource Graph ? (e.g. BEGINNING_OF_EXISTENCE_TYPE.E63) yours puzzled :-) Hannes -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
