Locations|Split Registry entry
Used to enable the Split Location facility.The Split Location facility is used to manage the location of multi-part objects. It works by tracking the location of leaf parts (a leaf part is one which does not have any child parts). Only leaf objects may be relocated. When a relocation takes place the System propagates the movement up the parts hierarchy, updating the location of each parent provided that all children are at the same location. If all the children are not in the same location, the parent record's location is marked as Split
.
With the Parts tab in the Catalog
Consider the following parts hierarchy:
Wedgwood Crockery Collection
(Split)
|
+---------------------+----------------------+
| | |
Piccadilly Collection Tower Collection Man on the Moon Collection
(Rm 1) (Rm 2) (Split)
| | |
+-----+-----+ +----+----+ +----+----+
| | | | | | |
Plate Cup Saucer Plate Milk Jug Plate Cup
(Rm 1) (Rm 1) (Rm 1) (Rm 2) (Rm 2) (Rm 3) (Rm 4)
The locations are shown in brackets in bold. Since all the Piccadilly Collection
is stored at the one location, the collection itself can be found there (and hence it has the same location). The record for the Piccadilly Collection
is thus not marked as split. The same applies for the Tower Collection
. The Man on the Moon Collection
however has parts in different locations (Rm 3 and Rm 4) and therefore the record for the collection is marked as split. The Wedgwood Crockery Collection
is also marked as split since its parts (Piccadilly Collection
, Tower Collection
and Man on the Moon Collection
) are not all in the one location.
The Split Location facility is enabled with this Registry entry.
Usage
Key | System |
---|---|
Key 1 | System |
Key 2 | Setting |
Key 3 | Locations |
Key 4 | Split |
Value | locationirn |
System | Setting | Locations | Split | locationirn |
where:
locationirn | is the IRN of a Locations record designated as the Split location. This is a faux location, that is a Locations record with a Level 1 location of |
When splitting is enabled EMu will not allow the location of any non-leaf part to be updated. The location information on the Location tab will be read-only and the Bulk Relocation tool will be unable to relocate a non-leaf part. When a leaf part's location is changed and saved, EMu automatically updates the location of all parent objects, splitting or merging as required. A merge occurs when all leaf parts are at the same location. In the example above if the Plate
object is moved to Rm 4, the location of Man on the Moon Collection
will be updated to Rm 4 since both the Plate
and Cup
can now be found at the same location.