$Organizing Data Areas5

HFRD Hypertext Services - Technical Overview

p [next] [previous][contents]
"

8 - Organizing Data Areas




G This section deals with the provision of physical file space for HFRD Ghypertext-related data, and the integration of that within the logical )organization of the HFRD hypertext data. 

I The logical organisation of served data is largely hierarchical, and is achieved via two mechanisms. 

    A
  1. The natural hierachy provided by a hierarchical file system.K
  2. The logical hierarchy possible using rules within the mapping file to Dplace disparate physical areas into a single logical structure (see 95 - HTTPd Mapping Rules). 


E HFRD has a single section of the file system for the core hypertext Nenvironment files, such as the Division home page, help areas, documentation, 0etc., it can be accessed using the logical area BHYPERDATA:[000000]. Physically integrated with this are Kdirectories providing data storage for specific groupings of data, such as OCEAC minutes, adminstration announcements, etc. Physically distinct areas are Jalso logical grouped into the hypertext environment, areas such as the IE group area, JFAS minutes, etc. 

H The reason for some areas being physically distinct are for legitimate Ophysical reasons (e.g. the area can best be hosted on a group-local disk), for Khistorical reasons (e.g. the area existed before any hypertext environment Hexisted) or for reasons of convenience (e.g. lets put this where access 6controls already allow the maintainers to manage it). 

C The reasons for an area being physically integrated with the core Lhypertext data area can be legitimate (e.g. there is really nowhere else it Oreasonably belongs), convenience (e.g. lets quickly put it here) or by logical Knecessity (it really does below as part of the core hypertext enviroment). 

Guidelines



F In general, only hypertext enviroment files need to go into the core Mphysical hypertext file system. All other groupings should, if possible, be Odecentralised into the portion of the file system they represent and logically Jplaced in the hypertext area using rules in the mapping file. That is, a Ogiven project's hypertext files should be located in the project's part of the Mfile system. If it doesn't have any then it may be a candidate for location in the core area. 

D When locating a hypertext area in a physically distinct area it is Hpossible the managers of that data will already have the correct access Lcontrols. If locating an area in the core hypertext environment it will be Nnecessary to give the manager ownership of the directory area, or provide ACL *access if multiple managers are involved. 

I When locating a hypertext area in a physically distinct area it will be :necessary to update the mapping file with a new rule (see d5 - HTTPd Mapping Rules). If located within the core hypertext area &the rules do not need to be adjusted. 




p [next] [previous][contents]