The following directory structure and file-naming convention plan is suggested to meet the following criteria:
Should the files be moved to another server, directory structure can move with it. Therefore, DOS file naming conventions must apply.
Most information is promoted to users by listing The URL. This includes the complete directory listing of the document to be reached. Long URL's with multiple levels of directories are harder to promote. Which would you rather try to use:
URL: http://www.nr.ky.us/nrepc/water/waterw.htm
Or:
URL: http://www.nr.ky.us/nrepc/dep/water/pgmpln/edu/106j/waterw.htm
For example, the subdirectory for Division of Water could be EP/DOW Or /water. When giving the URL to users, just saying "water" makes the Location more memorable.
Each organizational unit controls its own directory and subdirectories. in the same fashion that each internet domain controls it's own addressing. Special directories may be added as needed by webcore for projects that do not fit organizational patterns
In theory, you can have over 256 subdirectories in a single directory, but you would soon loose track. The suggested maximum is 24 (a screenful when you hit the DIR command.) This will allow skipping organizational rungs in directory control hierarchy.
The specific directories can be changed at whim, but a convention will aid in development. Before a directory can be established on the server, and files moved into the directory, a manager for that directory must be identified. The default is to have the webmaster or server administrator manage the directory files.
A program's web developer will be assigned a subdirectory to work within by the webmaster, server administrator, or webcore developer for his/her division. The server administrator will create the directory once the files have been approved for release by normal division and cabinet review channels.
Pre-assigned directories will facilitate link construction and testing. Links to files within the subdirectory can use "virtual" addressing, a simpler link address. Links to files outside that directory would use absolute addressing. Therefore, HTML files would not have to be rewritten if the entire directory is moved to another machine.
NREPC/SEC Secretary's Office NREPC/LAW Office of Legal Services NREPC/ADMIN Administrative Services NREPC/COM Communications NREPC/GIS Geographic Information NREPC/DATA Data Processing NREPC/EPCOM/ EP Commissioners Office NREPC/WATER/ Division of Water NREPC/WASTE/ Division of Waste Management NREPC/AIR/ Division of Air Quality NREPC/LAB/ Division of Environmental Services NREPC/NRCOM/ NR Commissioners Office NREPC/ENERGY/ Division of Energy NREPC/FOREST/ Division of Forestry NREPC/CONSERVE/ Division of Conservation NREPC/NATURE/ Nature Preserves Commission NREPC/MINECOM DSMRE Commissioners Office NREPC/ABANDON Division of Abandoned Lands NREP/MINENFOR Division of Enforcement NREPC/MINEPERM Division of Permits NREPC/UST Underground Storage Tank Authority NREPC/BLANTON (Existing Blanton Forest Directory) NREPC/EQC (Existing EQC) NREPC/KRA (Existing KY River Authority)
With that in mind, Here's how Division of Water plans to implement its directory structure
NREPC/WATER Directory Ownership Technical Manager; Ken Cooke: Content Manager; Maleva Chamberlain Subdirectory Organizational Unit Developer/Owner ================ =================== =========== WATER/DIRECTOR Directors Office M. Chamberlain WATER/PLAN Planning Section B. Stone WATER/ADMIN Administration Section K. Cooke WATER/WATCH Water Watch Program K. Cooke WATER/ECOLOGY Ecological Support M. Jones WATER/RIVERS Wild Rivers Program M. Jones WATER/QUALITY 401 Certification TBA WATER/STANDARD Standards and Specs. S. Hankla WATER/NONPOINT Nonpoint Source Section D. Rome WATER/PERMITS KPDES Branch J. Zeigler WATER/ENFORCE Enforcement Section TBA WATER/TRAIN Certification Killis Sinkhorn WATER/RESOURCE Water Resources Section Leon Smothers WATER/DAM Dam Safety Section J. Marchant WATER/FLOOD NFIP Program TBA WATER/GRANT Facilitites Construction J. Roland WATER/GROUND Groundwater B. Yarnell WATER/WELL Groundwater B. Yarnell WATER/FIELD Field Operations S. Mello WATER/DRINK Drinking Water Vicki Ray Of course, Subdirectories may be added as needed.
If a server administrator wants to sort out all the files belonging to the Water Watch program ww, a file sort by name will put them all together. With this system, each subdirectory can have up to 726 file categories
The manager for a particular directory can assign a file-name system to the developers working within it or select one by convention in cooperation with others working within that directory.
this file management convention will allow independent development with a management structure in place for Webcore and the Webmaster to effectively monitor and control file placement and updating.
As an example, Bill Yarnell could start developing files already knowing what directory his files will be housed in no matter what machine we move it to. Files he develops now will have the following URL:
