{sections}

 

{lessontitle}

1.7 File Naming Conventions

Currently there is not a common or standard naming convention for CHPS configuration files; therefore, each RFC may use a different system.

Naming files according to an established pattern makes them easier to locate. Define a naming convention for your RFC’s CHPS configuration files and use it consistently.

gears team

Remember, configuration of CHPS involves several staff members, and inconsistencies can result in miscommunications and errors.

Additionally, consistent use of a naming convention helps with continuity between current CHPS Focal Points and makes it easier for a new focal point to become proficient.

 

Here are some suggestions on keeping various versions of the same configuration file in an understandable format.

1. Add version numbers to XML file names to track the various copies. For example, use the following pattern to name files:

ImportGrids_3.xml

2. Add a default label to differentiate between the copy in use and altered versions of a configuration file. For example:

SpatialDisplay_default.xml

3. Combine the two previous methods:

SpatialDisplay_3_default.xml

Other Suggestions/Techniques

Make a copy of the entire current /Config directory and place it in a uniquely named folder on the CHPS application directory. If disk space is an issue, zip and tar the directory to save space.

Add the date in year-month-day format at the beginning of the archived file names. This allows you to find files quickly by sorting them in numerical order.