Changes between Version 2 and Version 3 of DirHierarchy


Ignore:
Timestamp:
07/30/07 17:38:09 (10 years ago)
Author:
Nicolas
Comment:

Minor formatting

Legend:

Unmodified
Added
Removed
Modified
  • DirHierarchy

    v2 v3  
    1818}}}
    1919
    20 This takes a name of the input file and the absolute path of the root of the download hierarchy (typically the download_dir element from [ProjectOptions config.xml]) and returns the absolute path of the file in the hierarchy. Generally make_directory_if_needed should be set to true: this creates a fanout directory if needed to accommodate a particular file.  Secondly, your validator and assimilator should call
     20This takes a name of the input file and the absolute path of the root of the download hierarchy (typically the `download_dir` element from [ProjectOptions config.xml]) and returns the absolute path of the file in the hierarchy. Generally `make_directory_if_needed` should be set to true: this creates a fanout directory if needed to accommodate a particular file.  Secondly, your validator and assimilator should call
    2121
    2222{{{
     
    3333}}}
    3434
    35 dir_hier_move moves all files from src_dir (flat) into dst_dir (hierarchical with the given fanout). dir_hier_path, given a filename, prints the full pathname of that file in the hierarchy.
     35`dir_hier_move` moves all files from `src_dir` (flat) into `dst_dir` (hierarchical with the given fanout). `dir_hier_path`, given a filename, prints the full pathname of that file in the hierarchy.
    3636
    3737== Transitioning from flat to hierarchical directories ==
     
    4545
    4646 This causes the file deleter to check both old and new locations.
    47  * Use dir_hier_move to move existing upload files to a hierarchy.
     47 * Use `dir_hier_move` to move existing upload files to a hierarchy.
    4848 * Start the project, and monitor everything closely for a while.
    4949