Here is a hierarchical display of the contents of the EDGE site. In order to understand this image, it is easiest to begin at the far right of the image, assuming you are a member of one or more projects.
Each project has a repository, and the web site is one element contained inside of the repository. Projects can also store other information in their repository, that has nothing to do with the web site. For example, your team may choose to use the repository to provide version control of your CAD drawings, and simulation results.
Within the repository established for each project, the EDGE site administrator has created a web space for each team. Anything that you place within the web space area of your repository can be rendered by the EDGE web site into an internet browser, as long as you follow the site conventions on material content. Anyone with Guest access to your project can view the entire contents of your web space.
Inside of your Web Space is a subdirectory call public. Any contents that a project Editor places in public may be Observed by anyone who has logged into the EDGE web site. The public contents should never contain confidential or proprietary information.
Anything contained inside of the web space, but NOT within the public subdirectory is considered to be accessible through a browser, but is only readable by individuals who have at least a Guest level of access. The EDGE adminisitrator creates a private subdirectory, as a convenient places for the memebrs of a team to host a web site for their internal efforts, but not for view by the general public.
All access control on the EDGE web site is controlled on a project by project basis. For example, you may be an Observer (public folder read access) of one project, a Guest (private folder read access) of a second project, and an Editor (write access) of a third project.
An observer of a project has chosen to list this project in their personal side bar along the left hand side-bar of their browser. An observer can only view content located in the public portion of the web site within the repository.
A guest has the ability to view all contents of the project repository. Guests can read the public and private areas of the web site, and can read the other contents of the repository that have been placed their by the team.
An editor has all of the access of the Guest, PLUS, an editor can create, or edit (e.g. write privileges) the contents of the project.
The curator of a project can control which versions of the contents are displayed to public view by Observers. The curator of senior design projects is typically the faculy member who is guiding the design team.
The administrator of a project has the ability to grant access control privileges to other people. If you are not currently a guest or an editor of a particular project, you may ask the administrator to grant you that access. The administrator is responsible for the security of the project.
Any information that is About a project is contained in a database, separate from the project's repository. You can review the project title, track affiliation, starting and ending terms, and a brief description at the "About" node for each project.
The Home node of a project is the place that visitors to the project will begin. The editors of a project can modify the home node and add links to other information that they wish to share.
Each EDGE server has a limited number of "tracks" to help organize projects at the very top level. One EDGE server may be organized by departments, such as "Mechanical Engineering" and "Electrical Engineering," etc. Another EDGE server may be organized by society inspired track such as Transportation, Energy, Communications and Healthcare." The tracks of an EDGE server are used to provide a top-level organization view of the content of the server.
A normal project has a publicly-accessable /web/public directory in its repository. The curator of a project controls what is displayed in that public web space through the project's information (the "edit mode" allows curators to view and change the hidden information).
A project starts life with a public revision of -1, which means that there is no publicly available information (although it is still available for guests). When the public web space is populated (with wiki pages and files) by the project's members, the curator can verify that a particular revision is suitable for public viewing and set the project's "public revision".
Public Revision Cases:
The public web space of the project is only viewable by guests
Any user can view that single revision of the public web space
The public view is always the latest revision of the public web space
NOTICE: This is dangerous in that any editor may change the public view without approval by the curator.