Final release for 1.7

git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@5970 9c30dcfa-912a-0410-8fc2-9e0234be79fd

dspace/docs/html/Directories.html

@@ -16,12 +16,28 @@
                                                     </span>
 				    </div>
 				    <div class="pagesubheading">
-					    This page last changed on Nov 06, 2010 by <font color="#0050B2">jtrimble</font>.
+					    This page last changed on Dec 15, 2010 by <font color="#0050B2">tdonohue</font>.
 				    </div>
 
 				    <h1><a name="Directories-DSpaceSystemDocumentation%3ADirectoriesandFiles"></a>DSpace System Documentation: Directories and Files</h1>
 
+<style type='text/css'>/*<![CDATA[*/
+div.rbtoc1292438149327 {margin-left: 0px;padding: 0px;}
+div.rbtoc1292438149327 ul {list-style: none;margin-left: 0px;}
+div.rbtoc1292438149327 li {margin-left: 0px;padding-left: 0px;}
 
+/*]]>*/</style><div class='rbtoc1292438149327'>
+<ul>
+    <li><span class='TOCOutline'>1</span> <a href='#Directories-Overview'>Overview</a></li>
+    <li><span class='TOCOutline'>2</span> <a href='#Directories-SourceDirectoryLayout'>Source Directory Layout</a></li>
+    <li><span class='TOCOutline'>3</span> <a href='#Directories-InstalledDirectoryLayout'>Installed Directory Layout</a></li>
+    <li><span class='TOCOutline'>4</span> <a href='#Directories-ContentsofJSPUIWebApplication'>Contents of JSPUI Web Application</a></li>
+    <li><span class='TOCOutline'>5</span> <a href='#Directories-ContentsofXMLUIWebApplication%28akaManakin%29'>Contents of XMLUI Web Application (aka Manakin)</a></li>
+    <li><span class='TOCOutline'>6</span> <a href='#Directories-LogFiles'>Log Files</a></li>
+<ul>
+    <li><span class='TOCOutline'>6.1</span> <a href='#Directories-log4j.propertiesFile.'>log4j.properties File.</a></li>
+</ul>
+</ul></div>
 
 <h2><a name="Directories-Overview"></a>Overview</h2>
 
@@ -29,7 +45,7 @@
 
 <ul>
 	<li><b>The source directory:</b>:  This is where (surprise&#33;) the source code lives. Note that the config files here are used only during the initial install process. After the install, config files should be changed in the install directory. It is referred to in this document as <em>[dspace-source]</em>.</li>
-	<li><b>The install directory:</b>:  This directory is populated during the install process and also by DSpace as it runs. It contains config files, command-line tools (and the libraries necessary to run them), and usually&#45;<del>although not necessarily</del>&#45;the contents of the DSpace archive (depending on how DSpace is configured). After the initial build and install, changes to config files should be made in this directory. It is referred to in this document as <em>[dspace]</em>.</li>
+	<li><b>The install directory:</b>:  This directory is populated during the install process and also by DSpace as it runs. It contains config files, command-line tools (and the libraries necessary to run them), and usually &#45;&#45; although not necessarily &#45;&#45; the contents of the DSpace archive (depending on how DSpace is configured). After the initial build and install, changes to config files should be made in this directory. It is referred to in this document as <em>[dspace]</em>.</li>
 	<li><b>The web deployment directory:</b>:  This directory is generated by the web server the first time it finds a dspace.war file in its webapps directory. It contains the unpacked contents of dspace.war, i.e. the JSPs and java classes and libraries necessary to run DSpace. Files in this directory should never be edited directly; if you wish to modify your DSpace installation, you should edit files in the source directory and then rebuild. The contents of this directory aren't listed here since its creation is completely automatic. It is usually referred to in this document as <em>[tomcat]/webapps/dspace</em>.</li>
 </ul>
 
@@ -162,9 +178,12 @@ This directory contains administrative files needed for the install process and
 		<li><em>themes/</em> &#45; Contains all out-of-the-box Manakin themes
 		<ul>
 			<li><em>Classic/</em> &#45; The classic theme, which makes the XMLUI look like classic DSpace</li>
-			<li><em>dri2xhtml/</em> &#45; The base theme, which converts XMLUI DRI (Digital Repository Interface) format into XHTML for display</li>
+			<li><em>Kubrick/</em> &#45; The Kubrick theme</li>
+			<li><em>Mirage/</em> &#45; The Mirage theme (see <a href="Mirage Configuration and Customization.html" title="Mirage Configuration and Customization">Mirage Configuration and Customization</a>)</li>
 			<li><em>Reference/</em> &#45; The default reference theme for XMLUI</li>
-			<li><em>template/</em> &#45; A theme template...useful as a starting point for your own custom theme(s)</li>
+			<li><em>dri2xhtml/</em> &#45; The base theme template, which converts XMLUI DRI (Digital Repository Interface) format into XHTML for display. See <a href="XMLUI Base Theme Templates (dri2xhtml).html" title="XMLUI Base Theme Templates (dri2xhtml)">XMLUI Base Theme Templates &#40;dri2xhtml&#41;</a> for more details.</li>
+			<li><em>dri2xhtml-alt/</em> &#45; The alternative theme template (used by Mirage Theme), which also converts XMLUI DRI (Digital Repository Interface) format into XHTML for display. See <a href="XMLUI Base Theme Templates (dri2xhtml).html" title="XMLUI Base Theme Templates (dri2xhtml)">XMLUI Base Theme Templates &#40;dri2xhtml&#41;</a> for more details.</li>
+			<li><em>template/</em> &#45; An empty theme template...useful as a starting point for your own custom theme(s)</li>
 			<li><em>dri2xhtml.xsl</em> &#45; The DRI-to-XHTML XSL Stylesheet. Uses the above 'dri2xhtml' theme to generate XHTML</li>
 			<li><em>themes.xmap</em> &#45; The Theme configuration file. It determines which theme(s) are used by XMLUI</li>
 		</ul>
@@ -193,10 +212,14 @@ This directory contains administrative files needed for the install process and
 <td class='confluenceTd'> <b>What's In It</b> </td>
 </tr>
 <tr>
-<td class='confluenceTd'> <em>[dspace]/log/dspace.log</em> </td>
+<td class='confluenceTd'> <em>[dspace]/log/dspace.log.yyyy-mm-dd</em> </td>
 <td class='confluenceTd'> Main DSpace log file. This is where the DSpace code writes a simple log of events and errors that occur within the DSpace code. You can control the verbosity of this by editing the <em>[dspace-source]/config/templates/log4j.properties</em> file and then running "<em>ant init_configs</em>". </td>
 </tr>
 <tr>
+<td class='confluenceTd'> <em>[dspace]/log/cocoon.log.yyyy-mm-dd</em> </td>
+<td class='confluenceTd'> Apache Cocoon log file for the XMLUI. This is where the DSpace XMLUI logs all of its events and errors. </td>
+</tr>
+<tr>
 <td class='confluenceTd'> <em>[tomcat]/logs/catalina.out</em> </td>
 <td class='confluenceTd'> This is where Tomcat's standard output is written. Many errors that occur within the Tomcat code are logged here. For example, if Tomcat can't find the DSpace code (<em>dspace.jar</em>), it would be logged in <em>catalina.out</em>. </td>
 </tr>
@@ -273,7 +296,7 @@ log4j.logger.org.dspace=INFO,A1</pre>
 				<td height="12" background="https://wiki.duraspace.org/images/border/border_bottom.gif"><img src="images/border/spacer.gif" width="1" height="1" border="0"/></td>
 			</tr>
 		    <tr>
-			    <td align="center"><font color="grey">Document generated by Confluence on Nov 06, 2010 19:27</font></td>
+			    <td align="center"><font color="grey">Document generated by Confluence on Dec 16, 2010 16:47</font></td>
 		    </tr>
 	    </table>
     </body>