By default, the Global Collaboration Framework replicates documents between folders with identical paths in all of the collaborating vaults. In situations where the vaults must use different folder structures, for example, due to different Field-Path definitions, you can configure path transformations to replicate documents to folders with different paths in each vault.
You configure path transformations by specifying how the levels of a common global Field-Path definition correspond to the folder path levels in each vault. The global Field-Path definition can be actually defined in one of the collaborating vaults or it can be logical only and not actually defined in any of the vaults. The global Field-Path definition is simply a common point of reference used by all of the vaults similar to the common global identifier described in Mapping security roles. In this way, each vault only needs to specify once how its structure relates to the global Field-Path definition instead of how its structure relates to every other potential vault with which it collaborates.
Path transformations are configured using two settings, IncomingPathTransformation and OutgoingPathTransformation. The OutgoingPathTransformation setting specifies how the path levels of the local vault correspond to the global Field-Path definition. The IncomingPathTransformation setting specifies how the path levels of the global Field-Path definition correspond to the local vault paths.
The path transformation settings can include several element types:
For example, assume two vaults with the following Field-Path definitions:
Vault 1: <Location>\<System>\<Contractor>\<Project>
Vault 2: <Contractor>\<Project>\<Location>\<System>
Also assume a global Field-Path definition of <Project>\<Contractor>\<Location>\<System>. By assigning numbers to each level of the path (<Project> = 1, <Contractor> = 2, <Location> = 3, and <System> = 4), we can specify how that path should be transformed by the Meridian Enterprise import processor so that documents are imported into the correct folders in both vaults. When configuring the transformations in the settings, each element except literal folder names must be enclosed in braces {}. The resulting IncomingPathTransformation settings would look like this:
Vault1: \{3}\{4}\{2}\{1}
Vault2: \{2}\{1}\{3}\{4}
Property names are specified using the syntax {<PropertySet>.<PropertyName>}.
For example:
\{3}\{4}\{2}\{Custom.MyProperty}
Briefcase property names are specified using a similar syntax {<PROPERTYNAME>}. The property name must be upper case and must be specified in the briefcase property mapping configuration.
For example:
\{3}\{4}\{2}\{MYPROPERTY}
Literal folder names require no special syntax.
For example:
\{3}\{4}\{2}\Docs
Note Path transformations are only supported by Meridian Enterprise 2011 and higher when using custom briefcase formats. For more information about custom briefcase formats, see the BlueCielo Meridian Enterprise Configuration Guide.
To configure path transformations:
For example, the settings for the preceding scenario would look like:
Vault1:
OutgoingPathTransformation=\{4}\{3}\{1}\{2}
IncomingPathTransformation=\{3}\{4}\{2}\{1}
Vault2:
OutgoingPathTransformation=\{2}\{1}\{3}\{4}
IncomingPathTransformation=\{2}\{1}\{3}\{4}
The asterisk character (*) can be used as a wildcard to represent all subsequent levels. For example, the Vault2 settings can also be specified as:
OutgoingPathTransformation=\{2}\{1}\{3*}
IncomingPathTransformation=\{2}\{1}\{3*}
Notes