Changes between Version 3 and Version 4 of DC3OutputStagePolicyDesign


Ignore:
Timestamp:
02/12/2009 05:01:49 PM (11 years ago)
Author:
ktl
Comment:

Improve somewhat. Still need to add information on Persistence sub-policy.

Legend:

Unmodified
Added
Removed
Modified
  • DC3OutputStagePolicyDesign

    v3 v4  
    22'''updated: Feb 11, 2009''' 
    33 
    4 == !OutputStage Policy File Componenets == 
     4== !OutputStage Policy File Components == 
    55 1. !AdditionalData: 
    6    * type: string 
    7    * description: ? 
     6   * type: string array 
     7   * description: allows clipboard values to be given names to be used as parameters in pathnames or by Formatters. Form is <name>=<clipboardKey>. 
    88 2. !RunMode: 
    99   * type: string 
     
    1212 3. !OutputItems: 
    1313   * type: policy 
    14    * description: list of items to persist 
     14   * description: items to persist 
    1515   * sub-policies: 
    1616     1. <itemName>: 
    1717       * type: policy 
    18        * description: replace <itemName> with the name you would like to assign to this output item. multiple item policies may be defined within the !OutputItems policy array. 
     18       * description: replace <itemName> with the name you would like to assign to this output item. multiple item policies may be defined within the !OutputItems policy. 
    1919       * sub-policies:          
    2020         1. !StoragePolicy: 
    2121           * type: policy 
    22            * description: specifies how and where to persist this item. Multiple !StoragePolicy can be defined for a single item. 
    23            * sub-policies: 
     22           * description: specifies how and where to persist this item. Multiple !StoragePolicy can be defined for a single item; they are used in sequence. 
     23           * components: 
    2424             1. Storage: 
    2525               * type: string 
     
    2828             2. Location: 
    2929               * type: string 
    30                * description: specifies '''where''' to perist the item. Can include %{...} parameters which will be filled in by the stage using the "!AdditionData" values. Built in %{...} operands include: 
     30               * description: specifies '''where''' to perist the item. Should be a ''logical'' location, not a ''physical'' one. Can include %{...} parameters which will be filled in by the stage using the "!AdditionalData" values. Built in %{...} operands include: 
    3131                 * %{runId} 
    3232                 * %{sliceId}