diff --git a/dspace/docs/convert2DB.sh b/dspace/docs/convert2DB.sh
index d35bdb6876..7d28a17eec 100755
--- a/dspace/docs/convert2DB.sh
+++ b/dspace/docs/convert2DB.sh
@@ -5,7 +5,9 @@
 # Developed On Ubuntu Hardy Heron, you'll need at least:
 # apt-get install herold docbook-utils docbook2x xsltproc docbook-xsl dbdoclet
 
-VERSION="1.5.1"
+if [ "a$DS_VERSION" == "a" ]; then
+  DS_VERSION="1.5.2"
+fi
 
 DBxml="docbook"
 HTMLfinal="html"
@@ -45,7 +47,7 @@ if [ $haveDB -lt 1 ]; then
     filelist=`ls *html`
 	cd ..
 
-	title="DSpace $VERSION Manual"
+	title="DSpace $DS_VERSION Manual"
 
 	# The initial raw html to db conversion:
 	for file in $filelist; do
@@ -93,7 +95,7 @@ if [ $haveDB -lt 1 ]; then
 
 <book>
   <bookinfo>
-    <title>DSpace $VERSION Manual</title>
+    <title>DSpace $DS_VERSION Manual</title>
     
     <author>
       <surname>The DSpace Foundation</surname>
@@ -236,7 +238,7 @@ XSLTP=" -param body.start.indent 0pt \
 if [ "a$FOP_HOME" == "a" ]; then
     FOP_HOME=/usr/local/share/fop-0.94
 fi
-java -Xmx128m -Dfop.home=$FOP_HOME -jar $FOP_HOME/build/fop.jar -xml $DBxml/book.xml -xsl $xslprint -pdf $PDFfinal/DSpace-$VERSION.pdf $XSLTP
+java -Xmx128m -Dfop.home=$FOP_HOME -jar $FOP_HOME/build/fop.jar -xml $DBxml/book.xml -xsl $xslprint -pdf $PDFfinal/DSpace-$DS_VERSION.pdf $XSLTP
 
 # HTML it using XSL
 if [ ! -d $HTMLfinal ]; then
@@ -290,7 +292,7 @@ please feel free to add them to the wiki page below.  You may also email suggest
  //--> \
  </script>.
 \$a\
-</p><br/><iframe src="http://wiki.dspace.org/index.php/AnnotateDoc_$VERSION_${file/.html/}" width="100%" height="600"/></body></html>
+</p><br/><iframe src="http://wiki.dspace.org/index.php/AnnotateDoc_$DS_VERSION_${file/.html/}" width="100%" height="600"/></body></html>
 EOF
     done
 fi
diff --git a/dspace/docs/docbook/DRISchemaReference.xml b/dspace/docs/docbook/DRISchemaReference.xml
index 68215f14e9..400995147d 100644
--- a/dspace/docs/docbook/DRISchemaReference.xml
+++ b/dspace/docs/docbook/DRISchemaReference.xml
@@ -29,7 +29,7 @@
       <section remap="h3">
         <title>Themes</title>
         <para>A Theme is a collection of XSL stylesheets and supporting files like images, CSS styles, translations, and help documents. The XSL stylesheets are applied to the DRI Document to covert it into a readable format and give it structure and basic visual formatting in that format. The supporting files are used to provide the page with a specific look and feel, insert images and other media, translate the content, and perform other tasks. The currently used output format is XHTML and the supporting files are generally limited to CSS, images, and JavaScript. More output formats, like PDF or SVG, may be added in the future.</para>
-        <para>A DSpace installation running Manakin may have several Themes associated with it. When applied to a page, a Theme determines most of the pageís look and feel. Different themes can be applied to different sets of DSpace pages allowing for both variety of styles between sets of pages and consistency within those sets. The xmlui.xconf configuration file determines which Themes are applied to which DSpace pages (see the <ulink url="configure.html#xmlui-configure">Configuration and Customization chapter</ulink> for more information on installing and configuring themes). Themes may be configured to apply to all pages of specific type, like browse-by-title, to all pages of a one particular community or collection or sets of communities and collections, and to any mix of the two. They can also be configured to apply to a singe arbitrary page or handle.</para>
+        <para>A DSpace installation running Manakin may have several Themes associated with it. When applied to a page, a Theme determines most of the pageís look and feel. Different themes can be applied to different sets of DSpace pages allowing for both variety of styles between sets of pages and consistency within those sets. The xmlui.xconf configuration file determines which Themes are applied to which DSpace pages (see the <link linkend="docbook-configure.html-xmlui-configure">Configuration and Customization chapter</link> for more information on installing and configuring themes). Themes may be configured to apply to all pages of specific type, like browse-by-title, to all pages of a one particular community or collection or sets of communities and collections, and to any mix of the two. They can also be configured to apply to a singe arbitrary page or handle.</para>
       </section>
       <section remap="h3">
         <title>Aspect Chains</title>
diff --git a/dspace/docs/docbook/appendix.xml b/dspace/docs/docbook/appendix.xml
index 46ac23fc9f..b3a77a65c1 100644
--- a/dspace/docs/docbook/appendix.xml
+++ b/dspace/docs/docbook/appendix.xml
@@ -1,9 +1,8 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Appendices</title>
+    <title><anchor id="docbook-appendix.html"/>DSpace System Documentation: Appendices</title>
     <section remap="h2">
-      <title><anchor id="docbook-appendix.html-dublincoreregistry" xreflabel="Default
-Dublin Core Metadata Registry"/>Default Dublin Core Metadata Registry</title>
+      <title><anchor id="docbook-appendix.html-dublincoreregistry" xreflabel="Default Dublin Core Metadata Registry"/>Default Dublin Core Metadata Registry</title>
       <informaltable frame="all">
         <tgroup cols="4">
           <colspec colname="c1" colwidth="25*"/>
diff --git a/dspace/docs/docbook/application.xml b/dspace/docs/docbook/application.xml
index 53c3d68440..8a34ba271a 100644
--- a/dspace/docs/docbook/application.xml
+++ b/dspace/docs/docbook/application.xml
@@ -1,8 +1,8 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Application Layer</title>
+    <title><anchor id="docbook-application.html"/>DSpace System Documentation: Application Layer</title>
     <para>
-      <ulink url="architecture.html">Back to architecture overview</ulink>
+      <link linkend="docbook-architecture.html">Back to architecture overview</link>
     </para>
     <section remap="h2">
       <title><anchor id="docbook-application.html-webui" xreflabel="Web User Interface"/>Web User Interface</title>
@@ -106,7 +106,7 @@
                   </para>
                 </entry>
                 <entry>
-                  <para>This is where you can place customized versions of JSPs -- see <ulink url="configure.html#customui">the configuration section</ulink></para>
+                  <para>This is where you can place customized versions of JSPs -- see <link linkend="docbook-configure.html-customui">the configuration section</link></para>
                 </entry>
               </row>
               <row>
@@ -212,7 +212,7 @@ ant -D<emphasis> [dspace]</emphasis>/config/dspace.cfg update
         <para><literal>[dspace-source]/jsp/dspace-admin/index.jsp</literal>, the administration UI index page, is invoked directly by Tomcat and not through a servlet for similar reasons.</para>
         <para>At the top of each JSP file, right after the license and copyright header, is documented the appropriate attributes that a servlet must fill out prior to forwarding to that JSP. No validation is performed; if the servlet does not fill out the necessary attributes, it is likely that an internal server error will occur.</para>
         <para>Many JSPs containing forms will include hidden parameters that tell the servlets which form has been filled out. The submission UI servlet (<literal>SubmissionController</literal> is a prime example of a servlet that deals with the input from many different JSPs. The <literal>step</literal> and <literal>page</literal> hidden parameters (written out by the <literal>SubmissionController.getSubmissionParameters()</literal> method) are used to inform the servlet which page of which step has just been filled out (i.e. which page of the submission the user has just completed).</para>
-        <para>Below is a detailed, scary diagram depicting the flow of control during the whole process of processing and responding to an HTTP request. More information about the authentication mechanism is mostly <ulink url="configure.html#authenticate">described in the configuration section</ulink>.</para>
+        <para>Below is a detailed, scary diagram depicting the flow of control during the whole process of processing and responding to an HTTP request. More information about the authentication mechanism is mostly <link linkend="docbook-configure.html-authenticate">described in the configuration section</link>.</para>
         <para>
           <inlinemediaobject>
             <imageobject>
@@ -425,7 +425,7 @@ https://dspace.mit.edu/html/1721.1/12345/contents.html
 https://dspace.mit.edu/html/1721.1/12345/figure1.gif
 </screen>
         <para>The HTML document servlet can work out which item the user is looking at, and then which Bitstream in it is called <literal>figure1.gif</literal>, and serve up that bitstream. Similar for following links to other HTML pages. Of course all the links and image references have to be relative and not absolute.</para>
-        <para>HTML documents must be &quot;self-contained&quot;, as <ulink url="functional.html#html">explained here</ulink>. Provided that full path information is known by DSpace, any depth or complexity of HTML document can be served subject to those contraints. This is usually possible with some kind of batch import. If, however, the document has been uploaded one file at a time using the Web UI, the path information has been stripped. The system can cope with relative links that refer to a deeper path, e.g.</para>
+        <para>HTML documents must be &quot;self-contained&quot;, as <link linkend="docbook-functional.html-html">explained here</link>. Provided that full path information is known by DSpace, any depth or complexity of HTML document can be served subject to those contraints. This is usually possible with some kind of batch import. If, however, the document has been uploaded one file at a time using the Web UI, the path information has been stripped. The system can cope with relative links that refer to a deeper path, e.g.</para>
         <screen>
 &lt;IMG SRC=&quot;images/figure1.gif&quot;&gt;
 </screen>
@@ -746,7 +746,7 @@ t;
       <section remap="h3">
         <title><anchor id="docbook-application.html-importingitems" xreflabel="Importing
 Items"/>Importing Items</title>
-        <para><emphasis role="bold">Note:</emphasis> Before running the item importer over items previously exported from a DSpace instance, please first refer to <ulink url="application.html#transferitem">Transferring Items Between DSpace Instances</ulink>.</para>
+        <para><emphasis role="bold">Note:</emphasis> Before running the item importer over items previously exported from a DSpace instance, please first refer to <link linkend="docbook-application.html-transferitem">Transferring Items Between DSpace Instances</link>.</para>
         <para>The item importer is in <literal>org.dspace.app.itemimport.ItemImport</literal>, and is run with the <literal>import</literal> utility in the <literal>dspace/bin</literal> directory. Running it with -h gets the current command-line arguments. Another very important flag is the --test flag, which you can use with any command to simulate all of the actions it will perform without actually making any changes to your DSpace instance - very useful for validating your item directories before doing an import. In the importer&apos;s arguments you can use either the user&apos;s database ID or email address and the eperson ID, and the collection&apos;s database ID or handle as arguments. Currently with the importer you can add, remove, and replace items in a collection. If you specify more than one collection argument then the items will be imported to multiple collections, and the first collection specified becomes the &quot;owning&quot; collection. If there is an error and the import is aborted, there is a --resume flag that you can try to resume the import where you left off after you fix the error.</para>
         <para>To add items to a collection with an EPerson as the submitter, type:</para>
         <screen>
@@ -827,10 +827,10 @@ Between DSpace Instances"/>Transferring Items Between DSpace Instances</title>
     <section remap="h2">
       <title><anchor id="docbook-application.html-registration" xreflabel="Registering (Not
 Importing) Bitstreams"/>Registering (Not Importing) Bitstreams</title>
-      <para>Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in storage accessible to DSpace. An example might be that there is a repository for existing digital assets. Rather than using the normal <ulink url="functional.html#ingest">interactive ingest process</ulink> or the <ulink url="functional.html#importexport">batch import</ulink> to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration.</para>
+      <para>Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in storage accessible to DSpace. An example might be that there is a repository for existing digital assets. Rather than using the normal <link linkend="docbook-functional.html-ingest">interactive ingest process</link> or the <link linkend="docbook-functional.html-importexport">batch import</link> to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration.</para>
       <section remap="h3">
         <title>Accessible Storage</title>
-        <para>To register an item its bitstreams must reside on storage accessible to DSpace and therefore referenced by an asset store number in <literal>dspace.cfg</literal>. The configuration file <literal>dspace.cfg</literal> establishes one or more asset stores through the use of an integer asset store number. This number relates to a directory in the DSpace host&apos;s file system or a set of SRB account parameters. This asset store number is described in <ulink url="configure.html#dspacecfg">The <literal>dspace.cfg</literal> Configuration Properties File</ulink> section and in the <literal>dspace.cfg</literal> file itself. The asset store number(s) used for registered items should generally not be the value of the <literal>assetstore.incoming</literal> property since it is unlikely that that you will want to mix the bitstreams of normally ingested and imported items and registered items.</para>
+        <para>To register an item its bitstreams must reside on storage accessible to DSpace and therefore referenced by an asset store number in <literal>dspace.cfg</literal>. The configuration file <literal>dspace.cfg</literal> establishes one or more asset stores through the use of an integer asset store number. This number relates to a directory in the DSpace host&apos;s file system or a set of SRB account parameters. This asset store number is described in <link linkend="docbook-configure.html-dspacecfg">The <literal>dspace.cfg</literal> Configuration Properties File</link> section and in the <literal>dspace.cfg</literal> file itself. The asset store number(s) used for registered items should generally not be the value of the <literal>assetstore.incoming</literal> property since it is unlikely that that you will want to mix the bitstreams of normally ingested and imported items and registered items.</para>
       </section>
       <section remap="h3">
         <title>Registering Items Using the Item Importer</title>
@@ -882,9 +882,9 @@ dsrun org.dspace.app.itemimport.ItemImport --add
 dsrun org.dspace.app.itemimport.ItemImport -a -e joe@user.com  -c
 	collectionID -s items_dir -m mapfile
 </screen>
-        <para>The <literal>--workflow</literal> and <literal>--test</literal> flags will function as described in <ulink url="application.html#importingitems">Importing Items</ulink>.</para>
-        <para>The <literal>--delete</literal> flag will function as described in <ulink url="application.html#importingitems">Importing Items</ulink> but the registered content files will not be removed from storage. See <link linkend="docbook-application.html-deletingregistereditems">Deleting Registered Items</link>.</para>
-        <para>The <literal>--replace</literal> flag will function as described in <ulink url="application.html#importingitems">Importing Items</ulink> but care should be taken to consider different cases and implications. With old items and new items being registered or ingested normally, there are four combinations or cases to consider. Foremost, an old registered item deleted from DSpace using <literal>--replace</literal> will not be removed from the storage. See <ulink url="application.html#deletingregistereditems">Deleting Registered Items</ulink>. where is resides. A new item added to DSpace using <literal>--replace</literal> will be ingested normally or will be registered depending on whether or not it is marked in the <literal>contents</literal> files with the -r.</para>
+        <para>The <literal>--workflow</literal> and <literal>--test</literal> flags will function as described in <link linkend="docbook-application.html-importingitems">Importing Items</link>.</para>
+        <para>The <literal>--delete</literal> flag will function as described in <link linkend="docbook-application.html-importingitems">Importing Items</link> but the registered content files will not be removed from storage. See <link linkend="docbook-application.html-deletingregistereditems">Deleting Registered Items</link>.</para>
+        <para>The <literal>--replace</literal> flag will function as described in <link linkend="docbook-application.html-importingitems">Importing Items</link> but care should be taken to consider different cases and implications. With old items and new items being registered or ingested normally, there are four combinations or cases to consider. Foremost, an old registered item deleted from DSpace using <literal>--replace</literal> will not be removed from the storage. See <link linkend="docbook-application.html-deletingregistereditems">Deleting Registered Items</link>. where is resides. A new item added to DSpace using <literal>--replace</literal> will be ingested normally or will be registered depending on whether or not it is marked in the <literal>contents</literal> files with the -r.</para>
       </section>
       <section remap="h3">
         <title>Internal Identification and Retrieval of Registered Items</title>
@@ -905,7 +905,7 @@ dsrun org.dspace.app.itemimport.ItemImport -a -e joe@user.com  -c
       </section>
       <section remap="h3">
         <title><anchor id="docbook-application.html-deletingregistereditems"/>Deleting Registered Items</title>
-        <para>If a registered item is deleted from DSpace, either interactively or by using the <literal>--delete</literal> or <literal>--replace</literal> flags described in <ulink url="application.html#importingitems">Importing Items</ulink>, the item will disappear from DSpace but it&apos;s registered content files will remain in place just as they were prior to registration. Bitstreams not registered but added by DSpace as part of registration, such as <literal>license.txt</literal> files, will be deleted.</para>
+        <para>If a registered item is deleted from DSpace, either interactively or by using the <literal>--delete</literal> or <literal>--replace</literal> flags described in <link linkend="docbook-application.html-importingitems">Importing Items</link>, the item will disappear from DSpace but it&apos;s registered content files will remain in place just as they were prior to registration. Bitstreams not registered but added by DSpace as part of registration, such as <literal>license.txt</literal> files, will be deleted.</para>
       </section>
     </section>
     <section remap="h2">
@@ -975,7 +975,7 @@ dsrun org.dspace.app.itemimport.ItemImport -a -e joe@user.com  -c
           </listitem>
           <listitem>
             <para> A <literal>fileSec</literal> containing a list of the bitstreams in the item. Each bundle constitutes a <literal>fileGrp</literal>. Each bitstream is represented by a <literal>file</literal> element, which contains an <literal>FLocat</literal> element with a simple XLink to the bitstream in the same directory as the <literal>mets.xml</literal> file. The <literal>file</literal> attributes consist of most of the basic technical metadata for the bitstream. Additionally, for those bitstreams that are thumbnails or text extracted from another bitstream in the item, those &apos;derived&apos; bitstreams have the same <literal>GROUPID</literal> as the bitstream they were derived from, in order that clients understand that there is a relationship.</para>
-            <para>The <literal>OWNERID</literal> of each <literal>file</literal> is the <ulink url="functional.html#bitstream_ids">&apos;persistent&apos; bitstream identifier</ulink> assigned by the DSpace instance. The <literal>ID</literal> and <literal>GROUPID</literal> attributes consist of the item&apos;s Handle, together with the bitstream&apos;s sequence ID, which underscores used in place of dots and slashes. For example, a bitstream with sequence ID 24, in the item <literal>hdl:123.456/789</literal> will have the <literal>ID</literal><literal>123_456_789_24</literal>. This is because <literal>ID</literal> and <literal>GROUPID</literal> attributes must be of type <literal>xsd:id</literal>.</para>
+            <para>The <literal>OWNERID</literal> of each <literal>file</literal> is the <link linkend="docbook-functional.html-bitstream_ids">&apos;persistent&apos; bitstream identifier</link> assigned by the DSpace instance. The <literal>ID</literal> and <literal>GROUPID</literal> attributes consist of the item&apos;s Handle, together with the bitstream&apos;s sequence ID, which underscores used in place of dots and slashes. For example, a bitstream with sequence ID 24, in the item <literal>hdl:123.456/789</literal> will have the <literal>ID</literal><literal>123_456_789_24</literal>. This is because <literal>ID</literal> and <literal>GROUPID</literal> attributes must be of type <literal>xsd:id</literal>.</para>
           </listitem>
         </itemizedlist>
       </section>
@@ -1003,7 +1003,7 @@ dsrun org.dspace.app.itemimport.ItemImport -a -e joe@user.com  -c
     <section remap="h2">
       <title><anchor id="docbook-application.html-mediafilters" xreflabel="MediaFilters:
 Transforming DSpace Content"/>MediaFilters: Transforming DSpace Content</title>
-      <para>DSpace can apply filters to content/bitstreams, creating new content. Filters are included that extract text for <emphasis role="bold">full-text searching</emphasis>, and create <emphasis role="bold">thumbnails</emphasis> for items that contain images. The media filters are controlled by the <literal>MediaFilterManager</literal> which traverses the asset store, invoking the <literal>MediaFilter</literal> or <literal>FormatFilter</literal> classes on bitstreams. The media filter plugin configuration <literal>filter.plugins</literal> in <literal>dspace.cfg</literal> contains a list of all enabled media/format filter plugins (see <ulink url="configure.html#mediafilters">Configuring Media Filters</ulink> for more information). The media filter system is intended to be run from the command line (or regularly as a cron task):</para>
+      <para>DSpace can apply filters to content/bitstreams, creating new content. Filters are included that extract text for <emphasis role="bold">full-text searching</emphasis>, and create <emphasis role="bold">thumbnails</emphasis> for items that contain images. The media filters are controlled by the <literal>MediaFilterManager</literal> which traverses the asset store, invoking the <literal>MediaFilter</literal> or <literal>FormatFilter</literal> classes on bitstreams. The media filter plugin configuration <literal>filter.plugins</literal> in <literal>dspace.cfg</literal> contains a list of all enabled media/format filter plugins (see <link linkend="docbook-configure.html-mediafilters">Configuring Media Filters</link> for more information). The media filter system is intended to be run from the command line (or regularly as a cron task):</para>
       <screen>
 [dspace]/bin/filter-media
 </screen>
@@ -1087,7 +1087,7 @@ Transforming DSpace Content"/>MediaFilters: Transforming DSpace Content</title>
           </itemizedlist>
         </listitem>
       </itemizedlist>
-      <para>Adding your own filters is done by creating a class which <literal>implements</literal> the <literal>org.dspace.app.mediafilter.FormatFilter</literal> interface. See the <ulink url="configure.html#newfilter">Creating a new Media Filter</ulink> topic and comments in the source file FormatFilter.java for more information. In theory filters could be implemented in any programming language (C, Perl, etc.) However, they need to be invoked by the Java code in the Media Filter class that you create.</para>
+      <para>Adding your own filters is done by creating a class which <literal>implements</literal> the <literal>org.dspace.app.mediafilter.FormatFilter</literal> interface. See the <link linkend="docbook-configure.html-newfilter">Creating a new Media Filter</link> topic and comments in the source file FormatFilter.java for more information. In theory filters could be implemented in any programming language (C, Perl, etc.) However, they need to be invoked by the Java code in the Media Filter class that you create.</para>
     </section>
     <section remap="h2">
       <title><anchor id="docbook-application.html-filiator" xreflabel="Sub-Community
diff --git a/dspace/docs/docbook/architecture.xml b/dspace/docs/docbook/architecture.xml
index 117d170187..39ca087e5e 100644
--- a/dspace/docs/docbook/architecture.xml
+++ b/dspace/docs/docbook/architecture.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Architecture</title>
+    <title><anchor id="docbook-architecture.html"/>DSpace System Documentation: Architecture</title>
     <section remap="h2">
       <title><anchor id="docbook-architecture.html-overview" xreflabel="Overview"/>Overview</title>
       <para>The DSpace system is organized into three layers, each of which consists of a number of components.</para>
@@ -77,16 +77,16 @@ mvn javadoc:javadoc
       <itemizedlist>
         <listitem>
           <para>
-            <ulink url="storage.html">Storage Layer</ulink>
+            <link linkend="docbook-storage.html">Storage Layer</link>
             <itemizedlist>
               <listitem>
                 <para>
-                  <ulink url="storage.html#rdbms">RDBMS</ulink>
+                  <link linkend="docbook-storage.html-rdbms">RDBMS</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="storage.html#bitstreams">Bitstream Store</ulink>
+                  <link linkend="docbook-storage.html-bitstreams">Bitstream Store</link>
                 </para>
               </listitem>
             </itemizedlist>
@@ -94,61 +94,61 @@ mvn javadoc:javadoc
         </listitem>
         <listitem>
           <para>
-            <ulink url="business.html">Business Logic Layer</ulink>
+            <link linkend="docbook-business.html">Business Logic Layer</link>
             <itemizedlist>
               <listitem>
                 <para>
-                  <ulink url="business.html#core">Core Classes</ulink>
+                  <link linkend="docbook-business.html-core">Core Classes</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#content">Content Management API</ulink>
+                  <link linkend="docbook-business.html-content">Content Management API</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#workflow">Workflow System</ulink>
+                  <link linkend="docbook-business.html-workflow">Workflow System</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#administer">Administration Toolkit</ulink>
+                  <link linkend="docbook-business.html-administer">Administration Toolkit</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#eperson">E-person/Group Manager</ulink>
+                  <link linkend="docbook-business.html-eperson">E-person/Group Manager</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#authorize">Authorisation</ulink>
+                  <link linkend="docbook-business.html-authorize">Authorisation</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#handle">Handle Manager/Handle Plugin</ulink>
+                  <link linkend="docbook-business.html-handle">Handle Manager/Handle Plugin</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#search">Search</ulink>
+                  <link linkend="docbook-business.html-search">Search</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#browse">Browse API</ulink>
+                  <link linkend="docbook-business.html-browse">Browse API</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#history">History Recorder</ulink>
+                  <link linkend="docbook-business.html-history">History Recorder</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="business.html#checker">Checksum Checker</ulink>
+                  <link linkend="docbook-business.html-checker">Checksum Checker</link>
                 </para>
               </listitem>
             </itemizedlist>
@@ -156,46 +156,46 @@ mvn javadoc:javadoc
         </listitem>
         <listitem>
           <para>
-            <ulink url="application.html">Application Layer</ulink>
+            <link linkend="docbook-application.html">Application Layer</link>
             <itemizedlist>
               <listitem>
                 <para>
-                  <ulink url="application.html#webui">Web User Interface</ulink>
+                  <link linkend="docbook-application.html-webui">Web User Interface</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#oai">OAI-PMH Data Provider</ulink>
+                  <link linkend="docbook-application.html-oai">OAI-PMH Data Provider</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#itemimporter">Item Importer and Exporter</ulink>
+                  <link linkend="docbook-application.html-itemimporter">Item Importer and Exporter</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#transferitem">Transferring Items Between DSpace Instances</ulink>
+                  <link linkend="docbook-application.html-transferitem">Transferring Items Between DSpace Instances</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#registration">Registration</ulink>
+                  <link linkend="docbook-application.html-registration">Registration</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#mets">METS Tools</ulink>
+                  <link linkend="docbook-application.html-mets">METS Tools</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#mediafilters">Media Filters</ulink>
+                  <link linkend="docbook-application.html-mediafilters">Media Filters</link>
                 </para>
               </listitem>
               <listitem>
                 <para>
-                  <ulink url="application.html#filiator">Sub-Community Management</ulink>
+                  <link linkend="docbook-application.html-filiator">Sub-Community Management</link>
                 </para>
               </listitem>
             </itemizedlist>
diff --git a/dspace/docs/docbook/book.xml b/dspace/docs/docbook/book.xml
index f1494abc01..a61a968d57 100644
--- a/dspace/docs/docbook/book.xml
+++ b/dspace/docs/docbook/book.xml
@@ -20,7 +20,7 @@
 
 <book>
   <bookinfo>
-    <title>DSpace 1.5.1 Manual</title>
+    <title>DSpace 1.5.2 Manual</title>
     
     <author>
       <surname>The DSpace Foundation</surname>
@@ -30,7 +30,7 @@
     </author>
 
     <copyright>
-      <year>2002-2008</year>
+      <year>2002-2009</year>
       <holder>
         <ulink url="http://www.dspace.org/">The DSpace Foundation</ulink>
       </holder>
diff --git a/dspace/docs/docbook/business.xml b/dspace/docs/docbook/business.xml
index 9ac032905f..595c545d54 100644
--- a/dspace/docs/docbook/business.xml
+++ b/dspace/docs/docbook/business.xml
@@ -1,13 +1,13 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Business Logic Layer</title>
+    <title><anchor id="docbook-business.html"/>DSpace System Documentation: Business Logic Layer</title>
     <section remap="h2">
       <title><anchor id="docbook-business.html-core" xreflabel="Core Classes"/>Core Classes</title>
       <para>The <literal>org.dspace.core</literal> package provides some basic classes that are used throughout the DSpace code.</para>
       <section remap="h3">
         <title>The Configuration Manager (<literal>ConfigurationManager</literal>)</title>
         <para>The configuration manager is responsible for reading the main <literal>dspace.cfg</literal> properties file, managing the &apos;template&apos; configuration files for other applications such as Apache, and for obtaining the text for e-mail messages.</para>
-        <para>The system is configured by editing the relevant files in <literal>/dspace/config</literal>, as described in the <ulink url="configure.html">configuration section</ulink>.</para>
+        <para>The system is configured by editing the relevant files in <literal>/dspace/config</literal>, as described in the <link linkend="docbook-configure.html">configuration section</link>.</para>
         <para>
           <emphasis role="bold">When editing configuration files for applications that DSpace uses, such as Apache, remember to edit the file in /dspace/config/templates and then run /dspace/bin/install-configs rather than editing the &apos;live&apos; version directly!</emphasis>
         </para>
@@ -19,7 +19,7 @@
                 <literal> /dspace/bin/install-configs</literal>
 
               </screen>
- This processes and installs configuration files for other applications, as described in the <ulink url="configure.html#templates">configuration section</ulink>.</para>
+ This processes and installs configuration files for other applications, as described in the <link linkend="docbook-configure.html-templates">configuration section</link>.</para>
           </listitem>
           <listitem>
             <para><screen>
@@ -214,7 +214,7 @@
     <section remap="h2">
       <title><anchor id="docbook-business.html-content" xreflabel="Content Management API"/>Content Management API</title>
       <para>The content management API package <literal>org.dspace.content</literal> contains Java classes for reading and manipulating content stored in the DSpace system. This is the API that components in the application layer will probably use most.</para>
-      <para>Classes corresponding to the main elements in the <ulink url="functional.html#data_model">DSpace data model</ulink> (<literal>Community</literal>, <literal>Collection</literal>, <literal>Item</literal>, <literal>Bundle</literal> and <literal>Bitstream</literal>) are sub-classes of the abstract class <literal>DSpaceObject</literal>. The <literal>Item</literal> object handles the Dublin Core metadata record.</para>
+      <para>Classes corresponding to the main elements in the <link linkend="docbook-functional.html-data_model">DSpace data model</link> (<literal>Community</literal>, <literal>Collection</literal>, <literal>Item</literal>, <literal>Bundle</literal> and <literal>Bitstream</literal>) are sub-classes of the abstract class <literal>DSpaceObject</literal>. The <literal>Item</literal> object handles the Dublin Core metadata record.</para>
       <para>Each class generally has one or more static <literal>find</literal> methods, which are used to instantiate content objects. Constructors do not have public access and are just used internally. The reasons for this are:</para>
       <itemizedlist>
         <listitem>
@@ -240,7 +240,7 @@ Collection myNewCollection = existingCommunity.createCollection();
 </screen>
       <para>The primary reason for this is for determining authorization. In order to know whether an e-person may create an object, the system must know which container the object is to be added to. It makes no sense to create a collection outside of a community, and the authorization system does not have a policy for that.</para>
       <para><literal>Item</literal>s are first created in the form of an implementation of <literal>InProgressSubmission</literal>. An <literal>InProgressSubmission</literal> represents an item under construction; once it is complete, it is installed into the main archive and added to the relevant collection by the <literal>InstallItem</literal> class. The <literal>org.dspace.content</literal> package provides an implementation of <literal>InProgressSubmission</literal> called <literal>WorkspaceItem</literal>; this is a simple implementation that contains some fields used by the Web submission UI. The <literal>org.dspace.workflow</literal> also contains an implementation called <literal>WorkflowItem</literal> which represents a submission undergoing a workflow process.</para>
-      <para>In the previous chapter there is an <ulink url="functional.html#ingest">overview of the item ingest process</ulink> which should clarify the previous paragraph. Also see the section on <link linkend="docbook-business.html-workflow">the workflow system</link>.</para>
+      <para>In the previous chapter there is an <link linkend="docbook-functional.html-ingest">overview of the item ingest process</link> which should clarify the previous paragraph. Also see the section on <link linkend="docbook-business.html-workflow">the workflow system</link>.</para>
       <para><literal>Community</literal> and <literal>BitstreamFormat</literal> do have static <literal>create</literal> methods; one must be a site administrator to have authorization to invoke these.</para>
       <section remap="h3">
         <title>Other Classes</title>
@@ -789,7 +789,7 @@ osswalk = \
         <para>Here are some usage examples to illustrate how the Plugin Manager works.</para>
         <section remap="h4">
           <title>Managing the MediaFilter plugins transparently</title>
-          <para>The existing DSpace 1.3 MediaFilterManager implementation has been largely replaced by the Plugin Manager. The MediaFilter classes become plugins named in the configuration. Refer to the <ulink url="configure.html#mediafilters">configuration guide</ulink> for further details.</para>
+          <para>The existing DSpace 1.3 MediaFilterManager implementation has been largely replaced by the Plugin Manager. The MediaFilter classes become plugins named in the configuration. Refer to the <link linkend="docbook-configure.html-mediafilters">configuration guide</link> for further details.</para>
         </section>
         <section remap="h4">
           <title>A Singleton Plugin</title>
@@ -865,7 +865,7 @@ public class XsltDisseminationCrosswalk extends SelfNamedPlugin
           </section>
         <section remap="h4">
           <title>Stackable Authentication</title>
-          <para>The Stackable Authentication mechanism needs to know all of the plugins configured for the interface, in the order of configuration, since order is significant. It gets a Sequence Plugin from the Plugin Manager. Refer to the <ulink url="configure.html#authenticate">configuration guide</ulink> for further details.</para>
+          <para>The Stackable Authentication mechanism needs to know all of the plugins configured for the interface, in the order of configuration, since order is significant. It gets a Sequence Plugin from the Plugin Manager. Refer to the <link linkend="docbook-configure.html-authenticate">configuration guide</link> for further details.</para>
         </section>
       </section>
     </section>
@@ -1027,7 +1027,7 @@ hdl:1721.123/4567
 http://hdl.handle.net/1721.123/4567
 </screen>
       <para>It is the responsibility of the caller to extract the basic form from whichever displayed form is used.</para>
-      <para>The <literal>handle</literal> table maps these Handles to resource type/resource ID pairs, where resource type is a value from <literal>org.dspace.core.Constants</literal> and resource ID is the internal identifier (database primary key) of the object. This allows Handles to be assigned to any type of object in the system, though as <ulink url="functional.html#handles">explained in the functional overview</ulink>, only communities, collections and items are presently assigned Handles.</para>
+      <para>The <literal>handle</literal> table maps these Handles to resource type/resource ID pairs, where resource type is a value from <literal>org.dspace.core.Constants</literal> and resource ID is the internal identifier (database primary key) of the object. This allows Handles to be assigned to any type of object in the system, though as <link linkend="docbook-functional.html-handles">explained in the functional overview</link>, only communities, collections and items are presently assigned Handles.</para>
       <para><literal>HandleManager</literal> contains static methods for:</para>
       <itemizedlist>
         <listitem>
diff --git a/dspace/docs/docbook/configure.xml b/dspace/docs/docbook/configure.xml
index 0ce20bb270..b2b14287b1 100644
--- a/dspace/docs/docbook/configure.xml
+++ b/dspace/docs/docbook/configure.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Configuration and Customization</title>
+    <title><anchor id="docbook-configure.html"/>DSpace System Documentation: Configuration and Customization</title>
     <para>There are a number of ways in which DSpace can be configured and/or customized:</para>
     <itemizedlist>
       <listitem>
@@ -195,7 +195,7 @@ stack"/>authentication stack. Authentication methods are called on in the order
                     </para>
                   </entry>
                   <entry>
-                    <para>The Handle prefix for your site, <ulink url="install.html#handles">see the Handle section</ulink></para>
+                    <para>The Handle prefix for your site, <link linkend="docbook-install.html-handles">see the Handle section</link></para>
                   </entry>
                 </row>
                 <row>
@@ -225,7 +225,7 @@ stack"/>authentication stack. Authentication methods are called on in the order
                     </para>
                   </entry>
                   <entry>
-                    <para>The location in the file system of asset (bitstream) store number <literal>n</literal>. When adding additional stores, start with 1 (<literal>assetstore.dir.1</literal> and count upwards. Always leave asset store zero (<literal>assetstore.dir</literal>). For more details, see <ulink url="storage.html#bitstreams">the Bitstream Storage section</ulink>.</para>
+                    <para>The location in the file system of asset (bitstream) store number <literal>n</literal>. When adding additional stores, start with 1 (<literal>assetstore.dir.1</literal> and count upwards. Always leave asset store zero (<literal>assetstore.dir</literal>). For more details, see <link linkend="docbook-storage.html-bitstreams">the Bitstream Storage section</link>.</para>
                   </entry>
                 </row>
                 <row>
@@ -240,7 +240,7 @@ stack"/>authentication stack. Authentication methods are called on in the order
                     </para>
                   </entry>
                   <entry>
-                    <para>The asset store number to use for storing new bitstreams. For example, if <literal>assetstore.dir.1</literal> is <literal>/anotherdisk/store1</literal>, and <literal>assetstore.incoming</literal> is <literal>1</literal>, new bitstreams will be stored under <literal>/anotherdisk/store1</literal>. A value of <literal>0</literal> (zero) corresponds to <literal>assetstore.dir</literal>. For more details, see <ulink url="storage.html#bitstreams">the Bitstream Storage section</ulink>.</para>
+                    <para>The asset store number to use for storing new bitstreams. For example, if <literal>assetstore.dir.1</literal> is <literal>/anotherdisk/store1</literal>, and <literal>assetstore.incoming</literal> is <literal>1</literal>, new bitstreams will be stored under <literal>/anotherdisk/store1</literal>. A value of <literal>0</literal> (zero) corresponds to <literal>assetstore.dir</literal>. For more details, see <link linkend="docbook-storage.html-bitstreams">the Bitstream Storage section</link>.</para>
                   </entry>
                 </row>
                 <row>
@@ -252,7 +252,7 @@ stack"/>authentication stack. Authentication methods are called on in the order
                     <para>/zone/home/user.domain</para>
                   </entry>
                   <entry>
-                    <para>The sets of SRB access parameters (see dspace.cfg) if one or more SRB accounts are used. The srb.xxx set would correspond to asset (bitstream) store number zero. The srb.xxx.n set would correspond to asset (bitstream) store number n. For more details, see <ulink url="storage.html#bitstreams">the Bitstream Storage section</ulink>.</para>
+                    <para>The sets of SRB access parameters (see dspace.cfg) if one or more SRB accounts are used. The srb.xxx set would correspond to asset (bitstream) store number zero. The srb.xxx.n set would correspond to asset (bitstream) store number n. For more details, see <link linkend="docbook-storage.html-bitstreams">the Bitstream Storage section</link>.</para>
                   </entry>
                 </row>
                 <row>
@@ -653,7 +653,7 @@ recent.submissions.sort-option = dateaccessioned
           <screen>
 recent.submissions.count = 5
 </screen>
-          <para>Now we need to set up the processors that the <ulink url="business.html#plugin">PluginManager</ulink> will load to actually perform the recent submissions query on the relevant pages.</para>
+          <para>Now we need to set up the processors that the <link linkend="docbook-business.html-plugin">PluginManager</link> will load to actually perform the recent submissions query on the relevant pages.</para>
           <para>Tell the community and collection pages that we are using the Recent Submissions code</para>
           <screen>
 plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \
@@ -677,7 +677,7 @@ itemmap.author.index = author
       <section remap="h3">
         <title><anchor id="docbook-configure.html-general-mediafilter" xreflabel="Configuring Media Filters"/>Configuring Media Filters</title>
         <para>Media or Format Filters are classes used to generate derivative or alternative versions of content or bitstreams within DSpace. For example, the PDF Media Filter will extract textual content from PDF bitstreams, the JPEG Media Filter can create thumbnails from image bitstreams.</para>
-        <para>Media Filters are configured as <ulink url="business.html#plugin">Named Plugins</ulink>, with each filter also having a separate configuration setting (in <literal>dspace.cfg</literal>) indicating which formats it can process. The default configuration is shown below.</para>
+        <para>Media Filters are configured as <link linkend="docbook-business.html-plugin">Named Plugins</link>, with each filter also having a separate configuration setting (in <literal>dspace.cfg</literal>) indicating which formats it can process. The default configuration is shown below.</para>
         <screen>
         #### Media Filter / Format Filter plugins (through
 	PluginManager) ####
@@ -720,7 +720,7 @@ s = GIF, JPEG, image/png
 </screen>
           <para>The enabled Media/Format Filters are named in the <literal>filter.plugins</literal> field above.</para>
         <para>Names are assigned to each filter using the <literal>plugin.named.org.dspace.app.mediafilter.FormatFilter</literal> field (e.g. by default the <literal>PDFFilter</literal> is named &quot;PDF Text Extractor&quot;).</para>
-        <para>Finally the appropriate <literal>filter.&lt;class path&gt;.inputFormats</literal> defines the vaild input formats which each filter can be applied to. These format names <emphasis role="bold">must match</emphasis> the <literal>short description</literal> field of the <ulink url="appendix.html#bitstreamformatregistry">Bitstream Format Registry</ulink>.</para>
+        <para>Finally the appropriate <literal>filter.&lt;class path&gt;.inputFormats</literal> defines the vaild input formats which each filter can be applied to. These format names <emphasis role="bold">must match</emphasis> the <literal>short description</literal> field of the <link linkend="docbook-appendix.html-bitstreamformatregistry">Bitstream Format Registry</link>.</para>
         <para>You can also implement more dynamic or configurable Media/Format Filters which extend <ulink url="business.html#selfnamedplugin">
             <literal>SelfNamedPlugin</literal>
           </ulink>
@@ -749,7 +749,7 @@ Messages"/>Wording of E-mail Messages</title>
     <section remap="h2">
       <title><anchor id="docbook-configure.html-general-registries" xreflabel="The
 Metadata and Bitstream Format Registries"/>The Metadata and Bitstream Format Registries</title>
-      <para>The <literal>[dspace]/config/registries</literal> directory contains three XML files. These are used to load the <emphasis>initial</emphasis> contents of the Metadata Schema Registry, <ulink url="appendix.html#dublincoreregistry">Dublin Core Metadata registry</ulink> and <ulink url="appendix.html#bitstreamformatregistry">Bitstream Format registry</ulink>. After the initial loading (performed by <literal>ant fresh_install</literal> above), the registries reside in the database; the XML files are not updated.</para>
+      <para>The <literal>[dspace]/config/registries</literal> directory contains three XML files. These are used to load the <emphasis>initial</emphasis> contents of the Metadata Schema Registry, <link linkend="docbook-appendix.html-dublincoreregistry">Dublin Core Metadata registry</link> and <link linkend="docbook-appendix.html-bitstreamformatregistry">Bitstream Format registry</link>. After the initial loading (performed by <literal>ant fresh_install</literal> above), the registries reside in the database; the XML files are not updated.</para>
       <para>In order to change the registries, you may adjust the XML files before the first installation of DSpace. On an allready running instance it is recommended to change bitstream registries via DSpace admin UI, but the metadata registries can be loaded again at any time from the XML files without difficult. The changes made via admin UI are not reflected in the XML files.</para>
       <section remap="h3">
         <title>Metadata Schema Registry</title>
@@ -773,7 +773,7 @@ Metadata and Bitstream Format Registries"/>The Metadata and Bitstream Format Reg
       <section remap="h3">
         <title>Metadata Format Registries</title>
         <para>The default metadata schema is Dublin Core, so DSpace is distributed with a default Dublin Core Metadata Registry. Currently, the system requires that every item have a Dublin Core record.</para>
-        <para>There is a set of Dublin Core Elements, which is used by the system and should not be removed or moved to another schema, see <ulink url="appendix.html#dublincoreregistry">Appendix: Default Dublin Core Metadata registry</ulink>.</para>
+        <para>There is a set of Dublin Core Elements, which is used by the system and should not be removed or moved to another schema, see <link linkend="docbook-appendix.html-dublincoreregistry">Appendix: Default Dublin Core Metadata registry</link>.</para>
         <para><emphasis role="bold">Note</emphasis>: altering a Metadata Registry has no effect on corresponding parts, e.g. item submission interface, item display, item import and vice versa. Every metadata element used in submission interface or item import must be registered before using it.</para>
         <para><emphasis role="bold">Note</emphasis> also that deleting a metadata element will delete all its corresponding values.</para>
         <para>If you wish to add more metadata elements, you can do this in one of two ways. Via the DSpace admin UI you may define new metadata elements in the different available schemas. But you may also modify the XML file (or provide an additional one), and re-import the data as follows:</para>
@@ -881,7 +881,7 @@ Submission License"/>The Default Submission License</title>
     <section remap="h2">
       <title><anchor id="docbook-configure.html-general-submission" xreflabel="Submission
 Configuration"/>Submission Configuration</title>
-      <para>Instructions for customizing and configuring the Item Submission user interface for either the JSP-UI or XML-UI are contained in the separate <ulink url="submission.html">Customizing and Configuring Submission User Interface</ulink> page.</para>
+      <para>Instructions for customizing and configuring the Item Submission user interface for either the JSP-UI or XML-UI are contained in the separate <link linkend="docbook-submission.html">Customizing and Configuring Submission User Interface</link> page.</para>
     </section>
     <section remap="h2">
       <title><anchor id="docbook-configure.html-xmlui" xreflabel="XMLUI Interface Customizations
@@ -1251,7 +1251,7 @@ Theme"/>Creating a New Theme</title>
         <para>
           <emphasis role="bold">4) Install theme and rebuild DSpace</emphasis>
         </para>
-        <para>Next rebuild &amp; deploy DSpace as described in the <ulink url="install.html">installation portion of the manual</ulink>, and ensure the theme has been installed as described in the previous section &quot;<ulink url="configure.html#xmlui-configure">Configuring Themes and Aspects</ulink>&quot;.</para>
+        <para>Next rebuild &amp; deploy DSpace as described in the <link linkend="docbook-install.html">installation portion of the manual</link>, and ensure the theme has been installed as described in the previous section &quot;<link linkend="docbook-configure.html-xmlui-configure">Configuring Themes and Aspects</link>&quot;.</para>
       </section>
       <section remap="h3">
         <title><anchor id="docbook-configure.html-xmlui-staticcontent" xreflabel="Static Content"/>Adding Static Content</title>
@@ -1605,7 +1605,7 @@ Multilingual Support"/>Configuring Multilingual Support</title>
 pages"/>Customizing the JSP pages</title>
         <para>The JSPUI interface is implemented using Java Servlets which handle the business logic, and JavaServer Pages (JSPs) which produce the HTML pages sent to an end-user. Since the JSPs are much closer to HTML than Java code, altering the look and feel of DSpace is relatively easy.</para>
         <para>To make it even easier, DSpace allows you to &apos;override&apos; the JSPs included in the source distribution with modified versions, that are stored in a separate place, so when it comes to updating your site with a new DSpace release, your modified versions will not be overwritten. It should be possible to dramatically change the look of DSpace to suit your organization by just changing the CSS style file and the site &apos;skin&apos; or &apos;layout&apos; JSPs in <literal>jsp/layout</literal>; if possible, it is recommended you limit local customizations to these files to make future upgrades easier.</para>
-        <para>You can also easily edit the text that appears on each JSP page by editing the dictionary file. However, note that unless you change the entry in all of the different language message files, users of other languages will still see the default text for their language. See <ulink url="application.html#i18n">internationalization</ulink>.</para>
+        <para>You can also easily edit the text that appears on each JSP page by editing the dictionary file. However, note that unless you change the entry in all of the different language message files, users of other languages will still see the default text for their language. See <link linkend="docbook-application.html-i18n">internationalization</link>.</para>
         <para>Note that the data (attributes) passed from an underlying Servlet to the JSP may change between versions, so you may have to modify your customized JSP to deal with the new data.</para>
         <para>Thus, if possible, it is recommended you limit your changes to the &apos;layout&apos; JSPs and the stylesheet.</para>
         <para>The JSPs are available in one of two places:</para>
@@ -1665,7 +1665,7 @@ pages"/>Customizing the JSP pages</title>
         <para>Heavy use is made of a style sheet, <literal>styles.css.jsp</literal>. If you make edits, copy the local version to <literal>[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/styles.css.jsp</literal>, and it will be used automatically in preference to the default, as described above.</para>
         <para>Fonts and colors can be easily changed using the stylesheet. The stylesheet is a JSP so that the user&apos;s browser version can be detected and the stylesheet tweaked accordingly.</para>
         <para>The &apos;layout&apos; of each page, that is, the top and bottom banners and the navigation bar, are determined by the JSPs <literal>/layout/header-*.jsp</literal> and <literal>/layout/footer-*.jsp</literal>. You can provide modified versions of these (in <literal>[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/layout</literal>), or define more styles and apply them to pages by using the &quot;style&quot; attribute of the <literal>dspace:layout</literal> tag.</para>
-        <para>After you&apos;ve customized your JSPs, <emphasis role="bold">you must rebuild the DSpace Web application</emphasis>. If you haven&apos;t already built and installed it, follow the <ulink url="install.html">install</ulink> directions. Otherwise, follow the steps below:</para>
+        <para>After you&apos;ve customized your JSPs, <emphasis role="bold">you must rebuild the DSpace Web application</emphasis>. If you haven&apos;t already built and installed it, follow the <link linkend="docbook-install.html">install</link> directions. Otherwise, follow the steps below:</para>
         <orderedlist>
           <listitem>
             <para> Rebuild the DSpace installation package by running the following command from your <literal>[dspace-source]/dspace/</literal> directory:</para>
@@ -1898,7 +1898,7 @@ Authentication"/>Custom Authentication</title>
           <para>The X.509 authentication method uses an X.509 certificate sent by the client to establish his/her identity. It requires the client to have a personal Web certificate installed on their browser (or other client software) which is issued by a Certifying Authority (CA) recognized by the web server.</para>
           <orderedlist>
             <listitem>
-              <para> See the <ulink url="install.html#https">HTTPS installation instructions</ulink> to configure your Web server. If you are using HTTPS with Tomcat, note that the <literal>&lt;Connector&gt;</literal> tag <emphasis>must</emphasis> include the attribute <literal>clientAuth=&quot;true&quot;</literal> so the server requests a personal Web certificate from the client.</para>
+              <para> See the <link linkend="docbook-install.html-https">HTTPS installation instructions</link> to configure your Web server. If you are using HTTPS with Tomcat, note that the <literal>&lt;Connector&gt;</literal> tag <emphasis>must</emphasis> include the attribute <literal>clientAuth=&quot;true&quot;</literal> so the server requests a personal Web certificate from the client.</para>
             </listitem>
             <listitem>
               <para> Add the <literal>org.dspace.authenticate.X509Authentication</literal> plugin <emphasis>first</emphasis> to the list of stackable authentication methods in the value of the configuration key <literal>plugin.sequence.org.dspace.authenticate.AuthenticationMethod</literal><emphasis>E.g.:</emphasis></para>
@@ -2129,12 +2129,12 @@ Crosswalks"/>Activating Additional OAI-PMH Crosswalks</title>
       </section>
       <section remap="h3">
         <title><anchor id="docbook-configure.html-packager" xreflabel="Configuring Packager Plugins"/>Configuring Packager Plugins</title>
-        <para>Package ingester plugins are configured as <ulink url="business.html#plugin">named or self-named plugins</ulink> for the interface <literal>org.dspace.content.packager.PackageIngester</literal>. Package disseminator plugins are configured as <ulink url="business.html#plugin">named or self-named plugins</ulink> for the interface <literal>org.dspace.content.packager.PackageDisseminator</literal>.</para>
-        <para>You can add names for the existing plugins, and add new plugins, by altering these configuration properties. See the <ulink url="business.html#plugin">Plugin Manager</ulink> architecture for more information about plugins.</para>
+        <para>Package ingester plugins are configured as <link linkend="docbook-business.html-plugin">named or self-named plugins</link> for the interface <literal>org.dspace.content.packager.PackageIngester</literal>. Package disseminator plugins are configured as <link linkend="docbook-business.html#plugin">named or self-named plugins</link> for the interface <literal>org.dspace.content.packager.PackageDisseminator</literal>.</para>
+        <para>You can add names for the existing plugins, and add new plugins, by altering these configuration properties. See the <link linkend="docbook-business.html-plugin">Plugin Manager</link> architecture for more information about plugins.</para>
       </section>
       <section remap="h3">
         <title><anchor id="docbook-configure.html-crosswalk" xreflabel="Configuring Crosswalk Plugins"/>Configuring Crosswalk Plugins</title>
-        <para>Ingestion crosswalk plugins are configured as <ulink url="business.html#plugin">named or self-named plugins</ulink> for the interface <literal>org.dspace.content.crosswalk.IngestionCrosswalk</literal>. Dissemination crosswalk plugins are configured as <ulink url="business.html#plugin">named or self-named plugins</ulink> for the interface <literal>org.dspace.content.crosswalk.DisseminationCrosswalk</literal>.</para>
+        <para>Ingestion crosswalk plugins are configured as <link linkend="docbook-business.html-plugin">named or self-named plugins</link> for the interface <literal>org.dspace.content.crosswalk.IngestionCrosswalk</literal>. Dissemination crosswalk plugins are configured as <link linkend="docbook-business.html#plugin">named or self-named plugins</link> for the interface <literal>org.dspace.content.crosswalk.DisseminationCrosswalk</literal>.</para>
         <para>You can add names for existing crosswalks, add new plugin classes, and add new configurations for the configurable crosswalks as noted below.</para>
         <section remap="h4">
           <title><anchor id="docbook-configure.html-mods" xreflabel="Configurable MODS dissemination
@@ -2316,7 +2316,7 @@ Filter"/>Creating a new Media/Format Filter</title>
 	MediaFilter</literal>
 
           </screen>
-            <para>You must give your new filter a &quot;name&quot;, by adding it and its name to the <literal>plugin.named.org.dspace.app.mediafilter.FormatFilter</literal> field in <literal>dspace.cfg</literal>. In addition to naming your filter, make sure to specify its input formats in the <literal>filter.&lt;class path&gt;.inputFormats</literal> config item. Note the input formats must match the <literal>short description</literal> field in the <ulink url="appendix.html#bitstreamformatregistry">Bitstream Format Registry</ulink> (i.e. <literal>bitstreamformatregistry</literal> table).</para>
+            <para>You must give your new filter a &quot;name&quot;, by adding it and its name to the <literal>plugin.named.org.dspace.app.mediafilter.FormatFilter</literal> field in <literal>dspace.cfg</literal>. In addition to naming your filter, make sure to specify its input formats in the <literal>filter.&lt;class path&gt;.inputFormats</literal> config item. Note the input formats must match the <literal>short description</literal> field in the <link linkend="docbook-appendix.html-bitstreamformatregistry">Bitstream Format Registry</link> (i.e. <literal>bitstreamformatregistry</literal> table).</para>
           <screen>
 
             <literal> plugin.named.org.dspace.app.mediafilter.FormatFilter = \
@@ -2343,7 +2343,7 @@ Filter"/>Creating a new Media/Format Filter</title>
 	SelfNamedPlugin implements FormatFilter</literal>
 
           </screen>
-            <para>Since <literal>SelfNamedPlugins</literal> are self-named (as stated), they must provide the various names the plugin uses by defining a <ulink url="business.html#pluginmethods">getPluginNames()</ulink> method. Generally speaking, each &quot;name&quot; the plugin uses should correspond to a different type of filter it implements (e.g. &quot;Word2PDF&quot; and &quot;Excel2CSV&quot; are two good names for a complex media filter which performs both Word to PDF and Excel to CSV conversions).</para>
+            <para>Since <literal>SelfNamedPlugins</literal> are self-named (as stated), they must provide the various names the plugin uses by defining a <link linkend="docbook-business.html-pluginmethods">getPluginNames()</link> method. Generally speaking, each &quot;name&quot; the plugin uses should correspond to a different type of filter it implements (e.g. &quot;Word2PDF&quot; and &quot;Excel2CSV&quot; are two good names for a complex media filter which performs both Word to PDF and Excel to CSV conversions).</para>
           <para>Self-Named Media/Format Filters are also configured differently in <literal>dspace.cfg</literal>. Below is a general template for a Self Named Filter (defined by an imaginary <literal>MyComplexMediaFilter</literal> class, which can perform both Word to PDF and Excel to CSV conversions):</para>
           <screen>
 
diff --git a/dspace/docs/docbook/directories.xml b/dspace/docs/docbook/directories.xml
index 82837bc056..af42455743 100644
--- a/dspace/docs/docbook/directories.xml
+++ b/dspace/docs/docbook/directories.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Directories and Files</title>
+    <title><anchor id="docbook-directories.html"/>DSpace System Documentation: Directories and Files</title>
     <section remap="h2">
       <title><anchor id="docbook-directories.html-overview" xreflabel="Overview"/>Overview</title>
       <para>A complete DSpace installation consists of three separate directory trees:</para>
diff --git a/dspace/docs/docbook/functional.xml b/dspace/docs/docbook/functional.xml
index a8963af115..d5d57b5819 100644
--- a/dspace/docs/docbook/functional.xml
+++ b/dspace/docs/docbook/functional.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Functional Overview</title>
+    <title><anchor id="docbook-functional.html"/>DSpace System Documentation: Functional Overview</title>
     <para>The following sections describe the various functional aspects of the DSpace system.</para>
     <section remap="h2">
       <title><anchor id="docbook-functional.html-data_model" xreflabel="Data Model"/>Data Model</title>
@@ -152,7 +152,7 @@ DSpace in one of two ways:"/>Items can be removed from DSpace in one of two ways
       <title><anchor id="docbook-functional.html-plugin" xreflabel="Plugin Manager"/>Plugin Manager</title>
       <para>The PluginManager is a very simple component container. It creates and organizes components (plugins), and helps select a plugin in the cases where there are many possible choices. It also gives some limited control over the lifecycle of a plugin.</para>
       <para>A plugin is defined by a Java interface. The consumer of a plugin asks for its plugin by interface. A Plugin is an instance of any class that implements the plugin interface. It is interchangeable with other implementations, so that any of them may be &quot;plugged in&quot;.</para>
-      <para>The mediafilter is a simple example of a plugin implementation. Refer to the <ulink url="business.html#plugin">Business Logic Layer</ulink> for more details on Plugins.</para>
+      <para>The mediafilter is a simple example of a plugin implementation. Refer to the <link linkend="docbook-business.html-plugin">Business Logic Layer</link> for more details on Plugins.</para>
     </section>
     <section remap="h2">
       <title><anchor id="docbook-functional.html-metadata" xreflabel="Metadata"/>Metadata</title>
diff --git a/dspace/docs/docbook/history.xml b/dspace/docs/docbook/history.xml
index 8f555a19a8..e49daf0d73 100644
--- a/dspace/docs/docbook/history.xml
+++ b/dspace/docs/docbook/history.xml
@@ -1,6 +1,44 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Version History</title>
+    <title><anchor id="docbook-history.html"/>DSpace System Documentation: Version History</title>
+    <section remap="h2">
+      <title><anchor id="docbook-history.html-version1_5_2" xreflabel="Changes in DSpace 1.5.2"/>Changes in DSpace 1.5.2</title>
+      <section remap="h3">
+        <title>General Improvements</title>
+        <itemizedlist>
+          <listitem>
+            <para> TBD</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+      <section remap="h3">
+        <title>Bug fixes and smaller patches</title>
+        <itemizedlist>
+          <listitem>
+            <para> TBD</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+    </section>
+    <section remap="h2">
+      <title><anchor id="docbook-history.html-version1_5_1" xreflabel="Changes in DSpace 1.5.1"/>Changes in DSpace 1.5.1</title>
+      <section remap="h3">
+        <title>General Improvements</title>
+        <itemizedlist>
+          <listitem>
+            <para> TBD</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+      <section remap="h3">
+        <title>Bug fixes and smaller patches</title>
+        <itemizedlist>
+          <listitem>
+            <para> TBD</para>
+          </listitem>
+        </itemizedlist>
+      </section>
+    </section>
     <section remap="h2">
       <title><anchor id="docbook-history.html-version1_5" xreflabel="Changes in DSpace 1.5"/>Changes in DSpace 1.5</title>
       <section remap="h3">
diff --git a/dspace/docs/docbook/index.xml b/dspace/docs/docbook/index.xml
index cdbb644922..ceaa01ebed 100644
--- a/dspace/docs/docbook/index.xml
+++ b/dspace/docs/docbook/index.xml
@@ -1,142 +1,142 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Contents</title>
+    <title><anchor id="docbook-index.html"/>DSpace System Documentation: Contents</title>
     <para>Authors: Robert Tansley, Mick Bass, Margret Branschofsky, Grace Carpenter, Greg McClellan, David Stuve, and others</para>
     <para>For DSpace Version: <emphasis role="bold">1.5</emphasis> (January-2008)</para>
     <para>Documentation for other versions of DSpace are included with the source code.</para>
     <itemizedlist>
       <listitem>
         <para>
-          <ulink url="introduction.html">Introduction</ulink>
+          <link linkend="docbook-introduction.html">Introduction</link>
         </para>
       </listitem>
       <listitem>
         <para>
-          <ulink url="functional.html">Functional Overview</ulink>
+          <link linkend="docbook-functional.html">Functional Overview</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="functional.html#data_model">Data Model</ulink>
+                <link linkend="docbook-functional.html-data_model">Data Model</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#plugin">Plugin Manager</ulink>
+                <link linkend="docbook-functional.html-plugin">Plugin Manager</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#metadata">Metadata</ulink>
+                <link linkend="docbook-functional.html-metadata">Metadata</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#packager">Packager Plugins</ulink>
+                <link linkend="docbook-functional.html-packager">Packager Plugins</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#crosswalk">Crosswalk Plugins</ulink>
+                <link linkend="docbook-functional.html-crosswalk">Crosswalk Plugins</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#epeople">E-people and Groups</ulink>
+                <link linkend="docbook-functional.html-epeople">E-people and Groups</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#authentication">Authentication</ulink>
+                <link linkend="docbook-functional.html-authentication">Authentication</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#auth">Authorization</ulink>
+                <link linkend="docbook-functional.html-auth">Authorization</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#ingest">Ingest Process and Workflow</ulink>
+                <link linkend="docbook-functional.html-ingest">Ingest Process and Workflow</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#supervision">Supervision and Collaboration</ulink>
+                <link linkend="docbook-functional.html-supervision">Supervision and Collaboration</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#handles">Handles</ulink>
+                <link linkend="docbook-functional.html-handles">Handles</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#bitstream_ids">Bitstream &apos;Persistent&apos; Identifiers</ulink>
+                <link linkend="docbook-functional.html-bitstream_ids">Bitstream &apos;Persistent&apos; Identifiers</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#srb">Storage Resource Broker (SRB) Support</ulink>
+                <link linkend="docbook-functional.html-srb">Storage Resource Broker (SRB) Support</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#search_browse">Search and Browse</ulink>
+                <link linkend="docbook-functional.html-search_browse">Search and Browse</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#html">HTML Support</ulink>
+                <link linkend="docbook-functional.html-html">HTML Support</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#oai">OAI Support</ulink>
+                <link linkend="docbook-functional.html-oai">OAI Support</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#openurl">OpenURL Support</ulink>
+                <link linkend="docbook-functional.html-openurl">OpenURL Support</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#creativecommons">Creative Commons Support</ulink>
+                <link linkend="docbook-functional.html-creativecommons">Creative Commons Support</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#subscriptions">Subscriptions</ulink>
+                <link linkend="docbook-functional.html-subscriptions">Subscriptions</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#history">History</ulink>
+                <link linkend="docbook-functional.html-history">History</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#history">Import and Export</ulink>
+                <link linkend="docbook-functional.html-history">Import and Export</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#registration">Registration</ulink>
+                <link linkend="docbook-functional.html-registration">Registration</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#statistics">Statistical Reports</ulink>
+                <link linkend="docbook-functional.html-statistics">Statistical Reports</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="functional.html#checker">Checksum Checker</ulink>
+                <link linkend="docbook-functional.html-checker">Checksum Checker</link>
               </para>
             </listitem>
             <listitem>
             	<para>
-            		<ulink url="functional.html#usage">Usage Instrumentation</ulink>
+            		<link linkend="docbook-functional.html-usage">Usage Instrumentation</link>
             	</para>
             </listitem>
           </itemizedlist>
@@ -144,36 +144,36 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="install.html">Installation</ulink>
+          <link linkend="docbook-install.html">Installation</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="install.html#prerequisite">Prerequisite Software</ulink>
+                <link linkend="docbook-install.html-prerequisite">Prerequisite Software</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="install.html#installsteps">Quick Installation Steps</ulink>
+                <link linkend="docbook-install.html-installsteps">Quick Installation Steps</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="install.html#advancedinstall">Advanced Installation</ulink>
+                <link linkend="docbook-install.html-advancedinstall">Advanced Installation</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="install.html#windows">Windows Installation</ulink>
+                <link linkend="docbook-install.html-windows">Windows Installation</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="install.html#knownbugs">Known Bugs</ulink>
+                <link linkend="docbook-install.html-knownbugs">Known Bugs</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="install.html#problems">Common Problems</ulink>
+                <link linkend="docbook-install.html-problems">Common Problems</link>
               </para>
             </listitem>
           </itemizedlist>
@@ -181,56 +181,56 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="update.html">Updating a DSpace Installation</ulink>
+          <link linkend="docbook-update.html">Updating a DSpace Installation</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="update.html#142_15">Updating from 1.4.2 to 1.5</ulink>
+                <link linkend="docbook-update.html-142_15">Updating from 1.4.2 to 1.5</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#14_141">Updating From 1.4 to 1.4.1</ulink>
+                <link linkend="docbook-update.html-14_141">Updating From 1.4 to 1.4.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#132_14">Updating From 1.3.x to 1.4.x</ulink>
+                <link linkend="docbook-update.html-132_14">Updating From 1.3.x to 1.4.x</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#131_132">Updating From 1.3.1 to 1.3.2</ulink>
+                <link linkend="docbook-update.html-131_132">Updating From 1.3.1 to 1.3.2</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#12_13">Updating From 1.2.x to 1.3.x</ulink>
+                <link linkend="docbook-update.html-12_13">Updating From 1.2.x to 1.3.x</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#121_122">Updating From 1.2.1 to 1.2.2</ulink>
+                <link linkend="docbook-update.html-121_122">Updating From 1.2.1 to 1.2.2</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#12_121">Updating From 1.2 to 1.2.1</ulink>
+                <link linkend="docbook-update.html-12_121">Updating From 1.2 to 1.2.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#11_12">Updating From 1.1 (or 1.1.1) to 1.2</ulink>
+                <link linkend="docbook-update.html-11_12">Updating From 1.1 (or 1.1.1) to 1.2</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#11_111">Updating From 1.1 to 1.1.1</ulink>
+                <link linkend="docbook-update.html-11_111">Updating From 1.1 to 1.1.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="update.html#101_11">Updating From 1.0.1 to 1.1</ulink>
+                <link linkend="docbook-update.html-101_11">Updating From 1.0.1 to 1.1</link>
               </para>
             </listitem>
           </itemizedlist>
@@ -238,7 +238,7 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="configure.html">Configuration and Customization</ulink>
+          <link linkend="docbook-configure.html">Configuration and Customization</link>
         </para>
       </listitem>
       <listitem>
@@ -246,7 +246,7 @@
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="configure.html#general">General Configuration</ulink>
+                <link linkend="docbook-configure.html-general">General Configuration</link>
               </para>
             </listitem>
             <listitem>
@@ -254,71 +254,71 @@
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-dspacecfg">dspace.cfg</ulink>
+                      <link linkend="docbook-configure.html-general-dspacecfg">dspace.cfg</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-search">Search Indexes</ulink>
+                      <link linkend="docbook-configure.html-general-search">Search Indexes</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-browse">Browse Configuration</ulink>
+                      <link linkend="docbook-configure.html-general-browse">Browse Configuration</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-mediafilter">Configuring Media Filters</ulink>
+                      <link linkend="docbook-configure.html-general-mediafilter">Configuring Media Filters</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-email">Email Messages</ulink>
+                      <link linkend="docbook-configure.html-general-email">Email Messages</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-registries">Metadata and Bitstream Format Registries</ulink>
+                      <link linkend="docbook-configure.html-general-registries">Metadata and Bitstream Format Registries</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#general-license">Default Submission License</ulink>
+                      <link linkend="docbook-configure.html-general-license">Default Submission License</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="submission.html">Submission Configuration</ulink>
+                      <link linkend="docbook-submission.html">Submission Configuration</link>
                       <itemizedlist>
                         <listitem>
                           <para>
-                            <ulink url="submission.html#configurationFile">Understanding the Submission Configuration File</ulink>
+                            <link linkend="docbook-submission.html-configurationFile">Understanding the Submission Configuration File</link>
                           </para>
                         </listitem>
                         <listitem>
                           <para>
-                            <ulink url="submission.html#stepOrdering">Reordering/Removing Submission Steps</ulink>
+                            <link linkend="docbook-submission.html-stepOrdering">Reordering/Removing Submission Steps</link>
                           </para>
                         </listitem>
                         <listitem>
                           <para>
-                            <ulink url="submission.html#collectionSubmission">Assigning a custom Submission Process to a Collection</ulink>
+                            <link linkend="docbook-submission.html-collectionSubmission">Assigning a custom Submission Process to a Collection</link>
                           </para>
                         </listitem>
                         <listitem>
                           <para>
-                            <ulink url="submission.html#metadataEntry">Customizing the Metadata-entry pages</ulink>
+                            <link linkend="docbook-submission.html-metadataEntry">Customizing the Metadata-entry pages</link>
                           </para>
                         </listitem>
                         <listitem>
                           <para>
-                            <ulink url="submission.html#uploadStep">Configuring the File Upload step</ulink>
+                            <link linkend="docbook-submission.html-uploadStep">Configuring the File Upload step</link>
                           </para>
                         </listitem>
                         <listitem>
                           <para>
-                            <ulink url="submission.html#createStep">Creating new Submission Steps</ulink>
+                            <link linkend="docbook-submission.html-createStep">Creating new Submission Steps</link>
                           </para>
                         </listitem>
                       </itemizedlist>
@@ -329,26 +329,26 @@
             </listitem>
             <listitem>
               <para>
-                <ulink url="configure.html#xmlui">XMLUI Interface Customizations (Manakin)</ulink>
+                <link linkend="docbook-configure.html-xmlui">XMLUI Interface Customizations (Manakin)</link>
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#xmlui-dspacecfg">dspace.cfg</ulink>
+                      <link linkend="docbook-configure.html-xmlui-dspacecfg">dspace.cfg</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#xmlui-configure">Configuring Themes and Aspects</ulink>
+                      <link linkend="docbook-configure.html-xmlui-configure">Configuring Themes and Aspects</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#xmlui-multilingual">Multilingual Support</ulink>
+                      <link linkend="docbook-configure.html-xmlui-multilingual">Multilingual Support</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#xmlui-newtheme">Creating a New Theme</ulink>
+                      <link linkend="docbook-configure.html-xmlui-newtheme">Creating a New Theme</link>
                     </para>
                   </listitem>
                 </itemizedlist>
@@ -356,7 +356,7 @@
             </listitem>
             <listitem>
               <para>
-                <ulink url="configure.html#jspui">JSPUI Interface Customizations</ulink>
+                <link linkend="docbook-configure.html-jspui">JSPUI Interface Customizations</link>
               </para>
             </listitem>
             <listitem>
@@ -364,22 +364,22 @@
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#jspui-dspacecfg">dspace.cfg</ulink>
+                      <link linkend="docbook-configure.html-jspui-dspacecfg">dspace.cfg</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#jspui-controlledvocabulary">Configuring Controlled Vocabularies</ulink>
+                      <link linkend="docbook-configure.html-jspui-controlledvocabulary">Configuring Controlled Vocabularies</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#jspui-multilingual">Configuring Multilingual Support</ulink>
+                      <link linkend="docbook-configure.html-jspui-multilingual">Configuring Multilingual Support</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#jspui-jsp">Customizing the JSP Pages</ulink>
+                      <link linkend="docbook-configure.html-jspui-jsp">Customizing the JSP Pages</link>
                     </para>
                   </listitem>
                 </itemizedlist>
@@ -387,7 +387,7 @@
             </listitem>
             <listitem>
               <para>
-                <ulink url="configure.html#advanced">Advanced DSpace Customizations</ulink>
+                <link linkend="docbook-configure.html-advanced">Advanced DSpace Customizations</link>
               </para>
             </listitem>
             <listitem>
@@ -395,47 +395,47 @@
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#checksum">Checksum Checker</ulink>
+                      <link linkend="docbook-configure.html-checksum">Checksum Checker</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#authentication">Custom Authentication</ulink>
+                      <link linkend="docbook-configure.html-authentication">Custom Authentication</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#statistics">Configuring Statistical Reports</ulink>
+                      <link linkend="docbook-configure.html-statistics">Configuring Statistical Reports</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#oai">Activating Additional OAI-PMH Crosswalks</ulink>
+                      <link linkend="docbook-configure.html-oai">Activating Additional OAI-PMH Crosswalks</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#packager">Configuring Packager Plugins</ulink>
+                      <link linkend="docbook-configure.html-packager">Configuring Packager Plugins</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#crosswalk">Configuring Crosswalk Plugins</ulink>
+                      <link linkend="docbook-configure.html-crosswalk">Configuring Crosswalk Plugins</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#mediafilters">Creating new Media/Format Filters</ulink>
+                      <link linkend="docbook-configure.html-mediafilters">Creating new Media/Format Filters</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#templates">Configuration Files for Other Applications</ulink>
+                      <link linkend="docbook-configure.html-templates">Configuration Files for Other Applications</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="configure.html#browse-index">Browse Index Creation</ulink>
+                      <link linkend="docbook-configure.html-browse-index">Browse Index Creation</link>
                     </para>
                   </listitem>
                 </itemizedlist>
@@ -446,26 +446,26 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="directories.html">Directories and Files</ulink>
+          <link linkend="docbook-directories.html">Directories and Files</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="directories.html#sourcedir">Source Directory Layout</ulink>
+                <link linkend="docbook-directories.html-sourcedir">Source Directory Layout</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="directories.html#installdir">Installed Directory Layout</ulink>
+                <link linkend="docbook-directories.html-installdir">Installed Directory Layout</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="directories.html#webapp">Contents of Web Application</ulink>
+                <link linkend="docbook-directories.html-webapp">Contents of Web Application</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="directories.html#logfiles">Log Files</ulink>
+                <link linkend="docbook-directories.html-logfiles">Log Files</link>
               </para>
             </listitem>
           </itemizedlist>
@@ -473,25 +473,25 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="architecture.html">Architecture</ulink>
+          <link linkend="docbook-architecture.html">Architecture</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="architecture.html#overview">Overview</ulink>
+                <link linkend="docbook-architecture.html-overview">Overview</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="storage.html">Storage Layer</ulink>
+                <link linkend="docbook-storage.html">Storage Layer</link>
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="storage.html#rdbms">RDBMS</ulink>
+                      <link linkend="docbook-storage.html-rdbms">RDBMS</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="storage.html#bitstreams">Bitstream Store</ulink>
+                      <link linkend="docbook-storage.html-bitstreams">Bitstream Store</link>
                     </para>
                   </listitem>
                 </itemizedlist>
@@ -499,61 +499,61 @@
             </listitem>
             <listitem>
               <para>
-                <ulink url="business.html">Business Logic Layer</ulink>
+                <link linkend="docbook-business.html">Business Logic Layer</link>
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="business.html#core">Core Classes</ulink>
+                      <link linkend="docbook-business.html-core">Core Classes</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#content">Content Management API</ulink>
+                      <link linkend="docbook-business.html-content">Content Management API</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#plugin">Plugin Manager</ulink>
+                      <link linkend="docbook-business.html-plugin">Plugin Manager</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#workflow">Workflow System</ulink>
+                      <link linkend="docbook-business.html-workflow">Workflow System</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#administer">Administration Toolkit</ulink>
+                      <link linkend="docbook-business.html-administer">Administration Toolkit</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#eperson">E-person/Group Manager</ulink>
+                      <link linkend="docbook-business.html-eperson">E-person/Group Manager</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#authorize">Authorization</ulink>
+                      <link linkend="docbook-business.html-authorize">Authorization</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#handle">Handle Manager/Handle Plugin</ulink>
+                      <link linkend="docbook-business.html-handle">Handle Manager/Handle Plugin</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#search">Search</ulink>
+                      <link linkend="docbook-business.html-search">Search</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#browse">Browse API</ulink>
+                      <link linkend="docbook-business.html-browse">Browse API</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="business.html#history">History Recorder</ulink>
+                      <link linkend="docbook-business.html-history">History Recorder</link>
                     </para>
                   </listitem>
                 </itemizedlist>
@@ -561,56 +561,56 @@
             </listitem>
             <listitem>
               <para>
-                <ulink url="application.html">Application Layer</ulink>
+                <link linkend="docbook-application.html">Application Layer</link>
                 <itemizedlist>
                   <listitem>
                     <para>
-                      <ulink url="application.html#webui">Web User Interface</ulink>
+                      <link linkend="docbook-application.html-webui">Web User Interface</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#oai">OAI-PMH Data Provider</ulink>
+                      <link linkend="docbook-application.html-oai">OAI-PMH Data Provider</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#structbuilder">Community and Collection Structure Importer</ulink>
+                      <link linkend="docbook-application.html-structbuilder">Community and Collection Structure Importer</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#packager">Package Importer and Exporter</ulink>
+                      <link linkend="docbook-application.html-packager">Package Importer and Exporter</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#itemimporter">Item Importer and Exporter</ulink>
+                      <link linkend="docbook-application.html-itemimporter">Item Importer and Exporter</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#transferitem">Transferring Items Between DSpace Instances</ulink>
+                      <link linkend="docbook-application.html-transferitem">Transferring Items Between DSpace Instances</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#registration">Registering (Not Importing) Bitstreams</ulink>
+                      <link linkend="docbook-application.html-registration">Registering (Not Importing) Bitstreams</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#mets">METS Tools</ulink>
+                      <link linkend="docbook-application.html-mets">METS Tools</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#mediafilters">Media Filters</ulink>
+                      <link linkend="docbook-application.html-mediafilters">Media Filters</link>
                     </para>
                   </listitem>
                   <listitem>
                     <para>
-                      <ulink url="application.html#filiator">Sub-Community Management</ulink>
+                      <link linkend="docbook-application.html-filiator">Sub-Community Management</link>
                     </para>
                   </listitem>
                 </itemizedlist>
@@ -621,41 +621,41 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="DRISchemaReference.html">DRI Schema Reference</ulink>
+          <link linkend="docbook-DRISchemaReference.html">DRI Schema Reference</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#Introduction">Introduction</ulink>
+                <link linkend="docbook-DRISchemaReference.html-Introduction">Introduction</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#DRI_in_Manakin">DRI in Manakin</ulink>
+                <link linkend="docbook-DRISchemaReference.html-DRI_in_Manakin">DRI in Manakin</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#Common_Design_Patterns">Common Design Patterns</ulink>
+                <link linkend="docbook-DRISchemaReference.html-Common_Design_Patterns">Common Design Patterns</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#Schema_Overview">Schema Overview</ulink>
+                <link linkend="docbook-DRISchemaReference.html-Schema_Overview">Schema Overview</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#Merging_of_DRI_Documents">Merging of DRI Documents</ulink>
+                <link linkend="docbook-DRISchemaReference.html-Merging_of_DRI_Documents">Merging of DRI Documents</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#Version_Changes">Version Changes</ulink>
+                <link linkend="docbook-DRISchemaReference.html-Version_Changes">Version Changes</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="DRISchemaReference.html#Element_Reference">Element Reference</ulink>
+                <link linkend="docbook-DRISchemaReference.html-Element_Reference">Element Reference</link>
               </para>
             </listitem>
           </itemizedlist>
@@ -663,61 +663,61 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="history.html">Version History</ulink>
+          <link linkend="docbook-history.html">Version History</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="history.html#version1_5">Changes in DSpace 1.5</ulink>
+                <link linkend="docbook-history.html-version1_5">Changes in DSpace 1.5</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_4_1">Changes in DSpace 1.4.1</ulink>
+                <link linkend="docbook-history.html-version1_4_1">Changes in DSpace 1.4.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_4">Changes in DSpace 1.4</ulink>
+                <link linkend="docbook-history.html-version1_4">Changes in DSpace 1.4</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_3_2">Changes in DSpace 1.3.2</ulink>
+                <link linkend="docbook-history.html-version1_3_2">Changes in DSpace 1.3.2</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_3_1">Changes in DSpace 1.3.1</ulink>
+                <link linkend="docbook-history.html-version1_3_1">Changes in DSpace 1.3.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_3">Changes in DSpace 1.3</ulink>
+                <link linkend="docbook-history.html-version1_3">Changes in DSpace 1.3</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_2_2">Changes in DSpace 1.2.2</ulink>
+                <link linkend="docbook-history.html-version1_2_2">Changes in DSpace 1.2.2</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_2_1">Changes in DSpace 1.2.1</ulink>
+                <link linkend="docbook-history.html-version1_2_1">Changes in DSpace 1.2.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_2">Changes in DSpace 1.2</ulink>
+                <link linkend="docbook-history.html-version1_2">Changes in DSpace 1.2</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_1_1">Changes in DSpace 1.1.1</ulink>
+                <link linkend="docbook-history.html-version1_1_1">Changes in DSpace 1.1.1</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="history.html#version1_1">Changes in DSpace 1.1</ulink>
+                <link linkend="docbook-history.html-version1_1">Changes in DSpace 1.1</link>
               </para>
             </listitem>
           </itemizedlist>
@@ -725,16 +725,16 @@
       </listitem>
       <listitem>
         <para>
-          <ulink url="appendix.html">Appendices</ulink>
+          <link linkend="docbook-appendix.html">Appendices</link>
           <itemizedlist>
             <listitem>
               <para>
-                <ulink url="appendix.html#dublincoreregistry">Default Dublin Core Metadata Registry</ulink>
+                <link linkend="docbook-appendix.html-dublincoreregistry">Default Dublin Core Metadata Registry</link>
               </para>
             </listitem>
             <listitem>
               <para>
-                <ulink url="appendix.html#bitstreamformatregistry">Default Bitstream Format Registry</ulink>
+                <link linkend="docbook-appendix.html-bitstreamformatregistry">Default Bitstream Format Registry</link>
               </para>
             </listitem>
           </itemizedlist>
diff --git a/dspace/docs/docbook/install.xml b/dspace/docs/docbook/install.xml
index 5ea69abc7c..a7bafd46ad 100644
--- a/dspace/docs/docbook/install.xml
+++ b/dspace/docs/docbook/install.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Installation</title>
+    <title><anchor id="docbook-install.html"/>DSpace System Documentation: Installation</title>
     <section remap="h2">
       <title><anchor id="docbook-install.html-prerequisite" xreflabel="Prerequisite Software"/>Prerequisite Software</title>
       <para>The list below describes the third-party components and tools you&apos;ll need to run a DSpace server. These are just guidelines. Since DSpace is built on open source, standards-based tools, there are numerous other possibilities and setups.</para>
@@ -251,7 +251,7 @@ dspace-&lt;version&gt;-src-release.zip )"/>Source Release ( dspace-&lt;version&g
  to <literal>[tomcat]/webapps/</literal> (with <literal>[tomcat]</literal> being wherever you installed Tomcat--also known as <literal>$CATALINA_HOME</literal>).</para>
           </listitem>
         </orderedlist>
-        <para>For details on the contents of these separate directory trees, refer to <ulink url="directories.html">directories.html</ulink>. <emphasis>Note that the <literal>[dspace-source]</literal> and <literal>[dspace]</literal> directories are always separate!</emphasis></para>
+        <para>For details on the contents of these separate directory trees, refer to <link linkend="docbook-directories.html">directories.html</link>. <emphasis>Note that the <literal>[dspace-source]</literal> and <literal>[dspace]</literal> directories are always separate!</emphasis></para>
       </section>
       <section remap="h3">
         <title><anchor id="docbook-install.html-installsteps" xreflabel="Installation"/>Installation</title>
@@ -455,7 +455,7 @@ crontab -e
 0 2 * * * [dspace]/bin/stat-report-monthly
 </screen>
         <para>Obviously, you should choose execution times which are most useful to you, and you should ensure that the <literal>-report-</literal> scripts run a short while after the analysis scripts to give them time to complete (a run of around 8 months worth of logs can take around 25 seconds to complete); the resulting reports will let you know how long analysis took and you can adjust your cron times accordingly.</para>
-        <para>For information on customising the output of this see <ulink url="configure.html#statistics">configuring system statistical reports</ulink>.</para>
+        <para>For information on customising the output of this see <link linkend="docbook-configure.html-statistics">configuring system statistical reports</link>.</para>
       </section>
       <section remap="h3">
         <title>Multilingual Installation</title>
@@ -463,7 +463,7 @@ crontab -e
         <para><literal>default.locale</literal>, e. g. default.locale = en</para>
         <para><literal>webui.supported locales</literal>, e. g. webui.supported.locales = en, de</para>
         <para> The Locales might have the form country, country_language, country_language_variant.</para>
-        <para> Accoding to the languages you wish to support, you have to make sure, that all the i18n related files are available see the <ulink url="configure.html#multilingualui">Multilingual User Interface Configuring MultiLingual Support</ulink> section for the JSPUI or the Multilingual Support for XMLUI in the configuration documentation. </para>
+        <para> Accoding to the languages you wish to support, you have to make sure, that all the i18n related files are available see the <link linkend="docbook-configure.html-multilingualui">Multilingual User Interface Configuring MultiLingual Support</link> section for the JSPUI or the Multilingual Support for XMLUI in the configuration documentation. </para>
       </section>
       <section remap="h3">
         <title><anchor id="docbook-install.html-https" xreflabel="DSpace over HTTPS"/>DSpace over HTTPS</title>
@@ -494,7 +494,7 @@ crontab -e
 </screen>
                 </listitem>
                 <listitem>
-                  <para> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <ulink url="configure.html#authenticate">configuration section</ulink> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <literal>client1.pem</literal>:</para>
+                  <para> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <link linkend="docbook-configure.html-authenticate">configuration section</link> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <literal>client1.pem</literal>:</para>
                   <screen>
  $JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
 	-trustcacerts -keystore $CATALINA_BASE/conf/keystore  -alias client1
@@ -587,7 +587,7 @@ $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keysize
                   <para>When answering the questions to identify the certificate, be sure to respond to &quot;First and last name&quot; with the fully-qualified domain name of your server (e.g. <literal>test-dspace.myuni.edu</literal>). The other questions are not important.</para>
                 </listitem>
                 <listitem>
-                  <para> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <ulink url="configure.html#authenticate">configuration section</ulink> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <literal>client1.pem</literal>:</para>
+                  <para> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <link linkend="docbook-configure.html-authenticate">configuration section</link> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <literal>client1.pem</literal>:</para>
                   <screen>
  $JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
 	-trustcacerts -keystore $CATALINA_BASE/conf/keystore  -alias client1
diff --git a/dspace/docs/docbook/introduction.xml b/dspace/docs/docbook/introduction.xml
index 9de005648c..76d5c3ede1 100644
--- a/dspace/docs/docbook/introduction.xml
+++ b/dspace/docs/docbook/introduction.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Introduction</title>
+    <title><anchor id="docbook-introduction.html"/>DSpace System Documentation: Introduction</title>
     <para>DSpace is an open source software platform that enables organisations to:</para>
     <itemizedlist>
       <listitem>
@@ -13,9 +13,9 @@
         <para> preserve digital assets over the long term</para>
       </listitem>
     </itemizedlist>
-    <para>This system documentation includes <ulink url="functional.html">a functional overview of the system</ulink>, which is a good introduction to the capabilities of the system, and should be readable by non-technical folk. Everyone should read this section first because it introduces some terminology used throughout the rest of the documentation.</para>
-    <para>For people actually running a DSpace service, there is <ulink url="install.html">an installation guide</ulink>, and sections on <ulink url="configure.html">configuration</ulink> and <ulink url="directories.html">the directory structure</ulink>. Note that as of DSpace 1.2, the administration user interface guide is now on-line help available from within the DSpace system.</para>
-    <para>Finally, for those interested in the details of how DSpace works, and those potentially interested in modifying the code for their own purposes, there is <ulink url="architecture.html">a detailed architecture and design section</ulink>.</para>
+    <para>This system documentation includes <link linkend="docbook-functional.html">a functional overview of the system</link>, which is a good introduction to the capabilities of the system, and should be readable by non-technical folk. Everyone should read this section first because it introduces some terminology used throughout the rest of the documentation.</para>
+    <para>For people actually running a DSpace service, there is <link linkend="docbook-install.html">an installation guide</link>, and sections on <link linkend="docbook-configure.html">configuration</link> and <link linkend="docbook-directories.html">the directory structure</link>. Note that as of DSpace 1.2, the administration user interface guide is now on-line help available from within the DSpace system.</para>
+    <para>Finally, for those interested in the details of how DSpace works, and those potentially interested in modifying the code for their own purposes, there is <link linkend="docbook-architecture.html">a detailed architecture and design section</link>.</para>
     <para>Other good sources of information are:</para>
     <itemizedlist>
       <listitem>
diff --git a/dspace/docs/docbook/storage.xml b/dspace/docs/docbook/storage.xml
index be4cd5fc82..393fc72fb8 100644
--- a/dspace/docs/docbook/storage.xml
+++ b/dspace/docs/docbook/storage.xml
@@ -1,8 +1,8 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Storage Layer</title>
+    <title><anchor id="docbook-storage.html"/>DSpace System Documentation: Storage Layer</title>
     <para>
-      <ulink url="architecture.html">Back to architecture overview</ulink>
+      <link linkend="docbook-architecture.html">Back to architecture overview</link>
     </para>
     <section remap="h2">
       <title><anchor id="docbook-storage.html-rdbms" xreflabel="RDBMS"/>RDBMS</title>
@@ -12,9 +12,9 @@
       </para>
       <para>Most of the functionality that DSpace uses can be offered by any standard SQL database that supports transactions. Presently, the browse indices use some features specific to <ulink url="http://www.postgresql.org/">PostgreSQL</ulink> and <ulink url="http://www.oracle.com/database/">Oracle</ulink>, so some modification to the code would be needed before DSpace would function fully with an alternative database back-end.</para>
       <para>The <literal>org.dspace.storage.rdbms</literal> package provides access to an SQL database in a somewhat simpler form than using JDBC directly. The main class is <literal>DatabaseManager</literal>, which executes SQL queries and returns <literal>TableRow</literal> or <literal>TableRowIterator</literal> objects. The <literal>InitializeDatabase</literal> class is used to load SQL into the database via JDBC, for example to set up the schema.</para>
-      <para>All calls to the <literal>Database Manager</literal> require a <ulink url="business.html#core">DSpace <literal>Context</literal> object</ulink>. Example use of the database manager API is given in the <literal>org.dspace.storage.rdbms</literal> package Javadoc.</para>
+      <para>All calls to the <literal>Database Manager</literal> require a <link linkend="docbook-business.html-core">DSpace <literal>Context</literal> object</link>. Example use of the database manager API is given in the <literal>org.dspace.storage.rdbms</literal> package Javadoc.</para>
       <para>The database schema used by DSpace (for PostgreSQL) is stored in <literal>[dspace-source]/dspace/etc/database_schema.sql</literal> in the source distribution. It is stored in the form of SQL that can be fed straight into the DBMS to construct the database. The schema SQL file also directly creates two e-person groups in the database that are required for the system to function properly.</para>
-      <para>Also in <literal>[dspace-source]/dspace/etc</literal> are various SQL files called <literal>database_schema_1x_1y</literal>. These contain the necessary SQL commands to update a live DSpace database from version 1.<literal>x</literal> to 1.<literal>y</literal>. Note that this might not be the only part of an upgrade process: see <ulink url="update.html">Updating a DSpace Installation</ulink> for details.</para>
+      <para>Also in <literal>[dspace-source]/dspace/etc</literal> are various SQL files called <literal>database_schema_1x_1y</literal>. These contain the necessary SQL commands to update a live DSpace database from version 1.<literal>x</literal> to 1.<literal>y</literal>. Note that this might not be the only part of an upgrade process: see <link linkend="docbook-update.html">Updating a DSpace Installation</link> for details.</para>
       <para>The DSpace database code uses an SQL function <literal>getnextid</literal> to assign primary keys to newly created rows. This SQL function must be safe to use if several JVMs are accessing the database at once; for example, the Web UI might be creating new rows in the database at the same time as the batch item importer. The PostgreSQL-specific implementation of the method uses <literal>SEQUENCES</literal> for each table in order to create new IDs. If an alternative database backend were to be used, the implementation of <literal>getnextid</literal> could be updated to operate with that specific DBMS.</para>
       <para>The <literal>etc</literal> directory in the source distribution contains two further SQL files. <literal>clean-database.sql</literal> contains the SQL necessary to completely clean out the database, so use with caution! The Ant target <literal>clean_database</literal> can be used to execute this. <literal>update-sequences.sql</literal> contains SQL to reset the primary key generation sequences to appropriate values. You&apos;d need to do this if, for example, you&apos;re restoring a backup database dump which creates rows with specific primary keys already defined. In such a case, the sequences would allocate primary keys that were already used.</para>
       <para>Versions of the <literal>*.sql*</literal> files for Oracle are stored in <literal>[dspace-source]/dspace/etc/oracle</literal>. These need to be copied over their PostgreSQL counterparts in <literal>[dspace-source]/dspace/etc</literal> prior to installation.</para>
@@ -104,9 +104,9 @@ psql -U dspace -f <emphasis>
       <para>DSpace offers two means for storing content. The first is in the file system on the server. The second is using <ulink url="http://www.sdsc.edu/srb">SRB (Storage Resource Broker)</ulink>. Both are achieved using a simple, lightweight API.</para>
       <para>SRB is purely an option but may be used in lieu of the server&apos;s file system or in addition to the file system. Without going into a full description, SRB is a very robust, sophisticated storage manager that offers essentially unlimited storage and straightforward means to replicate (in simple terms, backup) the content on other local or remote storage resources.</para>
       <para>The terms &quot;store&quot;, &quot;retrieve&quot;, &quot;in the system&quot;, &quot;storage&quot;, and so forth, used below can refer to storage in the file system on the server (&quot;traditional&quot;) or in SRB.</para>
-      <para>The <literal>BitstreamStorageManager</literal> provides low-level access to bitstreams stored in the system. In general, it should not be used directly; instead, use the <literal>Bitstream</literal> object in the <ulink url="business.html#content">content management API</ulink> since that encapsulated authorization and other metadata to do with a bitstream that are not maintained by the <literal>BitstreamStorageManager</literal>.</para>
+      <para>The <literal>BitstreamStorageManager</literal> provides low-level access to bitstreams stored in the system. In general, it should not be used directly; instead, use the <literal>Bitstream</literal> object in the <link linkend="docbook-business.html-content">content management API</link> since that encapsulated authorization and other metadata to do with a bitstream that are not maintained by the <literal>BitstreamStorageManager</literal>.</para>
       <para>The bitstream storage manager provides three methods that store, retrieve and delete bitstreams. Bitstreams are referred to by their &apos;ID&apos;; that is the primary key <literal>bitstream_id</literal> column of the corresponding row in the database.</para>
-      <para>As of DSpace version 1.1, there can be multiple bitstream stores. Each of these bitstream stores can be traditional storage or SRB storage. This means that the potential storage of a DSpace system is not bound by the maximum size of a single disk or file system and also that traditional and SRB storage can be combined in one DSpace installation. Both traditional and SRB storage are specified by <ulink url="configure.html">configuration parameters</ulink>. Also see Configuring the Bitstream Store below.</para>
+      <para>As of DSpace version 1.1, there can be multiple bitstream stores. Each of these bitstream stores can be traditional storage or SRB storage. This means that the potential storage of a DSpace system is not bound by the maximum size of a single disk or file system and also that traditional and SRB storage can be combined in one DSpace installation. Both traditional and SRB storage are specified by <link linkend="docbook-configure.html">configuration parameters</link>. Also see Configuring the Bitstream Store below.</para>
       <para>Stores are numbered, starting with zero, then counting upwards. Each bitstream entry in the database has a store number, used to retrieve the bitstream when required.</para>
       <para>At the moment, the store in which new bitstreams are placed is decided using a configuration parameter, and there is no provision for moving bitstreams between stores. Administrative tools for manipulating bitstreams and stores will be provided in future releases. Right now you can move a whole store (e.g. you could move store number 1 from <literal>/localdisk/store</literal> to <literal>/fs/anotherdisk/store</literal> but it would still have to be store number 1 and have the exact same contents.</para>
       <para>Bitstreams also have an 38-digit internal ID, different from the primary key ID of the bitstream table row. This is not visible or used outside of the bitstream storage manager. It is used to determine the exact location (relative to the relevant store directory) that the bitstream is stored in traditional or SRB storage. The first three pairs of digits are the directory path that the bitstream is stored under. The bitstream is stored in a file with the internal ID as the filename.</para>
@@ -165,7 +165,7 @@ psql -U dspace -f <emphasis>
       <para>The bitstream storage manager is fully transaction-safe. In order to implement transaction-safety, the following algorithm is used to store bitstreams:</para>
       <orderedlist>
         <listitem>
-          <para> A database connection is created, separately from the currently active connection in the <ulink url="business.html#core">current DSpace context</ulink>.</para>
+          <para> A database connection is created, separately from the currently active connection in the <link linkend="docbook-business.html-core">current DSpace context</link>.</para>
         </listitem>
         <listitem>
           <para> An unique internal identifier (separate from the database primary key) is generated.</para>
diff --git a/dspace/docs/docbook/submission.xml b/dspace/docs/docbook/submission.xml
index 9c3053104b..63a48968d0 100644
--- a/dspace/docs/docbook/submission.xml
+++ b/dspace/docs/docbook/submission.xml
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>Customizing and Configuring Submission User Interface</title>
+    <title><anchor id="docbook-submission.html"/>Customizing and Configuring Submission User Interface</title>
     <para>This page explains various customization and configuration options that are available within DSpace for the Item Submission user interface.</para>
     <para>
       <anchor id="docbook-submission.html-configurationFile"/>
@@ -491,7 +491,7 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
               </varlistentry>
             </variablelist>
             <para>Look at the example <literal>input-forms.xml</literal> and experiment with a a trial custom form to learn this specification language thoroughly. It is a very simple way to express the layout of data-entry forms, but the only way to learn all its subtleties is to use it.</para>
-            <para>For the use of controlled vocabularies see the <ulink url="configure.html#controlledvocabulary">Configuring Controlled Vocabularies</ulink> section.</para>
+            <para>For the use of controlled vocabularies see the <link linkend="docbook-configure.html-controlledvocabulary">Configuring Controlled Vocabularies</link> section.</para>
           </section>
           <section remap="h5">
             <title>Automatically Elided Fields</title>
@@ -676,7 +676,7 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
           <para> (<emphasis role="bold">Required</emphasis>) Add a valid Step Definition to the <literal>item-submission.xml</literal> configuration file. </para>
           <itemizedlist>
             <listitem>
-              <para> This may also require that you add an I18N (Internationalization) key for this step&apos;s <literal>heading</literal>. See the sections on <ulink url="configure.html#jspui-multilingual">Configuring Multilingual Support for JSPUI</ulink> or <ulink url="configure.html#xmlui-multilingual">Configuring Multilingual Support for XMLUI</ulink> for more details.</para>
+              <para> This may also require that you add an I18N (Internationalization) key for this step&apos;s <literal>heading</literal>. See the sections on <link linkend="docbook-configure.html-jspui-multilingual">Configuring Multilingual Support for JSPUI</link> or <link linkend="docbook-configure.html#xmlui-multilingual">Configuring Multilingual Support for XMLUI</link> for more details.</para>
             </listitem>
             <listitem>
               <para> For more information on <literal>&lt;step&gt;</literal> definitions within the <literal>item-submission.xml</literal>, see the section above on <anchor id="docbook-submission.html--stepDefinitions.1" xreflabel="Defining Steps
diff --git a/dspace/docs/docbook/update.xml b/dspace/docs/docbook/update.xml
index e829a021dc..91efa99908 100644
--- a/dspace/docs/docbook/update.xml
+++ b/dspace/docs/docbook/update.xml
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='UTF-8'?>
   <chapter remap="h1">
-    <title>DSpace System Documentation: Updating a DSpace Installation</title>
-    <para>This section describes how to update a DSpace installation from one version to the next. Details of the differences between the functionality of each version are given in the <ulink url="history.html">Version History</ulink> section.</para>
+    <title><anchor id="docbook-update.html"/>DSpace System Documentation: Updating a DSpace Installation</title>
+    <para>This section describes how to update a DSpace installation from one version to the next. Details of the differences between the functionality of each version are given in the <link linkend="docbook-history.html">Version History</link> section.</para>
     <section remap="h2">
       <title><anchor id="docbook-update.html-142_15" xreflabel="Updating From 1.4.2 to 1.5"/>Updating From 1.4.2 to 1.5</title>
       <para>The changes in DSpace 1.5 are significant and wide spread involving database schema upgrades, code restructuring, completely new user and programatic interfaces, and new build system.</para>
@@ -28,7 +28,7 @@
           <para><emphasis role="bold">Download DSpace 1.5</emphasis> Get the new DSpace 1.5 source code either as a download from <ulink url="#">SourceForge</ulink> or check it out directly from the <ulink url="#">SVN code repository</ulink>. If you downloaded DSpace do not unpack it on top of your existing installation.</para>
         </listitem>
         <listitem>
-          <para><emphasis role="bold">Build DSpace</emphasis> The build process has radically changed for DSpace 1.5. With this new release the build system has moved to a maven-based system enabling the various projects (JSPUI, XMLUI, OAI, and Core API) into separate projects. See the <ulink url="install.html">Installation section</ulink> for more information on building DSpace using the new maven-based build system. Run the following commands to compile DSpace.</para>
+          <para><emphasis role="bold">Build DSpace</emphasis> The build process has radically changed for DSpace 1.5. With this new release the build system has moved to a maven-based system enabling the various projects (JSPUI, XMLUI, OAI, and Core API) into separate projects. See the <link linkend="docbook-install.html">Installation section</link> for more information on building DSpace using the new maven-based build system. Run the following commands to compile DSpace.</para>
           <screen>
   cd [dspace-source]/dspace/;
   mvn package
@@ -181,7 +181,7 @@ cp [dspace-source]/dspace/config/emails/registration_notify
           </itemizedlist>
         </listitem>
         <listitem>
-          <para><emphasis role="bold">Apply any customizations</emphasis> If you have made any local customizations to your DSpace installation they will need to be migrated over to the new DSpace. Commonly these modifications are made to &quot;JSP&quot; pages located inside the <literal>[dspace 1.4.2]/jsp/local</literal> directory. These should be moved <literal>[dspace-source]/dspace/modules/jspui/src/main/webapp/</literal> in the new build structure. See <ulink url="configure.html#jspui-jsp">Customizing the JSP Pages</ulink> for more information.</para>
+          <para><emphasis role="bold">Apply any customizations</emphasis> If you have made any local customizations to your DSpace installation they will need to be migrated over to the new DSpace. Commonly these modifications are made to &quot;JSP&quot; pages located inside the <literal>[dspace 1.4.2]/jsp/local</literal> directory. These should be moved <literal>[dspace-source]/dspace/modules/jspui/src/main/webapp/</literal> in the new build structure. See <link linkend="docbook-configure.html-jspui-jsp">Customizing the JSP Pages</link> for more information.</para>
         </listitem>
         <listitem>
           <para><emphasis role="bold">Update DSpace</emphasis> Update the DSpace installed directory with new code and libraries. Inside the <literal>[dspace-source]/dspace/target/dspace-1.5-build.dir/</literal> directory run:</para>
@@ -440,7 +440,7 @@ search.index.1 = title:dc.title.alternative
 </screen>
             </listitem>
             <listitem>
-              <para> If you use LDAP or X509 authentication, you&apos;ll need to add <literal>org.dspace.eperson.LDAPAuthentication</literal> or <literal>org.dspace.eperson.X509Authentication</literal> respectively. See also <ulink url="configure.html#authenticate">configuring custom authentication code</ulink>.</para>
+              <para> If you use LDAP or X509 authentication, you&apos;ll need to add <literal>org.dspace.eperson.LDAPAuthentication</literal> or <literal>org.dspace.eperson.X509Authentication</literal> respectively. See also <link linkend="docbook-configure.html-authenticate">configuring custom authentication code</link>.</para>
             </listitem>
             <listitem>
               <para> If you have custom Media Filters, note that these are now configured through <literal>dspace.cfg</literal> (instead of <literal>mediafilter.cfg</literal> which is obsolete.)</para>
@@ -600,7 +600,7 @@ report.dir = /dspace/reports/
           </para>
         </listitem>
         <listitem>
-          <para> Customise the stat generating statistics as per the instructions in <ulink url="configure.html#statistics">System Statistical Reports</ulink></para>
+          <para> Customise the stat generating statistics as per the instructions in <link linkend="docbook-configure.html-statistics">System Statistical Reports</link></para>
         </listitem>
         <listitem>
           <para> Initialise the statistics using:</para>
@@ -653,7 +653,7 @@ cp postgresql.jar <emphasis> [dspace-1.2.2-source]</emphasis>/lib
           <para> Take down Tomcat (or whichever servlet container you&apos;re using).</para>
         </listitem>
         <listitem>
-          <para> Your &apos;localized&apos; JSPs (those in jsp/local) now need to be maintained in the <emphasis>source</emphasis> directory. If you have locally modified JSPs in your <literal>[dspace]/jsp/local</literal> directory, you might like to merge the changes in the new 1.2.2 versions into your locally modified ones. You can use the <literal>diff</literal> command to compare the 1.2.1 and 1.2.2 versions to do this. Also see <ulink url="history.html#jsp-changes-1_2_1-1_2_2">the version history</ulink> for a list of modified JSPs.</para>
+          <para> Your &apos;localized&apos; JSPs (those in jsp/local) now need to be maintained in the <emphasis>source</emphasis> directory. If you have locally modified JSPs in your <literal>[dspace]/jsp/local</literal> directory, you might like to merge the changes in the new 1.2.2 versions into your locally modified ones. You can use the <literal>diff</literal> command to compare the 1.2.1 and 1.2.2 versions to do this. Also see <link linkend="docbook-history.html-jsp-changes-1_2_1-1_2_2">the version history</link> for a list of modified JSPs.</para>
         </listitem>
         <listitem>
           <para> You need to add a new parameter to your <literal>[dspace]/dspace.cfg</literal> for configurable fulltext indexing</para>
@@ -708,7 +708,7 @@ cp postgresql.jar <emphasis> [dspace-1.2.1-source]</emphasis>/lib
           <para> Take down Tomcat (or whichever servlet container you&apos;re using).</para>
         </listitem>
         <listitem>
-          <para> Your &apos;localized&apos; JSPs (those in jsp/local) now need to be maintained in the <emphasis>source</emphasis> directory. If you have locally modified JSPs in your <literal>[dspace]/jsp/local</literal> directory, you might like to merge the changes in the new 1.2.1 versions into your locally modified ones. You can use the <literal>diff</literal> command to compare the 1.2 and 1.2.1 versions to do this. Also see <ulink url="history.html#jsp-changes-1_2-1_2_1">the version history</ulink> for a list of modified JSPs.</para>
+          <para> Your &apos;localized&apos; JSPs (those in jsp/local) now need to be maintained in the <emphasis>source</emphasis> directory. If you have locally modified JSPs in your <literal>[dspace]/jsp/local</literal> directory, you might like to merge the changes in the new 1.2.1 versions into your locally modified ones. You can use the <literal>diff</literal> command to compare the 1.2 and 1.2.1 versions to do this. Also see <link linkend="docbook-history.html-jsp-changes-1_2-1_2_1">the version history</link> for a list of modified JSPs.</para>
         </listitem>
         <listitem>
           <para> You need to add a few new parameters to your <literal>[dspace]/dspace.cfg</literal> for browse/search and item thumbnails display, and for configurable DC metadata fields to be indexed.</para>
@@ -789,7 +789,7 @@ cp <emphasis> [dspace-1.2.1-source]</emphasis>/build/*.war <emphasis>
           <para> Get the new DSpace 1.2 source code from <ulink url="http://sourceforge.net/projects/dspace/">the DSpace page on SourceForge</ulink> and unpack it somewhere. Do not unpack it on top of your existing installation!!</para>
         </listitem>
         <listitem>
-          <para> Copy the <ulink url="install.html#javalibs">required Java libraries</ulink> that we couldn&apos;t include in the bundle to the source tree. For example:</para>
+          <para> Copy the <link linkend="docbook-install.html-javalibs">required Java libraries</link> that we couldn&apos;t include in the bundle to the source tree. For example:</para>
           <screen>
 cd <emphasis> [dspace]</emphasis>/lib
 cp activation.jar servlet.jar mail.jar <emphasis>
@@ -824,7 +824,7 @@ cp activation.jar servlet.jar mail.jar <emphasis>
 thumbnail.maxwidth  80
 thumbnail.maxheight 80
 </screen>
-          <para>There are one or two other, optional extra parameters (for controlling the pool of database connections). See <ulink url="history.html">the version history</ulink> for details. If you leave them out, defaults will be used.</para>
+          <para>There are one or two other, optional extra parameters (for controlling the pool of database connections). See <link linkend="docbook-history.html">the version history</link> for details. If you leave them out, defaults will be used.</para>
           <para>Also, to avoid future confusion, you might like to <emphasis role="bold">remove</emphasis> the following property, which is no longer required:</para>
           <screen>
 config.template.oai-web.xml = <emphasis>
@@ -1037,7 +1037,7 @@ CREATE VIEW CollectionItemsByDateAccession AS SELECT
           <para>(If you haven&apos;t modified any JSPs, you don&apos;t have to do anything.)</para>
         </listitem>
         <listitem>
-          <para> Copy the <ulink url="install.html#javalibs">required Java libraries</ulink> that we couldn&apos;t include in the bundle to the source tree. For example:</para>
+          <para> Copy the <link linkend="docbook-install.html-javalibs">required Java libraries</link> that we couldn&apos;t include in the bundle to the source tree. For example:</para>
           <screen>
 cd <emphasis> [dspace]</emphasis>/lib
 cp *.policy activation.jar servlet.jar mail.jar <emphasis>
diff --git a/dspace/docs/html/ch01.html b/dspace/docs/html/ch01.html
index f1c50ea221..0dcf7b9b95 100644
--- a/dspace/docs/html/ch01.html
+++ b/dspace/docs/html/ch01.html
@@ -1,10 +1,10 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="pr01.html" title="Preface"><link rel="next" href="ch02.html" title="Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="pr01.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N1002C"></a>Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</h2></div></div></div><p>DSpace is an open source software platform that enables organisations to:</p><div class="itemizedlist"><ul type="disc"><li><p> capture and describe digital material using a submission workflow module, or a variety of programmatic ingest options</p></li><li><p> distribute an organisation's digital assets over the web through a search and retrieval system</p></li><li><p> preserve digital assets over the long term</p></li></ul></div><p>This system documentation includes <a class="ulink" href="functional.html" target="_top">a functional overview of the system</a>, which is a good introduction to the capabilities of the system, and should be readable by non-technical folk. Everyone should read this section first because it introduces some terminology used throughout the rest of the documentation.</p><p>For people actually running a DSpace service, there is <a class="ulink" href="install.html" target="_top">an installation guide</a>, and sections on <a class="ulink" href="configure.html" target="_top">configuration</a> and <a class="ulink" href="directories.html" target="_top">the directory structure</a>. Note that as of DSpace 1.2, the administration user interface guide is now on-line help available from within the DSpace system.</p><p>Finally, for those interested in the details of how DSpace works, and those potentially interested in modifying the code for their own purposes, there is <a class="ulink" href="architecture.html" target="_top">a detailed architecture and design section</a>.</p><p>Other good sources of information are:</p><div class="itemizedlist"><ul type="disc"><li><p> The DSpace Public API Javadocs. Build these with the command <code class="literal">mvn javadoc:javadoc</code>.</p></li><li><p> The <a class="ulink" href="http://wiki.dspace.org/" target="_top">DSpace Wiki</a> contains stacks of useful information about the DSpace platform and the work people are doing with it. You are strongly encouraged to visit this site and add information about your own work. Useful Wiki areas are: </p><div class="itemizedlist"><ul type="circle"><li><p><a class="ulink" href="http://wiki.dspace.org/DspaceResources" target="_top">A list of DSpace resources</a>  (Web sites, mailing lists etc.)</p></li><li><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="pr01.html" title="Preface"><link rel="next" href="ch02.html" title="Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="pr01.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N1002C"></a>Chapter&nbsp;1.&nbsp;<a name="docbook-introduction.html"></a>DSpace System Documentation: Introduction</h2></div></div></div><p>DSpace is an open source software platform that enables organisations to:</p><div class="itemizedlist"><ul type="disc"><li><p> capture and describe digital material using a submission workflow module, or a variety of programmatic ingest options</p></li><li><p> distribute an organisation's digital assets over the web through a search and retrieval system</p></li><li><p> preserve digital assets over the long term</p></li></ul></div><p>This system documentation includes <a class="link" href="ch02.html#docbook-functional.html">a functional overview of the system</a>, which is a good introduction to the capabilities of the system, and should be readable by non-technical folk. Everyone should read this section first because it introduces some terminology used throughout the rest of the documentation.</p><p>For people actually running a DSpace service, there is <a class="link" href="ch03.html#docbook-install.html">an installation guide</a>, and sections on <a class="link" href="ch05.html#docbook-configure.html">configuration</a> and <a class="link" href="ch07.html#docbook-directories.html">the directory structure</a>. Note that as of DSpace 1.2, the administration user interface guide is now on-line help available from within the DSpace system.</p><p>Finally, for those interested in the details of how DSpace works, and those potentially interested in modifying the code for their own purposes, there is <a class="link" href="ch08.html#docbook-architecture.html">a detailed architecture and design section</a>.</p><p>Other good sources of information are:</p><div class="itemizedlist"><ul type="disc"><li><p> The DSpace Public API Javadocs. Build these with the command <code class="literal">mvn javadoc:javadoc</code>.</p></li><li><p> The <a class="ulink" href="http://wiki.dspace.org/" target="_top">DSpace Wiki</a> contains stacks of useful information about the DSpace platform and the work people are doing with it. You are strongly encouraged to visit this site and add information about your own work. Useful Wiki areas are: </p><div class="itemizedlist"><ul type="circle"><li><p><a class="ulink" href="http://wiki.dspace.org/DspaceResources" target="_top">A list of DSpace resources</a>  (Web sites, mailing lists etc.)</p></li><li><p>
               <a class="ulink" href="http://wiki.dspace.org/TechnicalFaq" target="_top">Technical FAQ</a>
             </p></li><li><p>
               <a class="ulink" href="http://wiki.dspace.org/DspaceProjects" target="_top">A list of projects using DSpace</a>
             </p></li><li><p>
               <a class="ulink" href="http://wiki.dspace.org/ContributionGuidelines" target="_top">Guidelines for contributing back to DSpace</a>
-            </p></li></ul></div></li><li><p><a class="ulink" href="http://www.dspace.org/" target="_top">www.dspace.org</a>  has announcements and contains useful information about bringing up an instance of DSpace at your organization.</p></li><li><p> The <a class="ulink" href="#" target="_top">dspace-tech e-mail list on SourceForge</a> is the recommended place to ask questions, since a growing community of DSpace developers and users is on hand on that list to help with any questions you might have. The e-mail archive of that list is a useful resource.</p></li><li><p> The <a class="ulink" href="#" target="_top">dspace-devel e-mail list</a>, for those developing with the DSpace with a view to contributing to the core DSpace code.</p></li></ul></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+            </p></li></ul></div></li><li><p><a class="ulink" href="http://www.dspace.org/" target="_top">www.dspace.org</a>  has announcements and contains useful information about bringing up an instance of DSpace at your organization.</p></li><li><p> The <a class="ulink" href="#" target="_top">dspace-tech e-mail list on SourceForge</a> is the recommended place to ask questions, since a growing community of DSpace developers and users is on hand on that list to help with any questions you might have. The e-mail archive of that list is a useful resource.</p></li><li><p> The <a class="ulink" href="#" target="_top">dspace-devel e-mail list</a>, for those developing with the DSpace with a view to contributing to the core DSpace code.</p></li></ul></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch02.html b/dspace/docs/html/ch02.html
index b9bcf47f53..0f45fbc2ad 100644
--- a/dspace/docs/html/ch02.html
+++ b/dspace/docs/html/ch02.html
@@ -1,6 +1,7 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch01.html" title="Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction"><link rel="next" href="ch03.html" title="Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch01.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch03.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10097"></a>Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch02.html#N1009D">2.1. Data Model</a></span></dt><dt><span class="section"><a href="ch02.html#N1019F">2.2. Plugin Manager</a></span></dt><dt><span class="section"><a href="ch02.html#N101B0">2.3. Metadata</a></span></dt><dt><span class="section"><a href="ch02.html#N101F1">2.4. Packager Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N10216">2.5. Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N1023B">2.6. E-People and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N10248">2.6.1. E-Person</a></span></dt><dt><span class="section"><a href="ch02.html#N10264">2.6.2. Groups</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10275">2.7. Authentication</a></span></dt><dt><span class="section"><a href="ch02.html#N1028D">2.8. Authorization</a></span></dt><dt><span class="section"><a href="ch02.html#N1036A">2.9. Ingest Process and Workflow</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N103A5">2.9.1. Workflow Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10404">2.10. Supervision and Collaboration</a></span></dt><dt><span class="section"><a href="ch02.html#N1041B">2.11. Handles</a></span></dt><dt><span class="section"><a href="ch02.html#N10440">2.12. Bitstream 'Persistent' Identifiers</a></span></dt><dt><span class="section"><a href="ch02.html#N10460">2.13. Storage Resource Broker (SRB) Support</a></span></dt><dt><span class="section"><a href="ch02.html#N1046F">2.14. Search and Browse</a></span></dt><dt><span class="section"><a href="ch02.html#N1048A">2.15. HTML Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104D4">2.16. OAI Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104F7">2.17. OpenURL Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10508">2.18. Creative Commons Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10515">2.19. Subscriptions</a></span></dt><dt><span class="section"><a href="ch02.html#N10522">2.20. History</a></span></dt><dt><span class="section"><a href="ch02.html#N10531">2.21. Import and Export</a></span></dt><dt><span class="section"><a href="ch02.html#N1053C">2.22. Registration</a></span></dt><dt><span class="section"><a href="ch02.html#N1054D">2.23. Statistics</a></span></dt><dt><span class="section"><a href="ch02.html#N1057A">2.24. Checksum Checker</a></span></dt></dl></div><p>The following sections describe the various functional aspects of the DSpace system.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1009D"></a>2.1.&nbsp;<a name="docbook-functional.html-data_model"></a>Data Model</h2></div></div></div><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch01.html" title="Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction"><link rel="next" href="ch03.html" title="Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch01.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch03.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10099"></a>Chapter&nbsp;2.&nbsp;<a name="docbook-functional.html"></a>DSpace System Documentation: Functional Overview</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch02.html#N100A1">2.1. Data Model</a></span></dt><dt><span class="section"><a href="ch02.html#N101A3">2.2. Plugin Manager</a></span></dt><dt><span class="section"><a href="ch02.html#N101B4">2.3. Metadata</a></span></dt><dt><span class="section"><a href="ch02.html#N101F5">2.4. Packager Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N1021A">2.5. Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N1023F">2.6. E-People and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N1024C">2.6.1. E-Person</a></span></dt><dt><span class="section"><a href="ch02.html#N10268">2.6.2. Groups</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10279">2.7. Authentication</a></span></dt><dt><span class="section"><a href="ch02.html#N10291">2.8. Authorization</a></span></dt><dt><span class="section"><a href="ch02.html#N1036E">2.9. Ingest Process and Workflow</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N103A9">2.9.1. Workflow Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10408">2.10. Supervision and Collaboration</a></span></dt><dt><span class="section"><a href="ch02.html#N1041F">2.11. Handles</a></span></dt><dt><span class="section"><a href="ch02.html#N10444">2.12. Bitstream 'Persistent' Identifiers</a></span></dt><dt><span class="section"><a href="ch02.html#N10464">2.13. Storage Resource Broker (SRB) Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10473">2.14. Search and Browse</a></span></dt><dt><span class="section"><a href="ch02.html#N1048E">2.15. HTML Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104D8">2.16. OAI Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104FB">2.17. OpenURL Support</a></span></dt><dt><span class="section"><a href="ch02.html#N1050C">2.18. Creative Commons Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10519">2.19. Subscriptions</a></span></dt><dt><span class="section"><a href="ch02.html#N10526">2.20. History</a></span></dt><dt><span class="section"><a href="ch02.html#N10535">2.21. Import and Export</a></span></dt><dt><span class="section"><a href="ch02.html#N10540">2.22. Registration</a></span></dt><dt><span class="section"><a href="ch02.html#N10551">2.23. Statistics</a></span></dt><dt><span class="section"><a href="ch02.html#N1057E">2.24. Checksum Checker</a></span></dt><dt><span class="section"><a href="ch02.html#N10587">2.25. 
+    		Usage Instrumentation</a></span></dt></dl></div><p>The following sections describe the various functional aspects of the DSpace system.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N100A1"></a>2.1.&nbsp;<a name="docbook-functional.html-data_model"></a>Data Model</h2></div></div></div><p>
         <span class="inlinemediaobject"><img src="image/data-model.gif" width="585"></span>
-      </p><p>Data Model Diagram</p><p>The way data is organized in DSpace is intended to reflect the structure of the organization using the DSpace system. Each DSpace site is divided into <span class="emphasis"><em>communities</em></span>, which can be further divided into <span class="emphasis"><em>sub-communities</em></span> reflecting the typical university structure of college, departement, research center, or laboratory.</p><p>Communities contain <span class="emphasis"><em>collections</em></span>, which are groupings of related content. A collection may appear in more than one community.</p><p>Each collection is composed of <span class="emphasis"><em>items</em></span>, which are the basic archival elements of the archive. Each item is owned by one collection. Additionally, an item may appear in additional collections; however every item has one and only one owning collection.</p><p>Items are further subdivided into named <span class="emphasis"><em>bundles</em></span> of <span class="emphasis"><em>bitstreams</em></span>. Bitstreams are, as the name suggests, streams of bits, usually ordinary computer files. Bitstreams that are somehow closely related, for example HTML files and images that compose a single HTML document, are organised into bundles.</p><p>In practice, most items tend to have these named bundles:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>ORIGINAL</em></span>  -- the bundle with the original, deposited bitstreams</p></li><li><p><span class="emphasis"><em>THUMBNAILS</em></span>  -- thumbnails of any image bitstreams</p></li><li><p><span class="emphasis"><em>TEXT</em></span>  -- extracted full-text from bitstreams in ORIGINAL, for indexing</p></li><li><p><span class="emphasis"><em>LICENSE</em></span>  -- contains the deposit license that the submitter granted the host organization; in other words, specifies the rights that the hosting organization have</p></li><li><p><span class="emphasis"><em>CC_LICENSE</em></span>  -- contains the distribution license, if any (a <a class="ulink" href="http://www.creativecommons.org" target="_top">Creative Commons</a> license) associated with the item. This license specifies what end users downloading the content can do with the content</p></li></ul></div><p>Each bitstream is associated with one <span class="emphasis"><em>Bitstream Format</em></span>. Because preservation services may be an important aspect of the DSpace service, it is important to capture the specific formats of files that users submit. In DSpace, a bitstream format is a unique and consistent way to refer to a particular file format. An integral part of a bitstream format is an either implicit or explicit notion of how material in that format can be interpreted. For example, the interpretation for bitstreams encoded in the JPEG standard for still image compression is defined explicitly in the Standard ISO/IEC 10918-1. The interpretation of bitstreams in Microsoft Word 2000 format is defined implicitly, through reference to the Microsoft Word 2000 application. Bitstream formats can be more specific than MIME types or file suffixes. For example, <code class="literal">application/ms-word</code> and <code class="literal">.doc</code> span multiple versions of the Microsoft Word application, each of which produces bitstreams with presumably different characteristics.</p><p>Each bitstream format additionally has a <span class="emphasis"><em>support level</em></span>, indicating how well the hosting institution is likely to be able to preserve content in the format in the future. There are three possible support levels that bitstream formats may be assigned by the hosting institution. The host institution should determine the exact meaning of each support level, after careful consideration of costs and requirements. MIT Libraries' interpretation is shown below:</p><div class="table"><a name="N100FC"></a><p class="title"><b>Table&nbsp;2.1.&nbsp;MIT Libraries' Definitions of Bitstream Format Support Levels</b></p><div class="table-contents"><table summary="MIT Libraries' Definitions of Bitstream Format Support Levels" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+      </p><p>Data Model Diagram</p><p>The way data is organized in DSpace is intended to reflect the structure of the organization using the DSpace system. Each DSpace site is divided into <span class="emphasis"><em>communities</em></span>, which can be further divided into <span class="emphasis"><em>sub-communities</em></span> reflecting the typical university structure of college, departement, research center, or laboratory.</p><p>Communities contain <span class="emphasis"><em>collections</em></span>, which are groupings of related content. A collection may appear in more than one community.</p><p>Each collection is composed of <span class="emphasis"><em>items</em></span>, which are the basic archival elements of the archive. Each item is owned by one collection. Additionally, an item may appear in additional collections; however every item has one and only one owning collection.</p><p>Items are further subdivided into named <span class="emphasis"><em>bundles</em></span> of <span class="emphasis"><em>bitstreams</em></span>. Bitstreams are, as the name suggests, streams of bits, usually ordinary computer files. Bitstreams that are somehow closely related, for example HTML files and images that compose a single HTML document, are organised into bundles.</p><p>In practice, most items tend to have these named bundles:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>ORIGINAL</em></span>  -- the bundle with the original, deposited bitstreams</p></li><li><p><span class="emphasis"><em>THUMBNAILS</em></span>  -- thumbnails of any image bitstreams</p></li><li><p><span class="emphasis"><em>TEXT</em></span>  -- extracted full-text from bitstreams in ORIGINAL, for indexing</p></li><li><p><span class="emphasis"><em>LICENSE</em></span>  -- contains the deposit license that the submitter granted the host organization; in other words, specifies the rights that the hosting organization have</p></li><li><p><span class="emphasis"><em>CC_LICENSE</em></span>  -- contains the distribution license, if any (a <a class="ulink" href="http://www.creativecommons.org" target="_top">Creative Commons</a> license) associated with the item. This license specifies what end users downloading the content can do with the content</p></li></ul></div><p>Each bitstream is associated with one <span class="emphasis"><em>Bitstream Format</em></span>. Because preservation services may be an important aspect of the DSpace service, it is important to capture the specific formats of files that users submit. In DSpace, a bitstream format is a unique and consistent way to refer to a particular file format. An integral part of a bitstream format is an either implicit or explicit notion of how material in that format can be interpreted. For example, the interpretation for bitstreams encoded in the JPEG standard for still image compression is defined explicitly in the Standard ISO/IEC 10918-1. The interpretation of bitstreams in Microsoft Word 2000 format is defined implicitly, through reference to the Microsoft Word 2000 application. Bitstream formats can be more specific than MIME types or file suffixes. For example, <code class="literal">application/ms-word</code> and <code class="literal">.doc</code> span multiple versions of the Microsoft Word application, each of which produces bitstreams with presumably different characteristics.</p><p>Each bitstream format additionally has a <span class="emphasis"><em>support level</em></span>, indicating how well the hosting institution is likely to be able to preserve content in the format in the future. There are three possible support levels that bitstream formats may be assigned by the hosting institution. The host institution should determine the exact meaning of each support level, after careful consideration of costs and requirements. MIT Libraries' interpretation is shown below:</p><div class="table"><a name="N10100"></a><p class="title"><b>Table&nbsp;2.1.&nbsp;MIT Libraries' Definitions of Bitstream Format Support Levels</b></p><div class="table-contents"><table summary="MIT Libraries' Definitions of Bitstream Format Support Levels" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Supported</strong></span>
                 </p>
@@ -18,7 +19,7 @@
                 </p>
               </td><td>
                 <p>The format is unrecognized, but the hosting institution will undertake to preserve the bitstream as-is and allow it to be retrieved.</p>
-              </td></tr></tbody></table></div></div><br class="table-break"><p>Each item has one qualified Dublin Core metadata record. Other metadata might be stored in an item as a serialized bitstream, but we store Dublin Core for every item for interoperability and ease of discovery. The Dublin Core may be entered by end-users as they submit content, or it might be derived from other metadata as part of an ingest process.</p><p><a name="docbook-functional.html-deletions"></a>Items can be removed from DSpace in one of two ways: They may be 'withdrawn', which means they remain in the archive but are completely hidden from view. In this case, if an end-user attempts to access the withdrawn item, they are presented with a 'tombstone,' that indicates the item has been removed. For whatever reason, an item may also be 'expunged' if necessary, in which case all traces of it are removed from the archive.</p><div class="table"><a name="N1013D"></a><p class="title"><b>Table&nbsp;2.2.&nbsp;Objects in the DSpace Data Model</b></p><div class="table-contents"><table summary="Objects in the DSpace Data Model" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+              </td></tr></tbody></table></div></div><br class="table-break"><p>Each item has one qualified Dublin Core metadata record. Other metadata might be stored in an item as a serialized bitstream, but we store Dublin Core for every item for interoperability and ease of discovery. The Dublin Core may be entered by end-users as they submit content, or it might be derived from other metadata as part of an ingest process.</p><p><a name="docbook-functional.html-deletions"></a>Items can be removed from DSpace in one of two ways: They may be 'withdrawn', which means they remain in the archive but are completely hidden from view. In this case, if an end-user attempts to access the withdrawn item, they are presented with a 'tombstone,' that indicates the item has been removed. For whatever reason, an item may also be 'expunged' if necessary, in which case all traces of it are removed from the archive.</p><div class="table"><a name="N10141"></a><p class="title"><b>Table&nbsp;2.2.&nbsp;Objects in the DSpace Data Model</b></p><div class="table-contents"><table summary="Objects in the DSpace Data Model" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Object</strong></span>
                 </p>
@@ -50,7 +51,7 @@
                 <p>Bitstream Format</p>
               </td><td>
                 <p>Microsoft Word version 6.0; JPEG encoded image format</p>
-              </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1019F"></a>2.2.&nbsp;<a name="docbook-functional.html-plugin"></a>Plugin Manager</h2></div></div></div><p>The PluginManager is a very simple component container. It creates and organizes components (plugins), and helps select a plugin in the cases where there are many possible choices. It also gives some limited control over the lifecycle of a plugin.</p><p>A plugin is defined by a Java interface. The consumer of a plugin asks for its plugin by interface. A Plugin is an instance of any class that implements the plugin interface. It is interchangeable with other implementations, so that any of them may be "plugged in".</p><p>The mediafilter is a simple example of a plugin implementation. Refer to the <a class="ulink" href="business.html#plugin" target="_top">Business Logic Layer</a> for more details on Plugins.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101B0"></a>2.3.&nbsp;<a name="docbook-functional.html-metadata"></a>Metadata</h2></div></div></div><p>Broadly speaking, DSpace holds three sorts of metadata about archived content:</p><div class="variablelist"><dl><dt><span class="term">Descriptive Metadata</span></dt><dd><p> DSpace can support multiple flat metadata schemas for describing an item.</p><p>A qualified Dublin Core metadata schema loosely based on the <a class="ulink" href="http://www.dublincore.org/documents/library-application-profile/" target="_top">Library Application Profile</a> set of elements and qualifiers is provided by default. The <a class="ulink" href="http://dspace.org/technology/metadata.html" target="_top">set of elements and qualifiers used by MIT Libraries</a> comes pre-configured with the DSpace source code. However, you can configure multiple schemas and select metadata fields from a mix of configured schemas to describe your items.</p><p>Other descriptive metadata about items (e.g. metadata described in a hierarchical schema) may be held in serialized bitstreams. <span class="emphasis"><em>Communities</em></span> and <span class="emphasis"><em>collections</em></span> have some simple descriptive metadata (a name, and some descriptive prose), held in the DBMS.</p></dd><dt><span class="term">Administrative Metadata</span></dt><dd><p> This includes preservation metadata, provenance and authorization policy data. Most of this is held within DSpace's relation DBMS schema. Provenance metadata (prose) is stored in Dublin Core records. Additionally, some other administrative metadata (for example, bitstream byte sizes and MIME types) is replicated in Dublin Core records so that it is easily accessible outside of DSpace.</p></dd><dt><span class="term">Structural Metadata</span></dt><dd><p> This includes information about how to present an item, or bitstreams within an item, to an end-user, and the relationships between constituent parts of the item. As an example, consider a thesis consisting of a number of TIFF images, each depicting a single page of the thesis. Structural metadata would include the fact that each image is a single page, and the ordering of the TIFF images/pages. Structural metadata in DSpace is currently fairly basic; within an item, bitstreams can be arranged into separate bundles as <a class="link" href="ch02.html#docbook-functional.html-data_model">described above</a>. A bundle may also optionally have a <span class="emphasis"><em>primary bitstream</em></span>. This is currently used by the <a class="link" href="ch02.html#docbook-functional.html-html">HTML support</a> to indicate which bitstream in the bundle is the first HTML file to send to a browser.</p><p>In addition to some basic technical metadata, bitstreams also have a 'sequence ID' that uniquely identifies it within an item. This is used to produce a <a class="link" href="ch02.html#docbook-functional.html-bitstream_ids">'persistent' bitstream identifier</a> for each bitstream.</p><p>Additional structural metadata can be stored in serialized bitstreams, but DSpace does not currently understand this natively.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101F1"></a>2.4.&nbsp;<a name="docbook-functional.html-packager"></a>Packager Plugins</h2></div></div></div><p><span class="emphasis"><em>Packagers</em></span> are software modules that translate between DSpace Item objects and a self-contained external representation, or "package". A <span class="emphasis"><em>Package Ingester</em></span> interprets, or <span class="emphasis"><em>ingests</em></span>, the package and creates an Item. A <span class="emphasis"><em>Package Disseminator</em></span> writes out the contents of an Item in the package format.</p><p>A package is typically an archive file such as a Zip or "tar" file, including a <span class="emphasis"><em>manifest</em></span> document which contains metadata and a description of the package contents. The <a class="ulink" href="http://www.imsglobal.org/content/packaging/" target="_top">IMS Content Package</a> is a typical packaging standard. A package might also be a single document or media file that contains its own metadata, such as a PDF document with embedded descriptive metadata.</p><p>Package ingesters and package disseminators are each a type of named plugin (see <a class="link" href="ch02.html#docbook-functional.html-plugin">Plugin Manager</a>), so it is easy to add new packagers specific to the needs of your site. You do not have to supply both an ingester and disseminator for each format; it is perfectly acceptable to just implement one of them.</p><p>Most packager plugins call upon Crosswalk plugins to translate the metadata between DSpace's object model and the package format.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10216"></a>2.5.&nbsp;<a name="docbook-functional.html-crosswalk"></a>Crosswalk Plugins</h2></div></div></div><p><span class="emphasis"><em>Crosswalks</em></span> are software modules that translate between DSpace object metadata and a specific external representation. An <span class="emphasis"><em>Ingestion Crosswalk</em></span> interprets the external format and crosswalks it to DSpace's internal data structure, while a <span class="emphasis"><em>Dissemination Crosswalk</em></span> does the opposite.</p><p>For example, a MODS ingestion crosswalk translates descriptive metadata from the MODS format to the metadata fields on a DSpace Item. A MODS dissemination crosswalk generates a MODS document from the metadata on a DSpace Item.</p><p>Crosswalk plugins are named plugins see <a class="link" href="ch02.html#docbook-functional.html-plugin">Plugin Manager</a>), so it is easy to add new crosswalks. You do not have to supply both an ingester and disseminator for each format; it is perfectly acceptable to just implement one of them.</p><p>There is also a special pair of crosswalk plugins which use XSL stylesheets to translate the external metadata to or from an internal DSpace format. You can add and modify XSLT crosswalks simply by editing the DSpace configuration and the stylesheets, which are stored in files in the DSpace installation directory.</p><p>The <a class="link" href="ch02.html#docbook-functional.html-packager">Packager plugins</a> and <a class="link" href="ch02.html#docbook-functional.html-oai">OAH-PMH server</a> make use of crosswalk plugins.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1023B"></a>2.6.&nbsp;<a name="docbook-functional.html-epeople"></a>E-People and Groups</h2></div></div></div><p>Although many of DSpace's functions such as document discovery and retrieval can be used anonymously, some features (and perhaps some documents) are only available to certain "privileged" users. E-People and Groups are the way DSpace identifies application users for the purpose of granting privileges. This identity is bound to a session of a DSpace application such as the Web UI or one of the command-line batch programs. Both E-People and Groups are granted privileges by the <a class="link" href="ch02.html#docbook-functional.html-auth">authorization</a> system described below.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10248"></a>2.6.1.&nbsp;E-Person</h3></div></div></div><p>DSpace hold the following information about each e-person:</p><div class="itemizedlist"><ul type="disc"><li><p> E-mail address</p></li><li><p> First and last names</p></li><li><p> Whether the user is able to log in to the system via the Web UI, and whether they must use an X509 certificate to do so;</p></li><li><p> A password (encrypted), if appropriate</p></li><li><p> A list of collections for which the e-person wishes to be notified of new items</p></li><li><p> Whether the e-person 'self-registered' with the system; that is, whether the system created the e-person record automatically as a result of the end-user independently registering with the system, as opposed to the e-person record being generated from the institution's personnel database, for example.</p></li><li><p> The network ID for the corresponding LDAP record</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10264"></a>2.6.2.&nbsp;Groups</h3></div></div></div><p>Groups are another kind of entity that can be granted permissions in the <a class="link" href="ch02.html#docbook-functional.html-auth">authorization</a> system. A group is usually an explicit list of E-People; anyone identified as one of those E-People also gains the privileges granted to the group.</p><p>However, an application session can be assigned membership in a group <span class="emphasis"><em>without</em></span> being identified as an E-Person. For example, some sites use this feature to identify users of a local network so they can read restricted materials not open to the whole world. Sessions originating from the local network are given membership in the "LocalUsers" group and gain the corresonding privileges.</p><p>Administrators can also use groups as "roles" to manage the granting of privileges more efficiently.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10275"></a>2.7.&nbsp;<a name="docbook-functional.html-authentication"></a>Authentication</h2></div></div></div><p><span class="emphasis"><em>Authentication</em></span> is when an application session positively identifies itself as belonging to an E-Person and/or Group. In DSpace 1.4, it is implemented by a mechanism called <span class="emphasis"><em>Stackable Authentication</em></span>: the DSpace configuration declares a "stack" of authentication methods. An application (like the Web UI) calls on the Authentication Manager, which tries each of these methods in turn to identify the E-Person to which the session belongs, as well as any extra Groups. The E-Person authentication methods are tried in turn until one succeeds. Every authenticator in the stack is given a chance to assign extra Groups. This mechanism offers the following advantages:</p><div class="itemizedlist"><ul type="disc"><li><p> Separates authentication from the Web user interface so the same authentication methods are used for other applications such as non-interactive Web Services</p></li><li><p> Improved modularity: The authentication methods are all independent of each other. Custom authentication methods can be "stacked" on top of the default DSpace username/password method.</p></li><li><p> Cleaner support for "implicit" authentication where username is found in the environment of a Web request, e.g. in an X.509 client certificate.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1028D"></a>2.8.&nbsp;<a name="docbook-functional.html-auth"></a>Authorization</h2></div></div></div><p>DSpace's authorization system is based on associating actions with objects and the lists of EPeople who can perform them. The associations are called Resource Policies, and the lists of EPeople are called Groups. There are two special groups: 'administrators', who can do anything in a site, and 'anonymous', which is a list that contains all users. Assigning a policy for an action on an object to anonymous means giving everyone permission to do that action. (For example, most objects in DSpace sites have a policy of 'anonymous' READ.) Permissions must be explicit - lack of an explicit permission results in the default policy of 'deny'. Permissions also do not 'commute'; for example, if an e-person has READ permission on an item, they might not necessarily have READ permission on the bundles and bitstreams in that item. Currently Collections, Communities and Items are discoverable in the browse and search systems regardless of READ authorization.</p><p>The following actions are possible:</p><p>
+              </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101A3"></a>2.2.&nbsp;<a name="docbook-functional.html-plugin"></a>Plugin Manager</h2></div></div></div><p>The PluginManager is a very simple component container. It creates and organizes components (plugins), and helps select a plugin in the cases where there are many possible choices. It also gives some limited control over the lifecycle of a plugin.</p><p>A plugin is defined by a Java interface. The consumer of a plugin asks for its plugin by interface. A Plugin is an instance of any class that implements the plugin interface. It is interchangeable with other implementations, so that any of them may be "plugged in".</p><p>The mediafilter is a simple example of a plugin implementation. Refer to the <a class="link" href="ch10.html#docbook-business.html-plugin">Business Logic Layer</a> for more details on Plugins.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101B4"></a>2.3.&nbsp;<a name="docbook-functional.html-metadata"></a>Metadata</h2></div></div></div><p>Broadly speaking, DSpace holds three sorts of metadata about archived content:</p><div class="variablelist"><dl><dt><span class="term">Descriptive Metadata</span></dt><dd><p> DSpace can support multiple flat metadata schemas for describing an item.</p><p>A qualified Dublin Core metadata schema loosely based on the <a class="ulink" href="http://www.dublincore.org/documents/library-application-profile/" target="_top">Library Application Profile</a> set of elements and qualifiers is provided by default. The <a class="ulink" href="http://dspace.org/technology/metadata.html" target="_top">set of elements and qualifiers used by MIT Libraries</a> comes pre-configured with the DSpace source code. However, you can configure multiple schemas and select metadata fields from a mix of configured schemas to describe your items.</p><p>Other descriptive metadata about items (e.g. metadata described in a hierarchical schema) may be held in serialized bitstreams. <span class="emphasis"><em>Communities</em></span> and <span class="emphasis"><em>collections</em></span> have some simple descriptive metadata (a name, and some descriptive prose), held in the DBMS.</p></dd><dt><span class="term">Administrative Metadata</span></dt><dd><p> This includes preservation metadata, provenance and authorization policy data. Most of this is held within DSpace's relation DBMS schema. Provenance metadata (prose) is stored in Dublin Core records. Additionally, some other administrative metadata (for example, bitstream byte sizes and MIME types) is replicated in Dublin Core records so that it is easily accessible outside of DSpace.</p></dd><dt><span class="term">Structural Metadata</span></dt><dd><p> This includes information about how to present an item, or bitstreams within an item, to an end-user, and the relationships between constituent parts of the item. As an example, consider a thesis consisting of a number of TIFF images, each depicting a single page of the thesis. Structural metadata would include the fact that each image is a single page, and the ordering of the TIFF images/pages. Structural metadata in DSpace is currently fairly basic; within an item, bitstreams can be arranged into separate bundles as <a class="link" href="ch02.html#docbook-functional.html-data_model">described above</a>. A bundle may also optionally have a <span class="emphasis"><em>primary bitstream</em></span>. This is currently used by the <a class="link" href="ch02.html#docbook-functional.html-html">HTML support</a> to indicate which bitstream in the bundle is the first HTML file to send to a browser.</p><p>In addition to some basic technical metadata, bitstreams also have a 'sequence ID' that uniquely identifies it within an item. This is used to produce a <a class="link" href="ch02.html#docbook-functional.html-bitstream_ids">'persistent' bitstream identifier</a> for each bitstream.</p><p>Additional structural metadata can be stored in serialized bitstreams, but DSpace does not currently understand this natively.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N101F5"></a>2.4.&nbsp;<a name="docbook-functional.html-packager"></a>Packager Plugins</h2></div></div></div><p><span class="emphasis"><em>Packagers</em></span> are software modules that translate between DSpace Item objects and a self-contained external representation, or "package". A <span class="emphasis"><em>Package Ingester</em></span> interprets, or <span class="emphasis"><em>ingests</em></span>, the package and creates an Item. A <span class="emphasis"><em>Package Disseminator</em></span> writes out the contents of an Item in the package format.</p><p>A package is typically an archive file such as a Zip or "tar" file, including a <span class="emphasis"><em>manifest</em></span> document which contains metadata and a description of the package contents. The <a class="ulink" href="http://www.imsglobal.org/content/packaging/" target="_top">IMS Content Package</a> is a typical packaging standard. A package might also be a single document or media file that contains its own metadata, such as a PDF document with embedded descriptive metadata.</p><p>Package ingesters and package disseminators are each a type of named plugin (see <a class="link" href="ch02.html#docbook-functional.html-plugin">Plugin Manager</a>), so it is easy to add new packagers specific to the needs of your site. You do not have to supply both an ingester and disseminator for each format; it is perfectly acceptable to just implement one of them.</p><p>Most packager plugins call upon Crosswalk plugins to translate the metadata between DSpace's object model and the package format.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1021A"></a>2.5.&nbsp;<a name="docbook-functional.html-crosswalk"></a>Crosswalk Plugins</h2></div></div></div><p><span class="emphasis"><em>Crosswalks</em></span> are software modules that translate between DSpace object metadata and a specific external representation. An <span class="emphasis"><em>Ingestion Crosswalk</em></span> interprets the external format and crosswalks it to DSpace's internal data structure, while a <span class="emphasis"><em>Dissemination Crosswalk</em></span> does the opposite.</p><p>For example, a MODS ingestion crosswalk translates descriptive metadata from the MODS format to the metadata fields on a DSpace Item. A MODS dissemination crosswalk generates a MODS document from the metadata on a DSpace Item.</p><p>Crosswalk plugins are named plugins see <a class="link" href="ch02.html#docbook-functional.html-plugin">Plugin Manager</a>), so it is easy to add new crosswalks. You do not have to supply both an ingester and disseminator for each format; it is perfectly acceptable to just implement one of them.</p><p>There is also a special pair of crosswalk plugins which use XSL stylesheets to translate the external metadata to or from an internal DSpace format. You can add and modify XSLT crosswalks simply by editing the DSpace configuration and the stylesheets, which are stored in files in the DSpace installation directory.</p><p>The <a class="link" href="ch02.html#docbook-functional.html-packager">Packager plugins</a> and <a class="link" href="ch02.html#docbook-functional.html-oai">OAH-PMH server</a> make use of crosswalk plugins.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1023F"></a>2.6.&nbsp;<a name="docbook-functional.html-epeople"></a>E-People and Groups</h2></div></div></div><p>Although many of DSpace's functions such as document discovery and retrieval can be used anonymously, some features (and perhaps some documents) are only available to certain "privileged" users. E-People and Groups are the way DSpace identifies application users for the purpose of granting privileges. This identity is bound to a session of a DSpace application such as the Web UI or one of the command-line batch programs. Both E-People and Groups are granted privileges by the <a class="link" href="ch02.html#docbook-functional.html-auth">authorization</a> system described below.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1024C"></a>2.6.1.&nbsp;E-Person</h3></div></div></div><p>DSpace hold the following information about each e-person:</p><div class="itemizedlist"><ul type="disc"><li><p> E-mail address</p></li><li><p> First and last names</p></li><li><p> Whether the user is able to log in to the system via the Web UI, and whether they must use an X509 certificate to do so;</p></li><li><p> A password (encrypted), if appropriate</p></li><li><p> A list of collections for which the e-person wishes to be notified of new items</p></li><li><p> Whether the e-person 'self-registered' with the system; that is, whether the system created the e-person record automatically as a result of the end-user independently registering with the system, as opposed to the e-person record being generated from the institution's personnel database, for example.</p></li><li><p> The network ID for the corresponding LDAP record</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10268"></a>2.6.2.&nbsp;Groups</h3></div></div></div><p>Groups are another kind of entity that can be granted permissions in the <a class="link" href="ch02.html#docbook-functional.html-auth">authorization</a> system. A group is usually an explicit list of E-People; anyone identified as one of those E-People also gains the privileges granted to the group.</p><p>However, an application session can be assigned membership in a group <span class="emphasis"><em>without</em></span> being identified as an E-Person. For example, some sites use this feature to identify users of a local network so they can read restricted materials not open to the whole world. Sessions originating from the local network are given membership in the "LocalUsers" group and gain the corresonding privileges.</p><p>Administrators can also use groups as "roles" to manage the granting of privileges more efficiently.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10279"></a>2.7.&nbsp;<a name="docbook-functional.html-authentication"></a>Authentication</h2></div></div></div><p><span class="emphasis"><em>Authentication</em></span> is when an application session positively identifies itself as belonging to an E-Person and/or Group. In DSpace 1.4, it is implemented by a mechanism called <span class="emphasis"><em>Stackable Authentication</em></span>: the DSpace configuration declares a "stack" of authentication methods. An application (like the Web UI) calls on the Authentication Manager, which tries each of these methods in turn to identify the E-Person to which the session belongs, as well as any extra Groups. The E-Person authentication methods are tried in turn until one succeeds. Every authenticator in the stack is given a chance to assign extra Groups. This mechanism offers the following advantages:</p><div class="itemizedlist"><ul type="disc"><li><p> Separates authentication from the Web user interface so the same authentication methods are used for other applications such as non-interactive Web Services</p></li><li><p> Improved modularity: The authentication methods are all independent of each other. Custom authentication methods can be "stacked" on top of the default DSpace username/password method.</p></li><li><p> Cleaner support for "implicit" authentication where username is found in the environment of a Web request, e.g. in an X.509 client certificate.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10291"></a>2.8.&nbsp;<a name="docbook-functional.html-auth"></a>Authorization</h2></div></div></div><p>DSpace's authorization system is based on associating actions with objects and the lists of EPeople who can perform them. The associations are called Resource Policies, and the lists of EPeople are called Groups. There are two special groups: 'administrators', who can do anything in a site, and 'anonymous', which is a list that contains all users. Assigning a policy for an action on an object to anonymous means giving everyone permission to do that action. (For example, most objects in DSpace sites have a policy of 'anonymous' READ.) Permissions must be explicit - lack of an explicit permission results in the default policy of 'deny'. Permissions also do not 'commute'; for example, if an e-person has READ permission on an item, they might not necessarily have READ permission on the bundles and bitstreams in that item. Currently Collections, Communities and Items are discoverable in the browse and search systems regardless of READ authorization.</p><p>The following actions are possible:</p><p>
         <span class="bold"><strong>Community</strong></span>
       </p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>ADD/REMOVE</p>
@@ -104,9 +105,9 @@
                 <p>WRITE</p>
               </td><td>
                 <p>modify bitstream</p>
-              </td></tr></tbody></table></div><p>Note that there is no 'DELETE' action. In order to 'delete' an object (e.g. an item) from the archive, one must have REMOVE permission on all objects (in this case, collection) that contain it. The 'orphaned' item is automatically deleted.</p><p>Policies can apply to individual e-people or groups of e-people.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1036A"></a>2.9.&nbsp;<a name="docbook-functional.html-ingest"></a>Ingest Process and Workflow</h2></div></div></div><p>Rather than being a single subsystem, ingesting is a process that spans several. Below is a simple illustration of the current ingesting process in DSpace.</p><p>
+              </td></tr></tbody></table></div><p>Note that there is no 'DELETE' action. In order to 'delete' an object (e.g. an item) from the archive, one must have REMOVE permission on all objects (in this case, collection) that contain it. The 'orphaned' item is automatically deleted.</p><p>Policies can apply to individual e-people or groups of e-people.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1036E"></a>2.9.&nbsp;<a name="docbook-functional.html-ingest"></a>Ingest Process and Workflow</h2></div></div></div><p>Rather than being a single subsystem, ingesting is a process that spans several. Below is a simple illustration of the current ingesting process in DSpace.</p><p>
         <span class="inlinemediaobject"><img src="image/ingest.gif" width="585"></span>
-      </p><p>DSpace Ingest Process</p><p>The batch item importer is an application, which turns an external SIP (an XML metadata document with some content files) into an "in progress submission" object. The Web submission UI is similarly used by an end-user to assemble an "in progress submission" object.</p><p>Depending on the policy of the collection to which the submission in targeted, a workflow process may be started. This typically allows one or more human reviewers or 'gatekeepers' to check over the submission and ensure it is suitable for inclusion in the collection.</p><p>When the Batch Ingester or Web Submit UI completes the InProgressSubmission object, and invokes the next stage of ingest (be that workflow or item installation), a provenance message is added to the Dublin Core which includes the filenames and checksums of the content of the submission. Likewise, each time a workflow changes state (e.g. a reviewer accepts the submission), a similar provenance statement is added. This allows us to track how the item has changed since a user submitted it. (The <a class="link" href="ch02.html#docbook-functional.html-history">History system</a> is also invoked, but provenance is easier for us to access at the moment.)</p><p>Once any workflow process is successfully and positively completed, the InProgressSubmission object is consumed by an "item installer", that converts the InProgressSubmission into a fully blown archived item in DSpace. The item installer:</p><div class="itemizedlist"><ul type="disc"><li><p> Assigns an accession date</p></li><li><p> Adds a "date.available" value to the Dublin Core metadata record of the item</p></li><li><p> Adds an issue date if none already present</p></li><li><p> Adds a provenance message (including bitstream checksums)</p></li><li><p> Assigns a <a class="link" href="ch02.html#docbook-functional.html-handles">Handle</a> persistent identifier</p></li><li><p> Adds the item to the target collection, and adds appropriate authorization policies</p></li><li><p> Adds the new item to the search and browse indices</p></li></ul></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N103A5"></a>2.9.1.&nbsp;Workflow Steps</h3></div></div></div><p>A collection's workflow can have up to three steps. Each collection may have an associated e-person group for performing each step; if no group is associated with a certain step, that step is skipped. If a collection has no e-person groups associated with any step, submissions to that collection are installed straight into the main archive.</p><p>In other words, the sequence is this: The collection receives a submission. If the collection has a group assigned for workflow step 1, that step is invoked, and the group is notified. Otherwise, workflow step 1 is skipped. Likewise, workflow steps 2 and 3 are performed if and only if the collection has a group assigned to those steps.</p><p>When a step is invoked, the task of performing that workflow step put in the 'task pool' of the associated group. One member of that group takes the task from the pool, and it is then removed from the task pool, to avoid the situation where several people in the group may be performing the same task without realizing it.</p><p>The member of the group who has taken the task from the pool may then perform one of three actions:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+      </p><p>DSpace Ingest Process</p><p>The batch item importer is an application, which turns an external SIP (an XML metadata document with some content files) into an "in progress submission" object. The Web submission UI is similarly used by an end-user to assemble an "in progress submission" object.</p><p>Depending on the policy of the collection to which the submission in targeted, a workflow process may be started. This typically allows one or more human reviewers or 'gatekeepers' to check over the submission and ensure it is suitable for inclusion in the collection.</p><p>When the Batch Ingester or Web Submit UI completes the InProgressSubmission object, and invokes the next stage of ingest (be that workflow or item installation), a provenance message is added to the Dublin Core which includes the filenames and checksums of the content of the submission. Likewise, each time a workflow changes state (e.g. a reviewer accepts the submission), a similar provenance statement is added. This allows us to track how the item has changed since a user submitted it. (The <a class="link" href="ch02.html#docbook-functional.html-history">History system</a> is also invoked, but provenance is easier for us to access at the moment.)</p><p>Once any workflow process is successfully and positively completed, the InProgressSubmission object is consumed by an "item installer", that converts the InProgressSubmission into a fully blown archived item in DSpace. The item installer:</p><div class="itemizedlist"><ul type="disc"><li><p> Assigns an accession date</p></li><li><p> Adds a "date.available" value to the Dublin Core metadata record of the item</p></li><li><p> Adds an issue date if none already present</p></li><li><p> Adds a provenance message (including bitstream checksums)</p></li><li><p> Assigns a <a class="link" href="ch02.html#docbook-functional.html-handles">Handle</a> persistent identifier</p></li><li><p> Adds the item to the target collection, and adds appropriate authorization policies</p></li><li><p> Adds the new item to the search and browse indices</p></li></ul></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N103A9"></a>2.9.1.&nbsp;Workflow Steps</h3></div></div></div><p>A collection's workflow can have up to three steps. Each collection may have an associated e-person group for performing each step; if no group is associated with a certain step, that step is skipped. If a collection has no e-person groups associated with any step, submissions to that collection are installed straight into the main archive.</p><p>In other words, the sequence is this: The collection receives a submission. If the collection has a group assigned for workflow step 1, that step is invoked, and the group is notified. Otherwise, workflow step 1 is skipped. Likewise, workflow steps 2 and 3 are performed if and only if the collection has a group assigned to those steps.</p><p>When a step is invoked, the task of performing that workflow step put in the 'task pool' of the associated group. One member of that group takes the task from the pool, and it is then removed from the task pool, to avoid the situation where several people in the group may be performing the same task without realizing it.</p><p>The member of the group who has taken the task from the pool may then perform one of three actions:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>Workflow Step</strong></span>
                   </p>
@@ -128,14 +129,15 @@
                   <p>Can edit metadata provided by the user with the submission, but cannot change the submitted files. Must then commit to archive; may not reject submission.</p>
                 </td></tr></tbody></table></div><p>
           <span class="inlinemediaobject"><img src="image/workflow.gif" width="585"></span>
-        </p><p>Submission Workflow in DSpace</p><p>If a submission is rejected, the reason (entered by the workflow participant) is e-mailed to the submitter, and it is returned to the submitter's 'My DSpace' page. The submitter can then make any necessary modifications and re-submit, whereupon the process starts again.</p><p>If a submission is 'accepted', it is passed to the next step in the workflow. If there are no more workflow steps with associated groups, the submission is installed in the main archive.</p><p>One last possibility is that a workflow can be 'aborted' by a DSpace site administrator. This is accomplished using the administration UI.</p><p>The reason for this apparently arbitrary design is that is was the simplist case that covered the needs of the early adopter communities at MIT. The functionality of the workflow system will no doubt be extended in the future.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10404"></a>2.10.&nbsp;<a name="docbook-functional.html-supervision"></a>Supervision and Collaboration</h2></div></div></div><p>In order to facilitate, as a primary objective, the opportunity for thesis authors to be supervised in the preparation of their e-thesis, a supervision order system exists to bind groups of other users (thesis supervisors) to an item in someone's pre-submission workspace. The bound group can have system policies associated with it that allow different levels of interaction with the student's item; a small set of default policy groups are provided:</p><div class="itemizedlist"><ul type="disc"><li><p> Full editorial control</p></li><li><p> View item contents</p></li><li><p> No policies</p></li></ul></div><p>Once the default set has been applied, a system administrator may modify them as they would any other policy set in DSpace</p><p>This functionality could also be used in situations where researchers wish to collaborate on a particular submission, although there is no particular collaborative workspace functionality.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1041B"></a>2.11.&nbsp;<a name="docbook-functional.html-handles"></a>Handles</h2></div></div></div><p>Researchers require a stable point of reference for their works. The simple evolution from sharing of citations to emailing of URLs broke when Web users learned that sites can disappear or be reconfigured without notice, and that their bookmark files containing critical links to research results couldn't be trusted long term. To help solve this problem, a core DSpace feature is the creation of persistent identifier for every item, collection and community stored in DSpace. To persist identifier, DSpace requires a storage- and location- independent mechanism for creating and maintaining identifiers. DSpace uses the <a class="ulink" href="http://www.handle.net/" target="_top">CNRI Handle System</a> for creating these identifiers. The rest of this section assumes a basic familiarity with the Handle system.</p><p>DSpace uses Handles primarily as a means of assigning globally unique identifiers to objects. Each site running DSpace needs to obtain a Handle 'prefix' from CNRI, so we know that if we create identifiers with that prefix, they won't clash with identifiers created elsewhere.</p><p>Presently, Handles are assigned to communities, collections, and items. Bundles and bitstreams are not assigned Handles, since over time, the way in which an item is encoded as bits may change, in order to allow access with future technologies and devices. Older versions may be moved to off-line storage as a new standard becomes de facto. Since it's usually the <span class="emphasis"><em>item</em></span> that is being preserved, rather than the particular bit encoding, it only makes sense to persistently identify and allow access to the item, and allow users to access the appropriate bit encoding from there.</p><p>Of course, it may be that a particular bit encoding of a file is explicitly being preserved; in this case, the bitstream could be the only one in the item, and the item's Handle would then essentially refer just to that bitstream. The same bitstream can also be included in other items, and thus would be citable as part of a greater item, or individually.</p><p>The Handle system also features a global resolution infrastructure; that is, an end-user can enter a Handle into any service (e.g. Web page) that can resolve Handles, and the end-user will be directed to the object (in the case of DSpace, community, collection or item) identified by that Handle. In order to take advantage of this feature of the Handle system, a DSpace site must also run a 'Handle server' that can accept and resolve incoming resolution requests. All the code for this is included in the DSpace source code bundle.</p><p>Handles can be written in two forms:</p><pre class="screen">
+        </p><p>Submission Workflow in DSpace</p><p>If a submission is rejected, the reason (entered by the workflow participant) is e-mailed to the submitter, and it is returned to the submitter's 'My DSpace' page. The submitter can then make any necessary modifications and re-submit, whereupon the process starts again.</p><p>If a submission is 'accepted', it is passed to the next step in the workflow. If there are no more workflow steps with associated groups, the submission is installed in the main archive.</p><p>One last possibility is that a workflow can be 'aborted' by a DSpace site administrator. This is accomplished using the administration UI.</p><p>The reason for this apparently arbitrary design is that is was the simplist case that covered the needs of the early adopter communities at MIT. The functionality of the workflow system will no doubt be extended in the future.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10408"></a>2.10.&nbsp;<a name="docbook-functional.html-supervision"></a>Supervision and Collaboration</h2></div></div></div><p>In order to facilitate, as a primary objective, the opportunity for thesis authors to be supervised in the preparation of their e-thesis, a supervision order system exists to bind groups of other users (thesis supervisors) to an item in someone's pre-submission workspace. The bound group can have system policies associated with it that allow different levels of interaction with the student's item; a small set of default policy groups are provided:</p><div class="itemizedlist"><ul type="disc"><li><p> Full editorial control</p></li><li><p> View item contents</p></li><li><p> No policies</p></li></ul></div><p>Once the default set has been applied, a system administrator may modify them as they would any other policy set in DSpace</p><p>This functionality could also be used in situations where researchers wish to collaborate on a particular submission, although there is no particular collaborative workspace functionality.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1041F"></a>2.11.&nbsp;<a name="docbook-functional.html-handles"></a>Handles</h2></div></div></div><p>Researchers require a stable point of reference for their works. The simple evolution from sharing of citations to emailing of URLs broke when Web users learned that sites can disappear or be reconfigured without notice, and that their bookmark files containing critical links to research results couldn't be trusted long term. To help solve this problem, a core DSpace feature is the creation of persistent identifier for every item, collection and community stored in DSpace. To persist identifier, DSpace requires a storage- and location- independent mechanism for creating and maintaining identifiers. DSpace uses the <a class="ulink" href="http://www.handle.net/" target="_top">CNRI Handle System</a> for creating these identifiers. The rest of this section assumes a basic familiarity with the Handle system.</p><p>DSpace uses Handles primarily as a means of assigning globally unique identifiers to objects. Each site running DSpace needs to obtain a Handle 'prefix' from CNRI, so we know that if we create identifiers with that prefix, they won't clash with identifiers created elsewhere.</p><p>Presently, Handles are assigned to communities, collections, and items. Bundles and bitstreams are not assigned Handles, since over time, the way in which an item is encoded as bits may change, in order to allow access with future technologies and devices. Older versions may be moved to off-line storage as a new standard becomes de facto. Since it's usually the <span class="emphasis"><em>item</em></span> that is being preserved, rather than the particular bit encoding, it only makes sense to persistently identify and allow access to the item, and allow users to access the appropriate bit encoding from there.</p><p>Of course, it may be that a particular bit encoding of a file is explicitly being preserved; in this case, the bitstream could be the only one in the item, and the item's Handle would then essentially refer just to that bitstream. The same bitstream can also be included in other items, and thus would be citable as part of a greater item, or individually.</p><p>The Handle system also features a global resolution infrastructure; that is, an end-user can enter a Handle into any service (e.g. Web page) that can resolve Handles, and the end-user will be directed to the object (in the case of DSpace, community, collection or item) identified by that Handle. In order to take advantage of this feature of the Handle system, a DSpace site must also run a 'Handle server' that can accept and resolve incoming resolution requests. All the code for this is included in the DSpace source code bundle.</p><p>Handles can be written in two forms:</p><pre class="screen">
 hdl:1721.123/4567
 http://hdl.handle.net/1721.123/4567
-</pre><p>The above represent the same Handle. The first is possibly more convenient to use only as an identifier; however, by using the second form, any Web browser becomes capable of resolving Handles. An end-user need only access this form of the Handle as they would any other URL. It is possible to enable some browsers to resolve the first form of Handle as if they were standard URLs using <a class="ulink" href="http://www.handle.net/resolver/index.html" target="_top">CNRI's Handle Resolver plug-in</a>, but since the first form can always be simply derived from the second, DSpace displays Handles in the second form, so that it is more useful for end-users.</p><p>It is important to note that DSpace uses the CNRI Handle infrastructure only at the 'site' level. For example, in the above example, the DSpace site has been assigned the prefix '1721.123'. It is still the responsibility of the DSpace site to maintain the association between a full Handle (including the '4567' local part) and the community, collection or item in question.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10440"></a>2.12.&nbsp;<a name="docbook-functional.html-bitstream_ids"></a>Bitstream 'Persistent' Identifiers</h2></div></div></div><p>Similar to handles for DSpace items, bitstreams also have 'Persistent' identifiers. They are more volatile than Handles, since if the content is moved to a different server or organizaion, they will no longer work (hence the quotes around 'persistent'). However, they are more easily persisted than the simple URLs based on database primary key previously used. This means that external systems can more reliably refer to specific bitstreams stored in a DSpace instance.</p><p>Each bitstream has a sequence ID, unique within an item. This sequence ID is used to create a persistent ID, of the form:</p><p>
+</pre><p>The above represent the same Handle. The first is possibly more convenient to use only as an identifier; however, by using the second form, any Web browser becomes capable of resolving Handles. An end-user need only access this form of the Handle as they would any other URL. It is possible to enable some browsers to resolve the first form of Handle as if they were standard URLs using <a class="ulink" href="http://www.handle.net/resolver/index.html" target="_top">CNRI's Handle Resolver plug-in</a>, but since the first form can always be simply derived from the second, DSpace displays Handles in the second form, so that it is more useful for end-users.</p><p>It is important to note that DSpace uses the CNRI Handle infrastructure only at the 'site' level. For example, in the above example, the DSpace site has been assigned the prefix '1721.123'. It is still the responsibility of the DSpace site to maintain the association between a full Handle (including the '4567' local part) and the community, collection or item in question.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10444"></a>2.12.&nbsp;<a name="docbook-functional.html-bitstream_ids"></a>Bitstream 'Persistent' Identifiers</h2></div></div></div><p>Similar to handles for DSpace items, bitstreams also have 'Persistent' identifiers. They are more volatile than Handles, since if the content is moved to a different server or organizaion, they will no longer work (hence the quotes around 'persistent'). However, they are more easily persisted than the simple URLs based on database primary key previously used. This means that external systems can more reliably refer to specific bitstreams stored in a DSpace instance.</p><p>Each bitstream has a sequence ID, unique within an item. This sequence ID is used to create a persistent ID, of the form:</p><p>
         <code class="literal">dspace url/bitstream/handle/sequence ID/filename</code>
       </p><p>For example:</p><pre class="screen">
 https://dspace.myu.edu/bitstream/123.456/789/24/foo.html
-</pre><p>The above refers to the bitstream with sequence ID 24 in the item with the Handle <code class="literal">hdl:123.456/789</code>. The <code class="literal">foo.html</code> is really just there as a hint to browsers: Although DSpace will provide the appropriate MIME type, some browsers only function correctly if the file has an expected extension.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10460"></a>2.13.&nbsp;<a name="docbook-functional.html-srb"></a>Storage Resource Broker (SRB) Support</h2></div></div></div><p>DSpace offers two means for storing bitstreams. The first is in the file system on the server. The second is using <a class="ulink" href="http://www.sdsc.edu/srb" target="_top">SRB (Storage Resource Broker)</a>. Both are achieved using a simple, lightweight API.</p><p>SRB is purely an option but may be used in lieu of the server's file system or in addition to the file system. Without going into a full description, SRB is a very robust, sophisticated storage manager that offers essentially unlimited storage and straightforward means to replicate (in simple terms, backup) the content on other local or remote storage resources.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1046F"></a>2.14.&nbsp;<a name="docbook-functional.html-search_browse"></a>Search and Browse</h2></div></div></div><p>DSpace allows end-users to discover content in a number of ways, including:</p><div class="itemizedlist"><ul type="disc"><li><p> Via external reference, such as a Handle</p></li><li><p> Searching for one or more keywords in metadata or extracted full-text</p></li><li><p> Browsing though title, author, date or subject indices, with optional image thumbnails</p></li></ul></div><p>Search is an essential component of discovery in DSpace. Users' expectations from a search engine are quite high, so a goal for DSpace is to supply as many search features as possible. DSpace's indexing and search module has a very simple API which allows for indexing new content, regenerating the index, and performing searches on the entire corpus, a community, or collection. Behind the API is the Java freeware search engine <a class="ulink" href="http://jakarta.apache.org/lucene/" target="_top">Lucene</a>. Lucene gives us fielded searching, stop word removal, stemming, and the ability to incrementally add new indexed content without regenerating the entire index. The specific Lucene search indexes are configurable enabling institutions to customize which DSpace metadata fields are indexed.</p><p>Another important mechanism for discovery in DSpace is the browse. This is the process whereby the user views a particular index, such as the title index, and navigates around it in search of interesting items. The browse subsystem provides a simple API for achieving this by allowing a caller to specify an index, and a subsection of that index. The browse subsystem then discloses the portion of the index of interest. Indices that may be browsed are item title, item issue date, item author, and subject terms. Additionally, the browse can be limited to items within a particular collection or community.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1048A"></a>2.15.&nbsp;<a name="docbook-functional.html-html"></a>HTML Support</h2></div></div></div><p>For the most part, at present DSpace simply supports uploading and downloading of bitstreams as-is. This is fine for the majority of commonly-used file formats -- for example PDFs, Microsoft Word documents, spreadsheets and so forth. HTML documents (Web sites and Web pages) are far more complicated, and this has important ramifications when it comes to digital preservation:</p><div class="itemizedlist"><ul type="disc"><li><p> Web pages tend to consist of several files -- one or more HTML files that contain references to each other, and stylesheets and image files that are referenced by the HTML files.</p></li><li><p> Web pages also link to or include content from other sites, often imperceptably to the end-user. Thus, in a few year's time, when someone views the preserved Web site, they will probably find that many links are now broken or refer to other sites than are now out of context.</p><p>In fact, it may be unclear to an end-user when they are viewing content stored in DSpace and when they are seeing content included from another site, or have navigated to a page that is not stored in DSpace. This problem can manifest when a submitter uploads some HTML content. For example, the HTML document may include an image from an external Web site, or even their local hard drive. When the submitter views the HTML in DSpace, their browser is able to use the reference in the HTML to retrieve the appropriate image, and so to the submitter, the whole HTML document appears to have been deposited correctly. However, later on, when another user tries to view that HTML, their browser might not be able to retrieve the included image since it may have been removed from the external server. Hence the HTML will seem broken.</p></li><li><p> Often Web pages are produced dynamically by software running on the Web server, and represent the state of a changing database underneath it.</p></li></ul></div><p>Dealing with these issues is the topic of much active research. Currently, DSpace bites off a small, tractable chunk of this problem. DSpace can store and provide on-line browsing capability for <span class="emphasis"><em>self-contained, non-dynamic</em></span> HTML documents. In practical terms, this means:</p><div class="itemizedlist"><ul type="disc"><li><p> No dynamic content (CGI scripts and so forth)</p></li><li><p> All links to preserved content must be <span class="emphasis"><em>relative links</em></span>, that do not refer to 'parents' above the 'root' of the HTML document/site: </p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal">diagram.gif</code>  is OK</p></li><li><p><code class="literal">image/foo.gif</code>  is OK</p></li><li><p><code class="literal">../index.html</code>  is only OK in a file that is at least a directory deep in the HTML document/site hierarchy</p></li><li><p><code class="literal">/stylesheet.css</code>  is not OK (the link will break)</p></li><li><p><code class="literal">http://somedomain.com/content.html</code>  is not OK (the link will continue to link to the external site which may change or disappear)</p></li></ul></div></li><li><p> Any 'absolute links' (e.g. <code class="literal">http://somedomain.com/content.html</code>) are stored 'as is', and will continue to link to the external content (as opposed to relative links, which will link to the copy of the content stored in DSpace.) Thus, over time, the content refered to by the absolute link may change or disappear.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N104D4"></a>2.16.&nbsp;<a name="docbook-functional.html-oai"></a>OAI Support</h2></div></div></div><p>The <a class="ulink" href="http://www.openarchives.org/" target="_top">Open Archives Initiative</a> has developed a <a class="ulink" href="http://www.openarchives.org/OAI/openarchivesprotocol.html" target="_top">protocol for metadata harvesting</a>. This allows sites to programmatically retrieve or 'harvest' the metadata from several sources, and offer services using that metadata, such as indexing or linking services. Such a service could allow users to access information from a large number of sites from one place.</p><p>DSpace exposes the Dublin Core metadata for items that are publicly (anonymously) accessible. Additionally, the collection structure is also exposed via the OAI protocol's 'sets' mechanism. OCLC's open source <a class="ulink" href="http://www.oclc.org/research/software/oai/cat.shtm" target="_top">OAICat</a> framework is used to provide this functionality.</p><p>You can also configure the OAI service to make use of any <a class="link" href="ch02.html#docbook-functional.html-crosswalk">crosswalk plugin</a> to offer additional metadata formats, such as MODS.</p><p>DSpace's OAI service does support the exposing of deletion information for withdrawn items, but not for items that are 'expunged' (<a class="link" href="ch02.html#docbook-functional.html-deletions">see above</a>). DSpace also supports OAI-PMH resumption tokens.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N104F7"></a>2.17.&nbsp;<a name="docbook-functional.html-openurl"></a>OpenURL Support</h2></div></div></div><p>DSpace supports the <a class="ulink" href="http://www.sfxit.com/OpenURL/" target="_top">OpenURL protocol</a> from <a class="ulink" href="http://www.sfxit.com/" target="_top">SFX</a>, in a rather simple fashion. If your institution has an SFX server, DSpace will display an OpenURL link on every item page, automatically using the Dublin Core metadata. Additionally, DSpace can respond to incoming OpenURLs. Presently it simply passes the information in the OpenURL to the search subsystem. A list of results is then displayed, which usually gives the relevant item (if it is in DSpace) at the top of the list.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10508"></a>2.18.&nbsp;<a name="docbook-functional.html-creativecommons"></a>Creative Commons Support</h2></div></div></div><p>Dspace provides support for Creative Commons licenses to be attached to items in the repository. They represent an alternative to traditional copyright. To learn more about Creative Commons, visit <a class="ulink" href="http://creativecommons.org" target="_top">their website</a>. Support for the licenses is controlled by a site-wide configuration option, and since license selection involves redirection to the Creative Commons website, additional parameters may be configured to work with a proxy server. If the option is enabled, users may select a Creative Commons license during the submission process, or elect to skip Creative Commons licensing. If a selection is made a copy of the license text and RDF metadata is stored along with the item in the repository. There is also an indication - text and a Creative Commons icon - in the item display page of the web user interface when an item is licensed under Creative Commons.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10515"></a>2.19.&nbsp;<a name="docbook-functional.html-subscriptions"></a>Subscriptions</h2></div></div></div><p>As <a class="link" href="ch02.html#docbook-functional.html-epeople">noted above</a>, end-users (e-people) may 'subscribe' to collections in order to be alerted when new items appear in those collections. Each day, end-users who are subscribed to one or more collections will receive an e-mail giving brief details of all new items that appeared in any of those collections the previous day. If no new items appeared in any of the subscribed collections, no e-mail is sent. Users can unsubscribe themselves at any time. RSS feeds of new items are also available for collections and communities.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10522"></a>2.20.&nbsp;<a name="docbook-functional.html-history"></a>History</h2></div></div></div><p>While provenance information in the form of prose is very useful, it is not easily programmatically manipulated. The History system captures a time-based record of significant changes in DSpace, in a manner suitable for later 'refactoring' or repurposing.</p><p>Currently, the History subsystem is explicitly invoked when significant events occur (e.g., DSpace accepts an item into the archive). The History subsystem then creates RDF data describing the current state of the object. The RDF data is modeled using <a class="ulink" href="http://www.metadata.net/harmony/" target="_top">Harmony/ABC</a>, an ontology for describing temporal-based data, and stored in the file system. Some simple indices for unwinding the data are available.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10531"></a>2.21.&nbsp;<a name="docbook-functional.html-importexport"></a>Import and Export</h2></div></div></div><p>DSpace also includes batch tools to import and export items in a simple directory structure, where the Dublin Core metadata is stored in an XML file. This may be used as the basis for moving content between DSpace and other systems.</p><p>There is also a METS-based export tool, which exports items as METS-based metadata with associated bitstreams referenced from the METS file.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1053C"></a>2.22.&nbsp;<a name="docbook-functional.html-registration"></a>Registration</h2></div></div></div><p>Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in accessible computer storage. An example might be that there is a repository for existing digital assets. Rather than using the normal <a class="link" href="ch02.html#docbook-functional.html-ingest">interactive ingest process</a> or the <a class="link" href="ch02.html#docbook-functional.html-importexport">batch import</a> to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1054D"></a>2.23.&nbsp;<a name="docbook-functional.html-statistics"></a>Statistics</h2></div></div></div><p>Various statistical reports about the contents and use of your system can be automatically generated by the system. These are generated by analysing DSpace's log files. Statistics can be broken down monthly.</p><p>The report includes data such as:</p><div class="itemizedlist"><ul type="disc"><li><p> A customisable general summary of activities in the archive, by default including: </p><div class="itemizedlist"><ul type="circle"><li><p> Number of item views</p></li><li><p> Number of collection visits</p></li><li><p> Number of community visits</p></li><li><p> Number of OAI Requests</p></li></ul></div></li><li><p> Customisable summary of archive contents</p></li><li><p> Broken-down list of item viewings</p></li><li><p> A full break-down of all system activity</p></li><li><p> User logins</p></li><li><p> Most popular searches</p></li></ul></div><p>The results of statistical analysis can be presented on a by-month and an in-total report, and are available via the user interface. The reports can also either be made public or restricted to administrator access only.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1057A"></a>2.24.&nbsp;<a name="docbook-functional.html-checker"></a>Checksum Checker</h2></div></div></div><p>The purpose of the checker is to verify that the content in a DSpace repository has not become corrupted or been tampered with. The functionality can be invoked on an ad-hoc basis from the command line, or configured via cron or similar. Options exist to support large repositories that cannot be entirely checked in one run of the tool. The tool is extensible to new reporting and checking priority approaches.</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre><p>The above refers to the bitstream with sequence ID 24 in the item with the Handle <code class="literal">hdl:123.456/789</code>. The <code class="literal">foo.html</code> is really just there as a hint to browsers: Although DSpace will provide the appropriate MIME type, some browsers only function correctly if the file has an expected extension.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10464"></a>2.13.&nbsp;<a name="docbook-functional.html-srb"></a>Storage Resource Broker (SRB) Support</h2></div></div></div><p>DSpace offers two means for storing bitstreams. The first is in the file system on the server. The second is using <a class="ulink" href="http://www.sdsc.edu/srb" target="_top">SRB (Storage Resource Broker)</a>. Both are achieved using a simple, lightweight API.</p><p>SRB is purely an option but may be used in lieu of the server's file system or in addition to the file system. Without going into a full description, SRB is a very robust, sophisticated storage manager that offers essentially unlimited storage and straightforward means to replicate (in simple terms, backup) the content on other local or remote storage resources.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10473"></a>2.14.&nbsp;<a name="docbook-functional.html-search_browse"></a>Search and Browse</h2></div></div></div><p>DSpace allows end-users to discover content in a number of ways, including:</p><div class="itemizedlist"><ul type="disc"><li><p> Via external reference, such as a Handle</p></li><li><p> Searching for one or more keywords in metadata or extracted full-text</p></li><li><p> Browsing though title, author, date or subject indices, with optional image thumbnails</p></li></ul></div><p>Search is an essential component of discovery in DSpace. Users' expectations from a search engine are quite high, so a goal for DSpace is to supply as many search features as possible. DSpace's indexing and search module has a very simple API which allows for indexing new content, regenerating the index, and performing searches on the entire corpus, a community, or collection. Behind the API is the Java freeware search engine <a class="ulink" href="http://jakarta.apache.org/lucene/" target="_top">Lucene</a>. Lucene gives us fielded searching, stop word removal, stemming, and the ability to incrementally add new indexed content without regenerating the entire index. The specific Lucene search indexes are configurable enabling institutions to customize which DSpace metadata fields are indexed.</p><p>Another important mechanism for discovery in DSpace is the browse. This is the process whereby the user views a particular index, such as the title index, and navigates around it in search of interesting items. The browse subsystem provides a simple API for achieving this by allowing a caller to specify an index, and a subsection of that index. The browse subsystem then discloses the portion of the index of interest. Indices that may be browsed are item title, item issue date, item author, and subject terms. Additionally, the browse can be limited to items within a particular collection or community.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1048E"></a>2.15.&nbsp;<a name="docbook-functional.html-html"></a>HTML Support</h2></div></div></div><p>For the most part, at present DSpace simply supports uploading and downloading of bitstreams as-is. This is fine for the majority of commonly-used file formats -- for example PDFs, Microsoft Word documents, spreadsheets and so forth. HTML documents (Web sites and Web pages) are far more complicated, and this has important ramifications when it comes to digital preservation:</p><div class="itemizedlist"><ul type="disc"><li><p> Web pages tend to consist of several files -- one or more HTML files that contain references to each other, and stylesheets and image files that are referenced by the HTML files.</p></li><li><p> Web pages also link to or include content from other sites, often imperceptably to the end-user. Thus, in a few year's time, when someone views the preserved Web site, they will probably find that many links are now broken or refer to other sites than are now out of context.</p><p>In fact, it may be unclear to an end-user when they are viewing content stored in DSpace and when they are seeing content included from another site, or have navigated to a page that is not stored in DSpace. This problem can manifest when a submitter uploads some HTML content. For example, the HTML document may include an image from an external Web site, or even their local hard drive. When the submitter views the HTML in DSpace, their browser is able to use the reference in the HTML to retrieve the appropriate image, and so to the submitter, the whole HTML document appears to have been deposited correctly. However, later on, when another user tries to view that HTML, their browser might not be able to retrieve the included image since it may have been removed from the external server. Hence the HTML will seem broken.</p></li><li><p> Often Web pages are produced dynamically by software running on the Web server, and represent the state of a changing database underneath it.</p></li></ul></div><p>Dealing with these issues is the topic of much active research. Currently, DSpace bites off a small, tractable chunk of this problem. DSpace can store and provide on-line browsing capability for <span class="emphasis"><em>self-contained, non-dynamic</em></span> HTML documents. In practical terms, this means:</p><div class="itemizedlist"><ul type="disc"><li><p> No dynamic content (CGI scripts and so forth)</p></li><li><p> All links to preserved content must be <span class="emphasis"><em>relative links</em></span>, that do not refer to 'parents' above the 'root' of the HTML document/site: </p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal">diagram.gif</code>  is OK</p></li><li><p><code class="literal">image/foo.gif</code>  is OK</p></li><li><p><code class="literal">../index.html</code>  is only OK in a file that is at least a directory deep in the HTML document/site hierarchy</p></li><li><p><code class="literal">/stylesheet.css</code>  is not OK (the link will break)</p></li><li><p><code class="literal">http://somedomain.com/content.html</code>  is not OK (the link will continue to link to the external site which may change or disappear)</p></li></ul></div></li><li><p> Any 'absolute links' (e.g. <code class="literal">http://somedomain.com/content.html</code>) are stored 'as is', and will continue to link to the external content (as opposed to relative links, which will link to the copy of the content stored in DSpace.) Thus, over time, the content refered to by the absolute link may change or disappear.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N104D8"></a>2.16.&nbsp;<a name="docbook-functional.html-oai"></a>OAI Support</h2></div></div></div><p>The <a class="ulink" href="http://www.openarchives.org/" target="_top">Open Archives Initiative</a> has developed a <a class="ulink" href="http://www.openarchives.org/OAI/openarchivesprotocol.html" target="_top">protocol for metadata harvesting</a>. This allows sites to programmatically retrieve or 'harvest' the metadata from several sources, and offer services using that metadata, such as indexing or linking services. Such a service could allow users to access information from a large number of sites from one place.</p><p>DSpace exposes the Dublin Core metadata for items that are publicly (anonymously) accessible. Additionally, the collection structure is also exposed via the OAI protocol's 'sets' mechanism. OCLC's open source <a class="ulink" href="http://www.oclc.org/research/software/oai/cat.shtm" target="_top">OAICat</a> framework is used to provide this functionality.</p><p>You can also configure the OAI service to make use of any <a class="link" href="ch02.html#docbook-functional.html-crosswalk">crosswalk plugin</a> to offer additional metadata formats, such as MODS.</p><p>DSpace's OAI service does support the exposing of deletion information for withdrawn items, but not for items that are 'expunged' (<a class="link" href="ch02.html#docbook-functional.html-deletions">see above</a>). DSpace also supports OAI-PMH resumption tokens.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N104FB"></a>2.17.&nbsp;<a name="docbook-functional.html-openurl"></a>OpenURL Support</h2></div></div></div><p>DSpace supports the <a class="ulink" href="http://www.sfxit.com/OpenURL/" target="_top">OpenURL protocol</a> from <a class="ulink" href="http://www.sfxit.com/" target="_top">SFX</a>, in a rather simple fashion. If your institution has an SFX server, DSpace will display an OpenURL link on every item page, automatically using the Dublin Core metadata. Additionally, DSpace can respond to incoming OpenURLs. Presently it simply passes the information in the OpenURL to the search subsystem. A list of results is then displayed, which usually gives the relevant item (if it is in DSpace) at the top of the list.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1050C"></a>2.18.&nbsp;<a name="docbook-functional.html-creativecommons"></a>Creative Commons Support</h2></div></div></div><p>Dspace provides support for Creative Commons licenses to be attached to items in the repository. They represent an alternative to traditional copyright. To learn more about Creative Commons, visit <a class="ulink" href="http://creativecommons.org" target="_top">their website</a>. Support for the licenses is controlled by a site-wide configuration option, and since license selection involves redirection to the Creative Commons website, additional parameters may be configured to work with a proxy server. If the option is enabled, users may select a Creative Commons license during the submission process, or elect to skip Creative Commons licensing. If a selection is made a copy of the license text and RDF metadata is stored along with the item in the repository. There is also an indication - text and a Creative Commons icon - in the item display page of the web user interface when an item is licensed under Creative Commons.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10519"></a>2.19.&nbsp;<a name="docbook-functional.html-subscriptions"></a>Subscriptions</h2></div></div></div><p>As <a class="link" href="ch02.html#docbook-functional.html-epeople">noted above</a>, end-users (e-people) may 'subscribe' to collections in order to be alerted when new items appear in those collections. Each day, end-users who are subscribed to one or more collections will receive an e-mail giving brief details of all new items that appeared in any of those collections the previous day. If no new items appeared in any of the subscribed collections, no e-mail is sent. Users can unsubscribe themselves at any time. RSS feeds of new items are also available for collections and communities.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10526"></a>2.20.&nbsp;<a name="docbook-functional.html-history"></a>History</h2></div></div></div><p>While provenance information in the form of prose is very useful, it is not easily programmatically manipulated. The History system captures a time-based record of significant changes in DSpace, in a manner suitable for later 'refactoring' or repurposing.</p><p>Currently, the History subsystem is explicitly invoked when significant events occur (e.g., DSpace accepts an item into the archive). The History subsystem then creates RDF data describing the current state of the object. The RDF data is modeled using <a class="ulink" href="http://www.metadata.net/harmony/" target="_top">Harmony/ABC</a>, an ontology for describing temporal-based data, and stored in the file system. Some simple indices for unwinding the data are available.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10535"></a>2.21.&nbsp;<a name="docbook-functional.html-importexport"></a>Import and Export</h2></div></div></div><p>DSpace also includes batch tools to import and export items in a simple directory structure, where the Dublin Core metadata is stored in an XML file. This may be used as the basis for moving content between DSpace and other systems.</p><p>There is also a METS-based export tool, which exports items as METS-based metadata with associated bitstreams referenced from the METS file.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10540"></a>2.22.&nbsp;<a name="docbook-functional.html-registration"></a>Registration</h2></div></div></div><p>Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in accessible computer storage. An example might be that there is a repository for existing digital assets. Rather than using the normal <a class="link" href="ch02.html#docbook-functional.html-ingest">interactive ingest process</a> or the <a class="link" href="ch02.html#docbook-functional.html-importexport">batch import</a> to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10551"></a>2.23.&nbsp;<a name="docbook-functional.html-statistics"></a>Statistics</h2></div></div></div><p>Various statistical reports about the contents and use of your system can be automatically generated by the system. These are generated by analysing DSpace's log files. Statistics can be broken down monthly.</p><p>The report includes data such as:</p><div class="itemizedlist"><ul type="disc"><li><p> A customisable general summary of activities in the archive, by default including: </p><div class="itemizedlist"><ul type="circle"><li><p> Number of item views</p></li><li><p> Number of collection visits</p></li><li><p> Number of community visits</p></li><li><p> Number of OAI Requests</p></li></ul></div></li><li><p> Customisable summary of archive contents</p></li><li><p> Broken-down list of item viewings</p></li><li><p> A full break-down of all system activity</p></li><li><p> User logins</p></li><li><p> Most popular searches</p></li></ul></div><p>The results of statistical analysis can be presented on a by-month and an in-total report, and are available via the user interface. The reports can also either be made public or restricted to administrator access only.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1057E"></a>2.24.&nbsp;<a name="docbook-functional.html-checker"></a>Checksum Checker</h2></div></div></div><p>The purpose of the checker is to verify that the content in a DSpace repository has not become corrupted or been tampered with. The functionality can be invoked on an ad-hoc basis from the command line, or configured via cron or similar. Options exist to support large repositories that cannot be entirely checked in one run of the tool. The tool is extensible to new reporting and checking priority approaches.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10587"></a>2.25.&nbsp;
+    		<a name="docbook-functional.html-usage"></a>Usage Instrumentation</h2></div></div></div><p>DSpace can report usage events, such as bitstream downloads, to a pluggable event processor.  This can be used for developing customized usage statistics, for example.  Sample event processor plugins writes event records to a file as tab-separated values or XML.</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch03.html b/dspace/docs/html/ch03.html
index f4b4fdb7cc..799aca6fd1 100644
--- a/dspace/docs/html/ch03.html
+++ b/dspace/docs/html/ch03.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch02.html" title="Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview"><link rel="next" href="ch04.html" title="Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch02.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch04.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10583"></a>Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch03.html#N10587">3.1. Prerequisite Software</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10592">3.1.1. UNIX-like OS or Microsoft Windows</a></span></dt><dt><span class="section"><a href="ch03.html#N105A1">3.1.2. Java JDK 5 or later (standard SDK is fine, you don't need J2EE)</a></span></dt><dt><span class="section"><a href="ch03.html#N105AC">3.1.3. Apache Maven 2.0.8 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105BB">3.1.4. Apache Ant 1.6.2 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105CA">3.1.5. Relational Database: (PostgreSQL or Oracle).</a></span></dt><dt><span class="section"><a href="ch03.html#N10634">3.1.6. Servlet Engine: (Jakarta Tomcat 4.x, Jetty, Caucho Resin or equivalent).</a></span></dt><dt><span class="section"><a href="ch03.html#N1067F">3.1.7. Perl (required for [dspace]/bin/dspace-info.pl)</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10685">3.2. Installation Options</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N1068C">3.2.1. Overview of Install Options</a></span></dt><dt><span class="section"><a href="ch03.html#N10729">3.2.2. Overview of DSpace Directories</a></span></dt><dt><span class="section"><a href="ch03.html#N10787">3.2.3. Installation</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N1090F">3.3. Advanced Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10918">3.3.1. 'cron' Jobs</a></span></dt><dt><span class="section"><a href="ch03.html#N10958">3.3.2. Multilingual Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10973">3.3.3. DSpace over HTTPS</a></span></dt><dt><span class="section"><a href="ch03.html#N10AA9">3.3.4. The Handle Server</a></span></dt><dt><span class="section"><a href="ch03.html#N10B44">3.3.5. Google and HTML sitemaps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10B96">3.4. Windows Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10B9D">3.4.1. Pre-requisite Software</a></span></dt><dt><span class="section"><a href="ch03.html#N10BDF">3.4.2. Installation Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10C96">3.5. Checking Your Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10C9F">3.6. Known Bugs</a></span></dt><dt><span class="section"><a href="ch03.html#N10CB4">3.7. Common Problems</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10587"></a>3.1.&nbsp;<a name="docbook-install.html-prerequisite"></a>Prerequisite Software</h2></div></div></div><p>The list below describes the third-party components and tools you'll need to run a DSpace server. These are just guidelines. Since DSpace is built on open source, standards-based tools, there are numerous other possibilities and setups.</p><p>Also, please note that the configuration and installation guidelines relating to a particular tool below are here for convenience. You should refer to the documentation for each individual component for complete and up-to-date details. Many of the tools are updated on a frequent basis, and the guidelines below may become out of date.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10592"></a>3.1.1.&nbsp;UNIX-like OS or Microsoft Windows</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> UNIX-like OS (Linux, HP/UX etc) : Many distributions of Linux/Unix come with some of the dependencies below pre installed or easily installed via updates, you should consult your particular distributions documentation to determine what is already available.</p></li><li><p> Microsoft Windows: (see full <a class="link" href="ch03.html#docbook-install.html-windows">Windows Instructions</a> for full set of prerequisites)</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105A1"></a>3.1.2.&nbsp;Java JDK 5 or later (standard SDK is fine, you don't need J2EE)</h3></div></div></div><p>DSpace now required Java 5 or greater because of usage of new language capabilities introduced in 5 that make coding easier and cleaner.</p><p>Java 5 or later can be downloaded from the following location: <a class="ulink" href="http://java.sun.com/javase/downloads/index.jsp" target="_top">http://java.sun.com/javase/downloads/index.jsp</a></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105AC"></a>3.1.3.&nbsp;Apache Maven 2.0.8 or later (Java build tool)</h3></div></div></div><p>Maven is necessary in the first stage of the build process to assemble the installation package for your DSpace instance. It gives you the flexibility to customize DSpace using the exisitng Maven projects found in the <code class="literal">[dspace-source]/dspace/modules</code> directory or by adding in your own Maven project to build the installation package for DSpace, and apply any custom interface "overlay" changes.</p><p>Maven can be downloaded from the the following location: <a class="ulink" href="http://maven.apache.org/download.html" target="_top">http://maven.apache.org/download.html</a></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105BB"></a>3.1.4.&nbsp;Apache Ant 1.6.2 or later (Java build tool)</h3></div></div></div><p>Apache Ant is still required for the second stage of the build process. It is used once the installation package has been constructed in <code class="literal">[dspace-source]/dspace/target/dspace-&lt;version&gt;-build.dir</code> and still uses some of the familiar ant build targets found in the 1.4.x build process.</p><p>Ant can be downloaded from the following location: <a class="ulink" href="http://ant.apache.org/" target="_top">http://ant.apache.org</a></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105CA"></a>3.1.5.&nbsp;Relational Database: (PostgreSQL or Oracle).</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch02.html" title="Chapter&nbsp;2.&nbsp;DSpace System Documentation: Functional Overview"><link rel="next" href="ch04.html" title="Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch02.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch04.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10591"></a>Chapter&nbsp;3.&nbsp;<a name="docbook-install.html"></a>DSpace System Documentation: Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch03.html#N10597">3.1. Prerequisite Software</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N105A2">3.1.1. UNIX-like OS or Microsoft Windows</a></span></dt><dt><span class="section"><a href="ch03.html#N105B1">3.1.2. Java JDK 5 or later (standard SDK is fine, you don't need J2EE)</a></span></dt><dt><span class="section"><a href="ch03.html#N105BC">3.1.3. Apache Maven 2.0.8 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105CB">3.1.4. Apache Ant 1.6.2 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105DA">3.1.5. Relational Database: (PostgreSQL or Oracle).</a></span></dt><dt><span class="section"><a href="ch03.html#N10644">3.1.6. Servlet Engine: (Jakarta Tomcat 4.x, Jetty, Caucho Resin or equivalent).</a></span></dt><dt><span class="section"><a href="ch03.html#N1068F">3.1.7. Perl (required for [dspace]/bin/dspace-info.pl)</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10695">3.2. Installation Options</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N1069C">3.2.1. Overview of Install Options</a></span></dt><dt><span class="section"><a href="ch03.html#N10739">3.2.2. Overview of DSpace Directories</a></span></dt><dt><span class="section"><a href="ch03.html#N10797">3.2.3. Installation</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N1091F">3.3. Advanced Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10928">3.3.1. 'cron' Jobs</a></span></dt><dt><span class="section"><a href="ch03.html#N10968">3.3.2. Multilingual Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10983">3.3.3. DSpace over HTTPS</a></span></dt><dt><span class="section"><a href="ch03.html#N10AB9">3.3.4. The Handle Server</a></span></dt><dt><span class="section"><a href="ch03.html#N10B54">3.3.5. Google and HTML sitemaps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10BA6">3.4. Windows Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10BAD">3.4.1. Pre-requisite Software</a></span></dt><dt><span class="section"><a href="ch03.html#N10BEF">3.4.2. Installation Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10CA6">3.5. Checking Your Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10CAF">3.6. Known Bugs</a></span></dt><dt><span class="section"><a href="ch03.html#N10CC4">3.7. Common Problems</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10597"></a>3.1.&nbsp;<a name="docbook-install.html-prerequisite"></a>Prerequisite Software</h2></div></div></div><p>The list below describes the third-party components and tools you'll need to run a DSpace server. These are just guidelines. Since DSpace is built on open source, standards-based tools, there are numerous other possibilities and setups.</p><p>Also, please note that the configuration and installation guidelines relating to a particular tool below are here for convenience. You should refer to the documentation for each individual component for complete and up-to-date details. Many of the tools are updated on a frequent basis, and the guidelines below may become out of date.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105A2"></a>3.1.1.&nbsp;UNIX-like OS or Microsoft Windows</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> UNIX-like OS (Linux, HP/UX etc) : Many distributions of Linux/Unix come with some of the dependencies below pre installed or easily installed via updates, you should consult your particular distributions documentation to determine what is already available.</p></li><li><p> Microsoft Windows: (see full <a class="link" href="ch03.html#docbook-install.html-windows">Windows Instructions</a> for full set of prerequisites)</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105B1"></a>3.1.2.&nbsp;Java JDK 5 or later (standard SDK is fine, you don't need J2EE)</h3></div></div></div><p>DSpace now required Java 5 or greater because of usage of new language capabilities introduced in 5 that make coding easier and cleaner.</p><p>Java 5 or later can be downloaded from the following location: <a class="ulink" href="http://java.sun.com/javase/downloads/index.jsp" target="_top">http://java.sun.com/javase/downloads/index.jsp</a></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105BC"></a>3.1.3.&nbsp;Apache Maven 2.0.8 or later (Java build tool)</h3></div></div></div><p>Maven is necessary in the first stage of the build process to assemble the installation package for your DSpace instance. It gives you the flexibility to customize DSpace using the exisitng Maven projects found in the <code class="literal">[dspace-source]/dspace/modules</code> directory or by adding in your own Maven project to build the installation package for DSpace, and apply any custom interface "overlay" changes.</p><p>Maven can be downloaded from the the following location: <a class="ulink" href="http://maven.apache.org/download.html" target="_top">http://maven.apache.org/download.html</a></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105CB"></a>3.1.4.&nbsp;Apache Ant 1.6.2 or later (Java build tool)</h3></div></div></div><p>Apache Ant is still required for the second stage of the build process. It is used once the installation package has been constructed in <code class="literal">[dspace-source]/dspace/target/dspace-&lt;version&gt;-build.dir</code> and still uses some of the familiar ant build targets found in the 1.4.x build process.</p><p>Ant can be downloaded from the following location: <a class="ulink" href="http://ant.apache.org/" target="_top">http://ant.apache.org</a></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N105DA"></a>3.1.5.&nbsp;Relational Database: (PostgreSQL or Oracle).</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
                <span class="bold"><strong>PostgreSQL 7.3 or greater</strong></span>
             </p><p>PostgreSQL can be downloaded from the following location: <a class="ulink" href="http://www.postgresql.org/" target="_top">http://www.postgresql.org/  </a> Its highly recommended that you try to work with Postgres 8.x or greater, however, 7.3 or greater should still work. Unicode (specifically UTF-8) support must be enabled. This is enabled by default in 8.0+. For 7.<span class="emphasis"><em>x</em></span>, be sure to compile with the following options to the '<code class="literal">configure</code>' script:</p></li><li><p><pre class="screen">
 --enable-multibyte --enable-unicode --with-java
@@ -10,7 +10,7 @@ listen_addresses = 'localhost'
 host  dspace  dspace  127.0.0.1  255.255.255.255  md5
 </pre><p>Then restart PostgreSQL.</p></li><li><p>
                <span class="bold"><strong>Oracle 9 or greater</strong></span>
-            </p><p>Details on acquiring Oracle can be downloaded from the following location: <a class="ulink" href="http://www.oracle.com/database/" target="_top">http://www.oracle.com/database/</a></p><p> You will need to create a database for DSpace. Make sure that the character set is one of the Unicode character sets. DSpace uses UTF-8 natively, and it is suggested that the Oracle database use the same character set. You will also need to create a user account for DSpace (e.g. <code class="literal">dspace</code>,) and ensure that it has permissions to add and remove tables in the database. Refer to the Quick Installation for more details.</p><p><span class="bold"><strong>NOTE:</strong></span> DSpace uses sequences to generate unique object IDs - beware Oracle sequences, which are said to lose their values when doing a database export/import, say restoring from a backup. Be sure to run the script <code class="literal">etc/update-sequences.sql</code>.</p><p><span class="bold"><strong>ALSO NOTE:</strong></span> Everything is fully functional, although Oracle limits you to 4k of text in text fields such as item metadata or collection descriptions.</p><p>For people interested in switching from Postgres to Oracle, I know of no tools that would do this automatically. You will need to recreate the community, collection, and eperson structure in the Oracle system, and then use the item export and import tools to move your content over.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10634"></a>3.1.6.&nbsp;Servlet Engine: (Jakarta Tomcat 4.x, Jetty, Caucho Resin or equivalent).</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+            </p><p>Details on acquiring Oracle can be downloaded from the following location: <a class="ulink" href="http://www.oracle.com/database/" target="_top">http://www.oracle.com/database/</a></p><p> You will need to create a database for DSpace. Make sure that the character set is one of the Unicode character sets. DSpace uses UTF-8 natively, and it is suggested that the Oracle database use the same character set. You will also need to create a user account for DSpace (e.g. <code class="literal">dspace</code>,) and ensure that it has permissions to add and remove tables in the database. Refer to the Quick Installation for more details.</p><p><span class="bold"><strong>NOTE:</strong></span> DSpace uses sequences to generate unique object IDs - beware Oracle sequences, which are said to lose their values when doing a database export/import, say restoring from a backup. Be sure to run the script <code class="literal">etc/update-sequences.sql</code>.</p><p><span class="bold"><strong>ALSO NOTE:</strong></span> Everything is fully functional, although Oracle limits you to 4k of text in text fields such as item metadata or collection descriptions.</p><p>For people interested in switching from Postgres to Oracle, I know of no tools that would do this automatically. You will need to recreate the community, collection, and eperson structure in the Oracle system, and then use the item export and import tools to move your content over.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10644"></a>3.1.6.&nbsp;Servlet Engine: (Jakarta Tomcat 4.x, Jetty, Caucho Resin or equivalent).</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
               <span class="bold"><strong>Jakarta Tomcat 4.x or later.</strong></span>
             </p><p>  Tomcat can be dowloaded from the following location: <a class="ulink" href="http://tomcat.apache.org/whichversion.html" target="_top">http://tomcat.apache.org</a></p><p> Note that DSpace will need to run as the same user as Tomcat, so you might want to install and run Tomcat as a user called '<code class="literal">dspace</code>'. Set the environment variable TOMCAT_USER appropriately.</p><p> Modifications in [tomcat]/tomcat.conf</p><p> You need to ensure that Tomcat has a) enough memory to run DSpace and b) uses UTF-8 as its default file encoding for international character support. So ensure in your startup scripts (etc) that the following environment variable is set: </p><pre class="screen">
 JAVA_OPTS="-Xmx512M -Xms64M -Dfile.encoding=UTF-8"
@@ -29,8 +29,8 @@ URIEncoding="UTF-8"
 	/&gt;
 </pre><p> You may change the port from 8080 by editing it in the file above, and by setting the variable CONNECTOR_PORT in tomcat.conf</p></li><li><p>
               <span class="bold"><strong>Jetty or Caucho Resin</strong></span>
-            </p><p>  DSpace will also run on an equivalent servlet Engine, such as Jetty (<a class="ulink" href="http://www.mortbay.org/jetty/index.html" target="_top">http://www.mortbay.org/jetty/index.html</a>) or Caucho Resin (<a class="ulink" href="http://www.caucho.com/" target="_top">http://www.caucho.com/)</a>.</p><p> Jetty and Resin are configured for correct handling of UTF-8 by default.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1067F"></a>3.1.7.&nbsp;Perl (required for [dspace]/bin/dspace-info.pl)</h3></div></div></div><p>
-        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10685"></a>3.2.&nbsp;<a name="docbook-install.html-installoptions"></a>Installation Options</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1068C"></a>3.2.1.&nbsp;<a name="docbook-install.html-options"></a>Overview of Install Options</h3></div></div></div><p>With the advent of a new Apache <a class="ulink" href="http://maven.apache.org/" target="_top">Maven 2</a> based build architecture in DSpace 1.5.x, you now have two options in how you may wish to install and manage your local installation of DSpace. If you've used DSpace 1.4.x, please recognize that the initial build proceedure has changed to allow for more customization. You will find the later 'Ant based' stages of the installation proceedure familiar. Maven is used to resolve the dependencies of DSpace online from the 'Maven Central Repository' server.</p><p>Its important to note that the strategies are identical in terms of the list of proceedures required to complete the build process, the only difference being that the Source Release includes "more modules" that will be built given their presence in the distribution package.</p><div class="itemizedlist"><ul type="disc"><li><p><a name="docbook-install.html-defaultRelease"></a>Default Release ( dspace-&lt;version&gt;-release.zip )<div class="itemizedlist"><ul type="circle"><li><p>
+            </p><p>  DSpace will also run on an equivalent servlet Engine, such as Jetty (<a class="ulink" href="http://www.mortbay.org/jetty/index.html" target="_top">http://www.mortbay.org/jetty/index.html</a>) or Caucho Resin (<a class="ulink" href="http://www.caucho.com/" target="_top">http://www.caucho.com/)</a>.</p><p> Jetty and Resin are configured for correct handling of UTF-8 by default.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1068F"></a>3.1.7.&nbsp;Perl (required for [dspace]/bin/dspace-info.pl)</h3></div></div></div><p>
+        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10695"></a>3.2.&nbsp;<a name="docbook-install.html-installoptions"></a>Installation Options</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1069C"></a>3.2.1.&nbsp;<a name="docbook-install.html-options"></a>Overview of Install Options</h3></div></div></div><p>With the advent of a new Apache <a class="ulink" href="http://maven.apache.org/" target="_top">Maven 2</a> based build architecture in DSpace 1.5.x, you now have two options in how you may wish to install and manage your local installation of DSpace. If you've used DSpace 1.4.x, please recognize that the initial build proceedure has changed to allow for more customization. You will find the later 'Ant based' stages of the installation proceedure familiar. Maven is used to resolve the dependencies of DSpace online from the 'Maven Central Repository' server.</p><p>Its important to note that the strategies are identical in terms of the list of proceedures required to complete the build process, the only difference being that the Source Release includes "more modules" that will be built given their presence in the distribution package.</p><div class="itemizedlist"><ul type="disc"><li><p><a name="docbook-install.html-defaultRelease"></a>Default Release ( dspace-&lt;version&gt;-release.zip )<div class="itemizedlist"><ul type="circle"><li><p>
                     <span class="bold"><strong>This distribution will be adequate for most cases of running a DSpace instance.</strong></span>
                     <span class="bold"><strong>It is intended to be the quickest way to get DSpace installed and running while still allowing for customization of the themes and branding of your DSpace instance.</strong></span>
                   </p></li><li><p> This method allows you to customize DSpace configurations (in dspace.cfg) or user interfaces, using basic pre-built interface "overlays".</p></li><li><p> It downloads "precompiled" libraries for the core dspace-api, supporting servlets, taglibraries, aspects and themes for the dspace-xmlui, dspace-xmlui and other webservice/applications.</p></li><li><p> This approach exposes the parts of the application that the DSpace commiters would prefer to see customized. All other modules are downloaded from the 'Maven Central Repository'</p></li></ul></div>
@@ -45,7 +45,7 @@ URIEncoding="UTF-8"
                     <code class="literal">[dspace-source]</code>
                     <div class="itemizedlist"><ul type="square"><li><p><code class="literal">dspace/</code>  - DSpace 'build' and configuration module</p></li><li><p><code class="literal">dspace-api/</code>  - Java API source module</p></li><li><p><code class="literal">dspace-jspui/</code>  - JSP-UI source module</p></li><li><p><code class="literal">dspace-oai/</code>  - OAI-PMH source module</p></li><li><p><code class="literal">dspace-xmlui/</code>  - XML-UI source module</p></li><li><p><code class="literal">dspace-lni/</code>  - Lightweight Network Interface source module</p></li><li><p><code class="literal">dspace-sword/</code>  - SWORD (Simple Web-service Offering Repository Deposit) deposit service source module</p></li><li><p><code class="literal">pom.xml</code>  - DSpace Parent Project definition</p></li></ul></div>
                   </p></li></ul></div>
-            </p></li></ul></div><p>Both approaches provide you with the same control over how DSpace builds itself (especially in terms of adding completely custom/3rd-party DSpace "modules" you wish to use). Both methods allow you the ability to create more complex user interface "overlays" in Maven. An interface "overlay" allows you to only manage your local custom code (in your local CVS or SVN), and automatically download the rest of the interface code from the maven central repository whenever you build DSpace. This reduces the amount of out-of-the-box DSpace interface code maintained in your local CVS / SVN.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10729"></a>3.2.2.&nbsp;<a name="docbook-install.html-directories"></a>Overview of DSpace Directories</h3></div></div></div><p>Before beginning an installation, it is important to get a general understanding of the DSpace directories and the names by which they are generally referred. (Please attempt to use these below directory names when asking for help on the DSpace Mailing Lists, as it will help everyone better understand what directory you may be referring to.)</p><p>DSpace uses three separate directory trees. Although you don't need to know all the details of them in order to install DSpace, you do need to know they exist and also know how they're referred to in this document:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>the installation directory</strong></span> , referred to as <span class="emphasis"><em>
+            </p></li></ul></div><p>Both approaches provide you with the same control over how DSpace builds itself (especially in terms of adding completely custom/3rd-party DSpace "modules" you wish to use). Both methods allow you the ability to create more complex user interface "overlays" in Maven. An interface "overlay" allows you to only manage your local custom code (in your local CVS or SVN), and automatically download the rest of the interface code from the maven central repository whenever you build DSpace. This reduces the amount of out-of-the-box DSpace interface code maintained in your local CVS / SVN.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10739"></a>3.2.2.&nbsp;<a name="docbook-install.html-directories"></a>Overview of DSpace Directories</h3></div></div></div><p>Before beginning an installation, it is important to get a general understanding of the DSpace directories and the names by which they are generally referred. (Please attempt to use these below directory names when asking for help on the DSpace Mailing Lists, as it will help everyone better understand what directory you may be referring to.)</p><p>DSpace uses three separate directory trees. Although you don't need to know all the details of them in order to install DSpace, you do need to know they exist and also know how they're referred to in this document:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>the installation directory</strong></span> , referred to as <span class="emphasis"><em>
                 <code class="literal">[dspace]</code>
               </em></span>
 . This is the location where DSpace is installed and running off of it is the location that gets defined in the dspace.cfg as "dspace.dir". It is where all the DSpace configuration files, command line scripts, documentation and webapps will be installed to.</p></li><li><p><span class="bold"><strong>the source directory</strong></span> , referred to as <span class="emphasis"><em>
@@ -57,7 +57,7 @@ URIEncoding="UTF-8"
  by default. However, if you are using Tomcat, you may decide to copy your DSpace web applications from <span class="emphasis"><em>
                 <code class="literal">[dspace]/webapps/</code>
               </em></span>
- to <code class="literal">[tomcat]/webapps/</code> (with <code class="literal">[tomcat]</code> being wherever you installed Tomcat--also known as <code class="literal">$CATALINA_HOME</code>).</p></li></ol></div><p>For details on the contents of these separate directory trees, refer to <a class="ulink" href="directories.html" target="_top">directories.html</a>. <span class="emphasis"><em>Note that the <code class="literal">[dspace-source]</code> and <code class="literal">[dspace]</code> directories are always separate!</em></span></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10787"></a>3.2.3.&nbsp;<a name="docbook-install.html-installsteps"></a>Installation</h3></div></div></div><p> This method gets you up and running with DSpace quickly and easily. It is identical in both the <a class="link" href="ch03.html#docbook-install.html-defaultRelease">Default Release</a> and <a class="link" href="ch03.html#docbook-install.html-sourceRelease">Source Release</a> distributions. </p><div class="orderedlist"><ol type="1"><li><p> Create the DSpace user. This needs to be the same user that Tomcat (or Jetty etc) will run as. e.g. as root run:</p><pre class="screen">
+ to <code class="literal">[tomcat]/webapps/</code> (with <code class="literal">[tomcat]</code> being wherever you installed Tomcat--also known as <code class="literal">$CATALINA_HOME</code>).</p></li></ol></div><p>For details on the contents of these separate directory trees, refer to <a class="link" href="ch07.html#docbook-directories.html">directories.html</a>. <span class="emphasis"><em>Note that the <code class="literal">[dspace-source]</code> and <code class="literal">[dspace]</code> directories are always separate!</em></span></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10797"></a>3.2.3.&nbsp;<a name="docbook-install.html-installsteps"></a>Installation</h3></div></div></div><p> This method gets you up and running with DSpace quickly and easily. It is identical in both the <a class="link" href="ch03.html#docbook-install.html-defaultRelease">Default Release</a> and <a class="link" href="ch03.html#docbook-install.html-sourceRelease">Source Release</a> distributions. </p><div class="orderedlist"><ol type="1"><li><p> Create the DSpace user. This needs to be the same user that Tomcat (or Jetty etc) will run as. e.g. as root run:</p><pre class="screen">
 useradd -m dspace
 </pre></li><li><p> Download the <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">latest DSpace release</a> and unpack it. Although there are two available releases (<code class="literal">dspace-1.x-release.zip</code> and <code class="literal">dspace-1.x-src-release.zip</code>), you only need to choose one. If you want a copy of all underlying Java source code, you should download the <code class="literal">dspace-1.x-src-release.zip</code> release. </p><pre class="screen">
 unzip dspace-1.x-release.zip
@@ -111,7 +111,7 @@ cp -r <span class="emphasis"><em> [dspace]</em></span>/webapps/oai <span class="
 	[tomcat]</em></span>/webapps
 </pre></li><li><p> Create an initial administrator account: </p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/create-administrator
-</pre></li><li><p> Now the moment of truth! Start up (or restart) Tomcat/Jetty/Resin. Visit the base URL(s) of your server, depending on which DSpace web applications you want to use. You should see the DSpace home page. Congratulations! </p><p>Base URLs of DSpace Web Applications:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>JSP User Interface</em></span>  - (e.g.) http://dspace.myu.edu:8080/jspui</p></li><li><p><span class="emphasis"><em>XML User Interface (aka. Manakin)</em></span>  - (e.g.) http://dspace.myu.edu:8080/xmlui</p></li><li><p><span class="emphasis"><em>OAI-PMH Interface</em></span>  - (e.g.) http://dspace.myu.edu:8080/oai/request?verb=identify (Should return an XML-based response)</p></li></ul></div></li></ol></div><p>In order to set up some communities and collections, you'll need to login as your DSpace Administrator (which you created with <code class="literal">create-administrator</code> above) and access the administration UI in either the JSP or XML user interface.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1090F"></a>3.3.&nbsp;<a name="docbook-install.html-advancedinstall"></a>Advanced Installation</h2></div></div></div><p>The above installation steps are sufficient to set up a test server to play around with, but there are a few other steps and options you should probably consider before deploying a DSpace production site.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10918"></a>3.3.1.&nbsp;'cron' Jobs</h3></div></div></div><p>A couple of DSpace features require that a script is run regularly -- the e-mail subscription feature that alerts users of new items being deposited, and the new 'media filter' tool, that generates thumbnails of images and extracts the full-text of documents for indexing.</p><p>To set these up, you just need to run the following command as the <code class="literal">dspace</code> UNIX user:</p><pre class="screen">
+</pre></li><li><p> Now the moment of truth! Start up (or restart) Tomcat/Jetty/Resin. Visit the base URL(s) of your server, depending on which DSpace web applications you want to use. You should see the DSpace home page. Congratulations! </p><p>Base URLs of DSpace Web Applications:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>JSP User Interface</em></span>  - (e.g.) http://dspace.myu.edu:8080/jspui</p></li><li><p><span class="emphasis"><em>XML User Interface (aka. Manakin)</em></span>  - (e.g.) http://dspace.myu.edu:8080/xmlui</p></li><li><p><span class="emphasis"><em>OAI-PMH Interface</em></span>  - (e.g.) http://dspace.myu.edu:8080/oai/request?verb=identify (Should return an XML-based response)</p></li></ul></div></li></ol></div><p>In order to set up some communities and collections, you'll need to login as your DSpace Administrator (which you created with <code class="literal">create-administrator</code> above) and access the administration UI in either the JSP or XML user interface.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1091F"></a>3.3.&nbsp;<a name="docbook-install.html-advancedinstall"></a>Advanced Installation</h2></div></div></div><p>The above installation steps are sufficient to set up a test server to play around with, but there are a few other steps and options you should probably consider before deploying a DSpace production site.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10928"></a>3.3.1.&nbsp;'cron' Jobs</h3></div></div></div><p>A couple of DSpace features require that a script is run regularly -- the e-mail subscription feature that alerts users of new items being deposited, and the new 'media filter' tool, that generates thumbnails of images and extracts the full-text of documents for indexing.</p><p>To set these up, you just need to run the following command as the <code class="literal">dspace</code> UNIX user:</p><pre class="screen">
 crontab -e
 </pre><p>Then add the following lines:</p><pre class="screen">
 # Send out subscription e-mails at 01:00 every day
@@ -132,7 +132,7 @@ crontab -e
 0 1 * * * [dspace]/bin/stat-monthly
 0 2 * * * [dspace]/bin/stat-report-general
 0 2 * * * [dspace]/bin/stat-report-monthly
-</pre><p>Obviously, you should choose execution times which are most useful to you, and you should ensure that the <code class="literal">-report-</code> scripts run a short while after the analysis scripts to give them time to complete (a run of around 8 months worth of logs can take around 25 seconds to complete); the resulting reports will let you know how long analysis took and you can adjust your cron times accordingly.</p><p>For information on customising the output of this see <a class="ulink" href="configure.html#statistics" target="_top">configuring system statistical reports</a>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10958"></a>3.3.2.&nbsp;Multilingual Installation</h3></div></div></div><p> In order to deploy a multilingual version of DSpace you have to configure two parameters in <code class="literal">[dspace-source]/config/dspace.cfg:</code></p><p><code class="literal">default.locale</code>, e. g. default.locale = en</p><p><code class="literal">webui.supported locales</code>, e. g. webui.supported.locales = en, de</p><p> The Locales might have the form country, country_language, country_language_variant.</p><p> Accoding to the languages you wish to support, you have to make sure, that all the i18n related files are available see the <a class="ulink" href="configure.html#multilingualui" target="_top">Multilingual User Interface Configuring MultiLingual Support</a> section for the JSPUI or the Multilingual Support for XMLUI in the configuration documentation. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10973"></a>3.3.3.&nbsp;<a name="docbook-install.html-https"></a>DSpace over HTTPS</h3></div></div></div><p>If your DSpace is configured to have users login with a username and password (as opposed to, say, client Web certificates), then you should consider using HTTPS. Whenever a user logs in with the Web form (e.g. <code class="literal">dspace.myuni.edu/dspace/password-login</code>) their DSpace password is exposed in plain text on the network. This is a very serious security risk since network traffic monitoring is very common, especially at universities. If the risk seems minor, then consider that your DSpace administrators also login this way and they have ultimate control over the archive.</p><p>The solution is to use <span class="emphasis"><em>HTTPS</em></span> (HTTP over SSL, i.e. Secure Socket Layer, an encrypted transport), which protects your passwords against being captured. You can configure DSpace to require SSL on all "authenticated" transactions so it only accepts passwords on SSL connections.</p><p>The following sections show how to set up the most commonly-used Java Servlet containers to support HTTP over SSL.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10987"></a>To enable the HTTPS support in Tomcat 5.0:</h4></div></div></div><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>For Production use:</strong></span>  Follow this procedure to set up SSL on your server. Using a "real" server certificate ensures your users' browsers will accept it without complaints. </p><p>In the examples below, <code class="literal">$CATALINA_BASE</code> is the directory under which your Tomcat is installed.</p><div class="orderedlist"><ol type="a"><li><p> Create a Java keystore for your server with the password <code class="literal">changeit</code>, and install your server certificate under the alias <code class="literal">"tomcat"</code>. This assumes the certificate was put in the file <code class="literal">server.pem</code>:</p><pre class="screen">
+</pre><p>Obviously, you should choose execution times which are most useful to you, and you should ensure that the <code class="literal">-report-</code> scripts run a short while after the analysis scripts to give them time to complete (a run of around 8 months worth of logs can take around 25 seconds to complete); the resulting reports will let you know how long analysis took and you can adjust your cron times accordingly.</p><p>For information on customising the output of this see <a class="link" href="ch05.html#docbook-configure.html-statistics">configuring system statistical reports</a>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10968"></a>3.3.2.&nbsp;Multilingual Installation</h3></div></div></div><p> In order to deploy a multilingual version of DSpace you have to configure two parameters in <code class="literal">[dspace-source]/config/dspace.cfg:</code></p><p><code class="literal">default.locale</code>, e. g. default.locale = en</p><p><code class="literal">webui.supported locales</code>, e. g. webui.supported.locales = en, de</p><p> The Locales might have the form country, country_language, country_language_variant.</p><p> Accoding to the languages you wish to support, you have to make sure, that all the i18n related files are available see the <a class="link" href="">Multilingual User Interface Configuring MultiLingual Support</a> section for the JSPUI or the Multilingual Support for XMLUI in the configuration documentation. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10983"></a>3.3.3.&nbsp;<a name="docbook-install.html-https"></a>DSpace over HTTPS</h3></div></div></div><p>If your DSpace is configured to have users login with a username and password (as opposed to, say, client Web certificates), then you should consider using HTTPS. Whenever a user logs in with the Web form (e.g. <code class="literal">dspace.myuni.edu/dspace/password-login</code>) their DSpace password is exposed in plain text on the network. This is a very serious security risk since network traffic monitoring is very common, especially at universities. If the risk seems minor, then consider that your DSpace administrators also login this way and they have ultimate control over the archive.</p><p>The solution is to use <span class="emphasis"><em>HTTPS</em></span> (HTTP over SSL, i.e. Secure Socket Layer, an encrypted transport), which protects your passwords against being captured. You can configure DSpace to require SSL on all "authenticated" transactions so it only accepts passwords on SSL connections.</p><p>The following sections show how to set up the most commonly-used Java Servlet containers to support HTTP over SSL.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10997"></a>To enable the HTTPS support in Tomcat 5.0:</h4></div></div></div><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>For Production use:</strong></span>  Follow this procedure to set up SSL on your server. Using a "real" server certificate ensures your users' browsers will accept it without complaints. </p><p>In the examples below, <code class="literal">$CATALINA_BASE</code> is the directory under which your Tomcat is installed.</p><div class="orderedlist"><ol type="a"><li><p> Create a Java keystore for your server with the password <code class="literal">changeit</code>, and install your server certificate under the alias <code class="literal">"tomcat"</code>. This assumes the certificate was put in the file <code class="literal">server.pem</code>:</p><pre class="screen">
  $JAVA_HOME/bin/keytool -import -noprompt -v -storepass changeit
 	-keystore $CATALINA_BASE/conf/keystore -alias tomcat -file
 	myserver.pem
@@ -140,7 +140,7 @@ crontab -e
  $JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
 	-trustcacerts -keystore $CATALINA_BASE/conf/keystore -alias ServerCA
 	-file ca.pem
-</pre></li><li><p> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <a class="ulink" href="configure.html#authenticate" target="_top">configuration section</a> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <code class="literal">client1.pem</code>:</p><pre class="screen">
+</pre></li><li><p> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <a class="link" href="">configuration section</a> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <code class="literal">client1.pem</code>:</p><pre class="screen">
  $JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
 	-trustcacerts -keystore $CATALINA_BASE/conf/keystore  -alias client1
 	-file client1.pem
@@ -189,11 +189,11 @@ $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keysize
 </pre><p> Since you now have a signed server certificate in your keystore, you can, obviously, skip the next steps of installing a signed server certificate and the server CA's certificate.</p></li></ul></div></li><li><p> Create a Java keystore for your server with the password <code class="literal">changeit</code>, and install your server certificate under the alias <code class="literal">"tomcat"</code>. This assumes the certificate was put in the file <code class="literal">server.pem</code>:</p><pre class="screen">
  $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keystore
 	$CATALINA_BASE/conf/keystore -storepass changeit
-</pre><p>When answering the questions to identify the certificate, be sure to respond to "First and last name" with the fully-qualified domain name of your server (e.g. <code class="literal">test-dspace.myuni.edu</code>). The other questions are not important.</p></li><li><p> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <a class="ulink" href="configure.html#authenticate" target="_top">configuration section</a> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <code class="literal">client1.pem</code>:</p><pre class="screen">
+</pre><p>When answering the questions to identify the certificate, be sure to respond to "First and last name" with the fully-qualified domain name of your server (e.g. <code class="literal">test-dspace.myuni.edu</code>). The other questions are not important.</p></li><li><p> Optional -- ONLY if you need to accept client certificates for the X.509 certificate stackable authentication module See the <a class="link" href="">configuration section</a> for instructions on enabling the X.509 authentication method. Load the keystore with the CA (certifying authority) certificates for the authorities of any clients whose certificates you wish to accept. For example, assuming the client CA certificate is in <code class="literal">client1.pem</code>:</p><pre class="screen">
  $JAVA_HOME/bin/keytool -import -noprompt -storepass changeit
 	-trustcacerts -keystore $CATALINA_BASE/conf/keystore  -alias client1
 	-file client1.pem
-</pre></li><li><p> Follow the procedure in the section above to add another Connector tag, for the HTTPS port, to your <code class="literal">server.xml</code> file.</p></li></ol></div></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10A57"></a>To use SSL on Apache HTTPD with mod_jk:</h4></div></div></div><p> If you choose <a class="ulink" href="http://httpd.apache.org/" target="_top">Apache HTTPD</a> as your primary HTTP server, you can have it forward requests to the <a class="ulink" href="http://tomcat.apache.org/" target="_top">Tomcat servlet container</a> via <a class="ulink" href="http://tomcat.apache.org/connectors-doc/" target="_top">Apache Jakarta Tomcat Connector</a>. This can be configured to work over SSL as well.  First, you must configure Apache for SSL; for Apache 2.0 see <a class="ulink" href="http://httpd.apache.org/docs/2.0/ssl/" target="_top">Apache SSL/TLS Encryption</a> for information about using <a class="ulink" href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html" target="_top">mod_ssl</a>.</p><p><span class="emphasis"><em>
+</pre></li><li><p> Follow the procedure in the section above to add another Connector tag, for the HTTPS port, to your <code class="literal">server.xml</code> file.</p></li></ol></div></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N10A67"></a>To use SSL on Apache HTTPD with mod_jk:</h4></div></div></div><p> If you choose <a class="ulink" href="http://httpd.apache.org/" target="_top">Apache HTTPD</a> as your primary HTTP server, you can have it forward requests to the <a class="ulink" href="http://tomcat.apache.org/" target="_top">Tomcat servlet container</a> via <a class="ulink" href="http://tomcat.apache.org/connectors-doc/" target="_top">Apache Jakarta Tomcat Connector</a>. This can be configured to work over SSL as well.  First, you must configure Apache for SSL; for Apache 2.0 see <a class="ulink" href="http://httpd.apache.org/docs/2.0/ssl/" target="_top">Apache SSL/TLS Encryption</a> for information about using <a class="ulink" href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html" target="_top">mod_ssl</a>.</p><p><span class="emphasis"><em>
               <span class="bold"><strong>If you are using X.509 Client Certificates for authentication:</strong></span>
             </em></span>
  add these configuration options to the appropriate <span class="emphasis"><em>httpd</em></span> configuration file, e.g. <code class="literal">ssl.conf</code>, and be sure they are in force for the virtual host and namespace locations dedicated to DSpace:</p><pre class="screen">
@@ -205,7 +205,7 @@ $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keysize
 	path-to-your-client-CA-certificate</em></span>
         SSLOptions StdEnvVars ExportCertData
    
-</pre><p>Now consult the <a class="ulink" href="http://tomcat.apache.org/connectors-doc/" target="_top">Apache Jakarta Tomcat Connector</a> documentation to configure the <code class="literal">mod_jk</code> (note: <span class="bold"><strong>NOT</strong></span><code class="literal">mod_jk2</code>) module. Select the AJP 1.3 connector protocol. Also follow the instructions there to configure your Tomcat server to respond to AJP.</p><p><span class="bold"><strong>To use SSL on Apache HTTPD with mod_webapp</strong></span> consult the DSpace 1.3.2 documentation. Apache have deprecated the <code class="literal">mod_webapp</code> connector and recommend using <code class="literal">mod_jk</code>.</p><p><span class="bold"><strong>To use Jetty's HTTPS support</strong></span> consult the documentation for the relevant tool.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10AA9"></a>3.3.4.&nbsp;<a name="docbook-install.html-handles"></a>The Handle Server</h3></div></div></div><p>First a few facts to clear up some common misconceptions:</p><div class="itemizedlist"><ul type="disc"><li><p> You don't <span class="bold"><strong>have</strong></span> to use CNRI's Handle system. At the moment, you need to change the code a little to use something else (e.g PURLs) but that should change soon.</p></li><li><p> You'll notice that while you've been playing around with a test server, DSpace has apparently been creating handles for you looking like <code class="literal">hdl:123456789/24</code> and so forth. These aren't really Handles, since the global Handle system doesn't actually know about them, and lots of other DSpace test installs will have created the same IDs.</p><p>They're only really Handles once you've registered a prefix with CNRI (see below) and have correctly set up the Handle server included in the DSpace distribution. This Handle server communicates with the rest of the global Handle infrastructure so that anyone that understands Handles can find the Handles your DSpace has created.</p></li></ul></div><p>If you want to use the Handle system, you'll need to set up a Handle server. This is included with DSpace. Note that this is not required in order to evaluate DSpace; you only need one if you are running a production service. You'll need to obtain a Handle prefix from <a class="ulink" href="http://www.handle.net/" target="_top">the central CNRI Handle site</a>.</p><p>A Handle server runs as a separate process that receives TCP requests from other Handle servers, and issues resolution requests to a global server or servers if a Handle entered locally does not correspond to some local content. The Handle protocol is based on TCP, so it will need to be installed on a server that can broadcast and receive TCP on port 2641.</p><p>The Handle server code is included with the DSpace code in <code class="literal">[dspace-source]/lib/handle.jar</code>. <span class="bold"><strong>Note:</strong></span> The latest version of the <code class="literal">handle.jar</code> file is not included in the release due to licensing conditions changing between the provided version and later versions. It is recommended you read the <a class="ulink" href="http://www.handle.net/upgrade_6-2_DSpace.html" target="_top">new license conditions</a> and decide whether you wish to update your installation's <code class="literal">handle.jar</code>. If you decide to update, you should replace the existing <code class="literal">handle.jar</code> in <span class="emphasis"><em>[dspace-source]</em></span>/lib with the new version and rebuild your war files.</p><p>A script exists to create a simple Handle configuration - simply run <code class="literal">[dspace]/bin/make-handle-config</code> after you've set the appropriate parameters in <code class="literal">dspace.cfg</code>. You can also create a Handle configuration directly by following the <a class="ulink" href="http://www.handle.net/hs_manual_18jan02/server_manual_2.html" target="_top">installation instructions on handle.net</a>, but with these changes:</p><div class="itemizedlist"><ul type="disc"><li><p> Instead of running: </p><pre class="screen">
+</pre><p>Now consult the <a class="ulink" href="http://tomcat.apache.org/connectors-doc/" target="_top">Apache Jakarta Tomcat Connector</a> documentation to configure the <code class="literal">mod_jk</code> (note: <span class="bold"><strong>NOT</strong></span><code class="literal">mod_jk2</code>) module. Select the AJP 1.3 connector protocol. Also follow the instructions there to configure your Tomcat server to respond to AJP.</p><p><span class="bold"><strong>To use SSL on Apache HTTPD with mod_webapp</strong></span> consult the DSpace 1.3.2 documentation. Apache have deprecated the <code class="literal">mod_webapp</code> connector and recommend using <code class="literal">mod_jk</code>.</p><p><span class="bold"><strong>To use Jetty's HTTPS support</strong></span> consult the documentation for the relevant tool.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10AB9"></a>3.3.4.&nbsp;<a name="docbook-install.html-handles"></a>The Handle Server</h3></div></div></div><p>First a few facts to clear up some common misconceptions:</p><div class="itemizedlist"><ul type="disc"><li><p> You don't <span class="bold"><strong>have</strong></span> to use CNRI's Handle system. At the moment, you need to change the code a little to use something else (e.g PURLs) but that should change soon.</p></li><li><p> You'll notice that while you've been playing around with a test server, DSpace has apparently been creating handles for you looking like <code class="literal">hdl:123456789/24</code> and so forth. These aren't really Handles, since the global Handle system doesn't actually know about them, and lots of other DSpace test installs will have created the same IDs.</p><p>They're only really Handles once you've registered a prefix with CNRI (see below) and have correctly set up the Handle server included in the DSpace distribution. This Handle server communicates with the rest of the global Handle infrastructure so that anyone that understands Handles can find the Handles your DSpace has created.</p></li></ul></div><p>If you want to use the Handle system, you'll need to set up a Handle server. This is included with DSpace. Note that this is not required in order to evaluate DSpace; you only need one if you are running a production service. You'll need to obtain a Handle prefix from <a class="ulink" href="http://www.handle.net/" target="_top">the central CNRI Handle site</a>.</p><p>A Handle server runs as a separate process that receives TCP requests from other Handle servers, and issues resolution requests to a global server or servers if a Handle entered locally does not correspond to some local content. The Handle protocol is based on TCP, so it will need to be installed on a server that can broadcast and receive TCP on port 2641.</p><p>The Handle server code is included with the DSpace code in <code class="literal">[dspace-source]/lib/handle.jar</code>. <span class="bold"><strong>Note:</strong></span> The latest version of the <code class="literal">handle.jar</code> file is not included in the release due to licensing conditions changing between the provided version and later versions. It is recommended you read the <a class="ulink" href="http://www.handle.net/upgrade_6-2_DSpace.html" target="_top">new license conditions</a> and decide whether you wish to update your installation's <code class="literal">handle.jar</code>. If you decide to update, you should replace the existing <code class="literal">handle.jar</code> in <span class="emphasis"><em>[dspace-source]</em></span>/lib with the new version and rebuild your war files.</p><p>A script exists to create a simple Handle configuration - simply run <code class="literal">[dspace]/bin/make-handle-config</code> after you've set the appropriate parameters in <code class="literal">dspace.cfg</code>. You can also create a Handle configuration directly by following the <a class="ulink" href="http://www.handle.net/hs_manual_18jan02/server_manual_2.html" target="_top">installation instructions on handle.net</a>, but with these changes:</p><div class="itemizedlist"><ul type="disc"><li><p> Instead of running: </p><pre class="screen">
 java -cp /hs/bin/handle.jar net.handle.server.SimpleSetup /hs/svr_1
 </pre><p> as directed in the <a class="ulink" href="http://hdl.handle.net/4263537/4093" target="_top">Handle Server Administration Guide</a>, you should run </p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/dsrun net.handle.server.SimpleSetup <span class="emphasis"><em>
@@ -216,18 +216,18 @@ java -cp /hs/bin/handle.jar net.handle.server.SimpleSetup /hs/svr_1
 	"org.dspace.handle.HandlePlugin"
 </pre><p>This tells the Handle server to get information about individual Handles from the DSpace code.</p></li></ul></div><p>Whichever approach you take, start the Handle server with <code class="literal">[dspace]/bin/start-handle-server</code>, as the DSpace user. Once the configuration file has been generated, you will need to go to <a class="ulink" href="http://hdl.handle.net/4263537/5014" target="_top">http://hdl.handle.net/4263537/5014</a> to upload the generated sitebndl.zip file. The upload page will ask you for your contact information. An administrator will then create the naming authority/prefix on the root service (known as the Global Handle Registry), and notify you when this has been completed. You will not be able to continue the handle server installation until you receive further information concerning your naming authority.</p><p>Note that since the DSpace code manages individual Handles, administrative operations such as Handle creation and modification aren't supported by DSpace's Handle server.</p><p>If you need to update the handle prefix on items created before the CNRI registration process you can run the <code class="literal">[dspace]/bin/update-handle-prefix script</code>. You may need to do this if you loaded items prior to CNRI registration (e.g. setting up a demonstration system prior to migrating it to production). The script takes the current and new prefix as parameters. For example:</p><p>
           <code class="literal">[dspace]/bin/update-handle-prefix 123456789 1303</code>
-        </p><p>will change any handles currently assigned prefix 123456789 to prefix 1303, so for example handle 123456789/23 will be updated to 1303/23 in the database.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10B44"></a>3.3.5.&nbsp;<a name="docbook-install.html-sitemaps"></a>Google and HTML sitemaps</h3></div></div></div><p>To aid web crawlers index the content within your repository, you can make use of sitemaps. There are currently two forms of sitemaps included in DSpace; Google sitemaps and HTML sitemaps.</p><p>Sitemaps allow DSpace to expose it's content without the crawlers having to index every page. HTML sitemaps provide a list of all items, collections and communities in HTML format, whilst Google sitemaps provide the same information in gzipped XML format.</p><p>To generate the sitemaps, you need to run <code class="literal">[dspace]/bin/generate-sitemaps</code> This creates the sitemaps in <code class="literal">[dspace]/sitemaps/</code></p><p>The sitemaps can be accessed from the following URLs:</p><div class="itemizedlist"><ul type="disc"><li><p> http://dspace.example.com/dspace/sitemap - Index sitemap</p></li><li><p> http://dspace.example.com/dspace/sitemap?map=0 - First list of items (up to 50,000)</p></li><li><p> http://dspace.example.com/dspace/sitemap?map=n - Subsequent lists of items (e.g. 50,0001 to 100,000) etc...</p></li></ul></div><p> HTML sitemaps follow the same procedure: <div class="itemizedlist"><ul type="disc"><li><p> http://dspace.example.com/dspace/htmlmap - Index sitemap</p></li><li><p> etc...</p></li></ul></div>
+        </p><p>will change any handles currently assigned prefix 123456789 to prefix 1303, so for example handle 123456789/23 will be updated to 1303/23 in the database.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10B54"></a>3.3.5.&nbsp;<a name="docbook-install.html-sitemaps"></a>Google and HTML sitemaps</h3></div></div></div><p>To aid web crawlers index the content within your repository, you can make use of sitemaps. There are currently two forms of sitemaps included in DSpace; Google sitemaps and HTML sitemaps.</p><p>Sitemaps allow DSpace to expose it's content without the crawlers having to index every page. HTML sitemaps provide a list of all items, collections and communities in HTML format, whilst Google sitemaps provide the same information in gzipped XML format.</p><p>To generate the sitemaps, you need to run <code class="literal">[dspace]/bin/generate-sitemaps</code> This creates the sitemaps in <code class="literal">[dspace]/sitemaps/</code></p><p>The sitemaps can be accessed from the following URLs:</p><div class="itemizedlist"><ul type="disc"><li><p> http://dspace.example.com/dspace/sitemap - Index sitemap</p></li><li><p> http://dspace.example.com/dspace/sitemap?map=0 - First list of items (up to 50,000)</p></li><li><p> http://dspace.example.com/dspace/sitemap?map=n - Subsequent lists of items (e.g. 50,0001 to 100,000) etc...</p></li></ul></div><p> HTML sitemaps follow the same procedure: <div class="itemizedlist"><ul type="disc"><li><p> http://dspace.example.com/dspace/htmlmap - Index sitemap</p></li><li><p> etc...</p></li></ul></div>
 </p><p> When running <code class="literal">[dspace]/bin/generate-sitemaps</code> the script informs Google that the sitemaps have been updated. For this update to register correctly, you must first register your Google sitemap index page (<code class="literal">/dspace/sitemap</code>) with Google at <a class="ulink" href="http://www.google.com/webmasters/sitemaps/" target="_top">http://www.google.com/webmasters/sitemaps/</a>. If your DSpace server requires the use of a HTTP proxy to connect to the Internet, ensure that you have set <code class="literal">http.proxy.host</code> and <code class="literal">http.proxy.port</code> in <code class="literal">[dspace]/config/dspace.cfg</code></p><p>The URL for pinging Google, and in future, other search engines, is configured in <code class="literal">[dspace-space]/config/dspace.cfg</code> using the <code class="literal">sitemap.engineurls</code> setting where you can provide a comma-separated list of URLs to 'ping'.</p><p>You can generate the sitemaps automatically every day using an additional cron job:</p><pre class="screen">
 # Generate sitemaps
 
 
 0 6 * * * [dspace]/bin/generate-sitemaps
        
-</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10B96"></a>3.4.&nbsp;<a name="docbook-install.html-windows"></a>Windows Installation</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10B9D"></a>3.4.1.&nbsp;Pre-requisite Software</h3></div></div></div><p>You'll need to install this pre-requisite software:</p><div class="itemizedlist"><ul type="disc"><li><p> <a class="ulink" href="http://java.sun.com/" target="_top">Java SDK 1.5</a> or later (standard SDK is fine, you don't need J2EE)</p></li><li><p> <a class="ulink" href="http://www.postgresql.org/ftp/" target="_top">PostgreSQL 8.x for Windows</a> OR <a class="ulink" href="http://www.oracle.com/database/" target="_top">Oracle 9 or later</a>.</p><div class="itemizedlist"><ul type="circle"><li><p> If you install PostgreSQL, it's recommended to select to install the pgAdmin III tool</p></li></ul></div></li><li><p> <a class="ulink" href="http://ant.apache.org/" target="_top">Apache Ant 1.6.2 or later</a>. Unzip the package in <code class="literal">C:\</code> and add <code class="literal">C:\apache-ant-1.6.2\bin</code> to the <code class="literal">PATH</code> environment variable. For Ant to work properly, you should ensure that <code class="literal">JAVA_HOME</code> is set.</p></li><li><p>
+</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10BA6"></a>3.4.&nbsp;<a name="docbook-install.html-windows"></a>Windows Installation</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10BAD"></a>3.4.1.&nbsp;Pre-requisite Software</h3></div></div></div><p>You'll need to install this pre-requisite software:</p><div class="itemizedlist"><ul type="disc"><li><p> <a class="ulink" href="http://java.sun.com/" target="_top">Java SDK 1.5</a> or later (standard SDK is fine, you don't need J2EE)</p></li><li><p> <a class="ulink" href="http://www.postgresql.org/ftp/" target="_top">PostgreSQL 8.x for Windows</a> OR <a class="ulink" href="http://www.oracle.com/database/" target="_top">Oracle 9 or later</a>.</p><div class="itemizedlist"><ul type="circle"><li><p> If you install PostgreSQL, it's recommended to select to install the pgAdmin III tool</p></li></ul></div></li><li><p> <a class="ulink" href="http://ant.apache.org/" target="_top">Apache Ant 1.6.2 or later</a>. Unzip the package in <code class="literal">C:\</code> and add <code class="literal">C:\apache-ant-1.6.2\bin</code> to the <code class="literal">PATH</code> environment variable. For Ant to work properly, you should ensure that <code class="literal">JAVA_HOME</code> is set.</p></li><li><p>
                <a class="ulink" href="http://tomcat.apache.org/" target="_top">Jakarta Tomcat 5.x or later</a>
             </p></li><li><p>
                <a class="ulink" href="http://maven.apache.org/" target="_top">Apache Maven 2.0.8 or later</a>
-            </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10BDF"></a>3.4.2.&nbsp;Installation Steps</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p> Download the DSpace source from <a class="ulink" href="http://sourceforge.net/projects/dspace" target="_top">SourceForge</a> and untar it (<a class="ulink" href="http://www.winzip.com/" target="_top">WinZip</a> will do this)</p></li><li><p> Ensure the PostgreSQL service is running, and then run pgAdmin III (Start -&gt; PostgreSQL 8.0 -&gt; pgAdmin III). Connect to the local database as the postgres user and:</p><div class="itemizedlist"><ul type="disc"><li><p> Create a 'Login Role' (user) called <code class="literal">dspace</code> with the password <code class="literal">dspace</code></p></li><li><p> Create a database called <code class="literal">dspace</code> owned by the user <code class="literal">dspace</code>, with UTF-8 encoding</p></li></ul></div></li><li><p> Update paths in <code class="literal">[dspace-source]\dspace\config\dspace.cfg</code>. <span class="bold"><strong>Note:</strong></span> Use forward slashes / for path separators, though you can still use drive letters, e.g.:</p><p>
+            </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N10BEF"></a>3.4.2.&nbsp;Installation Steps</h3></div></div></div><div class="orderedlist"><ol type="1"><li><p> Download the DSpace source from <a class="ulink" href="http://sourceforge.net/projects/dspace" target="_top">SourceForge</a> and untar it (<a class="ulink" href="http://www.winzip.com/" target="_top">WinZip</a> will do this)</p></li><li><p> Ensure the PostgreSQL service is running, and then run pgAdmin III (Start -&gt; PostgreSQL 8.0 -&gt; pgAdmin III). Connect to the local database as the postgres user and:</p><div class="itemizedlist"><ul type="disc"><li><p> Create a 'Login Role' (user) called <code class="literal">dspace</code> with the password <code class="literal">dspace</code></p></li><li><p> Create a database called <code class="literal">dspace</code> owned by the user <code class="literal">dspace</code>, with UTF-8 encoding</p></li></ul></div></li><li><p> Update paths in <code class="literal">[dspace-source]\dspace\config\dspace.cfg</code>. <span class="bold"><strong>Note:</strong></span> Use forward slashes / for path separators, though you can still use drive letters, e.g.:</p><p>
               <code class="literal">dspace.dir = C:/DSpace</code>
             </p><p>Make sure you change all of the parameters with file paths to suit, specifically:</p><pre class="screen">
         dspace.dir
@@ -259,7 +259,7 @@ ant help
 &lt;Context path="/oai" docBase="[dspace]\webapps\oai" debug="0"
 	reloadable="true" cachingAllowed="false"
 	allowLinking="true"/&gt;
-</pre></li></ul></div></li><li><p> Start the Tomcat service</p></li><li><p> Browse to either <code class="literal">http://localhost:8080/jspui</code> or <code class="literal">http://localhost:8080/xmlui</code>. You should see the DSpace home page for either the JSPUI or XMLUI, respectively.</p></li></ol></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10C96"></a>3.5.&nbsp;<a name="docbook-install.html-checking"></a>Checking Your Installation</h2></div></div></div><p>TODO</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10C9F"></a>3.6.&nbsp;<a name="docbook-install.html-knownbugs"></a>Known Bugs</h2></div></div></div><p>In any software project of the scale of DSpace, there will be bugs. Sometimes, a stable version of DSpace includes known bugs. We do not always wait until every known bug is fixed before a release. If the software is sufficiently stable and an improvement on the previous release, and the bugs are minor and have known workarounds, we release it to enable the community to take advantage of those improvements.</p><p>The known bugs in a release are documented in the <code class="literal">KNOWN_BUGS</code> file in the source package.</p><p>Please see the <a class="ulink" href="#" target="_top">DSpace bug tracker</a> for further information on current bugs, and to find out if the bug has subsequently been fixed. This is also where you can report any further bugs you find.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10CB4"></a>3.7.&nbsp;<a name="docbook-install.html-problems"></a>Common Problems</h2></div></div></div><p>In an ideal world everyone would follow the above steps and have a fully functioning DSpace. Of couse, in the real world it doesn't always seem to work out that way. This section lists common problems that people encounter when installing DSpace, and likely causes and fixes. This is likely to grow over time as we learn about users' experiences.</p><div class="variablelist"><dl><dt><span class="term">Database errors occur when you run <code class="literal">ant fresh_install</code></span></dt><dd><p> There are two common errors that occur. If your error looks like this--</p><pre class="screen">
+</pre></li></ul></div></li><li><p> Start the Tomcat service</p></li><li><p> Browse to either <code class="literal">http://localhost:8080/jspui</code> or <code class="literal">http://localhost:8080/xmlui</code>. You should see the DSpace home page for either the JSPUI or XMLUI, respectively.</p></li></ol></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10CA6"></a>3.5.&nbsp;<a name="docbook-install.html-checking"></a>Checking Your Installation</h2></div></div></div><p>TODO</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10CAF"></a>3.6.&nbsp;<a name="docbook-install.html-knownbugs"></a>Known Bugs</h2></div></div></div><p>In any software project of the scale of DSpace, there will be bugs. Sometimes, a stable version of DSpace includes known bugs. We do not always wait until every known bug is fixed before a release. If the software is sufficiently stable and an improvement on the previous release, and the bugs are minor and have known workarounds, we release it to enable the community to take advantage of those improvements.</p><p>The known bugs in a release are documented in the <code class="literal">KNOWN_BUGS</code> file in the source package.</p><p>Please see the <a class="ulink" href="#" target="_top">DSpace bug tracker</a> for further information on current bugs, and to find out if the bug has subsequently been fixed. This is also where you can report any further bugs you find.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10CC4"></a>3.7.&nbsp;<a name="docbook-install.html-problems"></a>Common Problems</h2></div></div></div><p>In an ideal world everyone would follow the above steps and have a fully functioning DSpace. Of couse, in the real world it doesn't always seem to work out that way. This section lists common problems that people encounter when installing DSpace, and likely causes and fixes. This is likely to grow over time as we learn about users' experiences.</p><div class="variablelist"><dl><dt><span class="term">Database errors occur when you run <code class="literal">ant fresh_install</code></span></dt><dd><p> There are two common errors that occur. If your error looks like this--</p><pre class="screen">
 [java] 2004-03-25 15:17:07,730 INFO 
 	org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database
 [java] 2004-03-25 15:17:08,816 FATAL
@@ -295,7 +295,7 @@ dspace 16325  1997  0  Feb 14  ?         0:00 postgres: dspace dspace
 </pre><p>This is normal--DSpace maintains a 'pool' of open database connections, which are re-used to avoid the overhead of constantly opening and closing connections. If they're 'idle' it's OK; they're waiting to be used. However sometimes, if something went wrong, they might be stuck in the middle of a query, which seems to prevent other connections from operating, e.g.:</p><pre class="screen">
 dspace 16325  1997  0  Feb 14  ?         0:00 postgres: dspace dspace
 	127.0.0.1 SELECT
-</pre><p>This means the connection is in the middle of a <code class="literal">SELECT</code> operation, and if you're not using DSpace right that instant, it's probably a 'zombie' connection. If this is the case, try <code class="literal">kill</code>ing the process, and stopping and restarting Tomcat.</p></dd></dl></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre><p>This means the connection is in the middle of a <code class="literal">SELECT</code> operation, and if you're not using DSpace right that instant, it's probably a 'zombie' connection. If this is the case, try <code class="literal">kill</code>ing the process, and stopping and restarting Tomcat.</p></dd></dl></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch04.html b/dspace/docs/html/ch04.html
index 25f865a581..819ed7ea9e 100644
--- a/dspace/docs/html/ch04.html
+++ b/dspace/docs/html/ch04.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch03.html" title="Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation"><link rel="next" href="ch05.html" title="Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch03.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch05.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10D2F"></a>Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch04.html#N10D39">4.1. Updating From 1.4.2 to 1.5</a></span></dt><dt><span class="section"><a href="ch04.html#N10EB8">4.2. Updating From 1.4.1 to 1.4.2</a></span></dt><dt><span class="section"><a href="ch04.html#N10EC5">4.3. Updating From 1.4 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N10F6E">4.4. Updating From 1.3.2 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N1107C">4.5. Updating From 1.3.1 to 1.3.2</a></span></dt><dt><span class="section"><a href="ch04.html#N110F0">4.6. Updating From 1.2.x to 1.3.x</a></span></dt><dt><span class="section"><a href="ch04.html#N111AF">4.7. Updating From 1.2.1 to 1.2.2</a></span></dt><dt><span class="section"><a href="ch04.html#N1123C">4.8. Updating From 1.2 to 1.2.1</a></span></dt><dt><span class="section"><a href="ch04.html#N112BE">4.9. Updating From 1.1 (or 1.1.1) to 1.2</a></span></dt><dt><span class="section"><a href="ch04.html#N11436">4.10. Updating From 1.1 to 1.1.1</a></span></dt><dt><span class="section"><a href="ch04.html#N11470">4.11. Updating From 1.0.1 to 1.1</a></span></dt></dl></div><p>This section describes how to update a DSpace installation from one version to the next. Details of the differences between the functionality of each version are given in the <a class="ulink" href="history.html" target="_top">Version History</a> section.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10D39"></a>4.1.&nbsp;<a name="docbook-update.html-142_15"></a>Updating From 1.4.2 to 1.5</h2></div></div></div><p>The changes in DSpace 1.5 are significant and wide spread involving database schema upgrades, code restructuring, completely new user and programatic interfaces, and new build system.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-source]</code> to the source directory for DSpace 1.5. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Backup your DSpace</strong></span> First and foremost, make a complete backup of your system, including:</p><div class="itemizedlist"><ul type="disc"><li><p> A snapshot of the database</p></li><li><p> The asset store (<code class="literal">[dspace]/assetstore</code> by default)</p></li><li><p> Your configuration files and customizations to DSpace</p></li><li><p> Your statistics scripts (<code class="literal">[dspace]/bin/stat*</code>) which contain customizable dates</p></li></ul></div></li><li><p><span class="bold"><strong>Download DSpace 1.5</strong></span> Get the new DSpace 1.5 source code either as a download from <a class="ulink" href="#" target="_top">SourceForge</a> or check it out directly from the <a class="ulink" href="#" target="_top">SVN code repository</a>. If you downloaded DSpace do not unpack it on top of your existing installation.</p></li><li><p><span class="bold"><strong>Build DSpace</strong></span> The build process has radically changed for DSpace 1.5. With this new release the build system has moved to a maven-based system enabling the various projects (JSPUI, XMLUI, OAI, and Core API) into separate projects. See the <a class="ulink" href="install.html" target="_top">Installation section</a> for more information on building DSpace using the new maven-based build system. Run the following commands to compile DSpace.</p><pre class="screen">
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch03.html" title="Chapter&nbsp;3.&nbsp;DSpace System Documentation: Installation"><link rel="next" href="ch05.html" title="Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch03.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch05.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10D3F"></a>Chapter&nbsp;4.&nbsp;<a name="docbook-update.html"></a>DSpace System Documentation: Updating a DSpace Installation</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch04.html#N10D4B">4.1. Updating From 1.4.2 to 1.5</a></span></dt><dt><span class="section"><a href="ch04.html#N10ECA">4.2. Updating From 1.4.1 to 1.4.2</a></span></dt><dt><span class="section"><a href="ch04.html#N10ED7">4.3. Updating From 1.4 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N10F80">4.4. Updating From 1.3.2 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N1108E">4.5. Updating From 1.3.1 to 1.3.2</a></span></dt><dt><span class="section"><a href="ch04.html#N11102">4.6. Updating From 1.2.x to 1.3.x</a></span></dt><dt><span class="section"><a href="ch04.html#N111C1">4.7. Updating From 1.2.1 to 1.2.2</a></span></dt><dt><span class="section"><a href="ch04.html#N1124E">4.8. Updating From 1.2 to 1.2.1</a></span></dt><dt><span class="section"><a href="ch04.html#N112D0">4.9. Updating From 1.1 (or 1.1.1) to 1.2</a></span></dt><dt><span class="section"><a href="ch04.html#N11448">4.10. Updating From 1.1 to 1.1.1</a></span></dt><dt><span class="section"><a href="ch04.html#N11482">4.11. Updating From 1.0.1 to 1.1</a></span></dt></dl></div><p>This section describes how to update a DSpace installation from one version to the next. Details of the differences between the functionality of each version are given in the <a class="link" href="ch14.html#docbook-history.html">Version History</a> section.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10D4B"></a>4.1.&nbsp;<a name="docbook-update.html-142_15"></a>Updating From 1.4.2 to 1.5</h2></div></div></div><p>The changes in DSpace 1.5 are significant and wide spread involving database schema upgrades, code restructuring, completely new user and programatic interfaces, and new build system.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-source]</code> to the source directory for DSpace 1.5. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Backup your DSpace</strong></span> First and foremost, make a complete backup of your system, including:</p><div class="itemizedlist"><ul type="disc"><li><p> A snapshot of the database</p></li><li><p> The asset store (<code class="literal">[dspace]/assetstore</code> by default)</p></li><li><p> Your configuration files and customizations to DSpace</p></li><li><p> Your statistics scripts (<code class="literal">[dspace]/bin/stat*</code>) which contain customizable dates</p></li></ul></div></li><li><p><span class="bold"><strong>Download DSpace 1.5</strong></span> Get the new DSpace 1.5 source code either as a download from <a class="ulink" href="#" target="_top">SourceForge</a> or check it out directly from the <a class="ulink" href="#" target="_top">SVN code repository</a>. If you downloaded DSpace do not unpack it on top of your existing installation.</p></li><li><p><span class="bold"><strong>Build DSpace</strong></span> The build process has radically changed for DSpace 1.5. With this new release the build system has moved to a maven-based system enabling the various projects (JSPUI, XMLUI, OAI, and Core API) into separate projects. See the <a class="link" href="ch03.html#docbook-install.html">Installation section</a> for more information on building DSpace using the new maven-based build system. Run the following commands to compile DSpace.</p><pre class="screen">
   cd [dspace-source]/dspace/;
   mvn package
 </pre><p>You will find the result in <code class="literal">[dspace-source]/dspace/target/dspace-1.5-build.dir/</code>; inside this directory is the compiled binary distribution of DSpace.</p></li><li><p><span class="bold"><strong>Stop Tomcat</strong></span> Take down your servlet container, for Tomcat use the <code class="literal">bin/shutdown.sh</code> script.</p></li><li><p><span class="bold"><strong>Update <code class="literal">dspace.cfg</code></strong></span> Serveral new parameters need to be added to your <code class="literal">[dspace]/config/dspace.cfg</code>. While it is advisable to start with a fresh <span class="emphasis"><em>DSpace 1.5 <code class="literal">dspace.cfg</code> configuration file</em></span> here are the minimum set of parameters that need to be added to an old <span class="emphasis"><em>DSpace 1.4.2 configuration</em></span>.</p><pre class="screen">
@@ -106,7 +106,7 @@ cp [dspace-source]/dspace/config/emails/registration_notify
  
 </pre></li><li><p><span class="bold"><strong>Update the database</strong></span> The database schema needs updating. SQL files contain the relevant updates are provided, note if you have made any local customizations to the database schema you should consult these updates and make sure they will work for you.</p><div class="itemizedlist"><ul type="disc"><li><p> For PostgreSQL </p><p>
                 <code class="literal">psql -U [dspace-user] -f [dspace-source]/dspace/etc/database_schema_14-15.sql [database-name]</code>
-              </p></li><li><p> For Oracle </p><p><code class="literal">[dspace-source]/dspace/etc/oracle/database_schema_142-15.sql</code> contains the commands necessary to upgrade your database schema on oracle.</p></li></ul></div></li><li><p><span class="bold"><strong>Apply any customizations</strong></span> If you have made any local customizations to your DSpace installation they will need to be migrated over to the new DSpace. Commonly these modifications are made to "JSP" pages located inside the <code class="literal">[dspace 1.4.2]/jsp/local</code> directory. These should be moved <code class="literal">[dspace-source]/dspace/modules/jspui/src/main/webapp/</code> in the new build structure. See <a class="ulink" href="configure.html#jspui-jsp" target="_top">Customizing the JSP Pages</a> for more information.</p></li><li><p><span class="bold"><strong>Update DSpace</strong></span> Update the DSpace installed directory with new code and libraries. Inside the <code class="literal">[dspace-source]/dspace/target/dspace-1.5-build.dir/</code> directory run:</p><pre class="screen">
+              </p></li><li><p> For Oracle </p><p><code class="literal">[dspace-source]/dspace/etc/oracle/database_schema_142-15.sql</code> contains the commands necessary to upgrade your database schema on oracle.</p></li></ul></div></li><li><p><span class="bold"><strong>Apply any customizations</strong></span> If you have made any local customizations to your DSpace installation they will need to be migrated over to the new DSpace. Commonly these modifications are made to "JSP" pages located inside the <code class="literal">[dspace 1.4.2]/jsp/local</code> directory. These should be moved <code class="literal">[dspace-source]/dspace/modules/jspui/src/main/webapp/</code> in the new build structure. See <a class="link" href="ch05.html#docbook-configure.html-jspui-jsp">Customizing the JSP Pages</a> for more information.</p></li><li><p><span class="bold"><strong>Update DSpace</strong></span> Update the DSpace installed directory with new code and libraries. Inside the <code class="literal">[dspace-source]/dspace/target/dspace-1.5-build.dir/</code> directory run:</p><pre class="screen">
 cd [dspace-source]/dspace/target/dspace-1.5-build.dir/;
 ant -Dconfig=[dspace]/config/dspace.cfg update
 </pre></li><li><p><span class="bold"><strong>Update the Metadata Registry</strong></span> New Metadata Registry updates are required to support SWORD.</p><pre class="screen">
@@ -131,7 +131,7 @@ cp [dspace-source]/dspace/config/registries/sword-metadata.xml
             <code class="literal">start.month = 1</code>
           </p><p> Replace '2005' and '1' as with the values you noted down.</p><p><code class="literal">dstat.cfg</code> also used to contain the hostname and service name as displayed at the top of the statistics. These values are now taken from <code class="literal">dspace.cfg</code> so you can remove <code class="literal">host.name</code> and <code class="literal">host.url</code> from <code class="literal">dstat.cfg</code> if you wish. The values now used are <code class="literal">dspace.hostname</code> and <code class="literal">dspace.name</code> from <code class="literal">dspace.cfg</code></p></li><li><p><span class="bold"><strong>Deploy webapplications</strong></span> Copy the webapplications files from your [dspace]/webapps directory to the subdirectory of your servlet container (e.g. Tomcat):</p><pre class="screen">
 cp [dspace]/webapps/* [tomcat]/webapps/
-</pre></li><li><p><span class="bold"><strong>Restart Tomcat</strong></span> Restart your servlet container, for Tomcat use the <code class="literal">bin/startup.sh</code> script.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10EB8"></a>4.2.&nbsp;<a name="docbook-update.html-141_142"></a>Updating From 1.4.1 to 1.4.2</h2></div></div></div><p> See <a class="link" href="ch04.html#docbook-update.html-14_14x">Updating From 1.4 to 1.4.x</a>; the same instructions apply. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10EC5"></a>4.3.&nbsp;<a name="docbook-update.html-14_14x"></a>Updating From 1.4 to 1.4.x</h2></div></div></div><p>The changes in 1.4.x releases are only code and configuration changes so the update is simply a matter of rebuilding the wars and slight changes to your config file.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.4.x-source]</code> to the source directory for DSpace 1.4.x. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.4.x source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
+</pre></li><li><p><span class="bold"><strong>Restart Tomcat</strong></span> Restart your servlet container, for Tomcat use the <code class="literal">bin/startup.sh</code> script.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10ECA"></a>4.2.&nbsp;<a name="docbook-update.html-141_142"></a>Updating From 1.4.1 to 1.4.2</h2></div></div></div><p> See <a class="link" href="ch04.html#docbook-update.html-14_14x">Updating From 1.4 to 1.4.x</a>; the same instructions apply. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10ED7"></a>4.3.&nbsp;<a name="docbook-update.html-14_14x"></a>Updating From 1.4 to 1.4.x</h2></div></div></div><p>The changes in 1.4.x releases are only code and configuration changes so the update is simply a matter of rebuilding the wars and slight changes to your config file.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.4.x-source]</code> to the source directory for DSpace 1.4.x. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.4.x source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp postgresql.jar <span class="emphasis"><em> [dspace-1.4.x-source]</em></span>/lib
 </pre></li><li><p><span class="bold"><strong>Note:</strong></span>  Licensing conditions for the <code class="literal">handle.jar</code> file have changed. As a result, the latest version of the <code class="literal">handle.jar</code> file is not included in this distribution. It is recommended you read the <a class="ulink" href="http://www.handle.net/upgrade_6-2_DSpace.html" target="_top">new license conditions</a> and decide whether you wish to update your installation's <code class="literal">handle.jar</code>. If you decide to update, you should replace the existing <code class="literal">handle.jar</code> in <span class="emphasis"><em>[dspace-1.4.x-source]</em></span>/lib with the new version.</p></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> A new configuration item <code class="literal">webui.html.max-depth-guess</code> has been added to avoid infinite URL spaces. Add the following to the dspace.cfg file:</p><pre class="screen">
@@ -159,7 +159,7 @@ ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg
 </pre></li><li><p> Copy the <code class="literal">.war</code> Web application files in <code class="literal">[dspace-1.4.x-source]/build</code> to the <code class="literal">webapps</code> sub-directory of your servlet container (e.g. Tomcat). e.g.:</p><pre class="screen">
 cp <span class="emphasis"><em> [dspace-1.4.x-source]</em></span>/build/*.war <span class="emphasis"><em>
 	[tomcat]</em></span>/webapps
-</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10F6E"></a>4.4.&nbsp;<a name="docbook-update.html-132_14"></a>Updating From 1.3.2 to 1.4.x</h2></div></div></div><div class="orderedlist"><ol type="1"><li><p> First and foremost, <span class="bold"><strong>make a complete backup</strong></span> of your system, including:</p><div class="itemizedlist"><ul type="disc"><li><p> A snapshot of the database</p></li><li><p> The asset store (<code class="literal">[dspace]/assetstore</code> by default)</p></li><li><p> Your configuration files and localized JSPs</p></li></ul></div></li><li><p> Download the <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">latest DSpace 1.4.x source bundle</a> and unpack it in a suitable location (<span class="emphasis"><em>not</em></span> over your existing DSpace installation or source tree!)</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
+</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N10F80"></a>4.4.&nbsp;<a name="docbook-update.html-132_14"></a>Updating From 1.3.2 to 1.4.x</h2></div></div></div><div class="orderedlist"><ol type="1"><li><p> First and foremost, <span class="bold"><strong>make a complete backup</strong></span> of your system, including:</p><div class="itemizedlist"><ul type="disc"><li><p> A snapshot of the database</p></li><li><p> The asset store (<code class="literal">[dspace]/assetstore</code> by default)</p></li><li><p> Your configuration files and localized JSPs</p></li></ul></div></li><li><p> Download the <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">latest DSpace 1.4.x source bundle</a> and unpack it in a suitable location (<span class="emphasis"><em>not</em></span> over your existing DSpace installation or source tree!)</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp postgresql.jar <span class="emphasis"><em> [dspace-1.4.x-source]</em></span>/lib
 </pre></li><li><p><span class="bold"><strong>Note:</strong></span>  Licensing conditions for the <code class="literal">handle.jar</code> file have changed. As a result, the latest version of the <code class="literal">handle.jar</code> file is not included in this distribution. It is recommended you read the <a class="ulink" href="http://www.handle.net/upgrade_6-2_DSpace.html" target="_top">new license conditions</a> and decide whether you wish to update your installation's <code class="literal">handle.jar</code>. If you decide to update, you should replace the existing <code class="literal">handle.jar</code> in <span class="emphasis"><em>[dspace-1.4.x-source]</em></span>/lib with the new version.</p></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> Your DSpace configuration will need some updating:</p><div class="itemizedlist"><ul type="disc"><li><p> In <code class="literal">dspace.cfg</code>, paste in the following lines for the new stackable authentication feature, the new method for managing Media Filters, and the Checksum Checker.</p><pre class="screen">
@@ -241,7 +241,7 @@ checker.retention.CHECKSUM_MATCH=8w
 search.index.1 = title:title.alternative
 </pre><p>That needs to be changed to:</p><pre class="screen">
 search.index.1 = title:dc.title.alternative
-</pre></li><li><p> If you use LDAP or X509 authentication, you'll need to add <code class="literal">org.dspace.eperson.LDAPAuthentication</code> or <code class="literal">org.dspace.eperson.X509Authentication</code> respectively. See also <a class="ulink" href="configure.html#authenticate" target="_top">configuring custom authentication code</a>.</p></li><li><p> If you have custom Media Filters, note that these are now configured through <code class="literal">dspace.cfg</code> (instead of <code class="literal">mediafilter.cfg</code> which is obsolete.)</p></li><li><p> Also, take a look through the default <code class="literal">dspace.cfg</code> file supplied with DSpace 1.4.x, as this contains configuration options for various new features you might like to use. In general, these new features default to 'off' and you'll need to add configuration properties as described in the default 1.4.x <code class="literal">dspace.cfg</code> to activate them.</p></li></ul></div></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you will need to merge the changes in the new 1.4.x versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare your JSPs against the 1.4.x versions to do this. You can also check against the <a class="ulink" href="http://dspace.cvs.sourceforge.net/dspace/" target="_top">DSpace CVS</a>.</p></li><li><p> In <code class="literal">[dspace-1.4.x-source]</code> run:</p><pre class="screen">
+</pre></li><li><p> If you use LDAP or X509 authentication, you'll need to add <code class="literal">org.dspace.eperson.LDAPAuthentication</code> or <code class="literal">org.dspace.eperson.X509Authentication</code> respectively. See also <a class="link" href="">configuring custom authentication code</a>.</p></li><li><p> If you have custom Media Filters, note that these are now configured through <code class="literal">dspace.cfg</code> (instead of <code class="literal">mediafilter.cfg</code> which is obsolete.)</p></li><li><p> Also, take a look through the default <code class="literal">dspace.cfg</code> file supplied with DSpace 1.4.x, as this contains configuration options for various new features you might like to use. In general, these new features default to 'off' and you'll need to add configuration properties as described in the default 1.4.x <code class="literal">dspace.cfg</code> to activate them.</p></li></ul></div></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you will need to merge the changes in the new 1.4.x versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare your JSPs against the 1.4.x versions to do this. You can also check against the <a class="ulink" href="http://dspace.cvs.sourceforge.net/dspace/" target="_top">DSpace CVS</a>.</p></li><li><p> In <code class="literal">[dspace-1.4.x-source]</code> run:</p><pre class="screen">
 ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg update
 </pre></li><li><p> The database schema needs updating. SQL files containing the relevant file are provided. If you've modified the schema locally, you may need to check over this and make alterations.</p><div class="variablelist"><dl><dt><span class="term">For PostgreSQL</span></dt><dd><p> <code class="literal">[dspace-1.4.x-source]/etc/database_schema_13-14.sql</code> contains the SQL commands to achieve this for PostgreSQL. To apply the changes, go to the source directory, and run:</p><p>
                   <code class="literal">psql -f etc/database_schema_13-14.sql [DSpace database name] -h localhost</code>
@@ -250,7 +250,7 @@ ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg
           </p></li><li><p> Copy the <code class="literal">.war</code> Web application files in <code class="literal">[dspace-1.4-source]/build</code> to the <code class="literal">webapps</code> sub-directory of your servlet container (e.g. Tomcat). e.g.:</p><pre class="screen">
 cp <span class="emphasis"><em> [dspace-1.4-source]</em></span>/build/*.war <span class="emphasis"><em>
 	[tomcat]</em></span>/webapps
-</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1107C"></a>4.5.&nbsp;<a name="docbook-update.html-131_132"></a>Updating From 1.3.1 to 1.3.2</h2></div></div></div><p>The changes in 1.3.2 are only code changes so the update is simply a matter of rebuilding the wars.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.3.2-source]</code> to the source directory for DSpace 1.3.2. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.3.2 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
+</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1108E"></a>4.5.&nbsp;<a name="docbook-update.html-131_132"></a>Updating From 1.3.1 to 1.3.2</h2></div></div></div><p>The changes in 1.3.2 are only code changes so the update is simply a matter of rebuilding the wars.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.3.2-source]</code> to the source directory for DSpace 1.3.2. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.3.2 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp postgresql.jar <span class="emphasis"><em> [dspace-1.3.2-source]</em></span>/lib
 </pre></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you will need to merge the changes in the new 1.3.2 versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare the 1.3.1 and 1.3.2 versions to do this.</p></li><li><p> In <code class="literal">[dspace-1.3.2-source]</code> run:</p><pre class="screen">
@@ -258,7 +258,7 @@ ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg
 </pre></li><li><p> Copy the <code class="literal">.war</code> Web application files in <code class="literal">[dspace-1.3.2-source]/build</code> to the <code class="literal">webapps</code> sub-directory of your servlet container (e.g. Tomcat). e.g.:</p><pre class="screen">
 cp <span class="emphasis"><em> [dspace-1.3.2-source]</em></span>/build/*.war <span class="emphasis"><em>
 	[tomcat]</em></span>/webapps
-</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N110F0"></a>4.6.&nbsp;<a name="docbook-update.html-12_13"></a>Updating From 1.2.x to 1.3.x</h2></div></div></div><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.3.x-source]</code> to the source directory for DSpace 1.3.x. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Step one is, of course, to <span class="bold"><strong>back up all your data</strong></span> before proceeding!! Include all of the contents of <code class="literal">[dspace]</code> and the PostgreSQL database in your backup.</p></li><li><p> Get the new DSpace 1.3.x source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><p>
+</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11102"></a>4.6.&nbsp;<a name="docbook-update.html-12_13"></a>Updating From 1.2.x to 1.3.x</h2></div></div></div><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.3.x-source]</code> to the source directory for DSpace 1.3.x. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Step one is, of course, to <span class="bold"><strong>back up all your data</strong></span> before proceeding!! Include all of the contents of <code class="literal">[dspace]</code> and the PostgreSQL database in your backup.</p></li><li><p> Get the new DSpace 1.3.x source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><p>
             <code class="literal">cd [dspace]/lib</code>
           </p><p>
             <code class="literal">cp postgresql.jar [dspace-1.2.2-source]/lib</code>
@@ -281,7 +281,7 @@ report.dir = /dspace/reports/
             <code class="literal">ant -Dconfig=[dspace]/config/dspace.cfg update</code>
           </p></li><li><p> You'll need to make some changes to the database schema in your PostgreSQL database. <code class="literal">[dspace-1.3.x-source]/etc/database_schema_12-13.sql</code> contains the SQL commands to achieve this. If you've modified the schema locally, you may need to check over this and make alterations.</p><p>To apply the changes, go to the source directory, and run:</p><p>
             <code class="literal">psql -f etc/database_schema_12-13.sql [DSpace database name] -h localhost</code>
-          </p></li><li><p> Customise the stat generating statistics as per the instructions in <a class="ulink" href="configure.html#statistics" target="_top">System Statistical Reports</a></p></li><li><p> Initialise the statistics using:</p><p>
+          </p></li><li><p> Customise the stat generating statistics as per the instructions in <a class="link" href="ch05.html#docbook-configure.html-statistics">System Statistical Reports</a></p></li><li><p> Initialise the statistics using:</p><p>
             <code class="literal">[dspace]/bin/stat-initial</code>
           </p><p>
             <code class="literal">[dspace]/bin/stat-general</code>
@@ -293,10 +293,10 @@ report.dir = /dspace/reports/
             <code class="literal">[dspace]/bin/index-all</code>
           </p></li><li><p> Copy the <code class="literal">.war</code> Web application files in <code class="literal">[dspace-1.3.x-source]/build</code> to the <code class="literal">webapps</code> sub-directory of your servlet container (e.g. Tomcat). e.g.:</p><p>
             <code class="literal">cp [dspace-1.3.x-source]/build/*.war [tomcat]/webapps</code>
-          </p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N111AF"></a>4.7.&nbsp;<a name="docbook-update.html-121_122"></a>Updating From 1.2.1 to 1.2.2</h2></div></div></div><p>The changes in 1.2.2 are only code and config changes so the update should be fairly simple.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.2.2-source]</code> to the source directory for DSpace 1.2.2. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.2.2 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
+          </p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N111C1"></a>4.7.&nbsp;<a name="docbook-update.html-121_122"></a>Updating From 1.2.1 to 1.2.2</h2></div></div></div><p>The changes in 1.2.2 are only code and config changes so the update should be fairly simple.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.2.2-source]</code> to the source directory for DSpace 1.2.2. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.2.2 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp postgresql.jar <span class="emphasis"><em> [dspace-1.2.2-source]</em></span>/lib
-</pre></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you might like to merge the changes in the new 1.2.2 versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare the 1.2.1 and 1.2.2 versions to do this. Also see <a class="ulink" href="history.html#jsp-changes-1_2_1-1_2_2" target="_top">the version history</a> for a list of modified JSPs.</p></li><li><p> You need to add a new parameter to your <code class="literal">[dspace]/dspace.cfg</code> for configurable fulltext indexing</p><pre class="screen">
+</pre></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you might like to merge the changes in the new 1.2.2 versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare the 1.2.1 and 1.2.2 versions to do this. Also see <a class="link" href="ch14.html#docbook-history.html-jsp-changes-1_2_1-1_2_2">the version history</a> for a list of modified JSPs.</p></li><li><p> You need to add a new parameter to your <code class="literal">[dspace]/dspace.cfg</code> for configurable fulltext indexing</p><pre class="screen">
 ##### Fulltext Indexing settings #####
 # Maximum number of terms indexed for a single field in Lucene.
 # Default is 10,000 words - often not enough for full-text indexing.
@@ -309,10 +309,10 @@ ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg
 </pre></li><li><p> Copy the <code class="literal">.war</code> Web application files in <code class="literal">[dspace-1.2.2-source]/build</code> to the <code class="literal">webapps</code> sub-directory of your servlet container (e.g. Tomcat). e.g.:</p><pre class="screen">
 cp <span class="emphasis"><em> [dspace-1.2.2-source]</em></span>/build/*.war <span class="emphasis"><em>
 	[tomcat]</em></span>/webapps
-</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> To finialise the install of the new configurable submission forms you need to copy the file <code class="literal">[dspace-1.2.2-source]/config/input-forms.xml</code> into <code class="literal">[dspace]/config</code>.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1123C"></a>4.8.&nbsp;<a name="docbook-update.html-12_121"></a>Updating From 1.2 to 1.2.1</h2></div></div></div><p>The changes in 1.2.1 are only code changes so the update should be fairly simple.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.2.1-source]</code> to the source directory for DSpace 1.2.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.2.1 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
+</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> To finialise the install of the new configurable submission forms you need to copy the file <code class="literal">[dspace-1.2.2-source]/config/input-forms.xml</code> into <code class="literal">[dspace]/config</code>.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1124E"></a>4.8.&nbsp;<a name="docbook-update.html-12_121"></a>Updating From 1.2 to 1.2.1</h2></div></div></div><p>The changes in 1.2.1 are only code changes so the update should be fairly simple.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.2.1-source]</code> to the source directory for DSpace 1.2.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Get the new DSpace 1.2.1 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the PostgreSQL driver JAR to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp postgresql.jar <span class="emphasis"><em> [dspace-1.2.1-source]</em></span>/lib
-</pre></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you might like to merge the changes in the new 1.2.1 versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare the 1.2 and 1.2.1 versions to do this. Also see <a class="ulink" href="history.html#jsp-changes-1_2-1_2_1" target="_top">the version history</a> for a list of modified JSPs.</p></li><li><p> You need to add a few new parameters to your <code class="literal">[dspace]/dspace.cfg</code> for browse/search and item thumbnails display, and for configurable DC metadata fields to be indexed.</p><pre class="screen">
+</pre></li><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> Your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. If you have locally modified JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you might like to merge the changes in the new 1.2.1 versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare the 1.2 and 1.2.1 versions to do this. Also see <a class="link" href="ch14.html#docbook-history.html-jsp-changes-1_2-1_2_1">the version history</a> for a list of modified JSPs.</p></li><li><p> You need to add a few new parameters to your <code class="literal">[dspace]/dspace.cfg</code> for browse/search and item thumbnails display, and for configurable DC metadata fields to be indexed.</p><pre class="screen">
 # whether to display thumbnails on browse and search results pages
 	(1.2+)
 webui.browse.thumbnail.show = false
@@ -360,7 +360,7 @@ ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg
 </pre></li><li><p> Copy the <code class="literal">.war</code> Web application files in <code class="literal">[dspace-1.2.1-source]/build</code> to the <code class="literal">webapps</code> sub-directory of your servlet container (e.g. Tomcat). e.g.:</p><pre class="screen">
 cp <span class="emphasis"><em> [dspace-1.2.1-source]</em></span>/build/*.war <span class="emphasis"><em>
 	[tomcat]</em></span>/webapps
-</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N112BE"></a>4.9.&nbsp;<a name="docbook-update.html-11_12"></a>Updating From 1.1 (or 1.1.1) to 1.2</h2></div></div></div><p>The process for upgrading to 1.2 from either 1.1 or 1.1.1 is the same. If you are running DSpace 1.0 or 1.0.1, you need to follow the <a class="link" href="ch04.html#docbook-update.html-101_11">instructions for upgrading from 1.0.1 to 1.1</a> to before following these instructions.</p><p>Note also that if you've substantially modified DSpace, these instructions apply to an unmodified 1.1.1 DSpace instance, and you'll need to adapt the process to any modifications you've made.</p><p>This document refers to the install directory for your existing DSpace installation as <code class="literal">[dspace]</code>, and to the source directory for DSpace 1.2 as <code class="literal">[dspace-1.2-source]</code>. Whenever you see these path references below, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Step one is, of course, to <span class="bold"><strong>back up all your data</strong></span> before proceeding!! Include all of the contents of <code class="literal">[dspace]</code> and the PostgreSQL database in your backup.</p></li><li><p> Get the new DSpace 1.2 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the <a class="ulink" href="install.html#javalibs" target="_top">required Java libraries</a> that we couldn't include in the bundle to the source tree. For example:</p><pre class="screen">
+</pre><p>If you're using Tomcat, you need to delete the directories corresponding to the old <code class="literal">.war</code> files. For example, if <code class="literal">dspace.war</code> is installed in <code class="literal">[tomcat]/webapps/dspace.war</code>, you should delete the <code class="literal">[tomcat]/webapps/dspace</code> directory. Otherwise, Tomcat will continue to use the old code in that directory.</p></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N112D0"></a>4.9.&nbsp;<a name="docbook-update.html-11_12"></a>Updating From 1.1 (or 1.1.1) to 1.2</h2></div></div></div><p>The process for upgrading to 1.2 from either 1.1 or 1.1.1 is the same. If you are running DSpace 1.0 or 1.0.1, you need to follow the <a class="link" href="ch04.html#docbook-update.html-101_11">instructions for upgrading from 1.0.1 to 1.1</a> to before following these instructions.</p><p>Note also that if you've substantially modified DSpace, these instructions apply to an unmodified 1.1.1 DSpace instance, and you'll need to adapt the process to any modifications you've made.</p><p>This document refers to the install directory for your existing DSpace installation as <code class="literal">[dspace]</code>, and to the source directory for DSpace 1.2 as <code class="literal">[dspace-1.2-source]</code>. Whenever you see these path references below, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Step one is, of course, to <span class="bold"><strong>back up all your data</strong></span> before proceeding!! Include all of the contents of <code class="literal">[dspace]</code> and the PostgreSQL database in your backup.</p></li><li><p> Get the new DSpace 1.2 source code from <a class="ulink" href="http://sourceforge.net/projects/dspace/" target="_top">the DSpace page on SourceForge</a> and unpack it somewhere. Do not unpack it on top of your existing installation!!</p></li><li><p> Copy the <a class="link" href="">required Java libraries</a> that we couldn't include in the bundle to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp activation.jar servlet.jar mail.jar <span class="emphasis"><em>
 	[dspace-1.2-source]</em></span>/lib
@@ -369,7 +369,7 @@ cp activation.jar servlet.jar mail.jar <span class="emphasis"><em>
 # maximum width and height of generated thumbnails
 thumbnail.maxwidth  80
 thumbnail.maxheight 80
-</pre><p>There are one or two other, optional extra parameters (for controlling the pool of database connections). See <a class="ulink" href="history.html" target="_top">the version history</a> for details. If you leave them out, defaults will be used.</p><p>Also, to avoid future confusion, you might like to <span class="bold"><strong>remove</strong></span> the following property, which is no longer required:</p><pre class="screen">
+</pre><p>There are one or two other, optional extra parameters (for controlling the pool of database connections). See <a class="link" href="ch14.html#docbook-history.html">the version history</a> for details. If you leave them out, defaults will be used.</p><p>Also, to avoid future confusion, you might like to <span class="bold"><strong>remove</strong></span> the following property, which is no longer required:</p><pre class="screen">
 config.template.oai-web.xml = <span class="emphasis"><em>
 	[dspace]</em></span>/oai/WEB-INF/web.xml
 </pre></li><li><p> The layout of the installation directory (i.e. the structure of the contents of <code class="literal">[dspace]</code>) has changed somewhat since 1.1.1. First up, your 'localized' JSPs (those in jsp/local) now need to be maintained in the <span class="emphasis"><em>source</em></span> directory. So make a copy of them now!</p><p>Once you've done that, you can remove <code class="literal">[dspace]/jsp</code> and <code class="literal">[dspace]/oai</code>, these are no longer used. (.war Web application archive files are used instead).</p><p>Also, if you're using the same version of Tomcat as before, you need to <span class="bold"><strong>remove the lines from Tomcat's conf/server.xml file that enable symbolic links for DSpace.</strong></span> These are the <code class="literal">&lt;Context&gt;</code> elements you added to get DSpace 1.1.1 working, looking something like this:</p><pre class="screen">
@@ -399,7 +399,7 @@ cp <span class="emphasis"><em> [dspace-1.2-source]</em></span>/build/*.war <span
 </pre></li><li><p> Restart Tomcat.</p></li><li><p> To get image thumbnails generated and full-text extracted for indexing automatically, you need to set up a 'cron' job, for example one like this:</p><pre class="screen">
 # Run the media filter at 02:00 every day
 0 2 * * * <span class="emphasis"><em> [dspace]</em></span>/bin/filter-media
-</pre><p>You might also wish to run it now to generate thumbnails and index full text for the content already in your system.</p></li><li><p> <span class="bold"><strong>Note 1</strong></span>: This update process has effectively 'touched' all of your items. Although the dates in the Dublin Core metadata won't have changed (accession date and so forth), the 'last modified' date in the database for each will have been changed.</p><p>This means the e-mail subscription tool may be confused, thinking that all items in the archive have been deposited that day, and could thus send a rather long email to lots of subscribers. So, it is recommended that you <span class="bold"><strong>turn off the e-mail subscription feature for the next day</strong></span>, by commenting out the relevant line in DSpace's cron job, and then re-activating it the next day.</p><p>Say you performed the update on 08-June-2004 (UTC), and your e-mail subscription cron job runs at 4am (UTC). When the subscription tool runs at 4am on 09-June-2004, it will find that everything in the system has a modification date in 08-June-2004, and accordingly send out huge emails. So, immediately after the update, you would edit DSpace's 'crontab' and comment out the <code class="literal">/dspace/bin/subs-daily</code> line. Then, after 4am on 09-June-2004 you'd 'un-comment' it out, so that things proceed normally.</p><p>Of course this means, any <span class="emphasis"><em>real</em></span> new deposits on 08-June-2004 won't get e-mailed, however if you're updating the system it's likely to be down for some time so this shouldn't be a big problem.</p></li><li><p> <span class="bold"><strong>Note 2:</strong></span> After consulation with the OAI community, various OAI-PMH changes have occurred:</p><div class="itemizedlist"><ul type="disc"><li><p> The OAI-PMH identifiers have changed (they're now of the form <code class="literal">oai:hostname:handle</code> as opposed to just Handles)</p></li><li><p> The set structure has changed, due to the new sub-communities feature.</p></li><li><p> The default base URL has changed</p></li><li><p> As noted in note 1, every item has been 'touched' and will need re-harvesting.</p></li></ul></div><p>The above means that, if already registered and harvested, you will need to re-register your repository, effectively as a 'new' OAI-PMH data provider. You should also consider posting an announcement to the <a class="ulink" href="http://www.openarchives.org/mailman/listinfo/OAI-implementers" target="_top">OAI implementers e-mail list</a> so that harvesters know to update their systems.</p><p>Also note that your site may, over the next few days, take quite a big hit from OAI-PMH harvesters. The resumption token support should alleviate this a little, but you might want to temporarily whack up the database connection pool parameters in <code class="literal">[dspace]/config/dspace.cfg</code>. See the <code class="literal">dspace.cfg</code> distributed with the source code to see what these parameters are and how to use them. (You need to stop and restart Tomcat after changing them.)</p><p>I realize this is not ideal; for discussion as to the reasons behind this please see relevant posts to the OAI community: <a class="ulink" href="http://openarchives.org/pipermail/oai-implementers/2004-June/001214.html" target="_top">post one</a>, <a class="ulink" href="http://openarchives.org/pipermail/oai-implementers/2004-June/001224.html" target="_top">post two</a>, as well as <a class="ulink" href="#" target="_top">this post to the dspace-tech mailing list</a>.</p><p>If you really can't live with updating the base URL like this, you can fairly easily have thing proceed more-or-less as they are, by doing the following:</p><div class="itemizedlist"><ul type="disc"><li><p> Change the value of <code class="literal">OAI_ID_PREFIX</code> at the top of the <code class="literal">org.dspace.app.oai.DSpaceOAICatalog</code> class to <code class="literal">hdl:</code></p></li><li><p> Change the servlet mapping for the <code class="literal">OAIHandler</code> servlet back to <code class="literal">/</code> (from <code class="literal">/request</code>)</p></li><li><p> Rebuild and deploy <code class="literal">oai.war</code></p></li></ul></div><p>However, note that in this case, all the records will be re-harvested by harvesters anyway, so you still need to brace for the associated DB activity; also note that the set spec changes may not be picked up by some harvesters. It's recommended you read the above-linked mailing list posts to understand why the change was made.</p></li></ol></div><p>Now, you should be finished!</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11436"></a>4.10.&nbsp;<a name="docbook-update.html-11_111"></a>Updating From 1.1 to 1.1.1</h2></div></div></div><p>Fortunately the changes in 1.1.1 are only code changes so the update is fairly simple.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.1.1-source]</code> to the source directory for DSpace 1.1.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Take down Tomcat.</p></li><li><p> It would be a good idea to update any of the third-party tools used by DSpace at this point (e.g. PostgreSQL), following the instructions provided with the relevant tools.</p></li><li><p> In <code class="literal">[dspace-1.1.1-source]</code> run:</p><pre class="screen">
+</pre><p>You might also wish to run it now to generate thumbnails and index full text for the content already in your system.</p></li><li><p> <span class="bold"><strong>Note 1</strong></span>: This update process has effectively 'touched' all of your items. Although the dates in the Dublin Core metadata won't have changed (accession date and so forth), the 'last modified' date in the database for each will have been changed.</p><p>This means the e-mail subscription tool may be confused, thinking that all items in the archive have been deposited that day, and could thus send a rather long email to lots of subscribers. So, it is recommended that you <span class="bold"><strong>turn off the e-mail subscription feature for the next day</strong></span>, by commenting out the relevant line in DSpace's cron job, and then re-activating it the next day.</p><p>Say you performed the update on 08-June-2004 (UTC), and your e-mail subscription cron job runs at 4am (UTC). When the subscription tool runs at 4am on 09-June-2004, it will find that everything in the system has a modification date in 08-June-2004, and accordingly send out huge emails. So, immediately after the update, you would edit DSpace's 'crontab' and comment out the <code class="literal">/dspace/bin/subs-daily</code> line. Then, after 4am on 09-June-2004 you'd 'un-comment' it out, so that things proceed normally.</p><p>Of course this means, any <span class="emphasis"><em>real</em></span> new deposits on 08-June-2004 won't get e-mailed, however if you're updating the system it's likely to be down for some time so this shouldn't be a big problem.</p></li><li><p> <span class="bold"><strong>Note 2:</strong></span> After consulation with the OAI community, various OAI-PMH changes have occurred:</p><div class="itemizedlist"><ul type="disc"><li><p> The OAI-PMH identifiers have changed (they're now of the form <code class="literal">oai:hostname:handle</code> as opposed to just Handles)</p></li><li><p> The set structure has changed, due to the new sub-communities feature.</p></li><li><p> The default base URL has changed</p></li><li><p> As noted in note 1, every item has been 'touched' and will need re-harvesting.</p></li></ul></div><p>The above means that, if already registered and harvested, you will need to re-register your repository, effectively as a 'new' OAI-PMH data provider. You should also consider posting an announcement to the <a class="ulink" href="http://www.openarchives.org/mailman/listinfo/OAI-implementers" target="_top">OAI implementers e-mail list</a> so that harvesters know to update their systems.</p><p>Also note that your site may, over the next few days, take quite a big hit from OAI-PMH harvesters. The resumption token support should alleviate this a little, but you might want to temporarily whack up the database connection pool parameters in <code class="literal">[dspace]/config/dspace.cfg</code>. See the <code class="literal">dspace.cfg</code> distributed with the source code to see what these parameters are and how to use them. (You need to stop and restart Tomcat after changing them.)</p><p>I realize this is not ideal; for discussion as to the reasons behind this please see relevant posts to the OAI community: <a class="ulink" href="http://openarchives.org/pipermail/oai-implementers/2004-June/001214.html" target="_top">post one</a>, <a class="ulink" href="http://openarchives.org/pipermail/oai-implementers/2004-June/001224.html" target="_top">post two</a>, as well as <a class="ulink" href="#" target="_top">this post to the dspace-tech mailing list</a>.</p><p>If you really can't live with updating the base URL like this, you can fairly easily have thing proceed more-or-less as they are, by doing the following:</p><div class="itemizedlist"><ul type="disc"><li><p> Change the value of <code class="literal">OAI_ID_PREFIX</code> at the top of the <code class="literal">org.dspace.app.oai.DSpaceOAICatalog</code> class to <code class="literal">hdl:</code></p></li><li><p> Change the servlet mapping for the <code class="literal">OAIHandler</code> servlet back to <code class="literal">/</code> (from <code class="literal">/request</code>)</p></li><li><p> Rebuild and deploy <code class="literal">oai.war</code></p></li></ul></div><p>However, note that in this case, all the records will be re-harvested by harvesters anyway, so you still need to brace for the associated DB activity; also note that the set spec changes may not be picked up by some harvesters. It's recommended you read the above-linked mailing list posts to understand why the change was made.</p></li></ol></div><p>Now, you should be finished!</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11448"></a>4.10.&nbsp;<a name="docbook-update.html-11_111"></a>Updating From 1.1 to 1.1.1</h2></div></div></div><p>Fortunately the changes in 1.1.1 are only code changes so the update is fairly simple.</p><p>In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.1.1-source]</code> to the source directory for DSpace 1.1.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Take down Tomcat.</p></li><li><p> It would be a good idea to update any of the third-party tools used by DSpace at this point (e.g. PostgreSQL), following the instructions provided with the relevant tools.</p></li><li><p> In <code class="literal">[dspace-1.1.1-source]</code> run:</p><pre class="screen">
 ant -Dconfig=<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg update
 </pre></li><li><p> If you have locally modified JSPs of the following JSPs in your <code class="literal">[dspace]/jsp/local</code> directory, you might like to merge the changes in the new 1.1.1 versions into your locally modified ones. You can use the <code class="literal">diff</code> command to compare the 1.1 and 1.1.1 versions to do this. The changes are quite minor.</p><pre class="screen">
 collection-home.jsp
@@ -407,7 +407,7 @@ admin/authorize-collection-edit.jsp
 admin/authorize-community-edit.jsp
 admin/authorize-item-edit.jsp
 admin/eperson-edit.jsp
-</pre></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11470"></a>4.11.&nbsp;<a name="docbook-update.html-101_11"></a>Updating From 1.0.1 to 1.1</h2></div></div></div><p>To upgrade from DSpace 1.0.1 to 1.1, follow the steps below. Your <code class="literal">dspace.cfg</code> does not need to be changed. In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.1-source]</code> to the source directory for DSpace 1.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> We recommend that you upgrage to the latest version of PostgreSQL (7.3.2). Included are some <a class="ulink" href="postgres-upgrade-notes.txt" target="_top">notes to help you do this</a>. Note you will also have to upgrade Ant to version 1.5 if you do this.</p></li><li><p> Make the necessary changes to the DSpace database. These include a couple of minor schema changes, and some new indices which should improve performance. Also, the names of a couple of database views have been changed since the old names were so long they were causing problems. First run <code class="literal">psql</code> to access your database (e.g. <code class="literal">psql -U dspace -W</code> and then enter the password), and enter these SQL commands:</p><pre class="screen">
+</pre></li><li><p> Restart Tomcat.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11482"></a>4.11.&nbsp;<a name="docbook-update.html-101_11"></a>Updating From 1.0.1 to 1.1</h2></div></div></div><p>To upgrade from DSpace 1.0.1 to 1.1, follow the steps below. Your <code class="literal">dspace.cfg</code> does not need to be changed. In the notes below <code class="literal">[dspace]</code> refers to the install directory for your existing DSpace installation, and <code class="literal">[dspace-1.1-source]</code> to the source directory for DSpace 1.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</p><div class="orderedlist"><ol type="1"><li><p> Take down Tomcat (or whichever servlet container you're using).</p></li><li><p> We recommend that you upgrage to the latest version of PostgreSQL (7.3.2). Included are some <a class="ulink" href="postgres-upgrade-notes.txt" target="_top">notes to help you do this</a>. Note you will also have to upgrade Ant to version 1.5 if you do this.</p></li><li><p> Make the necessary changes to the DSpace database. These include a couple of minor schema changes, and some new indices which should improve performance. Also, the names of a couple of database views have been changed since the old names were so long they were causing problems. First run <code class="literal">psql</code> to access your database (e.g. <code class="literal">psql -U dspace -W</code> and then enter the password), and enter these SQL commands:</p><pre class="screen">
 ALTER TABLE bitstream ADD store_number INTEGER;
 UPDATE bitstream SET store_number = 0;
 
@@ -449,7 +449,7 @@ CREATE VIEW CollectionItemsByDateAccession AS SELECT
 	charset=UTF-8"&gt;
 </pre><p>to the &lt;HEAD&gt; element. If you have any locally-edited JSPs, you need to add this page directive to the top of all of them:</p><pre class="screen">
 &lt;%@ page contentType="text/html;charset=UTF-8" %&gt;
-</pre><p>(If you haven't modified any JSPs, you don't have to do anything.)</p></li><li><p> Copy the <a class="ulink" href="install.html#javalibs" target="_top">required Java libraries</a> that we couldn't include in the bundle to the source tree. For example:</p><pre class="screen">
+</pre><p>(If you haven't modified any JSPs, you don't have to do anything.)</p></li><li><p> Copy the <a class="link" href="">required Java libraries</a> that we couldn't include in the bundle to the source tree. For example:</p><pre class="screen">
 cd <span class="emphasis"><em> [dspace]</em></span>/lib
 cp *.policy activation.jar servlet.jar mail.jar <span class="emphasis"><em>
 	[dspace-1.1-source]</em></span>/lib
@@ -472,7 +472,7 @@ Identify.deletedRecord=persistent
 <span class="emphasis"><em> [dspace]</em></span>/bin/index-all
 </pre></li><li><p> Restart Tomcat. Tomcat should be run with the following environment variable set, to ensure that Unicode is handled properly. Also, the default JVM memory heap sizes are rather small. Adjust <code class="literal">-Xmx512M</code> (512Mb maximum heap size) and <code class="literal">-Xms64M</code> (64Mb Java thread stack size) to suit your hardware.</p><pre class="screen">
 JAVA_OPTS="-Xmx512M -Xms64M -Dfile.encoding=UTF-8"
-</pre></li></ol></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre></li></ol></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch05.html b/dspace/docs/html/ch05.html
index 7d84294f22..047af868dc 100644
--- a/dspace/docs/html/ch05.html
+++ b/dspace/docs/html/ch05.html
@@ -1,9 +1,10 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch04.html" title="Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation"><link rel="next" href="ch06.html" title="Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch04.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch06.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N11517"></a>Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch05.html#N11542">5.1. General Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N1154B">5.1.1. The dspace.cfg Configuration Properties File</a></span></dt><dt><span class="section"><a href="ch05.html#N11898">5.1.2. Configuring Lucene Search Indexes</a></span></dt><dt><span class="section"><a href="ch05.html#N118E4">5.1.3. Browse Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N119FC">5.1.4. Configuring Media Filters</a></span></dt><dt><span class="section"><a href="ch05.html#N11A42">5.1.5. Wording of E-mail Messages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11A6B">5.2. The Metadata and Bitstream Format Registries</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11A89">5.2.1. Metadata Schema Registry</a></span></dt><dt><span class="section"><a href="ch05.html#N11A97">5.2.2. Metadata Format Registries</a></span></dt><dt><span class="section"><a href="ch05.html#N11AB7">5.2.3. Bitstream Format Registry</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11AD2">5.3. The Default Submission License</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11AE7">5.3.1. Possible Points in a License</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11B1F">5.4. Submission Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N11B2C">5.5. XMLUI Interface Customizations (Manakin)</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11B35">5.5.1. XMLUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11CD8">5.5.2. Configuring Themes and Aspects</a></span></dt><dt><span class="section"><a href="ch05.html#N11D82">5.5.3. Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N11DC7">5.5.4. Creating a New Theme</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11E16">5.6. JSPUI Interface Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11E1F">5.6.1. JSPUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11F12">5.6.2. Configuring Controlled Vocabularies</a></span></dt><dt><span class="section"><a href="ch05.html#N11F7D">5.6.3. Configuring Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N1207F">5.6.4. Customizing the JSP pages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N12150">5.7. Advanced DSpace Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N12159">5.7.1. Checksum Checker</a></span></dt><dt><span class="section"><a href="ch05.html#N1224D">5.7.2. Custom Authentication</a></span></dt><dt><span class="section"><a href="ch05.html#N123C1">5.7.3. Configuring System Statistical Reports</a></span></dt><dt><span class="section"><a href="ch05.html#N12418">5.7.4. Activating Additional OAI-PMH Crosswalks</a></span></dt><dt><span class="section"><a href="ch05.html#N124B1">5.7.5. Configuring Packager Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N124D0">5.7.6. Configuring Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N12660">5.7.7. Creating a new Media/Format Filter</a></span></dt><dt><span class="section"><a href="ch05.html#N12764">5.7.8. Configuration Files for Other Applications</a></span></dt><dt><span class="section"><a href="ch05.html#N127C6">5.7.9. Browse Index Creation</a></span></dt></dl></dd></dl></div><p>There are a number of ways in which DSpace can be configured and/or customized:</p><div class="itemizedlist"><ul type="disc"><li><p> Altering the configuration files in <code class="literal">[dspace]/config</code></p></li><li><p> Creating a new XMLUI (Manakin) theme to change the look-and-feel of the repository</p></li><li><p> Creating modified versions of the JSP pages for local changes in the JSPUI interface</p></li><li><p> Implementing a custom 'plug-in' class -- for example, an 'authenticator' class, so that user authentication in the Web UI can be adapted and integrated with any existing mechanisms your organization might use, or a 'media filter' to generate thumbnails or extract full text from a new file format</p></li><li><p> Editing the source code</p></li></ul></div><p>Of these methods, only the last is likely to cause any headaches; if you update the DSpace source code directly, particularly core class files in <code class="literal">org.dspace.*</code> or <code class="literal">org.dspace.storage.*</code>, it may make applying future updates difficult. Before doing this, it is strongly recommended that you <a class="ulink" href="http://wiki.dspace.org/DspaceResources" target="_top">e-mail the DSpace developer community</a> to find out the best way to proceed, and the best way to implement your change in a way that can be <a class="ulink" href="http://wiki.dspace.org/HowToContribute" target="_top">contributed back to DSpace</a> for everyone's benefit.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11542"></a>5.1.&nbsp;<a name="docbook-configure.html-general"></a>General Configuration</h2></div></div></div><p>These are general configuration options that apply to the core of DSpace regardless of which interface you are using (JSPUI or XMLUI).</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1154B"></a>5.1.1.&nbsp;<a name="docbook-configure.html-general-dspacecfg"></a>The <code class="literal">dspace.cfg</code> Configuration Properties File</h3></div></div></div><p>The primary way of configuring DSpace is to edit the <code class="literal">dspace.cfg</code>. You'll definitely have to do this before you can operate DSpace properly. <code class="literal">dspace.cfg</code> contains basic information about a DSpace installation, including system path information, network host information, and other things like site name.</p><p>The default <code class="literal">dspace.cfg</code> is a good source of information, and contains comments for all properties. It's a basic Java properties file, where lines are either comments, starting with a '<code class="literal">#</code>', blank lines, or property/value pairs of the form:</p><pre class="screen">
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch04.html" title="Chapter&nbsp;4.&nbsp;DSpace System Documentation: Updating a DSpace Installation"><link rel="next" href="ch06.html" title="Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch04.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch06.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N11529"></a>Chapter&nbsp;5.&nbsp;<a name="docbook-configure.html"></a>DSpace System Documentation: Configuration and Customization</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch05.html#N11556">5.1. General Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N1155F">5.1.1. The dspace.cfg Configuration Properties File</a></span></dt><dt><span class="section"><a href="ch05.html#N118AC">5.1.2. Configuring Lucene Search Indexes</a></span></dt><dt><span class="section"><a href="ch05.html#N118F8">5.1.3. Browse Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N11A10">5.1.4. Configuring Media Filters</a></span></dt><dt><span class="section"><a href="ch05.html#N11A56">5.1.5. Wording of E-mail Messages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11A7F">5.2. The Metadata and Bitstream Format Registries</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11A9D">5.2.1. Metadata Schema Registry</a></span></dt><dt><span class="section"><a href="ch05.html#N11AAB">5.2.2. Metadata Format Registries</a></span></dt><dt><span class="section"><a href="ch05.html#N11ACB">5.2.3. Bitstream Format Registry</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11AE6">5.3. The Default Submission License</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11AFB">5.3.1. Possible Points in a License</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11B33">5.4. Submission Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N11B40">5.5. XMLUI Interface Customizations (Manakin)</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11B49">5.5.1. XMLUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11CEC">5.5.2. Configuring Themes and Aspects</a></span></dt><dt><span class="section"><a href="ch05.html#N11D96">5.5.3. Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N11DDB">5.5.4. Creating a New Theme</a></span></dt><dt><span class="section"><a href="ch05.html#N11E2A">5.5.5. Adding Static Content</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11E4A">5.6. JSPUI Interface Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11E53">5.6.1. JSPUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11F46">5.6.2. Configuring Controlled Vocabularies</a></span></dt><dt><span class="section"><a href="ch05.html#N11FB1">5.6.3. Configuring Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N120B3">5.6.4. Customizing the JSP pages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N12184">5.7. Advanced DSpace Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N1218D">5.7.1. Checksum Checker</a></span></dt><dt><span class="section"><a href="ch05.html#N12281">5.7.2. Custom Authentication</a></span></dt><dt><span class="section"><a href="ch05.html#N123F5">5.7.3. Configuring System Statistical Reports</a></span></dt><dt><span class="section"><a href="ch05.html#N1244C">5.7.4. Activating Additional OAI-PMH Crosswalks</a></span></dt><dt><span class="section"><a href="ch05.html#N124E5">5.7.5. Configuring Packager Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N12504">5.7.6. Configuring Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N12694">5.7.7. Creating a new Media/Format Filter</a></span></dt><dt><span class="section"><a href="ch05.html#N12798">5.7.8. Configuration Files for Other Applications</a></span></dt><dt><span class="section"><a href="ch05.html#N127FA">5.7.9. Browse Index Creation</a></span></dt><dt><span class="section"><a href="ch05.html#N12873">5.7.10. 
+      		Configuring Usage Instrumentation Plugins</a></span></dt></dl></dd></dl></div><p>There are a number of ways in which DSpace can be configured and/or customized:</p><div class="itemizedlist"><ul type="disc"><li><p> Altering the configuration files in <code class="literal">[dspace]/config</code></p></li><li><p> Creating a new XMLUI (Manakin) theme to change the look-and-feel of the repository</p></li><li><p> Creating modified versions of the JSP pages for local changes in the JSPUI interface</p></li><li><p> Implementing a custom 'plug-in' class -- for example, an 'authenticator' class, so that user authentication in the Web UI can be adapted and integrated with any existing mechanisms your organization might use, or a 'media filter' to generate thumbnails or extract full text from a new file format</p></li><li><p> Editing the source code</p></li></ul></div><p>Of these methods, only the last is likely to cause any headaches; if you update the DSpace source code directly, particularly core class files in <code class="literal">org.dspace.*</code> or <code class="literal">org.dspace.storage.*</code>, it may make applying future updates difficult. Before doing this, it is strongly recommended that you <a class="ulink" href="http://wiki.dspace.org/DspaceResources" target="_top">e-mail the DSpace developer community</a> to find out the best way to proceed, and the best way to implement your change in a way that can be <a class="ulink" href="http://wiki.dspace.org/HowToContribute" target="_top">contributed back to DSpace</a> for everyone's benefit.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11556"></a>5.1.&nbsp;<a name="docbook-configure.html-general"></a>General Configuration</h2></div></div></div><p>These are general configuration options that apply to the core of DSpace regardless of which interface you are using (JSPUI or XMLUI).</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1155F"></a>5.1.1.&nbsp;<a name="docbook-configure.html-general-dspacecfg"></a>The <code class="literal">dspace.cfg</code> Configuration Properties File</h3></div></div></div><p>The primary way of configuring DSpace is to edit the <code class="literal">dspace.cfg</code>. You'll definitely have to do this before you can operate DSpace properly. <code class="literal">dspace.cfg</code> contains basic information about a DSpace installation, including system path information, network host information, and other things like site name.</p><p>The default <code class="literal">dspace.cfg</code> is a good source of information, and contains comments for all properties. It's a basic Java properties file, where lines are either comments, starting with a '<code class="literal">#</code>', blank lines, or property/value pairs of the form:</p><pre class="screen">
 property.name = property value
 </pre><p>The property value may contain <span class="emphasis"><em>references</em></span> to other configuration properties, in the form <code class="literal">${</code>property.name<code class="literal">}</code>. This follows the <code class="literal">ant</code> convention of allowing references in property files. A property may not refer to itself. Examples:</p><pre class="screen">
 property.name = word1 ${other.property.name} more words
 property2.name = ${dspace.dir}/rest/of/path
-</pre><p> Whenever you edit dspace.cfg in [dspace-source]/dspace/config/, you should then run 'ant init_configs' in the directory [dspace-source]/dspace/target/dspace-1.5.0-build.dir so that any changes you may have made are reflected in the configuration files of other applications, for example Apache. You may then need to restart those applications, depending on what you changed. <div class="table"><a name="N11583"></a><p class="title"><b>Table&nbsp;5.1.&nbsp;dspace.cfg Main Properties (Not Complete)</b></p><div class="table-contents"><table summary="dspace.cfg Main Properties (Not Complete)" border="0"><colgroup><col><col><col></colgroup><tbody><tr><td>
+</pre><p> Whenever you edit dspace.cfg in [dspace-source]/dspace/config/, you should then run 'ant init_configs' in the directory [dspace-source]/dspace/target/dspace-1.5.0-build.dir so that any changes you may have made are reflected in the configuration files of other applications, for example Apache. You may then need to restart those applications, depending on what you changed. <div class="table"><a name="N11597"></a><p class="title"><b>Table&nbsp;5.1.&nbsp;dspace.cfg Main Properties (Not Complete)</b></p><div class="table-contents"><table summary="dspace.cfg Main Properties (Not Complete)" border="0"><colgroup><col><col><col></colgroup><tbody><tr><td>
                     <p>
                       <span class="bold"><strong>Property</strong></span>
                     </p>
@@ -107,7 +108,7 @@ property2.name = ${dspace.dir}/rest/of/path
                       <code class="literal">1721.1234</code>
                     </p>
                   </td><td>
-                    <p>The Handle prefix for your site, <a class="ulink" href="install.html#handles" target="_top">see the Handle section</a></p>
+                    <p>The Handle prefix for your site, <a class="link" href="ch03.html#docbook-install.html-handles">see the Handle section</a></p>
                   </td></tr><tr><td>
                     <p>
                       <code class="literal">assetstore.dir</code>
@@ -127,7 +128,7 @@ property2.name = ${dspace.dir}/rest/of/path
                       <code class="literal">/anotherdisk/store1</code>
                     </p>
                   </td><td>
-                    <p>The location in the file system of asset (bitstream) store number <code class="literal">n</code>. When adding additional stores, start with 1 (<code class="literal">assetstore.dir.1</code> and count upwards. Always leave asset store zero (<code class="literal">assetstore.dir</code>). For more details, see <a class="ulink" href="storage.html#bitstreams" target="_top">the Bitstream Storage section</a>.</p>
+                    <p>The location in the file system of asset (bitstream) store number <code class="literal">n</code>. When adding additional stores, start with 1 (<code class="literal">assetstore.dir.1</code> and count upwards. Always leave asset store zero (<code class="literal">assetstore.dir</code>). For more details, see <a class="link" href="ch06.html#docbook-storage.html-bitstreams">the Bitstream Storage section</a>.</p>
                   </td></tr><tr><td>
                     <p>
                       <code class="literal">assetstore.incoming</code>
@@ -137,14 +138,14 @@ property2.name = ${dspace.dir}/rest/of/path
                       <code class="literal">1</code>
                     </p>
                   </td><td>
-                    <p>The asset store number to use for storing new bitstreams. For example, if <code class="literal">assetstore.dir.1</code> is <code class="literal">/anotherdisk/store1</code>, and <code class="literal">assetstore.incoming</code> is <code class="literal">1</code>, new bitstreams will be stored under <code class="literal">/anotherdisk/store1</code>. A value of <code class="literal">0</code> (zero) corresponds to <code class="literal">assetstore.dir</code>. For more details, see <a class="ulink" href="storage.html#bitstreams" target="_top">the Bitstream Storage section</a>.</p>
+                    <p>The asset store number to use for storing new bitstreams. For example, if <code class="literal">assetstore.dir.1</code> is <code class="literal">/anotherdisk/store1</code>, and <code class="literal">assetstore.incoming</code> is <code class="literal">1</code>, new bitstreams will be stored under <code class="literal">/anotherdisk/store1</code>. A value of <code class="literal">0</code> (zero) corresponds to <code class="literal">assetstore.dir</code>. For more details, see <a class="link" href="ch06.html#docbook-storage.html-bitstreams">the Bitstream Storage section</a>.</p>
                   </td></tr><tr><td>
                     <p>srb.xxx</p>
                     <p>srb.xxx.n</p>
                   </td><td>
                     <p>/zone/home/user.domain</p>
                   </td><td>
-                    <p>The sets of SRB access parameters (see dspace.cfg) if one or more SRB accounts are used. The srb.xxx set would correspond to asset (bitstream) store number zero. The srb.xxx.n set would correspond to asset (bitstream) store number n. For more details, see <a class="ulink" href="storage.html#bitstreams" target="_top">the Bitstream Storage section</a>.</p>
+                    <p>The sets of SRB access parameters (see dspace.cfg) if one or more SRB accounts are used. The srb.xxx set would correspond to asset (bitstream) store number zero. The srb.xxx.n set would correspond to asset (bitstream) store number n. For more details, see <a class="link" href="ch06.html#docbook-storage.html-bitstreams">the Bitstream Storage section</a>.</p>
                   </td></tr><tr><td>
                     <p>
                       <code class="literal">webui.submit.enable-cc</code>
@@ -282,7 +283,7 @@ property2.name = ${dspace.dir}/rest/of/path
   dspace.dir = /dspace
   dspace.history = ${dspace.dir}/history
  
-</pre><p>Then the value of the <code class="literal">dspace.history</code> property is expanded to be <code class="literal">/dspace/history</code>. This method is especially useful for handling commonly used file paths.</p><p>Whenever you edit <code class="literal">dspace.cfg</code>, you should then run <code class="literal">[dspace]/bin/install-configs</code> so that any changes you may have made are reflected in the configuration files of other applications, for example Apache. You may then need to restart those applications, depending on what you changed.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11898"></a>5.1.2.&nbsp;<a name="docbook-configure.html-general-search"></a>Configuring Lucene Search Indexes</h3></div></div></div><p>Search Indexes can be configured via the <code class="literal">dspace.cfg</code> file. This allows institutions to choose which DSpace metadata fields are indexed by Lucene.</p><p>For example, the following entries appear in a default DSpace installation:</p><pre class="screen">
+</pre><p>Then the value of the <code class="literal">dspace.history</code> property is expanded to be <code class="literal">/dspace/history</code>. This method is especially useful for handling commonly used file paths.</p><p>Whenever you edit <code class="literal">dspace.cfg</code>, you should then run <code class="literal">[dspace]/bin/install-configs</code> so that any changes you may have made are reflected in the configuration files of other applications, for example Apache. You may then need to restart those applications, depending on what you changed.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N118AC"></a>5.1.2.&nbsp;<a name="docbook-configure.html-general-search"></a>Configuring Lucene Search Indexes</h3></div></div></div><p>Search Indexes can be configured via the <code class="literal">dspace.cfg</code> file. This allows institutions to choose which DSpace metadata fields are indexed by Lucene.</p><p>For example, the following entries appear in a default DSpace installation:</p><pre class="screen">
 search.index.1 = author:dc.contributor.*
 search.index.2 = author:dc.creator.*
 search.index.3 = title:dc.title.*
@@ -295,7 +296,7 @@ search.index.9 = mime:dc.format.mimetype
 search.index.10 = sponsor:dc.description.sponsorship
 search.index.11 = id:dc.identifier.*
        
-</pre><p>The form of each entry is <code class="literal">search.index.&lt;id&gt; = &lt;search &lt;schema&gt;field&gt;:&lt;metadata field&gt;</code> where:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">&lt;id&gt;</code>  is an incremental number to distinguish each search index entry</p></li><li><p><code class="literal">&lt;search field&gt;</code>  is an identifier for the search field this index will correspond to</p></li><li><p><code class="literal">&lt;metadata field&gt;</code>  is the DSpace metadata field to be indexed</p></li></ul></div><p>So in the example above, search.indexes1, 2 and 6 are configured as the <code class="literal">author</code> search field. The <code class="literal">author</code> index is created by Lucene indexing all <code class="literal">contributor</code>, <code class="literal">creator</code> and <code class="literal">description.statementofresponsibility</code> medatata fields.</p><p>After changing the configuration, run <code class="literal">index-all</code> to recreate the indexes.</p><p><span class="bold"><strong>NOTE:</strong></span> While the indexes are created, this only affects the search results and has no effect on the search components of the user interface. To add new search capability (e.g. to add a new search category to the Advanced Search) requires local customisation to the user interface.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N118E4"></a>5.1.3.&nbsp;<a name="docbook-configure.html-general-browse"></a>Browse Configuration</h3></div></div></div><p>The browse indices for DSpace can be extensively configured. This section of the configuration allows you to take control of the indices you wish to browse on, and how you wish to present the results. This configuration is broken down into several parts: defining the indices, defining the fields upon which users can sort results, defining truncation for potentially long fields (e.g. author lists), setting cross-links between different browse contexts (e.g. from an author's name to a complete list of their items), how many recent submissions to display, and configuration for item mapping browse.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N118ED"></a>Defining the Indices</h4></div></div></div><p>The form is:</p><pre class="screen">
+</pre><p>The form of each entry is <code class="literal">search.index.&lt;id&gt; = &lt;search &lt;schema&gt;field&gt;:&lt;metadata field&gt;</code> where:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">&lt;id&gt;</code>  is an incremental number to distinguish each search index entry</p></li><li><p><code class="literal">&lt;search field&gt;</code>  is an identifier for the search field this index will correspond to</p></li><li><p><code class="literal">&lt;metadata field&gt;</code>  is the DSpace metadata field to be indexed</p></li></ul></div><p>So in the example above, search.indexes1, 2 and 6 are configured as the <code class="literal">author</code> search field. The <code class="literal">author</code> index is created by Lucene indexing all <code class="literal">contributor</code>, <code class="literal">creator</code> and <code class="literal">description.statementofresponsibility</code> medatata fields.</p><p>After changing the configuration, run <code class="literal">index-all</code> to recreate the indexes.</p><p><span class="bold"><strong>NOTE:</strong></span> While the indexes are created, this only affects the search results and has no effect on the search components of the user interface. To add new search capability (e.g. to add a new search category to the Advanced Search) requires local customisation to the user interface.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N118F8"></a>5.1.3.&nbsp;<a name="docbook-configure.html-general-browse"></a>Browse Configuration</h3></div></div></div><p>The browse indices for DSpace can be extensively configured. This section of the configuration allows you to take control of the indices you wish to browse on, and how you wish to present the results. This configuration is broken down into several parts: defining the indices, defining the fields upon which users can sort results, defining truncation for potentially long fields (e.g. author lists), setting cross-links between different browse contexts (e.g. from an author's name to a complete list of their items), how many recent submissions to display, and configuration for item mapping browse.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11901"></a>Defining the Indices</h4></div></div></div><p>The form is:</p><pre class="screen">
 webui.browse.index.&lt;n&gt; = &lt;index name&gt; : \
                                &lt;schema
 	prefix&gt;.&lt;element&gt;[.&lt;qualifier&gt;|.*] : \
@@ -310,7 +311,7 @@ webui.browse.index.2 = author:dc.contributor.*:text:single
 webui.browse.index.3 = title:dc.title:title:full
 webui.browse.index.4 = subject:dc.subject.*:text:single
 webui.browse.index.5 = dateaccessioned:dc.date.accessioned:date:full
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1193E"></a>Defining Sort Options</h4></div></div></div><p>Sort options will be available when browsing a list of items (i.e. only in "full" mode, not "single" mode). You can define an arbitrary number of fields to sort on, irrespective of which fields you display using webui.itemlist.columns</p><p>The format is:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11952"></a>Defining Sort Options</h4></div></div></div><p>Sort options will be available when browsing a list of items (i.e. only in "full" mode, not "single" mode). You can define an arbitrary number of fields to sort on, irrespective of which fields you display using webui.itemlist.columns</p><p>The format is:</p><pre class="screen">
 webui.browse.sort-option.&lt;n&gt; = &lt;option name&gt; : \
                                &lt;schema
 	prefix&gt;.&lt;element&gt;[.&lt;qualifier&gt;|.*] : \
@@ -320,28 +321,28 @@ webui.browse.sort-option.&lt;n&gt; = &lt;option name&gt; : \
                            
 webui.browse.sort-option.1 = title:dc.title:text
 webui.browse.sort-option.2 = date:dc.date.issued:date
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11975"></a>Author (Multiple metadata value) Display</h4></div></div></div><p>(Note: this section actually applies to any field with multiple values, but authors are the defined case)</p><p>You can define which field is the author (or editor, or other repeated field) which this configuration will deal with thus:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11989"></a>Author (Multiple metadata value) Display</h4></div></div></div><p>(Note: this section actually applies to any field with multiple values, but authors are the defined case)</p><p>You can define which field is the author (or editor, or other repeated field) which this configuration will deal with thus:</p><pre class="screen">
 webui.browse.author-field = dc.contributor.*
 </pre><p> Replace <code class="literal">dc.contributor.*</code> with another field if appropriate.  The field should be listed in the configuration for <code class="literal">webui.itemlist.columns</code>, otherwise you will not see its effect. It must also be defined in <code class="literal">webui.itemlist.columns</code> as being of data type <code class="literal">text</code>, otherwise the functionality will be overriden by the specific data type features.</p><p>Now that we know which field is our author or other multiple metadata value field we can provide the option to truncate the number of values displayed by default. We replace the remaining list of values with "et al" or the language pack specific alternative. Note that this is just for the default, and users will have the option of changing the number displayed when they browse the results</p><pre class="screen">
 webui.browse.author-limit = &lt;n&gt;
-</pre><p>Where &lt;n&gt; is an integer number of values to be displayed. Use <code class="literal">-1</code> for unlimited (default).</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1199D"></a>Links to other browse contexts</h4></div></div></div><p>We can define which fields link to other browse listings. This is useful, for example, to link an author's name to a list of just that author's items. The effect this has is to create links to browse views for the item clicked on. If it is a "single" type, it will link to a view of all the items which share that metadata element in common (i.e. all the papers by a single author). If it is a "full" type, it will link to a view of the standard full browse page, starting with the value of the link clicked on.</p><p>The form is:</p><pre class="screen">
+</pre><p>Where &lt;n&gt; is an integer number of values to be displayed. Use <code class="literal">-1</code> for unlimited (default).</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N119B1"></a>Links to other browse contexts</h4></div></div></div><p>We can define which fields link to other browse listings. This is useful, for example, to link an author's name to a list of just that author's items. The effect this has is to create links to browse views for the item clicked on. If it is a "single" type, it will link to a view of all the items which share that metadata element in common (i.e. all the papers by a single author). If it is a "full" type, it will link to a view of the standard full browse page, starting with the value of the link clicked on.</p><p>The form is:</p><pre class="screen">
 webui.browse.link.&lt;n&gt; = &lt;index name&gt;:&lt;display column
 	metadata&gt;
 </pre><p>This should associated the name of one of the browse indices (<code class="literal">webui.browse.index.n</code>) with a metadata field listed in <code class="literal">webui.itemlist.columns</code> above. If this condition is not fulfilled, cross-linking will not work. Note also that cross-linking only works for metadata fields not tagged as <code class="literal">title</code> in <code class="literal">webui.itemlist.columns</code>.</p><p>The following example shows the default in <code class="literal">dspace.cfg</code> which links author names to lists of their publications:</p><pre class="screen">
 webui.browse.link.1 = author:dc.contributor.*
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N119C3"></a>Recent Submissions</h4></div></div></div><p>This allows us to define which index to base Recent Submission display on, and how many we should show at any one time. This uses the PluginManager to automatically load the relevant plugin for the Community and Collection home pages. Values given in examples are the defaults supplied in <code class="literal">dspace.cfg</code></p><p>First define the sort name (from <code class="literal">webui.browse.sort-option</code>) to use for # displaying recent submissions. For example:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N119D7"></a>Recent Submissions</h4></div></div></div><p>This allows us to define which index to base Recent Submission display on, and how many we should show at any one time. This uses the PluginManager to automatically load the relevant plugin for the Community and Collection home pages. Values given in examples are the defaults supplied in <code class="literal">dspace.cfg</code></p><p>First define the sort name (from <code class="literal">webui.browse.sort-option</code>) to use for # displaying recent submissions. For example:</p><pre class="screen">
 recent.submissions.sort-option = dateaccessioned
 </pre><p>Define how many recent submissions should be displayed at any one time, for example:</p><pre class="screen">
 recent.submissions.count = 5
-</pre><p>Now we need to set up the processors that the <a class="ulink" href="business.html#plugin" target="_top">PluginManager</a> will load to actually perform the recent submissions query on the relevant pages.</p><p>Tell the community and collection pages that we are using the Recent Submissions code</p><pre class="screen">
+</pre><p>Now we need to set up the processors that the <a class="link" href="ch10.html#docbook-business.html-plugin">PluginManager</a> will load to actually perform the recent submissions query on the relevant pages.</p><p>Tell the community and collection pages that we are using the Recent Submissions code</p><pre class="screen">
 plugin.sequence.org.dspace.plugin.CommunityHomeProcessor = \
         org.dspace.app.webui.components.RecentCommunitySubmissions
 
 plugin.sequence.org.dspace.plugin.CollectionHomeProcessor = \
         org.dspace.app.webui.components.RecentCollectionSubmissions
-</pre><p>This is already configured by default in <code class="literal">dspace.cfg</code> so there should be no need for you to worry about it</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N119EB"></a>Item Mapper</h4></div></div></div><p>Because the item mapper requires a primitive implementation of the browse system to be present, we simply need to tell that system which of our indices defines the author browse (or equivalent) so that the mapper can list authors' items for mapping</p><p>Define the the index name (from <code class="literal">webui.browse.index</code>) to use for displaying items by author</p><pre class="screen">
+</pre><p>This is already configured by default in <code class="literal">dspace.cfg</code> so there should be no need for you to worry about it</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N119FF"></a>Item Mapper</h4></div></div></div><p>Because the item mapper requires a primitive implementation of the browse system to be present, we simply need to tell that system which of our indices defines the author browse (or equivalent) so that the mapper can list authors' items for mapping</p><p>Define the the index name (from <code class="literal">webui.browse.index</code>) to use for displaying items by author</p><pre class="screen">
 itemmap.author.index = author
-</pre><p>So if you change the name of your author browse field, you will also need to update this configuration.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N119FC"></a>5.1.4.&nbsp;<a name="docbook-configure.html-general-mediafilter"></a>Configuring Media Filters</h3></div></div></div><p>Media or Format Filters are classes used to generate derivative or alternative versions of content or bitstreams within DSpace. For example, the PDF Media Filter will extract textual content from PDF bitstreams, the JPEG Media Filter can create thumbnails from image bitstreams.</p><p>Media Filters are configured as <a class="ulink" href="business.html#plugin" target="_top">Named Plugins</a>, with each filter also having a separate configuration setting (in <code class="literal">dspace.cfg</code>) indicating which formats it can process. The default configuration is shown below.</p><pre class="screen">
+</pre><p>So if you change the name of your author browse field, you will also need to update this configuration.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11A10"></a>5.1.4.&nbsp;<a name="docbook-configure.html-general-mediafilter"></a>Configuring Media Filters</h3></div></div></div><p>Media or Format Filters are classes used to generate derivative or alternative versions of content or bitstreams within DSpace. For example, the PDF Media Filter will extract textual content from PDF bitstreams, the JPEG Media Filter can create thumbnails from image bitstreams.</p><p>Media Filters are configured as <a class="link" href="ch10.html#docbook-business.html-plugin">Named Plugins</a>, with each filter also having a separate configuration setting (in <code class="literal">dspace.cfg</code>) indicating which formats it can process. The default configuration is shown below.</p><pre class="screen">
         #### Media Filter / Format Filter plugins (through
 	PluginManager) ####
 
@@ -380,14 +381,14 @@ itemmap.author.index = author
        
 	filter.org.dspace.app.mediafilter.BrandedPreviewJPEGFilter.inputFormat
 s = GIF, JPEG, image/png
-</pre><p>The enabled Media/Format Filters are named in the <code class="literal">filter.plugins</code> field above.</p><p>Names are assigned to each filter using the <code class="literal">plugin.named.org.dspace.app.mediafilter.FormatFilter</code> field (e.g. by default the <code class="literal">PDFFilter</code> is named "PDF Text Extractor").</p><p>Finally the appropriate <code class="literal">filter.&lt;class path&gt;.inputFormats</code> defines the vaild input formats which each filter can be applied to. These format names <span class="bold"><strong>must match</strong></span> the <code class="literal">short description</code> field of the <a class="ulink" href="appendix.html#bitstreamformatregistry" target="_top">Bitstream Format Registry</a>.</p><p>You can also implement more dynamic or configurable Media/Format Filters which extend <a class="ulink" href="business.html#selfnamedplugin" target="_top">
+</pre><p>The enabled Media/Format Filters are named in the <code class="literal">filter.plugins</code> field above.</p><p>Names are assigned to each filter using the <code class="literal">plugin.named.org.dspace.app.mediafilter.FormatFilter</code> field (e.g. by default the <code class="literal">PDFFilter</code> is named "PDF Text Extractor").</p><p>Finally the appropriate <code class="literal">filter.&lt;class path&gt;.inputFormats</code> defines the vaild input formats which each filter can be applied to. These format names <span class="bold"><strong>must match</strong></span> the <code class="literal">short description</code> field of the <a class="link" href="ch15.html#docbook-appendix.html-bitstreamformatregistry">Bitstream Format Registry</a>.</p><p>You can also implement more dynamic or configurable Media/Format Filters which extend <a class="ulink" href="business.html#selfnamedplugin" target="_top">
             <code class="literal">SelfNamedPlugin</code>
           </a>
-. More information is provide below in <a name="docbook-configure.html--newfilter"></a>Creating a new Media/Format Filter</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11A42"></a>5.1.5.&nbsp;<a name="docbook-configure.html-general-email"></a>Wording of E-mail Messages</h3></div></div></div><p>Sometimes DSpace automatically sends e-mail messages to users, for example to inform them of a new workflow task, or as a subscription e-mail alert. The wording of emails can be changed by editing the relevant file in <code class="literal">[dspace]/config/emails</code>. Each file is commented. Be careful to keep the right number 'placeholders' (e.g.<code class="literal">{2}</code>).</p><p><span class="bold"><strong>Note:</strong></span> You should replace the contact-information "<code class="literal">dspace-help@myu.edu or call us at xxx-555-xxxx</code>" with your own contact details in:</p><div class="itemizedlist"><ul type="disc"><li><p>
+. More information is provide below in <a name="docbook-configure.html--newfilter"></a>Creating a new Media/Format Filter</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11A56"></a>5.1.5.&nbsp;<a name="docbook-configure.html-general-email"></a>Wording of E-mail Messages</h3></div></div></div><p>Sometimes DSpace automatically sends e-mail messages to users, for example to inform them of a new workflow task, or as a subscription e-mail alert. The wording of emails can be changed by editing the relevant file in <code class="literal">[dspace]/config/emails</code>. Each file is commented. Be careful to keep the right number 'placeholders' (e.g.<code class="literal">{2}</code>).</p><p><span class="bold"><strong>Note:</strong></span> You should replace the contact-information "<code class="literal">dspace-help@myu.edu or call us at xxx-555-xxxx</code>" with your own contact details in:</p><div class="itemizedlist"><ul type="disc"><li><p>
               <code class="literal">config/emails/change_password</code>
             </p></li><li><p>
               <code class="literal">config/emails/register</code>
-            </p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11A6B"></a>5.2.&nbsp;<a name="docbook-configure.html-general-registries"></a>The Metadata and Bitstream Format Registries</h2></div></div></div><p>The <code class="literal">[dspace]/config/registries</code> directory contains three XML files. These are used to load the <span class="emphasis"><em>initial</em></span> contents of the Metadata Schema Registry, <a class="ulink" href="appendix.html#dublincoreregistry" target="_top">Dublin Core Metadata registry</a> and <a class="ulink" href="appendix.html#bitstreamformatregistry" target="_top">Bitstream Format registry</a>. After the initial loading (performed by <code class="literal">ant fresh_install</code> above), the registries reside in the database; the XML files are not updated.</p><p>In order to change the registries, you may adjust the XML files before the first installation of DSpace. On an allready running instance it is recommended to change bitstream registries via DSpace admin UI, but the metadata registries can be loaded again at any time from the XML files without difficult. The changes made via admin UI are not reflected in the XML files.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11A89"></a>5.2.1.&nbsp;Metadata Schema Registry</h3></div></div></div><p>The default metadata schema in DSpace is Dublin Core, so it is distributed with a single entry in the source XML file for that namespace. If you wish to add more schemas you can do this in one of two ways. Via the DSpace admin UI you may define new Metadata Schemas, edit existing schemas and move elements between schemas. But you may also modify the XML file (or provide an additional one), and re-import the data as follows:</p><pre class="screen">
+            </p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11A7F"></a>5.2.&nbsp;<a name="docbook-configure.html-general-registries"></a>The Metadata and Bitstream Format Registries</h2></div></div></div><p>The <code class="literal">[dspace]/config/registries</code> directory contains three XML files. These are used to load the <span class="emphasis"><em>initial</em></span> contents of the Metadata Schema Registry, <a class="link" href="ch15.html#docbook-appendix.html-dublincoreregistry">Dublin Core Metadata registry</a> and <a class="link" href="ch15.html#docbook-appendix.html-bitstreamformatregistry">Bitstream Format registry</a>. After the initial loading (performed by <code class="literal">ant fresh_install</code> above), the registries reside in the database; the XML files are not updated.</p><p>In order to change the registries, you may adjust the XML files before the first installation of DSpace. On an allready running instance it is recommended to change bitstream registries via DSpace admin UI, but the metadata registries can be loaded again at any time from the XML files without difficult. The changes made via admin UI are not reflected in the XML files.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11A9D"></a>5.2.1.&nbsp;Metadata Schema Registry</h3></div></div></div><p>The default metadata schema in DSpace is Dublin Core, so it is distributed with a single entry in the source XML file for that namespace. If you wish to add more schemas you can do this in one of two ways. Via the DSpace admin UI you may define new Metadata Schemas, edit existing schemas and move elements between schemas. But you may also modify the XML file (or provide an additional one), and re-import the data as follows:</p><pre class="screen">
   [dspace]/bin/dsrun org.dspace.adminster.SchemaImporter -f [xml
 	file]
  
@@ -400,7 +401,7 @@ s = GIF, JPEG, image/png
                 &lt;/schema&gt;
         &lt;/metadata-schemas&gt;
  
-</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11A97"></a>5.2.2.&nbsp;Metadata Format Registries</h3></div></div></div><p>The default metadata schema is Dublin Core, so DSpace is distributed with a default Dublin Core Metadata Registry. Currently, the system requires that every item have a Dublin Core record.</p><p>There is a set of Dublin Core Elements, which is used by the system and should not be removed or moved to another schema, see <a class="ulink" href="appendix.html#dublincoreregistry" target="_top">Appendix: Default Dublin Core Metadata registry</a>.</p><p><span class="bold"><strong>Note</strong></span>: altering a Metadata Registry has no effect on corresponding parts, e.g. item submission interface, item display, item import and vice versa. Every metadata element used in submission interface or item import must be registered before using it.</p><p><span class="bold"><strong>Note</strong></span> also that deleting a metadata element will delete all its corresponding values.</p><p>If you wish to add more metadata elements, you can do this in one of two ways. Via the DSpace admin UI you may define new metadata elements in the different available schemas. But you may also modify the XML file (or provide an additional one), and re-import the data as follows:</p><pre class="screen">
+</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11AAB"></a>5.2.2.&nbsp;Metadata Format Registries</h3></div></div></div><p>The default metadata schema is Dublin Core, so DSpace is distributed with a default Dublin Core Metadata Registry. Currently, the system requires that every item have a Dublin Core record.</p><p>There is a set of Dublin Core Elements, which is used by the system and should not be removed or moved to another schema, see <a class="link" href="ch15.html#docbook-appendix.html-dublincoreregistry">Appendix: Default Dublin Core Metadata registry</a>.</p><p><span class="bold"><strong>Note</strong></span>: altering a Metadata Registry has no effect on corresponding parts, e.g. item submission interface, item display, item import and vice versa. Every metadata element used in submission interface or item import must be registered before using it.</p><p><span class="bold"><strong>Note</strong></span> also that deleting a metadata element will delete all its corresponding values.</p><p>If you wish to add more metadata elements, you can do this in one of two ways. Via the DSpace admin UI you may define new metadata elements in the different available schemas. But you may also modify the XML file (or provide an additional one), and re-import the data as follows:</p><pre class="screen">
   [dspace]/bin/dsrun org.dspace.adminster.MetadataImporter -f [xml
 	file]
  
@@ -415,17 +416,17 @@ s = GIF, JPEG, image/png
                 &lt;/dc-type&gt;
         &lt;/dspace-dc-types&gt;
        
-</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11AB7"></a>5.2.3.&nbsp;Bitstream Format Registry</h3></div></div></div><p>The bitstream formats recognized by the system and levels of support are similarly stored in the bitstream format registry. This can also be edited at install-time via <code class="literal">[dspace]/config/registries/bitstream-formats.xml</code> or by the administation Web UI. The contents of the bitstream format registry are entirely up to you, though the system requires that the following two formats are present:</p><div class="itemizedlist"><ul type="disc"><li><p>
+</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11ACB"></a>5.2.3.&nbsp;Bitstream Format Registry</h3></div></div></div><p>The bitstream formats recognized by the system and levels of support are similarly stored in the bitstream format registry. This can also be edited at install-time via <code class="literal">[dspace]/config/registries/bitstream-formats.xml</code> or by the administation Web UI. The contents of the bitstream format registry are entirely up to you, though the system requires that the following two formats are present:</p><div class="itemizedlist"><ul type="disc"><li><p>
               <code class="literal">Unknown</code>
             </p></li><li><p>
               <code class="literal">License</code>
-            </p></li></ul></div><p> Deleting a format will cause any existing bitstreams of this format to be reverted to the unknown bitstream format. </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11AD2"></a>5.3.&nbsp;<a name="docbook-configure.html-general-license"></a>The Default Submission License</h2></div></div></div><p>For each submitted item, a license must be granted. The license will be stored along with the item in the bundle LICENSE in order to keep the information under which terms an items has been published.</p><p>You may define a license for each collection seperately, when creating/editing a collection. If no collection specific license is defined, the default license is used.</p><p>The default license can be found in <code class="literal">[dspace]/config/default.license</code> and can be edited via the dspace-admin interface.</p><p>DSpace comes with a demo license, which you must adopt to your institutional needs and the legal regulations of your country.</p><p>If in doubt, contact the law department of your institution.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11AE7"></a>5.3.1.&nbsp;Possible Points in a License</h3></div></div></div><p>
+            </p></li></ul></div><p> Deleting a format will cause any existing bitstreams of this format to be reverted to the unknown bitstream format. </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11AE6"></a>5.3.&nbsp;<a name="docbook-configure.html-general-license"></a>The Default Submission License</h2></div></div></div><p>For each submitted item, a license must be granted. The license will be stored along with the item in the bundle LICENSE in order to keep the information under which terms an items has been published.</p><p>You may define a license for each collection seperately, when creating/editing a collection. If no collection specific license is defined, the default license is used.</p><p>The default license can be found in <code class="literal">[dspace]/config/default.license</code> and can be edited via the dspace-admin interface.</p><p>DSpace comes with a demo license, which you must adopt to your institutional needs and the legal regulations of your country.</p><p>If in doubt, contact the law department of your institution.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11AFB"></a>5.3.1.&nbsp;Possible Points in a License</h3></div></div></div><p>
           <span class="emphasis"><em>Note, that this is no legal advice, just some starting thoughts for creating you own license.</em></span>
         </p><div class="itemizedlist"><ul type="disc"><li><p> Non-exclusive or exclusive right to</p></li><li><p>
               <div class="itemizedlist"><ul type="circle"><li><p> capture and store</p></li><li><p> distribute</p></li><li><p>
                     <div class="itemizedlist"><ul type="square"><li><p> worldwide</p></li><li><p> restricted (e.g. institutional wide</p></li></ul></div>
                   </p></li><li><p> translate</p></li><li><p> transform to other formats or mediums</p></li><li><p> without changing the content</p></li></ul></div>
-            </p></li><li><p> Make sure no rights (copyright or any other) are violated by this publication</p></li><li><p> In case the type of submission (e.g. thesis) needs approval, make sure it is the final and approved version.</p></li><li><p> Distinguish between the document itself and the metadata</p></li><li><p> Point out that the license granted and the information who granted it will be stored.</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11B1F"></a>5.4.&nbsp;<a name="docbook-configure.html-general-submission"></a>Submission Configuration</h2></div></div></div><p>Instructions for customizing and configuring the Item Submission user interface for either the JSP-UI or XML-UI are contained in the separate <a class="ulink" href="submission.html" target="_top">Customizing and Configuring Submission User Interface</a> page.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11B2C"></a>5.5.&nbsp;<a name="docbook-configure.html-xmlui"></a>XMLUI Interface Customizations (Manakin)</h2></div></div></div><p>The DSpace digital repository supports two user interfaces one based upon JSP technologies and the other based upon the Apache Cocoon framework. This section describes those parameters which are specific to the XMLUI interface based upon the Cocoon framework.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11B35"></a>5.5.1.&nbsp;<a name="docbook-configure.html-xmlui-dspacecfg"></a>XMLUI Configuration Properties</h3></div></div></div><p>There are several options effecting how the XMLUI user interface for DSpace operates. Listed below are the major elements and their description, refere to the <code class="literal">dspace.cfg</code> file itself for the exhaustive list of configuration parameters.</p><div class="informaltable"><table border="0"><colgroup><col><col><col></colgroup><tbody><tr><td>
+            </p></li><li><p> Make sure no rights (copyright or any other) are violated by this publication</p></li><li><p> In case the type of submission (e.g. thesis) needs approval, make sure it is the final and approved version.</p></li><li><p> Distinguish between the document itself and the metadata</p></li><li><p> Point out that the license granted and the information who granted it will be stored.</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11B33"></a>5.4.&nbsp;<a name="docbook-configure.html-general-submission"></a>Submission Configuration</h2></div></div></div><p>Instructions for customizing and configuring the Item Submission user interface for either the JSP-UI or XML-UI are contained in the separate <a class="link" href="ch11.html#docbook-submission.html">Customizing and Configuring Submission User Interface</a> page.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11B40"></a>5.5.&nbsp;<a name="docbook-configure.html-xmlui"></a>XMLUI Interface Customizations (Manakin)</h2></div></div></div><p>The DSpace digital repository supports two user interfaces one based upon JSP technologies and the other based upon the Apache Cocoon framework. This section describes those parameters which are specific to the XMLUI interface based upon the Cocoon framework.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11B49"></a>5.5.1.&nbsp;<a name="docbook-configure.html-xmlui-dspacecfg"></a>XMLUI Configuration Properties</h3></div></div></div><p>There are several options effecting how the XMLUI user interface for DSpace operates. Listed below are the major elements and their description, refere to the <code class="literal">dspace.cfg</code> file itself for the exhaustive list of configuration parameters.</p><div class="informaltable"><table border="0"><colgroup><col><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>Property</strong></span>
                   </p>
@@ -577,7 +578,7 @@ s = GIF, JPEG, image/png
                   </p>
                 </td><td>
                   <p>Optionally you may configure Manakin to take advantage of metadata stored as a bitstream. The METS metadata file must be inside the "METADATA" bundle and named either METS.xml. If this option is set to <code class="literal">true</code> and the bitstream is present then the stored METS file is merged with the METS file generated by Manakin for each item. Thus if the bitstream contains a <code class="literal">dmdSec</code> then there will be two <code class="literal">dmdSec</code> one from the bitstream and another generated from the Dublin Core stored inside the database.</p>
-                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11CD8"></a>5.5.2.&nbsp;<a name="docbook-configure.html-xmlui-configure"></a>Configuring Themes and Aspects</h3></div></div></div><p>The Manakin user interface is composed of two distinct components: <span class="emphasis"><em>aspects</em></span> and <span class="emphasis"><em>themes</em></span>. Manakin aspects are like extensions or plugins for Manakin; they are interactive components that modify existing features or provide new features for the digital repository. Manakin themes stylize the look-and-feel of the repository, community, or collection.</p><p>The repository administrator is able to define which aspects and themes are installed for the particular repository by editing the <code class="literal">[dspace]/config/xmlui.xconf</code> configuration file. The <code class="literal">xmlui.xconf</code> file consists of two major sections: Aspects and Themes.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11CF1"></a>Aspects</h4></div></div></div><p>The <code class="literal">&lt;aspects&gt;</code> section defines the "Aspect Chain", or the linear set of aspects that are installed in the repository. For each aspect that is installed in the repository, the aspect makes available new features to the interface. For example, if the "submission" aspect were to be commented out or removed from the <code class="literal">xmlui.xconf</code>, then users would not be able to submit new items into the repository (even the links and language prompting users to submit items are removed). Each <code class="literal">&lt;aspect&gt;</code> element has two attributes, <span class="emphasis"><em>name</em></span> &amp; <span class="emphasis"><em>path</em></span>. The name is used to identify the Aspect, while the path determines the directory where the aspect's code is located. Here is the default aspect configuration:</p><pre class="screen">
+                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11CEC"></a>5.5.2.&nbsp;<a name="docbook-configure.html-xmlui-configure"></a>Configuring Themes and Aspects</h3></div></div></div><p>The Manakin user interface is composed of two distinct components: <span class="emphasis"><em>aspects</em></span> and <span class="emphasis"><em>themes</em></span>. Manakin aspects are like extensions or plugins for Manakin; they are interactive components that modify existing features or provide new features for the digital repository. Manakin themes stylize the look-and-feel of the repository, community, or collection.</p><p>The repository administrator is able to define which aspects and themes are installed for the particular repository by editing the <code class="literal">[dspace]/config/xmlui.xconf</code> configuration file. The <code class="literal">xmlui.xconf</code> file consists of two major sections: Aspects and Themes.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11D05"></a>Aspects</h4></div></div></div><p>The <code class="literal">&lt;aspects&gt;</code> section defines the "Aspect Chain", or the linear set of aspects that are installed in the repository. For each aspect that is installed in the repository, the aspect makes available new features to the interface. For example, if the "submission" aspect were to be commented out or removed from the <code class="literal">xmlui.xconf</code>, then users would not be able to submit new items into the repository (even the links and language prompting users to submit items are removed). Each <code class="literal">&lt;aspect&gt;</code> element has two attributes, <span class="emphasis"><em>name</em></span> &amp; <span class="emphasis"><em>path</em></span>. The name is used to identify the Aspect, while the path determines the directory where the aspect's code is located. Here is the default aspect configuration:</p><pre class="screen">
    &lt;aspects&gt;
      &lt;aspect name="Artifact Browser"
 	path="resource://aspects/ArtifactBrowser/" /&gt;
@@ -597,7 +598,7 @@ s = GIF, JPEG, image/png
                 </p><p>  The Submission Aspect is responsible for submitting new items to DSpace, determining the workflow process and ingesting the new items into the DSpace repository.</p></li><li><p>
                   <span class="bold"><strong>Administrative</strong></span>
                 </p><p>  The Administrative Aspect is responsible for administrating DSpace, such as creating, modifying and removing all communities, collections, e-persons, groups, registries and authorizations.</p></li></ul></div>
-</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11D34"></a>Themes</h4></div></div></div><p>The <code class="literal">&lt;themes&gt;</code> section defines a set of "rules" that determine where themes are installed in the repository. Each rule is processed in the order that it appears, and the first rule that matches determines the theme that is applied (so order is important). Each rule consists of a <code class="literal">&lt;theme&gt;</code> element with several possible attributes:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>name</strong></span>  (<span class="emphasis"><em>always required</em></span>)</p><p> The name attribute is used to document the theme's name.</p></li><li><p><span class="bold"><strong>path</strong></span>  (<span class="emphasis"><em>always required</em></span>)</p><p> The path attribute determines where the theme is located relative to the <code class="literal">themes/</code> directory and must either contain a trailing slash or point directly to the theme's <code class="literal">sitemap.xmap</code> file.</p></li><li><p><span class="bold"><strong>regex</strong></span>  (<span class="emphasis"><em>either regex and/or handle is required</em></span>)</p><p> The regex attribute determines which URLs the theme should apply to.</p></li><li><p><span class="bold"><strong>handle</strong></span>  (<span class="emphasis"><em>either regex and/or handle is required</em></span>)</p><p> The handle attribute determines which community, collection, or item the theme should apply to.</p></li></ul></div><p>If you use the "handle" attribute, the effect is cascading, meaning if a rule is established for a community then all collections and items within that community will also have this theme apply to them as well. Here is an example configuration:</p><pre class="screen">
+</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11D48"></a>Themes</h4></div></div></div><p>The <code class="literal">&lt;themes&gt;</code> section defines a set of "rules" that determine where themes are installed in the repository. Each rule is processed in the order that it appears, and the first rule that matches determines the theme that is applied (so order is important). Each rule consists of a <code class="literal">&lt;theme&gt;</code> element with several possible attributes:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>name</strong></span>  (<span class="emphasis"><em>always required</em></span>)</p><p> The name attribute is used to document the theme's name.</p></li><li><p><span class="bold"><strong>path</strong></span>  (<span class="emphasis"><em>always required</em></span>)</p><p> The path attribute determines where the theme is located relative to the <code class="literal">themes/</code> directory and must either contain a trailing slash or point directly to the theme's <code class="literal">sitemap.xmap</code> file.</p></li><li><p><span class="bold"><strong>regex</strong></span>  (<span class="emphasis"><em>either regex and/or handle is required</em></span>)</p><p> The regex attribute determines which URLs the theme should apply to.</p></li><li><p><span class="bold"><strong>handle</strong></span>  (<span class="emphasis"><em>either regex and/or handle is required</em></span>)</p><p> The handle attribute determines which community, collection, or item the theme should apply to.</p></li></ul></div><p>If you use the "handle" attribute, the effect is cascading, meaning if a rule is established for a community then all collections and items within that community will also have this theme apply to them as well. Here is an example configuration:</p><pre class="screen">
   &lt;themes&gt;
     &lt;theme name="Theme 1" handle="123456789/23"
 	path="theme1/"/&gt;
@@ -606,7 +607,7 @@ s = GIF, JPEG, image/png
     &lt;theme name="Reference Theme" regex=".*"
 	path="Reference/"/&gt;
   &lt;/themes&gt;
-</pre><p>In the example above three themes are configured: "Theme 1", "Theme 2", and the "Reference Theme". The first rule specifies that "Theme 1" will apply to all communities, collections, or items that are contained under the parent community "123456789/23". The next rule specifies any URL containing the string "community-list" will get "Theme 2". The final rule, using the regular expression ".*", will match <span class="bold"><strong>anything</strong></span>, so all pages which have not matched one of the preceding rules will be matched to the Reference Theme.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11D82"></a>5.5.3.&nbsp;<a name="docbook-configure.html-xmlui-multilingual"></a>Multilingual Support</h3></div></div></div><p>The XMLUI user interface supports multiple languages through the use of internationalization catalogues as defined by the <a class="ulink" href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html" target="_top">Cocoon Internationalization Transformer</a>. Each catalogue contains the translation of all user-displayed strings into a particular language or variant. Each catalogue is a single xml file whose name is based upon the language it is designated for, thus:</p><p> messages_<span class="emphasis"><em>language</em></span>_<span class="emphasis"><em>country</em></span>_<span class="emphasis"><em>variant</em></span>.xml</p><p> messages_<span class="emphasis"><em>language</em></span>_<span class="emphasis"><em>country</em></span>.xml</p><p> messages_<span class="emphasis"><em>language</em></span>.xml</p><p> messages.xml</p><p> The interface will automatically determine which file to select based upon the user's browser and system configuration. For example, if the user's browser is set to Australian English then first the system will check if <code class="literal">messages_en_au.xml</code> is available. If this translation is not available it will fall back to <code class="literal">messages_en.xml</code>, and finally if that is not available, <code class="literal">messages.xml</code>.</p><p>Manakin supplies an English only translation of the interface. In order to add other translations to the system, locate the <code class="literal">[dspace-source]/dspace/modules/xmlui/src/main/webapp/i18n/</code> directory. By default this directory will be empty; to add additional translations add alternative versions of the <code class="literal">messages.xml</code> file in specific language and country variants as needed for your installation.</p><p> To set a language other than English as the default language for the repository's interface, simply name the translation catalogue for the new default language "<code class="literal">messages.xml</code>"</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11DC7"></a>5.5.4.&nbsp;<a name="docbook-configure.html-xmlui-newtheme"></a>Creating a New Theme</h3></div></div></div><p>Manakin themes stylize the look-and-feel of the repository, community, or collection and are distributed as self-contained packages. A Manakin/DSpace installation may have multiple themes installed and available to be used in different parts of the repository. The central component of a theme is the sitemap.xmap, which defines what resources are available to the theme such as XSL stylesheets, CSS stylesheets, images, or multimedia files.</p><p>
+</pre><p>In the example above three themes are configured: "Theme 1", "Theme 2", and the "Reference Theme". The first rule specifies that "Theme 1" will apply to all communities, collections, or items that are contained under the parent community "123456789/23". The next rule specifies any URL containing the string "community-list" will get "Theme 2". The final rule, using the regular expression ".*", will match <span class="bold"><strong>anything</strong></span>, so all pages which have not matched one of the preceding rules will be matched to the Reference Theme.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11D96"></a>5.5.3.&nbsp;<a name="docbook-configure.html-xmlui-multilingual"></a>Multilingual Support</h3></div></div></div><p>The XMLUI user interface supports multiple languages through the use of internationalization catalogues as defined by the <a class="ulink" href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html" target="_top">Cocoon Internationalization Transformer</a>. Each catalogue contains the translation of all user-displayed strings into a particular language or variant. Each catalogue is a single xml file whose name is based upon the language it is designated for, thus:</p><p> messages_<span class="emphasis"><em>language</em></span>_<span class="emphasis"><em>country</em></span>_<span class="emphasis"><em>variant</em></span>.xml</p><p> messages_<span class="emphasis"><em>language</em></span>_<span class="emphasis"><em>country</em></span>.xml</p><p> messages_<span class="emphasis"><em>language</em></span>.xml</p><p> messages.xml</p><p> The interface will automatically determine which file to select based upon the user's browser and system configuration. For example, if the user's browser is set to Australian English then first the system will check if <code class="literal">messages_en_au.xml</code> is available. If this translation is not available it will fall back to <code class="literal">messages_en.xml</code>, and finally if that is not available, <code class="literal">messages.xml</code>.</p><p>Manakin supplies an English only translation of the interface. In order to add other translations to the system, locate the <code class="literal">[dspace-source]/dspace/modules/xmlui/src/main/webapp/i18n/</code> directory. By default this directory will be empty; to add additional translations add alternative versions of the <code class="literal">messages.xml</code> file in specific language and country variants as needed for your installation.</p><p> To set a language other than English as the default language for the repository's interface, simply name the translation catalogue for the new default language "<code class="literal">messages.xml</code>"</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11DDB"></a>5.5.4.&nbsp;<a name="docbook-configure.html-xmlui-newtheme"></a>Creating a New Theme</h3></div></div></div><p>Manakin themes stylize the look-and-feel of the repository, community, or collection and are distributed as self-contained packages. A Manakin/DSpace installation may have multiple themes installed and available to be used in different parts of the repository. The central component of a theme is the sitemap.xmap, which defines what resources are available to the theme such as XSL stylesheets, CSS stylesheets, images, or multimedia files.</p><p>
           <span class="bold"><strong>1) Create theme skeleton</strong></span>
         </p><p>Most theme developers do not create a new theme from scratch; instead they start from the standard theme template, which defines a skeleton structure for a theme. The template is located at: <code class="literal">[dspace-source]/dspace-xmlui/dspace-xmlui-webbapp/src/main/webbapp/themes/template</code>. To start your new theme simply copy the theme template into your locally defined modules directory, <code class="literal">[dspace-source]/dspace/modules/xmlui/src/main/webbapp/themes/[your theme's directory]/</code>.</p><p>
           <span class="bold"><strong>2) Modify theme variables</strong></span>
@@ -620,7 +621,14 @@ s = GIF, JPEG, image/png
           <span class="bold"><strong>3) Add your CSS stylesheets</strong></span>
         </p><p>The base theme template will produce a repository interface without any style - just plain XHTML with no color or formatting. To make your theme useful you will need to supply a CSS Stylesheet that creates your desired look-and-feel. Add your new CSS stylesheets:</p><p><code class="literal">[your theme's directory]/lib/style.css</code> (The base style sheet used for all browsers)</p><p><code class="literal">[your theme's directory]/lib/style-ie.css</code> (Specific stylesheet used for internet explorer)</p><p>
           <span class="bold"><strong>4) Install theme and rebuild DSpace</strong></span>
-        </p><p>Next rebuild &amp; deploy DSpace as described in the <a class="ulink" href="install.html" target="_top">installation portion of the manual</a>, and ensure the theme has been installed as described in the previous section "<a class="ulink" href="configure.html#xmlui-configure" target="_top">Configuring Themes and Aspects</a>".</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11E16"></a>5.6.&nbsp;<a name="docbook-configure.html-jspui"></a>JSPUI Interface Customizations</h2></div></div></div><p>DSpace digital repository supports two user interfaces one based upon JSP technologies and the other based upon the Apache Cocoon framework. This section describes those parameters which are specific to the JSPUI interface.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11E1F"></a>5.6.1.&nbsp;<a name="docbook-configure.html-jspui-dspacecfg"></a>JSPUI Configuration Properties</h3></div></div></div><p>There are many options effecting how the JSP-based user interface for DSpace operates. Listed below are the major elements and their description, refer to the <code class="literal">dspace.cfg</code> file itself for the exhaustive list of configuration parameters.</p><div class="informaltable"><table border="0"><colgroup><col><col><col></colgroup><tbody><tr><td>
+        </p><p>Next rebuild &amp; deploy DSpace as described in the <a class="link" href="ch03.html#docbook-install.html">installation portion of the manual</a>, and ensure the theme has been installed as described in the previous section "<a class="link" href="ch05.html#docbook-configure.html-xmlui-configure">Configuring Themes and Aspects</a>".</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11E2A"></a>5.5.5.&nbsp;<a name="docbook-configure.html-xmlui-staticcontent"></a>Adding Static Content</h3></div></div></div><p>The XMLUI user interface supports the addition of globally static content (as well as static content within individual themes).</p><p>Globally static content can be placed in the <code class="literal">[dspace-source]/dspace/modules/xmlui/src/main/webapp/static/</code> directory. By default this directory only contains the default <code class="literal">robots.txt</code> file, which provides helpful site information to web spiders/crawlers. However, you may also add static HTML (<code class="literal">*.html</code>) content to this directory, as needed for your installation.</p><p>Any static HTML content you add to this directory may also reference static content (e.g. CSS, Javascript, Images, etc.) from the same <code class="literal">[dspace-source]/dspace/modules/xmlui/src/main/webapp/static/</code> directory.  You may reference other static content from your static HTML files similar to the following:</p><pre class="screen">
+  &lt;link href="./static/mystyle.css"
+  rel="stylesheet" type="text/css"/&gt;
+  &lt;img src="./static/images/static-image.gif"
+  alt="Static image in /static/images/ directory"/&gt;
+  &lt;img src="./static/static-image.jpg"
+  alt="Static image in /static/ directory"/&gt;
+ </pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N11E4A"></a>5.6.&nbsp;<a name="docbook-configure.html-jspui"></a>JSPUI Interface Customizations</h2></div></div></div><p>DSpace digital repository supports two user interfaces one based upon JSP technologies and the other based upon the Apache Cocoon framework. This section describes those parameters which are specific to the JSPUI interface.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11E53"></a>5.6.1.&nbsp;<a name="docbook-configure.html-jspui-dspacecfg"></a>JSPUI Configuration Properties</h3></div></div></div><p>There are many options effecting how the JSP-based user interface for DSpace operates. Listed below are the major elements and their description, refer to the <code class="literal">dspace.cfg</code> file itself for the exhaustive list of configuration parameters.</p><div class="informaltable"><table border="0"><colgroup><col><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>Property</strong></span>
                   </p>
@@ -702,14 +710,14 @@ s = GIF, JPEG, image/png
                   </p>
                 </td><td>
                   <p>Enables only logged in users to suggest an item. The default value is false.</p>
-                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11F12"></a>5.6.2.&nbsp;<a name="docbook-configure.html-jspui-controlledvocabulary"></a>Configuring Controlled Vocabularies</h3></div></div></div><p>DSpace now supports controlled vocabularies to confine the set of keywords that users can use while describing items.</p><p>The need for a limited set of keywords is important since it eliminates the ambiguity of a free description system, consequently simplifying the task of finding specific items of information.</p><p>The controlled vocabulary add-on allows the user to choose from a defined set of keywords organised in an tree (taxonomy) and then use these keywords to describe items while they are being submitted.</p><p>We have also developed a small search engine that displays the classification tree (or taxonomy) allowing the user to select the branches that best describe the information that he/she seeks.</p><p>The taxonomies are described in XML following this (very simple) structure:</p><p>
+                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11F46"></a>5.6.2.&nbsp;<a name="docbook-configure.html-jspui-controlledvocabulary"></a>Configuring Controlled Vocabularies</h3></div></div></div><p>DSpace now supports controlled vocabularies to confine the set of keywords that users can use while describing items.</p><p>The need for a limited set of keywords is important since it eliminates the ambiguity of a free description system, consequently simplifying the task of finding specific items of information.</p><p>The controlled vocabulary add-on allows the user to choose from a defined set of keywords organised in an tree (taxonomy) and then use these keywords to describe items while they are being submitted.</p><p>We have also developed a small search engine that displays the classification tree (or taxonomy) allowing the user to select the branches that best describe the information that he/she seeks.</p><p>The taxonomies are described in XML following this (very simple) structure:</p><p>
           <code class="literal">&lt;node id="acmccs98" label="ACMCCS98"&gt; &lt;isComposedBy&gt; &lt;node id="A." label="General Literature"&gt; &lt;isComposedBy&gt; &lt;node id="A.0" label="GENERAL"/&gt; &lt;node id="A.1" label="INTRODUCTORY AND SURVEY"/&gt; ... &lt;/isComposedBy&gt; &lt;/node&gt; ... &lt;/isComposedBy&gt; &lt;/node&gt;</code>
         </p><p>Your are free to use any application you want to create your controlled vocabularies. A simple text editor should be enough for small projects. Bigger projects will require more complex tools. You may use Proteg&eacute; to create your taxonomies, save them as OWL and then use a XML Stylesheet (XSLT) to transform your documents to the appropriate format. Future enhancements to this add-on should make it compatible with standard schemas such as OWL or RDF.</p><p>In order to make DSpace compatible with WAI 2.0, the add-on is <span class="bold"><strong>turned off</strong></span> by default (the add-on relies strongly on Javascript to function). It can be activated by setting the following property in <code class="literal">dspace.cfg</code>:</p><p>
           <code class="literal">webui.controlledvocabulary.enable = true</code>
         </p><p>New vocabularies should be placed in <code class="literal">[dspace]/config/controlled-vocabularies/</code> and must be according to the structure described. A validation XML Schema can be downloaded <a class="ulink" href="controlledvocabulary.xsd" target="_top">here</a>.</p><p>Vocabularies need to be associated with the correspondant DC metadata fields. Edit the file <code class="literal">[dspace]/config/input-forms.xml</code> and place a <code class="literal">"vocabulary"</code> tag under the <code class="literal">"field"</code> element that you want to control. Set value of the <code class="literal">"vocabulary"</code> element to the name of the file that contains the vocabulary, leaving out the extension (the add-on will only load files with extension "*.xml"). For example:</p><p>
           <code class="literal">&lt;field&gt; &lt;dc-schema&gt;dc&lt;/dc-schema&gt; &lt;dc-element&gt;subject&lt;/dc-element&gt; &lt;dc-qualifier&gt;&lt;/dc-qualifier&gt; &lt;!-- An input-type of twobox MUST be marked as repeatable --&gt; &lt;repeatable&gt;true&lt;/repeatable&gt; &lt;label&gt;Subject Keywords&lt;/label&gt; &lt;input-type&gt;twobox&lt;/input-type&gt; &lt;hint&gt; Enter appropriate subject keywords or phrases below. &lt;/hint&gt; &lt;required&gt;&lt;/required&gt;&lt;vocabulary [closed="false"]&gt;nsi&lt;/vocabulary&gt; &lt;/field&gt;</code>
-        </p><p>The vocabulary element has an optional boolean attribute <span class="bold"><strong>closed</strong></span> that can be used to force input only with the javascript of controlled-vocabulary add-on. The default behaviour (i.e. without this attribute) is as set <span class="bold"><strong>closed="false"</strong></span>. This allow the user also to enter the value in free way.</p><p>The following vocabularies are currently available by default:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>nsi</strong></span>  - <span class="emphasis"><em>nsi.xml</em></span> - The Norwegian Science Index</p></li><li><p><span class="bold"><strong>srsc</strong></span>  - <span class="emphasis"><em>srsc.xml</em></span> - Swedish Research Subject Categories</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11F7D"></a>5.6.3.&nbsp;<a name="docbook-configure.html-jspui-multilingual"></a>Configuring Multilingual Support</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11F84"></a>Setting the default language for the application</h4></div></div></div><p> The default language for the application is set via the <code class="literal">[dspace-source]/config/dspace.cfg</code> parameter <code class="literal">default.locale</code>. </p><p> This is a locale according to i18n and might consist of country, country_language or country_language_variant, </p><p> e. g.: <code class="literal">default.locale=en</code>. If not default locale is specified the server locale will be used instead. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11F9A"></a>Supporting more than one language</h4></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N11F9E"></a>Changes in dspace.cfg</h5></div></div></div><p> With the <code class="literal">[dspace-source]/config/dspace.cfg</code> parameter <code class="literal">webui.supported.locales</code> you may provide a comma seperated list of supported (including the default locale) locales. </p><p> The locales might have the form country, country_language or country_language_variant, e. g.:</p><p><code class="literal">webui.supported.locales = en, de</code> or <code class="literal">webui.supported.locales = en, en_ca, de</code>.</p><p> This will result in: <div class="itemizedlist"><ul type="disc"><li><p> a language switch in the default header</p></li><li><p> the user will able to choose his preferred language, this will be part of his profile</p></li><li><p> wording of emails </p><div class="itemizedlist"><ul type="circle"><li><p> mails to registered users e. g. alerting service will use the preferred language of the user</p></li><li><p> mails to unregistered users e. g. suggest an item will use the language of the session</p></li></ul></div></li><li><p> according to the language selected for the session, using dspace-admin Edit News will edit the news file of the language according to session</p></li></ul></div>
-</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N11FCE"></a>Related files</h5></div></div></div><p> If you set webui.supported.locales make sure that all the related additional files for each language are available. <code class="literal">LOCALE</code> should correspond to the locale set in <code class="literal">webui.supported.locales</code>, e. g.: for webui.supported.locales = en, de, fr, there should be: <div class="itemizedlist"><ul type="disc"><li><p>
+        </p><p>The vocabulary element has an optional boolean attribute <span class="bold"><strong>closed</strong></span> that can be used to force input only with the javascript of controlled-vocabulary add-on. The default behaviour (i.e. without this attribute) is as set <span class="bold"><strong>closed="false"</strong></span>. This allow the user also to enter the value in free way.</p><p>The following vocabularies are currently available by default:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>nsi</strong></span>  - <span class="emphasis"><em>nsi.xml</em></span> - The Norwegian Science Index</p></li><li><p><span class="bold"><strong>srsc</strong></span>  - <span class="emphasis"><em>srsc.xml</em></span> - Swedish Research Subject Categories</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N11FB1"></a>5.6.3.&nbsp;<a name="docbook-configure.html-jspui-multilingual"></a>Configuring Multilingual Support</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11FB8"></a>Setting the default language for the application</h4></div></div></div><p> The default language for the application is set via the <code class="literal">[dspace-source]/config/dspace.cfg</code> parameter <code class="literal">default.locale</code>. </p><p> This is a locale according to i18n and might consist of country, country_language or country_language_variant, </p><p> e. g.: <code class="literal">default.locale=en</code>. If not default locale is specified the server locale will be used instead. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N11FCE"></a>Supporting more than one language</h4></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N11FD2"></a>Changes in dspace.cfg</h5></div></div></div><p> With the <code class="literal">[dspace-source]/config/dspace.cfg</code> parameter <code class="literal">webui.supported.locales</code> you may provide a comma seperated list of supported (including the default locale) locales. </p><p> The locales might have the form country, country_language or country_language_variant, e. g.:</p><p><code class="literal">webui.supported.locales = en, de</code> or <code class="literal">webui.supported.locales = en, en_ca, de</code>.</p><p> This will result in: <div class="itemizedlist"><ul type="disc"><li><p> a language switch in the default header</p></li><li><p> the user will able to choose his preferred language, this will be part of his profile</p></li><li><p> wording of emails </p><div class="itemizedlist"><ul type="circle"><li><p> mails to registered users e. g. alerting service will use the preferred language of the user</p></li><li><p> mails to unregistered users e. g. suggest an item will use the language of the session</p></li></ul></div></li><li><p> according to the language selected for the session, using dspace-admin Edit News will edit the news file of the language according to session</p></li></ul></div>
+</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N12002"></a>Related files</h5></div></div></div><p> If you set webui.supported.locales make sure that all the related additional files for each language are available. <code class="literal">LOCALE</code> should correspond to the locale set in <code class="literal">webui.supported.locales</code>, e. g.: for webui.supported.locales = en, de, fr, there should be: <div class="itemizedlist"><ul type="disc"><li><p>
                     <code class="literal">[dspace-source]/dspace/modules/jspui/src/main/resources/Messages.properties</code>
                   </p></li><li><p>
                     <code class="literal">[dspace-source]/dspace/modules/jspui/src/main/resources/Messages_en.properties</code>
@@ -757,7 +765,7 @@ s = GIF, JPEG, image/png
                     <code class="literal">[dspace]/webapps/jspui/help/site-admin_LOCALE.html</code>
                     <span class="emphasis"><em>must be copied to [dspace-source]/dspace/modules/jspui/src/main/webapp/help</em></span>
                   </p></li></ul></div>
-</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1207F"></a>5.6.4.&nbsp;<a name="docbook-configure.html-jspui-jsp"></a>Customizing the JSP pages</h3></div></div></div><p>The JSPUI interface is implemented using Java Servlets which handle the business logic, and JavaServer Pages (JSPs) which produce the HTML pages sent to an end-user. Since the JSPs are much closer to HTML than Java code, altering the look and feel of DSpace is relatively easy.</p><p>To make it even easier, DSpace allows you to 'override' the JSPs included in the source distribution with modified versions, that are stored in a separate place, so when it comes to updating your site with a new DSpace release, your modified versions will not be overwritten. It should be possible to dramatically change the look of DSpace to suit your organization by just changing the CSS style file and the site 'skin' or 'layout' JSPs in <code class="literal">jsp/layout</code>; if possible, it is recommended you limit local customizations to these files to make future upgrades easier.</p><p>You can also easily edit the text that appears on each JSP page by editing the dictionary file. However, note that unless you change the entry in all of the different language message files, users of other languages will still see the default text for their language. See <a class="ulink" href="application.html#i18n" target="_top">internationalization</a>.</p><p>Note that the data (attributes) passed from an underlying Servlet to the JSP may change between versions, so you may have to modify your customized JSP to deal with the new data.</p><p>Thus, if possible, it is recommended you limit your changes to the 'layout' JSPs and the stylesheet.</p><p>The JSPs are available in one of two places:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-webapp/src/main/webapp/</code>  - Only exists if you downloaded the full Source Release of DSpace</p></li><li><p><code class="literal">[dspace-source]/dspace/target/dspace-[version].dir/webapps/dspace-jspui-webapp/</code>  - The location where they are copied after first building DSpace.</p></li></ul></div><p>If you wish to modify a particular JSP, place your edited version in the <code class="literal">[dspace-source]/dspace/modules/jspui/src/main/webapp/</code> directory (<span class="emphasis"><em>this is the replacement for the pre-1.5 <code class="literal">/jsp/local</code> directory</em></span>), with the same path as the original. If they exist, these will be used in preference to the default JSPs. For example:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N120B3"></a>5.6.4.&nbsp;<a name="docbook-configure.html-jspui-jsp"></a>Customizing the JSP pages</h3></div></div></div><p>The JSPUI interface is implemented using Java Servlets which handle the business logic, and JavaServer Pages (JSPs) which produce the HTML pages sent to an end-user. Since the JSPs are much closer to HTML than Java code, altering the look and feel of DSpace is relatively easy.</p><p>To make it even easier, DSpace allows you to 'override' the JSPs included in the source distribution with modified versions, that are stored in a separate place, so when it comes to updating your site with a new DSpace release, your modified versions will not be overwritten. It should be possible to dramatically change the look of DSpace to suit your organization by just changing the CSS style file and the site 'skin' or 'layout' JSPs in <code class="literal">jsp/layout</code>; if possible, it is recommended you limit local customizations to these files to make future upgrades easier.</p><p>You can also easily edit the text that appears on each JSP page by editing the dictionary file. However, note that unless you change the entry in all of the different language message files, users of other languages will still see the default text for their language. See <a class="link" href="ch09.html#docbook-application.html-i18n">internationalization</a>.</p><p>Note that the data (attributes) passed from an underlying Servlet to the JSP may change between versions, so you may have to modify your customized JSP to deal with the new data.</p><p>Thus, if possible, it is recommended you limit your changes to the 'layout' JSPs and the stylesheet.</p><p>The JSPs are available in one of two places:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-webapp/src/main/webapp/</code>  - Only exists if you downloaded the full Source Release of DSpace</p></li><li><p><code class="literal">[dspace-source]/dspace/target/dspace-[version].dir/webapps/dspace-jspui-webapp/</code>  - The location where they are copied after first building DSpace.</p></li></ul></div><p>If you wish to modify a particular JSP, place your edited version in the <code class="literal">[dspace-source]/dspace/modules/jspui/src/main/webapp/</code> directory (<span class="emphasis"><em>this is the replacement for the pre-1.5 <code class="literal">/jsp/local</code> directory</em></span>), with the same path as the original. If they exist, these will be used in preference to the default JSPs. For example:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>DSpace default</strong></span>
                   </p>
@@ -781,12 +789,12 @@ s = GIF, JPEG, image/png
                   <p>
                     <code class="literal">[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/mydspace/main.jsp</code>
                   </p>
-                </td></tr></tbody></table></div><p>Heavy use is made of a style sheet, <code class="literal">styles.css.jsp</code>. If you make edits, copy the local version to <code class="literal">[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/styles.css.jsp</code>, and it will be used automatically in preference to the default, as described above.</p><p>Fonts and colors can be easily changed using the stylesheet. The stylesheet is a JSP so that the user's browser version can be detected and the stylesheet tweaked accordingly.</p><p>The 'layout' of each page, that is, the top and bottom banners and the navigation bar, are determined by the JSPs <code class="literal">/layout/header-*.jsp</code> and <code class="literal">/layout/footer-*.jsp</code>. You can provide modified versions of these (in <code class="literal">[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/layout</code>), or define more styles and apply them to pages by using the "style" attribute of the <code class="literal">dspace:layout</code> tag.</p><p>After you've customized your JSPs, <span class="bold"><strong>you must rebuild the DSpace Web application</strong></span>. If you haven't already built and installed it, follow the <a class="ulink" href="install.html" target="_top">install</a> directions. Otherwise, follow the steps below:</p><div class="orderedlist"><ol type="1"><li><p> Rebuild the DSpace installation package by running the following command from your <code class="literal">[dspace-source]/dspace/</code> directory:</p><pre class="screen">
+                </td></tr></tbody></table></div><p>Heavy use is made of a style sheet, <code class="literal">styles.css.jsp</code>. If you make edits, copy the local version to <code class="literal">[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/styles.css.jsp</code>, and it will be used automatically in preference to the default, as described above.</p><p>Fonts and colors can be easily changed using the stylesheet. The stylesheet is a JSP so that the user's browser version can be detected and the stylesheet tweaked accordingly.</p><p>The 'layout' of each page, that is, the top and bottom banners and the navigation bar, are determined by the JSPs <code class="literal">/layout/header-*.jsp</code> and <code class="literal">/layout/footer-*.jsp</code>. You can provide modified versions of these (in <code class="literal">[jsp.custom-dir]/dspace/modules/jspui/src/main/webapp/layout</code>), or define more styles and apply them to pages by using the "style" attribute of the <code class="literal">dspace:layout</code> tag.</p><p>After you've customized your JSPs, <span class="bold"><strong>you must rebuild the DSpace Web application</strong></span>. If you haven't already built and installed it, follow the <a class="link" href="ch03.html#docbook-install.html">install</a> directions. Otherwise, follow the steps below:</p><div class="orderedlist"><ol type="1"><li><p> Rebuild the DSpace installation package by running the following command from your <code class="literal">[dspace-source]/dspace/</code> directory:</p><pre class="screen">
 mvn package
 </pre></li><li><p> Re-install the DSpace WAR(s) to <code class="literal">[dspace]/webapps</code> by running the following command from your <code class="literal">[dspace-source]/dspace/target/dspace-[version].dir</code> directory:</p><pre class="screen">
 ant -Dconfig=<span class="emphasis"><em> [dspace-source]</em></span>/config/dspace.cfg
 	update
-</pre></li><li><p> Depending on your setup with Tomcat, you may also need to do the following:</p><div class="itemizedlist"><ul type="disc"><li><p> Shut down Tomcat, and delete any existing <span class="emphasis"><em>[tomcat]</em></span>/webapps/dspace directories.</p></li><li><p> Copy the new .war file(s) to the Tomcat webapps directory:</p></li><li><p> Restart Tomcat.</p></li></ul></div></li></ol></div><p>When you restart the web server you should see your customized JSPs.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12150"></a>5.7.&nbsp;<a name="docbook-configure.html-advanced"></a>Advanced DSpace Customizations</h2></div></div></div><p>Some customizations to the DSpace platform require advanced skills or knowlege to complete. The options list here will require either knowlege in system administration or may involve light programming.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12159"></a>5.7.1.&nbsp;<a name="docbook-configure.html-checksum"></a>Checksum Checker</h3></div></div></div><p>There are three aspects of the Checksum Checker's operation that can be configured:</p><div class="orderedlist"><ol type="1"><li><p> the execution mode</p></li><li><p> the logging output</p></li><li><p> the policy for removing old checksum results from the database</p></li></ol></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1216E"></a>Checker Execution Mode</h4></div></div></div><p>Execution mode can be configured using command line options. Information on the options can be found at any time by running <code class="literal">[dspace]/bin/checker --help</code>. The different modes are described below; see the "Which to use" section that follows for details on the various pros and cons.</p><p>Unless a particular bitstream or handle is specified, the Checksum Checker will always check bitstreams in order of the least recently checked bitstream. (Note that this means that the most recently ingested bitstreams will be the last ones checked by the Checksum Checker.)</p><p>To check a specific number of bitstreams, use the -c option followed by an integer number of bitstreams to check:</p><pre class="screen">
+</pre></li><li><p> Depending on your setup with Tomcat, you may also need to do the following:</p><div class="itemizedlist"><ul type="disc"><li><p> Shut down Tomcat, and delete any existing <span class="emphasis"><em>[tomcat]</em></span>/webapps/dspace directories.</p></li><li><p> Copy the new .war file(s) to the Tomcat webapps directory:</p></li><li><p> Restart Tomcat.</p></li></ul></div></li></ol></div><p>When you restart the web server you should see your customized JSPs.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12184"></a>5.7.&nbsp;<a name="docbook-configure.html-advanced"></a>Advanced DSpace Customizations</h2></div></div></div><p>Some customizations to the DSpace platform require advanced skills or knowlege to complete. The options list here will require either knowlege in system administration or may involve light programming.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1218D"></a>5.7.1.&nbsp;<a name="docbook-configure.html-checksum"></a>Checksum Checker</h3></div></div></div><p>There are three aspects of the Checksum Checker's operation that can be configured:</p><div class="orderedlist"><ol type="1"><li><p> the execution mode</p></li><li><p> the logging output</p></li><li><p> the policy for removing old checksum results from the database</p></li></ol></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N121A2"></a>Checker Execution Mode</h4></div></div></div><p>Execution mode can be configured using command line options. Information on the options can be found at any time by running <code class="literal">[dspace]/bin/checker --help</code>. The different modes are described below; see the "Which to use" section that follows for details on the various pros and cons.</p><p>Unless a particular bitstream or handle is specified, the Checksum Checker will always check bitstreams in order of the least recently checked bitstream. (Note that this means that the most recently ingested bitstreams will be the last ones checked by the Checksum Checker.)</p><p>To check a specific number of bitstreams, use the -c option followed by an integer number of bitstreams to check:</p><pre class="screen">
 bin/checker -c 10
 </pre><p>Limited count mode is particularly useful for checking that the checker is executing properly. The Checksum Checker's default execution mode is to check a single bitstream, as if the -c 1 option had been given.</p><p>To run the Checker for a specific period of time, use the -d option with a time argument:</p><pre class="screen">
 bin/checker -d 10m
@@ -798,10 +806,10 @@ bin/checker -a 123456/123
 </pre><p>This will check all the bitstreams inside an item, collection or community.</p><p>There are two looping modes:</p><pre class="screen">
 bin/checker -l     # Loops once through the repository  
 bin/checker -L      # Loops continuously through the repository
-</pre><p>The -l option can be used if your repository is relatively small and your backup strategy requires it to be completely validated at a particular point. The -L option might be useful if you have a large repository, and you don't mind (or can avoid) the IO load caused by the checker.</p><p>The Checksum Checker was designed with the idea that most sys admins will run it from the cron. For small repositories we recommend using the -l option in the cron. For larger repositories that cannot be completely checked in a couple of hours, we recommend the -d option in the cron.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N121B9"></a>Checker Reporting</h4></div></div></div><p>Checksum Checker uses log4j to report its results. By default it will report to a log called <code class="literal">[dspace]/log/checker.log</code>, and it will report only on bitstreams for which the newly calculated checksum does not match the stored checksum. To report on all bitstreams checked regardless of outcome, use the <code class="literal">-v</code> (verbose) command line option:</p><pre class="screen">
+</pre><p>The -l option can be used if your repository is relatively small and your backup strategy requires it to be completely validated at a particular point. The -L option might be useful if you have a large repository, and you don't mind (or can avoid) the IO load caused by the checker.</p><p>The Checksum Checker was designed with the idea that most sys admins will run it from the cron. For small repositories we recommend using the -l option in the cron. For larger repositories that cannot be completely checked in a couple of hours, we recommend the -d option in the cron.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N121ED"></a>Checker Reporting</h4></div></div></div><p>Checksum Checker uses log4j to report its results. By default it will report to a log called <code class="literal">[dspace]/log/checker.log</code>, and it will report only on bitstreams for which the newly calculated checksum does not match the stored checksum. To report on all bitstreams checked regardless of outcome, use the <code class="literal">-v</code> (verbose) command line option:</p><pre class="screen">
 bin/checker -l -v    #Loop through the repository once and
   report in detail about every bitstream checked.
-</pre><p>To change the location of the log, or to modify the prefix used on each line of output, edit the <code class="literal">[dspace]/config/templates/log4j.properties</code> file and run <code class="literal">[dspace]/bin/install_configs</code>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N121D4"></a>Checker Results Pruning</h4></div></div></div><p>The Checksum Checker will store the result of every check in the checksum_history table. By default, successful checksum matches that are eight weeks old or older will be deleted when the -p command line option is used (unsuccessful ones will be retained indefinitely). The amount of time for which results are retained in the checksum_history table can be modified by one of two methods:</p><div class="orderedlist"><ol type="1"><li><p> editing the retention policies in <code class="literal">[dspace]/config/dspace.cfg</code> OR</p></li><li><p> passing in a properties file containing retention policies when using the -p option.</p></li></ol></div><p>Pruning is controlled by a number of properties, each of which describes a checksum result code, and the length of time for which results with that code should be retained. The format is <code class="literal">checker.retention.[RESULT CODE]=[duration]</code>. For example: -</p><pre class="screen">
+</pre><p>To change the location of the log, or to modify the prefix used on each line of output, edit the <code class="literal">[dspace]/config/templates/log4j.properties</code> file and run <code class="literal">[dspace]/bin/install_configs</code>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12208"></a>Checker Results Pruning</h4></div></div></div><p>The Checksum Checker will store the result of every check in the checksum_history table. By default, successful checksum matches that are eight weeks old or older will be deleted when the -p command line option is used (unsuccessful ones will be retained indefinitely). The amount of time for which results are retained in the checksum_history table can be modified by one of two methods:</p><div class="orderedlist"><ol type="1"><li><p> editing the retention policies in <code class="literal">[dspace]/config/dspace.cfg</code> OR</p></li><li><p> passing in a properties file containing retention policies when using the -p option.</p></li></ol></div><p>Pruning is controlled by a number of properties, each of which describes a checksum result code, and the length of time for which results with that code should be retained. The format is <code class="literal">checker.retention.[RESULT CODE]=[duration]</code>. For example: -</p><pre class="screen">
 checker.retention.CHECKSUM_MATCH=8w
 </pre><p>indicates that successful checksum matches will be retained for eight weeks. Supported units of time are</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                     <p>s</p>
@@ -827,7 +835,7 @@ checker.retention.CHECKSUM_MATCH=8w
                     <p>y</p>
                   </td><td>
                     <p>Years</p>
-                  </td></tr></tbody></table></div><p>(Note that these units are also used for describing durations for the <code class="literal">-d</code> limited duration mode.)</p><p>There is a special property, <code class="literal">checker.retention.default</code>, that is used to assign a default retention period.</p><p>To execute the pruning you must use the -p command line option (with or without a properties file). Checksum Checker will prune the history table before beginning new checks. We recommend that you use this option regularly, as the checksum_history table can grow very large without it.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1224D"></a>5.7.2.&nbsp;<a name="docbook-configure.html-authentication"></a>Custom Authentication</h3></div></div></div><p>Since many institutions and organizations have exisiting authentication systems, DSpace has been designed to allow these to be easily integrated into an existing authentication infrastructure. It keeps a series, or "stack", of <span class="emphasis"><em>authentication methods</em></span>, so each one can be tried in turn. This makes it easy to add new authentication methods or rearrange the order without changing any existing code. You can also share authentication code with other sites.</p><p>The configuration property <code class="literal">plugin.sequence.org.dspace.authenticate.AuthenticationMethod</code> defines the authentication stack. It is a comma-separated list of class names. Each of these classes implements a different <span class="emphasis"><em>authentication method</em></span>, or way of determining the identity of the user. They are invoked in the order specified until one succeeds.</p><p>An authentication method is a class that implements the interface <code class="literal">org.dspace.authenticate.AuthenticationMethod</code>. It <span class="emphasis"><em>authenticates</em></span> a user by evaluating the <span class="emphasis"><em>credentials</em></span> (e.g. username and password) he or she presents and checking that they are valid.</p><p>The basic authentication procedure in the DSpace Web UI is this:</p><div class="orderedlist"><ol type="1"><li><p> A request is received from an end-user's browser that, if fulfilled, would lead to an action requiring authorization taking place.</p></li><li><p> If the end-user is already authenticated: </p><div class="itemizedlist"><ul type="disc"><li><p> If the end-user is allowed to perform the action, the action proceeds</p></li><li><p> If the end-user is NOT allowed to perform the action, an authorization error is displayed.</p></li><li><p> If the end-user is NOT authenticated, i.e. is accessing DSpace anonymously:</p></li></ul></div></li><li><p> The parameters etc. of the request are stored</p></li><li><p> The Web UI's <code class="literal">startAuthentication</code> method is invoked.</p></li><li><p> First it tries all the authentication methods which do <span class="emphasis"><em>implicit</em></span> authentication (i.e. they work with just the information already in the Web request, such as an X.509 client certificate). If one of these succeeds, it proceeds from Step 2 above.</p></li><li><p> If none of the implicit methods succeed, the UI responds by putting up a "login" page to collect credentials for one of the <span class="emphasis"><em>explicit</em></span> authentication methods in the stack. The servlet processing that page then gives the proffered credentials to each authentication method in turn until one succeeds, at which point it retries the original operation from Step 2 above.</p></li></ol></div><p>Please see the source files <code class="literal">AuthenticationManager.java</code> and <code class="literal">AuthenticationMethod.java</code> for more details about this mechanism.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N122A3"></a>Authentication by Password</h4></div></div></div><p>The default method <code class="literal">org.dspace.authenticate.PasswordAuthentication</code> has the following properties:</p><div class="itemizedlist"><ul type="disc"><li><p> Use of inbuilt e-mail address/password-based log-in. This is achieved by forwarding a request that is attempting an action requiring authorization to the password log-in servlet, <code class="literal">/password-login</code>. The password log-in servlet (<code class="literal">org.dspace.app.webui.servlet.PasswordServlet</code> contains code that will resume the original request if authentication is successful, as per step 3. described above.</p></li><li><p> Users can register themselves (i.e. add themselves as e-people without needing approval from the administrators), and can set their own passwords when they do this</p></li><li><p> Users are not members of any special (dynamic) e-person groups</p></li><li><p> You can restrict the domains from which new users are able to regiser. To enable this feature, uncomment the following line from dspace.cfg: <code class="literal">authentication.password.domain.valid = example.com</code> Example options might be '<code class="literal">@example.com</code>' to restrict registration to users with addresses ending in @example.com, or '<code class="literal">@example.com, .ac.uk</code>' to restrict registration to users with addresses ending in @example.com or with addresses in the .ac.uk domain.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N122CE"></a>X.509 Certificate Authentication</h4></div></div></div><p>The X.509 authentication method uses an X.509 certificate sent by the client to establish his/her identity. It requires the client to have a personal Web certificate installed on their browser (or other client software) which is issued by a Certifying Authority (CA) recognized by the web server.</p><div class="orderedlist"><ol type="1"><li><p> See the <a class="ulink" href="install.html#https" target="_top">HTTPS installation instructions</a> to configure your Web server. If you are using HTTPS with Tomcat, note that the <code class="literal">&lt;Connector&gt;</code> tag <span class="emphasis"><em>must</em></span> include the attribute <code class="literal">clientAuth="true"</code> so the server requests a personal Web certificate from the client.</p></li><li><p> Add the <code class="literal">org.dspace.authenticate.X509Authentication</code> plugin <span class="emphasis"><em>first</em></span> to the list of stackable authentication methods in the value of the configuration key <code class="literal">plugin.sequence.org.dspace.authenticate.AuthenticationMethod</code><span class="emphasis"><em>E.g.:</em></span></p><pre class="screen">
+                  </td></tr></tbody></table></div><p>(Note that these units are also used for describing durations for the <code class="literal">-d</code> limited duration mode.)</p><p>There is a special property, <code class="literal">checker.retention.default</code>, that is used to assign a default retention period.</p><p>To execute the pruning you must use the -p command line option (with or without a properties file). Checksum Checker will prune the history table before beginning new checks. We recommend that you use this option regularly, as the checksum_history table can grow very large without it.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12281"></a>5.7.2.&nbsp;<a name="docbook-configure.html-authentication"></a>Custom Authentication</h3></div></div></div><p>Since many institutions and organizations have exisiting authentication systems, DSpace has been designed to allow these to be easily integrated into an existing authentication infrastructure. It keeps a series, or "stack", of <span class="emphasis"><em>authentication methods</em></span>, so each one can be tried in turn. This makes it easy to add new authentication methods or rearrange the order without changing any existing code. You can also share authentication code with other sites.</p><p>The configuration property <code class="literal">plugin.sequence.org.dspace.authenticate.AuthenticationMethod</code> defines the authentication stack. It is a comma-separated list of class names. Each of these classes implements a different <span class="emphasis"><em>authentication method</em></span>, or way of determining the identity of the user. They are invoked in the order specified until one succeeds.</p><p>An authentication method is a class that implements the interface <code class="literal">org.dspace.authenticate.AuthenticationMethod</code>. It <span class="emphasis"><em>authenticates</em></span> a user by evaluating the <span class="emphasis"><em>credentials</em></span> (e.g. username and password) he or she presents and checking that they are valid.</p><p>The basic authentication procedure in the DSpace Web UI is this:</p><div class="orderedlist"><ol type="1"><li><p> A request is received from an end-user's browser that, if fulfilled, would lead to an action requiring authorization taking place.</p></li><li><p> If the end-user is already authenticated: </p><div class="itemizedlist"><ul type="disc"><li><p> If the end-user is allowed to perform the action, the action proceeds</p></li><li><p> If the end-user is NOT allowed to perform the action, an authorization error is displayed.</p></li><li><p> If the end-user is NOT authenticated, i.e. is accessing DSpace anonymously:</p></li></ul></div></li><li><p> The parameters etc. of the request are stored</p></li><li><p> The Web UI's <code class="literal">startAuthentication</code> method is invoked.</p></li><li><p> First it tries all the authentication methods which do <span class="emphasis"><em>implicit</em></span> authentication (i.e. they work with just the information already in the Web request, such as an X.509 client certificate). If one of these succeeds, it proceeds from Step 2 above.</p></li><li><p> If none of the implicit methods succeed, the UI responds by putting up a "login" page to collect credentials for one of the <span class="emphasis"><em>explicit</em></span> authentication methods in the stack. The servlet processing that page then gives the proffered credentials to each authentication method in turn until one succeeds, at which point it retries the original operation from Step 2 above.</p></li></ol></div><p>Please see the source files <code class="literal">AuthenticationManager.java</code> and <code class="literal">AuthenticationMethod.java</code> for more details about this mechanism.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N122D7"></a>Authentication by Password</h4></div></div></div><p>The default method <code class="literal">org.dspace.authenticate.PasswordAuthentication</code> has the following properties:</p><div class="itemizedlist"><ul type="disc"><li><p> Use of inbuilt e-mail address/password-based log-in. This is achieved by forwarding a request that is attempting an action requiring authorization to the password log-in servlet, <code class="literal">/password-login</code>. The password log-in servlet (<code class="literal">org.dspace.app.webui.servlet.PasswordServlet</code> contains code that will resume the original request if authentication is successful, as per step 3. described above.</p></li><li><p> Users can register themselves (i.e. add themselves as e-people without needing approval from the administrators), and can set their own passwords when they do this</p></li><li><p> Users are not members of any special (dynamic) e-person groups</p></li><li><p> You can restrict the domains from which new users are able to regiser. To enable this feature, uncomment the following line from dspace.cfg: <code class="literal">authentication.password.domain.valid = example.com</code> Example options might be '<code class="literal">@example.com</code>' to restrict registration to users with addresses ending in @example.com, or '<code class="literal">@example.com, .ac.uk</code>' to restrict registration to users with addresses ending in @example.com or with addresses in the .ac.uk domain.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12302"></a>X.509 Certificate Authentication</h4></div></div></div><p>The X.509 authentication method uses an X.509 certificate sent by the client to establish his/her identity. It requires the client to have a personal Web certificate installed on their browser (or other client software) which is issued by a Certifying Authority (CA) recognized by the web server.</p><div class="orderedlist"><ol type="1"><li><p> See the <a class="link" href="ch03.html#docbook-install.html-https">HTTPS installation instructions</a> to configure your Web server. If you are using HTTPS with Tomcat, note that the <code class="literal">&lt;Connector&gt;</code> tag <span class="emphasis"><em>must</em></span> include the attribute <code class="literal">clientAuth="true"</code> so the server requests a personal Web certificate from the client.</p></li><li><p> Add the <code class="literal">org.dspace.authenticate.X509Authentication</code> plugin <span class="emphasis"><em>first</em></span> to the list of stackable authentication methods in the value of the configuration key <code class="literal">plugin.sequence.org.dspace.authenticate.AuthenticationMethod</code><span class="emphasis"><em>E.g.:</em></span></p><pre class="screen">
     plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \
         org.dspace.authenticate.X509Authentication, \
         org.dspace.authenticate.PasswordAuthentication
@@ -840,7 +848,7 @@ checker.retention.CHECKSUM_MATCH=8w
 </pre><p> ...or the separate CA certificate file (in PEM or DER format): </p><pre class="screen">
   authentication.x509.ca.cert = <span class="emphasis"><em> path to certificate file for CA
 	whose client certs to accept.</em></span>
-</pre></li><li><p> Choose whether to enable auto-registration: If you want users who authenticate successfully to be automatically registered as new E-Persons if they are not already, set the <code class="literal">authentication.x509.autoregister</code> configuration property to <code class="literal">true</code>. This lets you automatically accept all users with valid personal certificates. The default is <code class="literal">false</code>.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12321"></a>Example of a Custom Authentication Method</h4></div></div></div><p>Also included in the source is an implementation of an authentication method used at MIT, <code class="literal">edu.mit.dspace.MITSpecialGroup</code>. This does not actually authenticate a user, it <span class="emphasis"><em>only</em></span> adds the current user to a special (dynamic) group called 'MIT Users' (which must be present in the system!). This allows us to create authorization policies for MIT users without having to manually maintain membership of the MIT users group.</p><p>By keeping this code in a separate method, we can customize the authentication process for MIT by simply adding it to the stack in the DSpace configuration. None of the code has to be touched.</p><p>You can create your own custom authentication method and add it to the stack. Use the most similar existing method as a model, e.g. <code class="literal">org.dspace.authenticate.PasswordAuthentication</code> for an "explicit" method (with credentials entered interactively) or <code class="literal">org.dspace.authenticate.X509Authentication</code> for an implicit method.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1233A"></a><a name="docbook-configure.html-ipauthentication"></a>Configuring IP Authentication</h4></div></div></div><p>You can enable IP authentication by adding its method to the stack in the DSpace configuration, e.g.:</p><pre class="screen">
+</pre></li><li><p> Choose whether to enable auto-registration: If you want users who authenticate successfully to be automatically registered as new E-Persons if they are not already, set the <code class="literal">authentication.x509.autoregister</code> configuration property to <code class="literal">true</code>. This lets you automatically accept all users with valid personal certificates. The default is <code class="literal">false</code>.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12355"></a>Example of a Custom Authentication Method</h4></div></div></div><p>Also included in the source is an implementation of an authentication method used at MIT, <code class="literal">edu.mit.dspace.MITSpecialGroup</code>. This does not actually authenticate a user, it <span class="emphasis"><em>only</em></span> adds the current user to a special (dynamic) group called 'MIT Users' (which must be present in the system!). This allows us to create authorization policies for MIT users without having to manually maintain membership of the MIT users group.</p><p>By keeping this code in a separate method, we can customize the authentication process for MIT by simply adding it to the stack in the DSpace configuration. None of the code has to be touched.</p><p>You can create your own custom authentication method and add it to the stack. Use the most similar existing method as a model, e.g. <code class="literal">org.dspace.authenticate.PasswordAuthentication</code> for an "explicit" method (with credentials entered interactively) or <code class="literal">org.dspace.authenticate.X509Authentication</code> for an implicit method.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1236E"></a><a name="docbook-configure.html-ipauthentication"></a>Configuring IP Authentication</h4></div></div></div><p>You can enable IP authentication by adding its method to the stack in the DSpace configuration, e.g.:</p><pre class="screen">
 plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
 	org.dspace.authenticate.IPAuthentication
 </pre><p>You are than able to map DSpace groups to IP's in dspace.cfg by setting authentication.ip.GROUPNAME = iprange[, iprange ...], e.g:</p><pre class="screen">
@@ -852,7 +860,7 @@ plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
                                     12.7.8.9/255.255.128.0 # with
 	netmask
  
-</pre><p><span class="bold"><strong>Note:</strong></span> if the Groupname contains blanks you must escape the, e.g. Department\ of\ Statistics</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12350"></a><a name="docbook-configure.html-ldap"></a>Configuring LDAP Authentication</h4></div></div></div><p>You can enable LDAP authentication by adding its method to the stack in the DSpace configuration, e.g.</p><pre class="screen">
+</pre><p><span class="bold"><strong>Note:</strong></span> if the Groupname contains blanks you must escape the, e.g. Department\ of\ Statistics</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12384"></a><a name="docbook-configure.html-ldap"></a>Configuring LDAP Authentication</h4></div></div></div><p>You can enable LDAP authentication by adding its method to the stack in the DSpace configuration, e.g.</p><pre class="screen">
 plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
 	org.dspace.authenticate.LDAPAuthentication
 </pre><p>If LDAP is enabled in the dspace.cfg file, then new users will be able to register by entering their username and password without being sent the registration token. If users do not have a username and password, then they can still register and login with just their email address the same way they do now.</p><p>If you want to give any special privileges to LDAP users, create a stackable authentication method to automatically put people who have a netid into a special group. You might also want to give certain email addresses special privileges. Refer to the <a name="docbook-configure.html--authenticate.1"></a>Custom Authentication Code section above for more information about how to do this.</p><p>Here is an explanation of what each of the different configuration parameters are for:</p><div class="itemizedlist"><ul type="disc"><li><p>
@@ -875,7 +883,7 @@ plugin.sequence.org.dspace.authenticate.AuthenticationMethod =
                 <span class="bold"><strong>ldap.givenname_field = givenName</strong></span>
               </p><p>  This is the LDAP object field where the user's given names are stored. I'm not sure how common the givenName field is in different LDAP instances. If the field is not found the field will be left blank in the new eperson object.</p></li><li><p>
                 <span class="bold"><strong>ldap.phone_field = telephoneNumber</strong></span>
-              </p><p>  This is the field where the user's phone number is stored in the LDAP directory. If the field is not found the field will be left blank in the new eperson object.</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N123C1"></a>5.7.3.&nbsp;<a name="docbook-configure.html-statistics"></a>Configuring System Statistical Reports</h3></div></div></div><p>Statistics for the system can be made available at <code class="literal">http://www.mydspaceinstance.edu/statistics</code>. To use the system statistics you will have to initialise them as per the installation documentation, but before you do so you need to perform the customisations discussed here in order to ensure that the reports are generated correctly.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N123CE"></a>Configuration File</h4></div></div></div><p>Configuration for the statistics system are in <code class="literal">[dspace]/config/dstat.cfg</code> and the file should guide you to correctly filling in the details required. For the most part you will not need to change this file. You may wish to edit <code class="literal">start.year</code> and <code class="literal">start.month</code> to customize the start date of the statistics.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N123E0"></a>Generating the statistics</h4></div></div></div><p>The following scripts must be run (in this order) generate the statistcis:</p><pre class="screen">
+              </p><p>  This is the field where the user's phone number is stored in the LDAP directory. If the field is not found the field will be left blank in the new eperson object.</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N123F5"></a>5.7.3.&nbsp;<a name="docbook-configure.html-statistics"></a>Configuring System Statistical Reports</h3></div></div></div><p>Statistics for the system can be made available at <code class="literal">http://www.mydspaceinstance.edu/statistics</code>. To use the system statistics you will have to initialise them as per the installation documentation, but before you do so you need to perform the customisations discussed here in order to ensure that the reports are generated correctly.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12402"></a>Configuration File</h4></div></div></div><p>Configuration for the statistics system are in <code class="literal">[dspace]/config/dstat.cfg</code> and the file should guide you to correctly filling in the details required. For the most part you will not need to change this file. You may wish to edit <code class="literal">start.year</code> and <code class="literal">start.month</code> to customize the start date of the statistics.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12414"></a>Generating the statistics</h4></div></div></div><p>The following scripts must be run (in this order) generate the statistcis:</p><pre class="screen">
 stat-initial
 stat-general
 stat-monthly
@@ -885,7 +893,7 @@ stat-report-monthly
 </pre><p>Scripts eding with <code class="literal">-general</code> do the work for building reports spanning the entire history of the archive; scripts ending <code class="literal">-initial</code> are to initialise the reports by doing monthly reports from some start date up to the present; scripts ending <code class="literal">-monthly</code> generate a single monthly report <span class="emphasis"><em>for the current month</em></span>.</p><p><code class="literal">stat-inital</code> and <code class="literal">stat-report-inital</code> must be run to generate the first set of statistics. Following that, <code class="literal">stat-monthly</code>, <code class="literal">stat-general</code>, <code class="literal">stat-report-monthly</code> and <code class="literal">stat-report-general</code> should be run daily to update the statistics reports.</p><p>If you want additional customisations, you can find additional information about the scripts by running:</p><pre class="screen">
 [dspace]/bin/dsrun org.dspace.app.statistics.LogAnalyser -help
 [dspace]/bin/dsrun org.dspace.app.statistics.ReportGenerator -help
-</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12418"></a>5.7.4.&nbsp;<a name="docbook-configure.html-oai"></a>Activating Additional OAI-PMH Crosswalks</h3></div></div></div><p>DSpace comes with an unqualified DC Crosswalk used in the default OAI-PMH data provider. There are also other Crosswalks bundled with the DSpace distribution which can be activated by editing one or more configuration files. How to do this for each available Crosswalk is described below. The DSpace source includes the following crosswalk plugins available for use with OAI-PMH:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>
+</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1244C"></a>5.7.4.&nbsp;<a name="docbook-configure.html-oai"></a>Activating Additional OAI-PMH Crosswalks</h3></div></div></div><p>DSpace comes with an unqualified DC Crosswalk used in the default OAI-PMH data provider. There are also other Crosswalks bundled with the DSpace distribution which can be activated by editing one or more configuration files. How to do this for each available Crosswalk is described below. The DSpace source includes the following crosswalk plugins available for use with OAI-PMH:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>
                 <code class="literal">mets</code>
               </strong></span>
   - The manifest document from a DSpace METS SIP.</p></li><li><p><span class="bold"><strong>
@@ -898,7 +906,7 @@ stat-report-monthly
               <code class="literal">Crosswalks.</code>
               <span class="emphasis"><em>plugin_name</em></span>
               <code class="literal">=org.dspace.app.oai.PluginCrosswalk</code>
-            </p><p> substituting the plugin's name, e.g. <code class="literal">"mets"</code> or <code class="literal">"qdc"</code>for <span class="emphasis"><em>plugin_name</em></span>.</p></li><li><p> Run the <code class="literal">bin/install-configs</code> script</p></li><li><p> Restart your servlet container, e.g. Tomcat, for the change to take effect.</p></li></ol></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12481"></a>DIDL</h4></div></div></div><p>By activating the DIDL provider, DSpace items are represented as MPEG-21 DIDL objects. These DIDL objects are XML documents that wrap both the Dublin Core metadata that describes the DSpace item and its actual bitstreams. A bitstream is provided inline in the DIDL object in a base64 encoded manner, and/or by means of a pointer to the bitstream. The data provider exposes DIDL objects via the metadataPrefix didl.</p><p>The crosswalk does not deal with special characters and purposely skips dissemination of the <code class="literal">license.txt</code> file awaiting a better understanding on how to map DSpace rights information to MPEG21-DIDL.</p><p>The DIDL Crosswalk can be activated as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> Uncomment the <code class="literal">oai.didl.maxresponse</code> item in <code class="literal">dspace.cfg</code></p></li><li><p> Uncomment the DIDL Crosswalk entry from the <code class="literal">config/templates/oaicat.properties</code> file</p></li><li><p> Run the <code class="literal">bin/install-configs</code> script</p></li><li><p> Restart Tomcat</p></li><li><p> Verify the Crosswalk is activated by accessing a URL such as <code class="literal">http://mydspace/oai/request?verb=ListRecords&amp;metadataPrefix=didl</code></p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N124B1"></a>5.7.5.&nbsp;<a name="docbook-configure.html-packager"></a>Configuring Packager Plugins</h3></div></div></div><p>Package ingester plugins are configured as <a class="ulink" href="business.html#plugin" target="_top">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.packager.PackageIngester</code>. Package disseminator plugins are configured as <a class="ulink" href="business.html#plugin" target="_top">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.packager.PackageDisseminator</code>.</p><p>You can add names for the existing plugins, and add new plugins, by altering these configuration properties. See the <a class="ulink" href="business.html#plugin" target="_top">Plugin Manager</a> architecture for more information about plugins.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N124D0"></a>5.7.6.&nbsp;<a name="docbook-configure.html-crosswalk"></a>Configuring Crosswalk Plugins</h3></div></div></div><p>Ingestion crosswalk plugins are configured as <a class="ulink" href="business.html#plugin" target="_top">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.crosswalk.IngestionCrosswalk</code>. Dissemination crosswalk plugins are configured as <a class="ulink" href="business.html#plugin" target="_top">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.crosswalk.DisseminationCrosswalk</code>.</p><p>You can add names for existing crosswalks, add new plugin classes, and add new configurations for the configurable crosswalks as noted below.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N124EB"></a><a name="docbook-configure.html-mods"></a>Configurable MODS dissemination crosswalk</h4></div></div></div><p>The MODS crosswalk is a self-named plugin. To configure an instance of the MODS crosswalk, add a property to the DSpace configuration starting with <code class="literal">"crosswalk.mods.properties."</code>; the final word of the property name becomes the plugin's name. For example, a property name <code class="literal">crosswalk.mods.properties.MODS</code> defines a crosswalk plugin named <code class="literal">"MODS"</code>.</p><p>The value of this property is a path to a separate properties file containing the configuration for this crosswalk. The pathname is relative to the DSpace configuration directory, i.e. the <code class="literal">config</code> subdirectory of the DSpace install directory. So, a line like:</p><pre class="screen">
+            </p><p> substituting the plugin's name, e.g. <code class="literal">"mets"</code> or <code class="literal">"qdc"</code>for <span class="emphasis"><em>plugin_name</em></span>.</p></li><li><p> Run the <code class="literal">bin/install-configs</code> script</p></li><li><p> Restart your servlet container, e.g. Tomcat, for the change to take effect.</p></li></ol></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N124B5"></a>DIDL</h4></div></div></div><p>By activating the DIDL provider, DSpace items are represented as MPEG-21 DIDL objects. These DIDL objects are XML documents that wrap both the Dublin Core metadata that describes the DSpace item and its actual bitstreams. A bitstream is provided inline in the DIDL object in a base64 encoded manner, and/or by means of a pointer to the bitstream. The data provider exposes DIDL objects via the metadataPrefix didl.</p><p>The crosswalk does not deal with special characters and purposely skips dissemination of the <code class="literal">license.txt</code> file awaiting a better understanding on how to map DSpace rights information to MPEG21-DIDL.</p><p>The DIDL Crosswalk can be activated as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> Uncomment the <code class="literal">oai.didl.maxresponse</code> item in <code class="literal">dspace.cfg</code></p></li><li><p> Uncomment the DIDL Crosswalk entry from the <code class="literal">config/templates/oaicat.properties</code> file</p></li><li><p> Run the <code class="literal">bin/install-configs</code> script</p></li><li><p> Restart Tomcat</p></li><li><p> Verify the Crosswalk is activated by accessing a URL such as <code class="literal">http://mydspace/oai/request?verb=ListRecords&amp;metadataPrefix=didl</code></p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N124E5"></a>5.7.5.&nbsp;<a name="docbook-configure.html-packager"></a>Configuring Packager Plugins</h3></div></div></div><p>Package ingester plugins are configured as <a class="link" href="ch10.html#docbook-business.html-plugin">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.packager.PackageIngester</code>. Package disseminator plugins are configured as <a class="link" href="">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.packager.PackageDisseminator</code>.</p><p>You can add names for the existing plugins, and add new plugins, by altering these configuration properties. See the <a class="link" href="ch10.html#docbook-business.html-plugin">Plugin Manager</a> architecture for more information about plugins.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12504"></a>5.7.6.&nbsp;<a name="docbook-configure.html-crosswalk"></a>Configuring Crosswalk Plugins</h3></div></div></div><p>Ingestion crosswalk plugins are configured as <a class="link" href="ch10.html#docbook-business.html-plugin">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.crosswalk.IngestionCrosswalk</code>. Dissemination crosswalk plugins are configured as <a class="link" href="">named or self-named plugins</a> for the interface <code class="literal">org.dspace.content.crosswalk.DisseminationCrosswalk</code>.</p><p>You can add names for existing crosswalks, add new plugin classes, and add new configurations for the configurable crosswalks as noted below.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1251F"></a><a name="docbook-configure.html-mods"></a>Configurable MODS dissemination crosswalk</h4></div></div></div><p>The MODS crosswalk is a self-named plugin. To configure an instance of the MODS crosswalk, add a property to the DSpace configuration starting with <code class="literal">"crosswalk.mods.properties."</code>; the final word of the property name becomes the plugin's name. For example, a property name <code class="literal">crosswalk.mods.properties.MODS</code> defines a crosswalk plugin named <code class="literal">"MODS"</code>.</p><p>The value of this property is a path to a separate properties file containing the configuration for this crosswalk. The pathname is relative to the DSpace configuration directory, i.e. the <code class="literal">config</code> subdirectory of the DSpace install directory. So, a line like:</p><pre class="screen">
  crosswalk.mods.properties.MODS = crosswalks/mods.properties
 </pre><p> defines a crosswalk named <code class="literal">MODS</code> whose configuration comes from the file <code class="literal">[dspace]/config/crosswalks/mods.properties</code>.</p><p> The MODS crosswalk properties file is a list of properties describing how DSpace metadata elements are to be turned into elements of the MODS XML output document. The property name is a concatenation of the metadata schema, element name, and optionally the qualifier. For example, the <code class="literal">contributor.author</code> element in the native Dublin Core schema would be: <code class="literal">dc.contributor.author</code>. The value of the property is a line containing two segments separated by the vertical bar (<code class="literal">"|"</code>): The first part is an XML fragment which is copied into the output document. The second is an XPath expression describing where in that fragment to put the value of the metadata element. For example, in this property:</p><pre class="screen">
 dc.contributor.author = &lt;mods:name&gt;&lt;mods:role&gt;&lt;mods:roleTerm
@@ -914,7 +922,7 @@ dc.contributor.author = &lt;mods:name&gt;&lt;mods:role&gt;&lt;mods:roleTerm
             <code class="literal"> &lt;/mods:namePart&gt;
 	&lt;/mods:name&gt;</code>
 
-          </pre><p> into the output document. Read the example configuration file for more details. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1253D"></a><a name="docbook-configure.html-qdc"></a>Configurable Qualified Dublin Core (QDC) dissemination crosswalk</h4></div></div></div><p>The QDC crosswalk is a self-named plugin. To configure an instance of the QDC crosswalk, add a property to the DSpace configuration starting with <code class="literal">"crosswalk.qdc.properties."</code>; the final word of the property name becomes the plugin's name. For example, a property name <code class="literal">crosswalk.qdc.properties.QDC</code> defines a crosswalk plugin named <code class="literal">"QDC"</code>.</p><p>The value of this property is a path to a separate properties file containing the configuration for this crosswalk. The pathname is relative to the DSpace configuration directory, i.e. the <code class="literal">config</code> subdirectory of the DSpace install directory. So, a line like:</p><pre class="screen">
+          </pre><p> into the output document. Read the example configuration file for more details. </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12571"></a><a name="docbook-configure.html-qdc"></a>Configurable Qualified Dublin Core (QDC) dissemination crosswalk</h4></div></div></div><p>The QDC crosswalk is a self-named plugin. To configure an instance of the QDC crosswalk, add a property to the DSpace configuration starting with <code class="literal">"crosswalk.qdc.properties."</code>; the final word of the property name becomes the plugin's name. For example, a property name <code class="literal">crosswalk.qdc.properties.QDC</code> defines a crosswalk plugin named <code class="literal">"QDC"</code>.</p><p>The value of this property is a path to a separate properties file containing the configuration for this crosswalk. The pathname is relative to the DSpace configuration directory, i.e. the <code class="literal">config</code> subdirectory of the DSpace install directory. So, a line like:</p><pre class="screen">
   crosswalk.qdc.properties.QDC = crosswalks/qdc.properties
 </pre><p> defines a crosswalk named <code class="literal">QDC</code> whose configuration comes from the file <code class="literal">[dspace]/config/crosswalks/qdc.properties</code>.</p><p> You'll also need to configure the namespaces and schema location strings for the XML output generated by this crosswalk. The namespaces property names are of the format:</p><p><code class="literal">crosswalk.qdc.namespace.</code><span class="emphasis"><em>prefix</em></span> = <span class="emphasis"><em>uri</em></span></p><p> where <span class="emphasis"><em>prefix</em></span> is the namespace prefix and <span class="emphasis"><em>uri</em></span> is the namespace URI.</p><p>For example, this shows how a crosswalk named "QDC" would be configured:</p><pre class="screen">
 crosswalk.qdc.properties.QDC = crosswalks/QDC.properties
@@ -928,7 +936,7 @@ crosswalk.qdc.schemaLocation.QDC  = \
 </pre><p> the generated XML in the output document would look like,
 	e.g.: <pre class="screen">
   &lt;dcterms:temporal&gt;Fall, 2005&lt;/dcterms:temporal&gt;
-</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12591"></a>XSLT-based crosswalks</h4></div></div></div><p>The XSLT crosswalks use XSL stylesheet transformation (XSLT) to transform an XML-based external metadata format to or from DSpace's internal metadata. XSLT crosswalks are much more powerful and flexible than the configurable MODS and QDC crosswalks, but they demand some esoteric knowledge (XSL stylesheets). Given that, you can create all the crosswalks you need just by adding stylesheets and configuration lines, without touching any of the Java code.</p><p>A submission crosswalk is described by a configuration key starting with '<code class="literal">crosswalk.submission.</code>", like</p><pre class="screen">
+</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N125C5"></a>XSLT-based crosswalks</h4></div></div></div><p>The XSLT crosswalks use XSL stylesheet transformation (XSLT) to transform an XML-based external metadata format to or from DSpace's internal metadata. XSLT crosswalks are much more powerful and flexible than the configurable MODS and QDC crosswalks, but they demand some esoteric knowledge (XSL stylesheets). Given that, you can create all the crosswalks you need just by adding stylesheets and configuration lines, without touching any of the Java code.</p><p>A submission crosswalk is described by a configuration key starting with '<code class="literal">crosswalk.submission.</code>", like</p><pre class="screen">
   crosswalk.submission.<span class="emphasis"><em> PluginName</em></span>.stylesheet = <span class="emphasis"><em>
 	path</em></span>
 </pre><p> The <span class="emphasis"><em>PluginName</em></span> is, of course, the plugin's name. The <span class="emphasis"><em>path</em></span> value is the path to the file containing the crosswalk stylesheet (relative to <code class="literal">dspace.dir/config</code>).</p><p> Here is an example that configures a crosswalk named "LOM" using a stylesheet in <code class="literal">[dspace]/config/crosswalks/d-lom.xsl</code>:</p><pre class="screen">
@@ -954,7 +962,7 @@ crosswalk.qdc.schemaLocation.QDC  = \
    crosswalk.dissemination.qdc.schemaLocation = \
       http://purl.org/dc/elements/1.1/
 	http://dublincore.org/schemas/xmls/qdc/2003/04/02/qualifieddc.xsd
-</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N125F4"></a>DSpace Intermediate Metadata (DIM) format</h4></div></div></div><p> XSLT crosswalk plugins translate between the external metadata format and an XML format called <span class="emphasis"><em>DSpace Intermediate Metadata</em></span>, which exists <span class="emphasis"><em>only</em></span> for the purpose of XSLT crosswalks. It is <span class="emphasis"><em>never</em></span> to be exported from DSpace, since it is not an acknowledged metadata format, it is simply an expression of the way DSpace stores its metadata fields internally.  All the elements in a DIM document are in the namespace <code class="literal">http://www.dspace.org/xmlns/dspace/dim</code>.</p><p>The root element is named <code class="literal">dim</code>. It has zero or more children, all <code class="literal">field</code> elements. It may have an attribute <code class="literal">dspaceType</code>, which identifies the type of object ("ITEM", "COLLECTION", or "COMMUNITY") this metadata describes. This attribute is only guaranteed to be set for dissemination crosswalks.</p><p>Each <code class="literal">field</code> element may have the following attributes:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">mdschema</code>  (Required) The metadata schema, e.g. <code class="literal">"dc"</code>.</p></li><li><p><code class="literal">element</code>  (Required) Element name, such as "contributor".</p></li><li><p><code class="literal">qualifier</code>  Qualifier name, such as "author".</p></li><li><p><code class="literal">lang</code>  Language code describing language of this entry.</p></li></ul></div><p> The value of <code class="literal">field</code> is the value of that metadata field. Fields with the same qualifiers may be repeated.  Here is an example of the DIM format:</p><pre class="screen">
+</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12628"></a>DSpace Intermediate Metadata (DIM) format</h4></div></div></div><p> XSLT crosswalk plugins translate between the external metadata format and an XML format called <span class="emphasis"><em>DSpace Intermediate Metadata</em></span>, which exists <span class="emphasis"><em>only</em></span> for the purpose of XSLT crosswalks. It is <span class="emphasis"><em>never</em></span> to be exported from DSpace, since it is not an acknowledged metadata format, it is simply an expression of the way DSpace stores its metadata fields internally.  All the elements in a DIM document are in the namespace <code class="literal">http://www.dspace.org/xmlns/dspace/dim</code>.</p><p>The root element is named <code class="literal">dim</code>. It has zero or more children, all <code class="literal">field</code> elements. It may have an attribute <code class="literal">dspaceType</code>, which identifies the type of object ("ITEM", "COLLECTION", or "COMMUNITY") this metadata describes. This attribute is only guaranteed to be set for dissemination crosswalks.</p><p>Each <code class="literal">field</code> element may have the following attributes:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">mdschema</code>  (Required) The metadata schema, e.g. <code class="literal">"dc"</code>.</p></li><li><p><code class="literal">element</code>  (Required) Element name, such as "contributor".</p></li><li><p><code class="literal">qualifier</code>  Qualifier name, such as "author".</p></li><li><p><code class="literal">lang</code>  Language code describing language of this entry.</p></li></ul></div><p> The value of <code class="literal">field</code> is the value of that metadata field. Fields with the same qualifiers may be repeated.  Here is an example of the DIM format:</p><pre class="screen">
     &lt;dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim"
 	dspaceType="ITEM"&gt;
       &lt;dim:field mdschema="dc" element="title"
@@ -977,11 +985,11 @@ crosswalk.qdc.schemaLocation.QDC  = \
         Boston University Department of Biochemistry
       &lt;/dim:field&gt;
     &lt;/dim:dim&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12641"></a>Testing XSLT Crosswalks</h4></div></div></div><p> The XSLT crosswalks will automatically reload an XSL stylesheet that has been modified, so you can edit and test stylesheets without restarting DSpace.  You can test a dissemination crosswalk by hooking it up to an OAI-PMH crosswalk and using an OAI request to get the metadata for a known item.</p><p>Testing the submission crosswalk is more difficult, so we have supplied a command-line utility to help. It calls the crosswalk plugin to translate an XML document you submit, and displays the resulting intermediate XML (DIM). Invoke it with:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12675"></a>Testing XSLT Crosswalks</h4></div></div></div><p> The XSLT crosswalks will automatically reload an XSL stylesheet that has been modified, so you can edit and test stylesheets without restarting DSpace.  You can test a dissemination crosswalk by hooking it up to an OAI-PMH crosswalk and using an OAI request to get the metadata for a known item.</p><p>Testing the submission crosswalk is more difficult, so we have supplied a command-line utility to help. It calls the crosswalk plugin to translate an XML document you submit, and displays the resulting intermediate XML (DIM). Invoke it with:</p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/dsrun
 	org.dspace.content.crosswalk.XSLTIngestionCrosswalk [-l] <span class="emphasis"><em> plugin
 	input-file</em></span>
-</pre><p> ..where <span class="emphasis"><em>plugin</em></span> is the name of the crosswalk plugin to test (e.g. "LOM"), and <span class="emphasis"><em>input-file</em></span> is a file containing an XML document of metadata in the appropriate format.</p><p> Add the <code class="literal">-l</code> option to to pass the ingestion crosswalk a list of elements instead of a whole document, as if the List form of the ingest() method had been called. This is needed to test ingesters for formats like DC that get called with lists of elements instead of a root element.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12660"></a>5.7.7.&nbsp;<a name="docbook-configure.html-mediafilters"></a>Creating a new Media/Format Filter</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12667"></a>Creating a simple Media Filter</h4></div></div></div><p>New Media Filters <span class="bold"><strong>must implement</strong></span> the <code class="literal">org.dspace.app.mediafilter.FormatFilter</code> interface. More information on the methods you need to implement is provided in the <code class="literal">FormatFilter.java</code> source file. For example:</p><pre class="screen">
+</pre><p> ..where <span class="emphasis"><em>plugin</em></span> is the name of the crosswalk plugin to test (e.g. "LOM"), and <span class="emphasis"><em>input-file</em></span> is a file containing an XML document of metadata in the appropriate format.</p><p> Add the <code class="literal">-l</code> option to to pass the ingestion crosswalk a list of elements instead of a whole document, as if the List form of the ingest() method had been called. This is needed to test ingesters for formats like DC that get called with lists of elements instead of a root element.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12694"></a>5.7.7.&nbsp;<a name="docbook-configure.html-mediafilters"></a>Creating a new Media/Format Filter</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1269B"></a>Creating a simple Media Filter</h4></div></div></div><p>New Media Filters <span class="bold"><strong>must implement</strong></span> the <code class="literal">org.dspace.app.mediafilter.FormatFilter</code> interface. More information on the methods you need to implement is provided in the <code class="literal">FormatFilter.java</code> source file. For example:</p><pre class="screen">
 
             <code class="literal"> public class MySimpleMediaFilter implements
 	FormatFilter</code>
@@ -991,7 +999,7 @@ crosswalk.qdc.schemaLocation.QDC  = \
             <code class="literal"> public class MySimpleMediaFilter extends
 	MediaFilter</code>
 
-          </pre><p>You must give your new filter a "name", by adding it and its name to the <code class="literal">plugin.named.org.dspace.app.mediafilter.FormatFilter</code> field in <code class="literal">dspace.cfg</code>. In addition to naming your filter, make sure to specify its input formats in the <code class="literal">filter.&lt;class path&gt;.inputFormats</code> config item. Note the input formats must match the <code class="literal">short description</code> field in the <a class="ulink" href="appendix.html#bitstreamformatregistry" target="_top">Bitstream Format Registry</a> (i.e. <code class="literal">bitstreamformatregistry</code> table).</p><pre class="screen">
+          </pre><p>You must give your new filter a "name", by adding it and its name to the <code class="literal">plugin.named.org.dspace.app.mediafilter.FormatFilter</code> field in <code class="literal">dspace.cfg</code>. In addition to naming your filter, make sure to specify its input formats in the <code class="literal">filter.&lt;class path&gt;.inputFormats</code> config item. Note the input formats must match the <code class="literal">short description</code> field in the <a class="link" href="ch15.html#docbook-appendix.html-bitstreamformatregistry">Bitstream Format Registry</a> (i.e. <code class="literal">bitstreamformatregistry</code> table).</p><pre class="screen">
 
             <code class="literal"> plugin.named.org.dspace.app.mediafilter.FormatFilter = \
 	org.dspace.app.mediafilter.MySimpleMediaFilter = My Simple Text
@@ -1001,7 +1009,7 @@ crosswalk.qdc.schemaLocation.QDC  = \
 
           </pre><p>
             <span class="emphasis"><em>WARNING: If you neglect to define the <code class="literal">inputFormats</code> for a particular filter, the <code class="literal">MediaFilterManager</code> will never call that filter, since it will never find a bitstream which has a format matching that filter's input format(s).</em></span>
-          </p><p>If you have a complex Media Filter class, which actually performs different filtering for different formats (e.g. conversion from Word to PDF <span class="bold"><strong>and</strong></span> conversion from Excel to CSV), you should define this as a <a class="ulink" href="selfnamedfilter" target="_top">Dynamic / Self-Named Format Filter</a>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N126C5"></a>Creating a Dynamic or "Self-Named" Format Filter</h4></div></div></div><p>If you have a more complex Media/Format Filter, which actually performs <span class="bold"><strong>multiple</strong></span> filtering or conversions for different formats (e.g. conversion from Word to PDF <span class="bold"><strong>and</strong></span> conversion from Excel to CSV), you should have define a class which implements the <code class="literal">FormatFilter</code> interface, while also extending the <a class="ulink" href="business.html#selfnamedplugin" target="_top">
+          </p><p>If you have a complex Media Filter class, which actually performs different filtering for different formats (e.g. conversion from Word to PDF <span class="bold"><strong>and</strong></span> conversion from Excel to CSV), you should define this as a <a class="ulink" href="selfnamedfilter" target="_top">Dynamic / Self-Named Format Filter</a>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N126F9"></a>Creating a Dynamic or "Self-Named" Format Filter</h4></div></div></div><p>If you have a more complex Media/Format Filter, which actually performs <span class="bold"><strong>multiple</strong></span> filtering or conversions for different formats (e.g. conversion from Word to PDF <span class="bold"><strong>and</strong></span> conversion from Excel to CSV), you should have define a class which implements the <code class="literal">FormatFilter</code> interface, while also extending the <a class="ulink" href="business.html#selfnamedplugin" target="_top">
               <code class="literal">SelfNamedPlugin</code>
             </a>
  class. For example:</p><pre class="screen">
@@ -1009,7 +1017,7 @@ crosswalk.qdc.schemaLocation.QDC  = \
             <code class="literal"> public class MyComplexMediaFilter extends
 	SelfNamedPlugin implements FormatFilter</code>
 
-          </pre><p>Since <code class="literal">SelfNamedPlugins</code> are self-named (as stated), they must provide the various names the plugin uses by defining a <a class="ulink" href="business.html#pluginmethods" target="_top">getPluginNames()</a> method. Generally speaking, each "name" the plugin uses should correspond to a different type of filter it implements (e.g. "Word2PDF" and "Excel2CSV" are two good names for a complex media filter which performs both Word to PDF and Excel to CSV conversions).</p><p>Self-Named Media/Format Filters are also configured differently in <code class="literal">dspace.cfg</code>. Below is a general template for a Self Named Filter (defined by an imaginary <code class="literal">MyComplexMediaFilter</code> class, which can perform both Word to PDF and Excel to CSV conversions):</p><pre class="screen">
+          </pre><p>Since <code class="literal">SelfNamedPlugins</code> are self-named (as stated), they must provide the various names the plugin uses by defining a <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getPluginNames()</a> method. Generally speaking, each "name" the plugin uses should correspond to a different type of filter it implements (e.g. "Word2PDF" and "Excel2CSV" are two good names for a complex media filter which performs both Word to PDF and Excel to CSV conversions).</p><p>Self-Named Media/Format Filters are also configured differently in <code class="literal">dspace.cfg</code>. Below is a general template for a Self Named Filter (defined by an imaginary <code class="literal">MyComplexMediaFilter</code> class, which can perform both Word to PDF and Excel to CSV conversions):</p><pre class="screen">
 
             <code class="literal"> #Add to a list of all Self Named filters
 	plugin.selfnamed.org.dspace.app.mediafilter.FormatFilter = \
@@ -1036,13 +1044,13 @@ tFormat = Comma Separated Values</code>
 	"." + MyComplexMediaFilter.class.getName() + "." +
 	this.getPluginInstanceName() + ".outputFormat");</code>
 
-          </pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12764"></a>5.7.8.&nbsp;<a name="docbook-configure.html-templates"></a>Configuration Files for Other Applications</h3></div></div></div><p>To ease the hassle of keeping configuration files for other applications involved in running a DSpace site, for example Apache, in sync, the DSpace system can automatically update them for you when the main DSpace configuration is changed. This feature of the DSpace system is entirely optional, but we found it useful.</p><p>The way this is done is by placing the configuration files for those applications in <code class="literal">[dspace]/config/templates</code>, and inserting special values in the configuration file that will be filled out with appropriate DSpace configuration properties. Then, tell DSpace where to put filled-out, 'live' version of the configuration by adding an appropriate property to <code class="literal">dspace.cfg</code>, and run <code class="literal">[dspace]/bin/install-configs</code>.</p><p>Take the <code class="literal">apache13.conf</code> file as an example. This contains plenty of Apache-specific stuff, but where it uses a value that should be kept in sync across DSpace and associated applications, a 'placeholder' value is written. For example, the host name:</p><pre class="screen">
+          </pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12798"></a>5.7.8.&nbsp;<a name="docbook-configure.html-templates"></a>Configuration Files for Other Applications</h3></div></div></div><p>To ease the hassle of keeping configuration files for other applications involved in running a DSpace site, for example Apache, in sync, the DSpace system can automatically update them for you when the main DSpace configuration is changed. This feature of the DSpace system is entirely optional, but we found it useful.</p><p>The way this is done is by placing the configuration files for those applications in <code class="literal">[dspace]/config/templates</code>, and inserting special values in the configuration file that will be filled out with appropriate DSpace configuration properties. Then, tell DSpace where to put filled-out, 'live' version of the configuration by adding an appropriate property to <code class="literal">dspace.cfg</code>, and run <code class="literal">[dspace]/bin/install-configs</code>.</p><p>Take the <code class="literal">apache13.conf</code> file as an example. This contains plenty of Apache-specific stuff, but where it uses a value that should be kept in sync across DSpace and associated applications, a 'placeholder' value is written. For example, the host name:</p><pre class="screen">
 ServerName @@dspace.hostname@@
 </pre><p>The text <code class="literal">@@dspace.hostname@@</code> will be filled out with the value of the <code class="literal">dspace.hostname</code> property in <code class="literal">dspace.cfg</code>. Then we decide where we want the 'live' version, that is, the version actually read in by Apache when it starts up, will go.</p><p>Let's say we want the live version to be located at <code class="literal">/opt/apache/conf/dspace-httpd.conf</code>. To do this, we add the following property to <code class="literal">dspace.cfg</code> so DSpace knows where to put it:</p><pre class="screen">
 config.template.apache13.conf = /opt/apache/conf/dspace-httpd.conf
 </pre><p>Now, we run <code class="literal">[dspace]/bin/install-configs</code>. This reads in <code class="literal">[dspace]/config/templates/apache13.conf</code>, and places a copy at <code class="literal">/opt/apache/conf/dspace-httpd.conf</code> with the placeholders filled out.</p><p>So, in <code class="literal">/opt/apache/conf/dspace-httpd.conf</code>, there will be a line like:</p><pre class="screen">
 ServerName dspace.myu.edu
-</pre><p>The advantage of this approach is that if a property like the hostname changes, you can just change it in <code class="literal">dspace.cfg</code> and run <code class="literal">install-configs</code>, and all of your tools' configuration files will be updated.</p><p>However, take care to make all your edits to the versions in <code class="literal">[dspace]/config/templates</code>! It's a wise idea to put a big reminder at the top of each file, since someone might unwittingly edit a 'live' configuration file which would later be overwritten.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N127C6"></a>5.7.9.&nbsp;<a name="docbook-configure.html-browse-index"></a>Browse Index Creation</h3></div></div></div><p>To create all the various browse indices that you define in the configuration as described in the section <a name="docbook-configure.html--browse"></a>Browse Configuration there are a variety of options available to you. You can see these options at any time by running the indexer without any arguments, thus:</p><pre class="screen">
+</pre><p>The advantage of this approach is that if a property like the hostname changes, you can just change it in <code class="literal">dspace.cfg</code> and run <code class="literal">install-configs</code>, and all of your tools' configuration files will be updated.</p><p>However, take care to make all your edits to the versions in <code class="literal">[dspace]/config/templates</code>! It's a wise idea to put a big reminder at the top of each file, since someone might unwittingly edit a 'live' configuration file which would later be overwritten.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N127FA"></a>5.7.9.&nbsp;<a name="docbook-configure.html-browse-index"></a>Browse Index Creation</h3></div></div></div><p>To create all the various browse indices that you define in the configuration as described in the section <a name="docbook-configure.html--browse"></a>Browse Configuration there are a variety of options available to you. You can see these options at any time by running the indexer without any arguments, thus:</p><pre class="screen">
 [dspace]/bin/dsrun org.dspace.browse.IndexBrowse
 </pre><p>This will show you the following options are available to you:</p><div class="variablelist"><dl><dt><span class="term">-r,--rebuild</span></dt><dd><p>should we rebuild all the indices, which removes old index tables and creates new ones. For use with -f. Mutually exclusive with -d</p></dd><dt><span class="term">-s,--start</span></dt><dd><p>[-s &lt;int&gt;] start from this index number and work upward (mostly only useful for debugging). For use with -t and -f</p></dd><dt><span class="term">-x,--execute</span></dt><dd><p>execute all the remove and create SQL against the database. For use with -t and -f</p></dd><dt><span class="term">-i,--index</span></dt><dd><p>actually do the indexing. Mutually exclusive with -t and -f</p></dd><dt><span class="term">-o,--out</span></dt><dd><p>[-o &lt;filename&gt;] write the remove and create SQL to the given file. For use with -t and -f</p></dd><dt><span class="term">-p,--print</span></dt><dd><p>write the remove and create SQL to the stdout. For use with -t and -f</p></dd><dt><span class="term">-t,--tables</span></dt><dd><p>create the tables only, do not attempt to index. Mutually exclusive with -f and -i</p></dd><dt><span class="term">-f,--full</span></dt><dd><p>make the tables, and do the indexing. This forces -x. Mutually exclusive with -t and -i</p></dd><dt><span class="term">-v,--verbose</span></dt><dd><p>print extra information to the stdout. If used in conjunction with -p, you cannot use the stdout to generate your database structure</p></dd><dt><span class="term">-d,--delete</span></dt><dd><p>delete all the indices, but don't create new ones. For use with -f. This is mutually exclusive with -r</p></dd><dt><span class="term">-h,--help</span></dt><dd><p>show this help documentation. Overrides all other arguments</p></dd></dl></div><p>The following, then, are examples of what you want to achieve and how this is done with the command line options</p><p>
           <span class="emphasis"><em>Do a full browse re-index, tearing down all old tables and reconstructing with the new configuration</em></span>
@@ -1059,7 +1067,26 @@ ServerName dspace.myu.edu
 ant index
 </pre><p>This creates the index tables as per the configuration, and will produce your initial indexed state. From this point on, you should not use ant to generate your indices, as it is not a very good execution environment. Instead, if you feel the need, or your local customisations demand regular full indexing you should set up a regular script to execute:</p><pre class="screen">
 [dspace]/bin/dsrun org.dspace.browse.IndexBrowse -i
-</pre></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12873"></a>5.7.10.&nbsp;
+      		<a name="docbook-configure.html-usage-instrumentation"></a>Configuring Usage Instrumentation Plugins</h3></div></div></div><p>A usage instrumentation plugin is configured as a
+				<a class="link" href="ch10.html#docbook-business.html-plugin">singleton plugin</a>
+				for the abstract class <code class="code">org.dspace.app.statistics.AbstractUsageEvent</code>.
+			</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12884"></a>
+					<a name="docbook-configure.html-usage-insturmentation-passive"></a>
+					The Passive Plugin
+				</h4></div></div></div><p>
+					The Passive plugin is provided as the class <code class="code">org.dspace.app.statistics.PassiveUsageEvent</code>.  It absorbs events without effect.  Use the Passive plugin when you have no use for usage event postings.  This is the default if no plugin is configured.
+				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12891"></a>
+					<a name="docbook-configure.html-usage-instrumentation-tsv"></a>
+					The Tab File Logger Plugin
+				</h4></div></div></div><p>
+					The Tab File Logger plugin is provided as the class <code class="code">org.dspace.app.statistics.UsageEventTabFileLogger</code>.  It writes event records to a file in tab-separated column format.  If left unconfigured, an error will be noted in the DSpace log and no file will be produced.  To specify the file path, provide an absolute path as the value for <code class="code">usageEvent.tabFileLogger.file</code> in <code class="code">dspace.cfg</code>.
+				</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N128A4"></a>
+					<a name="docbook-configure.html-usage-instrumentation-xml"></a>
+					The XML Logger Plugin
+				</h4></div></div></div><p>
+					The XML Logger plugin is provided as the class <code class="code">org.dspace.app.statistics.UsageEventXMLLogger</code>.  It writes event records to a file in a simple XML-like format.  If left unconfigured, an error will be noted in the DSpace log and no file will be produced.  To specify the file path, provide an absolute path as the value for <code class="code">usageEvent.xmlLogger.file</code> in <code class="code">dspace.cfg</code>.
+				</p></div></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch06.html b/dspace/docs/html/ch06.html
index 98a286ab22..04ac556f91 100644
--- a/dspace/docs/html/ch06.html
+++ b/dspace/docs/html/ch06.html
@@ -1,8 +1,8 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch05.html" title="Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization"><link rel="next" href="ch07.html" title="Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch05.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch07.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N1283F"></a>Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch06.html#N12849">6.1. RDBMS</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N128D4">6.1.1. Maintenance and Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N1290D">6.1.2. Configuring the RDBMS Component</a></span></dt></dl></dd><dt><span class="section"><a href="ch06.html#N12962">6.2. Bitstream Store</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N12A59">6.2.1. Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N12A6D">6.2.2. Configuring the Bitstream Store</a></span></dt></dl></dd></dl></div><p>
-      <a class="ulink" href="architecture.html" target="_top">Back to architecture overview</a>
-    </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12849"></a>6.1.&nbsp;<a name="docbook-storage.html-rdbms"></a>RDBMS</h2></div></div></div><p>DSpace uses a relational database to store all information about the organization of content, metadata about the content, information about e-people and authorization, and the state of currently-running workflows. The DSpace system also uses the relational database in order to maintain indices that users can browse.</p><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch05.html" title="Chapter&nbsp;5.&nbsp;DSpace System Documentation: Configuration and Customization"><link rel="next" href="ch07.html" title="Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch05.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch07.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N128B7"></a>Chapter&nbsp;6.&nbsp;<a name="docbook-storage.html"></a>DSpace System Documentation: Storage Layer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch06.html#N128C3">6.1. RDBMS</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N1294E">6.1.1. Maintenance and Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N12987">6.1.2. Configuring the RDBMS Component</a></span></dt></dl></dd><dt><span class="section"><a href="ch06.html#N129DC">6.2. Bitstream Store</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N12AD3">6.2.1. Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N12AE7">6.2.2. Configuring the Bitstream Store</a></span></dt></dl></dd></dl></div><p>
+      <a class="link" href="ch08.html#docbook-architecture.html">Back to architecture overview</a>
+    </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N128C3"></a>6.1.&nbsp;<a name="docbook-storage.html-rdbms"></a>RDBMS</h2></div></div></div><p>DSpace uses a relational database to store all information about the organization of content, metadata about the content, information about e-people and authorization, and the state of currently-running workflows. The DSpace system also uses the relational database in order to maintain indices that users can browse.</p><p>
         <a class="ulink" href="image/db-schema.gif" target="_top">Graphical visualization of the relational database</a>
-      </p><p>Most of the functionality that DSpace uses can be offered by any standard SQL database that supports transactions. Presently, the browse indices use some features specific to <a class="ulink" href="http://www.postgresql.org/" target="_top">PostgreSQL</a> and <a class="ulink" href="http://www.oracle.com/database/" target="_top">Oracle</a>, so some modification to the code would be needed before DSpace would function fully with an alternative database back-end.</p><p>The <code class="literal">org.dspace.storage.rdbms</code> package provides access to an SQL database in a somewhat simpler form than using JDBC directly. The main class is <code class="literal">DatabaseManager</code>, which executes SQL queries and returns <code class="literal">TableRow</code> or <code class="literal">TableRowIterator</code> objects. The <code class="literal">InitializeDatabase</code> class is used to load SQL into the database via JDBC, for example to set up the schema.</p><p>All calls to the <code class="literal">Database Manager</code> require a <a class="ulink" href="business.html#core" target="_top">DSpace <code class="literal">Context</code> object</a>. Example use of the database manager API is given in the <code class="literal">org.dspace.storage.rdbms</code> package Javadoc.</p><p>The database schema used by DSpace (for PostgreSQL) is stored in <code class="literal">[dspace-source]/dspace/etc/database_schema.sql</code> in the source distribution. It is stored in the form of SQL that can be fed straight into the DBMS to construct the database. The schema SQL file also directly creates two e-person groups in the database that are required for the system to function properly.</p><p>Also in <code class="literal">[dspace-source]/dspace/etc</code> are various SQL files called <code class="literal">database_schema_1x_1y</code>. These contain the necessary SQL commands to update a live DSpace database from version 1.<code class="literal">x</code> to 1.<code class="literal">y</code>. Note that this might not be the only part of an upgrade process: see <a class="ulink" href="update.html" target="_top">Updating a DSpace Installation</a> for details.</p><p>The DSpace database code uses an SQL function <code class="literal">getnextid</code> to assign primary keys to newly created rows. This SQL function must be safe to use if several JVMs are accessing the database at once; for example, the Web UI might be creating new rows in the database at the same time as the batch item importer. The PostgreSQL-specific implementation of the method uses <code class="literal">SEQUENCES</code> for each table in order to create new IDs. If an alternative database backend were to be used, the implementation of <code class="literal">getnextid</code> could be updated to operate with that specific DBMS.</p><p>The <code class="literal">etc</code> directory in the source distribution contains two further SQL files. <code class="literal">clean-database.sql</code> contains the SQL necessary to completely clean out the database, so use with caution! The Ant target <code class="literal">clean_database</code> can be used to execute this. <code class="literal">update-sequences.sql</code> contains SQL to reset the primary key generation sequences to appropriate values. You'd need to do this if, for example, you're restoring a backup database dump which creates rows with specific primary keys already defined. In such a case, the sequences would allocate primary keys that were already used.</p><p>Versions of the <code class="literal">*.sql*</code> files for Oracle are stored in <code class="literal">[dspace-source]/dspace/etc/oracle</code>. These need to be copied over their PostgreSQL counterparts in <code class="literal">[dspace-source]/dspace/etc</code> prior to installation.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N128D4"></a>6.1.1.&nbsp;Maintenance and Backup</h3></div></div></div><p>When using PostgreSQL, it's a good idea to perform regular 'vacuuming' of the database to optimize performance. This is performed by the <code class="literal">vacuumdb</code> command which can be executed via a 'cron' job, for example by putting this in the system <code class="literal">crontab</code>:</p><pre class="screen">
+      </p><p>Most of the functionality that DSpace uses can be offered by any standard SQL database that supports transactions. Presently, the browse indices use some features specific to <a class="ulink" href="http://www.postgresql.org/" target="_top">PostgreSQL</a> and <a class="ulink" href="http://www.oracle.com/database/" target="_top">Oracle</a>, so some modification to the code would be needed before DSpace would function fully with an alternative database back-end.</p><p>The <code class="literal">org.dspace.storage.rdbms</code> package provides access to an SQL database in a somewhat simpler form than using JDBC directly. The main class is <code class="literal">DatabaseManager</code>, which executes SQL queries and returns <code class="literal">TableRow</code> or <code class="literal">TableRowIterator</code> objects. The <code class="literal">InitializeDatabase</code> class is used to load SQL into the database via JDBC, for example to set up the schema.</p><p>All calls to the <code class="literal">Database Manager</code> require a <a class="link" href="ch10.html#docbook-business.html-core">DSpace <code class="literal">Context</code> object</a>. Example use of the database manager API is given in the <code class="literal">org.dspace.storage.rdbms</code> package Javadoc.</p><p>The database schema used by DSpace (for PostgreSQL) is stored in <code class="literal">[dspace-source]/dspace/etc/database_schema.sql</code> in the source distribution. It is stored in the form of SQL that can be fed straight into the DBMS to construct the database. The schema SQL file also directly creates two e-person groups in the database that are required for the system to function properly.</p><p>Also in <code class="literal">[dspace-source]/dspace/etc</code> are various SQL files called <code class="literal">database_schema_1x_1y</code>. These contain the necessary SQL commands to update a live DSpace database from version 1.<code class="literal">x</code> to 1.<code class="literal">y</code>. Note that this might not be the only part of an upgrade process: see <a class="link" href="ch04.html#docbook-update.html">Updating a DSpace Installation</a> for details.</p><p>The DSpace database code uses an SQL function <code class="literal">getnextid</code> to assign primary keys to newly created rows. This SQL function must be safe to use if several JVMs are accessing the database at once; for example, the Web UI might be creating new rows in the database at the same time as the batch item importer. The PostgreSQL-specific implementation of the method uses <code class="literal">SEQUENCES</code> for each table in order to create new IDs. If an alternative database backend were to be used, the implementation of <code class="literal">getnextid</code> could be updated to operate with that specific DBMS.</p><p>The <code class="literal">etc</code> directory in the source distribution contains two further SQL files. <code class="literal">clean-database.sql</code> contains the SQL necessary to completely clean out the database, so use with caution! The Ant target <code class="literal">clean_database</code> can be used to execute this. <code class="literal">update-sequences.sql</code> contains SQL to reset the primary key generation sequences to appropriate values. You'd need to do this if, for example, you're restoring a backup database dump which creates rows with specific primary keys already defined. In such a case, the sequences would allocate primary keys that were already used.</p><p>Versions of the <code class="literal">*.sql*</code> files for Oracle are stored in <code class="literal">[dspace-source]/dspace/etc/oracle</code>. These need to be copied over their PostgreSQL counterparts in <code class="literal">[dspace-source]/dspace/etc</code> prior to installation.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1294E"></a>6.1.1.&nbsp;Maintenance and Backup</h3></div></div></div><p>When using PostgreSQL, it's a good idea to perform regular 'vacuuming' of the database to optimize performance. This is performed by the <code class="literal">vacuumdb</code> command which can be executed via a 'cron' job, for example by putting this in the system <code class="literal">crontab</code>:</p><pre class="screen">
 # clean up the database nightly
 40 2 * * * /usr/local/pgsql/bin/vacuumdb --analyze dspace &gt; /dev/null
 	2&gt;&amp;1
@@ -13,7 +13,7 @@ DELETE FROM epersongroup;
 </pre></li><li><p> After restoring a backup, you will need to reset the primary key generation sequences so that they do not produce already-used primary keys. Do this by executing the SQL in <code class="literal">[dspace-source]/dspace/etc/update-sequences.sql</code>, for example with:</p><pre class="screen">
 psql -U dspace -f <span class="emphasis"><em>
 	[dspace-source]</em></span>/dspace/etc/update-sequences.sql
-</pre></li></ul></div><p>Future updates of DSpace may involve minor changes to the database schema. Specific instructions on how to update the schema whilst keeping live data will be included. The current schema also contains a few currently unused database columns, to be used for extra functionality in future releases. These unused columns have been added in advance to minimize the effort required to upgrade.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1290D"></a>6.1.2.&nbsp;Configuring the RDBMS Component</h3></div></div></div><p>The database manager is configured with the following properties in <code class="literal">dspace.cfg</code>:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+</pre></li></ul></div><p>Future updates of DSpace may involve minor changes to the database schema. Specific instructions on how to update the schema whilst keeping live data will be included. The current schema also contains a few currently unused database columns, to be used for extra functionality in future releases. These unused columns have been added in advance to minimize the effort required to upgrade.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12987"></a>6.1.2.&nbsp;Configuring the RDBMS Component</h3></div></div></div><p>The database manager is configured with the following properties in <code class="literal">dspace.cfg</code>:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>
                     <code class="literal">db.url</code>
                   </p>
@@ -37,7 +37,7 @@ psql -U dspace -f <span class="emphasis"><em>
                   </p>
                 </td><td>
                   <p>Corresponding password ot use when accessing the database.</p>
-                </td></tr></tbody></table></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12962"></a>6.2.&nbsp;<a name="docbook-storage.html-bitstreams"></a>Bitstream Store</h2></div></div></div><p>DSpace offers two means for storing content. The first is in the file system on the server. The second is using <a class="ulink" href="http://www.sdsc.edu/srb" target="_top">SRB (Storage Resource Broker)</a>. Both are achieved using a simple, lightweight API.</p><p>SRB is purely an option but may be used in lieu of the server's file system or in addition to the file system. Without going into a full description, SRB is a very robust, sophisticated storage manager that offers essentially unlimited storage and straightforward means to replicate (in simple terms, backup) the content on other local or remote storage resources.</p><p>The terms "store", "retrieve", "in the system", "storage", and so forth, used below can refer to storage in the file system on the server ("traditional") or in SRB.</p><p>The <code class="literal">BitstreamStorageManager</code> provides low-level access to bitstreams stored in the system. In general, it should not be used directly; instead, use the <code class="literal">Bitstream</code> object in the <a class="ulink" href="business.html#content" target="_top">content management API</a> since that encapsulated authorization and other metadata to do with a bitstream that are not maintained by the <code class="literal">BitstreamStorageManager</code>.</p><p>The bitstream storage manager provides three methods that store, retrieve and delete bitstreams. Bitstreams are referred to by their 'ID'; that is the primary key <code class="literal">bitstream_id</code> column of the corresponding row in the database.</p><p>As of DSpace version 1.1, there can be multiple bitstream stores. Each of these bitstream stores can be traditional storage or SRB storage. This means that the potential storage of a DSpace system is not bound by the maximum size of a single disk or file system and also that traditional and SRB storage can be combined in one DSpace installation. Both traditional and SRB storage are specified by <a class="ulink" href="configure.html" target="_top">configuration parameters</a>. Also see Configuring the Bitstream Store below.</p><p>Stores are numbered, starting with zero, then counting upwards. Each bitstream entry in the database has a store number, used to retrieve the bitstream when required.</p><p>At the moment, the store in which new bitstreams are placed is decided using a configuration parameter, and there is no provision for moving bitstreams between stores. Administrative tools for manipulating bitstreams and stores will be provided in future releases. Right now you can move a whole store (e.g. you could move store number 1 from <code class="literal">/localdisk/store</code> to <code class="literal">/fs/anotherdisk/store</code> but it would still have to be store number 1 and have the exact same contents.</p><p>Bitstreams also have an 38-digit internal ID, different from the primary key ID of the bitstream table row. This is not visible or used outside of the bitstream storage manager. It is used to determine the exact location (relative to the relevant store directory) that the bitstream is stored in traditional or SRB storage. The first three pairs of digits are the directory path that the bitstream is stored under. The bitstream is stored in a file with the internal ID as the filename.</p><p>For example, a bitstream with the internal ID <code class="literal">12345678901234567890123456789012345678</code> is stored in the directory:</p><pre class="screen">
+                </td></tr></tbody></table></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N129DC"></a>6.2.&nbsp;<a name="docbook-storage.html-bitstreams"></a>Bitstream Store</h2></div></div></div><p>DSpace offers two means for storing content. The first is in the file system on the server. The second is using <a class="ulink" href="http://www.sdsc.edu/srb" target="_top">SRB (Storage Resource Broker)</a>. Both are achieved using a simple, lightweight API.</p><p>SRB is purely an option but may be used in lieu of the server's file system or in addition to the file system. Without going into a full description, SRB is a very robust, sophisticated storage manager that offers essentially unlimited storage and straightforward means to replicate (in simple terms, backup) the content on other local or remote storage resources.</p><p>The terms "store", "retrieve", "in the system", "storage", and so forth, used below can refer to storage in the file system on the server ("traditional") or in SRB.</p><p>The <code class="literal">BitstreamStorageManager</code> provides low-level access to bitstreams stored in the system. In general, it should not be used directly; instead, use the <code class="literal">Bitstream</code> object in the <a class="link" href="ch10.html#docbook-business.html-content">content management API</a> since that encapsulated authorization and other metadata to do with a bitstream that are not maintained by the <code class="literal">BitstreamStorageManager</code>.</p><p>The bitstream storage manager provides three methods that store, retrieve and delete bitstreams. Bitstreams are referred to by their 'ID'; that is the primary key <code class="literal">bitstream_id</code> column of the corresponding row in the database.</p><p>As of DSpace version 1.1, there can be multiple bitstream stores. Each of these bitstream stores can be traditional storage or SRB storage. This means that the potential storage of a DSpace system is not bound by the maximum size of a single disk or file system and also that traditional and SRB storage can be combined in one DSpace installation. Both traditional and SRB storage are specified by <a class="link" href="ch05.html#docbook-configure.html">configuration parameters</a>. Also see Configuring the Bitstream Store below.</p><p>Stores are numbered, starting with zero, then counting upwards. Each bitstream entry in the database has a store number, used to retrieve the bitstream when required.</p><p>At the moment, the store in which new bitstreams are placed is decided using a configuration parameter, and there is no provision for moving bitstreams between stores. Administrative tools for manipulating bitstreams and stores will be provided in future releases. Right now you can move a whole store (e.g. you could move store number 1 from <code class="literal">/localdisk/store</code> to <code class="literal">/fs/anotherdisk/store</code> but it would still have to be store number 1 and have the exact same contents.</p><p>Bitstreams also have an 38-digit internal ID, different from the primary key ID of the bitstream table row. This is not visible or used outside of the bitstream storage manager. It is used to determine the exact location (relative to the relevant store directory) that the bitstream is stored in traditional or SRB storage. The first three pairs of digits are the directory path that the bitstream is stored under. The bitstream is stored in a file with the internal ID as the filename.</p><p>For example, a bitstream with the internal ID <code class="literal">12345678901234567890123456789012345678</code> is stored in the directory:</p><pre class="screen">
 (assetstore dir)/12/34/56/12345678901234567890123456789012345678
 </pre><p>The reasons for storing files this way are:</p><div class="itemizedlist"><ul type="disc"><li><p> Using a randomly-generated 38-digit number means that the 'number space' is less cluttered than simply using the primary keys, which are allocated sequentially and are thus close together. This means that the bitstreams in the store are distributed around the directory structure, improving access efficiency.</p></li><li><p> The internal ID is used as the filename partly to avoid requiring an extra lookup of the filename of the bitstream, and partly because bitstreams may be received from a variety of operating systems. The original name of a bitstream may be an illegal UNIX filename.</p></li></ul></div><p>When storing a bitstream, the <code class="literal">BitstreamStorageManager</code> DOES set the following fields in the corresponding database table row:</p><div class="itemizedlist"><ul type="disc"><li><p>
             <code class="literal">bitstream_id</code>
@@ -53,14 +53,14 @@ psql -U dspace -f <span class="emphasis"><em>
             <code class="literal">deleted</code>
           </p></li><li><p>
             <code class="literal">store_number</code>
-          </p></li></ul></div><p>The remaining fields are the responsibility of the <code class="literal">Bitstream</code> content management API class.</p><p>The bitstream storage manager is fully transaction-safe. In order to implement transaction-safety, the following algorithm is used to store bitstreams:</p><div class="orderedlist"><ol type="1"><li><p> A database connection is created, separately from the currently active connection in the <a class="ulink" href="business.html#core" target="_top">current DSpace context</a>.</p></li><li><p> An unique internal identifier (separate from the database primary key) is generated.</p></li><li><p> The bitstream DB table row is created using this new connection, with the <code class="literal">deleted</code> column set to <code class="literal">true</code>.</p></li><li><p> The new connection is <code class="literal">commit</code>ted, so the 'deleted' bitstream row is written to the database</p></li><li><p> The bitstream itself is stored in a file in the configured 'asset store directory', with a directory path and filename derived from the internal ID</p></li><li><p> The <code class="literal">deleted</code> flag in the bitstream row is set to <code class="literal">false</code>. This will occur (or not) as part of the current DSpace <code class="literal">Context</code>.</p></li></ol></div><p>This means that should anything go wrong before, during or after the bitstream storage, only one of the following can be true:</p><div class="itemizedlist"><ul type="disc"><li><p> No bitstream table row was created, and no file was stored</p></li><li><p> A bitstream table row with <code class="literal">deleted=true</code> was created, no file was stored</p></li><li><p> A bitstream table row with <code class="literal">deleted=true</code> was created, and a file was stored</p></li></ul></div><p>None of these affect the integrity of the data in the database or bitstream store.</p><p>Similarly, when a bitstream is deleted for some reason, its <code class="literal">deleted</code> flag is set to true as part of the overall transaction, and the corresponding file in storage is <span class="emphasis"><em>not</em></span> deleted.</p><p>The above techniques mean that the bitstream storage manager is transaction-safe. Over time, the bitstream database table and file store may contain a number of 'deleted' bitstreams. The <code class="literal">cleanup</code> method of <code class="literal">BitstreamStorageManager</code> goes through these deleted rows, and actually deletes them along with any corresponding files left in the storage. It only removes 'deleted' bitstreams that are more than one hour old, just in case cleanup is happening in the middle of a storage operation.</p><p>This cleanup can be invoked from the command line via the <code class="literal">Cleanup</code> class, which can in turn be easily executed from a shell on the server machine using <code class="literal">/dspace/bin/cleanup</code>. You might like to have this run regularly by <code class="literal">cron</code>, though since DSpace is read-lots, write-not-so-much it doesn't need to be run very often.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12A59"></a>6.2.1.&nbsp;Backup</h3></div></div></div><p>The bitstreams (files) in traditional storage may be backed up very easily by simply 'tarring' or 'zipping' the <code class="literal">assetstore</code> directory (or whichever directory is configured in <code class="literal">dspace.cfg</code>). Restoring is as simple as extracting the backed-up compressed file in the appropriate location.</p><p>Similar means could be used for SRB, but SRB offers many more options for managing backup.</p><p>It is important to note that since the bitstream storage manager holds the bitstreams in storage, and information about them in the database, that a database backup and a backup of the files in the bitstream store must be made at the same time; the bitstream data in the database must correspond to the stored files.</p><p>Of course, it isn't really ideal to 'freeze' the system while backing up to ensure that the database and files match up. Since DSpace uses the bitstream data in the database as the authoritative record, it's best to back up the database before the files. This is because it's better to have a bitstream in storage but not the database (effectively non-existent to DSpace) than a bitstream record in the database but not storage, since people would be able to find the bitstream but not actually get the contents.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12A6D"></a>6.2.2.&nbsp;Configuring the Bitstream Store</h3></div></div></div><p>Both traditional and SRB bitstream stores are configured in <code class="literal">dspace.cfg</code>.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12A77"></a>Configuring Traditonal Storage</h4></div></div></div><p>Bitstream stores in the file system on the server are configured like this:</p><pre class="screen">
+          </p></li></ul></div><p>The remaining fields are the responsibility of the <code class="literal">Bitstream</code> content management API class.</p><p>The bitstream storage manager is fully transaction-safe. In order to implement transaction-safety, the following algorithm is used to store bitstreams:</p><div class="orderedlist"><ol type="1"><li><p> A database connection is created, separately from the currently active connection in the <a class="link" href="ch10.html#docbook-business.html-core">current DSpace context</a>.</p></li><li><p> An unique internal identifier (separate from the database primary key) is generated.</p></li><li><p> The bitstream DB table row is created using this new connection, with the <code class="literal">deleted</code> column set to <code class="literal">true</code>.</p></li><li><p> The new connection is <code class="literal">commit</code>ted, so the 'deleted' bitstream row is written to the database</p></li><li><p> The bitstream itself is stored in a file in the configured 'asset store directory', with a directory path and filename derived from the internal ID</p></li><li><p> The <code class="literal">deleted</code> flag in the bitstream row is set to <code class="literal">false</code>. This will occur (or not) as part of the current DSpace <code class="literal">Context</code>.</p></li></ol></div><p>This means that should anything go wrong before, during or after the bitstream storage, only one of the following can be true:</p><div class="itemizedlist"><ul type="disc"><li><p> No bitstream table row was created, and no file was stored</p></li><li><p> A bitstream table row with <code class="literal">deleted=true</code> was created, no file was stored</p></li><li><p> A bitstream table row with <code class="literal">deleted=true</code> was created, and a file was stored</p></li></ul></div><p>None of these affect the integrity of the data in the database or bitstream store.</p><p>Similarly, when a bitstream is deleted for some reason, its <code class="literal">deleted</code> flag is set to true as part of the overall transaction, and the corresponding file in storage is <span class="emphasis"><em>not</em></span> deleted.</p><p>The above techniques mean that the bitstream storage manager is transaction-safe. Over time, the bitstream database table and file store may contain a number of 'deleted' bitstreams. The <code class="literal">cleanup</code> method of <code class="literal">BitstreamStorageManager</code> goes through these deleted rows, and actually deletes them along with any corresponding files left in the storage. It only removes 'deleted' bitstreams that are more than one hour old, just in case cleanup is happening in the middle of a storage operation.</p><p>This cleanup can be invoked from the command line via the <code class="literal">Cleanup</code> class, which can in turn be easily executed from a shell on the server machine using <code class="literal">/dspace/bin/cleanup</code>. You might like to have this run regularly by <code class="literal">cron</code>, though since DSpace is read-lots, write-not-so-much it doesn't need to be run very often.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12AD3"></a>6.2.1.&nbsp;Backup</h3></div></div></div><p>The bitstreams (files) in traditional storage may be backed up very easily by simply 'tarring' or 'zipping' the <code class="literal">assetstore</code> directory (or whichever directory is configured in <code class="literal">dspace.cfg</code>). Restoring is as simple as extracting the backed-up compressed file in the appropriate location.</p><p>Similar means could be used for SRB, but SRB offers many more options for managing backup.</p><p>It is important to note that since the bitstream storage manager holds the bitstreams in storage, and information about them in the database, that a database backup and a backup of the files in the bitstream store must be made at the same time; the bitstream data in the database must correspond to the stored files.</p><p>Of course, it isn't really ideal to 'freeze' the system while backing up to ensure that the database and files match up. Since DSpace uses the bitstream data in the database as the authoritative record, it's best to back up the database before the files. This is because it's better to have a bitstream in storage but not the database (effectively non-existent to DSpace) than a bitstream record in the database but not storage, since people would be able to find the bitstream but not actually get the contents.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12AE7"></a>6.2.2.&nbsp;Configuring the Bitstream Store</h3></div></div></div><p>Both traditional and SRB bitstream stores are configured in <code class="literal">dspace.cfg</code>.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12AF1"></a>Configuring Traditonal Storage</h4></div></div></div><p>Bitstream stores in the file system on the server are configured like this:</p><pre class="screen">
 assetstore.dir = <span class="emphasis"><em> [dspace]</em></span>/assetstore
 </pre><p>(Remember that <span class="emphasis"><em>[dspace]</em></span> is a placeholder for the actual name of your DSpace install directory).</p><p>The above example specifies a single asset store.</p><pre class="screen">
 assetstore.dir = <span class="emphasis"><em> [dspace]</em></span>/assetstore_0
 assetstore.dir.1 = /mnt/other_filesystem/assetstore_1
 </pre><p>The above example specifies two asset stores. assetstore.dir specifies the asset store number 0 (zero); after that use assetstore.dir.1, assetstore.dir.2 and so on. The particular asset store a bitstream is stored in is held in the database, so don't move bitstreams between asset stores, and don't renumber them.</p><p>By default, newly created bitstreams are put in asset store 0 (i.e. the one specified by the assetstore.dir property.) This allows backwards compatibility with pre-DSpace 1.1 configurations. To change this, for example when asset store 0 is getting full, add a line to <code class="literal">dspace.cfg</code> like:</p><pre class="screen">
 assetstore.incoming = 1
-</pre><p>Then restart DSpace (Tomcat). New bitstreams will be written to the asset store specified by <code class="literal">assetstore.dir.1</code>, which is <code class="literal">/mnt/other_filesystem/assetstore_1</code> in the above example.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12AA5"></a>Configuring SRB Storage</h4></div></div></div><p>The same framework is used to configure SRB storage. That is, the asset store number (0..n) can reference a file system directory as above or it can reference a set of SRB account parameters. But any particular asset store number can reference one or the other but not both. This way traditional and SRB storage can both be used but with different asset store numbers. The same cautions mentioned above apply to SRB asset stores as well: The particular asset store a bitstream is stored in is held in the database, so don't move bitstreams between asset stores, and don't renumber them.</p><p>For example, let's say asset store number 1 will refer to SRB. The there will be a set of SRB account parameters like this:</p><pre class="screen">
+</pre><p>Then restart DSpace (Tomcat). New bitstreams will be written to the asset store specified by <code class="literal">assetstore.dir.1</code>, which is <code class="literal">/mnt/other_filesystem/assetstore_1</code> in the above example.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N12B1F"></a>Configuring SRB Storage</h4></div></div></div><p>The same framework is used to configure SRB storage. That is, the asset store number (0..n) can reference a file system directory as above or it can reference a set of SRB account parameters. But any particular asset store number can reference one or the other but not both. This way traditional and SRB storage can both be used but with different asset store numbers. The same cautions mentioned above apply to SRB asset stores as well: The particular asset store a bitstream is stored in is held in the database, so don't move bitstreams between asset stores, and don't renumber them.</p><p>For example, let's say asset store number 1 will refer to SRB. The there will be a set of SRB account parameters like this:</p><pre class="screen">
 srb.host.1 = mysrbmcathost.myu.edu
 srb.port.1 = 5544
 srb.mcatzone.1 = mysrbzone
@@ -70,7 +70,7 @@ srb.username.1 = mysrbuser
 srb.password.1 = mysrbpassword
 srb.homedirectory.1 = /mysrbzone/home/mysrbuser.mysrbdomain
 srb.parentdir.1 = mysrbdspaceassetstore
-</pre><p>Several of the terms, such as <code class="literal">mcatzone</code>, have meaning only in the SRB context and will be familiar to SRB users. The last, <code class="literal">srb.parentdir.n</code>, can be used to used for addition (SRB) upper directory structure within an SRB account. This property value could be blank as well.</p><p>(If asset store 0 would refer to SRB it would be <code class="literal">srb.host =</code> ..., <code class="literal">srb.port =</code> ..., and so on (<code class="literal">.0</code> omitted) to be consistent with the traditional storage configuration above.)</p><p>The similar use of <code class="literal">assetstore.incoming</code> to reference asset store 0 (default) or 1..n (explicit property) means that new bitstreams will be written to traditional or SRB storage determined by whether a file system directory on the server is referenced or a set of SRB account parameters are referenced.</p><p>There are comments in dspace.cfg that further elaborate the configuration of traditional and SRB storage.</p></div></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre><p>Several of the terms, such as <code class="literal">mcatzone</code>, have meaning only in the SRB context and will be familiar to SRB users. The last, <code class="literal">srb.parentdir.n</code>, can be used to used for addition (SRB) upper directory structure within an SRB account. This property value could be blank as well.</p><p>(If asset store 0 would refer to SRB it would be <code class="literal">srb.host =</code> ..., <code class="literal">srb.port =</code> ..., and so on (<code class="literal">.0</code> omitted) to be consistent with the traditional storage configuration above.)</p><p>The similar use of <code class="literal">assetstore.incoming</code> to reference asset store 0 (default) or 1..n (explicit property) means that new bitstreams will be written to traditional or SRB storage determined by whether a file system directory on the server is referenced or a set of SRB account parameters are referenced.</p><p>There are comments in dspace.cfg that further elaborate the configuration of traditional and SRB storage.</p></div></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch07.html b/dspace/docs/html/ch07.html
index fb4410fc8d..52c0e8641d 100644
--- a/dspace/docs/html/ch07.html
+++ b/dspace/docs/html/ch07.html
@@ -1,16 +1,16 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch06.html" title="Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer"><link rel="next" href="ch08.html" title="Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch06.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch08.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N12AD0"></a>Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch07.html#N12AD4">7.1. Overview</a></span></dt><dt><span class="section"><a href="ch07.html#N12AFC">7.2. Source Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12C11">7.3. Installed Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12C66">7.4. Contents of JSPUI Web Application</a></span></dt><dt><span class="section"><a href="ch07.html#N12CA2">7.5. Contents of XMLUI Web Application (aka Manakin)</a></span></dt><dt><span class="section"><a href="ch07.html#N12D16">7.6. Log Files</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12AD4"></a>7.1.&nbsp;<a name="docbook-directories.html-overview"></a>Overview</h2></div></div></div><p>A complete DSpace installation consists of three separate directory trees:</p><div class="variablelist"><dl><dt><span class="term">The source directory:</span></dt><dd><p> This is where (surprise!) 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 <code class="literal">[dspace-source]</code>.</p></dd><dt><span class="term">The install directory:</span></dt><dd><p> 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--although not necessarily--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 <code class="literal">[dspace]</code>.</p></dd><dt><span class="term">The web deployment directory:</span></dt><dd><p> 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 <code class="literal">[tomcat]/webapps/dspace</code>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12AFC"></a>7.2.&nbsp;<a name="docbook-directories.html-sourcedir"></a>Source Directory Layout</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch06.html" title="Chapter&nbsp;6.&nbsp;DSpace System Documentation: Storage Layer"><link rel="next" href="ch08.html" title="Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch06.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch08.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N12B4A"></a>Chapter&nbsp;7.&nbsp;<a name="docbook-directories.html"></a>DSpace System Documentation: Directories and Files</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch07.html#N12B50">7.1. Overview</a></span></dt><dt><span class="section"><a href="ch07.html#N12B78">7.2. Source Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12C8D">7.3. Installed Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12CE2">7.4. Contents of JSPUI Web Application</a></span></dt><dt><span class="section"><a href="ch07.html#N12D1E">7.5. Contents of XMLUI Web Application (aka Manakin)</a></span></dt><dt><span class="section"><a href="ch07.html#N12D92">7.6. Log Files</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12B50"></a>7.1.&nbsp;<a name="docbook-directories.html-overview"></a>Overview</h2></div></div></div><p>A complete DSpace installation consists of three separate directory trees:</p><div class="variablelist"><dl><dt><span class="term">The source directory:</span></dt><dd><p> This is where (surprise!) 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 <code class="literal">[dspace-source]</code>.</p></dd><dt><span class="term">The install directory:</span></dt><dd><p> 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--although not necessarily--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 <code class="literal">[dspace]</code>.</p></dd><dt><span class="term">The web deployment directory:</span></dt><dd><p> 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 <code class="literal">[tomcat]/webapps/dspace</code>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12B78"></a>7.2.&nbsp;<a name="docbook-directories.html-sourcedir"></a>Source Directory Layout</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
             <code class="literal">[dspace-source]</code>
             <div class="itemizedlist"><ul type="circle"><li><p><code class="literal">dspace/</code>  - Directory which contains all build and configuration information for DSpace </p><div class="itemizedlist"><ul type="square"><li><p><code class="literal">build.xml</code>  - The Build file for Ant -- used to preform a fresh_install, upgrade, or deploy new changes.</p></li><li><p><code class="literal">CHANGES</code>  - Detailed list of code changes between versions.</p></li><li><p><code class="literal">KNOWN_BUGS</code>  - Known bugs in the current version.</p></li><li><p><code class="literal">LICENSE</code>  - DSpace source code license.</p></li><li><p><code class="literal">README</code>  - Obligatory basic information file.</p></li><li><p><code class="literal">bin/</code>  - Some shell and Perl scripts for running DSpace command-line tasks.</p></li><li><p><code class="literal">config/</code>  - Configuration files: </p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">controlled-vocabularies/</code>  - Fixed, limited vocabularies used in metadata entry</p></li><li><p><code class="literal">crosswalks/</code>  - Metadata crosswalks - property files or XSL stylesheets</p></li><li><p><code class="literal">dspace.cfg</code>  - The Main DSpace configuration file (You will need to edit this).</p></li><li><p><code class="literal">dc2mods.cfg</code>  - Mappings from Dublin Core metadata to <a class="ulink" href="http://www.loc.gov/standards/mods/" target="_top">MODS</a> for the METS export.</p></li><li><p><code class="literal">default.license</code>  - The default license that users must grant when submitting items.</p></li><li><p><code class="literal">dstat.cfg</code> , <code class="literal">dstat.map</code> - Configuration for statistical reports.</p></li><li><p><code class="literal">input-forms.xml</code>  - Submission UI metadata field configuration.</p></li><li><p><code class="literal">news-side.html</code>  - Text of the front-page news in the sidebar, only used in JSPUI.</p></li><li><p><code class="literal">news-top.html</code>  - Text of the front-page news in the top box, only used in teh JSPUI.</p></li><li><p><code class="literal">emails/</code>  - Text and layout templates for emails sent out by the system.</p></li><li><p><code class="literal">language-packs/</code>  - Contains "dictionary files" -- Java properties files that contain user interface text in different languages</p></li><li><p><code class="literal">registries/</code>  - <span class="bold"><strong>Initial</strong></span> contents of the bitstream format registry and Dublin Core element/qualifier registry. These are only used on initial system setup, after which they are maintained in the database.</p></li><li><p><code class="literal">templates/</code>  - Configuration files for libraries and external applications (e.g. Apache, Tomcat) are kept and edited here. They can refer to properties in the main DSpace configuration - have a look at a couple. When they're updated, a command line tool fills out these files with appropriate values from dspace.cfg, and copies them to their appropriate location (hence "templates".)</p></li></ul></div></li><li><p><code class="literal">docs/</code>  - DSpace system documentation. The technical documentation for functionality, installation, configuration, etc.</p></li><li><p><code class="literal">etc/</code>  - Miscelleanous configuration need to install DSpace that isn't really to do with system configuration - e.g. the PostgreSQL database schema, and a couple of configuration files that are used during the build process but not by the live system. Also contains the deployment descriptors (<code class="literal">web.xml</code> files) for the Web UI and OAI-PMH support <code class="literal">.war</code> files. </p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">oracle/</code>  - Versions of the database schema and updater SQL scripts for Oracle.</p></li></ul></div></li><li><p><code class="literal">modules/</code>  - The Web UI modules "overlay" directory. DSpace uses Maven to automatically look here for any customizations you wish to make to DSpace Web interfaces. </p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">jspui</code>  - Contains all customizations for the JSP User Interface. </p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal">src/main/resources/</code>  - The overlay for JSPUI Resources. This is the location to place any custom Messages.properties files.</p></li><li><p><code class="literal">src/main/webapp/</code>  - The overlay for JSPUI Web Application. This is the location to place any custom JSPs to be used by DSpace.</p></li></ul></div></li><li><p><code class="literal">lni</code>  - Contains all customizations for the Lightweight Network Interface.</p></li><li><p><code class="literal">oai</code>  - Contains all customizations for the OAI-PMH Interface.</p></li><li><p><code class="literal">sword</code>  - Contains all customizations for the SWORD (Simple Web-service Offering Repository Deposit) Interface.</p></li><li><p><code class="literal">xmlui</code>  - Contains all customizations for the XML User Interface (aka Manakin). </p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal">src/main/webapp/</code>  - The overlay for XMLUI Web Application. This is the location to place custom Themes or Configurations. </p><div class="itemizedlist"><ul type="square"><li><p><code class="literal">i18n/</code>  - The location to place a custom version of the XMLUI's messages.xml</p></li><li><p><code class="literal">themes/</code>  - The location to place custom Themes for the XMLUI</p></li></ul></div></li></ul></div></li></ul></div></li><li><p><code class="literal">src/</code>  - Maven configurations for DSpace System. This directory contains the Maven and Ant build files for DSpace.</p></li><li><p><code class="literal">target/</code>  - (Only exists after building DSpace) This is the location Maven uses to build your DSpace installation package. </p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">dspace-[version].dir</code>  - The location of the DSpace Installation Package (which can then be installed by running <code class="literal">ant update</code>)</p></li></ul></div></li></ul></div></li></ul></div>
-          </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12C11"></a>7.3.&nbsp;<a name="docbook-directories.html-installdir"></a>Installed Directory Layout</h2></div></div></div><p>Below is the basic layout of a DSpace installation using the default configuration. These paths can be configured if necessary.</p><div class="itemizedlist"><ul type="disc"><li><p>
+          </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12C8D"></a>7.3.&nbsp;<a name="docbook-directories.html-installdir"></a>Installed Directory Layout</h2></div></div></div><p>Below is the basic layout of a DSpace installation using the default configuration. These paths can be configured if necessary.</p><div class="itemizedlist"><ul type="disc"><li><p>
             <code class="literal">[dspace]</code>
             <div class="itemizedlist"><ul type="circle"><li><p><code class="literal">assetstore/</code>  - asset store files</p></li><li><p><code class="literal">bin/</code>  - shell and Perl scripts</p></li><li><p><code class="literal">config/</code>  - configuration, with sub-directories as above</p></li><li><p><code class="literal">handle-server/</code>  - Handles server files</p></li><li><p><code class="literal">history/</code>  - stored history files (generally RDF/XML)</p></li><li><p><code class="literal">lib/</code>  - JARs, including dspace.jar, containing the DSpace classes</p></li><li><p><code class="literal">log/</code>  - Log files</p></li><li><p><code class="literal">reports/</code>  - Reports generated by statistical report generator</p></li><li><p><code class="literal">search/</code>  - Lucene search index files</p></li><li><p><code class="literal">upload/</code>  - temporary directory used during file uploads etc.</p></li><li><p><code class="literal">webapps/</code>  - location where DSpace installs all Web Applications</p></li></ul></div>
-          </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12C66"></a>7.4.&nbsp;<a name="docbook-directories.html-webapp"></a>Contents of JSPUI Web Application</h2></div></div></div><p>DSpace's Ant build file creates a <code class="literal">dspace-jspui-webapp/</code> directory with the following structure:</p><div class="itemizedlist"><ul type="disc"><li><p> (top level dir) </p><div class="itemizedlist"><ul type="circle"><li><p> The JSPs</p></li><li><p>
+          </p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12CE2"></a>7.4.&nbsp;<a name="docbook-directories.html-webapp"></a>Contents of JSPUI Web Application</h2></div></div></div><p>DSpace's Ant build file creates a <code class="literal">dspace-jspui-webapp/</code> directory with the following structure:</p><div class="itemizedlist"><ul type="disc"><li><p> (top level dir) </p><div class="itemizedlist"><ul type="circle"><li><p> The JSPs</p></li><li><p>
                 <code class="literal">WEB-INF/</code>
                 <div class="itemizedlist"><ul type="square"><li><p><code class="literal">web.xml</code>  - DSpace JSPUI Web Application configuration and Servlet mappings</p></li><li><p><code class="literal">dspace-tags.tld</code>  - DSpace custom tag descriptor</p></li><li><p><code class="literal">fmt.tld</code>  - JSTL message format tag descriptor, for internationalization</p></li><li><p><code class="literal">lib/</code>  - All the third-party JARs and pre-compiled DSpace API JARs needed to run JSPUI</p></li><li><p><code class="literal">classes/</code>  - Any additional necessary class files</p></li></ul></div>
-              </p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12CA2"></a>7.5.&nbsp;<a name="docbook-directories.html-webapp.1"></a>Contents of XMLUI Web Application (aka Manakin)</h2></div></div></div><p>DSpace's Ant build file creates a <code class="literal">dspace-xmlui-webapp/</code> directory with the following structure:</p><div class="itemizedlist"><ul type="disc"><li><p> (top level dir) </p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal">aspects/</code>  - Contains overarching Aspect Generator config and Prototype DRI (Digital Repository Interface) document for Manakin.</p></li><li><p><code class="literal">i18n/</code>  - Internationalization / Multilingual support. Contains the <code class="literal">messages.xml</code> English language pack by default.</p></li><li><p><code class="literal">themes/</code>  - Contains all out-of-the-box Manakin themes </p><div class="itemizedlist"><ul type="square"><li><p><code class="literal">Classic/</code>  - The classic theme, which makes the XMLUI look like classic DSpace</p></li><li><p><code class="literal">dri2xhtml/</code>  - The base theme, which converts XMLUI DRI (Digital Repository Interface) format into XHTML for display</p></li><li><p><code class="literal">Reference/</code>  - The default reference theme for XMLUI</p></li><li><p><code class="literal">template/</code>  - A theme template...useful as a starting point for your own custom theme(s)</p></li><li><p><code class="literal">dri2xhtml.xsl</code>  - The DRI-to-XHTML XSL Stylesheet. Uses the above 'dri2xhtml' theme to generate XHTML</p></li><li><p><code class="literal">themes.xmap</code>  - The Theme configuration file. It determines which theme(s) are used by XMLUI</p></li></ul></div></li><li><p>
+              </p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12D1E"></a>7.5.&nbsp;<a name="docbook-directories.html-webapp.1"></a>Contents of XMLUI Web Application (aka Manakin)</h2></div></div></div><p>DSpace's Ant build file creates a <code class="literal">dspace-xmlui-webapp/</code> directory with the following structure:</p><div class="itemizedlist"><ul type="disc"><li><p> (top level dir) </p><div class="itemizedlist"><ul type="circle"><li><p><code class="literal">aspects/</code>  - Contains overarching Aspect Generator config and Prototype DRI (Digital Repository Interface) document for Manakin.</p></li><li><p><code class="literal">i18n/</code>  - Internationalization / Multilingual support. Contains the <code class="literal">messages.xml</code> English language pack by default.</p></li><li><p><code class="literal">themes/</code>  - Contains all out-of-the-box Manakin themes </p><div class="itemizedlist"><ul type="square"><li><p><code class="literal">Classic/</code>  - The classic theme, which makes the XMLUI look like classic DSpace</p></li><li><p><code class="literal">dri2xhtml/</code>  - The base theme, which converts XMLUI DRI (Digital Repository Interface) format into XHTML for display</p></li><li><p><code class="literal">Reference/</code>  - The default reference theme for XMLUI</p></li><li><p><code class="literal">template/</code>  - A theme template...useful as a starting point for your own custom theme(s)</p></li><li><p><code class="literal">dri2xhtml.xsl</code>  - The DRI-to-XHTML XSL Stylesheet. Uses the above 'dri2xhtml' theme to generate XHTML</p></li><li><p><code class="literal">themes.xmap</code>  - The Theme configuration file. It determines which theme(s) are used by XMLUI</p></li></ul></div></li><li><p>
                 <code class="literal">WEB-INF/</code>
                 <div class="itemizedlist"><ul type="square"><li><p><code class="literal">lib/</code>  - All the third-party JARs and pre-compiled DSpace JARs needed to run XMLUI</p></li><li><p><code class="literal">classes/</code>  - Any additional necessary class files</p></li><li><p><code class="literal">cocoon.xconf</code>  - XMLUI's Apache Cocoon configuration</p></li><li><p><code class="literal">logkit.xconf</code>  - XMLUI's Apache Cocoon Logging configuration</p></li><li><p><code class="literal">web.xml</code>  - XMLUI Web Application configuration and Servlet mappings</p></li></ul></div>
-              </p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12D16"></a>7.6.&nbsp;<a name="docbook-directories.html-logfiles"></a>Log Files</h2></div></div></div><p>The first source of potential confusion is the log files. Since DSpace uses a number of third-party tools, problems can occur in a variety of places. Below is a table listing the main log files used in a typical DSpace setup. The locations given are defaults, and might be different for your system depending on where you installed DSpace and the third-party tools. The ordering of the list is roughly the recommended order for searching them for the details about a particular problem or error.</p><div class="table"><a name="N12D1F"></a><p class="title"><b>Table&nbsp;7.1.&nbsp;DSpace Log File Locations</b></p><div class="table-contents"><table summary="DSpace Log File Locations" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+              </p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12D92"></a>7.6.&nbsp;<a name="docbook-directories.html-logfiles"></a>Log Files</h2></div></div></div><p>The first source of potential confusion is the log files. Since DSpace uses a number of third-party tools, problems can occur in a variety of places. Below is a table listing the main log files used in a typical DSpace setup. The locations given are defaults, and might be different for your system depending on where you installed DSpace and the third-party tools. The ordering of the list is roughly the recommended order for searching them for the details about a particular problem or error.</p><div class="table"><a name="N12D9B"></a><p class="title"><b>Table&nbsp;7.1.&nbsp;DSpace Log File Locations</b></p><div class="table-contents"><table summary="DSpace Log File Locations" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Log File</strong></span>
                 </p>
@@ -70,7 +70,7 @@
                 <p>PostgreSQL log</p>
               </td><td>
                 <p>PostgreSQL also writes a log file. This one doesn't seem to have a default location, you probably had to specify it yourself at some point during installation. In general, this log file rarely contains pertinent information--PostgreSQL is pretty stable, you're more likely to encounter problems with connecting via JDBC, and these problems will be logged in <code class="literal">dspace.log</code>.</p>
-              </td></tr></tbody></table></div></div><br class="table-break"></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+              </td></tr></tbody></table></div></div><br class="table-break"></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch08.html b/dspace/docs/html/ch08.html
index bb0ed64921..a8ad7a0357 100644
--- a/dspace/docs/html/ch08.html
+++ b/dspace/docs/html/ch08.html
@@ -1,6 +1,6 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch07.html" title="Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files"><link rel="next" href="ch09.html" title="Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch07.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch09.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N12DF2"></a>Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch08.html#N12DF6">8.1. Overview</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12DF6"></a>8.1.&nbsp;<a name="docbook-architecture.html-overview"></a>Overview</h2></div></div></div><p>The DSpace system is organized into three layers, each of which consists of a number of components.</p><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch07.html" title="Chapter&nbsp;7.&nbsp;DSpace System Documentation: Directories and Files"><link rel="next" href="ch09.html" title="Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch07.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch09.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N12E6E"></a>Chapter&nbsp;8.&nbsp;<a name="docbook-architecture.html"></a>DSpace System Documentation: Architecture</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch08.html#N12E74">8.1. Overview</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12E74"></a>8.1.&nbsp;<a name="docbook-architecture.html-overview"></a>Overview</h2></div></div></div><p>The DSpace system is organized into three layers, each of which consists of a number of components.</p><p>
         <span class="inlinemediaobject"><img src="image/architecture-600x450.gif" width="585"></span>
-      </p><p>DSpace System Architecture</p><p>The storage layer is responsible for physical storage of metadata and content. The business logic layer deals with managing the content of the archive, users of the archive (e-people), authorization, and workflow. The application layer contains components that communicate with the world outside of the individual DSpace installation, for example the Web user interface and the <a class="ulink" href="http://www.openarchives.org/" target="_top">Open Archives Initiative</a> protocol for metadata harvesting service.</p><p>Each layer only invokes the layer below it; the application layer may not used the storage layer directly, for example. Each component in the storage and business logic layers has a defined public API. The union of the APIs of those components are referred to as the Storage API (in the case of the storage layer) and the DSpace Public API (in the case of the business logic layer). These APIs are in-process Java classes, objects and methods.</p><p>It is important to note that each layer is <span class="emphasis"><em>trusted</em></span>. Although the logic for <span class="emphasis"><em>authorising actions</em></span> is in the business logic layer, the system relies on individual applications in the application layer to correctly and securely <span class="emphasis"><em>authenticate</em></span> e-people. If a 'hostile' or insecure application were allowed to invoke the Public API directly, it could very easily perform actions as any e-person in the system.</p><p>The reason for this design choice is that authentication methods will vary widely between different applications, so it makes sense to leave the logic and responsibility for that in these applications.</p><p>The source code is organized to cohere very strictly to this three-layer architecture. Also, only methods in a component's public API are given the <code class="literal">public</code> access level. This means that the Java compiler helps ensure that the source code conforms to the architecture.</p><div class="table"><a name="N12E26"></a><p class="title"><b>Table&nbsp;8.1.&nbsp;Source Code Packages</b></p><div class="table-contents"><table summary="Source Code Packages" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+      </p><p>DSpace System Architecture</p><p>The storage layer is responsible for physical storage of metadata and content. The business logic layer deals with managing the content of the archive, users of the archive (e-people), authorization, and workflow. The application layer contains components that communicate with the world outside of the individual DSpace installation, for example the Web user interface and the <a class="ulink" href="http://www.openarchives.org/" target="_top">Open Archives Initiative</a> protocol for metadata harvesting service.</p><p>Each layer only invokes the layer below it; the application layer may not used the storage layer directly, for example. Each component in the storage and business logic layers has a defined public API. The union of the APIs of those components are referred to as the Storage API (in the case of the storage layer) and the DSpace Public API (in the case of the business logic layer). These APIs are in-process Java classes, objects and methods.</p><p>It is important to note that each layer is <span class="emphasis"><em>trusted</em></span>. Although the logic for <span class="emphasis"><em>authorising actions</em></span> is in the business logic layer, the system relies on individual applications in the application layer to correctly and securely <span class="emphasis"><em>authenticate</em></span> e-people. If a 'hostile' or insecure application were allowed to invoke the Public API directly, it could very easily perform actions as any e-person in the system.</p><p>The reason for this design choice is that authentication methods will vary widely between different applications, so it makes sense to leave the logic and responsibility for that in these applications.</p><p>The source code is organized to cohere very strictly to this three-layer architecture. Also, only methods in a component's public API are given the <code class="literal">public</code> access level. This means that the Java compiler helps ensure that the source code conforms to the architecture.</p><div class="table"><a name="N12EA4"></a><p class="title"><b>Table&nbsp;8.1.&nbsp;Source Code Packages</b></p><div class="table-contents"><table summary="Source Code Packages" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Packages within</strong></span>
                 </p>
@@ -29,57 +29,57 @@
               </td></tr></tbody></table></div></div><br class="table-break"><p>The storage and business logic layer APIs are extensively documented with Javadoc-style comments. Generate the HTML version of these by entering the [dspace-source]/dspace directory and running:</p><pre class="screen">
 mvn javadoc:javadoc
 </pre><p> The resulting documentation will be at <code class="literal">[dspace-source]dspace-api/target/site/apidocs/index.html</code>.  The package-level documentation of each package usually contains an overview of the package and some example usage. This information is not repeated in this architecture document; this and the Javadoc APIs are intended to be used in parallel.</p><p>Each layer is described in a separate section:</p><div class="itemizedlist"><ul type="disc"><li><p>
-            <a class="ulink" href="storage.html" target="_top">Storage Layer</a>
+            <a class="link" href="ch06.html#docbook-storage.html">Storage Layer</a>
             <div class="itemizedlist"><ul type="circle"><li><p>
-                  <a class="ulink" href="storage.html#rdbms" target="_top">RDBMS</a>
+                  <a class="link" href="ch06.html#docbook-storage.html-rdbms">RDBMS</a>
                 </p></li><li><p>
-                  <a class="ulink" href="storage.html#bitstreams" target="_top">Bitstream Store</a>
+                  <a class="link" href="ch06.html#docbook-storage.html-bitstreams">Bitstream Store</a>
                 </p></li></ul></div>
           </p></li><li><p>
-            <a class="ulink" href="business.html" target="_top">Business Logic Layer</a>
+            <a class="link" href="ch10.html#docbook-business.html">Business Logic Layer</a>
             <div class="itemizedlist"><ul type="circle"><li><p>
-                  <a class="ulink" href="business.html#core" target="_top">Core Classes</a>
+                  <a class="link" href="ch10.html#docbook-business.html-core">Core Classes</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#content" target="_top">Content Management API</a>
+                  <a class="link" href="ch10.html#docbook-business.html-content">Content Management API</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#workflow" target="_top">Workflow System</a>
+                  <a class="link" href="ch10.html#docbook-business.html-workflow">Workflow System</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#administer" target="_top">Administration Toolkit</a>
+                  <a class="link" href="ch10.html#docbook-business.html-administer">Administration Toolkit</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#eperson" target="_top">E-person/Group Manager</a>
+                  <a class="link" href="ch10.html#docbook-business.html-eperson">E-person/Group Manager</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#authorize" target="_top">Authorisation</a>
+                  <a class="link" href="ch10.html#docbook-business.html-authorize">Authorisation</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#handle" target="_top">Handle Manager/Handle Plugin</a>
+                  <a class="link" href="ch10.html#docbook-business.html-handle">Handle Manager/Handle Plugin</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#search" target="_top">Search</a>
+                  <a class="link" href="ch10.html#docbook-business.html-search">Search</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#browse" target="_top">Browse API</a>
+                  <a class="link" href="ch10.html#docbook-business.html-browse">Browse API</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#history" target="_top">History Recorder</a>
+                  <a class="link" href="ch10.html#docbook-business.html-history">History Recorder</a>
                 </p></li><li><p>
-                  <a class="ulink" href="business.html#checker" target="_top">Checksum Checker</a>
+                  <a class="link" href="ch10.html#docbook-business.html-checker">Checksum Checker</a>
                 </p></li></ul></div>
           </p></li><li><p>
-            <a class="ulink" href="application.html" target="_top">Application Layer</a>
+            <a class="link" href="ch09.html#docbook-application.html">Application Layer</a>
             <div class="itemizedlist"><ul type="circle"><li><p>
-                  <a class="ulink" href="application.html#webui" target="_top">Web User Interface</a>
+                  <a class="link" href="ch09.html#docbook-application.html-webui">Web User Interface</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#oai" target="_top">OAI-PMH Data Provider</a>
+                  <a class="link" href="ch09.html#docbook-application.html-oai">OAI-PMH Data Provider</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#itemimporter" target="_top">Item Importer and Exporter</a>
+                  <a class="link" href="ch09.html#docbook-application.html-itemimporter">Item Importer and Exporter</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#transferitem" target="_top">Transferring Items Between DSpace Instances</a>
+                  <a class="link" href="ch09.html#docbook-application.html-transferitem">Transferring Items Between DSpace Instances</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#registration" target="_top">Registration</a>
+                  <a class="link" href="ch09.html#docbook-application.html-registration">Registration</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#mets" target="_top">METS Tools</a>
+                  <a class="link" href="ch09.html#docbook-application.html-mets">METS Tools</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#mediafilters" target="_top">Media Filters</a>
+                  <a class="link" href="ch09.html#docbook-application.html-mediafilters">Media Filters</a>
                 </p></li><li><p>
-                  <a class="ulink" href="application.html#filiator" target="_top">Sub-Community Management</a>
+                  <a class="link" href="ch09.html#docbook-application.html-filiator">Sub-Community Management</a>
                 </p></li></ul></div>
-          </p></li></ul></div><p> 2002-2008 The DSpace Foundation </p></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+          </p></li></ul></div><p> 2002-2008 The DSpace Foundation </p></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch09.html b/dspace/docs/html/ch09.html
index 371ea71e43..3819abdcd8 100644
--- a/dspace/docs/html/ch09.html
+++ b/dspace/docs/html/ch09.html
@@ -1,6 +1,6 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch08.html" title="Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture"><link rel="next" href="ch10.html" title="Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch08.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch10.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N12F39"></a>Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch09.html#N12F43">9.1. Web User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N12F4E">9.1.1. Web UI Files</a></span></dt><dt><span class="section"><a href="ch09.html#N1301C">9.1.2. The Build Process</a></span></dt><dt><span class="section"><a href="ch09.html#N130A0">9.1.3. Servlets and JSPs</a></span></dt><dt><span class="section"><a href="ch09.html#N13153">9.1.4. Custom JSP Tags</a></span></dt><dt><span class="section"><a href="ch09.html#N131F8">9.1.5. Internationalisation</a></span></dt><dt><span class="section"><a href="ch09.html#N132D5">9.1.6. HTML Content in Items</a></span></dt><dt><span class="section"><a href="ch09.html#N1334F">9.1.7. Thesis Blocking</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13365">9.2. OAI-PMH Data Provider</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13424">9.2.1. Sets</a></span></dt><dt><span class="section"><a href="ch09.html#N13433">9.2.2. Unique Identifier</a></span></dt><dt><span class="section"><a href="ch09.html#N1345F">9.2.3. Access control</a></span></dt><dt><span class="section"><a href="ch09.html#N13469">9.2.4. Modification Date (OAI Date Stamp)</a></span></dt><dt><span class="section"><a href="ch09.html#N1346F">9.2.5. 'About' Information</a></span></dt><dt><span class="section"><a href="ch09.html#N13475">9.2.6. Deletions</a></span></dt><dt><span class="section"><a href="ch09.html#N13484">9.2.7. Flow Control (Resumption Tokens)</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N134C8">9.3. Community and Collection Structure Importer</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N134E7">9.3.1. Limitation</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N134F0">9.4. Package Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13509">9.4.1. Ingesting</a></span></dt><dt><span class="section"><a href="ch09.html#N1353D">9.4.2. Disseminating</a></span></dt><dt><span class="section"><a href="ch09.html#N1356A">9.4.3. METS packages</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1358A">9.5. Item Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13593">9.5.1. DSpace simple archive format</a></span></dt><dt><span class="section"><a href="ch09.html#N135D0">9.5.2. Importing Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13608">9.5.3. Exporting Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13622">9.6. Transferring Items Between DSpace Instances</a></span></dt><dt><span class="section"><a href="ch09.html#N13661">9.7. Registering (Not Importing) Bitstreams</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13672">9.7.1. Accessible Storage</a></span></dt><dt><span class="section"><a href="ch09.html#N13690">9.7.2. Registering Items Using the Item Importer</a></span></dt><dt><span class="section"><a href="ch09.html#N13722">9.7.3. Internal Identification and Retrieval of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N1374E">9.7.4. Exporting Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13758">9.7.5. METS Export of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13762">9.7.6. Deleting Registered Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1377A">9.8. METS Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13783">9.8.1. The Export Tool</a></span></dt><dt><span class="section"><a href="ch09.html#N137B4">9.8.2. The AIP Format</a></span></dt><dt><span class="section"><a href="ch09.html#N13857">9.8.3. Limitations</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1386F">9.9. MediaFilters: Transforming DSpace Content</a></span></dt><dt><span class="section"><a href="ch09.html#N1393B">9.10. Sub-Community Management</a></span></dt></dl></div><p>
-      <a class="ulink" href="architecture.html" target="_top">Back to architecture overview</a>
-    </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12F43"></a>9.1.&nbsp;<a name="docbook-application.html-webui"></a>Web User Interface</h2></div></div></div><p>The DSpace Web UI is the largest and most-used component in the application layer. Built on Java Servlet and JavaServer Page technology, it allows end-users to access DSpace over the Web via their Web browsers. As of Dspace 1.3.2 the UI meets both XHTML 1.0 standards and Web Accessibility Initiative (WAI) level-2 standard.</p><p>It also features an administration section, consisting of pages intended for use by central administrators. Presently, this part of the Web UI is not particularly sophisticated; users of the administration section need to know what they are doing! Selected parts of this may also be used by collection administrators.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12F4E"></a>9.1.1.&nbsp;Web UI Files</h3></div></div></div><p>The Web UI-related files are located in a variety of directories in the DSpace source tree. Note that as of DSpace version 1.2, the deployment mechanism has changed; the build process creates easy-to-deploy Web application archives (<code class="literal">.war</code> files).</p><div class="table"><a name="N12F58"></a><p class="title"><b>Table&nbsp;9.1.&nbsp;Locations of Web UI Source Files</b></p><div class="table-contents"><table summary="Locations of Web UI Source Files" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch08.html" title="Chapter&nbsp;8.&nbsp;DSpace System Documentation: Architecture"><link rel="next" href="ch10.html" title="Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch08.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch10.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N12FB7"></a>Chapter&nbsp;9.&nbsp;<a name="docbook-application.html"></a>DSpace System Documentation: Application Layer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch09.html#N12FC3">9.1. Web User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N12FCE">9.1.1. Web UI Files</a></span></dt><dt><span class="section"><a href="ch09.html#N1309C">9.1.2. The Build Process</a></span></dt><dt><span class="section"><a href="ch09.html#N13120">9.1.3. Servlets and JSPs</a></span></dt><dt><span class="section"><a href="ch09.html#N131D3">9.1.4. Custom JSP Tags</a></span></dt><dt><span class="section"><a href="ch09.html#N13278">9.1.5. Internationalisation</a></span></dt><dt><span class="section"><a href="ch09.html#N13355">9.1.6. HTML Content in Items</a></span></dt><dt><span class="section"><a href="ch09.html#N133CF">9.1.7. Thesis Blocking</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N133E5">9.2. OAI-PMH Data Provider</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N134A4">9.2.1. Sets</a></span></dt><dt><span class="section"><a href="ch09.html#N134B3">9.2.2. Unique Identifier</a></span></dt><dt><span class="section"><a href="ch09.html#N134DF">9.2.3. Access control</a></span></dt><dt><span class="section"><a href="ch09.html#N134E9">9.2.4. Modification Date (OAI Date Stamp)</a></span></dt><dt><span class="section"><a href="ch09.html#N134EF">9.2.5. 'About' Information</a></span></dt><dt><span class="section"><a href="ch09.html#N134F5">9.2.6. Deletions</a></span></dt><dt><span class="section"><a href="ch09.html#N13504">9.2.7. Flow Control (Resumption Tokens)</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13548">9.3. Community and Collection Structure Importer</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13567">9.3.1. Limitation</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13570">9.4. Package Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13589">9.4.1. Ingesting</a></span></dt><dt><span class="section"><a href="ch09.html#N135BD">9.4.2. Disseminating</a></span></dt><dt><span class="section"><a href="ch09.html#N135EA">9.4.3. METS packages</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1360A">9.5. Item Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13613">9.5.1. DSpace simple archive format</a></span></dt><dt><span class="section"><a href="ch09.html#N13650">9.5.2. Importing Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13688">9.5.3. Exporting Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N136A2">9.6. Transferring Items Between DSpace Instances</a></span></dt><dt><span class="section"><a href="ch09.html#N136E1">9.7. Registering (Not Importing) Bitstreams</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N136F2">9.7.1. Accessible Storage</a></span></dt><dt><span class="section"><a href="ch09.html#N13710">9.7.2. Registering Items Using the Item Importer</a></span></dt><dt><span class="section"><a href="ch09.html#N137A2">9.7.3. Internal Identification and Retrieval of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N137CE">9.7.4. Exporting Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N137D8">9.7.5. METS Export of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N137E2">9.7.6. Deleting Registered Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N137FA">9.8. METS Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13803">9.8.1. The Export Tool</a></span></dt><dt><span class="section"><a href="ch09.html#N13834">9.8.2. The AIP Format</a></span></dt><dt><span class="section"><a href="ch09.html#N138D7">9.8.3. Limitations</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N138EF">9.9. MediaFilters: Transforming DSpace Content</a></span></dt><dt><span class="section"><a href="ch09.html#N139BB">9.10. Sub-Community Management</a></span></dt></dl></div><p>
+      <a class="link" href="ch08.html#docbook-architecture.html">Back to architecture overview</a>
+    </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N12FC3"></a>9.1.&nbsp;<a name="docbook-application.html-webui"></a>Web User Interface</h2></div></div></div><p>The DSpace Web UI is the largest and most-used component in the application layer. Built on Java Servlet and JavaServer Page technology, it allows end-users to access DSpace over the Web via their Web browsers. As of Dspace 1.3.2 the UI meets both XHTML 1.0 standards and Web Accessibility Initiative (WAI) level-2 standard.</p><p>It also features an administration section, consisting of pages intended for use by central administrators. Presently, this part of the Web UI is not particularly sophisticated; users of the administration section need to know what they are doing! Selected parts of this may also be used by collection administrators.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N12FCE"></a>9.1.1.&nbsp;Web UI Files</h3></div></div></div><p>The Web UI-related files are located in a variety of directories in the DSpace source tree. Note that as of DSpace version 1.2, the deployment mechanism has changed; the build process creates easy-to-deploy Web application archives (<code class="literal">.war</code> files).</p><div class="table"><a name="N12FD8"></a><p class="title"><b>Table&nbsp;9.1.&nbsp;Locations of Web UI Source Files</b></p><div class="table-contents"><table summary="Locations of Web UI Source Files" border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>Location</strong></span>
                   </p>
@@ -55,7 +55,7 @@
                     <code class="literal">[dspace-source]/jsp/local</code>
                   </p>
                 </td><td>
-                  <p>This is where you can place customized versions of JSPs -- see <a class="ulink" href="configure.html#customui" target="_top">the configuration section</a></p>
+                  <p>This is where you can place customized versions of JSPs -- see <a class="link" href="">the configuration section</a></p>
                 </td></tr><tr><td>
                   <p>
                     <code class="literal">[dspace-source]/jsp/WEB-INF/dspace-tags.tld</code>
@@ -68,11 +68,11 @@
                   </p>
                 </td><td>
                   <p>The Web application deployment descriptor. Before including in the <code class="literal">.war</code> file, the text <code class="literal">@@dspace.dir@@</code> will be replaced with the DSpace installation directory (referred to as <span class="emphasis"><em>[dspace]</em></span> elsewhere in this system documentation). This allows the Web application to pick up the DSpace configuration and environment.</p>
-                </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1301C"></a>9.1.2.&nbsp;<a name="docbook-application.html-webui_build"></a>The Build Process</h3></div></div></div><p>The DSpace build process constructs a Web application archive, which is placed in <code class="literal">[dspace-source]/build/dspace.war</code>. The <code class="literal">build_wars</code> Ant target does the work. The process works as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> All the DSpace source code is compiled.</p></li><li><p><code class="literal">[dspace-source]/etc/dspace-web.xml</code>  is copied to <code class="literal">[dspace-source]/build</code> and the <code class="literal">@@dspace.dir@@</code> token inside it replaced with the DSpace installation directory (<code class="literal">dspace.dir</code> property from <code class="literal">dspace.cfg</code></p></li><li><p> The JSPs are all copied to <code class="literal">[dspace-source]/build/jsp</code></p></li><li><p> Customized JSPs from <code class="literal">[dspace-source]/jsp/local</code> are copied on top of these, thus 'overriding' the default versions</p></li><li><p><code class="literal">[dspace-source]/build/dspace.war</code>  is built</p></li></ul></div><p>The contents of <code class="literal">dspace.war</code> are:</p><div class="itemizedlist"><ul type="disc"><li><p> (Top level) -- the JSPs (customized versions from <code class="literal">[dspace-source]/jsp/local</code> will have overwritten the defaults from the DSpace source distribution)</p></li><li><p><code class="literal">WEB-INF/classes</code>  -- the compiled DSpace classes</p></li><li><p><code class="literal">WEB-INF/lib</code>  -- the third party library JAR files from <code class="literal">[dspace-source]/lib</code>, minus <code class="literal">servlet.jar</code> which will be available as part of Tomcat (or other servlet engine)</p></li><li><p><code class="literal">WEB-INF/web.xml</code>  -- web deployment descriptor, copied from <code class="literal">[dspace-source]/build/dspace-web.xml</code></p></li><li><p><code class="literal">WEB-INF/dspace-tags.tld</code>  -- tag descriptor</p></li></ul></div><p>Note that this does mean there are multiple copies of the compiled DSpace code and third-party libraries in the system, so care must be taken to ensure that they are all in sync. (The storage overhead is a few megabytes, totally insignificant these days.) In general, when you change any DSpace code or JSP, it's best to do a complete update of both the installation (<code class="literal">[dspace]</code>), and to rebuild and redeploy the Web UI and OAI <code class="literal">.war</code> files, by running this in <code class="literal">[dspace-source]</code>:</p><pre class="screen">
+                </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1309C"></a>9.1.2.&nbsp;<a name="docbook-application.html-webui_build"></a>The Build Process</h3></div></div></div><p>The DSpace build process constructs a Web application archive, which is placed in <code class="literal">[dspace-source]/build/dspace.war</code>. The <code class="literal">build_wars</code> Ant target does the work. The process works as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> All the DSpace source code is compiled.</p></li><li><p><code class="literal">[dspace-source]/etc/dspace-web.xml</code>  is copied to <code class="literal">[dspace-source]/build</code> and the <code class="literal">@@dspace.dir@@</code> token inside it replaced with the DSpace installation directory (<code class="literal">dspace.dir</code> property from <code class="literal">dspace.cfg</code></p></li><li><p> The JSPs are all copied to <code class="literal">[dspace-source]/build/jsp</code></p></li><li><p> Customized JSPs from <code class="literal">[dspace-source]/jsp/local</code> are copied on top of these, thus 'overriding' the default versions</p></li><li><p><code class="literal">[dspace-source]/build/dspace.war</code>  is built</p></li></ul></div><p>The contents of <code class="literal">dspace.war</code> are:</p><div class="itemizedlist"><ul type="disc"><li><p> (Top level) -- the JSPs (customized versions from <code class="literal">[dspace-source]/jsp/local</code> will have overwritten the defaults from the DSpace source distribution)</p></li><li><p><code class="literal">WEB-INF/classes</code>  -- the compiled DSpace classes</p></li><li><p><code class="literal">WEB-INF/lib</code>  -- the third party library JAR files from <code class="literal">[dspace-source]/lib</code>, minus <code class="literal">servlet.jar</code> which will be available as part of Tomcat (or other servlet engine)</p></li><li><p><code class="literal">WEB-INF/web.xml</code>  -- web deployment descriptor, copied from <code class="literal">[dspace-source]/build/dspace-web.xml</code></p></li><li><p><code class="literal">WEB-INF/dspace-tags.tld</code>  -- tag descriptor</p></li></ul></div><p>Note that this does mean there are multiple copies of the compiled DSpace code and third-party libraries in the system, so care must be taken to ensure that they are all in sync. (The storage overhead is a few megabytes, totally insignificant these days.) In general, when you change any DSpace code or JSP, it's best to do a complete update of both the installation (<code class="literal">[dspace]</code>), and to rebuild and redeploy the Web UI and OAI <code class="literal">.war</code> files, by running this in <code class="literal">[dspace-source]</code>:</p><pre class="screen">
 ant -D<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg update
-</pre><p>and then following the instructions that command writes to the console.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N130A0"></a>9.1.3.&nbsp;Servlets and JSPs</h3></div></div></div><p>The Web UI is loosely based around the MVC (model, view, controller) model. The content management API corresponds to the model, the Java Servlets are the controllers, and the JSPs are the views. Interactions take the following basic form:</p><div class="orderedlist"><ol type="1"><li><p> An HTTP request is received from a browser</p></li><li><p> The appropriate servlet is invoked, and processes the request by invoking the DSpace business logic layer public API</p></li><li><p> Depending on the outcome of the processing, the servlet invokes the appropriate JSP</p></li><li><p> The JSP is processed and sent to the browser</p></li></ol></div><p>The reasons for this approach are:</p><div class="itemizedlist"><ul type="disc"><li><p> All of the processing is done before the JSP is invoked, so any error or problem that occurs does not occur halfway through HTML rendering</p></li><li><p> The JSPs contain as little code as possible, so they can be customized without having to delve into Java code too much</p></li></ul></div><p>The <code class="literal">org.dspace.app.webui.servlet.LoadDSpaceConfig</code> servlet is always loaded first. This is a very simple servlet that checks the <code class="literal">dspace-config</code> context parameter from the DSpace deployment descriptor, and uses it to locate <code class="literal">dspace.cfg</code>. It also loads up the Log4j configuration. It's important that this servlet is loaded first, since if another servlet is loaded up, it will cause the system to try and load DSpace and Log4j configurations, neither of which would be found.</p><p>All DSpace servlets are subclasses of the <code class="literal">DSpaceServlet</code> class. The <code class="literal">DSpaceServlet</code> class handles some basic operations such as creating a DSpace <code class="literal">Context</code> object (opening a database connection etc.), authentication and error handling. Instead of overriding the <code class="literal">doGet</code> and <code class="literal">doPost</code> methods as one normally would for a servlet, DSpace servlets implement <code class="literal">doDSGet</code> or <code class="literal">doDSPost</code> which have an extra context parameter, and allow the servlet to throw various exceptions that can be handled in a standard way.</p><p>The DSpace servlet processes the contents of the HTTP request. This might involve retrieving the results of a search with a query term, accessing the current user's eperson record, or updating a submission in progress. According to the results of this processing, the servlet must decide which JSP should be displayed. The servlet then fills out the appropriate attributes in the <code class="literal">HttpRequest</code> object that represents the HTTP request being processed. This is done by invoking the <code class="literal">setAttribute</code> method of the <code class="literal">javax.servlet.http.HttpServletRequest</code> object that is passed into the servlet from Tomcat. The servlet then forwards control of the request to the appropriate JSP using the <code class="literal">JSPManager.showJSP</code> method.</p><p>The <code class="literal">JSPManager.showJSP</code> method uses the standard Java servlet forwarding mechanism is then used to forward the HTTP request to the JSP. The JSP is processed by Tomcat and the results sent back to the user's browser.</p><p>There is an exception to this servlet/JSP style: <code class="literal">index.jsp</code>, the 'home page', receives the HTTP request directly from Tomcat without a servlet being invoked first. This is because in the servlet 2.3 specification, there is no way to map a servlet to handle only requests made to '<code class="literal">/</code>'; such a mapping results in every request being directed to that servlet. By default, Tomcat forwards requests to '<code class="literal">/</code>' to <code class="literal">index.jsp</code>. To try and make things as clean as possible, <code class="literal">index.jsp</code> contains some simple code that would normally go in a servlet, and then forwards to <code class="literal">home.jsp</code> using the <code class="literal">JSPManager.showJSP</code> method. This means localized versions of the 'home page' can be created by placing a customized <code class="literal">home.jsp</code> in <code class="literal">[dspace-source]/jsp/local</code>, in the same manner as other JSPs.</p><p><code class="literal">[dspace-source]/jsp/dspace-admin/index.jsp</code>, the administration UI index page, is invoked directly by Tomcat and not through a servlet for similar reasons.</p><p>At the top of each JSP file, right after the license and copyright header, is documented the appropriate attributes that a servlet must fill out prior to forwarding to that JSP. No validation is performed; if the servlet does not fill out the necessary attributes, it is likely that an internal server error will occur.</p><p>Many JSPs containing forms will include hidden parameters that tell the servlets which form has been filled out. The submission UI servlet (<code class="literal">SubmissionController</code> is a prime example of a servlet that deals with the input from many different JSPs. The <code class="literal">step</code> and <code class="literal">page</code> hidden parameters (written out by the <code class="literal">SubmissionController.getSubmissionParameters()</code> method) are used to inform the servlet which page of which step has just been filled out (i.e. which page of the submission the user has just completed).</p><p>Below is a detailed, scary diagram depicting the flow of control during the whole process of processing and responding to an HTTP request. More information about the authentication mechanism is mostly <a class="ulink" href="configure.html#authenticate" target="_top">described in the configuration section</a>.</p><p>
+</pre><p>and then following the instructions that command writes to the console.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13120"></a>9.1.3.&nbsp;Servlets and JSPs</h3></div></div></div><p>The Web UI is loosely based around the MVC (model, view, controller) model. The content management API corresponds to the model, the Java Servlets are the controllers, and the JSPs are the views. Interactions take the following basic form:</p><div class="orderedlist"><ol type="1"><li><p> An HTTP request is received from a browser</p></li><li><p> The appropriate servlet is invoked, and processes the request by invoking the DSpace business logic layer public API</p></li><li><p> Depending on the outcome of the processing, the servlet invokes the appropriate JSP</p></li><li><p> The JSP is processed and sent to the browser</p></li></ol></div><p>The reasons for this approach are:</p><div class="itemizedlist"><ul type="disc"><li><p> All of the processing is done before the JSP is invoked, so any error or problem that occurs does not occur halfway through HTML rendering</p></li><li><p> The JSPs contain as little code as possible, so they can be customized without having to delve into Java code too much</p></li></ul></div><p>The <code class="literal">org.dspace.app.webui.servlet.LoadDSpaceConfig</code> servlet is always loaded first. This is a very simple servlet that checks the <code class="literal">dspace-config</code> context parameter from the DSpace deployment descriptor, and uses it to locate <code class="literal">dspace.cfg</code>. It also loads up the Log4j configuration. It's important that this servlet is loaded first, since if another servlet is loaded up, it will cause the system to try and load DSpace and Log4j configurations, neither of which would be found.</p><p>All DSpace servlets are subclasses of the <code class="literal">DSpaceServlet</code> class. The <code class="literal">DSpaceServlet</code> class handles some basic operations such as creating a DSpace <code class="literal">Context</code> object (opening a database connection etc.), authentication and error handling. Instead of overriding the <code class="literal">doGet</code> and <code class="literal">doPost</code> methods as one normally would for a servlet, DSpace servlets implement <code class="literal">doDSGet</code> or <code class="literal">doDSPost</code> which have an extra context parameter, and allow the servlet to throw various exceptions that can be handled in a standard way.</p><p>The DSpace servlet processes the contents of the HTTP request. This might involve retrieving the results of a search with a query term, accessing the current user's eperson record, or updating a submission in progress. According to the results of this processing, the servlet must decide which JSP should be displayed. The servlet then fills out the appropriate attributes in the <code class="literal">HttpRequest</code> object that represents the HTTP request being processed. This is done by invoking the <code class="literal">setAttribute</code> method of the <code class="literal">javax.servlet.http.HttpServletRequest</code> object that is passed into the servlet from Tomcat. The servlet then forwards control of the request to the appropriate JSP using the <code class="literal">JSPManager.showJSP</code> method.</p><p>The <code class="literal">JSPManager.showJSP</code> method uses the standard Java servlet forwarding mechanism is then used to forward the HTTP request to the JSP. The JSP is processed by Tomcat and the results sent back to the user's browser.</p><p>There is an exception to this servlet/JSP style: <code class="literal">index.jsp</code>, the 'home page', receives the HTTP request directly from Tomcat without a servlet being invoked first. This is because in the servlet 2.3 specification, there is no way to map a servlet to handle only requests made to '<code class="literal">/</code>'; such a mapping results in every request being directed to that servlet. By default, Tomcat forwards requests to '<code class="literal">/</code>' to <code class="literal">index.jsp</code>. To try and make things as clean as possible, <code class="literal">index.jsp</code> contains some simple code that would normally go in a servlet, and then forwards to <code class="literal">home.jsp</code> using the <code class="literal">JSPManager.showJSP</code> method. This means localized versions of the 'home page' can be created by placing a customized <code class="literal">home.jsp</code> in <code class="literal">[dspace-source]/jsp/local</code>, in the same manner as other JSPs.</p><p><code class="literal">[dspace-source]/jsp/dspace-admin/index.jsp</code>, the administration UI index page, is invoked directly by Tomcat and not through a servlet for similar reasons.</p><p>At the top of each JSP file, right after the license and copyright header, is documented the appropriate attributes that a servlet must fill out prior to forwarding to that JSP. No validation is performed; if the servlet does not fill out the necessary attributes, it is likely that an internal server error will occur.</p><p>Many JSPs containing forms will include hidden parameters that tell the servlets which form has been filled out. The submission UI servlet (<code class="literal">SubmissionController</code> is a prime example of a servlet that deals with the input from many different JSPs. The <code class="literal">step</code> and <code class="literal">page</code> hidden parameters (written out by the <code class="literal">SubmissionController.getSubmissionParameters()</code> method) are used to inform the servlet which page of which step has just been filled out (i.e. which page of the submission the user has just completed).</p><p>Below is a detailed, scary diagram depicting the flow of control during the whole process of processing and responding to an HTTP request. More information about the authentication mechanism is mostly <a class="link" href="">described in the configuration section</a>.</p><p>
           <span class="inlinemediaobject"><img src="image/web-ui-flow.gif" width="585"></span>
-        </p><p>Flow of Control During HTTP Request Processing</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13153"></a>9.1.4.&nbsp;Custom JSP Tags</h3></div></div></div><p>The DSpace JSPs all use some custom tags defined in <code class="literal">/dspace/jsp/WEB-INF/dspace-tags.tld</code>, and the corresponding Java classes reside in <code class="literal">org.dspace.app.webui.jsptag</code>. The tags are listed below. The <code class="literal">dspace-tags.tld</code> file contains detailed comments about how to use the tags, so that information is not repeated here.</p><div class="variablelist"><dl><dt><span class="term">
+        </p><p>Flow of Control During HTTP Request Processing</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N131D3"></a>9.1.4.&nbsp;Custom JSP Tags</h3></div></div></div><p>The DSpace JSPs all use some custom tags defined in <code class="literal">/dspace/jsp/WEB-INF/dspace-tags.tld</code>, and the corresponding Java classes reside in <code class="literal">org.dspace.app.webui.jsptag</code>. The tags are listed below. The <code class="literal">dspace-tags.tld</code> file contains detailed comments about how to use the tags, so that information is not repeated here.</p><div class="variablelist"><dl><dt><span class="term">
               <code class="literal">layout</code>
             </span></dt><dd><p> Just about every JSP uses this tag. It produces the standard HTML header and <code class="literal">&lt;BODY&gt;</code>tag. Thus the content of each JSP is nested inside a <code class="literal">&lt;dspace:layout&gt;</code> tag. The (XML-style)attributes of this tag are slightly complicated--see <code class="literal">dspace-tags.tld</code>. The JSPs in the source code bundle also provide plenty of examples.</p></dd><dt><span class="term">
               <code class="literal">sidebar</code>
@@ -88,7 +88,7 @@ ant -D<span class="emphasis"><em> [dspace]</em></span>/config/dspace.cfg update
               <code class="literal">selecteperson</code>
             </span></dt><dd><p> A tag which produces a widget analogous to HTML <code class="literal">&lt;SELECT&gt;</code>, that allows a user to select one or multiple e-people from a pop-up list.</p></dd><dt><span class="term">
               <code class="literal">sfxlink</code>
-            </span></dt><dd><p> Using an item's Dublin Core metadata DSpace can display an SFX link, if an SFX server is available. This tag does so for a particular item if the <code class="literal">sfx.server.url</code> property is defined in <code class="literal">dspace.cfg</code>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N131F8"></a>9.1.5.&nbsp;<a name="docbook-application.html-i18n"></a>Internationalisation</h3></div></div></div><p>The <a class="ulink" href="http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/intro.html" target="_top">Java Standard Tag Library v1.0</a> is used to specify messages in the JSPs like this:</p><p>OLD:</p><pre class="screen">
+            </span></dt><dd><p> Using an item's Dublin Core metadata DSpace can display an SFX link, if an SFX server is available. This tag does so for a particular item if the <code class="literal">sfx.server.url</code> property is defined in <code class="literal">dspace.cfg</code>.</p></dd></dl></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13278"></a>9.1.5.&nbsp;<a name="docbook-application.html-i18n"></a>Internationalisation</h3></div></div></div><p>The <a class="ulink" href="http://jakarta.apache.org/taglibs/doc/standard-1.0-doc/intro.html" target="_top">Java Standard Tag Library v1.0</a> is used to specify messages in the JSPs like this:</p><p>OLD:</p><pre class="screen">
 &lt;H1&gt;Search Results&lt;/H1&gt;
 </pre><p>NEW:</p><pre class="screen">
 &lt;H1&gt;&lt;fmt:message key="jsp.search.results.title"
@@ -126,7 +126,7 @@ Messages_fr_CA.properties
                parentlink="/mydspace"
                parenttitlekey="jsp.mydspace"&gt;
 
-</pre><p>And so the layout tag itself gets the relevant stuff out of the dictionary. <code class="literal">title</code> and <code class="literal">parenttitle</code> still work as before for backwards compatibility, and the odd spot where that's preferable.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1328A"></a>Message Key Convention</h4></div></div></div><p>When translating further pages, please follow the convention for naming message keys to avoid clashes.</p><p><span class="bold"><strong>For text in JSPs</strong></span> use the complete path + filename of the JSP, then a one-word name for the message. e.g. for the title of <code class="literal">jsp/mydspace/main.jsp</code> use:</p><pre class="screen">
+</pre><p>And so the layout tag itself gets the relevant stuff out of the dictionary. <code class="literal">title</code> and <code class="literal">parenttitle</code> still work as before for backwards compatibility, and the odd spot where that's preferable.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1330A"></a>Message Key Convention</h4></div></div></div><p>When translating further pages, please follow the convention for naming message keys to avoid clashes.</p><p><span class="bold"><strong>For text in JSPs</strong></span> use the complete path + filename of the JSP, then a one-word name for the message. e.g. for the title of <code class="literal">jsp/mydspace/main.jsp</code> use:</p><pre class="screen">
 jsp.mydspace.main.title
 </pre><p>Some common words (e.g. "Help") can be brought out into keys starting <code class="literal">jsp.</code> for ease of translation, e.g.:</p><pre class="screen">
 jsp.admin = Administer
@@ -138,7 +138,7 @@ jsp.tools.general.delete = Delete
 jsp.mydspace.general.goto-mydspace = Go to My DSpace
 </pre><p><span class="bold"><strong>For text in servlet code</strong></span>, in custom JSP tags or wherever applicable use the fully qualified classname + a one-word name for the message. e.g.</p><pre class="screen">
 org.dspace.app.webui.jsptag.ItemListTag.title = Title
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N132CB"></a>Which Languages are currently supported?</h4></div></div></div><p>To view translations currently being developed, please refer to the <a class="ulink" href="http://wiki.dspace.org/I18nSupport" target="_top">i18n page</a> of the DSpace Wiki.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N132D5"></a>9.1.6.&nbsp;HTML Content in Items</h3></div></div></div><p>For the most part, the DSpace item display just gives a link that allows an end-user to download a bitstream. However, if a bundle has a primary bitstream whose format is of MIME type <code class="literal">text/html</code>, instead a link to the HTML servlet is given.</p><p>So if we had an HTML document like this:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1334B"></a>Which Languages are currently supported?</h4></div></div></div><p>To view translations currently being developed, please refer to the <a class="ulink" href="http://wiki.dspace.org/I18nSupport" target="_top">i18n page</a> of the DSpace Wiki.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13355"></a>9.1.6.&nbsp;HTML Content in Items</h3></div></div></div><p>For the most part, the DSpace item display just gives a link that allows an end-user to download a bitstream. However, if a bundle has a primary bitstream whose format is of MIME type <code class="literal">text/html</code>, instead a link to the HTML servlet is given.</p><p>So if we had an HTML document like this:</p><pre class="screen">
 contents.html
 chapter1.html
 chapter2.html
@@ -153,7 +153,7 @@ figure6.gif
 https://dspace.mit.edu/html/1721.1/12345/contents.html
 </pre><p>If there's an image called <code class="literal">figure1.gif</code> in that HTML page, the browser will do HTTP GET on this URL:</p><pre class="screen">
 https://dspace.mit.edu/html/1721.1/12345/figure1.gif
-</pre><p>The HTML document servlet can work out which item the user is looking at, and then which Bitstream in it is called <code class="literal">figure1.gif</code>, and serve up that bitstream. Similar for following links to other HTML pages. Of course all the links and image references have to be relative and not absolute.</p><p>HTML documents must be "self-contained", as <a class="ulink" href="functional.html#html" target="_top">explained here</a>. Provided that full path information is known by DSpace, any depth or complexity of HTML document can be served subject to those contraints. This is usually possible with some kind of batch import. If, however, the document has been uploaded one file at a time using the Web UI, the path information has been stripped. The system can cope with relative links that refer to a deeper path, e.g.</p><pre class="screen">
+</pre><p>The HTML document servlet can work out which item the user is looking at, and then which Bitstream in it is called <code class="literal">figure1.gif</code>, and serve up that bitstream. Similar for following links to other HTML pages. Of course all the links and image references have to be relative and not absolute.</p><p>HTML documents must be "self-contained", as <a class="link" href="ch02.html#docbook-functional.html-html">explained here</a>. Provided that full path information is known by DSpace, any depth or complexity of HTML document can be served subject to those contraints. This is usually possible with some kind of batch import. If, however, the document has been uploaded one file at a time using the Web UI, the path information has been stripped. The system can cope with relative links that refer to a deeper path, e.g.</p><pre class="screen">
 &lt;IMG SRC="images/figure1.gif"&gt;
 </pre><p>If the item has been uploaded via the Web submit UI, in the Bitstream table in the database we have the 'name' field, which will contain the filename with no path (<code class="literal">figure1.gif</code>). We can still work out what <code class="literal">images/figure1.gif</code> is by making the HTML document servlet strip any path that comes in from the URL, e.g.</p><pre class="screen">
 https://dspace.mit.edu/html/1721.1/12345/images/figure1.gif
@@ -168,7 +168,7 @@ chapter2_images/figure.gif
 </pre><p>since the HTML document servlet wouldn't know which bitstream to serve up for:</p><pre class="screen">
 https://dspace.mit.edu/html/1721.1/12345/chapter1_images/figure.gif
 https://dspace.mit.edu/html/1721.1/12345/chapter2_images/figure.gif
-</pre><p>since it would just have <code class="literal">figure.gif</code></p><p>To prevent "infinite URL spaces" appearing (e.g. if a file <code class="literal">foo.html</code> linked to <code class="literal">bar/foo.html</code>, which would link to <code class="literal">bar/bar/foo.html</code>...) this behavior can be configured by setting the configuration property <code class="literal">webui.html.max-depth-guess</code>.</p><p>For example, if we receive a request for <code class="literal">foo/bar/index.html</code>, and we have a bitstream called just <code class="literal">index.html</code>, we will serve up that bitstream for the request if <code class="literal">webui.html.max-depth-guess</code> is 2 or greater. If <code class="literal">webui.html.max-depth-guess</code> is 1 or less, we would not serve that bitstream, as the depth of the file is greater. If <code class="literal">webui.html.max-depth-guess</code> is zero, the request filename and path must always exactly match the bitstream name. The default value (if that property is not present in <code class="literal">dspace.cfg</code>) is 3.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1334F"></a>9.1.7.&nbsp;Thesis Blocking</h3></div></div></div><p>The submission UI has an optional feature that came about as a result of MIT Libraries policy. If the <code class="literal">block.theses</code> parameter in <code class="literal">dspace.cfg</code> is <code class="literal">true</code>, an extra checkbox is included in the first page of the submission UI. This asks the user if the submission is a thesis. If the user checks this box, the submission is halted (deleted) and an error message displayed, explaining that DSpace should not be used to submit theses. This feature can be turned off and on, and the message displayed (<code class="literal">/dspace/jsp/submit/no-theses.jsp</code> can be localized as necessary.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13365"></a>9.2.&nbsp;<a name="docbook-application.html-oai"></a>OAI-PMH Data Provider</h2></div></div></div><p>The DSpace platform supports the <a class="ulink" href="http://www.openarchives.org/" target="_top">Open Archives Initiative Protocol for Metadata Harvesting</a> (OAI-PMH) version 2.0 as a data provider. This is accomplished using the <a class="ulink" href="http://www.oclc.org/research/software/oai/cat.shtm" target="_top">OAICat framework from OCLC</a>.</p><p>The DSpace build process builds a Web application archive, <code class="literal">[dspace-source]/build/oai.war</code>), in much the same way as <a class="link" href="ch09.html#docbook-application.html-webui_build">the Web UI build process</a> described above. The only differences are that the JSPs are not included, and <code class="literal">[dspace-source]/etc/oai-web.xml</code> is used as the deployment descriptor. This 'webapp' is deployed to receive and respond to OAI-PMH requests via HTTP. Note that typically it should <span class="emphasis"><em>not</em></span> be deployed on SSL (<code class="literal">https:</code> protocol). In a typical configuration, this is deployed at <code class="literal">oai</code>, for example:</p><pre class="screen">
+</pre><p>since it would just have <code class="literal">figure.gif</code></p><p>To prevent "infinite URL spaces" appearing (e.g. if a file <code class="literal">foo.html</code> linked to <code class="literal">bar/foo.html</code>, which would link to <code class="literal">bar/bar/foo.html</code>...) this behavior can be configured by setting the configuration property <code class="literal">webui.html.max-depth-guess</code>.</p><p>For example, if we receive a request for <code class="literal">foo/bar/index.html</code>, and we have a bitstream called just <code class="literal">index.html</code>, we will serve up that bitstream for the request if <code class="literal">webui.html.max-depth-guess</code> is 2 or greater. If <code class="literal">webui.html.max-depth-guess</code> is 1 or less, we would not serve that bitstream, as the depth of the file is greater. If <code class="literal">webui.html.max-depth-guess</code> is zero, the request filename and path must always exactly match the bitstream name. The default value (if that property is not present in <code class="literal">dspace.cfg</code>) is 3.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N133CF"></a>9.1.7.&nbsp;Thesis Blocking</h3></div></div></div><p>The submission UI has an optional feature that came about as a result of MIT Libraries policy. If the <code class="literal">block.theses</code> parameter in <code class="literal">dspace.cfg</code> is <code class="literal">true</code>, an extra checkbox is included in the first page of the submission UI. This asks the user if the submission is a thesis. If the user checks this box, the submission is halted (deleted) and an error message displayed, explaining that DSpace should not be used to submit theses. This feature can be turned off and on, and the message displayed (<code class="literal">/dspace/jsp/submit/no-theses.jsp</code> can be localized as necessary.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N133E5"></a>9.2.&nbsp;<a name="docbook-application.html-oai"></a>OAI-PMH Data Provider</h2></div></div></div><p>The DSpace platform supports the <a class="ulink" href="http://www.openarchives.org/" target="_top">Open Archives Initiative Protocol for Metadata Harvesting</a> (OAI-PMH) version 2.0 as a data provider. This is accomplished using the <a class="ulink" href="http://www.oclc.org/research/software/oai/cat.shtm" target="_top">OAICat framework from OCLC</a>.</p><p>The DSpace build process builds a Web application archive, <code class="literal">[dspace-source]/build/oai.war</code>), in much the same way as <a class="link" href="ch09.html#docbook-application.html-webui_build">the Web UI build process</a> described above. The only differences are that the JSPs are not included, and <code class="literal">[dspace-source]/etc/oai-web.xml</code> is used as the deployment descriptor. This 'webapp' is deployed to receive and respond to OAI-PMH requests via HTTP. Note that typically it should <span class="emphasis"><em>not</em></span> be deployed on SSL (<code class="literal">https:</code> protocol). In a typical configuration, this is deployed at <code class="literal">oai</code>, for example:</p><pre class="screen">
 http://dspace.myu.edu/oai/request?verb=Identify
 </pre><p>The 'base URL' of this DSpace deployment would be:</p><pre class="screen">
 http://dspace.myu.edu/oai/request
@@ -176,17 +176,17 @@ http://dspace.myu.edu/oai/request
             <code class="literal">oaicat.properties</code>
           </span></dt><dd><p> This resides as a template in <code class="literal">[dspace]/config/templates</code>, and the live version is written to <code class="literal">[dspace]/config</code>. You probably won't need to edit this; the <code class="literal">install-configs</code> script fills out the relevant deployment-specific parameters. You might want to change the <code class="literal">earliestDatestamp</code> field to accurately reflect the oldest datestamp in the system. (Note that this is the value of the <code class="literal">last_modified</code> column in the <code class="literal">Item</code> database table.)</p></dd><dt><span class="term">
             <code class="literal">oai-web.xml</code>
-          </span></dt><dd><p> This standard Java Servlet 'deployment descriptor' is stored in the source as <code class="literal">[dspace-source]/etc/oai-web.xml</code>, and is written to <code class="literal">/dspace/oai/WEB-INF/web.xml</code>.</p></dd></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13424"></a>9.2.1.&nbsp;Sets</h3></div></div></div><p>OAI-PMH allows repositories to expose an hierarchy of sets in which records may be placed. A record can be in zero or more sets.</p><p>DSpace exposes collections as sets. The organization of communities is likely to change over time, and is therefore a less stable basis for selective harvesting.</p><p>Each collection has a corresponding OAI set, discoverable by harvesters via the ListSets verb. The setSpec is the Handle of the collection, with the ':' and '/' converted to underscores so that the Handle is a legal setSpec, for example:</p><pre class="screen">
+          </span></dt><dd><p> This standard Java Servlet 'deployment descriptor' is stored in the source as <code class="literal">[dspace-source]/etc/oai-web.xml</code>, and is written to <code class="literal">/dspace/oai/WEB-INF/web.xml</code>.</p></dd></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134A4"></a>9.2.1.&nbsp;Sets</h3></div></div></div><p>OAI-PMH allows repositories to expose an hierarchy of sets in which records may be placed. A record can be in zero or more sets.</p><p>DSpace exposes collections as sets. The organization of communities is likely to change over time, and is therefore a less stable basis for selective harvesting.</p><p>Each collection has a corresponding OAI set, discoverable by harvesters via the ListSets verb. The setSpec is the Handle of the collection, with the ':' and '/' converted to underscores so that the Handle is a legal setSpec, for example:</p><pre class="screen">
 hdl_1721.1_1234
-</pre><p>Naturally enough, the collection name is also the name of the corresponding set.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13433"></a>9.2.2.&nbsp;Unique Identifier</h3></div></div></div><p>Every item in OAI-PMH data repository must have an unique identifier, which must conform to the URI syntax. As of DSpace 1.2, Handles are not used; this is because in OAI-PMH, the OAI identifier identifies the <span class="emphasis"><em>metadata record</em></span> associated with the <span class="emphasis"><em>resource</em></span>. The <span class="emphasis"><em>resource</em></span> is the DSpace item, whose <span class="emphasis"><em>resource identifier</em></span> is the Handle. In practical terms, using the Handle for the OAI identifier may cause problems in the future if DSpace instances share items with the same Handles; the OAI metadata record identifiers should be different as the different DSpace instances would need to be harvested separately and may have different metadata for the item.</p><p>The OAI identifiers that DSpace uses are of the form:</p><p>
+</pre><p>Naturally enough, the collection name is also the name of the corresponding set.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134B3"></a>9.2.2.&nbsp;Unique Identifier</h3></div></div></div><p>Every item in OAI-PMH data repository must have an unique identifier, which must conform to the URI syntax. As of DSpace 1.2, Handles are not used; this is because in OAI-PMH, the OAI identifier identifies the <span class="emphasis"><em>metadata record</em></span> associated with the <span class="emphasis"><em>resource</em></span>. The <span class="emphasis"><em>resource</em></span> is the DSpace item, whose <span class="emphasis"><em>resource identifier</em></span> is the Handle. In practical terms, using the Handle for the OAI identifier may cause problems in the future if DSpace instances share items with the same Handles; the OAI metadata record identifiers should be different as the different DSpace instances would need to be harvested separately and may have different metadata for the item.</p><p>The OAI identifiers that DSpace uses are of the form:</p><p>
           <code class="literal">oai:host name:handle</code>
         </p><p>For example:</p><p>
           <code class="literal">oai:dspace.myu.edu:123456789/345</code>
-        </p><p>If you wish to use a different scheme, this can easily be changed by editing the value of <code class="literal">OAI_ID_PREFIX</code> at the top of the <code class="literal">org.dspace.app.oai.DSpaceOAICatalog</code> class. (You do not need to change the code if the above scheme works for you; the code picks up the host name and Handles automatically from the DSpace configuration.)</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1345F"></a>9.2.3.&nbsp;Access control</h3></div></div></div><p>OAI provides no authentication/authorisation details, although these could be implemented using standard HTTP methods. It is assumed that all access will be anonymous for the time being.</p><p>A question is, "is all metadata public?" Presently the answer to this is yes; all metadata is exposed via OAI-PMH, even if the item has restricted access policies. The reasoning behind this is that people who do actually have permission to read a restricted item should still be able to use OAI-based services to discover the content.</p><p>If in the future, this 'expose all metadata' approach proves unsatisfactory for any reason, it should be possible to expose only publicly readable metadata. The authorisation system has separate permissions for READing and item and READing the content (bitstreams) within it. This means the system can differentiate between an item with public metadata and hidden content, and an item with hidden metadata as well as hidden content. In this case the OAI data repository should only expose items those with anonymous READ access, so it can hide the existence of records to the outside world completely. In this scenario, one should be wary of protected items that are made public after a time. When this happens, the items are "new" from the OAI-PMH perspective.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13469"></a>9.2.4.&nbsp;Modification Date (OAI Date Stamp)</h3></div></div></div><p>OAI-PMH harvesters need to know when a record has been created, changed or deleted. DSpace keeps track of a 'last modified' date for each item in the system, and this date is used for the OAI-PMH date stamp. This means that any changes to the metadata (e.g. admins correcting a field, or a withdrawal) will be exposed to harvesters.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1346F"></a>9.2.5.&nbsp;'About' Information</h3></div></div></div><p>As part of each record given out to a harvester, there is an optional, repeatable "about" section which can be filled out in any (XML-schema conformant) way. Common uses are for provenance and rights information, and there are schemas in use by OAI communities for this. Presently DSpace does not provide any of this information.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13475"></a>9.2.6.&nbsp;Deletions</h3></div></div></div><p>DSpace keeps track of deletions (withdrawals). These are exposed via OAI, which has a specific mechansim for dealing with this. Since DSpace keeps a permanent record of withdrawn items, in the OAI-PMH sense DSpace supports deletions 'persistently'. This is as opposed to 'transient' deletion support, which would mean that deleted records are forgotten after a time.</p><p>Once an item has been withdrawn, OAI-PMH harvests of the date range in which the withdrawal occurred will find the 'deleted' record header. Harvests of a date range prior to the withdrawal will <span class="emphasis"><em>not</em></span> find the record, despite the fact that the record did exist at that time.</p><p>As an example of this, consider an item that was created on 2002-05-02 and withdrawn on 2002-10-06. A request to harvest the month 2002-10 will yield the 'record deleted' header. However, a harvest of the month 2002-05 will not yield the original record.</p><p>Note that presently, the deletion of 'expunged' items is not exposed through OAI.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13484"></a>9.2.7.&nbsp;Flow Control (Resumption Tokens)</h3></div></div></div><p>An OAI data provider can prevent any performance impact caused by harvesting by forcing a harvester to receive data in time-separated chunks. If the data provider receives a request for a lot of data, it can send part of the data with a resumption token. The harvester can then return later with the resumption token and continue.</p><p>DSpace supports resumption tokens for 'ListRecords' OAI-PMH requests. ListIdentifiers and ListSets requests do not produce a particularly high load on the system, so resumption tokens are not used for those requests.</p><p>Each OAI-PMH ListRecords request will return at most 100 records. This limit is set at the top of <code class="literal">org.dspace.app.oai.DSpaceOAICatalog.java</code> (<code class="literal">MAX_RECORDS</code>). A potential issue here is that if a harvest yields an exact multiple of <code class="literal">MAX_RECORDS</code>, the last operation will result in a harvest with no records in it. It is unclear from the OAI-PMH specification if this is acceptable.</p><p>When a resumption token is issued, the optional <code class="literal">completeListSize</code> and <code class="literal">cursor</code> attributes are not included. OAICat sets the <code class="literal">expirationDate</code> of the resumption token to one hour after it was issued, though in fact since DSpace resumption tokens contain all the information required to continue a request they do not actually expire.</p><p>Resumption tokens contain all the state information required to continue a request. The format is:</p><pre class="screen">
+        </p><p>If you wish to use a different scheme, this can easily be changed by editing the value of <code class="literal">OAI_ID_PREFIX</code> at the top of the <code class="literal">org.dspace.app.oai.DSpaceOAICatalog</code> class. (You do not need to change the code if the above scheme works for you; the code picks up the host name and Handles automatically from the DSpace configuration.)</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134DF"></a>9.2.3.&nbsp;Access control</h3></div></div></div><p>OAI provides no authentication/authorisation details, although these could be implemented using standard HTTP methods. It is assumed that all access will be anonymous for the time being.</p><p>A question is, "is all metadata public?" Presently the answer to this is yes; all metadata is exposed via OAI-PMH, even if the item has restricted access policies. The reasoning behind this is that people who do actually have permission to read a restricted item should still be able to use OAI-based services to discover the content.</p><p>If in the future, this 'expose all metadata' approach proves unsatisfactory for any reason, it should be possible to expose only publicly readable metadata. The authorisation system has separate permissions for READing and item and READing the content (bitstreams) within it. This means the system can differentiate between an item with public metadata and hidden content, and an item with hidden metadata as well as hidden content. In this case the OAI data repository should only expose items those with anonymous READ access, so it can hide the existence of records to the outside world completely. In this scenario, one should be wary of protected items that are made public after a time. When this happens, the items are "new" from the OAI-PMH perspective.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134E9"></a>9.2.4.&nbsp;Modification Date (OAI Date Stamp)</h3></div></div></div><p>OAI-PMH harvesters need to know when a record has been created, changed or deleted. DSpace keeps track of a 'last modified' date for each item in the system, and this date is used for the OAI-PMH date stamp. This means that any changes to the metadata (e.g. admins correcting a field, or a withdrawal) will be exposed to harvesters.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134EF"></a>9.2.5.&nbsp;'About' Information</h3></div></div></div><p>As part of each record given out to a harvester, there is an optional, repeatable "about" section which can be filled out in any (XML-schema conformant) way. Common uses are for provenance and rights information, and there are schemas in use by OAI communities for this. Presently DSpace does not provide any of this information.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134F5"></a>9.2.6.&nbsp;Deletions</h3></div></div></div><p>DSpace keeps track of deletions (withdrawals). These are exposed via OAI, which has a specific mechansim for dealing with this. Since DSpace keeps a permanent record of withdrawn items, in the OAI-PMH sense DSpace supports deletions 'persistently'. This is as opposed to 'transient' deletion support, which would mean that deleted records are forgotten after a time.</p><p>Once an item has been withdrawn, OAI-PMH harvests of the date range in which the withdrawal occurred will find the 'deleted' record header. Harvests of a date range prior to the withdrawal will <span class="emphasis"><em>not</em></span> find the record, despite the fact that the record did exist at that time.</p><p>As an example of this, consider an item that was created on 2002-05-02 and withdrawn on 2002-10-06. A request to harvest the month 2002-10 will yield the 'record deleted' header. However, a harvest of the month 2002-05 will not yield the original record.</p><p>Note that presently, the deletion of 'expunged' items is not exposed through OAI.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13504"></a>9.2.7.&nbsp;Flow Control (Resumption Tokens)</h3></div></div></div><p>An OAI data provider can prevent any performance impact caused by harvesting by forcing a harvester to receive data in time-separated chunks. If the data provider receives a request for a lot of data, it can send part of the data with a resumption token. The harvester can then return later with the resumption token and continue.</p><p>DSpace supports resumption tokens for 'ListRecords' OAI-PMH requests. ListIdentifiers and ListSets requests do not produce a particularly high load on the system, so resumption tokens are not used for those requests.</p><p>Each OAI-PMH ListRecords request will return at most 100 records. This limit is set at the top of <code class="literal">org.dspace.app.oai.DSpaceOAICatalog.java</code> (<code class="literal">MAX_RECORDS</code>). A potential issue here is that if a harvest yields an exact multiple of <code class="literal">MAX_RECORDS</code>, the last operation will result in a harvest with no records in it. It is unclear from the OAI-PMH specification if this is acceptable.</p><p>When a resumption token is issued, the optional <code class="literal">completeListSize</code> and <code class="literal">cursor</code> attributes are not included. OAICat sets the <code class="literal">expirationDate</code> of the resumption token to one hour after it was issued, though in fact since DSpace resumption tokens contain all the information required to continue a request they do not actually expire.</p><p>Resumption tokens contain all the state information required to continue a request. The format is:</p><pre class="screen">
 from/until/setSpec/offset
 </pre><p><code class="literal">from</code> and <code class="literal">until</code> are the ISO 8601 dates passed in as part of the original request, and <code class="literal">setSpec</code> is also taken from the original request. <code class="literal">offset</code> is the number of records that have already been sent to the harvester. For example:</p><pre class="screen">
 2003-01-01//hdl_1721_1_1234/300
-</pre><p>This means the harvest is 'from' <code class="literal">2003-01-01</code>, has no 'until' date, is for collection hdl:1721.1/1234, and 300 records have already been sent to the harvester. (Actually, if the original OAI-PMH request doesn't specify a 'from' or 'until, OAICat fills them out automatically to '0000-00-00T00:00:00Z' and '9999-12-31T23:59:59Z' respectively. This means DSpace resumption tokens will always have from and until dates in them.)</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N134C8"></a>9.3.&nbsp;<a name="docbook-application.html-structbuilder"></a>Community and Collection Structure Importer</h2></div></div></div><p>This command-line tool gives you the ability to import a community and collection structure directly from a source XML file. It is executed as follows:</p><p>
+</pre><p>This means the harvest is 'from' <code class="literal">2003-01-01</code>, has no 'until' date, is for collection hdl:1721.1/1234, and 300 records have already been sent to the harvester. (Actually, if the original OAI-PMH request doesn't specify a 'from' or 'until, OAICat fills them out automatically to '0000-00-00T00:00:00Z' and '9999-12-31T23:59:59Z' respectively. This means DSpace resumption tokens will always have from and until dates in them.)</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13548"></a>9.3.&nbsp;<a name="docbook-application.html-structbuilder"></a>Community and Collection Structure Importer</h2></div></div></div><p>This command-line tool gives you the ability to import a community and collection structure directly from a source XML file. It is executed as follows:</p><p>
         <code class="literal">[dspace]/bin/structure-builder -f [source xml] -o [output xml file] -e [administrator email]</code>
       </p><p>This will examine the contents of <code class="literal">[source xml]</code>, import the structure into DSpace while logged in as the supplied administrator, and then output the same structure to the output file, but including the handle for each imported community and collection as an attribute.</p><p>The source xml document needs to be in the following format:</p><pre class="screen">
 &lt;import_structure&gt;
@@ -248,9 +248,9 @@ from/until/setSpec/offset
                 &lt;/collection&gt;
         &lt;/community&gt;
 &lt;/import_structure&gt;
-</pre><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N134E7"></a>9.3.1.&nbsp;Limitation</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Currently this does not export community and collection structures, although it should only be a small modification to make it do so</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N134F0"></a>9.4.&nbsp;<a name="docbook-application.html-packager"></a>Package Importer and Exporter</h2></div></div></div><p>This command-line tool gives you access to the Packager plugins. It can <span class="emphasis"><em>ingest</em></span> a package to create a new DSpace Item, or <span class="emphasis"><em>disseminate</em></span> an Item as a package.</p><p>To see all the options, invoke it as:</p><pre class="screen">
+</pre><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13567"></a>9.3.1.&nbsp;Limitation</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Currently this does not export community and collection structures, although it should only be a small modification to make it do so</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13570"></a>9.4.&nbsp;<a name="docbook-application.html-packager"></a>Package Importer and Exporter</h2></div></div></div><p>This command-line tool gives you access to the Packager plugins. It can <span class="emphasis"><em>ingest</em></span> a package to create a new DSpace Item, or <span class="emphasis"><em>disseminate</em></span> an Item as a package.</p><p>To see all the options, invoke it as:</p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/packager --help
-</pre><p> This mode also displays a list of the names of package ingesters and disseminators that are available.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13509"></a>9.4.1.&nbsp;Ingesting</h3></div></div></div><p>To ingest a package from a file, give the command:</p><pre class="screen">
+</pre><p> This mode also displays a list of the names of package ingesters and disseminators that are available.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13589"></a>9.4.1.&nbsp;Ingesting</h3></div></div></div><p>To ingest a package from a file, give the command:</p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/packager -e <span class="emphasis"><em> user</em></span> -c <span class="emphasis"><em> handle</em></span> -t <span class="emphasis"><em> packager</em></span> <span class="emphasis"><em>
 	path</em></span>
 </pre><p> Where <span class="emphasis"><em>user</em></span> is the e-mail address of the E-Person under whose authority this runs; <span class="emphasis"><em>handle</em></span> is the Handle of the collection into which the Item is added, <span class="emphasis"><em>packager</em></span> is the plugin name of the package ingester to use, and <span class="emphasis"><em>path</em></span> is the path to the file to ingest (or <code class="literal">"-"</code> to read from the standard input).</p><p> Here is an example that loads a PDF file with internal metadata as a package:</p><pre class="screen">
@@ -259,7 +259,7 @@ from/until/setSpec/offset
 </pre><p>This example takes the result of retrieving a URL and ingests it:</p><pre class="screen">
 wget -O - http://alum.mit.edu/jarandom/my-thesis.pdf | \
 /dspace/bin/packager -e florey@mit.edu -c 1721.2/13  -t pdf -
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1353D"></a>9.4.2.&nbsp;Disseminating</h3></div></div></div><p>To disseminate an Item as a package, give the command:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N135BD"></a>9.4.2.&nbsp;Disseminating</h3></div></div></div><p>To disseminate an Item as a package, give the command:</p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/packager -e <span class="emphasis"><em> user</em></span> -d -i <span class="emphasis"><em> handle</em></span> -t   <span class="emphasis"><em> packager</em></span> <span class="emphasis"><em>
 	path</em></span>
 </pre><p> Where <span class="emphasis"><em>user</em></span> is the e-mail address of the E-Person under whose
@@ -270,10 +270,10 @@ wget -O - http://alum.mit.edu/jarandom/my-thesis.pdf | \
 	in the file "454.zip": <pre class="screen">
 /dspace/bin/packager -e florey@mit.edu -d -i 1721.2/454 -t METS
 	454.zip
-</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1356A"></a>9.4.3.&nbsp;METS packages</h3></div></div></div><p>DSpace 1.4 includes a package disseminator and matching ingester for the DSpace METS SIP (Submission Information Package) format. They were created to help end users prepare sets of digital resources and metadata for submission to the archive using well-defined standards such as <a class="ulink" href="http://www.loc.gov/standards/mets/" target="_top">METS</a>, <a class="ulink" href="http://www.loc.gov/standards/mods/" target="_top">MODS</a>, <a class="ulink" href="http://www.loc.gov/standards/premis/" target="_top">and PREMIS</a>. The plugin name is <code class="literal">METS</code> by default, and it uses MODS for descriptive metadata.</p><p>The DSpace METS SIP profile is available at: <a class="ulink" href="http://www.dspace.org/standards/METS/SIP/profilev1p0/metsipv1p0.pdf" target="_top">
+</pre></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N135EA"></a>9.4.3.&nbsp;METS packages</h3></div></div></div><p>DSpace 1.4 includes a package disseminator and matching ingester for the DSpace METS SIP (Submission Information Package) format. They were created to help end users prepare sets of digital resources and metadata for submission to the archive using well-defined standards such as <a class="ulink" href="http://www.loc.gov/standards/mets/" target="_top">METS</a>, <a class="ulink" href="http://www.loc.gov/standards/mods/" target="_top">MODS</a>, <a class="ulink" href="http://www.loc.gov/standards/premis/" target="_top">and PREMIS</a>. The plugin name is <code class="literal">METS</code> by default, and it uses MODS for descriptive metadata.</p><p>The DSpace METS SIP profile is available at: <a class="ulink" href="http://www.dspace.org/standards/METS/SIP/profilev1p0/metsipv1p0.pdf" target="_top">
             <code class="literal">http://www.dspace.org/standards/METS/SIP/profilev1p0/metsipv1p0.pdf</code>
           </a>
-.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1358A"></a>9.5.&nbsp;<a name="docbook-application.html-itemimporter"></a>Item Importer and Exporter</h2></div></div></div><p>DSpace has a set of command line tools for importing and exporting items in batches, using the DSpace simple archive format. The tools are not terribly robust, but are useful and are easily modified. They also give a good demonstration of how to implement your own item importer if desired.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13593"></a>9.5.1.&nbsp;DSpace simple archive format</h3></div></div></div><p>The basic concept behind the DSpace's simple archive format is to create an archive, which is directory full of items, with a subdirectory per item. Each item directory contains a file for the item's descriptive metadata, and the files that make up the item.</p><pre class="screen">
+.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1360A"></a>9.5.&nbsp;<a name="docbook-application.html-itemimporter"></a>Item Importer and Exporter</h2></div></div></div><p>DSpace has a set of command line tools for importing and exporting items in batches, using the DSpace simple archive format. The tools are not terribly robust, but are useful and are easily modified. They also give a good demonstration of how to implement your own item importer if desired.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13613"></a>9.5.1.&nbsp;DSpace simple archive format</h3></div></div></div><p>The basic concept behind the DSpace's simple archive format is to create an archive, which is directory full of items, with a subdirectory per item. Each item directory contains a file for the item's descriptive metadata, and the files that make up the item.</p><pre class="screen">
 archive_directory/
     item_000/
         dublin_core.xml -- qualified Dublin Core metadata
@@ -300,7 +300,7 @@ t;
 
 </pre><p>(Note the optional language tag attribute which notifies the system that the optional title is in French.)</p><p>The <code class="literal">contents</code> file simply enumerates, one file per line, the bitstream file names. The bitstream name may optionally be followed by the sequence:</p><p>
           <code class="literal">\tbundle:bundlename</code>
-        </p><p> where '\t' is the tab character and 'bundlename' is replaced by the name of the bundle to which the bitstream should be added. If no bundle is specified, the bitstream will be added to the 'ORIGINAL' bundle.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N135D0"></a>9.5.2.&nbsp;<a name="docbook-application.html-importingitems"></a>Importing Items</h3></div></div></div><p><span class="bold"><strong>Note:</strong></span> Before running the item importer over items previously exported from a DSpace instance, please first refer to <a class="ulink" href="application.html#transferitem" target="_top">Transferring Items Between DSpace Instances</a>.</p><p>The item importer is in <code class="literal">org.dspace.app.itemimport.ItemImport</code>, and is run with the <code class="literal">import</code> utility in the <code class="literal">dspace/bin</code> directory. Running it with -h gets the current command-line arguments. Another very important flag is the --test flag, which you can use with any command to simulate all of the actions it will perform without actually making any changes to your DSpace instance - very useful for validating your item directories before doing an import. In the importer's arguments you can use either the user's database ID or email address and the eperson ID, and the collection's database ID or handle as arguments. Currently with the importer you can add, remove, and replace items in a collection. If you specify more than one collection argument then the items will be imported to multiple collections, and the first collection specified becomes the "owning" collection. If there is an error and the import is aborted, there is a --resume flag that you can try to resume the import where you left off after you fix the error.</p><p>To add items to a collection with an EPerson as the submitter, type:</p><pre class="screen">
+        </p><p> where '\t' is the tab character and 'bundlename' is replaced by the name of the bundle to which the bitstream should be added. If no bundle is specified, the bitstream will be added to the 'ORIGINAL' bundle.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13650"></a>9.5.2.&nbsp;<a name="docbook-application.html-importingitems"></a>Importing Items</h3></div></div></div><p><span class="bold"><strong>Note:</strong></span> Before running the item importer over items previously exported from a DSpace instance, please first refer to <a class="link" href="ch09.html#docbook-application.html-transferitem">Transferring Items Between DSpace Instances</a>.</p><p>The item importer is in <code class="literal">org.dspace.app.itemimport.ItemImport</code>, and is run with the <code class="literal">import</code> utility in the <code class="literal">dspace/bin</code> directory. Running it with -h gets the current command-line arguments. Another very important flag is the --test flag, which you can use with any command to simulate all of the actions it will perform without actually making any changes to your DSpace instance - very useful for validating your item directories before doing an import. In the importer's arguments you can use either the user's database ID or email address and the eperson ID, and the collection's database ID or handle as arguments. Currently with the importer you can add, remove, and replace items in a collection. If you specify more than one collection argument then the items will be imported to multiple collections, and the first collection specified becomes the "owning" collection. If there is an error and the import is aborted, there is a --resume flag that you can try to resume the import where you left off after you fix the error.</p><p>To add items to a collection with an EPerson as the submitter, type:</p><pre class="screen">
 [dspace]/bin/import --add --eperson=joe@user.com 
 	--collection=collectionID --source=items_dir --mapfile=mapfile
 </pre><p>(or by using the short form)</p><pre class="screen">
@@ -311,17 +311,17 @@ t;
 </pre><p>The imported items listed in the map file would then be deleted. If you wish to replace previously imported items, you can give the command:</p><pre class="screen">
 [dspace]/bin/import --replace --eperson=joe@user.com
 	--collection=collectID --source=items_dir --mapfile=mapfile
-</pre><p>Replacing items uses the map file to replace the old items and still retain their handles.</p><p>The importer usually bypasses any workflow assigned to a collection, but adding the --workflow option will route the imported items through the workflow system.</p><p>The importer also has a --test flag that will simulate the entire import process without actually doing the import. This is extremely useful for verifying your import files before doing the import step.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13608"></a>9.5.3.&nbsp;<a name="docbook-application.html-exportingitems"></a>Exporting Items</h3></div></div></div><p>The item exporter can export a single item or a collection of items, and creates a DSpace simple archive for each item to be exported. To export a collection's items you type:</p><pre class="screen">
+</pre><p>Replacing items uses the map file to replace the old items and still retain their handles.</p><p>The importer usually bypasses any workflow assigned to a collection, but adding the --workflow option will route the imported items through the workflow system.</p><p>The importer also has a --test flag that will simulate the entire import process without actually doing the import. This is extremely useful for verifying your import files before doing the import step.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13688"></a>9.5.3.&nbsp;<a name="docbook-application.html-exportingitems"></a>Exporting Items</h3></div></div></div><p>The item exporter can export a single item or a collection of items, and creates a DSpace simple archive for each item to be exported. To export a collection's items you type:</p><pre class="screen">
 [dspace]/bin/export --type=COLLECTION --id=collID --dest=dest_dir
 	--number=seq_num
 </pre><p>The keyword <code class="literal">COLLECTION</code> means that you intend to export an entire collection. The ID can either be the database ID or the handle. The exporter will begin numbering the simple archives with the sequence number that you supply. To export a single item use the keyword <code class="literal">ITEM</code> and give the item ID as an argument:</p><pre class="screen">
 [dspace]/bin/export --type=ITEM --id=itemID --dest=dest_dir
 	--number=seq_num
-</pre><p>Each exported item will have an additional file in its directory, named 'handle'. This will contain the handle that was assigned to the item, and this file will be read by the importer so that items exported and then imported to another machine will retain the item's original handle.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13622"></a>9.6.&nbsp;<a name="docbook-application.html-transferitem"></a>Transferring Items Between DSpace Instances</h2></div></div></div><p>Where items are to be moved between DSpace instances (for example from a test DSpace into a production DSpace) the item exporter and item importer can be used in conjunction with a script to assist in this process.</p><p>After running the item exporter each <code class="literal">dublin_core.xml</code> file will contain metadata that was automatically added by DSpace. These fields are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> date.accessioned</p></li><li><p> date.available</p></li><li><p> date.issued</p></li><li><p> description.provenance</p></li><li><p> format.extent</p></li><li><p> format.mimetype</p></li><li><p> identifier.uri</p></li></ul></div><p>In order to avoid duplication of this metadata, run</p><p>
+</pre><p>Each exported item will have an additional file in its directory, named 'handle'. This will contain the handle that was assigned to the item, and this file will be read by the importer so that items exported and then imported to another machine will retain the item's original handle.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N136A2"></a>9.6.&nbsp;<a name="docbook-application.html-transferitem"></a>Transferring Items Between DSpace Instances</h2></div></div></div><p>Where items are to be moved between DSpace instances (for example from a test DSpace into a production DSpace) the item exporter and item importer can be used in conjunction with a script to assist in this process.</p><p>After running the item exporter each <code class="literal">dublin_core.xml</code> file will contain metadata that was automatically added by DSpace. These fields are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> date.accessioned</p></li><li><p> date.available</p></li><li><p> date.issued</p></li><li><p> description.provenance</p></li><li><p> format.extent</p></li><li><p> format.mimetype</p></li><li><p> identifier.uri</p></li></ul></div><p>In order to avoid duplication of this metadata, run</p><p>
         <code class="literal">dspace_migrate &lt;exported item directory&gt;</code>
       </p><p>prior to running the item importer. This will remove the above metadata items, except for date.issued - if the item has been published or publicly distributed before and identifier.uri - if it is not the handle, from the <code class="literal">dublin_core.xml</code> file and remove all <code class="literal">handle</code> files. It will then be safe to run the item exporter. Use</p><p>
         <code class="literal">dspace_migrate --help</code>
-      </p><p>for instructions on use of the script.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13661"></a>9.7.&nbsp;<a name="docbook-application.html-registration"></a>Registering (Not Importing) Bitstreams</h2></div></div></div><p>Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in storage accessible to DSpace. An example might be that there is a repository for existing digital assets. Rather than using the normal <a class="ulink" href="functional.html#ingest" target="_top">interactive ingest process</a> or the <a class="ulink" href="functional.html#importexport" target="_top">batch import</a> to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13672"></a>9.7.1.&nbsp;Accessible Storage</h3></div></div></div><p>To register an item its bitstreams must reside on storage accessible to DSpace and therefore referenced by an asset store number in <code class="literal">dspace.cfg</code>. The configuration file <code class="literal">dspace.cfg</code> establishes one or more asset stores through the use of an integer asset store number. This number relates to a directory in the DSpace host's file system or a set of SRB account parameters. This asset store number is described in <a class="ulink" href="configure.html#dspacecfg" target="_top">The <code class="literal">dspace.cfg</code> Configuration Properties File</a> section and in the <code class="literal">dspace.cfg</code> file itself. The asset store number(s) used for registered items should generally not be the value of the <code class="literal">assetstore.incoming</code> property since it is unlikely that that you will want to mix the bitstreams of normally ingested and imported items and registered items.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13690"></a>9.7.2.&nbsp;Registering Items Using the Item Importer</h3></div></div></div><p>DSpace uses the same import tool that is used for batch import except that several variations are employed to support registration. The discussion that follows assumes familiarity with the import tool.</p><p>The archive format for registration does not include the actual content files (bitstreams) being registered. The format is however a directory full of items to be registered, with a subdirectory per item. Each item directory contains a file for the item's descriptive metadata (<code class="literal">dublin_core.xml</code>) and a file listing the item's content files (<code class="literal">contents</code>), but not the actual content files themselves.</p><p>The <code class="literal">dublin_core.xml</code> file for item registration is exactly the same as for regular item import.</p><p>The <code class="literal">contents</code> file, like that for regular item import, lists the item's content files, one content file per line, but each line has the one of the following formats:</p><pre class="screen">
+      </p><p>for instructions on use of the script.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N136E1"></a>9.7.&nbsp;<a name="docbook-application.html-registration"></a>Registering (Not Importing) Bitstreams</h2></div></div></div><p>Registration is an alternate means of incorporating items, their metadata, and their bitstreams into DSpace by taking advantage of the bitstreams already being in storage accessible to DSpace. An example might be that there is a repository for existing digital assets. Rather than using the normal <a class="link" href="ch02.html#docbook-functional.html-ingest">interactive ingest process</a> or the <a class="link" href="ch02.html#docbook-functional.html-importexport">batch import</a> to furnish DSpace the metadata and to upload bitstreams, registration provides DSpace the metadata and the location of the bitstreams. DSpace uses a variation of the import tool to accomplish registration.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N136F2"></a>9.7.1.&nbsp;Accessible Storage</h3></div></div></div><p>To register an item its bitstreams must reside on storage accessible to DSpace and therefore referenced by an asset store number in <code class="literal">dspace.cfg</code>. The configuration file <code class="literal">dspace.cfg</code> establishes one or more asset stores through the use of an integer asset store number. This number relates to a directory in the DSpace host's file system or a set of SRB account parameters. This asset store number is described in <a class="link" href="">The <code class="literal">dspace.cfg</code> Configuration Properties File</a> section and in the <code class="literal">dspace.cfg</code> file itself. The asset store number(s) used for registered items should generally not be the value of the <code class="literal">assetstore.incoming</code> property since it is unlikely that that you will want to mix the bitstreams of normally ingested and imported items and registered items.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13710"></a>9.7.2.&nbsp;Registering Items Using the Item Importer</h3></div></div></div><p>DSpace uses the same import tool that is used for batch import except that several variations are employed to support registration. The discussion that follows assumes familiarity with the import tool.</p><p>The archive format for registration does not include the actual content files (bitstreams) being registered. The format is however a directory full of items to be registered, with a subdirectory per item. Each item directory contains a file for the item's descriptive metadata (<code class="literal">dublin_core.xml</code>) and a file listing the item's content files (<code class="literal">contents</code>), but not the actual content files themselves.</p><p>The <code class="literal">dublin_core.xml</code> file for item registration is exactly the same as for regular item import.</p><p>The <code class="literal">contents</code> file, like that for regular item import, lists the item's content files, one content file per line, but each line has the one of the following formats:</p><pre class="screen">
 -r -s n -f filepath
 -r -s n -f filepath\tbundle:bundlename
 -r -s n -f filepath\tbundle:bundlename\tpermissions: -[r|w] 'group
@@ -335,7 +335,7 @@ dsrun org.dspace.app.itemimport.ItemImport --add
 </pre><p>(or by using the short form)</p><pre class="screen">
 dsrun org.dspace.app.itemimport.ItemImport -a -e joe@user.com  -c
 	collectionID -s items_dir -m mapfile
-</pre><p>The <code class="literal">--workflow</code> and <code class="literal">--test</code> flags will function as described in <a class="ulink" href="application.html#importingitems" target="_top">Importing Items</a>.</p><p>The <code class="literal">--delete</code> flag will function as described in <a class="ulink" href="application.html#importingitems" target="_top">Importing Items</a> but the registered content files will not be removed from storage. See <a class="link" href="ch09.html#docbook-application.html-deletingregistereditems">Deleting Registered Items</a>.</p><p>The <code class="literal">--replace</code> flag will function as described in <a class="ulink" href="application.html#importingitems" target="_top">Importing Items</a> but care should be taken to consider different cases and implications. With old items and new items being registered or ingested normally, there are four combinations or cases to consider. Foremost, an old registered item deleted from DSpace using <code class="literal">--replace</code> will not be removed from the storage. See <a class="ulink" href="application.html#deletingregistereditems" target="_top">Deleting Registered Items</a>. where is resides. A new item added to DSpace using <code class="literal">--replace</code> will be ingested normally or will be registered depending on whether or not it is marked in the <code class="literal">contents</code> files with the -r.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13722"></a>9.7.3.&nbsp;Internal Identification and Retrieval of Registered Items</h3></div></div></div><p>Once an item has been registered, superficially it is indistinguishable from items ingested interactively or by batch import. But internally there are some differences:</p><p>First, the randomly generated internal ID is not used because DSpace does not control the file path and name of the bitstream. Instead, the file path and name are that specified in the <code class="literal">contents</code> file.</p><p>Second, the <code class="literal">store_number</code> column of the bitstream database row contains the asset store number specified in the <code class="literal">contents</code> file.</p><p>Third, the <code class="literal">internal_id</code> column of the bitstream database row contains a leading flag (<code class="literal">-R</code>) followed by the registered file path and name. For example, <code class="literal">-Rfilepath</code> where <code class="literal">filepath</code> is the file path and name relative to the asset store corresponding to the asset store number. The asset store could be traditional storage in the DSpace server's file system or an SRB account.</p><p>Fourth, an MD5 checksum is calculated by reading the registered file if it is in local storage. If the registerd file is in remote storage (say, SRB) a checksum is calulated on just the file name! This is an efficiency choice since registering a large number of large files that are in SRB would consume substantial network resources and time. A future option could be to have an SRB proxy process calculate MD5s and store them in SRB's metadata catalog (MCAT) for rapid retrieval. SRB offers such an option but it's not yet in production release.</p><p>Registered items and their bitstreams can be retrieved transparently just like normally ingested items.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1374E"></a>9.7.4.&nbsp;Exporting Registered Items</h3></div></div></div><p>Registered items may be exported as described in <a class="link" href="ch09.html#docbook-application.html-exportingitems">Exporting Items</a>. If so, the export directory will contain actual copies of the files being exported but the lines in the contents file will flag the files as registered. This means that if DSpace items are "round tripped" (see Transferring Items Between DSpace Instances) using the exporter and importer, the registered files in the export directory will again registered in DSpace instead of being uploaded and ingested normally.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13758"></a>9.7.5.&nbsp;METS Export of Registered Items</h3></div></div></div><p>The <a class="link" href="ch09.html#docbook-application.html-mets">METS Export Tool</a> can also be used but note the cautions described in that section and note that MD5 values for items in remote storage are actually MD5 values on just the file name.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13762"></a>9.7.6.&nbsp;<a name="docbook-application.html-deletingregistereditems"></a>Deleting Registered Items</h3></div></div></div><p>If a registered item is deleted from DSpace, either interactively or by using the <code class="literal">--delete</code> or <code class="literal">--replace</code> flags described in <a class="ulink" href="application.html#importingitems" target="_top">Importing Items</a>, the item will disappear from DSpace but it's registered content files will remain in place just as they were prior to registration. Bitstreams not registered but added by DSpace as part of registration, such as <code class="literal">license.txt</code> files, will be deleted.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1377A"></a>9.8.&nbsp;<a name="docbook-application.html-mets"></a>METS Tools</h2></div></div></div><p>The experimental (incomplete) METS export tool writes DSpace items to a filesystem with the metadata held in a more standard format based on METS.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13783"></a>9.8.1.&nbsp;The Export Tool</h3></div></div></div><p>The METS export tool is invoked via the command line like this:</p><pre class="screen">
+</pre><p>The <code class="literal">--workflow</code> and <code class="literal">--test</code> flags will function as described in <a class="link" href="ch09.html#docbook-application.html-importingitems">Importing Items</a>.</p><p>The <code class="literal">--delete</code> flag will function as described in <a class="link" href="ch09.html#docbook-application.html-importingitems">Importing Items</a> but the registered content files will not be removed from storage. See <a class="link" href="ch09.html#docbook-application.html-deletingregistereditems">Deleting Registered Items</a>.</p><p>The <code class="literal">--replace</code> flag will function as described in <a class="link" href="ch09.html#docbook-application.html-importingitems">Importing Items</a> but care should be taken to consider different cases and implications. With old items and new items being registered or ingested normally, there are four combinations or cases to consider. Foremost, an old registered item deleted from DSpace using <code class="literal">--replace</code> will not be removed from the storage. See <a class="link" href="ch09.html#docbook-application.html-deletingregistereditems">Deleting Registered Items</a>. where is resides. A new item added to DSpace using <code class="literal">--replace</code> will be ingested normally or will be registered depending on whether or not it is marked in the <code class="literal">contents</code> files with the -r.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N137A2"></a>9.7.3.&nbsp;Internal Identification and Retrieval of Registered Items</h3></div></div></div><p>Once an item has been registered, superficially it is indistinguishable from items ingested interactively or by batch import. But internally there are some differences:</p><p>First, the randomly generated internal ID is not used because DSpace does not control the file path and name of the bitstream. Instead, the file path and name are that specified in the <code class="literal">contents</code> file.</p><p>Second, the <code class="literal">store_number</code> column of the bitstream database row contains the asset store number specified in the <code class="literal">contents</code> file.</p><p>Third, the <code class="literal">internal_id</code> column of the bitstream database row contains a leading flag (<code class="literal">-R</code>) followed by the registered file path and name. For example, <code class="literal">-Rfilepath</code> where <code class="literal">filepath</code> is the file path and name relative to the asset store corresponding to the asset store number. The asset store could be traditional storage in the DSpace server's file system or an SRB account.</p><p>Fourth, an MD5 checksum is calculated by reading the registered file if it is in local storage. If the registerd file is in remote storage (say, SRB) a checksum is calulated on just the file name! This is an efficiency choice since registering a large number of large files that are in SRB would consume substantial network resources and time. A future option could be to have an SRB proxy process calculate MD5s and store them in SRB's metadata catalog (MCAT) for rapid retrieval. SRB offers such an option but it's not yet in production release.</p><p>Registered items and their bitstreams can be retrieved transparently just like normally ingested items.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N137CE"></a>9.7.4.&nbsp;Exporting Registered Items</h3></div></div></div><p>Registered items may be exported as described in <a class="link" href="ch09.html#docbook-application.html-exportingitems">Exporting Items</a>. If so, the export directory will contain actual copies of the files being exported but the lines in the contents file will flag the files as registered. This means that if DSpace items are "round tripped" (see Transferring Items Between DSpace Instances) using the exporter and importer, the registered files in the export directory will again registered in DSpace instead of being uploaded and ingested normally.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N137D8"></a>9.7.5.&nbsp;METS Export of Registered Items</h3></div></div></div><p>The <a class="link" href="ch09.html#docbook-application.html-mets">METS Export Tool</a> can also be used but note the cautions described in that section and note that MD5 values for items in remote storage are actually MD5 values on just the file name.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N137E2"></a>9.7.6.&nbsp;<a name="docbook-application.html-deletingregistereditems"></a>Deleting Registered Items</h3></div></div></div><p>If a registered item is deleted from DSpace, either interactively or by using the <code class="literal">--delete</code> or <code class="literal">--replace</code> flags described in <a class="link" href="ch09.html#docbook-application.html-importingitems">Importing Items</a>, the item will disappear from DSpace but it's registered content files will remain in place just as they were prior to registration. Bitstreams not registered but added by DSpace as part of registration, such as <code class="literal">license.txt</code> files, will be deleted.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N137FA"></a>9.8.&nbsp;<a name="docbook-application.html-mets"></a>METS Tools</h2></div></div></div><p>The experimental (incomplete) METS export tool writes DSpace items to a filesystem with the metadata held in a more standard format based on METS.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13803"></a>9.8.1.&nbsp;The Export Tool</h3></div></div></div><p>The METS export tool is invoked via the command line like this:</p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/dsrun org.dspace.app.mets.METSExport
 	--help
 </pre><p>The tool can export an individual item, the items within a given collection, or everything in the DSpace instance. To export an individual item, use:</p><pre class="screen">
@@ -347,20 +347,20 @@ dsrun org.dspace.app.itemimport.ItemImport -a -e joe@user.com  -c
 </pre><p>To export all the items DSpace, use:</p><pre class="screen">
 <span class="emphasis"><em> [dspace]</em></span>/bin/dsrun org.dspace.app.mets.METSExport
 	--all
-</pre><p>With any of the above forms, you can specify the base directory into which the items will be exported, using <code class="literal">--destination [directory]</code>. If this parameter is omitted, the current directory is used.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N137B4"></a>9.8.2.&nbsp;The AIP Format</h3></div></div></div><p>Each exported item is written to a separate directory, created under the base directory specified in the command-line arguments, or in the current directory if <code class="literal">--destination</code> is omitted. The name of each directory is the Handle, URL-encoded so that the directory name is 'legal'.</p><p>Within each item directory is a <code class="literal">mets.xml</code> file which contains the METS-encoded metadata for the item. Bitstreams in the item are also stored in the directory. Their filenames are their MD5 checksums, firstly for easy integrity checking, and also to avoid any problems with 'special characters' in the filenames that were legal on the original filing system they came from but are illegal in the server filing system. The <code class="literal">mets.xml</code> file includes XLink pointers to these bitstream files.</p><p>An example AIP might look like this:</p><div class="itemizedlist"><ul type="disc"><li><p>
+</pre><p>With any of the above forms, you can specify the base directory into which the items will be exported, using <code class="literal">--destination [directory]</code>. If this parameter is omitted, the current directory is used.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13834"></a>9.8.2.&nbsp;The AIP Format</h3></div></div></div><p>Each exported item is written to a separate directory, created under the base directory specified in the command-line arguments, or in the current directory if <code class="literal">--destination</code> is omitted. The name of each directory is the Handle, URL-encoded so that the directory name is 'legal'.</p><p>Within each item directory is a <code class="literal">mets.xml</code> file which contains the METS-encoded metadata for the item. Bitstreams in the item are also stored in the directory. Their filenames are their MD5 checksums, firstly for easy integrity checking, and also to avoid any problems with 'special characters' in the filenames that were legal on the original filing system they came from but are illegal in the server filing system. The <code class="literal">mets.xml</code> file includes XLink pointers to these bitstream files.</p><p>An example AIP might look like this:</p><div class="itemizedlist"><ul type="disc"><li><p>
               <code class="literal">hdl%3A123456789%2F8/</code>
               <div class="itemizedlist"><ul type="circle"><li><p><code class="literal">mets.xml</code>  -- METS metadata</p></li><li><p><code class="literal">184BE84F293342</code>  -- bitstream</p></li><li><p>
                     <code class="literal">3F9AD0389CB821</code>
                   </p></li><li><p>
                     <code class="literal">135FB82113C32D</code>
                   </p></li></ul></div>
-            </p></li></ul></div><p>The contents of the METS in the <code class="literal">mets.xml</code> file are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> A <code class="literal">dmdSec</code> (descriptive metadata section) containing the item's metadata in <a class="ulink" href="http://www.loc.gov/standards/mods/" target="_top">Metadata Object Description Schema (MODS)</a> XML. The Dublin Core descriptive metadata is mapped to MODS since there is no official qualified Dublin Core XML schema in existence as of yet, and the Library Application Profile of DC that DSpace uses includes some qualifiers that are not part of the <a class="ulink" href="http://dublincore.org/documents/dcmi-terms/" target="_top">DCMI Metadata Terms</a>.</p></li><li><p> An <code class="literal">amdSec</code> (administrative metadata section), which contains the a rights metadata element, which in turn contains the base64-encoded deposit license (the license the submitter granted as part of the submission process).</p></li><li><p> A <code class="literal">fileSec</code> containing a list of the bitstreams in the item. Each bundle constitutes a <code class="literal">fileGrp</code>. Each bitstream is represented by a <code class="literal">file</code> element, which contains an <code class="literal">FLocat</code> element with a simple XLink to the bitstream in the same directory as the <code class="literal">mets.xml</code> file. The <code class="literal">file</code> attributes consist of most of the basic technical metadata for the bitstream. Additionally, for those bitstreams that are thumbnails or text extracted from another bitstream in the item, those 'derived' bitstreams have the same <code class="literal">GROUPID</code> as the bitstream they were derived from, in order that clients understand that there is a relationship.</p><p>The <code class="literal">OWNERID</code> of each <code class="literal">file</code> is the <a class="ulink" href="functional.html#bitstream_ids" target="_top">'persistent' bitstream identifier</a> assigned by the DSpace instance. The <code class="literal">ID</code> and <code class="literal">GROUPID</code> attributes consist of the item's Handle, together with the bitstream's sequence ID, which underscores used in place of dots and slashes. For example, a bitstream with sequence ID 24, in the item <code class="literal">hdl:123.456/789</code> will have the <code class="literal">ID</code><code class="literal">123_456_789_24</code>. This is because <code class="literal">ID</code> and <code class="literal">GROUPID</code> attributes must be of type <code class="literal">xsd:id</code>.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13857"></a>9.8.3.&nbsp;Limitations</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> No corresponding import tool yet</p></li><li><p> No <code class="literal">structmap</code> section</p></li><li><p> Some technical metadata not written, e.g. the primary bitstream in a bundle, original filenames or descriptions.</p></li><li><p> Only the MIME type is stored, not the (finer grained) bitstream format.</p></li><li><p> Dublin Core to MODS mapping is very simple, probably needs verification</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1386F"></a>9.9.&nbsp;<a name="docbook-application.html-mediafilters"></a>MediaFilters: Transforming DSpace Content</h2></div></div></div><p>DSpace can apply filters to content/bitstreams, creating new content. Filters are included that extract text for <span class="bold"><strong>full-text searching</strong></span>, and create <span class="bold"><strong>thumbnails</strong></span> for items that contain images. The media filters are controlled by the <code class="literal">MediaFilterManager</code> which traverses the asset store, invoking the <code class="literal">MediaFilter</code> or <code class="literal">FormatFilter</code> classes on bitstreams. The media filter plugin configuration <code class="literal">filter.plugins</code> in <code class="literal">dspace.cfg</code> contains a list of all enabled media/format filter plugins (see <a class="ulink" href="configure.html#mediafilters" target="_top">Configuring Media Filters</a> for more information). The media filter system is intended to be run from the command line (or regularly as a cron task):</p><pre class="screen">
+            </p></li></ul></div><p>The contents of the METS in the <code class="literal">mets.xml</code> file are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p> A <code class="literal">dmdSec</code> (descriptive metadata section) containing the item's metadata in <a class="ulink" href="http://www.loc.gov/standards/mods/" target="_top">Metadata Object Description Schema (MODS)</a> XML. The Dublin Core descriptive metadata is mapped to MODS since there is no official qualified Dublin Core XML schema in existence as of yet, and the Library Application Profile of DC that DSpace uses includes some qualifiers that are not part of the <a class="ulink" href="http://dublincore.org/documents/dcmi-terms/" target="_top">DCMI Metadata Terms</a>.</p></li><li><p> An <code class="literal">amdSec</code> (administrative metadata section), which contains the a rights metadata element, which in turn contains the base64-encoded deposit license (the license the submitter granted as part of the submission process).</p></li><li><p> A <code class="literal">fileSec</code> containing a list of the bitstreams in the item. Each bundle constitutes a <code class="literal">fileGrp</code>. Each bitstream is represented by a <code class="literal">file</code> element, which contains an <code class="literal">FLocat</code> element with a simple XLink to the bitstream in the same directory as the <code class="literal">mets.xml</code> file. The <code class="literal">file</code> attributes consist of most of the basic technical metadata for the bitstream. Additionally, for those bitstreams that are thumbnails or text extracted from another bitstream in the item, those 'derived' bitstreams have the same <code class="literal">GROUPID</code> as the bitstream they were derived from, in order that clients understand that there is a relationship.</p><p>The <code class="literal">OWNERID</code> of each <code class="literal">file</code> is the <a class="link" href="ch02.html#docbook-functional.html-bitstream_ids">'persistent' bitstream identifier</a> assigned by the DSpace instance. The <code class="literal">ID</code> and <code class="literal">GROUPID</code> attributes consist of the item's Handle, together with the bitstream's sequence ID, which underscores used in place of dots and slashes. For example, a bitstream with sequence ID 24, in the item <code class="literal">hdl:123.456/789</code> will have the <code class="literal">ID</code><code class="literal">123_456_789_24</code>. This is because <code class="literal">ID</code> and <code class="literal">GROUPID</code> attributes must be of type <code class="literal">xsd:id</code>.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N138D7"></a>9.8.3.&nbsp;Limitations</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> No corresponding import tool yet</p></li><li><p> No <code class="literal">structmap</code> section</p></li><li><p> Some technical metadata not written, e.g. the primary bitstream in a bundle, original filenames or descriptions.</p></li><li><p> Only the MIME type is stored, not the (finer grained) bitstream format.</p></li><li><p> Dublin Core to MODS mapping is very simple, probably needs verification</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N138EF"></a>9.9.&nbsp;<a name="docbook-application.html-mediafilters"></a>MediaFilters: Transforming DSpace Content</h2></div></div></div><p>DSpace can apply filters to content/bitstreams, creating new content. Filters are included that extract text for <span class="bold"><strong>full-text searching</strong></span>, and create <span class="bold"><strong>thumbnails</strong></span> for items that contain images. The media filters are controlled by the <code class="literal">MediaFilterManager</code> which traverses the asset store, invoking the <code class="literal">MediaFilter</code> or <code class="literal">FormatFilter</code> classes on bitstreams. The media filter plugin configuration <code class="literal">filter.plugins</code> in <code class="literal">dspace.cfg</code> contains a list of all enabled media/format filter plugins (see <a class="link" href="ch05.html#docbook-configure.html-mediafilters">Configuring Media Filters</a> for more information). The media filter system is intended to be run from the command line (or regularly as a cron task):</p><pre class="screen">
 [dspace]/bin/filter-media
 </pre><p>With no options, this traverses the asset store, applying media filters to bitstreams, and skipping bitstreams that have already been filtered.</p><p>
         <span class="bold"><strong>Available Command-Line Options:</strong></span>
       </p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>Help</strong></span> : <code class="literal">[dspace]/bin/filter-media -h</code></p><div class="itemizedlist"><ul type="circle"><li><p> Display help message describing all command-line options.</p></li></ul></div></li><li><p><span class="bold"><strong>Force mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -f</code></p><div class="itemizedlist"><ul type="circle"><li><p> Apply filters to ALL bitstreams, even if they've already been filtered. If they've already been filtered, the previously filtered content is overwritten.</p></li></ul></div></li><li><p><span class="bold"><strong>Identifier mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -i 123456789/2</code></p><div class="itemizedlist"><ul type="circle"><li><p> Restrict processing to the community, collection, or item named by the identifier - by default, all bitstreams of all items in the repository are processed. The identifier must be a Handle, not a DB key. This option may be combined with any other option.</p></li></ul></div></li><li><p><span class="bold"><strong>Maximum mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -m 1000</code></p><div class="itemizedlist"><ul type="circle"><li><p> Suspend operation after the specified maximum number of items have been processed - by default, no limit exists. This option may be combined with any other option.</p></li></ul></div></li><li><p><span class="bold"><strong>No-Index mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -n</code></p><div class="itemizedlist"><ul type="circle"><li><p> Suppress index creation - by default, a new search index is created for full-text searching. This option suppresses index creation if you intend to run <code class="literal">index-all</code> elsewhere.</p></li></ul></div></li><li><p><span class="bold"><strong>Plugin mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -p "PDF Text Extractor","Word Text Extractor"</code></p><div class="itemizedlist"><ul type="circle"><li><p> Apply ONLY the filter plugin(s) listed (separated by commas). By default all named filters listed in the <code class="literal">filter.plugins</code> field of <code class="literal">dspace.cfg</code> are applied. This option may be combined with any other option. <span class="emphasis"><em>WARNING:</em></span> multiple plugin names must be separated by a comma (i.e. ',') and NOT a comma followed by a space (i.e. ', ').</p></li></ul></div></li><li><p><span class="bold"><strong>Skip mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -s 123456789/9,123456789/100</code></p><div class="itemizedlist"><ul type="circle"><li><p> SKIP the listed identifiers (separated by commas) during processing. The identifiers must be Handles (not DB Keys). They may refer to items, collections or communities which should be skipped. This option may be combined with any other option. <span class="emphasis"><em>WARNING:</em></span> multiple identifiers must be separated by a comma (i.e. ',') and NOT a comma followed by a space (i.e. ', ').</p></li><li><p> NOTE: If you have a large number of identifiers to skip, you may maintain this comma-separated list within a separate file (e.g. <code class="literal">filter-skiplist.txt</code>), and call it similar to the following: </p><div class="itemizedlist"><ul type="square"><li><p>
                     <code class="literal">[dspace]/bin/filter-media -s `less filter-skiplist.txt`</code>
-                  </p></li></ul></div></li></ul></div></li><li><p><span class="bold"><strong>Verbose mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -v</code></p><div class="itemizedlist"><ul type="circle"><li><p> Verbose mode - print all extracted text and other filter details to STDOUT.</p></li></ul></div></li></ul></div><p>Adding your own filters is done by creating a class which <code class="literal">implements</code> the <code class="literal">org.dspace.app.mediafilter.FormatFilter</code> interface. See the <a class="ulink" href="configure.html#newfilter" target="_top">Creating a new Media Filter</a> topic and comments in the source file FormatFilter.java for more information. In theory filters could be implemented in any programming language (C, Perl, etc.) However, they need to be invoked by the Java code in the Media Filter class that you create.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1393B"></a>9.10.&nbsp;<a name="docbook-application.html-filiator"></a>Sub-Community Management</h2></div></div></div><p>DSpace provides an administrative tool - 'CommunityFiliator' - for managing community sub-structure. Normally this structure seldom changes, but prior to the 1.2 release sub-communities were not supported, so this tool could be used to place existing pre-1.2 communities into a hierarchy. It has two operations, either establishing a community to sub-community relationship, or dis-establishing an existing relationship.</p><p>The familiar parent/child metaphor can be used to explain how it works. Every community in DSpace can be either a 'parent' community - meaning it has at least one sub-community, or a 'child' community - meaning it is a sub-community of another community, or both or neither. In these terms, an 'orphan' is a community that lacks a parent (although it can be a parent); 'orphans' are referred to as 'top-level' communities in the DSpace user-interface, since there is no parent community 'above' them. The first operation - establishing a parent/child relationship - can take place between any community and an orphan. The second operation - removing a parent/child relationship - will make the child an orphan.</p><p>Using the dsrun utility in the dspace/bin directory, the establish operation looks like this:</p><pre class="screen">
+                  </p></li></ul></div></li></ul></div></li><li><p><span class="bold"><strong>Verbose mode</strong></span> : <code class="literal">[dspace]/bin/filter-media -v</code></p><div class="itemizedlist"><ul type="circle"><li><p> Verbose mode - print all extracted text and other filter details to STDOUT.</p></li></ul></div></li></ul></div><p>Adding your own filters is done by creating a class which <code class="literal">implements</code> the <code class="literal">org.dspace.app.mediafilter.FormatFilter</code> interface. See the <a class="link" href="">Creating a new Media Filter</a> topic and comments in the source file FormatFilter.java for more information. In theory filters could be implemented in any programming language (C, Perl, etc.) However, they need to be invoked by the Java code in the Media Filter class that you create.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N139BB"></a>9.10.&nbsp;<a name="docbook-application.html-filiator"></a>Sub-Community Management</h2></div></div></div><p>DSpace provides an administrative tool - 'CommunityFiliator' - for managing community sub-structure. Normally this structure seldom changes, but prior to the 1.2 release sub-communities were not supported, so this tool could be used to place existing pre-1.2 communities into a hierarchy. It has two operations, either establishing a community to sub-community relationship, or dis-establishing an existing relationship.</p><p>The familiar parent/child metaphor can be used to explain how it works. Every community in DSpace can be either a 'parent' community - meaning it has at least one sub-community, or a 'child' community - meaning it is a sub-community of another community, or both or neither. In these terms, an 'orphan' is a community that lacks a parent (although it can be a parent); 'orphans' are referred to as 'top-level' communities in the DSpace user-interface, since there is no parent community 'above' them. The first operation - establishing a parent/child relationship - can take place between any community and an orphan. The second operation - removing a parent/child relationship - will make the child an orphan.</p><p>Using the dsrun utility in the dspace/bin directory, the establish operation looks like this:</p><pre class="screen">
 dsrun org.dspace.administer.CommunityFiliator --set --parent=parentID
 	--child=childID
 </pre><p>(or using the short form)</p><pre class="screen">
@@ -372,7 +372,7 @@ dsrun org.dspace.administer.CommunityFiliator --remove
 </pre><p>(or using the short form)</p><pre class="screen">
 dsrun org.dspace.administer.CommunityFiliator -r -p parentID -c
 	childID
-</pre><p>where '-r' or '--remove' means dis-establish the current relationship in which the community identified by 'parentID' is the parent of the community identified by 'childID'. The outcome will be that the 'childID' community will become an orphan, i.e. a top-level community.</p><p>If the required constraints of operation are violated, an error message will appear explaining the problem, and no change will be made. An example in a removal operation, where the stated child community does not have the stated parent community as its parent: "Error, child community not a child of parent community".</p><p>It is possible to effect arbitrary changes to the community hierarchy by chaining the basic operations together. For example, to move a child community from one parent to another, simply perform a 'remove' from its current parent (which will leave it an orphan), followed by a 'set' to its new parent.</p><p>It is important to understand that when any operation is performed, all the sub-structure of the child community follows it. Thus, if a child has itself children (sub-communities), or collections, they will all move with it to its new 'location' in the community tree.</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre><p>where '-r' or '--remove' means dis-establish the current relationship in which the community identified by 'parentID' is the parent of the community identified by 'childID'. The outcome will be that the 'childID' community will become an orphan, i.e. a top-level community.</p><p>If the required constraints of operation are violated, an error message will appear explaining the problem, and no change will be made. An example in a removal operation, where the stated child community does not have the stated parent community as its parent: "Error, child community not a child of parent community".</p><p>It is possible to effect arbitrary changes to the community hierarchy by chaining the basic operations together. For example, to move a child community from one parent to another, simply perform a 'remove' from its current parent (which will leave it an orphan), followed by a 'set' to its new parent.</p><p>It is important to understand that when any operation is performed, all the sub-structure of the child community follows it. Thus, if a child has itself children (sub-communities), or collections, they will all move with it to its new 'location' in the community tree.</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch10.html b/dspace/docs/html/ch10.html
index d79227c383..5a7771979e 100644
--- a/dspace/docs/html/ch10.html
+++ b/dspace/docs/html/ch10.html
@@ -1,18 +1,18 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch09.html" title="Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer"><link rel="next" href="ch11.html" title="Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch09.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch11.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N13964"></a>Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch10.html#N13968">10.1. Core Classes</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13975">10.1.1. The Configuration Manager (ConfigurationManager)</a></span></dt><dt><span class="section"><a href="ch10.html#N139BE">10.1.2. Constants</a></span></dt><dt><span class="section"><a href="ch10.html#N139DC">10.1.3. Context</a></span></dt><dt><span class="section"><a href="ch10.html#N13A2A">10.1.4. Email</a></span></dt><dt><span class="section"><a href="ch10.html#N13A42">10.1.5. LogManager</a></span></dt><dt><span class="section"><a href="ch10.html#N13B26">10.1.6. Utils</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13B2F">10.2. Content Management API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13BD9">10.2.1. Other Classes</a></span></dt><dt><span class="section"><a href="ch10.html#N13BFD">10.2.2. Modifications</a></span></dt><dt><span class="section"><a href="ch10.html#N13C82">10.2.3. What's In Memory?</a></span></dt><dt><span class="section"><a href="ch10.html#N13CD2">10.2.4. Dublin Core Metadata</a></span></dt><dt><span class="section"><a href="ch10.html#N13DB3">10.2.5. Support for Other Metadata Schemas</a></span></dt><dt><span class="section"><a href="ch10.html#N13DD2">10.2.6. Packager Plugins</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13E0E">10.3. Plugin Manager</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13E17">10.3.1. Concepts</a></span></dt><dt><span class="section"><a href="ch10.html#N13E46">10.3.2. Using the Plugin Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N13EC6">10.3.3. Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N13F6D">10.3.4. Configuring Plugins</a></span></dt><dt><span class="section"><a href="ch10.html#N1402D">10.3.5. Validating the Configuration</a></span></dt><dt><span class="section"><a href="ch10.html#N1407D">10.3.6. Use Cases</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N140D0">10.4. Workflow System</a></span></dt><dt><span class="section"><a href="ch10.html#N14148">10.5. Administration Toolkit</a></span></dt><dt><span class="section"><a href="ch10.html#N14183">10.6. E-person/Group Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N141CA">10.7. Authorization</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N14253">10.7.1. Special Groups</a></span></dt><dt><span class="section"><a href="ch10.html#N14259">10.7.2. Miscellaneous Authorization Notes</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N1425F">10.8. Handle Manager/Handle Plugin</a></span></dt><dt><span class="section"><a href="ch10.html#N142D7">10.9. Search</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N14336">10.9.1. Our Lucene Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N14348">10.9.2. Indexed Fields</a></span></dt><dt><span class="section"><a href="ch10.html#N143FD">10.9.3. Harvesting API</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N1442C">10.10. Browse API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N144A9">10.10.1. Using the API</a></span></dt><dt><span class="section"><a href="ch10.html#N14508">10.10.2. Index Maintenance</a></span></dt><dt><span class="section"><a href="ch10.html#N14518">10.10.3. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N14533">10.11. History Recorder</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N1455A">10.11.1. Archival Events</a></span></dt><dt><span class="section"><a href="ch10.html#N14590">10.11.2. Serializations</a></span></dt><dt><span class="section"><a href="ch10.html#N1459D">10.11.3. Unique Ids</a></span></dt><dt><span class="section"><a href="ch10.html#N145AD">10.11.4. Storage</a></span></dt><dt><span class="section"><a href="ch10.html#N145C8">10.11.5. Example</a></span></dt><dt><span class="section"><a href="ch10.html#N145E1">10.11.6. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N145EB">10.12. Checksum checker</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13968"></a>10.1.&nbsp;<a name="docbook-business.html-core"></a>Core Classes</h2></div></div></div><p>The <code class="literal">org.dspace.core</code> package provides some basic classes that are used throughout the DSpace code.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13975"></a>10.1.1.&nbsp;The Configuration Manager (<code class="literal">ConfigurationManager</code>)</h3></div></div></div><p>The configuration manager is responsible for reading the main <code class="literal">dspace.cfg</code> properties file, managing the 'template' configuration files for other applications such as Apache, and for obtaining the text for e-mail messages.</p><p>The system is configured by editing the relevant files in <code class="literal">/dspace/config</code>, as described in the <a class="ulink" href="configure.html" target="_top">configuration section</a>.</p><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch09.html" title="Chapter&nbsp;9.&nbsp;DSpace System Documentation: Application Layer"><link rel="next" href="ch11.html" title="Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch09.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch11.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N139E4"></a>Chapter&nbsp;10.&nbsp;<a name="docbook-business.html"></a>DSpace System Documentation: Business Logic Layer</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch10.html#N139EA">10.1. Core Classes</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N139F7">10.1.1. The Configuration Manager (ConfigurationManager)</a></span></dt><dt><span class="section"><a href="ch10.html#N13A40">10.1.2. Constants</a></span></dt><dt><span class="section"><a href="ch10.html#N13A5E">10.1.3. Context</a></span></dt><dt><span class="section"><a href="ch10.html#N13AAC">10.1.4. Email</a></span></dt><dt><span class="section"><a href="ch10.html#N13AC4">10.1.5. LogManager</a></span></dt><dt><span class="section"><a href="ch10.html#N13BA8">10.1.6. Utils</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13BB1">10.2. Content Management API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13C5B">10.2.1. Other Classes</a></span></dt><dt><span class="section"><a href="ch10.html#N13C7F">10.2.2. Modifications</a></span></dt><dt><span class="section"><a href="ch10.html#N13D04">10.2.3. What's In Memory?</a></span></dt><dt><span class="section"><a href="ch10.html#N13D54">10.2.4. Dublin Core Metadata</a></span></dt><dt><span class="section"><a href="ch10.html#N13E35">10.2.5. Support for Other Metadata Schemas</a></span></dt><dt><span class="section"><a href="ch10.html#N13E54">10.2.6. Packager Plugins</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13E90">10.3. Plugin Manager</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13E99">10.3.1. Concepts</a></span></dt><dt><span class="section"><a href="ch10.html#N13EC8">10.3.2. Using the Plugin Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N13F48">10.3.3. Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N13FEF">10.3.4. Configuring Plugins</a></span></dt><dt><span class="section"><a href="ch10.html#N140AF">10.3.5. Validating the Configuration</a></span></dt><dt><span class="section"><a href="ch10.html#N140FF">10.3.6. Use Cases</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N14152">10.4. Workflow System</a></span></dt><dt><span class="section"><a href="ch10.html#N141CA">10.5. Administration Toolkit</a></span></dt><dt><span class="section"><a href="ch10.html#N14205">10.6. E-person/Group Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N1424C">10.7. Authorization</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N142D5">10.7.1. Special Groups</a></span></dt><dt><span class="section"><a href="ch10.html#N142DB">10.7.2. Miscellaneous Authorization Notes</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N142E1">10.8. Handle Manager/Handle Plugin</a></span></dt><dt><span class="section"><a href="ch10.html#N14359">10.9. Search</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N143B8">10.9.1. Our Lucene Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N143CA">10.9.2. Indexed Fields</a></span></dt><dt><span class="section"><a href="ch10.html#N1447F">10.9.3. Harvesting API</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N144AE">10.10. Browse API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N1452B">10.10.1. Using the API</a></span></dt><dt><span class="section"><a href="ch10.html#N1458A">10.10.2. Index Maintenance</a></span></dt><dt><span class="section"><a href="ch10.html#N1459A">10.10.3. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N145B5">10.11. History Recorder</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N145DC">10.11.1. Archival Events</a></span></dt><dt><span class="section"><a href="ch10.html#N14612">10.11.2. Serializations</a></span></dt><dt><span class="section"><a href="ch10.html#N1461F">10.11.3. Unique Ids</a></span></dt><dt><span class="section"><a href="ch10.html#N1462F">10.11.4. Storage</a></span></dt><dt><span class="section"><a href="ch10.html#N1464A">10.11.5. Example</a></span></dt><dt><span class="section"><a href="ch10.html#N14663">10.11.6. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N1466D">10.12. Checksum checker</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N139EA"></a>10.1.&nbsp;<a name="docbook-business.html-core"></a>Core Classes</h2></div></div></div><p>The <code class="literal">org.dspace.core</code> package provides some basic classes that are used throughout the DSpace code.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N139F7"></a>10.1.1.&nbsp;The Configuration Manager (<code class="literal">ConfigurationManager</code>)</h3></div></div></div><p>The configuration manager is responsible for reading the main <code class="literal">dspace.cfg</code> properties file, managing the 'template' configuration files for other applications such as Apache, and for obtaining the text for e-mail messages.</p><p>The system is configured by editing the relevant files in <code class="literal">/dspace/config</code>, as described in the <a class="link" href="ch05.html#docbook-configure.html">configuration section</a>.</p><p>
           <span class="bold"><strong>When editing configuration files for applications that DSpace uses, such as Apache, remember to edit the file in /dspace/config/templates and then run /dspace/bin/install-configs rather than editing the 'live' version directly!</strong></span>
         </p><p>The <code class="literal">ConfigurationManager</code> class can also be invoked as a command line tool, with two possible uses:</p><div class="itemizedlist"><ul type="disc"><li><p><pre class="screen">
 
                 <code class="literal"> /dspace/bin/install-configs</code>
 
               </pre>
- This processes and installs configuration files for other applications, as described in the <a class="ulink" href="configure.html#templates" target="_top">configuration section</a>.</p></li><li><p><pre class="screen">
+ This processes and installs configuration files for other applications, as described in the <a class="link" href="ch05.html#docbook-configure.html-templates">configuration section</a>.</p></li><li><p><pre class="screen">
 
                 <code class="literal"> /dspace/bin/dsrun
 	org.dspace.core.ConfigurationManager -property
 	property.name</code>
 
               </pre>
- This writes the value of <code class="literal">property.name</code> from <code class="literal">dspace.cfg</code> to the standard output, so that shell scripts can access the DSpace configuration. For an example, see <code class="literal">/dspace/bin/start-handle-server</code>. If the property has no value, nothing is written.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N139BE"></a>10.1.2.&nbsp;Constants</h3></div></div></div><p>This class contains constants that are used to represent types of object and actions in the database. For example, authorization policies can relate to objects of different types, so the <code class="literal">resourcepolicy</code> table has columns <code class="literal">resource_id</code>, which is the internal ID of the object, and <code class="literal">resource_type_id</code>, which indicates whether the object is an item, collection, bitstream etc. The value of <code class="literal">resource_type_id</code> is taken from the <code class="literal">Constants</code> class, for example <code class="literal">Constants.ITEM</code>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N139DC"></a>10.1.3.&nbsp;Context</h3></div></div></div><p>The <code class="literal">Context</code> class is central to the DSpace operation. Any code that wishes to use the any API in the business logic layer must first create itself a <code class="literal">Context</code> object. This is akin to opening a connection to a database (which is in fact one of the things that happens.)</p><p>A context object is involved in most method calls and object constructors, so that the method or object has access to information about the current operation. When the context object is constructed, the following information is automatically initialized:</p><div class="itemizedlist"><ul type="disc"><li><p> A connection to the database. This is a transaction-safe connection. i.e. the 'auto-commit' flag is set to false.</p></li><li><p> A cache of content management API objects. Each time a content object is created (for example <code class="literal">Item</code> or <code class="literal">Bitstream</code>) it is stored in the <code class="literal">Context</code> object. If the object is then requested again, the cached copy is used. Apart from reducing database use, this addresses the problem of having two copies of the same object in memory in different states.</p></li></ul></div><p>The following information is also held in a context object, though it is the responsiblity of the application creating the context object to fill it out correctly:</p><div class="itemizedlist"><ul type="disc"><li><p> The current authenticated user, if any</p></li><li><p> Any 'special groups' the user is a member of. For example, a user might automatically be part of a particular group based on the IP address they are accessing DSpace from, even though they don't have an e-person record. Such a group is called a 'special group'.</p></li><li><p> Any extra information from the application layer that should be added to log messages that are written within this context. For example, the Web UI adds a session ID, so that when the logs are analysed the actions of a particular user in a particular session can be tracked.</p></li><li><p> A flag indicating whether authorization should be circumvented. This should only be used in rare, specific circumstances. For example, when first installing the system, there are no authorized administrators who would be able to create an administrator account!</p><p>As noted above, the public API is <span class="emphasis"><em>trusted</em></span>, so it is up to applications in the application layer to use this flag responsibly.</p></li></ul></div><p>Typical use of the context object will involve constructing one, and setting the current user if one is authenticated. Several operations may be performed using the context object. If all goes well, <code class="literal">complete</code> is called to commit the changes and free up any resources used by the context. If anything has gone wrong, <code class="literal">abort</code> is called to roll back any changes and free up the resources.</p><p>You should always <code class="literal">abort</code> a context if <span class="emphasis"><em>any</em></span> error happens during its lifespan; otherwise the data in the system may be left in an inconsistent state. You can also <code class="literal">commit</code> a context, which means that any changes are written to the database, and the context is kept active for further use.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13A2A"></a>10.1.4.&nbsp;Email</h3></div></div></div><p>Sending e-mails is pretty easy. Just use the configuration manager's <code class="literal">getEmail</code> method, set the arguments and recipients, and send.</p><p>The e-mail texts are stored in <code class="literal">/dspace/config/emails</code>. They are processed by the standard <code class="literal">java.text.MessageFormat</code>. At the top of each e-mail are listed the appropriate arguments that should be filled out by the sender. Example usage is shown in the <code class="literal">org.dspace.core.Email</code> Javadoc API documentation.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13A42"></a>10.1.5.&nbsp;LogManager</h3></div></div></div><p>The log manager consists of a method that creates a standard log header, and returns it as a string suitable for logging. Note that this class does not actually write anything to the logs; the log header returned should be logged directly by the sender using an appropriate Log4J call, so that information about where the logging is taking place is also stored.</p><p>The level of logging can be configured on a per-package or per-class basis by editing <code class="literal">/dspace/config/templates/log4j.properties</code> and then executing <code class="literal">/dspace/bin/install-configs</code>. You will need to stop and restart Tomcat for the changes to take effect.</p><p>A typical log entry looks like this:</p><p>
+ This writes the value of <code class="literal">property.name</code> from <code class="literal">dspace.cfg</code> to the standard output, so that shell scripts can access the DSpace configuration. For an example, see <code class="literal">/dspace/bin/start-handle-server</code>. If the property has no value, nothing is written.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13A40"></a>10.1.2.&nbsp;Constants</h3></div></div></div><p>This class contains constants that are used to represent types of object and actions in the database. For example, authorization policies can relate to objects of different types, so the <code class="literal">resourcepolicy</code> table has columns <code class="literal">resource_id</code>, which is the internal ID of the object, and <code class="literal">resource_type_id</code>, which indicates whether the object is an item, collection, bitstream etc. The value of <code class="literal">resource_type_id</code> is taken from the <code class="literal">Constants</code> class, for example <code class="literal">Constants.ITEM</code>.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13A5E"></a>10.1.3.&nbsp;Context</h3></div></div></div><p>The <code class="literal">Context</code> class is central to the DSpace operation. Any code that wishes to use the any API in the business logic layer must first create itself a <code class="literal">Context</code> object. This is akin to opening a connection to a database (which is in fact one of the things that happens.)</p><p>A context object is involved in most method calls and object constructors, so that the method or object has access to information about the current operation. When the context object is constructed, the following information is automatically initialized:</p><div class="itemizedlist"><ul type="disc"><li><p> A connection to the database. This is a transaction-safe connection. i.e. the 'auto-commit' flag is set to false.</p></li><li><p> A cache of content management API objects. Each time a content object is created (for example <code class="literal">Item</code> or <code class="literal">Bitstream</code>) it is stored in the <code class="literal">Context</code> object. If the object is then requested again, the cached copy is used. Apart from reducing database use, this addresses the problem of having two copies of the same object in memory in different states.</p></li></ul></div><p>The following information is also held in a context object, though it is the responsiblity of the application creating the context object to fill it out correctly:</p><div class="itemizedlist"><ul type="disc"><li><p> The current authenticated user, if any</p></li><li><p> Any 'special groups' the user is a member of. For example, a user might automatically be part of a particular group based on the IP address they are accessing DSpace from, even though they don't have an e-person record. Such a group is called a 'special group'.</p></li><li><p> Any extra information from the application layer that should be added to log messages that are written within this context. For example, the Web UI adds a session ID, so that when the logs are analysed the actions of a particular user in a particular session can be tracked.</p></li><li><p> A flag indicating whether authorization should be circumvented. This should only be used in rare, specific circumstances. For example, when first installing the system, there are no authorized administrators who would be able to create an administrator account!</p><p>As noted above, the public API is <span class="emphasis"><em>trusted</em></span>, so it is up to applications in the application layer to use this flag responsibly.</p></li></ul></div><p>Typical use of the context object will involve constructing one, and setting the current user if one is authenticated. Several operations may be performed using the context object. If all goes well, <code class="literal">complete</code> is called to commit the changes and free up any resources used by the context. If anything has gone wrong, <code class="literal">abort</code> is called to roll back any changes and free up the resources.</p><p>You should always <code class="literal">abort</code> a context if <span class="emphasis"><em>any</em></span> error happens during its lifespan; otherwise the data in the system may be left in an inconsistent state. You can also <code class="literal">commit</code> a context, which means that any changes are written to the database, and the context is kept active for further use.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13AAC"></a>10.1.4.&nbsp;Email</h3></div></div></div><p>Sending e-mails is pretty easy. Just use the configuration manager's <code class="literal">getEmail</code> method, set the arguments and recipients, and send.</p><p>The e-mail texts are stored in <code class="literal">/dspace/config/emails</code>. They are processed by the standard <code class="literal">java.text.MessageFormat</code>. At the top of each e-mail are listed the appropriate arguments that should be filled out by the sender. Example usage is shown in the <code class="literal">org.dspace.core.Email</code> Javadoc API documentation.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13AC4"></a>10.1.5.&nbsp;LogManager</h3></div></div></div><p>The log manager consists of a method that creates a standard log header, and returns it as a string suitable for logging. Note that this class does not actually write anything to the logs; the log header returned should be logged directly by the sender using an appropriate Log4J call, so that information about where the logging is taking place is also stored.</p><p>The level of logging can be configured on a per-package or per-class basis by editing <code class="literal">/dspace/config/templates/log4j.properties</code> and then executing <code class="literal">/dspace/bin/install-configs</code>. You will need to stop and restart Tomcat for the changes to take effect.</p><p>A typical log entry looks like this:</p><p>
           <code class="literal">2002-11-11 08:11:32,903 INFO org.dspace.app.webui.servlet.DSpaceServlet @ anonymous:session_id=BD84E7C194C2CF4BD0EC3A6CAD0142BB:view_item:handle=1721.1/1686</code>
         </p><p>This is breaks down like this:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>Date and time, milliseconds</p>
@@ -82,14 +82,14 @@
                   </p>
                 </td></tr></tbody></table></div><p>The above format allows the logs to be easily parsed and analysed. The <code class="literal">/dspace/bin/log-reporter</code> script is a simple tool for analysing logs. Try:</p><pre class="screen">
 /dspace/bin/log-reporter --help
-</pre><p>It's a good idea to 'nice' this log reporter to avoid an impact on server performance.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13B26"></a>10.1.6.&nbsp;Utils</h3></div></div></div><p><code class="literal">Utils</code> comtains miscellaneous utility method that are required in a variety of places throughout the code, and thus have no particular 'home' in a subsystem.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13B2F"></a>10.2.&nbsp;<a name="docbook-business.html-content"></a>Content Management API</h2></div></div></div><p>The content management API package <code class="literal">org.dspace.content</code> contains Java classes for reading and manipulating content stored in the DSpace system. This is the API that components in the application layer will probably use most.</p><p>Classes corresponding to the main elements in the <a class="ulink" href="functional.html#data_model" target="_top">DSpace data model</a> (<code class="literal">Community</code>, <code class="literal">Collection</code>, <code class="literal">Item</code>, <code class="literal">Bundle</code> and <code class="literal">Bitstream</code>) are sub-classes of the abstract class <code class="literal">DSpaceObject</code>. The <code class="literal">Item</code> object handles the Dublin Core metadata record.</p><p>Each class generally has one or more static <code class="literal">find</code> methods, which are used to instantiate content objects. Constructors do not have public access and are just used internally. The reasons for this are:</p><div class="itemizedlist"><ul type="disc"><li><p> "Constructing" an object may be misconstrued as the action of creating an object in the DSpace system, for example one might expect something like:</p><pre class="screen">
+</pre><p>It's a good idea to 'nice' this log reporter to avoid an impact on server performance.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13BA8"></a>10.1.6.&nbsp;Utils</h3></div></div></div><p><code class="literal">Utils</code> comtains miscellaneous utility method that are required in a variety of places throughout the code, and thus have no particular 'home' in a subsystem.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13BB1"></a>10.2.&nbsp;<a name="docbook-business.html-content"></a>Content Management API</h2></div></div></div><p>The content management API package <code class="literal">org.dspace.content</code> contains Java classes for reading and manipulating content stored in the DSpace system. This is the API that components in the application layer will probably use most.</p><p>Classes corresponding to the main elements in the <a class="link" href="ch02.html#docbook-functional.html-data_model">DSpace data model</a> (<code class="literal">Community</code>, <code class="literal">Collection</code>, <code class="literal">Item</code>, <code class="literal">Bundle</code> and <code class="literal">Bitstream</code>) are sub-classes of the abstract class <code class="literal">DSpaceObject</code>. The <code class="literal">Item</code> object handles the Dublin Core metadata record.</p><p>Each class generally has one or more static <code class="literal">find</code> methods, which are used to instantiate content objects. Constructors do not have public access and are just used internally. The reasons for this are:</p><div class="itemizedlist"><ul type="disc"><li><p> "Constructing" an object may be misconstrued as the action of creating an object in the DSpace system, for example one might expect something like:</p><pre class="screen">
 Context dsContent = new Context();
 Item myItem = new Item(context, id)
 </pre><p>to construct a brand new item in the system, rather than simply instantiating an in-memory instance of an object in the system.</p></li><li><p> <code class="literal">find</code> methods may often be called with invalid IDs, and return <code class="literal">null</code> in such a case. A constructor would have to throw an exception in this case. A <code class="literal">null</code> return value from a static method can in general be dealt with more simply in code.</p></li><li><p> If an instantiation representing the same underlying archival entity already exists, the <code class="literal">find</code> method can simply return that same instantiation to avoid multiple copies and any inconsistencies which might result.</p></li></ul></div><p><code class="literal">Collection</code>, <code class="literal">Bundle</code> and <code class="literal">Bitstream</code> do not have <code class="literal">create</code> methods; rather, one has to create an object using the relevant method on the container. For example, to create a collection, one must invoke <code class="literal">createCollection</code> on the community that the collection is to appear in:</p><pre class="screen">
 Context context = new Context();
 Community existingCommunity = Community.find(context, 123);
 Collection myNewCollection = existingCommunity.createCollection();
-</pre><p>The primary reason for this is for determining authorization. In order to know whether an e-person may create an object, the system must know which container the object is to be added to. It makes no sense to create a collection outside of a community, and the authorization system does not have a policy for that.</p><p><code class="literal">Item</code>s are first created in the form of an implementation of <code class="literal">InProgressSubmission</code>. An <code class="literal">InProgressSubmission</code> represents an item under construction; once it is complete, it is installed into the main archive and added to the relevant collection by the <code class="literal">InstallItem</code> class. The <code class="literal">org.dspace.content</code> package provides an implementation of <code class="literal">InProgressSubmission</code> called <code class="literal">WorkspaceItem</code>; this is a simple implementation that contains some fields used by the Web submission UI. The <code class="literal">org.dspace.workflow</code> also contains an implementation called <code class="literal">WorkflowItem</code> which represents a submission undergoing a workflow process.</p><p>In the previous chapter there is an <a class="ulink" href="functional.html#ingest" target="_top">overview of the item ingest process</a> which should clarify the previous paragraph. Also see the section on <a class="link" href="ch10.html#docbook-business.html-workflow">the workflow system</a>.</p><p><code class="literal">Community</code> and <code class="literal">BitstreamFormat</code> do have static <code class="literal">create</code> methods; one must be a site administrator to have authorization to invoke these.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13BD9"></a>10.2.1.&nbsp;Other Classes</h3></div></div></div><p>Classes whose name begins <code class="literal">DC</code> are for manipulating Dublin Core metadata, as <a class="link" href="ch10.html#docbook-business.html-dublincore">explained below</a>.</p><p>The <code class="literal">FormatIdentifier</code> class attempts to guess the bitstream format of a particular bitstream. Presently, it does this simply by looking at any file extension in the bitstream name and matching it up with the file extensions associated with bitstream formats. Hopefully this can be greatly improved in the future!</p><p>The <code class="literal">ItemIterator</code> class allows items to be retrieved from storage one at a time, and is returned by methods that may return a large number of items, more than would be desirable to have in memory at once.</p><p>The <code class="literal">ItemComparator</code> class is an implementation of the standard <code class="literal">java.util.Comparator</code> that can be used to compare and order items based on a particular Dublin Core metadata field.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13BFD"></a>10.2.2.&nbsp;Modifications</h3></div></div></div><p>When creating, modifying or for whatever reason removing data with the content management API, it is important to know when changes happen in-memory, and when they occur in the physical DSpace storage.</p><p>Primarily, one should note that no change made using a particular <code class="literal">org.dspace.core.Context</code> object will actually be made in the underlying storage unless <code class="literal">complete</code> or <code class="literal">commit</code> is invoked on that <code class="literal">Context</code>. If anything should go wrong during an operation, the context should always be aborted by invoking <code class="literal">abort</code>, to ensure that no inconsistent state is written to the storage.</p><p>Additionally, some changes made to objects only happen in-memory. In these cases, invoking the <code class="literal">update</code> method lines up the in-memory changes to occur in storage when the <code class="literal">Context</code> is committed or completed. In general, methods that change any [meta]data field only make the change in-memory; methods that involve relationships with other objects in the system line up the changes to be committed with the context. See individual methods in the API Javadoc.</p><p>Some examples to illustrate this are shown below:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+</pre><p>The primary reason for this is for determining authorization. In order to know whether an e-person may create an object, the system must know which container the object is to be added to. It makes no sense to create a collection outside of a community, and the authorization system does not have a policy for that.</p><p><code class="literal">Item</code>s are first created in the form of an implementation of <code class="literal">InProgressSubmission</code>. An <code class="literal">InProgressSubmission</code> represents an item under construction; once it is complete, it is installed into the main archive and added to the relevant collection by the <code class="literal">InstallItem</code> class. The <code class="literal">org.dspace.content</code> package provides an implementation of <code class="literal">InProgressSubmission</code> called <code class="literal">WorkspaceItem</code>; this is a simple implementation that contains some fields used by the Web submission UI. The <code class="literal">org.dspace.workflow</code> also contains an implementation called <code class="literal">WorkflowItem</code> which represents a submission undergoing a workflow process.</p><p>In the previous chapter there is an <a class="link" href="ch02.html#docbook-functional.html-ingest">overview of the item ingest process</a> which should clarify the previous paragraph. Also see the section on <a class="link" href="ch10.html#docbook-business.html-workflow">the workflow system</a>.</p><p><code class="literal">Community</code> and <code class="literal">BitstreamFormat</code> do have static <code class="literal">create</code> methods; one must be a site administrator to have authorization to invoke these.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13C5B"></a>10.2.1.&nbsp;Other Classes</h3></div></div></div><p>Classes whose name begins <code class="literal">DC</code> are for manipulating Dublin Core metadata, as <a class="link" href="ch10.html#docbook-business.html-dublincore">explained below</a>.</p><p>The <code class="literal">FormatIdentifier</code> class attempts to guess the bitstream format of a particular bitstream. Presently, it does this simply by looking at any file extension in the bitstream name and matching it up with the file extensions associated with bitstream formats. Hopefully this can be greatly improved in the future!</p><p>The <code class="literal">ItemIterator</code> class allows items to be retrieved from storage one at a time, and is returned by methods that may return a large number of items, more than would be desirable to have in memory at once.</p><p>The <code class="literal">ItemComparator</code> class is an implementation of the standard <code class="literal">java.util.Comparator</code> that can be used to compare and order items based on a particular Dublin Core metadata field.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13C7F"></a>10.2.2.&nbsp;Modifications</h3></div></div></div><p>When creating, modifying or for whatever reason removing data with the content management API, it is important to know when changes happen in-memory, and when they occur in the physical DSpace storage.</p><p>Primarily, one should note that no change made using a particular <code class="literal">org.dspace.core.Context</code> object will actually be made in the underlying storage unless <code class="literal">complete</code> or <code class="literal">commit</code> is invoked on that <code class="literal">Context</code>. If anything should go wrong during an operation, the context should always be aborted by invoking <code class="literal">abort</code>, to ensure that no inconsistent state is written to the storage.</p><p>Additionally, some changes made to objects only happen in-memory. In these cases, invoking the <code class="literal">update</code> method lines up the in-memory changes to occur in storage when the <code class="literal">Context</code> is committed or completed. In general, methods that change any [meta]data field only make the change in-memory; methods that involve relationships with other objects in the system line up the changes to be committed with the context. See individual methods in the API Javadoc.</p><p>Some examples to illustrate this are shown below:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>
                     <pre class="screen">
 Context context = new Context();
@@ -136,7 +136,7 @@ context.complete();
                   </p>
                 </td><td>
                   <p>The bitstream <span class="bold"><strong>will</strong></span> be included in the bundle, since <code class="literal">update</code> doesn't need to be called</p>
-                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13C82"></a>10.2.3.&nbsp;What's In Memory?</h3></div></div></div><p>Instantiating some content objects also causes other content objects to be loaded into memory.</p><p>Instantiating a <code class="literal">Bitstream</code> object causes the appropriate <code class="literal">BitstreamFormat</code> object to be instantiated. Of course the <code class="literal">Bitstream</code> object does not load the underlying bits from the bitstream store into memory!</p><p>Instantiating a <code class="literal">Bundle</code> object causes the appropriate <code class="literal">Bitstream</code> objects (and hence <code class="literal">BitstreamFormat</code>s) to be instantiated.</p><p>Instantiating an <code class="literal">Item</code> object causes the appropriate <code class="literal">Bundle</code> objects (etc.) and hence <code class="literal">BitstreamFormat</code>s to be instantiated. All the Dublin Core metadata associated with that item are also loaded into memory.</p><p>The reasoning behind this is that for the vast majority of cases, anyone instantiating an item object is going to need information about the bundles and bitstreams within it, and this methodology allows that to be done in the most efficient way and is simple for the caller. For example, in the Web UI, the servlet (controller) needs to pass information about an item to the viewer (JSP), which needs to have all the information in-memory to display the item without further accesses to the database which may cause errors mid-display.</p><p>You do not need to worry about multiple in-memory instantiations of the same object, or any inconsistenties that may result; the <code class="literal">Context</code> object keeps a cache of the instantiated objects. The <code class="literal">find</code> methods of classes in <code class="literal">org.dspace.content</code> will use a cached object if one exists.</p><p>It may be that in enough cases this automatic instantiation of contained objects reduces performance in situations where it is important; if this proves to be true the API may be changed in the future to include a <code class="literal">loadContents</code> method or somesuch, or perhaps a Boolean parameter indicating what to do will be added to the <code class="literal">find</code> methods.</p><p>When a <code class="literal">Context</code> object is completed, aborted or garbage-collected, any objects instantiated using that context are invalidated and should not be used (in much the same way an AWT button is invalid if the window containing it is destroyed).</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13CD2"></a>10.2.4.&nbsp;<a name="docbook-business.html-dublincore"></a>Dublin Core Metadata</h3></div></div></div><p>The <code class="literal">DCValue</code> class is a simple container that represents a single Dublin Core element, optional qualifier, value and language. Note that since DSpace 1.4 the <code class="literal">MetadataValue</code> and associated classes are preferred (see <a class="link" href="ch10.html#docbook-business.html-otherschemas">Support for Other Metadata Schemas</a>). The other classes starting with <code class="literal">DC</code> are utility classes for handling types of data in Dublin Core, such as people's names and dates. As supplied, the DSpace registry of elements and qualifiers corresponds to the <a class="ulink" href="http://www.dublincore.org/documents/2002/09/24/library-application-profile/" target="_top">Library Application Profile</a> for Dublin Core. It should be noted that these utility classes assume that the values will be in a certain syntax, which will be true for all data generated within the DSpace system, but since Dublin Core does not always define strict syntax, this may not be true for Dublin Core originating outside DSpace.</p><p>Below is the specific syntax that DSpace expects various fields to adhere to:</p><div class="informaltable"><table border="0"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13D04"></a>10.2.3.&nbsp;What's In Memory?</h3></div></div></div><p>Instantiating some content objects also causes other content objects to be loaded into memory.</p><p>Instantiating a <code class="literal">Bitstream</code> object causes the appropriate <code class="literal">BitstreamFormat</code> object to be instantiated. Of course the <code class="literal">Bitstream</code> object does not load the underlying bits from the bitstream store into memory!</p><p>Instantiating a <code class="literal">Bundle</code> object causes the appropriate <code class="literal">Bitstream</code> objects (and hence <code class="literal">BitstreamFormat</code>s) to be instantiated.</p><p>Instantiating an <code class="literal">Item</code> object causes the appropriate <code class="literal">Bundle</code> objects (etc.) and hence <code class="literal">BitstreamFormat</code>s to be instantiated. All the Dublin Core metadata associated with that item are also loaded into memory.</p><p>The reasoning behind this is that for the vast majority of cases, anyone instantiating an item object is going to need information about the bundles and bitstreams within it, and this methodology allows that to be done in the most efficient way and is simple for the caller. For example, in the Web UI, the servlet (controller) needs to pass information about an item to the viewer (JSP), which needs to have all the information in-memory to display the item without further accesses to the database which may cause errors mid-display.</p><p>You do not need to worry about multiple in-memory instantiations of the same object, or any inconsistenties that may result; the <code class="literal">Context</code> object keeps a cache of the instantiated objects. The <code class="literal">find</code> methods of classes in <code class="literal">org.dspace.content</code> will use a cached object if one exists.</p><p>It may be that in enough cases this automatic instantiation of contained objects reduces performance in situations where it is important; if this proves to be true the API may be changed in the future to include a <code class="literal">loadContents</code> method or somesuch, or perhaps a Boolean parameter indicating what to do will be added to the <code class="literal">find</code> methods.</p><p>When a <code class="literal">Context</code> object is completed, aborted or garbage-collected, any objects instantiated using that context are invalidated and should not be used (in much the same way an AWT button is invalid if the window containing it is destroyed).</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13D54"></a>10.2.4.&nbsp;<a name="docbook-business.html-dublincore"></a>Dublin Core Metadata</h3></div></div></div><p>The <code class="literal">DCValue</code> class is a simple container that represents a single Dublin Core element, optional qualifier, value and language. Note that since DSpace 1.4 the <code class="literal">MetadataValue</code> and associated classes are preferred (see <a class="link" href="ch10.html#docbook-business.html-otherschemas">Support for Other Metadata Schemas</a>). The other classes starting with <code class="literal">DC</code> are utility classes for handling types of data in Dublin Core, such as people's names and dates. As supplied, the DSpace registry of elements and qualifiers corresponds to the <a class="ulink" href="http://www.dublincore.org/documents/2002/09/24/library-application-profile/" target="_top">Library Application Profile</a> for Dublin Core. It should be noted that these utility classes assume that the values will be in a certain syntax, which will be true for all data generated within the DSpace system, but since Dublin Core does not always define strict syntax, this may not be true for Dublin Core originating outside DSpace.</p><p>Below is the specific syntax that DSpace expects various fields to adhere to:</p><div class="informaltable"><table border="0"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>Element</strong></span>
                   </p>
@@ -208,7 +208,7 @@ context.complete();
                   <p>
                     <code class="literal">DCSeriesNumber</code>
                   </p>
-                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13DB3"></a>10.2.5.&nbsp;<a name="docbook-business.html-otherschemas"></a>Support for Other Metadata Schemas</h3></div></div></div><p>To support additional metadata schemas a new set of metadata classes have been added. These are backwards compatible with the DC classes and should be used rather than the DC specific classes whereever possible. Note that hierarchical metadata schemas are not currently supported, only flat schemas (such as DC) are able to be defined.</p><p>The <code class="literal">MetadataField</code> class describes a metadata field by schema, element and optional qualifier. The value of a <code class="literal">MetadataField</code> is described by a <code class="literal">MetadataValue</code> which is roughly equivalent to the older <code class="literal">DCValue</code> class. Finally the <code class="literal">MetadataSchema</code> class is used to describe supported schemas. The DC schema is supported by default. Refer to the javadoc for method details.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13DD2"></a>10.2.6.&nbsp;<a name="docbook-business.html-packager"></a>Packager Plugins</h3></div></div></div><p>The Packager plugins let you <span class="emphasis"><em>ingest</em></span> a package to create a new DSpace Object, and <span class="emphasis"><em>disseminate</em></span> a content Object as a package. A package is simply a data stream; its contents are defined by the packager plugin's implementation.</p><p>To ingest an object, which is currently only implemented for Items, the sequence of operations is:</p><div class="orderedlist"><ol type="1"><li><p> Get an instance of the chosen <code class="literal">PackageIngester</code> plugin.</p></li><li><p> Locate a Collection in which to create the new Item.</p></li><li><p> Call its <code class="literal">ingest</code> method, and get back a <code class="literal">WorkspaceItem</code>.</p></li></ol></div><p>The packager also takes a <code class="literal">PackageParameters</code> object, which is a property list of parameters specific to that packager which might be passed in from the user interface.</p><p>Here is an example package ingestion code fragment:</p><pre class="screen">
+                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13E35"></a>10.2.5.&nbsp;<a name="docbook-business.html-otherschemas"></a>Support for Other Metadata Schemas</h3></div></div></div><p>To support additional metadata schemas a new set of metadata classes have been added. These are backwards compatible with the DC classes and should be used rather than the DC specific classes whereever possible. Note that hierarchical metadata schemas are not currently supported, only flat schemas (such as DC) are able to be defined.</p><p>The <code class="literal">MetadataField</code> class describes a metadata field by schema, element and optional qualifier. The value of a <code class="literal">MetadataField</code> is described by a <code class="literal">MetadataValue</code> which is roughly equivalent to the older <code class="literal">DCValue</code> class. Finally the <code class="literal">MetadataSchema</code> class is used to describe supported schemas. The DC schema is supported by default. Refer to the javadoc for method details.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13E54"></a>10.2.6.&nbsp;<a name="docbook-business.html-packager"></a>Packager Plugins</h3></div></div></div><p>The Packager plugins let you <span class="emphasis"><em>ingest</em></span> a package to create a new DSpace Object, and <span class="emphasis"><em>disseminate</em></span> a content Object as a package. A package is simply a data stream; its contents are defined by the packager plugin's implementation.</p><p>To ingest an object, which is currently only implemented for Items, the sequence of operations is:</p><div class="orderedlist"><ol type="1"><li><p> Get an instance of the chosen <code class="literal">PackageIngester</code> plugin.</p></li><li><p> Locate a Collection in which to create the new Item.</p></li><li><p> Call its <code class="literal">ingest</code> method, and get back a <code class="literal">WorkspaceItem</code>.</p></li></ol></div><p>The packager also takes a <code class="literal">PackageParameters</code> object, which is a property list of parameters specific to that packager which might be passed in from the user interface.</p><p>Here is an example package ingestion code fragment:</p><pre class="screen">
     Collection collection = <span class="emphasis"><em> find target
 	collection</em></span>
      InputStream source = ...;
@@ -229,10 +229,10 @@ context.complete();
              .getNamedPlugin(PackageDisseminator.class, packageType);
 
      dip.disseminate(context, dso, params, destination);
-</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13E0E"></a>10.3.&nbsp;<a name="docbook-business.html-plugin"></a>Plugin Manager</h2></div></div></div><p>The PluginManager is a very simple component container. It creates and organizes components (plugins), and helps select a plugin in the cases where there are many possible choices. It also gives some limited control over the lifecycle of a plugin.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13E17"></a>10.3.1.&nbsp;Concepts</h3></div></div></div><p>The following terms are important in understanding the rest of this section:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>Plugin Interface</strong></span> A Java interface, the defining characteristic of a plugin. The consumer of a plugin asks for its plugin by interface.</p></li><li><p><span class="bold"><strong>Plugin</strong></span> a.k.a. Component, this is an instance of a class that implements a certain interface. It is interchangeable with other implementations, so that any of them may be "plugged in", hence the name. A Plugin is an instance of any class that implements the plugin interface.</p></li><li><p><span class="bold"><strong>Implementation class</strong></span> The actual class of a plugin. It may implement several plugin interfaces, but must implement at least one.</p></li><li><p><span class="bold"><strong>Name</strong></span> Plugin implementations can be distinguished from each other by name, a short String meant to symbolically represent the implementation class. They are called "named plugins". Plugins only need to be named when the caller has to make an active choice between them.</p></li><li><p><span class="bold"><strong>SelfNamedPlugin class</strong></span> Plugins that extend the <code class="literal">SelfNamedPlugin</code> class can take advantage of additional features of the Plugin Manager. Any class can be managed as a plugin, so it is not necessary, just possible.</p></li><li><p><span class="bold"><strong>Reusable</strong></span> Reusable plugins are only instantiated once, and the Plugin Manager returns the same (cached) instance whenever that same plugin is requested again. This behavior can be turned off if desired.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13E46"></a>10.3.2.&nbsp;Using the Plugin Manager</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13E4A"></a>Types of Plugin</h4></div></div></div><p>The Plugin Manager supports three different patterns of usage:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Singleton Plugins</strong></span> There is only one implementation class for the plugin. It is indicated in the configuration. This type of plugin chooses an implementation of a service, for the entire system, at configuration time. Your application just fetches the plugin for that interface and gets the configured-in choice. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getSinglePlugin()</a> method.</p></li><li><p><span class="bold"><strong>Sequence Plugins</strong></span> You need a sequence or series of plugins, to implement a mechanism like Stackable Authentication or a pipeline, where each plugin is called in order to contribute its implementation of a process to the whole. The Plugin Manager supports this by letting you configure a sequence of plugins for a given interface. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getPluginSequence()</a> method.</p></li><li><p><span class="bold"><strong>Named Plugins</strong></span> Use a named plugin when the application has to choose one plugin implementation out of many available ones. Each implementation is bound to one or more names (symbolic identifiers) in the configuration.</p><p>The name is just a string to be associated with the combination of implementation class and interface. It may contain any characters except for comma (,) and equals (=). It may contain embedded spaces. Comma is a special character used to separate names in the configuration entry.</p><p>Names must be unique within an interface: No plugin classes implementing the same interface may have the same name.</p><p>Think of plugin names as a controlled vocabulary -- for a given plugin interface, there is a set of names for which plugins can be found. The designer of a Named Plugin interface is responsible for deciding what the name means and how to derive it; for example, names of metadata crosswalk plugins may describe the target metadata format.</p><p>See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getNamedPlugin()</a> method and the getPluginNames() methods.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13E79"></a><a name="docbook-business.html-selfnamedplugin"></a>Self-Named Plugins</h4></div></div></div><p>Named plugins can get their names either from the configuration or, for a variant called self-named plugins, from within the plugin itself.</p><p>Self-named plugins are necessary because one plugin implementation can be configured itself to take on many "personalities", each of which deserves its own plugin name. It is already managing its own configuration for each of these personalities, so it makes sense to allow it to export them to the Plugin Manager rather than expecting the plugin configuration to be kept in sync with it own configuration.</p><p>An example helps clarify the point: There is a named plugin that does crosswalks, call it <code class="literal">CrosswalkPlugin</code>. It has several implementations that crosswalk some kind of metadata. Now we add a new plugin which uses XSL stylesheet transformation (XSLT) to crosswalk many types of metadata -- so the single plugin can act like many different plugins, depending on which stylesheet it employs.</p><p>This XSLT-crosswalk plugin has its own configuration that maps a Plugin Name to a stylesheet -- it has to, since of course the Plugin Manager doesn't know anything about stylesheets. It becomes a self-named plugin, so that it reads its configuration data, gets the list of names to which it can respond, and passes those on to the Plugin Manager.</p><p>When the Plugin Manager creates an instance of the XSLT-crosswalk, it records the Plugin Name that was responsible for that instance. The plugin can look at that Name later in order to configure itself correctly for the Name that created it. This mechanism is all part of the SelfNamedPlugin class which is part of any self-named plugin.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13E8E"></a>Obtaining a Plugin Instance</h4></div></div></div><p>The most common thing you will do with the Plugin Manager is obtain an instance of a plugin. To request a plugin, you must always specify the plugin interface you want. You will also supply a name when asking for a named plugin.</p><p>A sequence plugin is returned as an array of <code class="literal">Object</code>s since it is actually an ordered list of plugins.</p><p>See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getSinglePlugin(), getPluginSequence(), getNamedPlugin()</a> methods.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13EA0"></a>Lifecycle Management</h4></div></div></div><p>When <code class="literal">PluginManager</code> fulfills a request for a plugin, it checks whether the implementation class is reusable; if so, it creates one instance of that class and returns it for every subsequent request for that interface and name. If it is not reusable, a new instance is always created.</p><p>For reasons that will become clear later, the manager actually caches a separate instance of an implementation class for each name under which it can be requested.</p><p>You can ask the <code class="literal">PluginManager</code> to forget about (decache) a plugin instance, by releasing it. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">PluginManager.releasePlugin()</a> method. The manager will drop its reference to the plugin so the garbage collector can reclaim it. The next time that plugin/name combination is requested, it will create a new instance.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13EB6"></a>Getting Meta-Information</h4></div></div></div><p>The <code class="literal">PluginManager</code> can list all the names of the Named Plugins which implement an interface. You may need this, for example, to implement a menu in a user interface that presents a choice among all possible plugins. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getPluginNames()</a> method.</p><p>Note that it only returns the plugin name, so if you need a more sophisticated or meaningful "label" (i.e. a key into the I18N message catalog) then you should add a method to the plugin itself to return that.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13EC6"></a>10.3.3.&nbsp;Implementation</h3></div></div></div><p>Note: The <code class="literal">PluginManager</code> refers to interfaces and classes internally only by their names whenever possible, to avoid loading classes until absolutely necessary (i.e. to create an instance). As you'll see below, self-named classes still have to be loaded to query them for names, but for the most part it can avoid loading classes. This saves a lot of time at start-up and keeps the JVM memory footprint down, too. As the Plugin Manager gets used for more classes, this will become a greater concern.</p><p>The only downside of "on-demand" loading is that errors in the configuration don't get discovered right away. The solution is to call the <code class="literal">checkConfiguration()</code> method after making any changes to the configuration.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13ED6"></a><a name="docbook-business.html-pluginmethods"></a>PluginManager Class</h4></div></div></div><p>The <code class="literal">PluginManager</code> class is your main interface to the Plugin Manager. It behaves like a factory class that never gets instantiated, so its public methods are static.</p><p>Here are the public methods, followed by explanations:</p><div class="itemizedlist"><ul type="disc"><li><p><pre class="screen">
+</pre></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N13E90"></a>10.3.&nbsp;<a name="docbook-business.html-plugin"></a>Plugin Manager</h2></div></div></div><p>The PluginManager is a very simple component container. It creates and organizes components (plugins), and helps select a plugin in the cases where there are many possible choices. It also gives some limited control over the lifecycle of a plugin.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13E99"></a>10.3.1.&nbsp;Concepts</h3></div></div></div><p>The following terms are important in understanding the rest of this section:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>Plugin Interface</strong></span> A Java interface, the defining characteristic of a plugin. The consumer of a plugin asks for its plugin by interface.</p></li><li><p><span class="bold"><strong>Plugin</strong></span> a.k.a. Component, this is an instance of a class that implements a certain interface. It is interchangeable with other implementations, so that any of them may be "plugged in", hence the name. A Plugin is an instance of any class that implements the plugin interface.</p></li><li><p><span class="bold"><strong>Implementation class</strong></span> The actual class of a plugin. It may implement several plugin interfaces, but must implement at least one.</p></li><li><p><span class="bold"><strong>Name</strong></span> Plugin implementations can be distinguished from each other by name, a short String meant to symbolically represent the implementation class. They are called "named plugins". Plugins only need to be named when the caller has to make an active choice between them.</p></li><li><p><span class="bold"><strong>SelfNamedPlugin class</strong></span> Plugins that extend the <code class="literal">SelfNamedPlugin</code> class can take advantage of additional features of the Plugin Manager. Any class can be managed as a plugin, so it is not necessary, just possible.</p></li><li><p><span class="bold"><strong>Reusable</strong></span> Reusable plugins are only instantiated once, and the Plugin Manager returns the same (cached) instance whenever that same plugin is requested again. This behavior can be turned off if desired.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13EC8"></a>10.3.2.&nbsp;Using the Plugin Manager</h3></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13ECC"></a>Types of Plugin</h4></div></div></div><p>The Plugin Manager supports three different patterns of usage:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Singleton Plugins</strong></span> There is only one implementation class for the plugin. It is indicated in the configuration. This type of plugin chooses an implementation of a service, for the entire system, at configuration time. Your application just fetches the plugin for that interface and gets the configured-in choice. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getSinglePlugin()</a> method.</p></li><li><p><span class="bold"><strong>Sequence Plugins</strong></span> You need a sequence or series of plugins, to implement a mechanism like Stackable Authentication or a pipeline, where each plugin is called in order to contribute its implementation of a process to the whole. The Plugin Manager supports this by letting you configure a sequence of plugins for a given interface. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getPluginSequence()</a> method.</p></li><li><p><span class="bold"><strong>Named Plugins</strong></span> Use a named plugin when the application has to choose one plugin implementation out of many available ones. Each implementation is bound to one or more names (symbolic identifiers) in the configuration.</p><p>The name is just a string to be associated with the combination of implementation class and interface. It may contain any characters except for comma (,) and equals (=). It may contain embedded spaces. Comma is a special character used to separate names in the configuration entry.</p><p>Names must be unique within an interface: No plugin classes implementing the same interface may have the same name.</p><p>Think of plugin names as a controlled vocabulary -- for a given plugin interface, there is a set of names for which plugins can be found. The designer of a Named Plugin interface is responsible for deciding what the name means and how to derive it; for example, names of metadata crosswalk plugins may describe the target metadata format.</p><p>See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getNamedPlugin()</a> method and the getPluginNames() methods.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13EFB"></a><a name="docbook-business.html-selfnamedplugin"></a>Self-Named Plugins</h4></div></div></div><p>Named plugins can get their names either from the configuration or, for a variant called self-named plugins, from within the plugin itself.</p><p>Self-named plugins are necessary because one plugin implementation can be configured itself to take on many "personalities", each of which deserves its own plugin name. It is already managing its own configuration for each of these personalities, so it makes sense to allow it to export them to the Plugin Manager rather than expecting the plugin configuration to be kept in sync with it own configuration.</p><p>An example helps clarify the point: There is a named plugin that does crosswalks, call it <code class="literal">CrosswalkPlugin</code>. It has several implementations that crosswalk some kind of metadata. Now we add a new plugin which uses XSL stylesheet transformation (XSLT) to crosswalk many types of metadata -- so the single plugin can act like many different plugins, depending on which stylesheet it employs.</p><p>This XSLT-crosswalk plugin has its own configuration that maps a Plugin Name to a stylesheet -- it has to, since of course the Plugin Manager doesn't know anything about stylesheets. It becomes a self-named plugin, so that it reads its configuration data, gets the list of names to which it can respond, and passes those on to the Plugin Manager.</p><p>When the Plugin Manager creates an instance of the XSLT-crosswalk, it records the Plugin Name that was responsible for that instance. The plugin can look at that Name later in order to configure itself correctly for the Name that created it. This mechanism is all part of the SelfNamedPlugin class which is part of any self-named plugin.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13F10"></a>Obtaining a Plugin Instance</h4></div></div></div><p>The most common thing you will do with the Plugin Manager is obtain an instance of a plugin. To request a plugin, you must always specify the plugin interface you want. You will also supply a name when asking for a named plugin.</p><p>A sequence plugin is returned as an array of <code class="literal">Object</code>s since it is actually an ordered list of plugins.</p><p>See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getSinglePlugin(), getPluginSequence(), getNamedPlugin()</a> methods.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13F22"></a>Lifecycle Management</h4></div></div></div><p>When <code class="literal">PluginManager</code> fulfills a request for a plugin, it checks whether the implementation class is reusable; if so, it creates one instance of that class and returns it for every subsequent request for that interface and name. If it is not reusable, a new instance is always created.</p><p>For reasons that will become clear later, the manager actually caches a separate instance of an implementation class for each name under which it can be requested.</p><p>You can ask the <code class="literal">PluginManager</code> to forget about (decache) a plugin instance, by releasing it. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">PluginManager.releasePlugin()</a> method. The manager will drop its reference to the plugin so the garbage collector can reclaim it. The next time that plugin/name combination is requested, it will create a new instance.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13F38"></a>Getting Meta-Information</h4></div></div></div><p>The <code class="literal">PluginManager</code> can list all the names of the Named Plugins which implement an interface. You may need this, for example, to implement a menu in a user interface that presents a choice among all possible plugins. See the <a class="link" href="ch10.html#docbook-business.html-pluginmethods">getPluginNames()</a> method.</p><p>Note that it only returns the plugin name, so if you need a more sophisticated or meaningful "label" (i.e. a key into the I18N message catalog) then you should add a method to the plugin itself to return that.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13F48"></a>10.3.3.&nbsp;Implementation</h3></div></div></div><p>Note: The <code class="literal">PluginManager</code> refers to interfaces and classes internally only by their names whenever possible, to avoid loading classes until absolutely necessary (i.e. to create an instance). As you'll see below, self-named classes still have to be loaded to query them for names, but for the most part it can avoid loading classes. This saves a lot of time at start-up and keeps the JVM memory footprint down, too. As the Plugin Manager gets used for more classes, this will become a greater concern.</p><p>The only downside of "on-demand" loading is that errors in the configuration don't get discovered right away. The solution is to call the <code class="literal">checkConfiguration()</code> method after making any changes to the configuration.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13F58"></a><a name="docbook-business.html-pluginmethods"></a>PluginManager Class</h4></div></div></div><p>The <code class="literal">PluginManager</code> class is your main interface to the Plugin Manager. It behaves like a factory class that never gets instantiated, so its public methods are static.</p><p>Here are the public methods, followed by explanations:</p><div class="itemizedlist"><ul type="disc"><li><p><pre class="screen">
 static Object getSinglePlugin(Class intface)
     throws PluginConfigurationError;
-</pre> Returns an instance of the singleton (single) plugin implementing the given interface. There must be exactly one single plugin configured for this interface, otherwise the <code class="literal">PluginConfigurationError</code> is thrown.</p><p>Note that this is the only "get plugin" method which throws an exception. It is typically used at initialization time to set up a permanent part of the system so any failure is fatal.</p><p>See the <code class="literal">plugin.single</code> configuration key for configuration details.</p></li><li><p><code class="literal">static Object[] getPluginSequence(Class intface);</code> Returns instances of all plugins that implement the interface <code class="literal">intface</code>, in an <code class="literal">Array</code>. Returns an empty array if no there are no matching plugins.</p><p>The order of the plugins in the array is the same as their class names in the configuration's value field.</p><p>See the <code class="literal">plugin.sequence</code> configuration key for configuration details.</p></li><li><p><code class="literal">static Object getNamedPlugin(Class intface, String name);</code> Returns an instance of a plugin that implements the interface <code class="literal">intface</code> and is bound to a name matching name. If there is no matching plugin, it returns null. The names are matched by <code class="literal">String.equals()</code>.</p><p>See the <code class="literal">plugin.named</code> and <code class="literal">plugin.selfnamed</code> configuration keys for configuration details.</p></li><li><p><code class="literal">static void releasePlugin(Object plugin);</code> Tells the Plugin Manager to let go of any references to a reusable plugin, to prevent it from being given out again and to allow the object to be garbage-collected. Call this when a plugin instance must be taken out of circulation.</p></li><li><p><code class="literal">static String[] getAllPluginNames(Class intface);</code> Returns all of the names under which a named plugin implementing the interface <code class="literal">intface</code> can be requested (with <code class="literal">getNamedPlugin()</code>). The array is empty if there are no matches. Use this to populate a menu of plugins for interactive selection, or to document what the possible choices are.</p><p>The names are NOT returned in any predictable order, so you may wish to sort them first.</p><p>Note: Since a plugin may be bound to more than one name, the list of names this returns does not represent the list of plugins. To get the list of unique implementation classes corresponding to the names, you might have to eliminate duplicates (i.e. create a Set of classes).</p></li><li><p><code class="literal">static void checkConfiguration();</code> Validates the keys in the DSpace <code class="literal">ConfigurationManager</code> pertaining to the Plugin Manager and reports any errors by logging them. This is intended to be used interactively by a DSpace administrator, to check the configuration file after modifying it. See the section about <a class="link" href="ch10.html#docbook-business.html-confval">validating configuration</a> for details.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13F4C"></a>SelfNamedPlugin Class</h4></div></div></div><p>A named plugin implementation must extend this class if it wants to supply its own Plugin Name(s). See <a class="link" href="ch10.html#docbook-business.html-selfnamedplugin">Self-Named Plugins</a> for why this is sometimes necessary.</p><pre class="screen">
+</pre> Returns an instance of the singleton (single) plugin implementing the given interface. There must be exactly one single plugin configured for this interface, otherwise the <code class="literal">PluginConfigurationError</code> is thrown.</p><p>Note that this is the only "get plugin" method which throws an exception. It is typically used at initialization time to set up a permanent part of the system so any failure is fatal.</p><p>See the <code class="literal">plugin.single</code> configuration key for configuration details.</p></li><li><p><code class="literal">static Object[] getPluginSequence(Class intface);</code> Returns instances of all plugins that implement the interface <code class="literal">intface</code>, in an <code class="literal">Array</code>. Returns an empty array if no there are no matching plugins.</p><p>The order of the plugins in the array is the same as their class names in the configuration's value field.</p><p>See the <code class="literal">plugin.sequence</code> configuration key for configuration details.</p></li><li><p><code class="literal">static Object getNamedPlugin(Class intface, String name);</code> Returns an instance of a plugin that implements the interface <code class="literal">intface</code> and is bound to a name matching name. If there is no matching plugin, it returns null. The names are matched by <code class="literal">String.equals()</code>.</p><p>See the <code class="literal">plugin.named</code> and <code class="literal">plugin.selfnamed</code> configuration keys for configuration details.</p></li><li><p><code class="literal">static void releasePlugin(Object plugin);</code> Tells the Plugin Manager to let go of any references to a reusable plugin, to prevent it from being given out again and to allow the object to be garbage-collected. Call this when a plugin instance must be taken out of circulation.</p></li><li><p><code class="literal">static String[] getAllPluginNames(Class intface);</code> Returns all of the names under which a named plugin implementing the interface <code class="literal">intface</code> can be requested (with <code class="literal">getNamedPlugin()</code>). The array is empty if there are no matches. Use this to populate a menu of plugins for interactive selection, or to document what the possible choices are.</p><p>The names are NOT returned in any predictable order, so you may wish to sort them first.</p><p>Note: Since a plugin may be bound to more than one name, the list of names this returns does not represent the list of plugins. To get the list of unique implementation classes corresponding to the names, you might have to eliminate duplicates (i.e. create a Set of classes).</p></li><li><p><code class="literal">static void checkConfiguration();</code> Validates the keys in the DSpace <code class="literal">ConfigurationManager</code> pertaining to the Plugin Manager and reports any errors by logging them. This is intended to be used interactively by a DSpace administrator, to check the configuration file after modifying it. See the section about <a class="link" href="ch10.html#docbook-business.html-confval">validating configuration</a> for details.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13FCE"></a>SelfNamedPlugin Class</h4></div></div></div><p>A named plugin implementation must extend this class if it wants to supply its own Plugin Name(s). See <a class="link" href="ch10.html#docbook-business.html-selfnamedplugin">Self-Named Plugins</a> for why this is sometimes necessary.</p><pre class="screen">
 abstract class SelfNamedPlugin
 {
     // Your class must override this:
@@ -244,7 +244,7 @@ abstract class SelfNamedPlugin
 	overridden.
     public String getPluginInstanceName();
 }
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13F59"></a>Errors and Exceptions</h4></div></div></div><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13FDB"></a>Errors and Exceptions</h4></div></div></div><pre class="screen">
 public class PluginConfigurationError extends Error
 {
     public PluginConfigurationError(String message);
@@ -254,16 +254,16 @@ public class PluginInstantiationException extends RuntimeException
 {
     public PluginInstantiationException(String msg, Throwable cause)
 }
-</pre><p>This exception indicates a fatal error when instantiating a plugin class. It should only be thrown when something unexpected happens in the course of instantiating a plugin, e.g. an access error, class not found, etc. Simply not finding a class in the configuration is not an exception.</p><p>This is a <code class="literal">RuntimeException</code> so it doesn't have to be declared, and can be passed all the way up to a generalized fatal exception handler.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13F6D"></a>10.3.4.&nbsp;<a name="docbook-business.html-pluginconfig"></a>Configuring Plugins</h3></div></div></div><p>All of the Plugin Manager's configuration comes from the DSpace Configuration Manager, which is a Java Properties map. You can configure these characteristics of each plugin:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Interface</strong></span> : Classname of the Java interface which defines the plugin, including package name. e.g. <code class="literal">org.dspace.app.mediafilter.FormatFilter</code></p></li><li><p><span class="bold"><strong>Implementation Class</strong></span> : Classname of the implementation class, including package. e.g. <code class="literal">org.dspace.app.mediafilter.PDFFilter</code></p></li><li><p><span class="bold"><strong>Names</strong></span> : (Named plugins only) There are two ways to bind names to plugins: listing them in the value of a plugin.named.interface key, or configuring a class in <code class="literal">plugin.selfnamed.interface</code> which extends the <code class="literal">SelfNamedPlugin</code> class.</p></li><li><p><span class="bold"><strong>Reusable option</strong></span> : (Optional) This is declared in a <code class="literal">plugin.reusable</code> configuration line. Plugins are reusable by default, so you only need to configure the non-reusable ones.</p></li></ol></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13FA3"></a>Configuring Singleton (Single) Plugins</h4></div></div></div><p>This entry configures a Single Plugin for use with getSinglePlugin():</p><p>
+</pre><p>This exception indicates a fatal error when instantiating a plugin class. It should only be thrown when something unexpected happens in the course of instantiating a plugin, e.g. an access error, class not found, etc. Simply not finding a class in the configuration is not an exception.</p><p>This is a <code class="literal">RuntimeException</code> so it doesn't have to be declared, and can be passed all the way up to a generalized fatal exception handler.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N13FEF"></a>10.3.4.&nbsp;<a name="docbook-business.html-pluginconfig"></a>Configuring Plugins</h3></div></div></div><p>All of the Plugin Manager's configuration comes from the DSpace Configuration Manager, which is a Java Properties map. You can configure these characteristics of each plugin:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Interface</strong></span> : Classname of the Java interface which defines the plugin, including package name. e.g. <code class="literal">org.dspace.app.mediafilter.FormatFilter</code></p></li><li><p><span class="bold"><strong>Implementation Class</strong></span> : Classname of the implementation class, including package. e.g. <code class="literal">org.dspace.app.mediafilter.PDFFilter</code></p></li><li><p><span class="bold"><strong>Names</strong></span> : (Named plugins only) There are two ways to bind names to plugins: listing them in the value of a plugin.named.interface key, or configuring a class in <code class="literal">plugin.selfnamed.interface</code> which extends the <code class="literal">SelfNamedPlugin</code> class.</p></li><li><p><span class="bold"><strong>Reusable option</strong></span> : (Optional) This is declared in a <code class="literal">plugin.reusable</code> configuration line. Plugins are reusable by default, so you only need to configure the non-reusable ones.</p></li></ol></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14025"></a>Configuring Singleton (Single) Plugins</h4></div></div></div><p>This entry configures a Single Plugin for use with getSinglePlugin():</p><p>
             <code class="literal">plugin.single.interface = classname</code>
           </p><p>For example, this configures the class <code class="literal">org.dspace.checker.SimpleDispatcher</code> as the plugin for interface <code class="literal">org.dspace.checker.BitstreamDispatcher</code>:</p><p>
             <code class="literal">plugin.single.org.dspace.checker.BitstreamDispatcher=org.dspace.checker.SimpleDispatcher</code>
-          </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13FBF"></a>Configuring Sequence of Plugins</h4></div></div></div><p>This kind of configuration entry defines a Sequence Plugin, which is bound to a sequence of implementation classes. The key identifies the interface, and the value is a comma-separated list of classnames:</p><pre class="programlisting">plugin.sequence.interface = classname, ...</pre><p>The plugins are returned by <code class="literal">getPluginSequence()</code> in the same order as their classes are listed in the configuration value.</p><p>For example, this entry configures Stackable Authentication with three implementation classes:</p><pre class="screen">
+          </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14041"></a>Configuring Sequence of Plugins</h4></div></div></div><p>This kind of configuration entry defines a Sequence Plugin, which is bound to a sequence of implementation classes. The key identifies the interface, and the value is a comma-separated list of classnames:</p><pre class="programlisting">plugin.sequence.interface = classname, ...</pre><p>The plugins are returned by <code class="literal">getPluginSequence()</code> in the same order as their classes are listed in the configuration value.</p><p>For example, this entry configures Stackable Authentication with three implementation classes:</p><pre class="screen">
 plugin.sequence.org.dspace.eperson.AuthenticationMethod = \
             org.dspace.eperson.X509Authentication, \
             org.dspace.eperson.PasswordAuthentication, \
             edu.mit.dspace.MITSpecialGroup
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N13FD3"></a>Configuring Named Plugins</h4></div></div></div><p>There are two ways of configuring named plugins:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Plugins Named in the Configuration</strong></span> A named plugin which gets its name(s) from the configuration is listed in this kind of entry:</p><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14055"></a>Configuring Named Plugins</h4></div></div></div><p>There are two ways of configuring named plugins:</p><div class="orderedlist"><ol type="1"><li><p><span class="bold"><strong>Plugins Named in the Configuration</strong></span> A named plugin which gets its name(s) from the configuration is listed in this kind of entry:</p><p>
                 <code class="literal">plugin.named.interface = classname = name [ , name.. ] [ classname = name.. ]</code>
               </p><p>The syntax of the configuration value is: classname, followed by an equal-sign and then at least one plugin name. Bind more names to the same implementation class by by adding them here, separated by commas. Names may include any character other than comma (,) and equal-sign (=).</p><p>For example, this entry creates one plugin with the names GIF, JPEG, and image/png, and another with the name TeX:</p><pre class="screen">
 plugin.named.org.dspace.app.mediafilter.MediaFilter = \
@@ -286,11 +286,11 @@ plugin.selfnamed.crosswalk.org.dspace.content.metadata.DisseminationCr
 osswalk = \
         org.dspace.content.metadata.MODSDisseminationCrosswalk, \
         org.dspace.content.metadata.XsltDisseminationCrosswalk
-</pre><p>NOTE: Since there can only be one key with plugin.selfnamed. followed by the interface name in the configuration, all of the plugin implementations must be configured in that entry. The <code class="literal">MODSDisseminationCrosswalk</code> class is only shown to illustrate this point.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14019"></a>Configuring the Reusable Status of a Plugin</h4></div></div></div><p>Plugins are assumed to be reusable by default, so you only need to configure the ones which you would prefer not to be reusable. The format is as follows:</p><p>
+</pre><p>NOTE: Since there can only be one key with plugin.selfnamed. followed by the interface name in the configuration, all of the plugin implementations must be configured in that entry. The <code class="literal">MODSDisseminationCrosswalk</code> class is only shown to illustrate this point.</p></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1409B"></a>Configuring the Reusable Status of a Plugin</h4></div></div></div><p>Plugins are assumed to be reusable by default, so you only need to configure the ones which you would prefer not to be reusable. The format is as follows:</p><p>
             <code class="literal">plugin.reusable.classname = ( true | false )</code>
           </p><p>For example, this marks the PDF plugin from the example above as non-reusable:</p><p>
             <code class="literal">plugin.reusable.org.dspace.app.mediafilter.PDFFilter = false</code>
-          </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1402D"></a>10.3.5.&nbsp;<a name="docbook-business.html-confval"></a>Validating the Configuration</h3></div></div></div><p>The Plugin Manager is very sensitive to mistakes in the DSpace configuration. Subtle errors can have unexpected consequnces that are hard to detect: for example, if there are two "plugin.single" entries for the same interface, one of them will be silently ignored.</p><p>To validate the Plugin Manager configuration, call the <code class="literal">PluginManager.checkConfiguration()</code> method. It looks for the following mistakes:</p><div class="itemizedlist"><ul type="disc"><li><p> Any duplicate keys starting with "plugin.".</p></li><li><p> Keys starting <code class="literal">plugin.single</code>, <code class="literal">plugin.sequence</code>, <code class="literal">plugin.named</code>, and <code class="literal">plugin.selfnamed</code> that don't include a valid interface.</p></li><li><p> Classnames in the configuration values that don't exist, or don't implement the plugin interface in the key.</p></li><li><p> Classes declared in plugin.selfnamed lines that don't extend the <code class="literal">SelfNamedPlugin</code> class.</p></li><li><p> Any name collisions among named plugins for a given interface.</p></li><li><p> Named plugin configuration entries without any names.</p></li><li><p> Classnames mentioned in <code class="literal">plugin.reusable</code> keys must exist and have been configured as a plugin implementation class.</p></li></ul></div><p>The <code class="literal">PluginManager</code> class also has a <code class="literal">main()</code> method which simply runs <code class="literal">checkConfiguration()</code>, so you can invoke it from the command line to test the validity of plugin configuration changes.</p><p>Eventually, someone should develop a general configuration-file sanity checker for DSpace, which would just call <code class="literal">PluginManager.checkConfiguration().</code></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1407D"></a>10.3.6.&nbsp;Use Cases</h3></div></div></div><p>Here are some usage examples to illustrate how the Plugin Manager works.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14083"></a>Managing the MediaFilter plugins transparently</h4></div></div></div><p>The existing DSpace 1.3 MediaFilterManager implementation has been largely replaced by the Plugin Manager. The MediaFilter classes become plugins named in the configuration. Refer to the <a class="ulink" href="configure.html#mediafilters" target="_top">configuration guide</a> for further details.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1408D"></a>A Singleton Plugin</h4></div></div></div><p>This shows how to configure and access a single anonymous plugin, such as the BitstreamDispatcher plugin:</p><p>Configuration:</p><p>
+          </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N140AF"></a>10.3.5.&nbsp;<a name="docbook-business.html-confval"></a>Validating the Configuration</h3></div></div></div><p>The Plugin Manager is very sensitive to mistakes in the DSpace configuration. Subtle errors can have unexpected consequnces that are hard to detect: for example, if there are two "plugin.single" entries for the same interface, one of them will be silently ignored.</p><p>To validate the Plugin Manager configuration, call the <code class="literal">PluginManager.checkConfiguration()</code> method. It looks for the following mistakes:</p><div class="itemizedlist"><ul type="disc"><li><p> Any duplicate keys starting with "plugin.".</p></li><li><p> Keys starting <code class="literal">plugin.single</code>, <code class="literal">plugin.sequence</code>, <code class="literal">plugin.named</code>, and <code class="literal">plugin.selfnamed</code> that don't include a valid interface.</p></li><li><p> Classnames in the configuration values that don't exist, or don't implement the plugin interface in the key.</p></li><li><p> Classes declared in plugin.selfnamed lines that don't extend the <code class="literal">SelfNamedPlugin</code> class.</p></li><li><p> Any name collisions among named plugins for a given interface.</p></li><li><p> Named plugin configuration entries without any names.</p></li><li><p> Classnames mentioned in <code class="literal">plugin.reusable</code> keys must exist and have been configured as a plugin implementation class.</p></li></ul></div><p>The <code class="literal">PluginManager</code> class also has a <code class="literal">main()</code> method which simply runs <code class="literal">checkConfiguration()</code>, so you can invoke it from the command line to test the validity of plugin configuration changes.</p><p>Eventually, someone should develop a general configuration-file sanity checker for DSpace, which would just call <code class="literal">PluginManager.checkConfiguration().</code></p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N140FF"></a>10.3.6.&nbsp;Use Cases</h3></div></div></div><p>Here are some usage examples to illustrate how the Plugin Manager works.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14105"></a>Managing the MediaFilter plugins transparently</h4></div></div></div><p>The existing DSpace 1.3 MediaFilterManager implementation has been largely replaced by the Plugin Manager. The MediaFilter classes become plugins named in the configuration. Refer to the <a class="link" href="ch05.html#docbook-configure.html-mediafilters">configuration guide</a> for further details.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1410F"></a>A Singleton Plugin</h4></div></div></div><p>This shows how to configure and access a single anonymous plugin, such as the BitstreamDispatcher plugin:</p><p>Configuration:</p><p>
             <code class="literal">plugin.single.org.dspace.checker.BitstreamDispatcher=org.dspace.checker.SimpleDispatcher</code>
           </p><p>The following code fragment shows how dispatcher, the service object, is initialized and used:</p><pre class="screen">
 BitstreamDispatcher dispatcher =
@@ -308,7 +308,7 @@ while (id != BitstreamDispatcher.SENTINEL)
 
      id = dispatcher.next();
 }
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N140A0"></a>Plugin that Names Itself</h4></div></div></div><p>This crosswalk plugin acts like many different plugins since it is configured with different XSL translation stylesheets. Since it already gets each of its stylesheets out of the DSpace configuration, it makes sense to have the plugin give PluginManager the names to which it answers instead of forcing someone to configure those names in two places (and try to keep them synchronized).</p><p>NOTE: Remember how <code class="literal">getPlugin()</code> caches a separate instance of an implementation class for every name bound to it? This is why: the instance can look at the name under which it was invoked and configure itself specifically for that name. Since the instance for each name might be different, the Plugin Manager has to cache a separate instance for each name.</p><p>Here is the configuration file listing both the plugin's own configuration and the <code class="literal">PluginManager</code> config line:</p><pre class="screen">
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14122"></a>Plugin that Names Itself</h4></div></div></div><p>This crosswalk plugin acts like many different plugins since it is configured with different XSL translation stylesheets. Since it already gets each of its stylesheets out of the DSpace configuration, it makes sense to have the plugin give PluginManager the names to which it answers instead of forcing someone to configure those names in two places (and try to keep them synchronized).</p><p>NOTE: Remember how <code class="literal">getPlugin()</code> caches a separate instance of an implementation class for every name bound to it? This is why: the instance can look at the name under which it was invoked and configure itself specifically for that name. Since the instance for each name might be different, the Plugin Manager has to cache a separate instance for each name.</p><p>Here is the configuration file listing both the plugin's own configuration and the <code class="literal">PluginManager</code> config line:</p><pre class="screen">
 crosswalk.dissemination.stylesheet.DublinCore =
 	xwalk/TESTDIM-2-DC_copy.xsl
 crosswalk.dissemination.stylesheet.MODS = xwalk/mods.xsl
@@ -345,7 +345,7 @@ public class XsltDisseminationCrosswalk extends SelfNamedPlugin
 	getPluginInstanceName());
     }
 }
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N140C6"></a>Stackable Authentication</h4></div></div></div><p>The Stackable Authentication mechanism needs to know all of the plugins configured for the interface, in the order of configuration, since order is significant. It gets a Sequence Plugin from the Plugin Manager. Refer to the <a class="ulink" href="configure.html#authenticate" target="_top">configuration guide</a> for further details.</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N140D0"></a>10.4.&nbsp;<a name="docbook-business.html-workflow"></a>Workflow System</h2></div></div></div><p>The primary classes are:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14148"></a>Stackable Authentication</h4></div></div></div><p>The Stackable Authentication mechanism needs to know all of the plugins configured for the interface, in the order of configuration, since order is significant. It gets a Sequence Plugin from the Plugin Manager. Refer to the <a class="link" href="">configuration guide</a> for further details.</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14152"></a>10.4.&nbsp;<a name="docbook-business.html-workflow"></a>Workflow System</h2></div></div></div><p>The primary classes are:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>
                   <code class="literal">org.dspace.content.WorkspaceItem</code>
                 </p>
@@ -381,7 +381,7 @@ public class XsltDisseminationCrosswalk extends SelfNamedPlugin
                 </p>
               </td><td>
                 <p>used to email messages to Group members and submitters</p>
-              </td></tr></tbody></table></div><p>The workflow system models the states of an Item in a state machine with 5 states (SUBMIT, STEP_1, STEP_2, STEP_3, ARCHIVE.) These are the three optional steps where the item can be viewed and corrected by different groups of people. Actually, it's more like 8 states, with STEP_1_POOL, STEP_2_POOL, and STEP_3_POOL. These pooled states are when items are waiting to enter the primary states.</p><p>The WorkflowManager is invoked by events. While an Item is being submitted, it is held by a WorkspaceItem. Calling the start() method in the WorkflowManager converts a WorkspaceItem to a WorkflowItem, and begins processing the WorkflowItem's state. Since all three steps of the workflow are optional, if no steps are defined, then the Item is simply archived.</p><p>Workflows are set per Collection, and steps are defined by creating corresponding entries in the List named workflowGroup. If you wish the workflow to have a step 1, use the administration tools for Collections to create a workflow Group with members who you want to be able to view and approve the Item, and the workflowGroup[0] becomes set with the ID of that Group.</p><p>If a step is defined in a Collection's workflow, then the WorkflowItem's state is set to that step_POOL. This pooled state is the WorkflowItem waiting for an EPerson in that group to claim the step's task for that WorkflowItem. The WorkflowManager emails the members of that Group notifying them that there is a task to be performed (the text is defined in config/emails,) and when an EPerson goes to their 'My DSpace' page to claim the task, the WorkflowManager is invoked with a claim event, and the WorkflowItem's state advances from STEP_x_POOL to STEP_x (where x is the corresponding step.) The EPerson can also generate an 'unclaim' event, returning the WorkflowItem to the STEP_x_POOL.</p><p>Other events the WorkflowManager handles are advance(), which advances the WorkflowItem to the next state. If there are no further states, then the WorkflowItem is removed, and the Item is then archived. An EPerson performing one of the tasks can reject the Item, which stops the workflow, rebuilds the WorkspaceItem for it and sends a rejection note to the submitter. More drastically, an abort() event is generated by the admin tools to cancel a workflow outright.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14148"></a>10.5.&nbsp;<a name="docbook-business.html-administer"></a>Administration Toolkit</h2></div></div></div><p>The <code class="literal">org.dspace.administer</code> package contains some classes for administering a DSpace system that are not generally needed by most applications.</p><p>The <code class="literal">CreateAdministrator</code> class is a simple command-line tool, executed via <code class="literal">/dspace/bin/create-administrator</code>, that creates an administrator e-person with information entered from standard input. This is generally used only once when a DSpace system is initially installed, to create an initial administrator who can then use the Web administration UI to further set up the system. This script does not check for authorization, since it is typically run before there are any e-people to authorize! Since it must be run as a command-line tool on the server machine, generally this shouldn't cause a problem. A possibility is to have the script only operate when there are no e-people in the system already, though in general, someone with access to command-line scripts on your server is probably in a position to do what they want anyway!</p><p>The <code class="literal">DCType</code> class is similar to the <code class="literal">org.dspace.content.BitstreamFormat</code> class. It represents an entry in the Dublin Core type registry, that is, a particular element and qualifier, or unqualified element. It is in the <code class="literal">administer</code> package because it is only generally required when manipulating the registry itself. Elements and qualifiers are specified as literals in <code class="literal">org.dspace.content.Item</code> methods and the <code class="literal">org.dspace.content.DCValue</code> class. Only administrators may modify the Dublin Core type registry.</p><p>The <code class="literal">org.dspace.administer.RegistryLoader</code> class contains methods for initialising the Dublin Core type registry and bitstream format registry with entries in an XML file. Typically this is executed via the command line during the build process (see <code class="literal">build.xml</code> in the source.) To see examples of the XML formats, see the files in <code class="literal">config/registries</code> in the source directory. There is no XML schema, they aren't validated strictly when loaded in.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14183"></a>10.6.&nbsp;<a name="docbook-business.html-eperson"></a>E-person/Group Manager</h2></div></div></div><p>DSpace keeps track of registered users with the <code class="literal">org.dspace.eperson.EPerson</code> class. The class has methods to create and manipulate an <code class="literal">EPerson</code> such as get and set methods for first and last names, email, and password. (Actually, there is no <code class="literal">getPassword()</code> method--an MD5 hash of the password is stored, and can only be verified with the <code class="literal">checkPassword()</code> method.) There are find methods to find an EPerson by email (which is assumed to be unique,) or to find all EPeople in the system.</p><p>The <code class="literal">EPerson</code> object should probably be reworked to allow for easy expansion; the current EPerson object tracks pretty much only what MIT was interested in tracking - first and last names, email, phone. The access methods are hardcoded and should probably be replaced with methods to access arbitrary name/value pairs for institutions that wish to customize what EPerson information is stored.</p><p>Groups are simply lists of <code class="literal">EPerson</code> objects. Other than membership, <code class="literal">Group</code> objects have only one other attribute: a name. Group names must be unique, so we have adopted naming conventions where the role of the group is its name, such as <code class="literal">COLLECTION_100_ADD</code>. Groups add and remove EPerson objects with <code class="literal">addMember()</code> and <code class="literal">removeMember()</code> methods. One important thing to know about groups is that they store their membership in memory until the <code class="literal">update()</code> method is called - so when modifying a group's membership don't forget to invoke <code class="literal">update()</code> or your changes will be lost! Since group membership is used heavily by the authorization system a fast <code class="literal">isMember()</code> method is also provided.</p><p>Another kind of Group is also implemented in DSpace--special Groups. The <code class="literal">Context</code> object for each session carries around a List of Group IDs that the user is also a member of--currently the MITUser Group ID is added to the list of a user's special groups if certain IP address or certificate criteria are met.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N141CA"></a>10.7.&nbsp;<a name="docbook-business.html-authorize"></a>Authorization</h2></div></div></div><p>The primary classes are:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+              </td></tr></tbody></table></div><p>The workflow system models the states of an Item in a state machine with 5 states (SUBMIT, STEP_1, STEP_2, STEP_3, ARCHIVE.) These are the three optional steps where the item can be viewed and corrected by different groups of people. Actually, it's more like 8 states, with STEP_1_POOL, STEP_2_POOL, and STEP_3_POOL. These pooled states are when items are waiting to enter the primary states.</p><p>The WorkflowManager is invoked by events. While an Item is being submitted, it is held by a WorkspaceItem. Calling the start() method in the WorkflowManager converts a WorkspaceItem to a WorkflowItem, and begins processing the WorkflowItem's state. Since all three steps of the workflow are optional, if no steps are defined, then the Item is simply archived.</p><p>Workflows are set per Collection, and steps are defined by creating corresponding entries in the List named workflowGroup. If you wish the workflow to have a step 1, use the administration tools for Collections to create a workflow Group with members who you want to be able to view and approve the Item, and the workflowGroup[0] becomes set with the ID of that Group.</p><p>If a step is defined in a Collection's workflow, then the WorkflowItem's state is set to that step_POOL. This pooled state is the WorkflowItem waiting for an EPerson in that group to claim the step's task for that WorkflowItem. The WorkflowManager emails the members of that Group notifying them that there is a task to be performed (the text is defined in config/emails,) and when an EPerson goes to their 'My DSpace' page to claim the task, the WorkflowManager is invoked with a claim event, and the WorkflowItem's state advances from STEP_x_POOL to STEP_x (where x is the corresponding step.) The EPerson can also generate an 'unclaim' event, returning the WorkflowItem to the STEP_x_POOL.</p><p>Other events the WorkflowManager handles are advance(), which advances the WorkflowItem to the next state. If there are no further states, then the WorkflowItem is removed, and the Item is then archived. An EPerson performing one of the tasks can reject the Item, which stops the workflow, rebuilds the WorkspaceItem for it and sends a rejection note to the submitter. More drastically, an abort() event is generated by the admin tools to cancel a workflow outright.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N141CA"></a>10.5.&nbsp;<a name="docbook-business.html-administer"></a>Administration Toolkit</h2></div></div></div><p>The <code class="literal">org.dspace.administer</code> package contains some classes for administering a DSpace system that are not generally needed by most applications.</p><p>The <code class="literal">CreateAdministrator</code> class is a simple command-line tool, executed via <code class="literal">/dspace/bin/create-administrator</code>, that creates an administrator e-person with information entered from standard input. This is generally used only once when a DSpace system is initially installed, to create an initial administrator who can then use the Web administration UI to further set up the system. This script does not check for authorization, since it is typically run before there are any e-people to authorize! Since it must be run as a command-line tool on the server machine, generally this shouldn't cause a problem. A possibility is to have the script only operate when there are no e-people in the system already, though in general, someone with access to command-line scripts on your server is probably in a position to do what they want anyway!</p><p>The <code class="literal">DCType</code> class is similar to the <code class="literal">org.dspace.content.BitstreamFormat</code> class. It represents an entry in the Dublin Core type registry, that is, a particular element and qualifier, or unqualified element. It is in the <code class="literal">administer</code> package because it is only generally required when manipulating the registry itself. Elements and qualifiers are specified as literals in <code class="literal">org.dspace.content.Item</code> methods and the <code class="literal">org.dspace.content.DCValue</code> class. Only administrators may modify the Dublin Core type registry.</p><p>The <code class="literal">org.dspace.administer.RegistryLoader</code> class contains methods for initialising the Dublin Core type registry and bitstream format registry with entries in an XML file. Typically this is executed via the command line during the build process (see <code class="literal">build.xml</code> in the source.) To see examples of the XML formats, see the files in <code class="literal">config/registries</code> in the source directory. There is no XML schema, they aren't validated strictly when loaded in.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14205"></a>10.6.&nbsp;<a name="docbook-business.html-eperson"></a>E-person/Group Manager</h2></div></div></div><p>DSpace keeps track of registered users with the <code class="literal">org.dspace.eperson.EPerson</code> class. The class has methods to create and manipulate an <code class="literal">EPerson</code> such as get and set methods for first and last names, email, and password. (Actually, there is no <code class="literal">getPassword()</code> method--an MD5 hash of the password is stored, and can only be verified with the <code class="literal">checkPassword()</code> method.) There are find methods to find an EPerson by email (which is assumed to be unique,) or to find all EPeople in the system.</p><p>The <code class="literal">EPerson</code> object should probably be reworked to allow for easy expansion; the current EPerson object tracks pretty much only what MIT was interested in tracking - first and last names, email, phone. The access methods are hardcoded and should probably be replaced with methods to access arbitrary name/value pairs for institutions that wish to customize what EPerson information is stored.</p><p>Groups are simply lists of <code class="literal">EPerson</code> objects. Other than membership, <code class="literal">Group</code> objects have only one other attribute: a name. Group names must be unique, so we have adopted naming conventions where the role of the group is its name, such as <code class="literal">COLLECTION_100_ADD</code>. Groups add and remove EPerson objects with <code class="literal">addMember()</code> and <code class="literal">removeMember()</code> methods. One important thing to know about groups is that they store their membership in memory until the <code class="literal">update()</code> method is called - so when modifying a group's membership don't forget to invoke <code class="literal">update()</code> or your changes will be lost! Since group membership is used heavily by the authorization system a fast <code class="literal">isMember()</code> method is also provided.</p><p>Another kind of Group is also implemented in DSpace--special Groups. The <code class="literal">Context</code> object for each session carries around a List of Group IDs that the user is also a member of--currently the MITUser Group ID is added to the list of a user's special groups if certain IP address or certificate criteria are met.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1424C"></a>10.7.&nbsp;<a name="docbook-business.html-authorize"></a>Authorization</h2></div></div></div><p>The primary classes are:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                 <p>
                   <code class="literal">org.dspace.authorize.AuthorizeManager</code>
                 </p>
@@ -399,14 +399,14 @@ public class XsltDisseminationCrosswalk extends SelfNamedPlugin
                 </p>
               </td><td>
                 <p>all policies are defined in terms of EPerson Groups</p>
-              </td></tr></tbody></table></div><p>The authorization system is based on the classic 'police state' model of security; no action is allowed unless it is expressed in a policy. The policies are attached to resources (hence the name <code class="literal">ResourcePolicy</code>,) and detail who can perform that action. The resource can be any of the DSpace object types, listed in <code class="literal">org.dspace.core.Constants</code> (<code class="literal">BITSTREAM</code>, <code class="literal">ITEM</code>, <code class="literal">COLLECTION</code>, etc.) The 'who' is made up of EPerson groups. The actions are also in <code class="literal">Constants.java</code> (<code class="literal">READ</code>, <code class="literal">WRITE</code>, <code class="literal">ADD</code>, etc.) The only non-obvious actions are <code class="literal">ADD</code> and <code class="literal">REMOVE</code>, which are authorizations for container objects. To be able to create an Item, you must have <code class="literal">ADD</code> permission in a Collection, which contains Items. (Communities, Collections, Items, and Bundles are all container objects.)</p><p>Currently most of the read policy checking is done with items--communities and collections are assumed to be openly readable, but items and their bitstreams are checked. Separate policy checks for items and their bitstreams enables policies that allow publicly readable items, but parts of their content may be restricted to certain groups.</p><p>The <code class="literal">AuthorizeManager</code> class' <code class="literal">authorizeAction(Context, object, action)</code> is the primary source of all authorization in the system. It gets a list of all of the ResourcePolicies in the system that match the object and action. It then iterates through the policies, extracting the EPerson Group from each policy, and checks to see if the EPersonID from the Context is a member of any of those groups. If all of the policies are queried and no permission is found, then an <code class="literal">AuthorizeException</code> is thrown. An <code class="literal">authorizeAction()</code> method is also supplied that returns a boolean for applications that require higher performance.</p><p>ResourcePolicies are very simple, and there are quite a lot of them. Each can only list a single group, a single action, and a single object. So each object will likely have several policies, and if multiple groups share permissions for actions on an object, each group will get its own policy. (It's a good thing they're small.)</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14253"></a>10.7.1.&nbsp;Special Groups</h3></div></div></div><p>All users are assumed to be part of the public group (ID=0.) DSpace admins (ID=1) are automatically part of all groups, much like super-users in the Unix OS. The Context object also carries around a List of special groups, which are also first checked for membership. These special groups are used at MIT to indicate membership in the MIT community, something that is very difficult to enumerate in the database! When a user logs in with an MIT certificate or with an MIT IP address, the login code adds this MIT user group to the user's Context.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14259"></a>10.7.2.&nbsp;Miscellaneous Authorization Notes</h3></div></div></div><p>Where do items get their read policies? From the their collection's read policy. There once was a separate item read default policy in each collection, and perhaps there will be again since it appears that administrators are notoriously bad at defining collection's read policies. There is also code in place to enable policies that are timed--have a start and end date. However, the admin tools to enable these sorts of policies have not been written.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1425F"></a>10.8.&nbsp;<a name="docbook-business.html-handle"></a>Handle Manager/Handle Plugin</h2></div></div></div><p>The <code class="literal">org.dspace.handle</code> package contains two classes; <code class="literal">HandleManager</code> is used to create and look up Handles, and <code class="literal">HandlePlugin</code> is used to expose and resolve DSpace Handles for the outside world via the CNRI Handle Server code.</p><p>Handles are stored internally in the <code class="literal">handle</code> database table in the form:</p><pre class="screen">
+              </td></tr></tbody></table></div><p>The authorization system is based on the classic 'police state' model of security; no action is allowed unless it is expressed in a policy. The policies are attached to resources (hence the name <code class="literal">ResourcePolicy</code>,) and detail who can perform that action. The resource can be any of the DSpace object types, listed in <code class="literal">org.dspace.core.Constants</code> (<code class="literal">BITSTREAM</code>, <code class="literal">ITEM</code>, <code class="literal">COLLECTION</code>, etc.) The 'who' is made up of EPerson groups. The actions are also in <code class="literal">Constants.java</code> (<code class="literal">READ</code>, <code class="literal">WRITE</code>, <code class="literal">ADD</code>, etc.) The only non-obvious actions are <code class="literal">ADD</code> and <code class="literal">REMOVE</code>, which are authorizations for container objects. To be able to create an Item, you must have <code class="literal">ADD</code> permission in a Collection, which contains Items. (Communities, Collections, Items, and Bundles are all container objects.)</p><p>Currently most of the read policy checking is done with items--communities and collections are assumed to be openly readable, but items and their bitstreams are checked. Separate policy checks for items and their bitstreams enables policies that allow publicly readable items, but parts of their content may be restricted to certain groups.</p><p>The <code class="literal">AuthorizeManager</code> class' <code class="literal">authorizeAction(Context, object, action)</code> is the primary source of all authorization in the system. It gets a list of all of the ResourcePolicies in the system that match the object and action. It then iterates through the policies, extracting the EPerson Group from each policy, and checks to see if the EPersonID from the Context is a member of any of those groups. If all of the policies are queried and no permission is found, then an <code class="literal">AuthorizeException</code> is thrown. An <code class="literal">authorizeAction()</code> method is also supplied that returns a boolean for applications that require higher performance.</p><p>ResourcePolicies are very simple, and there are quite a lot of them. Each can only list a single group, a single action, and a single object. So each object will likely have several policies, and if multiple groups share permissions for actions on an object, each group will get its own policy. (It's a good thing they're small.)</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N142D5"></a>10.7.1.&nbsp;Special Groups</h3></div></div></div><p>All users are assumed to be part of the public group (ID=0.) DSpace admins (ID=1) are automatically part of all groups, much like super-users in the Unix OS. The Context object also carries around a List of special groups, which are also first checked for membership. These special groups are used at MIT to indicate membership in the MIT community, something that is very difficult to enumerate in the database! When a user logs in with an MIT certificate or with an MIT IP address, the login code adds this MIT user group to the user's Context.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N142DB"></a>10.7.2.&nbsp;Miscellaneous Authorization Notes</h3></div></div></div><p>Where do items get their read policies? From the their collection's read policy. There once was a separate item read default policy in each collection, and perhaps there will be again since it appears that administrators are notoriously bad at defining collection's read policies. There is also code in place to enable policies that are timed--have a start and end date. However, the admin tools to enable these sorts of policies have not been written.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N142E1"></a>10.8.&nbsp;<a name="docbook-business.html-handle"></a>Handle Manager/Handle Plugin</h2></div></div></div><p>The <code class="literal">org.dspace.handle</code> package contains two classes; <code class="literal">HandleManager</code> is used to create and look up Handles, and <code class="literal">HandlePlugin</code> is used to expose and resolve DSpace Handles for the outside world via the CNRI Handle Server code.</p><p>Handles are stored internally in the <code class="literal">handle</code> database table in the form:</p><pre class="screen">
 1721.123/4567
 </pre><p>Typically when they are used outside of the system they are displayed in either URI or "URL proxy" forms:</p><pre class="screen">
 hdl:1721.123/4567
 http://hdl.handle.net/1721.123/4567
-</pre><p>It is the responsibility of the caller to extract the basic form from whichever displayed form is used.</p><p>The <code class="literal">handle</code> table maps these Handles to resource type/resource ID pairs, where resource type is a value from <code class="literal">org.dspace.core.Constants</code> and resource ID is the internal identifier (database primary key) of the object. This allows Handles to be assigned to any type of object in the system, though as <a class="ulink" href="functional.html#handles" target="_top">explained in the functional overview</a>, only communities, collections and items are presently assigned Handles.</p><p><code class="literal">HandleManager</code> contains static methods for:</p><div class="itemizedlist"><ul type="disc"><li><p> Creating a Handle</p></li><li><p> Finding the Handle for a <code class="literal">DSpaceObject</code>, though this is usually only invoked by the object itself, since <code class="literal">DSpaceObject</code> has a <code class="literal">getHandle</code> method</p></li><li><p> Retrieving the <code class="literal">DSpaceObject</code> identified by a particular Handle</p></li><li><p> Obtaining displayable forms of the Handle (URI or "proxy URL").</p></li></ul></div><p><code class="literal">HandlePlugin</code> is a simple implementation of the Handle Server's <code class="literal">net.handle.hdllib.HandleStorage</code> interface. It only implements the basic Handle retrieval methods, which get information from the <code class="literal">handle</code> database table. The CNRI Handle Server is configured to use this plug-in via its <code class="literal">config.dct</code> file.</p><p>Note that since the Handle server runs as a separate JVM to the DSpace Web applications, it uses a separate 'Log4J' configuration, since Log4J does not support multiple JVMs using the same daily rolling logs. This alternative configuration is held as a template in <code class="literal">/dspace/config/templates/log4j-handle-plugin.properties</code>, written to <code class="literal">/dspace/config/log4j-handle-plugin.properties</code> by the <code class="literal">install-configs</code> script. The <code class="literal">/dspace/bin/start-handle-server</code> script passes in the appropriate command line parameters so that the Handle server uses this configuration.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N142D7"></a>10.9.&nbsp;<a name="docbook-business.html-search"></a>Search</h2></div></div></div><p>DSpace's search code is a simple API which currently wraps the Lucene search engine. The first half of the search task is indexing, and <code class="literal">org.dspace.search.DSIndexer</code> is the indexing class, which contains <code class="literal">indexContent()</code> which if passed an <code class="literal">Item</code>, <code class="literal">Community</code>, or <code class="literal">Collection</code>, will add that content's fields to the index. The methods <code class="literal">unIndexContent()</code> and <code class="literal">reIndexContent()</code> remove and update content's index information. The <code class="literal">DSIndexer</code> class also has a <code class="literal">main()</code> method which will rebuild the index completely. This is invoked by the <code class="literal">dspace/bin/index-all</code> script. The intent was for the <code class="literal">main()</code> method to be invoked on a regular basis to avoid index corruption, but we have had no problem with that so far.</p><p>Which fields are indexed by <code class="literal">DSIndexer</code>? These fields are defined in dspace.cfg in the section "Fields to index for search" as name-value-pairs. The name must be unique in the form search.index.i (i is an arbitrary positive number). The value on the right side has a unique value again, which can be referenced in search-form (e.g. title, author). Then comes the metadata element which is indexed. '*' is a wildcard which includes all subelements. For example:</p><p>
+</pre><p>It is the responsibility of the caller to extract the basic form from whichever displayed form is used.</p><p>The <code class="literal">handle</code> table maps these Handles to resource type/resource ID pairs, where resource type is a value from <code class="literal">org.dspace.core.Constants</code> and resource ID is the internal identifier (database primary key) of the object. This allows Handles to be assigned to any type of object in the system, though as <a class="link" href="ch02.html#docbook-functional.html-handles">explained in the functional overview</a>, only communities, collections and items are presently assigned Handles.</p><p><code class="literal">HandleManager</code> contains static methods for:</p><div class="itemizedlist"><ul type="disc"><li><p> Creating a Handle</p></li><li><p> Finding the Handle for a <code class="literal">DSpaceObject</code>, though this is usually only invoked by the object itself, since <code class="literal">DSpaceObject</code> has a <code class="literal">getHandle</code> method</p></li><li><p> Retrieving the <code class="literal">DSpaceObject</code> identified by a particular Handle</p></li><li><p> Obtaining displayable forms of the Handle (URI or "proxy URL").</p></li></ul></div><p><code class="literal">HandlePlugin</code> is a simple implementation of the Handle Server's <code class="literal">net.handle.hdllib.HandleStorage</code> interface. It only implements the basic Handle retrieval methods, which get information from the <code class="literal">handle</code> database table. The CNRI Handle Server is configured to use this plug-in via its <code class="literal">config.dct</code> file.</p><p>Note that since the Handle server runs as a separate JVM to the DSpace Web applications, it uses a separate 'Log4J' configuration, since Log4J does not support multiple JVMs using the same daily rolling logs. This alternative configuration is held as a template in <code class="literal">/dspace/config/templates/log4j-handle-plugin.properties</code>, written to <code class="literal">/dspace/config/log4j-handle-plugin.properties</code> by the <code class="literal">install-configs</code> script. The <code class="literal">/dspace/bin/start-handle-server</code> script passes in the appropriate command line parameters so that the Handle server uses this configuration.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14359"></a>10.9.&nbsp;<a name="docbook-business.html-search"></a>Search</h2></div></div></div><p>DSpace's search code is a simple API which currently wraps the Lucene search engine. The first half of the search task is indexing, and <code class="literal">org.dspace.search.DSIndexer</code> is the indexing class, which contains <code class="literal">indexContent()</code> which if passed an <code class="literal">Item</code>, <code class="literal">Community</code>, or <code class="literal">Collection</code>, will add that content's fields to the index. The methods <code class="literal">unIndexContent()</code> and <code class="literal">reIndexContent()</code> remove and update content's index information. The <code class="literal">DSIndexer</code> class also has a <code class="literal">main()</code> method which will rebuild the index completely. This is invoked by the <code class="literal">dspace/bin/index-all</code> script. The intent was for the <code class="literal">main()</code> method to be invoked on a regular basis to avoid index corruption, but we have had no problem with that so far.</p><p>Which fields are indexed by <code class="literal">DSIndexer</code>? These fields are defined in dspace.cfg in the section "Fields to index for search" as name-value-pairs. The name must be unique in the form search.index.i (i is an arbitrary positive number). The value on the right side has a unique value again, which can be referenced in search-form (e.g. title, author). Then comes the metadata element which is indexed. '*' is a wildcard which includes all subelements. For example:</p><p>
         <code class="literal">search.index.4 = keyword:dc.subject.*</code>
-      </p><p>tells the indexer to create a keyword index containing all dc.subject element values. Since the wildcard ('*') character was used in place of a qualifier, all subject metadata fields will be indexed (e.g. dc.subject.other, dc.subject.lcsh, etc)</p><p>By default, the fields shown in the <code class="literal">Indexed Fields</code> section below are indexed. These are hardcoded in the DSIndexer class. If any search.index.i items are specified in <code class="literal">dspace.cfg</code> these are used rather than these hardcoded fields.</p><p>The query class <code class="literal">DSQuery</code> contains the three flavors of <code class="literal">doQuery()</code> methods--one searches the DSpace site, and the other two restrict searches to Collections and Communities. The results from a query are returned as three lists of handles; each list represents a type of result. One list is a list of Items with matches, and the other two are Collections and Communities that match. This separation allows the UI to handle the types of results gracefully without resolving all of the handles first to see what kind of content the handle points to. The <code class="literal">DSQuery</code> class also has a <code class="literal">main()</code> method for debugging via command-line searches.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14336"></a>10.9.1.&nbsp;Our Lucene Implementation</h3></div></div></div><p>Currently we have our own Analyzer and Tokenizer classes (<code class="literal">DSAnalyzer</code> and <code class="literal">DSTokenizer</code>) to customize our indexing. They invoke the stemming and stop word features within Lucene. We create an <code class="literal">IndexReader</code> for each query, which we now realize isn't the most efficient use of resources - we seem to run out of filehandles on really heavy loads. (A wildcard query can open many filehandles!) Since Lucene is thread-safe, a better future implementation would be to have a single Lucene IndexReader shared by all queries, and then is invalidated and re-opened when the index changes. Future API growth could include relevance scores (Lucene generates them, but we ignore them,) and abstractions for more advanced search concepts such as booleans.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14348"></a>10.9.2.&nbsp;Indexed Fields</h3></div></div></div><p>The <code class="literal">DSIndexer</code> class shipped with DSpace indexes the Dublin Core metadata in the following way:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
+      </p><p>tells the indexer to create a keyword index containing all dc.subject element values. Since the wildcard ('*') character was used in place of a qualifier, all subject metadata fields will be indexed (e.g. dc.subject.other, dc.subject.lcsh, etc)</p><p>By default, the fields shown in the <code class="literal">Indexed Fields</code> section below are indexed. These are hardcoded in the DSIndexer class. If any search.index.i items are specified in <code class="literal">dspace.cfg</code> these are used rather than these hardcoded fields.</p><p>The query class <code class="literal">DSQuery</code> contains the three flavors of <code class="literal">doQuery()</code> methods--one searches the DSpace site, and the other two restrict searches to Collections and Communities. The results from a query are returned as three lists of handles; each list represents a type of result. One list is a list of Items with matches, and the other two are Collections and Communities that match. This separation allows the UI to handle the types of results gracefully without resolving all of the handles first to see what kind of content the handle points to. The <code class="literal">DSQuery</code> class also has a <code class="literal">main()</code> method for debugging via command-line searches.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N143B8"></a>10.9.1.&nbsp;Our Lucene Implementation</h3></div></div></div><p>Currently we have our own Analyzer and Tokenizer classes (<code class="literal">DSAnalyzer</code> and <code class="literal">DSTokenizer</code>) to customize our indexing. They invoke the stemming and stop word features within Lucene. We create an <code class="literal">IndexReader</code> for each query, which we now realize isn't the most efficient use of resources - we seem to run out of filehandles on really heavy loads. (A wildcard query can open many filehandles!) Since Lucene is thread-safe, a better future implementation would be to have a single Lucene IndexReader shared by all queries, and then is invalidated and re-opened when the index changes. Future API growth could include relevance scores (Lucene generates them, but we ignore them,) and abstractions for more advanced search concepts such as booleans.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N143CA"></a>10.9.2.&nbsp;Indexed Fields</h3></div></div></div><p>The <code class="literal">DSIndexer</code> class shipped with DSpace indexes the Dublin Core metadata in the following way:</p><div class="informaltable"><table border="0"><colgroup><col><col></colgroup><tbody><tr><td>
                   <p>
                     <span class="bold"><strong>Search Field</strong></span>
                   </p>
@@ -471,7 +471,7 @@ http://hdl.handle.net/1721.123/4567
                   <p>
                     <code class="literal">identifier.*</code>
                   </p>
-                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N143FD"></a>10.9.3.&nbsp;Harvesting API</h3></div></div></div><p>The <code class="literal">org.dspace.search</code> package also provides a 'harvesting' API. This allows callers to extract information about items modified within a particular timeframe, and within a particular scope (all of DSpace, or a community or collection.) Currently this is used by the Open Archives Initiative metadata harvesting protocol application, and the e-mail subscription code.</p><p>The <code class="literal">Harvest.harvest</code> is invoked with the required scope and start and end dates. Either date can be omitted. The dates should be in the ISO8601, UTC time zone format used elsewhere in the DSpace system.</p><p><code class="literal">HarvestedItemInfo</code> objects are returned. These objects are simple containers with basic information about the items falling within the given scope and date range. Depending on parameters passed to the <code class="literal">harvest</code> method, the <code class="literal">containers</code> and <code class="literal">item</code> fields may have been filled out with the IDs of communities and collections containing an item, and the corresponding <code class="literal">Item</code> object respectively. Electing not to have these fields filled out means the harvest operation executes considerable faster.</p><p>In case it is required, <code class="literal">Harvest</code> also offers a method for creating a single <code class="literal">HarvestedItemInfo</code> object, which might make things easier for the caller.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1442C"></a>10.10.&nbsp;<a name="docbook-business.html-browse"></a>Browse API</h2></div></div></div><p>The browse API maintains indices of dates, authors, titles and subjects, and allows callers to extract parts of these:</p><div class="variablelist"><dl><dt><span class="term">Title</span></dt><dd><p> Values of the Dublin Core element <span class="bold"><strong>title</strong></span> (unqualified) are indexed. These are sorted in a case-insensitive fashion, with any leading article removed. For example:</p><pre class="screen">
+                </td></tr></tbody></table></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1447F"></a>10.9.3.&nbsp;Harvesting API</h3></div></div></div><p>The <code class="literal">org.dspace.search</code> package also provides a 'harvesting' API. This allows callers to extract information about items modified within a particular timeframe, and within a particular scope (all of DSpace, or a community or collection.) Currently this is used by the Open Archives Initiative metadata harvesting protocol application, and the e-mail subscription code.</p><p>The <code class="literal">Harvest.harvest</code> is invoked with the required scope and start and end dates. Either date can be omitted. The dates should be in the ISO8601, UTC time zone format used elsewhere in the DSpace system.</p><p><code class="literal">HarvestedItemInfo</code> objects are returned. These objects are simple containers with basic information about the items falling within the given scope and date range. Depending on parameters passed to the <code class="literal">harvest</code> method, the <code class="literal">containers</code> and <code class="literal">item</code> fields may have been filled out with the IDs of communities and collections containing an item, and the corresponding <code class="literal">Item</code> object respectively. Electing not to have these fields filled out means the harvest operation executes considerable faster.</p><p>In case it is required, <code class="literal">Harvest</code> also offers a method for creating a single <code class="literal">HarvestedItemInfo</code> object, which might make things easier for the caller.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N144AE"></a>10.10.&nbsp;<a name="docbook-business.html-browse"></a>Browse API</h2></div></div></div><p>The browse API maintains indices of dates, authors, titles and subjects, and allows callers to extract parts of these:</p><div class="variablelist"><dl><dt><span class="term">Title</span></dt><dd><p> Values of the Dublin Core element <span class="bold"><strong>title</strong></span> (unqualified) are indexed. These are sorted in a case-insensitive fashion, with any leading article removed. For example:</p><pre class="screen">
 The DSpace System
 </pre><p>Appears under 'D' rather than 'T'.</p></dd><dt><span class="term">Author</span></dt><dd><p> Values of the <span class="bold"><strong>contributor</strong></span> (any qualifier or unqualified) element are indexed. Since <code class="literal">contributor</code> values typically are in the form 'last name, first name', a simple case-insensitive alphanumeric sort is used which orders authors in last name order.</p><p>Note that this is an index of <span class="emphasis"><em>authors</em></span>, and not <span class="emphasis"><em>items by author</em></span>. If four items have the same author, that author will appear in the index only once. Hence, the index of authors may be greater or smaller than the index of titles; items often have more than one author, though the same author may have authored several items.</p><p>The author indexing in the browse API does have limitations:</p><div class="itemizedlist"><ul type="disc"><li><p> Ideally, a name that appears as an author for more than one item would appear in the author index only once. For example, 'Doe, John' may be the author of tens of items. However, in practice, author's names often appear in slightly differently forms, for example:</p><pre class="screen">
 Doe, John
@@ -485,7 +485,7 @@ Doe, John S.
 2002-04-09T15:34:12Z
 2002-04-09T19:21:12Z
 2002-04-10
-</pre></dd><dt><span class="term">Date Accessioned</span></dt><dd><p> In order to determine which items most recently appeared, rather than using the date of issue, an item's accession date is used. This is the Dublin Core field <span class="bold"><strong>date.accessioned</strong></span>. In other aspects this index is identical to the date of issue index.</p></dd><dt><span class="term">Items by a Particular Author</span></dt><dd><p> The browse API can perform is to extract items by a particular author. They do not have to be primary author of an item for that item to be extracted. You can specify a scope, too; that is, you can ask for items by author X in collection Y, for example.</p><p>This particular flavour of browse is slightly simpler than the others. You cannot presently specify a particular subset of results to be returned. The API call will simply return all of the items by a particular author within a certain scope.</p><p>Note that the author of the item must <span class="emphasis"><em>exactly</em></span> match the author passed in to the API; see the explanation about the caveats of the author index browsing to see why this is the case.</p></dd><dt><span class="term">Subject</span></dt><dd><p> Values of the Dublin Core element <span class="bold"><strong>subject</strong></span> (both unqualified and with any qualifier) are indexed. These are sorted in a case-insensitive fashion.</p></dd></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N144A9"></a>10.10.1.&nbsp;Using the API</h3></div></div></div><p>The API is generally invoked by creating a <code class="literal">BrowseScope</code> object, and setting the parameters for which particular part of an index you want to extract. This is then passed to the relevent <code class="literal">Browse</code> method call, which returns a <code class="literal">BrowseInfo</code> object which contains the results of the operation. The parameters set in the <code class="literal">BrowseScope</code> object are:</p><div class="itemizedlist"><ul type="disc"><li><p> How many entries from the index you want</p></li><li><p> Whether you only want entries from a particular community or collection, or from the whole of DSpace</p></li><li><p> Which part of the index to start from (called the <span class="emphasis"><em>focus</em></span> of the browse). If you don't specify this, the start of the index is used</p></li><li><p> How many entries to include before the <span class="emphasis"><em>focus</em></span> entry</p></li></ul></div><p>To illustrate, here is an example:</p><div class="itemizedlist"><ul type="disc"><li><p> We want <span class="bold"><strong>7</strong></span> entries in total</p></li><li><p> We want entries from collection <span class="emphasis"><em>x</em></span></p></li><li><p> We want the focus to be 'Really'</p></li><li><p> We want <span class="bold"><strong>2</strong></span> entries included before the focus.</p></li></ul></div><p>The results of invoking <code class="literal">Browse.getItemsByTitle</code> with the above parameters might look like this:</p><pre class="screen">
+</pre></dd><dt><span class="term">Date Accessioned</span></dt><dd><p> In order to determine which items most recently appeared, rather than using the date of issue, an item's accession date is used. This is the Dublin Core field <span class="bold"><strong>date.accessioned</strong></span>. In other aspects this index is identical to the date of issue index.</p></dd><dt><span class="term">Items by a Particular Author</span></dt><dd><p> The browse API can perform is to extract items by a particular author. They do not have to be primary author of an item for that item to be extracted. You can specify a scope, too; that is, you can ask for items by author X in collection Y, for example.</p><p>This particular flavour of browse is slightly simpler than the others. You cannot presently specify a particular subset of results to be returned. The API call will simply return all of the items by a particular author within a certain scope.</p><p>Note that the author of the item must <span class="emphasis"><em>exactly</em></span> match the author passed in to the API; see the explanation about the caveats of the author index browsing to see why this is the case.</p></dd><dt><span class="term">Subject</span></dt><dd><p> Values of the Dublin Core element <span class="bold"><strong>subject</strong></span> (both unqualified and with any qualifier) are indexed. These are sorted in a case-insensitive fashion.</p></dd></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1452B"></a>10.10.1.&nbsp;Using the API</h3></div></div></div><p>The API is generally invoked by creating a <code class="literal">BrowseScope</code> object, and setting the parameters for which particular part of an index you want to extract. This is then passed to the relevent <code class="literal">Browse</code> method call, which returns a <code class="literal">BrowseInfo</code> object which contains the results of the operation. The parameters set in the <code class="literal">BrowseScope</code> object are:</p><div class="itemizedlist"><ul type="disc"><li><p> How many entries from the index you want</p></li><li><p> Whether you only want entries from a particular community or collection, or from the whole of DSpace</p></li><li><p> Which part of the index to start from (called the <span class="emphasis"><em>focus</em></span> of the browse). If you don't specify this, the start of the index is used</p></li><li><p> How many entries to include before the <span class="emphasis"><em>focus</em></span> entry</p></li></ul></div><p>To illustrate, here is an example:</p><div class="itemizedlist"><ul type="disc"><li><p> We want <span class="bold"><strong>7</strong></span> entries in total</p></li><li><p> We want entries from collection <span class="emphasis"><em>x</em></span></p></li><li><p> We want the focus to be 'Really'</p></li><li><p> We want <span class="bold"><strong>2</strong></span> entries included before the focus.</p></li></ul></div><p>The results of invoking <code class="literal">Browse.getItemsByTitle</code> with the above parameters might look like this:</p><pre class="screen">
         Rabble-Rousing Rabbis From Sardinia
         Reality TV: Love It or Hate It?
 FOCUS&gt;  The Really Exciting Research Video
@@ -493,12 +493,12 @@ FOCUS&gt;  The Really Exciting Research Video
         Regional Television Variation Studies
         Revenue Streams
         Ridiculous Example Titles:  I'm Out of Ideas
-</pre><p>Note that in the case of title and date browses, <code class="literal">Item</code> objects are returned as opposed to actual titles. In these cases, you can specify the 'focus' to be a specific item, or a partial or full literal value. In the case of a literal value, if no entry in the index matches exactly, the closest match is used as the focus. It's quite reasonable to specify a focus of a single letter, for example.</p><p>Being able to specify a specific item to start at is particularly important with dates, since many items may have the save issue date. Say 30 items in a collection have the issue date 2002. To be able to page through the index 20 items at a time, you need to be able to specify exactly which item's 2002 is the focus of the browse, otherwise each time you invoked the browse code, the results would start at the first item with the issue date 2002.</p><p>Author browses return <code class="literal">String</code> objects with the actual author names. You can only specify the focus as a full or partial literal <code class="literal">String</code>.</p><p>Another important point to note is that presently, the browse indices contain metadata for all items in the main archive, regardless of authorization policies. This means that all items in the archive will appear to all users when browsing. Of course, should the user attempt to access a non-public item, the usual authorization mechanism will apply. Whether this approach is ideal is under review; implementing the browse API such that the results retrieved reflect a user's level of authorization may be possible, but rather tricky.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14508"></a>10.10.2.&nbsp;Index Maintenance</h3></div></div></div><p>The browse API contains calls to add and remove items from the index, and to regenerate the indices from scratch. In general the content management API invokes the necessary browse API calls to keep the browse indices in sync with what is in the archive, so most applications will not need to invoke those methods.</p><p>If the browse index becomes inconsistent for some reason, the <code class="literal">InitializeBrowse</code> class is a command line tool (generally invoked using the <code class="literal">/dspace/bin/index-all</code> shell script) that causes the indices to be regenerated from scratch.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14518"></a>10.10.3.&nbsp;Caveats</h3></div></div></div><p>Presently, the browse API is not tremendously efficient. 'Indexing' takes the form of simply extracting the relevant Dublin Core value, normalising it (lower-casing and removing any leading article in the case of titles), and inserting that normalized value with the corresponding item ID in the appropriate browse database table. Database views of this table include collection and community IDs for browse operations with a limited scope. When a browse operation is performed, a simple <code class="literal">SELECT</code> query is performed, along the lines of:</p><pre class="screen">
+</pre><p>Note that in the case of title and date browses, <code class="literal">Item</code> objects are returned as opposed to actual titles. In these cases, you can specify the 'focus' to be a specific item, or a partial or full literal value. In the case of a literal value, if no entry in the index matches exactly, the closest match is used as the focus. It's quite reasonable to specify a focus of a single letter, for example.</p><p>Being able to specify a specific item to start at is particularly important with dates, since many items may have the save issue date. Say 30 items in a collection have the issue date 2002. To be able to page through the index 20 items at a time, you need to be able to specify exactly which item's 2002 is the focus of the browse, otherwise each time you invoked the browse code, the results would start at the first item with the issue date 2002.</p><p>Author browses return <code class="literal">String</code> objects with the actual author names. You can only specify the focus as a full or partial literal <code class="literal">String</code>.</p><p>Another important point to note is that presently, the browse indices contain metadata for all items in the main archive, regardless of authorization policies. This means that all items in the archive will appear to all users when browsing. Of course, should the user attempt to access a non-public item, the usual authorization mechanism will apply. Whether this approach is ideal is under review; implementing the browse API such that the results retrieved reflect a user's level of authorization may be possible, but rather tricky.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1458A"></a>10.10.2.&nbsp;Index Maintenance</h3></div></div></div><p>The browse API contains calls to add and remove items from the index, and to regenerate the indices from scratch. In general the content management API invokes the necessary browse API calls to keep the browse indices in sync with what is in the archive, so most applications will not need to invoke those methods.</p><p>If the browse index becomes inconsistent for some reason, the <code class="literal">InitializeBrowse</code> class is a command line tool (generally invoked using the <code class="literal">/dspace/bin/index-all</code> shell script) that causes the indices to be regenerated from scratch.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1459A"></a>10.10.3.&nbsp;Caveats</h3></div></div></div><p>Presently, the browse API is not tremendously efficient. 'Indexing' takes the form of simply extracting the relevant Dublin Core value, normalising it (lower-casing and removing any leading article in the case of titles), and inserting that normalized value with the corresponding item ID in the appropriate browse database table. Database views of this table include collection and community IDs for browse operations with a limited scope. When a browse operation is performed, a simple <code class="literal">SELECT</code> query is performed, along the lines of:</p><pre class="screen">
 SELECT item_id FROM ItemsByTitle ORDER BY sort_title OFFSET 40 LIMIT
 	20
-</pre><p>There are two main drawbacks to this: Firstly, <code class="literal">LIMIT</code> and <code class="literal">OFFSET</code> are PostgreSQL-specific keywords. Secondly, the database is still actually performing dynamic sorting of the titles, so the browse code as it stands will not scale particularly well. The code does cache <code class="literal">BrowseInfo</code> objects, so that common browse operations are performed quickly, but this is not an ideal solution.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14533"></a>10.11.&nbsp;<a name="docbook-business.html-history"></a>History Recorder</h2></div></div></div><p>The purpose of the history subsystem is to capture a time-based record of significant changes in DSpace, in a manner suitable for later refactoring or repurposing. Note that the history data is not expected to provide current information about the archive; it simply records what has happened in the past.</p><p>The <a class="ulink" href="http://www.metadata.net/harmony/" target="_top">Harmony project</a> describes a simple and powerful approach for modeling temporal data. The DSpace history framework adopts this model. The Harmony model is used by the serialization mechanism (and ultimately by agents who interpret the serializations); users of the History API need not be aware of it. The content management API handles invocations of the history system. Users of the DSpace public API do not generally need to use the history API.</p><p>When anything of archival interest occurs in DSpace, the <code class="literal">saveHistory</code> method of the <code class="literal">HistoryManager</code> is invoked. The parameters contains a reference to anything of archival interest. Upon reception of the object, it serializes the state of all archive objects referred to by it, and creates Harmony-style objects and associations to describe the relationships between the objects. (A simple example is given below). Note that each archive object must have a unique identifier to allow linkage between discrete events; this is discussed under "Unique IDs" below.</p><p>The serializations (including the Harmony objects and associations) are persisted as files in the <code class="literal">/dspace/history</code> (or other configured) directory. The <code class="literal">history</code> and <code class="literal">historystate</code> tables contain simple indicies into the serializations in the file system.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1455A"></a>10.11.1.&nbsp;Archival Events</h3></div></div></div><p>The following events are significant enough to warrant history records:</p><div class="itemizedlist"><ul type="disc"><li><p> Communities </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li><li><p> add/remove Collection to/from Community</p></li></ul></div></li><li><p> Collections </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li><li><p> add/remove Item to/from Collection</p></li></ul></div></li><li><p> Items </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li><li><p> assign Handle to Item</p></li><li><p> modify Item contents (Bundles, Bitstreams, metadata fields, etc)</p></li></ul></div></li><li><p> EPerson </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li></ul></div></li><li><p> Workflow </p><div class="itemizedlist"><ul type="circle"><li><p> Workflow completed</p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14590"></a>10.11.2.&nbsp;Serializations</h3></div></div></div><p>The serialization of an archival object consists of:</p><div class="itemizedlist"><ul type="disc"><li><p> Its instance fields (ie, non-static, non-transient fields)</p></li><li><p> The serializations of associated objects (or references to these serializations).</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1459D"></a>10.11.3.&nbsp;Unique Ids</h3></div></div></div><p>To be able to trace the history of an object, it is essential that the object have a unique identifier. Since not all objects in the system have Handles, the unique identifiers are only weakly tied to the Handle system. Instead, the identifier consists of:</p><div class="itemizedlist"><ul type="disc"><li><p> an identifer for the project</p></li><li><p> a site id (using the handle prefix)</p></li><li><p> an RDBMS-based id for objects</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N145AD"></a>10.11.4.&nbsp;Storage</h3></div></div></div><p>When an archive object is serialized, an object ID and MD5 checksum are recorded. When another object is serialized, the checksum for the serialization is matched against existing checksums for that object. If the checksum already exists, the object is not stored; a reference to the object is used instead. Note that since none of the serializations are deleted, reference counting is unnecessary.</p><p>The history data is not initially stored in a queryable form. Two simple RDBMS tables give basic indications of what is stored, and where. The <code class="literal">history</code> table is an index of serializations with checksums and dates. The <code class="literal">history_id</code> column corresponds to the file in which a serialization is stored. For example, if the history ID is 123456, it will be stored in the file:</p><pre class="screen">
+</pre><p>There are two main drawbacks to this: Firstly, <code class="literal">LIMIT</code> and <code class="literal">OFFSET</code> are PostgreSQL-specific keywords. Secondly, the database is still actually performing dynamic sorting of the titles, so the browse code as it stands will not scale particularly well. The code does cache <code class="literal">BrowseInfo</code> objects, so that common browse operations are performed quickly, but this is not an ideal solution.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N145B5"></a>10.11.&nbsp;<a name="docbook-business.html-history"></a>History Recorder</h2></div></div></div><p>The purpose of the history subsystem is to capture a time-based record of significant changes in DSpace, in a manner suitable for later refactoring or repurposing. Note that the history data is not expected to provide current information about the archive; it simply records what has happened in the past.</p><p>The <a class="ulink" href="http://www.metadata.net/harmony/" target="_top">Harmony project</a> describes a simple and powerful approach for modeling temporal data. The DSpace history framework adopts this model. The Harmony model is used by the serialization mechanism (and ultimately by agents who interpret the serializations); users of the History API need not be aware of it. The content management API handles invocations of the history system. Users of the DSpace public API do not generally need to use the history API.</p><p>When anything of archival interest occurs in DSpace, the <code class="literal">saveHistory</code> method of the <code class="literal">HistoryManager</code> is invoked. The parameters contains a reference to anything of archival interest. Upon reception of the object, it serializes the state of all archive objects referred to by it, and creates Harmony-style objects and associations to describe the relationships between the objects. (A simple example is given below). Note that each archive object must have a unique identifier to allow linkage between discrete events; this is discussed under "Unique IDs" below.</p><p>The serializations (including the Harmony objects and associations) are persisted as files in the <code class="literal">/dspace/history</code> (or other configured) directory. The <code class="literal">history</code> and <code class="literal">historystate</code> tables contain simple indicies into the serializations in the file system.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N145DC"></a>10.11.1.&nbsp;Archival Events</h3></div></div></div><p>The following events are significant enough to warrant history records:</p><div class="itemizedlist"><ul type="disc"><li><p> Communities </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li><li><p> add/remove Collection to/from Community</p></li></ul></div></li><li><p> Collections </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li><li><p> add/remove Item to/from Collection</p></li></ul></div></li><li><p> Items </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li><li><p> assign Handle to Item</p></li><li><p> modify Item contents (Bundles, Bitstreams, metadata fields, etc)</p></li></ul></div></li><li><p> EPerson </p><div class="itemizedlist"><ul type="circle"><li><p> create/modify/delete</p></li></ul></div></li><li><p> Workflow </p><div class="itemizedlist"><ul type="circle"><li><p> Workflow completed</p></li></ul></div></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14612"></a>10.11.2.&nbsp;Serializations</h3></div></div></div><p>The serialization of an archival object consists of:</p><div class="itemizedlist"><ul type="disc"><li><p> Its instance fields (ie, non-static, non-transient fields)</p></li><li><p> The serializations of associated objects (or references to these serializations).</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1461F"></a>10.11.3.&nbsp;Unique Ids</h3></div></div></div><p>To be able to trace the history of an object, it is essential that the object have a unique identifier. Since not all objects in the system have Handles, the unique identifiers are only weakly tied to the Handle system. Instead, the identifier consists of:</p><div class="itemizedlist"><ul type="disc"><li><p> an identifer for the project</p></li><li><p> a site id (using the handle prefix)</p></li><li><p> an RDBMS-based id for objects</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1462F"></a>10.11.4.&nbsp;Storage</h3></div></div></div><p>When an archive object is serialized, an object ID and MD5 checksum are recorded. When another object is serialized, the checksum for the serialization is matched against existing checksums for that object. If the checksum already exists, the object is not stored; a reference to the object is used instead. Note that since none of the serializations are deleted, reference counting is unnecessary.</p><p>The history data is not initially stored in a queryable form. Two simple RDBMS tables give basic indications of what is stored, and where. The <code class="literal">history</code> table is an index of serializations with checksums and dates. The <code class="literal">history_id</code> column corresponds to the file in which a serialization is stored. For example, if the history ID is 123456, it will be stored in the file:</p><pre class="screen">
 /dspace/history/00/12/34/123456
-</pre><p>The table also contains the date the serialization was written and the MD5 checksum of the serialization.</p><p>The <code class="literal">historystate</code> table is supposed to indicate the most recent serialization of any given object.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N145C8"></a>10.11.5.&nbsp;Example</h3></div></div></div><p>An item is submitted to a collection via bulk upload. When (and if) the item is eventually added to the collection, the history method is called, with references to the item, its collection, the e-person who performed the bulk upload, and some indication of the fact that it was submitted via a bulk upload.</p><p>When called, the HistoryManager does the following: It creates the following new resources (all with unique ids):</p><div class="itemizedlist"><ul type="disc"><li><p> An event</p></li><li><p> A state</p></li><li><p> An action</p></li></ul></div><p>It also generates the following relationships:</p><pre class="screen">
+</pre><p>The table also contains the date the serialization was written and the MD5 checksum of the serialization.</p><p>The <code class="literal">historystate</code> table is supposed to indicate the most recent serialization of any given object.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1464A"></a>10.11.5.&nbsp;Example</h3></div></div></div><p>An item is submitted to a collection via bulk upload. When (and if) the item is eventually added to the collection, the history method is called, with references to the item, its collection, the e-person who performed the bulk upload, and some indication of the fact that it was submitted via a bulk upload.</p><p>When called, the HistoryManager does the following: It creates the following new resources (all with unique ids):</p><div class="itemizedlist"><ul type="disc"><li><p> An event</p></li><li><p> A state</p></li><li><p> An action</p></li></ul></div><p>It also generates the following relationships:</p><pre class="screen">
 event  --atTime--&gt;     time
 event  --hasOutput--&gt;  state
 Item   --inState--&gt;    state
@@ -507,7 +507,7 @@ action --creates--&gt;    Item
 event  --hasAction--&gt;  action
 action --usesTool--&gt;   DSpace Upload
 action --hasAgent--&gt;   User
-</pre><p>The history component serializes the state of all archival objects involved (in this case, the item, the e-person, and the collection). It creates entries in the history database tables which associate the archival objects with the generated serializations.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N145E1"></a>10.11.6.&nbsp;Caveats</h3></div></div></div><p>This history system is a largely untested experiment. It also needs further documentation. There have been no serious efforts to determine whether the information written by the history system, either to files or the database tables, is accurate. In particular, the <code class="literal">historystate</code> table does not seem to be correctly written.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N145EB"></a>10.12.&nbsp;<a name="docbook-business.html-checker"></a>Checksum checker</h2></div></div></div><p>The architecture of the checker is documented in the package javadocs, run <code class="literal">cd [dspace-source]/dspace;mvn javadoc:javadoc</code>, and look in <code class="literal">[dspace-source]dspace-api/target/site/apidocs/index.html</code>.</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre><p>The history component serializes the state of all archival objects involved (in this case, the item, the e-person, and the collection). It creates entries in the history database tables which associate the archival objects with the generated serializations.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14663"></a>10.11.6.&nbsp;Caveats</h3></div></div></div><p>This history system is a largely untested experiment. It also needs further documentation. There have been no serious efforts to determine whether the information written by the history system, either to files or the database tables, is accurate. In particular, the <code class="literal">historystate</code> table does not seem to be correctly written.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1466D"></a>10.12.&nbsp;<a name="docbook-business.html-checker"></a>Checksum checker</h2></div></div></div><p>The architecture of the checker is documented in the package javadocs, run <code class="literal">cd [dspace-source]/dspace;mvn javadoc:javadoc</code>, and look in <code class="literal">[dspace-source]dspace-api/target/site/apidocs/index.html</code>.</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch11.html b/dspace/docs/html/ch11.html
index d901b414e6..d7234a8023 100644
--- a/dspace/docs/html/ch11.html
+++ b/dspace/docs/html/ch11.html
@@ -1,6 +1,6 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch10.html" title="Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer"><link rel="next" href="ch12.html" title="Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch10.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch12.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N145FC"></a>Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch11.html#N14607">11.1. Understanding the Submission Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14614">11.1.1. The Structure of item-submission.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N14643">11.1.2. Defining Steps (&lt;step&gt;) within the item-submission.xml</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N14777">11.2. Reordering/Removing Submission Steps</a></span></dt><dt><span class="section"><a href="ch11.html#N14824">11.3. Assigning a custom Submission Process to a Collection</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14877">11.3.1. Getting A Collection's Handle</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N1489A">11.4. Custom Metadata-entry Pages for Submission</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N1489E">11.4.1. Introduction</a></span></dt><dt><span class="section"><a href="ch11.html#N148C9">11.4.2. Describing Custom Metadata Forms</a></span></dt><dt><span class="section"><a href="ch11.html#N148EC">11.4.3. The Structure of input-forms.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N14B7A">11.4.4. Deploying Your Custom Forms</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N14B97">11.5. Configuring the File Upload step</a></span></dt><dt><span class="section"><a href="ch11.html#N14BC3">11.6. Creating new Submission Steps</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14C5C">11.6.1. Creating a Non-Interactive Step</a></span></dt></dl></dd></dl></div><p>This page explains various customization and configuration options that are available within DSpace for the Item Submission user interface.</p><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch10.html" title="Chapter&nbsp;10.&nbsp;DSpace System Documentation: Business Logic Layer"><link rel="next" href="ch12.html" title="Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch10.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch12.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N1467E"></a>Chapter&nbsp;11.&nbsp;<a name="docbook-submission.html"></a>Customizing and Configuring Submission User Interface</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch11.html#N1468B">11.1. Understanding the Submission Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14698">11.1.1. The Structure of item-submission.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N146C7">11.1.2. Defining Steps (&lt;step&gt;) within the item-submission.xml</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N147FB">11.2. Reordering/Removing Submission Steps</a></span></dt><dt><span class="section"><a href="ch11.html#N148A8">11.3. Assigning a custom Submission Process to a Collection</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N148FB">11.3.1. Getting A Collection's Handle</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N1491E">11.4. Custom Metadata-entry Pages for Submission</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14922">11.4.1. Introduction</a></span></dt><dt><span class="section"><a href="ch11.html#N1494D">11.4.2. Describing Custom Metadata Forms</a></span></dt><dt><span class="section"><a href="ch11.html#N14970">11.4.3. The Structure of input-forms.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N14BFE">11.4.4. Deploying Your Custom Forms</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N14C1B">11.5. Configuring the File Upload step</a></span></dt><dt><span class="section"><a href="ch11.html#N14C47">11.6. Creating new Submission Steps</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14CE0">11.6.1. Creating a Non-Interactive Step</a></span></dt></dl></dd></dl></div><p>This page explains various customization and configuration options that are available within DSpace for the Item Submission user interface.</p><p>
       <a name="docbook-submission.html-configurationFile"></a>
-    </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14607"></a>11.1.&nbsp;Understanding the Submission Configuration File</h2></div></div></div><p>The <code class="literal">[dspace]/config/item-submission.xml</code> contains the submission configurations for <span class="emphasis"><em>both</em></span> the DSpace JSP user interface (JSPUI) or the DSpace XML user interface (XMLUI or Manakin). This configuration file contains detailed documentation within the file itself, which should help you better understand how to best utilize it.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14614"></a>11.1.1.&nbsp;The Structure of <code class="literal">item-submission.xml</code></h3></div></div></div><pre class="screen">
+    </p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1468B"></a>11.1.&nbsp;Understanding the Submission Configuration File</h2></div></div></div><p>The <code class="literal">[dspace]/config/item-submission.xml</code> contains the submission configurations for <span class="emphasis"><em>both</em></span> the DSpace JSP user interface (JSPUI) or the DSpace XML user interface (XMLUI or Manakin). This configuration file contains detailed documentation within the file itself, which should help you better understand how to best utilize it.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14698"></a>11.1.1.&nbsp;The Structure of <code class="literal">item-submission.xml</code></h3></div></div></div><pre class="screen">
 
           <code class="literal"> &lt;item-submission&gt; &lt;!-- Where submission processes are
 	mapped to specific Collections --&gt; &lt;submission-map&gt; &lt;name-map
@@ -22,7 +22,7 @@
            <code class="literal">Select Collection -&gt; Initial Questions -&gt; Describe -&gt; Upload -&gt; Verify -&gt; License -&gt; Complete</code>
         </p><p>If you would like to customize the steps used or the ordering of the steps, you can do so within the <code class="literal">&lt;submission-definition&gt;</code> section of the <code class="literal">item-submission.xml</code> .</p><p>In addition, you may also specify different Submission Processes for different DSpace Collections. This can be done in the <code class="literal">&lt;submission-map&gt;</code> section. The <code class="literal">item-submission.xml</code> file itself documents the syntax required to perform these configuration changes.</p><p>
           <a name="docbook-submission.html--stepDefinitions"></a>
-        </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14643"></a>11.1.2.&nbsp;Defining Steps (<code class="literal">&lt;step&gt;</code>) within the <code class="literal">item-submission.xml</code></h3></div></div></div><p>This section describes how Steps of the Submission Process are defined within the <code class="literal">item-submission.xml</code>.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14654"></a>Where to place your <code class="literal">&lt;step&gt;</code> definitions</h4></div></div></div><p><code class="literal">&lt;step&gt;</code> definitions can appear in one of two places within the <code class="literal">item-submission.xml</code> configuration file.</p><div class="orderedlist"><ol type="1"><li><p> Within the <code class="literal">&lt;step-definitions&gt;</code> section </p><div class="itemizedlist"><ul type="disc"><li><p> This is for globally defined <code class="literal">&lt;step&gt;</code> definitions (i.e. steps which are used in multiple <code class="literal">&lt;submission-process&gt;</code> definitions). Steps defined in this section <span class="bold"><strong>must</strong></span> define a unique <code class="literal">id</code> which can be used to reference this step.</p></li><li><p> For example: </p><pre class="screen">
+        </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N146C7"></a>11.1.2.&nbsp;Defining Steps (<code class="literal">&lt;step&gt;</code>) within the <code class="literal">item-submission.xml</code></h3></div></div></div><p>This section describes how Steps of the Submission Process are defined within the <code class="literal">item-submission.xml</code>.</p><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N146D8"></a>Where to place your <code class="literal">&lt;step&gt;</code> definitions</h4></div></div></div><p><code class="literal">&lt;step&gt;</code> definitions can appear in one of two places within the <code class="literal">item-submission.xml</code> configuration file.</p><div class="orderedlist"><ol type="1"><li><p> Within the <code class="literal">&lt;step-definitions&gt;</code> section </p><div class="itemizedlist"><ul type="disc"><li><p> This is for globally defined <code class="literal">&lt;step&gt;</code> definitions (i.e. steps which are used in multiple <code class="literal">&lt;submission-process&gt;</code> definitions). Steps defined in this section <span class="bold"><strong>must</strong></span> define a unique <code class="literal">id</code> which can be used to reference this step.</p></li><li><p> For example: </p><pre class="screen">
 
                     <code class="literal"> &lt;step-definitions&gt; &lt;step id="custom-step"&gt; ...
 	&lt;/step&gt; ... &lt;/step-definitions&gt; </code>
@@ -32,7 +32,7 @@
                     <code class="literal"> &lt;submission-process&gt; &lt;step&gt; ... &lt;/step&gt;
 	&lt;/submission-process&gt;</code>
 
-                  </pre></li></ul></div></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N146B0"></a>The ordering of <code class="literal">&lt;step&gt;</code> definitions <span class="bold"><strong>matters</strong></span>!</h4></div></div></div><p>The ordering of the <code class="literal">&lt;step&gt;</code> tags within a <code class="literal">&lt;submission-process&gt;</code> definition directly corresponds to the order in which those steps will appear!</p><p>For example, the following defines a Submission Process where the <span class="emphasis"><em>License</em></span> step directly precedes the <span class="emphasis"><em>Initial Questions</em></span> step (more information about the structure of the information under each &lt;step&gt; tag can be found in the section on <a class="link" href="ch11.html#docbook-submission.html-stepStructure">Structure of the &lt;step&gt; Definition</a> below):</p><pre class="screen">
+                  </pre></li></ul></div></li></ol></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14734"></a>The ordering of <code class="literal">&lt;step&gt;</code> definitions <span class="bold"><strong>matters</strong></span>!</h4></div></div></div><p>The ordering of the <code class="literal">&lt;step&gt;</code> tags within a <code class="literal">&lt;submission-process&gt;</code> definition directly corresponds to the order in which those steps will appear!</p><p>For example, the following defines a Submission Process where the <span class="emphasis"><em>License</em></span> step directly precedes the <span class="emphasis"><em>Initial Questions</em></span> step (more information about the structure of the information under each &lt;step&gt; tag can be found in the section on <a class="link" href="ch11.html#docbook-submission.html-stepStructure">Structure of the &lt;step&gt; Definition</a> below):</p><pre class="screen">
 
             <code class="literal"> &lt;submission-process&gt; &lt;!--Step 1 will be to Sign off on
 	the License--&gt; &lt;step&gt; &lt;heading&gt;submit.progressbar.license&lt;/heading&gt;
@@ -55,7 +55,7 @@ tialQuestionsStep&lt;/xmlui-binding&gt;
 
           </pre><p>
             <a name="docbook-submission.html-stepStructure"></a>
-          </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N146DE"></a>Structure of the &lt;step&gt; Definition</h4></div></div></div><p>The same &lt;step&gt; definition is used by both the DSpace JSP user interface (JSPUI) an the DSpace XML user interface (XMLUI or Manakin). Therefore, you will notice each &lt;step&gt; definition contains information specific to each of these two interfaces.</p><p>The structure of the &lt;step&gt; Definition is as follows:</p><pre class="screen">
+          </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14762"></a>Structure of the &lt;step&gt; Definition</h4></div></div></div><p>The same &lt;step&gt; definition is used by both the DSpace JSP user interface (JSPUI) an the DSpace XML user interface (XMLUI or Manakin). Therefore, you will notice each &lt;step&gt; definition contains information specific to each of these two interfaces.</p><p>The structure of the &lt;step&gt; Definition is as follows:</p><pre class="screen">
 
             <code class="literal"> &lt;step&gt; &lt;heading&gt;submit.progressbar.describe&lt;/heading&gt;
 	&lt;processing-class&gt;org.dspace.submit.step.DescribeStep&lt;/processing-clas
@@ -80,13 +80,13 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
                 <span class="bold"><strong>workflow-editable</strong></span>
               </span></dt><dd><p>Defines whether or not this step can be edited during the <span class="emphasis"><em>Edit Metadata</em></span> process with the DSpace approval/rejection workflow process. Possible values include <code class="literal">true</code> and <code class="literal">false</code>. If undefined, defaults to <code class="literal">true</code> (which means that workflow reviewers would be allowed to edit information gathered during that step).</p></dd></dl></div><p>
             <a name="docbook-submission.html-stepOrdering"></a>
-          </p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14777"></a>11.2.&nbsp;Reordering/Removing Submission Steps</h2></div></div></div><p>The removal of existing steps and reordering of existing steps is a relatively easy process!</p><p>
+          </p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N147FB"></a>11.2.&nbsp;Reordering/Removing Submission Steps</h2></div></div></div><p>The removal of existing steps and reordering of existing steps is a relatively easy process!</p><p>
         <span class="bold"><strong>Reordering steps</strong></span>
       </p><div class="orderedlist"><ol type="1"><li><p> Locate the <code class="literal">&lt;submission-process&gt;</code> tag which defines the Submission Process that you are using. If you are unsure which Submission Process you are using, it's likely the one with <code class="literal">name="traditional"</code>, since this is the traditional DSpace submission process.</p></li><li><p> Reorder the <code class="literal">&lt;step&gt;</code> tags within that <code class="literal">&lt;submission-process&gt;</code> tag. Be sure to move the <span class="emphasis"><em>entire</em></span><code class="literal">&lt;step&gt;</code> tag (i.e. everything between and including the opening <code class="literal">&lt;step&gt;</code> and closing <code class="literal">&lt;/step&gt;</code> tags). </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Hint #1:</em></span> The <code class="literal">&lt;step&gt;</code> defining the <span class="emphasis"><em>Review/Verify</em></span> step only allows the user to review information from steps which appear <span class="bold"><strong>before</strong></span> it. So, it's likely you'd want this to appear as one of your last few steps</p></li><li><p><span class="emphasis"><em>Hint #2:</em></span> If you are using it, the <code class="literal">&lt;step&gt;</code> defining the <span class="emphasis"><em>Initial Questions</em></span> step should always appear <span class="bold"><strong>before</strong></span> the <span class="emphasis"><em>Upload</em></span> or <span class="emphasis"><em>Describe</em></span> steps since it asks questions which help to set up those later steps.</p></li></ul></div></li></ol></div><p>
         <span class="bold"><strong>Removing one or more steps</strong></span>
       </p><div class="orderedlist"><ol type="1"><li><p> Locate the <code class="literal">&lt;submission-process&gt;</code> tag which defines the Submission Process that you are using. If you are unsure which Submission Process you are using, it's likely the one with <code class="literal">name="traditional"</code>, since this is the traditional DSpace submission process.</p></li><li><p> Comment out (i.e. surround with &lt;!-- and --&gt;) the <code class="literal">&lt;step&gt;</code> tags which you want to remove from that <code class="literal">&lt;submission-process&gt;</code> tag. Be sure to comment out the <span class="emphasis"><em>entire</em></span><code class="literal">&lt;step&gt;</code> tag (i.e. everything between and including the opening <code class="literal">&lt;step&gt;</code> and closing <code class="literal">&lt;/step&gt;</code> tags). </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Hint #1:</em></span> You cannot remove the <span class="emphasis"><em>Select a Collection</em></span> step, as an DSpace Item cannot exist without belonging to a Collection.</p></li><li><p><span class="emphasis"><em>Hint #2:</em></span> If you decide to remove the <code class="literal">&lt;step&gt;</code> defining the <span class="emphasis"><em>Initial Questions</em></span> step, you should be aware that this may affect your <span class="emphasis"><em>Describe</em></span> and <span class="emphasis"><em>Upload</em></span> steps! The <span class="emphasis"><em>Initial Questions</em></span> step asks questions which help to initialize these later steps. If you decide to remove the <span class="emphasis"><em>Initial Questions</em></span> step you may wish to create a custom, automated step which will provide default answers for the questions asked!</p></li></ul></div></li></ol></div><p>
         <a name="docbook-submission.html-collectionSubmission"></a>
-      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14824"></a>11.3.&nbsp;Assigning a custom Submission Process to a Collection</h2></div></div></div><p>Assigning a custom submission process to a Collection in DSpace involves working with the <code class="literal">submission-map</code> section of the <code class="literal">item-submission.xml</code>. For a review of the structure of the <code class="literal">item-submission.xml</code> see the section above on <a class="link" href="ch11.html#docbook-submission.html-configurationFile">Understanding the Submission Configuration File</a>.</p><p>Each <code class="literal">name-map</code> element within <code class="literal">submission-map</code> associates a collection with the name of a submission definition. Its <code class="literal">collection-handle</code> attribute is the Handle of the collection. Its <code class="literal">submission-name</code> attribute is the submission definition name, which must match the <code class="literal">name</code> attribute of a <code class="literal">submission-process</code> element (in the <code class="literal">submission-definitions</code> section of <code class="literal">item-submission.xml</code>.</p><p>For example, the following fragment shows how the collection with handle "12345.6789/42" is assigned the "custom" submission process:</p><pre class="screen">
+      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N148A8"></a>11.3.&nbsp;Assigning a custom Submission Process to a Collection</h2></div></div></div><p>Assigning a custom submission process to a Collection in DSpace involves working with the <code class="literal">submission-map</code> section of the <code class="literal">item-submission.xml</code>. For a review of the structure of the <code class="literal">item-submission.xml</code> see the section above on <a class="link" href="ch11.html#docbook-submission.html-configurationFile">Understanding the Submission Configuration File</a>.</p><p>Each <code class="literal">name-map</code> element within <code class="literal">submission-map</code> associates a collection with the name of a submission definition. Its <code class="literal">collection-handle</code> attribute is the Handle of the collection. Its <code class="literal">submission-name</code> attribute is the submission definition name, which must match the <code class="literal">name</code> attribute of a <code class="literal">submission-process</code> element (in the <code class="literal">submission-definitions</code> section of <code class="literal">item-submission.xml</code>.</p><p>For example, the following fragment shows how the collection with handle "12345.6789/42" is assigned the "custom" submission process:</p><pre class="screen">
   &lt;submission-map&gt;
     &lt;name-map collection-handle="<span class="bold"><strong> 12345.6789/42</strong></span>" submission-name="<span class="bold"><strong>
 	custom</strong></span>" /&gt;
@@ -98,12 +98,12 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
 	custom</strong></span>"&gt;
     ...
   &lt;/submission-definitions&gt;
-</pre><p>It's a good idea to keep the definition of the <code class="literal">default</code> name-map from the example <code class="literal">input-forms.xml</code> so there is always a default for collections which do not have a custom form set.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14877"></a>11.3.1.&nbsp;Getting A Collection's Handle</h3></div></div></div><p>You will need the <span class="emphasis"><em>handle</em></span> of a collection in order to assign it a custom form set. To discover the handle, go to the "Communities &amp; Collections" page under "<span class="bold"><strong>Browse</strong></span>" in the left-hand menu on your DSpace home page. Then, find the link to your collection. It should look something like:</p><pre class="screen">
+</pre><p>It's a good idea to keep the definition of the <code class="literal">default</code> name-map from the example <code class="literal">input-forms.xml</code> so there is always a default for collections which do not have a custom form set.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N148FB"></a>11.3.1.&nbsp;Getting A Collection's Handle</h3></div></div></div><p>You will need the <span class="emphasis"><em>handle</em></span> of a collection in order to assign it a custom form set. To discover the handle, go to the "Communities &amp; Collections" page under "<span class="bold"><strong>Browse</strong></span>" in the left-hand menu on your DSpace home page. Then, find the link to your collection. It should look something like:</p><pre class="screen">
     http://myhost.my.edu/dspace/handle/<span class="underline">
 	12345.6789/42</span>
 </pre><p>The underlined part of the URL is the handle. It should look familiar to any DSpace administrator. That is what goes in the <code class="literal">collection-handle</code> attribute of your <code class="literal">name-map</code> element.</p><p>
           <a name="docbook-submission.html-metadataEntry"></a>
-        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1489A"></a>11.4.&nbsp;Custom Metadata-entry Pages for Submission</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1489E"></a>11.4.1.&nbsp;Introduction</h3></div></div></div><p>This section explains how to customize the Web forms used by submitters and editors to enter and modify the metadata for a new item. These metadata web forms are controlled by the <span class="emphasis"><em>Describe</em></span> step within the Submission Process. However, they are also configurable via their own XML configuration file (<code class="literal">input-forms.xml</code>).</p><p>You can customize the "default" metadata forms used by all collections, and also create alternate sets of metadata forms and assign them to specific collections. In creating custom metadata forms, you can choose:</p><div class="itemizedlist"><ul type="disc"><li><p> The number of metadata-entry pages.</p></li><li><p> Which fields appear on each page, and their sequence.</p></li><li><p> Labels, prompts, and other text associated with each field.</p></li><li><p> List of available choices for each menu-driven field.</p></li></ul></div><p><span class="bold"><strong>N.B.</strong></span>The cosmetic and ergonomic details of metadata entry fields remain the same as the fixed metadata pages in previous DSpace releases, and can only be altered by modifying the appropriate stylesheet and JSP pages.</p><p>All of the custom metadata-entry forms for a DSpace instance are controlled by a single XML file, <code class="literal">input-forms.xml</code>, in the <code class="literal">config</code> subdirectory under the DSpace home. DSpace comes with a sample configuration that implements the traditional metadata-entry forms, which also serves as a well-documented example. The rest of this section explains how to create your own sets of custom forms.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N148C9"></a>11.4.2.&nbsp;Describing Custom Metadata Forms</h3></div></div></div><p>The description of a set of pages through which submitters enter their metadata is called a <span class="emphasis"><em>form</em></span> (although it is actually a set of forms, in the HTML sense of the term). A form is identified by a unique symbolic <span class="emphasis"><em>name</em></span>. In the XML structure, the <span class="emphasis"><em>form</em></span> is broken down into a series of <span class="emphasis"><em>pages</em></span>: each of these represents a separate Web page for collecting metadata elements.</p><p>To set up one of your DSpace collections with customized submission forms, first you make an entry in the <span class="emphasis"><em>form-map</em></span>. This is effectively a table that relates a collection to a form set, by connecting the collection's <span class="emphasis"><em>Handle</em></span> to the form name. Collections are identified by handle because their names are mutable and not necessarily unique, while handles are unique and persistent.</p><p>A special map entry, for the collection handle "default", defines the <span class="emphasis"><em>default</em></span> form set. It applies to all collections which are not explicitly mentioned in the map. In the example XML this form set is named <code class="literal">traditional</code> (for the "traditional" DSpace user interface) but it could be named anything.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N148EC"></a>11.4.3.&nbsp;The Structure of <code class="literal">input-forms.xml</code></h3></div></div></div><p>The XML configuration file has a single top-level element, <code class="literal">input-forms</code>, which contains three elements in a specific order. The outline is as follows:</p><pre class="screen">
+        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1491E"></a>11.4.&nbsp;Custom Metadata-entry Pages for Submission</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14922"></a>11.4.1.&nbsp;Introduction</h3></div></div></div><p>This section explains how to customize the Web forms used by submitters and editors to enter and modify the metadata for a new item. These metadata web forms are controlled by the <span class="emphasis"><em>Describe</em></span> step within the Submission Process. However, they are also configurable via their own XML configuration file (<code class="literal">input-forms.xml</code>).</p><p>You can customize the "default" metadata forms used by all collections, and also create alternate sets of metadata forms and assign them to specific collections. In creating custom metadata forms, you can choose:</p><div class="itemizedlist"><ul type="disc"><li><p> The number of metadata-entry pages.</p></li><li><p> Which fields appear on each page, and their sequence.</p></li><li><p> Labels, prompts, and other text associated with each field.</p></li><li><p> List of available choices for each menu-driven field.</p></li></ul></div><p><span class="bold"><strong>N.B.</strong></span>The cosmetic and ergonomic details of metadata entry fields remain the same as the fixed metadata pages in previous DSpace releases, and can only be altered by modifying the appropriate stylesheet and JSP pages.</p><p>All of the custom metadata-entry forms for a DSpace instance are controlled by a single XML file, <code class="literal">input-forms.xml</code>, in the <code class="literal">config</code> subdirectory under the DSpace home. DSpace comes with a sample configuration that implements the traditional metadata-entry forms, which also serves as a well-documented example. The rest of this section explains how to create your own sets of custom forms.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1494D"></a>11.4.2.&nbsp;Describing Custom Metadata Forms</h3></div></div></div><p>The description of a set of pages through which submitters enter their metadata is called a <span class="emphasis"><em>form</em></span> (although it is actually a set of forms, in the HTML sense of the term). A form is identified by a unique symbolic <span class="emphasis"><em>name</em></span>. In the XML structure, the <span class="emphasis"><em>form</em></span> is broken down into a series of <span class="emphasis"><em>pages</em></span>: each of these represents a separate Web page for collecting metadata elements.</p><p>To set up one of your DSpace collections with customized submission forms, first you make an entry in the <span class="emphasis"><em>form-map</em></span>. This is effectively a table that relates a collection to a form set, by connecting the collection's <span class="emphasis"><em>Handle</em></span> to the form name. Collections are identified by handle because their names are mutable and not necessarily unique, while handles are unique and persistent.</p><p>A special map entry, for the collection handle "default", defines the <span class="emphasis"><em>default</em></span> form set. It applies to all collections which are not explicitly mentioned in the map. In the example XML this form set is named <code class="literal">traditional</code> (for the "traditional" DSpace user interface) but it could be named anything.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14970"></a>11.4.3.&nbsp;The Structure of <code class="literal">input-forms.xml</code></h3></div></div></div><p>The XML configuration file has a single top-level element, <code class="literal">input-forms</code>, which contains three elements in a specific order. The outline is as follows:</p><pre class="screen">
 &lt;input-forms&gt;
 
   &lt;-- <span class="emphasis"><em> Map of Collections to Form Sets</em></span> --&gt;
@@ -127,7 +127,7 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
     ...
   &lt;/form-value-pairs&gt;
 &lt;/input-forms&gt;
-</pre><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14905"></a>Adding a Collection Map</h4></div></div></div><p>Each <code class="literal">name-map</code> element within <code class="literal">form-map</code> associates a collection with the name of a form set. Its <code class="literal">collection-handle</code> attribute is the Handle of the collection, and its <code class="literal">form-name</code> attribute is the form set name, which must match the <code class="literal">name</code> attribute of a <code class="literal">form</code> element.</p><p>For example, the following fragment shows how the collection with handle "12345.6789/42" is attached to the "TechRpt" form set:</p><pre class="screen">
+</pre><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14989"></a>Adding a Collection Map</h4></div></div></div><p>Each <code class="literal">name-map</code> element within <code class="literal">form-map</code> associates a collection with the name of a form set. Its <code class="literal">collection-handle</code> attribute is the Handle of the collection, and its <code class="literal">form-name</code> attribute is the form set name, which must match the <code class="literal">name</code> attribute of a <code class="literal">form</code> element.</p><p>For example, the following fragment shows how the collection with handle "12345.6789/42" is attached to the "TechRpt" form set:</p><pre class="screen">
   &lt;form-map&gt;
     &lt;name-map collection-handle="<span class="bold"><strong> 12345.6789/42</strong></span>" form-name="<span class="bold"><strong> TechRpt</strong></span>"
 	/&gt;
@@ -139,12 +139,12 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
 	TechRept</strong></span>"&gt;
     ...
   &lt;/form-definitions&gt;
-</pre><p>It's a good idea to keep the definition of the <code class="literal">default</code> name-map from the example <code class="literal">input-forms.xml</code> so there is always a default for collections which do not have a custom form set.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N1493E"></a>Getting A Collection's Handle</h5></div></div></div><p>You will need the <span class="emphasis"><em>handle</em></span> of a collection in order to assign it a custom form set. To discover the handle, go to the "Communities &amp; Collections" page under "<span class="bold"><strong>Browse</strong></span>" in the left-hand menu on your DSpace home page. Then, find the link to your collection. It should look something like:</p><pre class="screen">
+</pre><p>It's a good idea to keep the definition of the <code class="literal">default</code> name-map from the example <code class="literal">input-forms.xml</code> so there is always a default for collections which do not have a custom form set.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N149C2"></a>Getting A Collection's Handle</h5></div></div></div><p>You will need the <span class="emphasis"><em>handle</em></span> of a collection in order to assign it a custom form set. To discover the handle, go to the "Communities &amp; Collections" page under "<span class="bold"><strong>Browse</strong></span>" in the left-hand menu on your DSpace home page. Then, find the link to your collection. It should look something like:</p><pre class="screen">
     http://myhost.my.edu/dspace/handle/<span class="underline">
 	12345.6789/42</span>
-</pre><p>The underlined part of the URL is the handle. It should look familiar to any DSpace administrator. That is what goes in the <code class="literal">collection-handle</code> attribute of your <code class="literal">name-map</code> element.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N1495C"></a>Adding a Form Set</h4></div></div></div><p>You can add a new form set by creating a new <code class="literal">form</code> element within the <code class="literal">form-definitions</code> element. It has one attribute, <code class="literal">name</code>, which as seen above must match the value of the <code class="literal">name-map</code> for the collections it is to be used for.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N14972"></a>Forms and Pages</h5></div></div></div><p>The content of the <code class="literal">form</code> is a sequence of <code class="literal">page</code> elements. Each of these corresponds to a Web page of forms for entering metadata elements, presented in sequence between the initial "Describe" page and the final "Verify" page (which presents a summary of all the metadata collected).</p><p>A <code class="literal">form</code> must contain at least one and at most six pages. They are presented in the order they appear in the XML. Each <code class="literal">page</code> element must include a <code class="literal">number</code> attribute, that should be its sequence number, e.g.</p><pre class="screen">
+</pre><p>The underlined part of the URL is the handle. It should look familiar to any DSpace administrator. That is what goes in the <code class="literal">collection-handle</code> attribute of your <code class="literal">name-map</code> element.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N149E0"></a>Adding a Form Set</h4></div></div></div><p>You can add a new form set by creating a new <code class="literal">form</code> element within the <code class="literal">form-definitions</code> element. It has one attribute, <code class="literal">name</code>, which as seen above must match the value of the <code class="literal">name-map</code> for the collections it is to be used for.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N149F6"></a>Forms and Pages</h5></div></div></div><p>The content of the <code class="literal">form</code> is a sequence of <code class="literal">page</code> elements. Each of these corresponds to a Web page of forms for entering metadata elements, presented in sequence between the initial "Describe" page and the final "Verify" page (which presents a summary of all the metadata collected).</p><p>A <code class="literal">form</code> must contain at least one and at most six pages. They are presented in the order they appear in the XML. Each <code class="literal">page</code> element must include a <code class="literal">number</code> attribute, that should be its sequence number, e.g.</p><pre class="screen">
 &lt;page number="1"&gt;
-</pre><p>The <code class="literal">page</code> element, in turn, contains a sequence of <code class="literal">field</code> elements. Each field defines an interactive dialog where the submitter enters one of the Dublin Core metadata items.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N1499B"></a>Composition of a Field</h5></div></div></div><p>Each <code class="literal">field</code> contains the following elements, in the order indicated. The required sub-elements are so marked:</p><div class="variablelist"><dl><dt><span class="term">
+</pre><p>The <code class="literal">page</code> element, in turn, contains a sequence of <code class="literal">field</code> elements. Each field defines an interactive dialog where the submitter enters one of the Dublin Core metadata items.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N14A1F"></a>Composition of a Field</h5></div></div></div><p>Each <code class="literal">field</code> contains the following elements, in the order indicated. The required sub-elements are so marked:</p><div class="variablelist"><dl><dt><span class="term">
                   <span class="bold"><strong>dc-schema</strong></span>
                   <span class="emphasis"><em>(Required)</em></span>
                 </span></dt><dd><p>Name of metadata schema employed, e.g. <code class="literal">dc</code> for Dublin Core. This value must match the value of the <code class="literal">schema</code> element defined in <code class="literal">dublin-core-types.xml</code></p></dd><dt><span class="term">
@@ -173,7 +173,7 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
                 </span></dt><dd><p>When this optional element is included with a value, it restricts the visibility of the field to the scope defined by that value. If the element is missing or empty, the field is visible in all scopes. Currently supported scopes are: <div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>workflow</strong></span> : the field will only be visible in the workflow stages of submission. This is good for hiding difficult fields for users, such as subject classifications, thereby easing the use of the submission system.</p></li><li><p><span class="bold"><strong>submit</strong></span> : the field will only be visible in the initial submission, and not in the workflow stages.</p></li></ul></div>
  For example:</p><p>
                     <code class="literal">&lt;visibility&gt;workflow&lt;/visibility&gt;</code>
-                  </p><p> Note that it is considered a configuration error to limit a field's scope while also requiring it - an exception will be generated when this combination is detected.</p></dd></dl></div><p>Look at the example <code class="literal">input-forms.xml</code> and experiment with a a trial custom form to learn this specification language thoroughly. It is a very simple way to express the layout of data-entry forms, but the only way to learn all its subtleties is to use it.</p><p>For the use of controlled vocabularies see the <a class="ulink" href="configure.html#controlledvocabulary" target="_top">Configuring Controlled Vocabularies</a> section.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N14ADB"></a>Automatically Elided Fields</h5></div></div></div><p>You may notice that some fields are automatically skipped when a custom form page is displayed, depending on the kind of item being submitted. This is because the DSpace user-interface engine skips Dublin Core fields which are not needed, according to the initial description of the item. For example, if the user indicates there are no alternate titles on the first "Describe" page (the one with a few checkboxes), the input for the <code class="literal">title.alternative</code> DC element is automatically elided, <span class="emphasis"><em>even on custom submission pages.</em></span></p><p> When a user initiates a submission, DSpace first displays what we'll call the "initial-questions page". By default, it contains three questions with check-boxes: <div class="orderedlist"><ol type="1"><li><p>
+                  </p><p> Note that it is considered a configuration error to limit a field's scope while also requiring it - an exception will be generated when this combination is detected.</p></dd></dl></div><p>Look at the example <code class="literal">input-forms.xml</code> and experiment with a a trial custom form to learn this specification language thoroughly. It is a very simple way to express the layout of data-entry forms, but the only way to learn all its subtleties is to use it.</p><p>For the use of controlled vocabularies see the <a class="link" href="">Configuring Controlled Vocabularies</a> section.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N14B5F"></a>Automatically Elided Fields</h5></div></div></div><p>You may notice that some fields are automatically skipped when a custom form page is displayed, depending on the kind of item being submitted. This is because the DSpace user-interface engine skips Dublin Core fields which are not needed, according to the initial description of the item. For example, if the user indicates there are no alternate titles on the first "Describe" page (the one with a few checkboxes), the input for the <code class="literal">title.alternative</code> DC element is automatically elided, <span class="emphasis"><em>even on custom submission pages.</em></span></p><p> When a user initiates a submission, DSpace first displays what we'll call the "initial-questions page". By default, it contains three questions with check-boxes: <div class="orderedlist"><ol type="1"><li><p>
                     <span class="bold"><strong>The item has more than one title, e.g. a translated title</strong></span>
                   </p><p>  Controls <code class="literal">title.alternative</code> field.</p></li><li><p>
                     <span class="bold"><strong>The item has been published or publicly distributed before</strong></span>
@@ -188,9 +188,9 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
                   </p><p>
                     <span class="emphasis"><em>Does not affect any metadata input fields.</em></span>
                   </p></li></ol></div>
- The answers to the first two questions control whether inputs for certain of the DC metadata fields will displayed, even if they are defined as fields in a custom page.  Conversely, if the metadata fields controlled by a checkbox are not mentioned in the custom form, the checkbox is elided from the initial page to avoid confusing or misleading the user.</p><p>The two relevant checkbox entries are "The item has more than one title, e.g. a translated title", and "The item has been published or publicly distributed before". The checkbox for multiple titles trigger the display of the field with dc-element equal to 'title' and dc-qualifier equal to 'alternative'. If the controlling collection's form set does not contain this field, then the multiple titles question will not appear on the initial questions page.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14B27"></a>Adding <code class="literal">Value-Pairs</code></h4></div></div></div><p> Finally, your custom form description needs to define the "value pairs" for any fields with input types that refer to them. Do this by adding a <code class="literal">value-pairs</code> element to the contents of <code class="literal">form-value-pairs</code>. It has the following required attributes: <div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>value-pairs-name</strong></span>  -- Name by which an <code class="literal">input-type</code> refers to this list.</p></li><li><p><span class="bold"><strong>dc-term</strong></span>  -- Qualified Dublin Core field for which this choice list is selecting a value.</p></li></ul></div>
+ The answers to the first two questions control whether inputs for certain of the DC metadata fields will displayed, even if they are defined as fields in a custom page.  Conversely, if the metadata fields controlled by a checkbox are not mentioned in the custom form, the checkbox is elided from the initial page to avoid confusing or misleading the user.</p><p>The two relevant checkbox entries are "The item has more than one title, e.g. a translated title", and "The item has been published or publicly distributed before". The checkbox for multiple titles trigger the display of the field with dc-element equal to 'title' and dc-qualifier equal to 'alternative'. If the controlling collection's form set does not contain this field, then the multiple titles question will not appear on the initial questions page.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="N14BAB"></a>Adding <code class="literal">Value-Pairs</code></h4></div></div></div><p> Finally, your custom form description needs to define the "value pairs" for any fields with input types that refer to them. Do this by adding a <code class="literal">value-pairs</code> element to the contents of <code class="literal">form-value-pairs</code>. It has the following required attributes: <div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>value-pairs-name</strong></span>  -- Name by which an <code class="literal">input-type</code> refers to this list.</p></li><li><p><span class="bold"><strong>dc-term</strong></span>  -- Qualified Dublin Core field for which this choice list is selecting a value.</p></li></ul></div>
  Each <code class="literal">value-pairs</code> element contains a sequence of <code class="literal">pair</code> sub-elements, each of which in turn contains two elements: <div class="itemizedlist"><ul type="disc"><li><p><span class="bold"><strong>displayed-value</strong></span>  -- Name shown (on the web page) for the menu entry.</p></li><li><p><span class="bold"><strong>stored-value</strong></span>  -- Value stored in the DC element when this entry is chosen.</p></li></ul></div>
- Unlike the HTML <code class="literal">select</code> tag, there is no way to indicate one of the entries should be the default, so the first entry is always the default choice.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N14B64"></a>Example</h5></div></div></div><p>Here is a menu of types of common identifiers:</p><pre class="screen">
+ Unlike the HTML <code class="literal">select</code> tag, there is no way to indicate one of the entries should be the default, so the first entry is always the default choice.</p><div class="section" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="N14BE8"></a>Example</h5></div></div></div><p>Here is a menu of types of common identifiers:</p><pre class="screen">
    &lt;value-pairs value-pairs-name="common_identifiers"
 	dc-term="identifier"&gt;
      &lt;pair&gt;
@@ -218,25 +218,25 @@ cribeStep&lt;/xmlui-binding&gt; &lt;workflow-editable&gt;true&lt;/workflow-edita
 &lt;option VALUE="uri"&gt;URI&lt;/option&gt;
 &lt;option VALUE="isbn"&gt;ISBN&lt;/option&gt;
 &lt;/select&gt;
-</pre><span class="bold"><strong>Identifiers:</strong></span>Gov't Doc #URIISBN</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14B7A"></a>11.4.4.&nbsp;Deploying Your Custom Forms</h3></div></div></div><p> The DSpace web application only reads your custom form definitions when it starts up, so it is important to remember: <div class="blockquote"><blockquote class="blockquote"><p>
+</pre><span class="bold"><strong>Identifiers:</strong></span>Gov't Doc #URIISBN</p></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14BFE"></a>11.4.4.&nbsp;Deploying Your Custom Forms</h3></div></div></div><p> The DSpace web application only reads your custom form definitions when it starts up, so it is important to remember: <div class="blockquote"><blockquote class="blockquote"><p>
               <span class="emphasis"><em><span class="bold"><strong>You must always restart Tomcat</strong></span> (or whatever servlet container you are using) for changes made to the <code class="literal">input-forms.xml</code> file take effect.</em></span>
             </p></blockquote></div>
  Any mistake in the syntax or semantics of the form definitions, such as poorly formed XML or a reference to a nonexistent field name, will cause a fatal error in the DSpace UI. The exception message (at the top of the stack trace in the <code class="literal">dspace.log</code> file) usually has a concise and helpful explanation of what went wrong. Don't forget to stop and restart the servlet container before testing your fix to a bug.</p><p>
           <a name="docbook-submission.html-uploadStep"></a>
-        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14B97"></a>11.5.&nbsp;Configuring the File Upload step</h2></div></div></div><p>The <span class="emphasis"><em>Upload</em></span> step in the DSpace submission process has two configuration options which can be set with your <code class="literal">[dspace]/config/dspace.cfg</code> configuration file. They are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">upload.max</code>  - The maximum size of a file (in bytes) that can be uploaded from the JSPUI (not applicable for the XMLUI). It defaults to 536870912 bytes (512MB). You may set this to -1 to disable any file size limitation. </p><div class="itemizedlist"><ul type="circle"><li><p><span class="emphasis"><em>Note:</em></span>  Increasing this value or setting to -1 does <span class="bold"><strong>not</strong></span> guarantee that DSpace will be able to successfully upload larger files via the web, as large uploads depend on many other factors including bandwidth, web server settings, internet connection speed, etc.</p></li></ul></div></li><li><p><code class="literal">webui.submit.upload.required</code>  - Whether or not all users are <span class="emphasis"><em>required</em></span> to upload a file when they submit an item to DSpace. It defaults to 'true'. When set to 'false' users will see an option to skip the upload step when they submit a new item.</p></li></ul></div><p>
+        </p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14C1B"></a>11.5.&nbsp;Configuring the File Upload step</h2></div></div></div><p>The <span class="emphasis"><em>Upload</em></span> step in the DSpace submission process has two configuration options which can be set with your <code class="literal">[dspace]/config/dspace.cfg</code> configuration file. They are as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">upload.max</code>  - The maximum size of a file (in bytes) that can be uploaded from the JSPUI (not applicable for the XMLUI). It defaults to 536870912 bytes (512MB). You may set this to -1 to disable any file size limitation. </p><div class="itemizedlist"><ul type="circle"><li><p><span class="emphasis"><em>Note:</em></span>  Increasing this value or setting to -1 does <span class="bold"><strong>not</strong></span> guarantee that DSpace will be able to successfully upload larger files via the web, as large uploads depend on many other factors including bandwidth, web server settings, internet connection speed, etc.</p></li></ul></div></li><li><p><code class="literal">webui.submit.upload.required</code>  - Whether or not all users are <span class="emphasis"><em>required</em></span> to upload a file when they submit an item to DSpace. It defaults to 'true'. When set to 'false' users will see an option to skip the upload step when they submit a new item.</p></li></ul></div><p>
         <a name="docbook-submission.html-createStep"></a>
-      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14BC3"></a>11.6.&nbsp;Creating new Submission Steps</h2></div></div></div><p>First, a brief warning: <span class="emphasis"><em>Creating a new Submission Step requires some Java knowledge, and is therefore recommended to be undertaken by a Java programmer whenever possible</em></span></p><p>That being said, at a higher level, creating a new Submission Step requires the following (in this relative order):</p><div class="orderedlist"><ol type="1"><li><p> (<span class="bold"><strong>Required</strong></span>) Create a new Step Processing class </p><div class="itemizedlist"><ul type="disc"><li><p> This class <span class="bold"><strong>must</strong></span> extend the abstract <code class="literal">org.dspace.submit.AbstractProcessingStep</code> class and implement all methods defined by that abstract class.</p></li><li><p> This class should be built in such a way that it can process the input gathered from <span class="emphasis"><em>either</em></span> the XMLUI or JSPUI interface.</p></li></ul></div></li><li><p> (<span class="emphasis"><em>For steps using JSPUI</em></span>) Create the JSPs to display the user interface. Create a new JSPUI "binding" class to initialize and call these JSPs.</p></li><li><p>
+      </p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14C47"></a>11.6.&nbsp;Creating new Submission Steps</h2></div></div></div><p>First, a brief warning: <span class="emphasis"><em>Creating a new Submission Step requires some Java knowledge, and is therefore recommended to be undertaken by a Java programmer whenever possible</em></span></p><p>That being said, at a higher level, creating a new Submission Step requires the following (in this relative order):</p><div class="orderedlist"><ol type="1"><li><p> (<span class="bold"><strong>Required</strong></span>) Create a new Step Processing class </p><div class="itemizedlist"><ul type="disc"><li><p> This class <span class="bold"><strong>must</strong></span> extend the abstract <code class="literal">org.dspace.submit.AbstractProcessingStep</code> class and implement all methods defined by that abstract class.</p></li><li><p> This class should be built in such a way that it can process the input gathered from <span class="emphasis"><em>either</em></span> the XMLUI or JSPUI interface.</p></li></ul></div></li><li><p> (<span class="emphasis"><em>For steps using JSPUI</em></span>) Create the JSPs to display the user interface. Create a new JSPUI "binding" class to initialize and call these JSPs.</p></li><li><p>
             <div class="itemizedlist"><ul type="disc"><li><p> Your JSPUI "binding" class must extend the abstract class <code class="literal">org.dspace.app.webui.submit.JSPStep</code> and implement all methods defined there. It's recommended to use one of the classes in <code class="literal">org.dspace.app.webui.submit.step.*</code> as a reference.</p></li><li><p> Any JSPs created should be loaded by calling the showJSP() method of the <code class="literal">org.dspace.app.webui.submit.JSPStepManager</code> class</p></li><li><p> If this step gathers information to be reviewed, you must also create a Review JSP which will display a read-only view of all data gathered during this step. The path to this JSP must be returned by your getReviewJSP() method. You will find examples of Review JSPs (named similar to <code class="literal">review-[step].jsp</code>) in the JSP <code class="literal">submit/</code> directory.</p></li></ul></div>
-          </p></li><li><p> (<span class="emphasis"><em>For steps using XMLUI</em></span>) Create an XMLUI "binding" Step Transformer which will generate the DRI XML which Manakin requires. </p><div class="itemizedlist"><ul type="disc"><li><p> The Step Transformer must extend and implement all necessary methods within the abstract class <code class="literal">org.dspace.app.xmlui.submission.AbstractSubmissionStep</code></p></li><li><p> It is useful to use the existing classes in <code class="literal">org.dspace.app.xmlui.submission.submit.*</code> as references</p></li></ul></div></li><li><p> (<span class="bold"><strong>Required</strong></span>) Add a valid Step Definition to the <code class="literal">item-submission.xml</code> configuration file. </p><div class="itemizedlist"><ul type="disc"><li><p> This may also require that you add an I18N (Internationalization) key for this step's <code class="literal">heading</code>. See the sections on <a class="ulink" href="configure.html#jspui-multilingual" target="_top">Configuring Multilingual Support for JSPUI</a> or <a class="ulink" href="configure.html#xmlui-multilingual" target="_top">Configuring Multilingual Support for XMLUI</a> for more details.</p></li><li><p> For more information on <code class="literal">&lt;step&gt;</code> definitions within the <code class="literal">item-submission.xml</code>, see the section above on <a name="docbook-submission.html--stepDefinitions.1"></a>Defining Steps (<code class="literal">&lt;step&gt;</code>) within the <code class="literal">item-submission.xml</code>.</p></li></ul></div></li></ol></div><p>
+          </p></li><li><p> (<span class="emphasis"><em>For steps using XMLUI</em></span>) Create an XMLUI "binding" Step Transformer which will generate the DRI XML which Manakin requires. </p><div class="itemizedlist"><ul type="disc"><li><p> The Step Transformer must extend and implement all necessary methods within the abstract class <code class="literal">org.dspace.app.xmlui.submission.AbstractSubmissionStep</code></p></li><li><p> It is useful to use the existing classes in <code class="literal">org.dspace.app.xmlui.submission.submit.*</code> as references</p></li></ul></div></li><li><p> (<span class="bold"><strong>Required</strong></span>) Add a valid Step Definition to the <code class="literal">item-submission.xml</code> configuration file. </p><div class="itemizedlist"><ul type="disc"><li><p> This may also require that you add an I18N (Internationalization) key for this step's <code class="literal">heading</code>. See the sections on <a class="link" href="ch05.html#docbook-configure.html-jspui-multilingual">Configuring Multilingual Support for JSPUI</a> or <a class="link" href="">Configuring Multilingual Support for XMLUI</a> for more details.</p></li><li><p> For more information on <code class="literal">&lt;step&gt;</code> definitions within the <code class="literal">item-submission.xml</code>, see the section above on <a name="docbook-submission.html--stepDefinitions.1"></a>Defining Steps (<code class="literal">&lt;step&gt;</code>) within the <code class="literal">item-submission.xml</code>.</p></li></ul></div></li></ol></div><p>
         <a name="docbook-submission.html-createStep.1"></a>
-      </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14C5C"></a>11.6.1.&nbsp;Creating a Non-Interactive Step</h3></div></div></div><p>Non-interactive steps are ones that have no user interface and only perform backend processing. You may find a need to create non-interactive steps which perform further processing of previously entered information.</p><p>To create a non-interactive step, do the following:</p><div class="orderedlist"><ol type="1"><li><p> Create the required Step Processing class, which extends the abstract <code class="literal">org.dspace.submit.AbstractProcessingStep</code> class. In this class add any processing which this step will perform.</p></li><li><p> Add your non-interactive step to your <code class="literal">item-submission.xml</code> at the place where you wish this step to be called during the submission process. For example, if you want it to be called <span class="emphasis"><em>immediately after</em></span> the existing 'Upload File' step, then place its configuration immediately after the configuration for that 'Upload File' step. The configuration should look similar to the following: </p><pre class="screen">
+      </p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14CE0"></a>11.6.1.&nbsp;Creating a Non-Interactive Step</h3></div></div></div><p>Non-interactive steps are ones that have no user interface and only perform backend processing. You may find a need to create non-interactive steps which perform further processing of previously entered information.</p><p>To create a non-interactive step, do the following:</p><div class="orderedlist"><ol type="1"><li><p> Create the required Step Processing class, which extends the abstract <code class="literal">org.dspace.submit.AbstractProcessingStep</code> class. In this class add any processing which this step will perform.</p></li><li><p> Add your non-interactive step to your <code class="literal">item-submission.xml</code> at the place where you wish this step to be called during the submission process. For example, if you want it to be called <span class="emphasis"><em>immediately after</em></span> the existing 'Upload File' step, then place its configuration immediately after the configuration for that 'Upload File' step. The configuration should look similar to the following: </p><pre class="screen">
 
               <code class="literal"> &lt;step&gt;
 	&lt;processing-class&gt;org.dspace.submit.step.MyNonInteractveStep&lt;/processi
 /processing-class&gt; &lt;workflow-editable&gt;false&lt;/workflow-editable&gt;
 	&lt;/step&gt;</code>
 
-            </pre></li></ol></div><p>Note: Non-interactive steps will not appear in the Progress Bar! Therefore, your submitters will not even know they are there. However, because they are not visible to your users, you should make sure that your non-interactive step does not take a large amount of time to finish its processing and return control to the next step (otherwise there will be a visible time delay in the user interface).</p></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+            </pre></li></ol></div><p>Note: Non-interactive steps will not appear in the Progress Bar! Therefore, your submitters will not even know they are there. However, because they are not visible to your users, you should make sure that your non-interactive step does not take a large amount of time to finish its processing and return control to the next step (otherwise there will be a visible time delay in the user interface).</p></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch12.html b/dspace/docs/html/ch12.html
index c034dc167b..b4c2724290 100644
--- a/dspace/docs/html/ch12.html
+++ b/dspace/docs/html/ch12.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch11.html" title="Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface"><link rel="next" href="ch13.html" title="Chapter&nbsp;13.&nbsp;DRI Schema Reference"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch11.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch13.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N14C81"></a>Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html</h2></div></div></div><p> /* Code style */ div.element-example pre { border: 1px dashed black; overflow-x: hidden; background: rgb(240,240,240); margin: 0px; padding: 10px;} </p></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch11.html" title="Chapter&nbsp;11.&nbsp;Customizing and Configuring Submission User Interface"><link rel="next" href="ch13.html" title="Chapter&nbsp;13.&nbsp;DRI Schema Reference"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch11.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch13.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N14D05"></a>Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html</h2></div></div></div><p> /* Code style */ div.element-example pre { border: 1px dashed black; overflow-x: hidden; background: rgb(240,240,240); margin: 0px; padding: 10px;} </p></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch13.html b/dspace/docs/html/ch13.html
index 231e366f15..d346cf99ec 100644
--- a/dspace/docs/html/ch13.html
+++ b/dspace/docs/html/ch13.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;13.&nbsp;DRI Schema Reference</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch12.html" title="Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html"><link rel="next" href="ch14.html" title="Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;13.&nbsp;DRI Schema Reference</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch12.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N14C87"></a>Chapter&nbsp;13.&nbsp;DRI Schema Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch13.html#N14C9C">13.1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14CAD">13.1.1. The Purpose of DRI</a></span></dt><dt><span class="section"><a href="ch13.html#N14CB3">13.1.2. The Development of DRI</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14CCF">13.2. DRI in Manakin</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14CD8">13.2.1. Themes</a></span></dt><dt><span class="section"><a href="ch13.html#N14CE4">13.2.2. Aspect Chains</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14CEA">13.3. Common Design Patterns</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14CFC">13.3.1. Localization and Internationalization</a></span></dt><dt><span class="section"><a href="ch13.html#N14D10">13.3.2. Standard attribute triplet</a></span></dt><dt><span class="section"><a href="ch13.html#N14D5E">13.3.3. Structure-oriented markup</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14D64">13.4. Schema Overview</a></span></dt><dt><span class="section"><a href="ch13.html#N14DF7">13.5. Merging of DRI Documents</a></span></dt><dt><span class="section"><a href="ch13.html#N14E9C">13.6. Version Changes</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14EA5">13.6.1. Changes from 1.0 to 1.1</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14ECF">13.7. Element Reference</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N153C8">13.7.1. BODY</a></span></dt><dt><span class="section"><a href="ch13.html#N15407">13.7.2. cell</a></span></dt><dt><span class="section"><a href="ch13.html#N154B9">13.7.3. div</a></span></dt><dt><span class="section"><a href="ch13.html#N155E8">13.7.4. DOCUMENT</a></span></dt><dt><span class="section"><a href="ch13.html#N15634">13.7.5. field</a></span></dt><dt><span class="section"><a href="ch13.html#N1573B">13.7.6. figure</a></span></dt><dt><span class="section"><a href="ch13.html#N157A9">13.7.7. head</a></span></dt><dt><span class="section"><a href="ch13.html#N1582C">13.7.8. help</a></span></dt><dt><span class="section"><a href="ch13.html#N15867">13.7.9. hi</a></span></dt><dt><span class="section"><a href="ch13.html#N158F6">13.7.10. instance</a></span></dt><dt><span class="section"><a href="ch13.html#N15927">13.7.11. item</a></span></dt><dt><span class="section"><a href="ch13.html#N159CB">13.7.12. label</a></span></dt><dt><span class="section"><a href="ch13.html#N15A29">13.7.13. list</a></span></dt><dt><span class="section"><a href="ch13.html#N15B65">13.7.14. META</a></span></dt><dt><span class="section"><a href="ch13.html#N15BB8">13.7.15. metadata</a></span></dt><dt><span class="section"><a href="ch13.html#N15C27">13.7.16. OPTIONS</a></span></dt><dt><span class="section"><a href="ch13.html#N15C66">13.7.17. p</a></span></dt><dt><span class="section"><a href="ch13.html#N15CE6">13.7.18. pageMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15D4B">13.7.19. params</a></span></dt><dt><span class="section"><a href="ch13.html#N15DAD">13.7.20. reference</a></span></dt><dt><span class="section"><a href="ch13.html#N15E11">13.7.21. referenceSet</a></span></dt><dt><span class="section"><a href="ch13.html#N15E9F">13.7.22. repository</a></span></dt><dt><span class="section"><a href="ch13.html#N15EE5">13.7.23. repositoryMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15F2E">13.7.24. row</a></span></dt><dt><span class="section"><a href="ch13.html#N15F93">13.7.25. table</a></span></dt><dt><span class="section"><a href="ch13.html#N16007">13.7.26. trail</a></span></dt><dt><span class="section"><a href="ch13.html#N1604D">13.7.27. userMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N160BD">13.7.28. value</a></span></dt><dt><span class="section"><a href="ch13.html#N16137">13.7.29. xref</a></span></dt></dl></dd></dl></div><p><span class="bold"><strong>D</strong></span>igital <span class="bold"><strong>R</strong></span>epository <span class="bold"><strong>I</strong></span>nterface (<span class="bold"><strong>DRI</strong></span>) is a schema that governs the structure of a Manakin DSpace page when encoded as an XML Document. It determines what elements can be present in the Document and the relationship of those elements to each other. This reference document explains the purpose of DRI, provides a broad architectural overview, and explains common design patterns. The appendix includes a complete reference for elements used in the DRI Schema, a graphical representation of the element hierarchy, and a quick reference table of elements and attributes.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14C9C"></a>13.1.&nbsp;<a name="docbook-DRISchemaReference.html-Introduction"></a>Introduction</h2></div></div></div><p>This manual describes the Digital Repository Interface (DRI) as it applies to the DSpace digital repository and XMLUI Manakin based interface. DSpace XML UI is a comprehensive user interface system. It is centralized and generic, allowing it to be applied to all DSpace pages, effectively replacing the JSP-based interface system. Its ability to apply specific styles to arbitrarily large sets of DSpace pages significantly eases the task of adapting the DSpace look and feel to that of the adopting institution. This also allows for several levels of branding, lending institutional credibility to the repository and collections.</p><p>Manakin, the second version of DSpace XML UI, consists of several components, written using Java, XML, and XSL, and is implemented in <a class="ulink" href="http://cocoon.apache.org/" target="_top">Cocoon</a>. Central to the interface is the XML Document, which is a semantic representation of a DSpace page. In Manakin, the XML Document adheres to a schema called the Digital Repository Interface (DRI) Schema, which was developed in conjunction with Manakin and is the subject of this guide. For the remainder of this guide, the terms XML Document, DRI Document, and Document will be used interchangeably.</p><p>This reference document explains the purpose of DRI, provides a broad architectural overview, and explains common design patterns. The appendix includes a complete reference for elements used in the DRI Schema, a graphical representation of the element hierarchy, and a quick reference table of elements and attributes.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14CAD"></a>13.1.1.&nbsp;The Purpose of DRI</h3></div></div></div><p>DRI is a schema that governs the structure of the XML Document. It determines the elements that can be present in the Document and the relationship of those elements to each other. Since all Manakin components produce XML Documents that adhere to the DRI schema, The XML Document serves as the abstraction layer. Two such components, Themes and Aspects, are essential to the workings of Manakin and are described briefly in this manual.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14CB3"></a>13.1.2.&nbsp;The Development of DRI</h3></div></div></div><p>The DRI schema was developed for use in Manakin. The choice to develop our own schema rather than adapt an existing one came after a careful analysis of the schema's purpose as well as the lessons learned from earlier attempts at customizing the DSpace interface. Since every DSpace page in Manakin exists as an XML Document at some point in the process, the schema describing that Document had to be able to structurally represent all content, metadata and relationships between different parts of a DSpace page. It had to be precise enough to avoid losing any structural information, and yet generic enough to allow Themes a certain degree of freedom in expressing that information in a readable format.</p><p>Popular schemas such as XHTML suffer from the problem of not relating elements together explicitly. For example, if a heading precedes a paragraph, the heading is related to the paragraph not because it is encoded as such but because it happens to precede it. When these structures are attempted to be translated into formats where these types of relationships are explicit, the translation becomes tedious, and potentially problematic. More structured schemas, like TEI or Docbook, are domain specific (much like DRI itself) and therefore not suitable for our purposes.</p><p>We also decided that the schema should natively support a metadata standard for encoding artifacts. Rather than encoding artifact metadata in structural elements, like tables or lists, the schema would include artifacts as objects encoded in a particular standard. The inclusion of metadata in native format would enable the Theme to choose the best method to render the artifact for display without being tied to a particular structure.</p><p>Ultimately, we chose to develop our own schema. We have constructed the DRI schema by incorporating other standards when appropriate, such as <a class="ulink" href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html" target="_top">Cocoon's i18n schema</a> for internationalization, <a class="ulink" href="http://dublincore.org/" target="_top">DCMI's Dublin Core</a>, and the <a class="ulink" href="http://www.loc.gov/standards/mets/" target="_top">Library of Congress's METS schema</a>. The design of structural elements was derived primarily from <a class="ulink" href="http://www.tei-c.org/index.xml" target="_top">TEI</a>, with some of the design patterns borrowed from other existing standards such as DocBook and XHTML. While the structural elements were designed to be easily translated into XHTML, they preserve the semantic relationships for use in more expressive languages.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14CCF"></a>13.2.&nbsp;<a name="docbook-DRISchemaReference.html-DRI_in_Manakin"></a>DRI in Manakin</h2></div></div></div><p>The general process for handling a request in DSpace XML UI consists of two parts. The first part builds the XML Document, and the second part stylizes that Document for output. In Manakin, the two parts are not discrete and instead wrapped within two processes: Content Generation, which builds an XML representation of the page, and Style Application, which stylizes the resulting Document. Content Generation is performed by Aspect chaining, while Style Application is performed by a Theme.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14CD8"></a>13.2.1.&nbsp;Themes</h3></div></div></div><p>A Theme is a collection of XSL stylesheets and supporting files like images, CSS styles, translations, and help documents. The XSL stylesheets are applied to the DRI Document to covert it into a readable format and give it structure and basic visual formatting in that format. The supporting files are used to provide the page with a specific look and feel, insert images and other media, translate the content, and perform other tasks. The currently used output format is XHTML and the supporting files are generally limited to CSS, images, and JavaScript. More output formats, like PDF or SVG, may be added in the future.</p><p>A DSpace installation running Manakin may have several Themes associated with it. When applied to a page, a Theme determines most of the page&iacute;s look and feel. Different themes can be applied to different sets of DSpace pages allowing for both variety of styles between sets of pages and consistency within those sets. The xmlui.xconf configuration file determines which Themes are applied to which DSpace pages (see the <a class="ulink" href="configure.html#xmlui-configure" target="_top">Configuration and Customization chapter</a> for more information on installing and configuring themes). Themes may be configured to apply to all pages of specific type, like browse-by-title, to all pages of a one particular community or collection or sets of communities and collections, and to any mix of the two. They can also be configured to apply to a singe arbitrary page or handle.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14CE4"></a>13.2.2.&nbsp;Aspect Chains</h3></div></div></div><p>Manakin Aspects are arrangements of Cocoon components (transformers, actions, matchers, etc) that implement a new set of coupled features for the system. These Aspects are chained together to form all the features of Manakin. Five Aspects exist in the default installation of Manakin, each handling a particular set of features of DSpace, and more can be added to implement extra features. All Aspects take a DRI Document as input and generate one as output. This allows Aspects to be linked together to form an Aspect chain. Each Aspect in the chain takes a DRI Document as input, adds its own functionality, and passes the modified Document to the next Aspect in the chain.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14CEA"></a>13.3.&nbsp;<a name="docbook-DRISchemaReference.html-Common_Design_Patterns"></a>Common Design Patterns</h2></div></div></div><p>There are several design patterns used consistently within the DRI schema. This section identifies the need for and describes the implementation of these patterns. Three patterns are discussed: language and internationalization issues, standard attribute triplet (<span class="emphasis"><em>id</em></span>, <span class="emphasis"><em>n</em></span>, and <span class="emphasis"><em>rend</em></span>), and the use of structure-oriented markup.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14CFC"></a>13.3.1.&nbsp;Localization and Internationalization</h3></div></div></div><p>Internationalization is a very important component of the DRI system. It allows content to be offered in other languages based on user's locale and conditioned upon availability of translations, as well as present dates and currency in a localized manner. There are two types of translated content: content stored and displayed by DSpace itself, and content introduced by the DRI styling process in the XSL transformations. Both types are handled by Cocoon's i18n transformer without regard to their origin.</p><p>When the Content Generation process produces a DRI Document, some of the textual content may be marked up with <code class="literal">i18n</code> elements to signify that translations are available for that content. During the Style Application process, the Theme can also introduce new textual content, marking it up with <code class="literal">i18n</code> tags. As a result, after the Theme's XSL templates are applied to the DRI Document, the final output consists of a DSpace page marked up in the chosen display format (like XHTML) with <code class="literal">i18n</code> elements from both DSpace and XSL content. This final document is sent through Cocoon's i18n transformer that translates the marked up text.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D10"></a>13.3.2.&nbsp;Standard attribute triplet</h3></div></div></div><p>Many elements in the DRI system (all top-level containers, character classes, and many others) contain one or several of the three standard attributes: <span class="emphasis"><em>id</em></span>, <span class="emphasis"><em>n</em></span>, and <span class="emphasis"><em>rend</em></span>. The <span class="emphasis"><em>id</em></span> and <span class="emphasis"><em>n</em></span> attributes can be required or optional based on the element&iacute;s purpose, while the <span class="emphasis"><em>rend</em></span> attribute is always optional. The first two are used for identification purposes, while the third is used as a display hint issued to the styling step.</p><p>Identification is important because it allows elements to be separated from their peers for sorting, special case rendering, and other tasks. The first attribute, <span class="emphasis"><em>id</em></span>, is the global identifier and it is unique to the entire document. Any element that contains an <span class="emphasis"><em>id</em></span> attribute can thus be uniquely referenced by it. The <span class="emphasis"><em>id</em></span> attribute of an element can be either assigned explicitly, or generated from the Java Class Path of the originating object if no name is given. While all elements that can be uniquely identified can carry the <span class="emphasis"><em>id</em></span> attribute, only those that are independent on their context are required to do so. For example, tables are required to have an id since they retain meaning regardless of their location in the document, while table rows and cells can omit the attribute since their meaning depends on the parent element.</p><p>The name attribute <span class="emphasis"><em>n</em></span> is simply the name assigned to the element, and it is used to distinguish an element from its immediate peers. In the example of a particular list, all items in that list will have different names to distinguish them from each other. Other lists in the document, however, can also contain items whose names will be different from each other, but identical to those in the first list. The <span class="emphasis"><em>n</em></span> attribute of an element is therefore unique only in the scope of that element&iacute;s parent and is used mostly for sorting purposes and special rendering of a certain class of elements, like, for example, all first items in lists, or all items named "browse". The <span class="emphasis"><em>n</em></span> attribute follows the same rules as id when determining whether or not it is required for a given element.</p><p>The last attribute in the standard triplet is <span class="emphasis"><em>rend</em></span>. Unlike <span class="emphasis"><em>id</em></span> and <span class="emphasis"><em>n</em></span>, the <span class="emphasis"><em>rend</em></span> attribute can consist of several space delimited values and is optional for all elements that can contain it. Its purpose is to provide a rendering hint from the middle layer component to the styling theme. How that hint is interpreted and whether it is used at all when provided, is completely up the theme. There are several cases, however, where the content of the <span class="emphasis"><em>rend</em></span> attribute is outlined in detail and its use is encouraged. Those cases are the emphasis element <code class="literal">hi</code>, the division element <code class="literal">div</code>, and the <code class="literal">list</code> element. Please refer to the Element Reference for more detail on these elements.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D5E"></a>13.3.3.&nbsp;Structure-oriented markup</h3></div></div></div><p>The final design pattern is the use of structure-oriented markup for content carried by the XML Document. Once generated by Cocoon, the Document contains two major types of information: metadata about the repository and its contents, and the actual content of the page to be displayed. A complete overview of metadata and content markup and their relationship to each other is given in the next section. An important thing to note here, however, is that the markup of the content is oriented towards explicitly stating structural relationships between the elements rather than focusing on the presentational aspects. This makes the markup used by the Document more similar to TEI or Docbook rather than HTML. For this reason, XSL templates are used by the themes to convert structural DRI markup to XHTML. Even then, an attempt is made to create XHTML as structural as possible, leaving presentation entirely to CSS. This allows the XML Document to be generic enough to represent any DSpace page without dictating how it should be rendered.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14D64"></a>13.4.&nbsp;<a name="docbook-DRISchemaReference.html-Schema_Overview"></a>Schema Overview</h2></div></div></div><p>The DRI XML Document consists of the root element document and three top-level elements that contain two major types of elements. The three top-level containers are <code class="literal">meta</code>, <code class="literal">body</code>, and <code class="literal">options</code>. The two types of elements they contain are metadata and content, carrying metadata about the page and the contents of the page, respectively. Figure 1 depicts the relationship between these six components.</p><div class="informalfigure"><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="585"><tr><td><img src="image/DRISchemaOverview.png" width="585"></td></tr></table></div></div><p>Figure 1: The two content types across three major divisions of a DRI page. The <code class="literal">document</code> element is the root for all DRI pages and contains all other elements. It bears only one attribute, <span class="emphasis"><em>version</em></span>, that contains the version number of the DRI system and the schema used to validate the produced document. At the time of writing the working version number is "1.1".</p><p>The <code class="literal">meta</code> element is a the top-level element under document and contains all metadata information about the page, the user that requested it, and the repository it is used with. It contains no structural elements, instead being the only container of metadata elements in a DRI Document. The metadata stored by the meta element is broken up into three major groups: <code class="literal">userMeta</code>, <code class="literal">pageMeta</code>, and <code class="literal">objectMeta</code>, each storing metadata information about their respective component. Please refer to the reference entries for more information about these elements.</p><p>The <code class="literal">options</code> element is another top-level element that contains all navigation and action options available to the user. The options are stored as items in list elements, broken up by the type of action they perform. The five types of actions are: browsing, search, language selection, actions that are always available, and actions that are context dependent. The two action types also contain sub-lists that contain actions available to users of varying degrees of access to the system. The <code class="literal">options</code> element contains no metadata elements and can only make use of a small set of structural elements, namely the <code class="literal">list</code> element and its children.</p><p>The last major top-level element is the <code class="literal">body</code> element. It contains all structural elements in a DRI Document, including the lists used by the <code class="literal">options</code> element. Structural elements are used to build a generic representation of a DSpace page. Any DSpace page can be represented with a combination of the structural elements, which will in turn be transformed by the XSL templates into another format. This is the core mechanism that allows DSpace XML UI to apply uniform templates and styling rules to all DSpace pages and is the fundamental difference from the JSP approach currently used by DSpace.</p><p>The <code class="literal">body</code> element directly contains only one type of element: <code class="literal">div</code>. The <code class="literal">div</code> element serves as a major division of content and any number of them can be contained by the <code class="literal">body</code>. Additionally, divisions are recursive, allowing <code class="literal">divs</code> to contain other <code class="literal">divs</code>. It is within these elements that all other structural elements are contained. Those elements include tables, paragraph elements <code class="literal">p</code>, and lists, as well as their various children elements. At the lower levels of this hierarchy lie the character container elements. These elements, namely paragraphs <code class="literal">p</code>, table <code class="literal">cells</code>, lists <code class="literal">items</code>, and the emphasis element <code class="literal">hi</code>, contain the textual content of a DSpace page, optionally modified with links, figures, and emphasis. If the division within which the character class is contained is tagged as interactive (via the <span class="emphasis"><em>interactive</em></span> attribute), those elements can also contain interactive form fields. Divisions tagged as interactive must also provide <span class="emphasis"><em>method</em></span> and <span class="emphasis"><em>action</em></span> attributes for its fields to use.</p><div class="informalfigure"><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="585"><tr><td><img src="image/DRISchema.png" width="585"></td></tr></table></div></div><p>Figure 2: All the elements in the DRI schema. Note: This image is out-of-date, it does not reflect the changes between 1.0 and 1.1 such as reference and referenceSet.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14DF7"></a>13.5.&nbsp;<a name="docbook-DRISchemaReference.html-Merging_of_DRI_Documents"></a>Merging of DRI Documents</h2></div></div></div><p>Having described the structure of the DRI Document, as well as its function in Manakin's Aspect chains, we now turn our attention to the one last detail of their use: merging two Documents into one. There are several situations where the need to merge two documents arises. In Manakin, for example, every Aspect is responsible for adding different functionality to a DSpace page. Since every instance of a page has to be a complete DRI Document, each Aspect is faced with the task of merging the Document it generated with the ones generated (and merged into one Document) by previously executed Aspects. For this reason rules exist that describe which elements can be merged together and what happens to their data and child elements in the process.</p><p>When merging two DRI Documents, one is considered to be the main document, and the other a feeder document that is added in. The three top level containers (<code class="literal">meta</code>, <code class="literal">body</code> and <code class="literal">options</code>) of both documents are then individually analyzed and merged. In the case of the <code class="literal">options</code> and <code class="literal">meta</code> elements, the children tags are taken individually as well and treated differently from their siblings.</p><p>The <code class="literal">body</code> elements are the easiest to merge: their respective <code class="literal">div</code> children are preserved along with their ordering and are grouped together under one element. Thus, the new <code class="literal">body</code> tag will contain all the <code class="literal">divs</code> of the main document followed by all the <code class="literal">divs</code> of the feeder. However, if two <code class="literal">divs</code> have the same <span class="emphasis"><em>n</em></span> and <span class="emphasis"><em>rend</em></span> attributes (and in case of an interactive <code class="literal">div</code> the same <span class="emphasis"><em>action</em></span> and <span class="emphasis"><em>method</em></span> attributes as well), those <code class="literal">divs</code> will be merged into one. The resulting div will bear the <span class="emphasis"><em>id</em></span>, <span class="emphasis"><em>n</em></span>, and <span class="emphasis"><em>rend</em></span> attributes of the main document's div and contain all the <code class="literal">divs</code> of the main document followed by all the <code class="literal">divs</code> of the feeder. This process continues recursively until all the <code class="literal">divs</code> have been merged. It should be noted that two divisions with separate pagination rules cannot be merged together.</p><p>Merging the <code class="literal">options</code> elements is somewhat different. First, <code class="literal">list</code> elements under <code class="literal">options</code> of both documents are compared with each other. Those unique to either document are simply added under the new options element, just like <code class="literal">divs</code> under <code class="literal">body</code>. In case of duplicates, that is <code class="literal">list</code> elements that belong to both documents and have the same <span class="emphasis"><em>n</em></span> attribute, the two <code class="literal">lists</code> will be merged into one. The new <code class="literal">list</code> element will consist of the main document&iacute;s head element, followed <code class="literal">label-item</code> pairs from the main document, and then finally the <code class="literal">label-item</code> pairs of the feeder, provided they are different from those of the main.</p><p>Finally, the <code class="literal">meta</code> elements are merged much like the elements under body. The three children of <code class="literal">meta</code> - <code class="literal">userMeta</code>, <code class="literal">pageMeta</code>, and <code class="literal">objectMeta</code> - are individually merged, adding the contents of the feeder after the contents of the main.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14E9C"></a>13.6.&nbsp;<a name="docbook-DRISchemaReference.html-version_changes"></a>Version Changes</h2></div></div></div><p>The DRI schema will continue to evolve overtime as the needs of interface design require. The version attribute on the document will indicate which version of the schema the document conforms to. At the time Manakin was incorporated into the standard distribution of DSpac the current version was "1.1", however earlier versions of the Manakin interface may use "1.0".</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14EA5"></a>13.6.1.&nbsp;Changes from 1.0 to 1.1</h3></div></div></div><p>There were major structural changes between these two version numbers. Several elements were removed from the schema:<code class="literal">includeSet</code>, <code class="literal">include</code>, <code class="literal">objectMeta</code>, and <code class="literal">object</code>. Originally all metadata for objects were included in-line with the DRI document, this proved to have several problems and has been removed in version 1.1 of the DRI schema. Instead of including metadata in-line, external references to the metadata is included. Thus, a <code class="literal">reference</code> element has been added along with <code class="literal">referenceSet</code>. These new elements operate like their counterparts in the previous version except refrencing metadata contained on the <code class="literal">objectMeta</code> element they reference metadata in external files. The <code class="literal">repository</code> and <code class="literal">repositoryMeta</code> elements were alse modified in a similar mannor removing in-line metadata and refrencing external metadata documents.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14ECF"></a>13.7.&nbsp;<a name="docbook-DRISchemaReference.html-Element_Reference"></a>Element Reference</h2></div></div></div><div class="informaltable"><table border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;13.&nbsp;DRI Schema Reference</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch12.html" title="Chapter&nbsp;12.&nbsp;docbook/DRISchemaReference.html"><link rel="next" href="ch14.html" title="Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;13.&nbsp;DRI Schema Reference</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch12.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch14.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N14D0B"></a>Chapter&nbsp;13.&nbsp;DRI Schema Reference</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch13.html#N14D20">13.1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D31">13.1.1. The Purpose of DRI</a></span></dt><dt><span class="section"><a href="ch13.html#N14D37">13.1.2. The Development of DRI</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14D53">13.2. DRI in Manakin</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D5C">13.2.1. Themes</a></span></dt><dt><span class="section"><a href="ch13.html#N14D68">13.2.2. Aspect Chains</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14D6E">13.3. Common Design Patterns</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D80">13.3.1. Localization and Internationalization</a></span></dt><dt><span class="section"><a href="ch13.html#N14D94">13.3.2. Standard attribute triplet</a></span></dt><dt><span class="section"><a href="ch13.html#N14DE2">13.3.3. Structure-oriented markup</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14DE8">13.4. Schema Overview</a></span></dt><dt><span class="section"><a href="ch13.html#N14E7B">13.5. Merging of DRI Documents</a></span></dt><dt><span class="section"><a href="ch13.html#N14F20">13.6. Version Changes</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14F29">13.6.1. Changes from 1.0 to 1.1</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14F53">13.7. Element Reference</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N1544C">13.7.1. BODY</a></span></dt><dt><span class="section"><a href="ch13.html#N1548B">13.7.2. cell</a></span></dt><dt><span class="section"><a href="ch13.html#N1553D">13.7.3. div</a></span></dt><dt><span class="section"><a href="ch13.html#N1566C">13.7.4. DOCUMENT</a></span></dt><dt><span class="section"><a href="ch13.html#N156B8">13.7.5. field</a></span></dt><dt><span class="section"><a href="ch13.html#N157BF">13.7.6. figure</a></span></dt><dt><span class="section"><a href="ch13.html#N1582D">13.7.7. head</a></span></dt><dt><span class="section"><a href="ch13.html#N158B0">13.7.8. help</a></span></dt><dt><span class="section"><a href="ch13.html#N158EB">13.7.9. hi</a></span></dt><dt><span class="section"><a href="ch13.html#N1597A">13.7.10. instance</a></span></dt><dt><span class="section"><a href="ch13.html#N159AB">13.7.11. item</a></span></dt><dt><span class="section"><a href="ch13.html#N15A4F">13.7.12. label</a></span></dt><dt><span class="section"><a href="ch13.html#N15AAD">13.7.13. list</a></span></dt><dt><span class="section"><a href="ch13.html#N15BE9">13.7.14. META</a></span></dt><dt><span class="section"><a href="ch13.html#N15C3C">13.7.15. metadata</a></span></dt><dt><span class="section"><a href="ch13.html#N15CAB">13.7.16. OPTIONS</a></span></dt><dt><span class="section"><a href="ch13.html#N15CEA">13.7.17. p</a></span></dt><dt><span class="section"><a href="ch13.html#N15D6A">13.7.18. pageMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15DCF">13.7.19. params</a></span></dt><dt><span class="section"><a href="ch13.html#N15E31">13.7.20. reference</a></span></dt><dt><span class="section"><a href="ch13.html#N15E95">13.7.21. referenceSet</a></span></dt><dt><span class="section"><a href="ch13.html#N15F23">13.7.22. repository</a></span></dt><dt><span class="section"><a href="ch13.html#N15F69">13.7.23. repositoryMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15FB2">13.7.24. row</a></span></dt><dt><span class="section"><a href="ch13.html#N16017">13.7.25. table</a></span></dt><dt><span class="section"><a href="ch13.html#N1608B">13.7.26. trail</a></span></dt><dt><span class="section"><a href="ch13.html#N160D1">13.7.27. userMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N16141">13.7.28. value</a></span></dt><dt><span class="section"><a href="ch13.html#N161BB">13.7.29. xref</a></span></dt></dl></dd></dl></div><p><span class="bold"><strong>D</strong></span>igital <span class="bold"><strong>R</strong></span>epository <span class="bold"><strong>I</strong></span>nterface (<span class="bold"><strong>DRI</strong></span>) is a schema that governs the structure of a Manakin DSpace page when encoded as an XML Document. It determines what elements can be present in the Document and the relationship of those elements to each other. This reference document explains the purpose of DRI, provides a broad architectural overview, and explains common design patterns. The appendix includes a complete reference for elements used in the DRI Schema, a graphical representation of the element hierarchy, and a quick reference table of elements and attributes.</p><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14D20"></a>13.1.&nbsp;<a name="docbook-DRISchemaReference.html-Introduction"></a>Introduction</h2></div></div></div><p>This manual describes the Digital Repository Interface (DRI) as it applies to the DSpace digital repository and XMLUI Manakin based interface. DSpace XML UI is a comprehensive user interface system. It is centralized and generic, allowing it to be applied to all DSpace pages, effectively replacing the JSP-based interface system. Its ability to apply specific styles to arbitrarily large sets of DSpace pages significantly eases the task of adapting the DSpace look and feel to that of the adopting institution. This also allows for several levels of branding, lending institutional credibility to the repository and collections.</p><p>Manakin, the second version of DSpace XML UI, consists of several components, written using Java, XML, and XSL, and is implemented in <a class="ulink" href="http://cocoon.apache.org/" target="_top">Cocoon</a>. Central to the interface is the XML Document, which is a semantic representation of a DSpace page. In Manakin, the XML Document adheres to a schema called the Digital Repository Interface (DRI) Schema, which was developed in conjunction with Manakin and is the subject of this guide. For the remainder of this guide, the terms XML Document, DRI Document, and Document will be used interchangeably.</p><p>This reference document explains the purpose of DRI, provides a broad architectural overview, and explains common design patterns. The appendix includes a complete reference for elements used in the DRI Schema, a graphical representation of the element hierarchy, and a quick reference table of elements and attributes.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D31"></a>13.1.1.&nbsp;The Purpose of DRI</h3></div></div></div><p>DRI is a schema that governs the structure of the XML Document. It determines the elements that can be present in the Document and the relationship of those elements to each other. Since all Manakin components produce XML Documents that adhere to the DRI schema, The XML Document serves as the abstraction layer. Two such components, Themes and Aspects, are essential to the workings of Manakin and are described briefly in this manual.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D37"></a>13.1.2.&nbsp;The Development of DRI</h3></div></div></div><p>The DRI schema was developed for use in Manakin. The choice to develop our own schema rather than adapt an existing one came after a careful analysis of the schema's purpose as well as the lessons learned from earlier attempts at customizing the DSpace interface. Since every DSpace page in Manakin exists as an XML Document at some point in the process, the schema describing that Document had to be able to structurally represent all content, metadata and relationships between different parts of a DSpace page. It had to be precise enough to avoid losing any structural information, and yet generic enough to allow Themes a certain degree of freedom in expressing that information in a readable format.</p><p>Popular schemas such as XHTML suffer from the problem of not relating elements together explicitly. For example, if a heading precedes a paragraph, the heading is related to the paragraph not because it is encoded as such but because it happens to precede it. When these structures are attempted to be translated into formats where these types of relationships are explicit, the translation becomes tedious, and potentially problematic. More structured schemas, like TEI or Docbook, are domain specific (much like DRI itself) and therefore not suitable for our purposes.</p><p>We also decided that the schema should natively support a metadata standard for encoding artifacts. Rather than encoding artifact metadata in structural elements, like tables or lists, the schema would include artifacts as objects encoded in a particular standard. The inclusion of metadata in native format would enable the Theme to choose the best method to render the artifact for display without being tied to a particular structure.</p><p>Ultimately, we chose to develop our own schema. We have constructed the DRI schema by incorporating other standards when appropriate, such as <a class="ulink" href="http://cocoon.apache.org/2.1/userdocs/i18nTransformer.html" target="_top">Cocoon's i18n schema</a> for internationalization, <a class="ulink" href="http://dublincore.org/" target="_top">DCMI's Dublin Core</a>, and the <a class="ulink" href="http://www.loc.gov/standards/mets/" target="_top">Library of Congress's METS schema</a>. The design of structural elements was derived primarily from <a class="ulink" href="http://www.tei-c.org/index.xml" target="_top">TEI</a>, with some of the design patterns borrowed from other existing standards such as DocBook and XHTML. While the structural elements were designed to be easily translated into XHTML, they preserve the semantic relationships for use in more expressive languages.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14D53"></a>13.2.&nbsp;<a name="docbook-DRISchemaReference.html-DRI_in_Manakin"></a>DRI in Manakin</h2></div></div></div><p>The general process for handling a request in DSpace XML UI consists of two parts. The first part builds the XML Document, and the second part stylizes that Document for output. In Manakin, the two parts are not discrete and instead wrapped within two processes: Content Generation, which builds an XML representation of the page, and Style Application, which stylizes the resulting Document. Content Generation is performed by Aspect chaining, while Style Application is performed by a Theme.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D5C"></a>13.2.1.&nbsp;Themes</h3></div></div></div><p>A Theme is a collection of XSL stylesheets and supporting files like images, CSS styles, translations, and help documents. The XSL stylesheets are applied to the DRI Document to covert it into a readable format and give it structure and basic visual formatting in that format. The supporting files are used to provide the page with a specific look and feel, insert images and other media, translate the content, and perform other tasks. The currently used output format is XHTML and the supporting files are generally limited to CSS, images, and JavaScript. More output formats, like PDF or SVG, may be added in the future.</p><p>A DSpace installation running Manakin may have several Themes associated with it. When applied to a page, a Theme determines most of the page&iacute;s look and feel. Different themes can be applied to different sets of DSpace pages allowing for both variety of styles between sets of pages and consistency within those sets. The xmlui.xconf configuration file determines which Themes are applied to which DSpace pages (see the <a class="link" href="ch05.html#docbook-configure.html-xmlui-configure">Configuration and Customization chapter</a> for more information on installing and configuring themes). Themes may be configured to apply to all pages of specific type, like browse-by-title, to all pages of a one particular community or collection or sets of communities and collections, and to any mix of the two. They can also be configured to apply to a singe arbitrary page or handle.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D68"></a>13.2.2.&nbsp;Aspect Chains</h3></div></div></div><p>Manakin Aspects are arrangements of Cocoon components (transformers, actions, matchers, etc) that implement a new set of coupled features for the system. These Aspects are chained together to form all the features of Manakin. Five Aspects exist in the default installation of Manakin, each handling a particular set of features of DSpace, and more can be added to implement extra features. All Aspects take a DRI Document as input and generate one as output. This allows Aspects to be linked together to form an Aspect chain. Each Aspect in the chain takes a DRI Document as input, adds its own functionality, and passes the modified Document to the next Aspect in the chain.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14D6E"></a>13.3.&nbsp;<a name="docbook-DRISchemaReference.html-Common_Design_Patterns"></a>Common Design Patterns</h2></div></div></div><p>There are several design patterns used consistently within the DRI schema. This section identifies the need for and describes the implementation of these patterns. Three patterns are discussed: language and internationalization issues, standard attribute triplet (<span class="emphasis"><em>id</em></span>, <span class="emphasis"><em>n</em></span>, and <span class="emphasis"><em>rend</em></span>), and the use of structure-oriented markup.</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D80"></a>13.3.1.&nbsp;Localization and Internationalization</h3></div></div></div><p>Internationalization is a very important component of the DRI system. It allows content to be offered in other languages based on user's locale and conditioned upon availability of translations, as well as present dates and currency in a localized manner. There are two types of translated content: content stored and displayed by DSpace itself, and content introduced by the DRI styling process in the XSL transformations. Both types are handled by Cocoon's i18n transformer without regard to their origin.</p><p>When the Content Generation process produces a DRI Document, some of the textual content may be marked up with <code class="literal">i18n</code> elements to signify that translations are available for that content. During the Style Application process, the Theme can also introduce new textual content, marking it up with <code class="literal">i18n</code> tags. As a result, after the Theme's XSL templates are applied to the DRI Document, the final output consists of a DSpace page marked up in the chosen display format (like XHTML) with <code class="literal">i18n</code> elements from both DSpace and XSL content. This final document is sent through Cocoon's i18n transformer that translates the marked up text.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14D94"></a>13.3.2.&nbsp;Standard attribute triplet</h3></div></div></div><p>Many elements in the DRI system (all top-level containers, character classes, and many others) contain one or several of the three standard attributes: <span class="emphasis"><em>id</em></span>, <span class="emphasis"><em>n</em></span>, and <span class="emphasis"><em>rend</em></span>. The <span class="emphasis"><em>id</em></span> and <span class="emphasis"><em>n</em></span> attributes can be required or optional based on the element&iacute;s purpose, while the <span class="emphasis"><em>rend</em></span> attribute is always optional. The first two are used for identification purposes, while the third is used as a display hint issued to the styling step.</p><p>Identification is important because it allows elements to be separated from their peers for sorting, special case rendering, and other tasks. The first attribute, <span class="emphasis"><em>id</em></span>, is the global identifier and it is unique to the entire document. Any element that contains an <span class="emphasis"><em>id</em></span> attribute can thus be uniquely referenced by it. The <span class="emphasis"><em>id</em></span> attribute of an element can be either assigned explicitly, or generated from the Java Class Path of the originating object if no name is given. While all elements that can be uniquely identified can carry the <span class="emphasis"><em>id</em></span> attribute, only those that are independent on their context are required to do so. For example, tables are required to have an id since they retain meaning regardless of their location in the document, while table rows and cells can omit the attribute since their meaning depends on the parent element.</p><p>The name attribute <span class="emphasis"><em>n</em></span> is simply the name assigned to the element, and it is used to distinguish an element from its immediate peers. In the example of a particular list, all items in that list will have different names to distinguish them from each other. Other lists in the document, however, can also contain items whose names will be different from each other, but identical to those in the first list. The <span class="emphasis"><em>n</em></span> attribute of an element is therefore unique only in the scope of that element&iacute;s parent and is used mostly for sorting purposes and special rendering of a certain class of elements, like, for example, all first items in lists, or all items named "browse". The <span class="emphasis"><em>n</em></span> attribute follows the same rules as id when determining whether or not it is required for a given element.</p><p>The last attribute in the standard triplet is <span class="emphasis"><em>rend</em></span>. Unlike <span class="emphasis"><em>id</em></span> and <span class="emphasis"><em>n</em></span>, the <span class="emphasis"><em>rend</em></span> attribute can consist of several space delimited values and is optional for all elements that can contain it. Its purpose is to provide a rendering hint from the middle layer component to the styling theme. How that hint is interpreted and whether it is used at all when provided, is completely up the theme. There are several cases, however, where the content of the <span class="emphasis"><em>rend</em></span> attribute is outlined in detail and its use is encouraged. Those cases are the emphasis element <code class="literal">hi</code>, the division element <code class="literal">div</code>, and the <code class="literal">list</code> element. Please refer to the Element Reference for more detail on these elements.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14DE2"></a>13.3.3.&nbsp;Structure-oriented markup</h3></div></div></div><p>The final design pattern is the use of structure-oriented markup for content carried by the XML Document. Once generated by Cocoon, the Document contains two major types of information: metadata about the repository and its contents, and the actual content of the page to be displayed. A complete overview of metadata and content markup and their relationship to each other is given in the next section. An important thing to note here, however, is that the markup of the content is oriented towards explicitly stating structural relationships between the elements rather than focusing on the presentational aspects. This makes the markup used by the Document more similar to TEI or Docbook rather than HTML. For this reason, XSL templates are used by the themes to convert structural DRI markup to XHTML. Even then, an attempt is made to create XHTML as structural as possible, leaving presentation entirely to CSS. This allows the XML Document to be generic enough to represent any DSpace page without dictating how it should be rendered.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14DE8"></a>13.4.&nbsp;<a name="docbook-DRISchemaReference.html-Schema_Overview"></a>Schema Overview</h2></div></div></div><p>The DRI XML Document consists of the root element document and three top-level elements that contain two major types of elements. The three top-level containers are <code class="literal">meta</code>, <code class="literal">body</code>, and <code class="literal">options</code>. The two types of elements they contain are metadata and content, carrying metadata about the page and the contents of the page, respectively. Figure 1 depicts the relationship between these six components.</p><div class="informalfigure"><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="585"><tr><td><img src="image/DRISchemaOverview.png" width="585"></td></tr></table></div></div><p>Figure 1: The two content types across three major divisions of a DRI page. The <code class="literal">document</code> element is the root for all DRI pages and contains all other elements. It bears only one attribute, <span class="emphasis"><em>version</em></span>, that contains the version number of the DRI system and the schema used to validate the produced document. At the time of writing the working version number is "1.1".</p><p>The <code class="literal">meta</code> element is a the top-level element under document and contains all metadata information about the page, the user that requested it, and the repository it is used with. It contains no structural elements, instead being the only container of metadata elements in a DRI Document. The metadata stored by the meta element is broken up into three major groups: <code class="literal">userMeta</code>, <code class="literal">pageMeta</code>, and <code class="literal">objectMeta</code>, each storing metadata information about their respective component. Please refer to the reference entries for more information about these elements.</p><p>The <code class="literal">options</code> element is another top-level element that contains all navigation and action options available to the user. The options are stored as items in list elements, broken up by the type of action they perform. The five types of actions are: browsing, search, language selection, actions that are always available, and actions that are context dependent. The two action types also contain sub-lists that contain actions available to users of varying degrees of access to the system. The <code class="literal">options</code> element contains no metadata elements and can only make use of a small set of structural elements, namely the <code class="literal">list</code> element and its children.</p><p>The last major top-level element is the <code class="literal">body</code> element. It contains all structural elements in a DRI Document, including the lists used by the <code class="literal">options</code> element. Structural elements are used to build a generic representation of a DSpace page. Any DSpace page can be represented with a combination of the structural elements, which will in turn be transformed by the XSL templates into another format. This is the core mechanism that allows DSpace XML UI to apply uniform templates and styling rules to all DSpace pages and is the fundamental difference from the JSP approach currently used by DSpace.</p><p>The <code class="literal">body</code> element directly contains only one type of element: <code class="literal">div</code>. The <code class="literal">div</code> element serves as a major division of content and any number of them can be contained by the <code class="literal">body</code>. Additionally, divisions are recursive, allowing <code class="literal">divs</code> to contain other <code class="literal">divs</code>. It is within these elements that all other structural elements are contained. Those elements include tables, paragraph elements <code class="literal">p</code>, and lists, as well as their various children elements. At the lower levels of this hierarchy lie the character container elements. These elements, namely paragraphs <code class="literal">p</code>, table <code class="literal">cells</code>, lists <code class="literal">items</code>, and the emphasis element <code class="literal">hi</code>, contain the textual content of a DSpace page, optionally modified with links, figures, and emphasis. If the division within which the character class is contained is tagged as interactive (via the <span class="emphasis"><em>interactive</em></span> attribute), those elements can also contain interactive form fields. Divisions tagged as interactive must also provide <span class="emphasis"><em>method</em></span> and <span class="emphasis"><em>action</em></span> attributes for its fields to use.</p><div class="informalfigure"><div class="mediaobject"><table cellpadding="0" cellspacing="0" summary="manufactured viewport for HTML img" border="0" width="585"><tr><td><img src="image/DRISchema.png" width="585"></td></tr></table></div></div><p>Figure 2: All the elements in the DRI schema. Note: This image is out-of-date, it does not reflect the changes between 1.0 and 1.1 such as reference and referenceSet.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14E7B"></a>13.5.&nbsp;<a name="docbook-DRISchemaReference.html-Merging_of_DRI_Documents"></a>Merging of DRI Documents</h2></div></div></div><p>Having described the structure of the DRI Document, as well as its function in Manakin's Aspect chains, we now turn our attention to the one last detail of their use: merging two Documents into one. There are several situations where the need to merge two documents arises. In Manakin, for example, every Aspect is responsible for adding different functionality to a DSpace page. Since every instance of a page has to be a complete DRI Document, each Aspect is faced with the task of merging the Document it generated with the ones generated (and merged into one Document) by previously executed Aspects. For this reason rules exist that describe which elements can be merged together and what happens to their data and child elements in the process.</p><p>When merging two DRI Documents, one is considered to be the main document, and the other a feeder document that is added in. The three top level containers (<code class="literal">meta</code>, <code class="literal">body</code> and <code class="literal">options</code>) of both documents are then individually analyzed and merged. In the case of the <code class="literal">options</code> and <code class="literal">meta</code> elements, the children tags are taken individually as well and treated differently from their siblings.</p><p>The <code class="literal">body</code> elements are the easiest to merge: their respective <code class="literal">div</code> children are preserved along with their ordering and are grouped together under one element. Thus, the new <code class="literal">body</code> tag will contain all the <code class="literal">divs</code> of the main document followed by all the <code class="literal">divs</code> of the feeder. However, if two <code class="literal">divs</code> have the same <span class="emphasis"><em>n</em></span> and <span class="emphasis"><em>rend</em></span> attributes (and in case of an interactive <code class="literal">div</code> the same <span class="emphasis"><em>action</em></span> and <span class="emphasis"><em>method</em></span> attributes as well), those <code class="literal">divs</code> will be merged into one. The resulting div will bear the <span class="emphasis"><em>id</em></span>, <span class="emphasis"><em>n</em></span>, and <span class="emphasis"><em>rend</em></span> attributes of the main document's div and contain all the <code class="literal">divs</code> of the main document followed by all the <code class="literal">divs</code> of the feeder. This process continues recursively until all the <code class="literal">divs</code> have been merged. It should be noted that two divisions with separate pagination rules cannot be merged together.</p><p>Merging the <code class="literal">options</code> elements is somewhat different. First, <code class="literal">list</code> elements under <code class="literal">options</code> of both documents are compared with each other. Those unique to either document are simply added under the new options element, just like <code class="literal">divs</code> under <code class="literal">body</code>. In case of duplicates, that is <code class="literal">list</code> elements that belong to both documents and have the same <span class="emphasis"><em>n</em></span> attribute, the two <code class="literal">lists</code> will be merged into one. The new <code class="literal">list</code> element will consist of the main document&iacute;s head element, followed <code class="literal">label-item</code> pairs from the main document, and then finally the <code class="literal">label-item</code> pairs of the feeder, provided they are different from those of the main.</p><p>Finally, the <code class="literal">meta</code> elements are merged much like the elements under body. The three children of <code class="literal">meta</code> - <code class="literal">userMeta</code>, <code class="literal">pageMeta</code>, and <code class="literal">objectMeta</code> - are individually merged, adding the contents of the feeder after the contents of the main.</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14F20"></a>13.6.&nbsp;<a name="docbook-DRISchemaReference.html-version_changes"></a>Version Changes</h2></div></div></div><p>The DRI schema will continue to evolve overtime as the needs of interface design require. The version attribute on the document will indicate which version of the schema the document conforms to. At the time Manakin was incorporated into the standard distribution of DSpac the current version was "1.1", however earlier versions of the Manakin interface may use "1.0".</p><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N14F29"></a>13.6.1.&nbsp;Changes from 1.0 to 1.1</h3></div></div></div><p>There were major structural changes between these two version numbers. Several elements were removed from the schema:<code class="literal">includeSet</code>, <code class="literal">include</code>, <code class="literal">objectMeta</code>, and <code class="literal">object</code>. Originally all metadata for objects were included in-line with the DRI document, this proved to have several problems and has been removed in version 1.1 of the DRI schema. Instead of including metadata in-line, external references to the metadata is included. Thus, a <code class="literal">reference</code> element has been added along with <code class="literal">referenceSet</code>. These new elements operate like their counterparts in the previous version except refrencing metadata contained on the <code class="literal">objectMeta</code> element they reference metadata in external files. The <code class="literal">repository</code> and <code class="literal">repositoryMeta</code> elements were alse modified in a similar mannor removing in-line metadata and refrencing external metadata documents.</p></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N14F53"></a>13.7.&nbsp;<a name="docbook-DRISchemaReference.html-Element_Reference"></a>Element Reference</h2></div></div></div><div class="informaltable"><table border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Element</strong></span>
                 </p>
@@ -434,7 +434,7 @@
                 <p>target</p>
               </td><td>
                 <p>required</p>
-              </td><td class="auto-generated">&nbsp;</td></tr></tbody></table></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N153C8"></a>13.7.1.&nbsp;<a name="docbook-DRISchemaReference.html-element:body"></a>BODY</h3></div></div></div><p>
+              </td><td class="auto-generated">&nbsp;</td></tr></tbody></table></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1544C"></a>13.7.1.&nbsp;<a name="docbook-DRISchemaReference.html-element:body"></a>BODY</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Top-Level-Container"></a>
         </p><p>Top-Level Container</p><p>The <code class="literal">body</code> element is the main container for all content displayed to the user. It contains any number of <code class="literal">div</code> elements that group content into interactive and display blocks.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:document.1"></a>
@@ -457,7 +457,7 @@
   <span class="bold"><strong> &lt;/body&gt;</strong></span>
   &lt;options&gt; ... &lt;/options&gt;
 &lt;/document&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15407"></a>13.7.2.&nbsp;<a name="docbook-DRISchemaReference.html-element:cell"></a>cell</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1548B"></a>13.7.2.&nbsp;<a name="docbook-DRISchemaReference.html-element:cell"></a>cell</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Rich-Text-Container"></a>
         </p><p>Rich Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element"></a>
@@ -486,7 +486,7 @@
     &lt;/row&gt;
     ...
 &lt;/table&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N154B9"></a>13.7.3.&nbsp;<a name="docbook-DRISchemaReference.html-element:div"></a>div</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1553D"></a>13.7.3.&nbsp;<a name="docbook-DRISchemaReference.html-element:div"></a>div</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.1"></a>
         </p><p>Structural Element</p><p>The <code class="literal">div</code> element represents a major section of content and can contain a wide variety of structural elements to present that content to the user. It can contain paragraphs, tables, and lists, as well as references to artifact information stored in <code class="literal">artifactMeta</code>, <code class="literal">repositoryMeta</code>, <code class="literal">collections</code>, and <code class="literal">communities</code>. The <code class="literal">div</code> element is also recursive, allowing it to be further divided into other divs. Divs can be of two types: interactive and static. The two types are set by the use of the <span class="emphasis"><em>interactive</em></span> attribute and differ in their ability to contain interactive content. Children elements of divs tagged as interactive can contain form fields, with the <span class="emphasis"><em>action</em></span> and <span class="emphasis"><em>method</em></span> attributes of the <code class="literal">div</code> serving to resolve those fields.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:body.1"></a>
@@ -530,7 +530,7 @@
     <span class="bold"><strong> &lt;/div&gt;</strong></span>
     ...
 &lt;/body&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N155E8"></a>13.7.4.&nbsp;<a name="docbook-DRISchemaReference.html-element:document"></a>DOCUMENT</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1566C"></a>13.7.4.&nbsp;<a name="docbook-DRISchemaReference.html-element:document"></a>DOCUMENT</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Document-Root"></a>
         </p><p>Document Root</p><p>The document element is the root container of an XML UI document. All other elements are contained within it either directly or indirectly. The only attribute it carries is the version of the Schema to which it conforms.</p><p>Parent</p><p>none</p><p>Children</p><p>
           <a name="docbook-DRISchemaReference.html--element:meta.1"></a>
@@ -551,7 +551,7 @@
       ...
     &lt;/options&gt;
 <span class="bold"><strong> &lt;/document&gt;</strong></span>
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15634"></a>13.7.5.&nbsp;<a name="docbook-DRISchemaReference.html-element:field"></a>field</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N156B8"></a>13.7.5.&nbsp;<a name="docbook-DRISchemaReference.html-element:field"></a>field</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.2"></a>
@@ -594,7 +594,7 @@
   <span class="bold"><strong> &lt;/field&gt;</strong></span>
 &lt;/p&gt;
        
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1573B"></a>13.7.6.&nbsp;<a name="docbook-DRISchemaReference.html-element:figure"></a>figure</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N157BF"></a>13.7.6.&nbsp;<a name="docbook-DRISchemaReference.html-element:figure"></a>figure</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.1"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.3"></a>
@@ -622,7 +622,7 @@
     <span class="bold"><strong> &lt;/figure&gt;</strong></span>
     ...
 &lt;/p&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N157A9"></a>13.7.7.&nbsp;<a name="docbook-DRISchemaReference.html-element:head"></a>head</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1582D"></a>13.7.7.&nbsp;<a name="docbook-DRISchemaReference.html-element:head"></a>head</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.2"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.4"></a>
@@ -659,7 +659,7 @@
     &lt;/list&gt;
     ...
 &lt;/body&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1582C"></a>13.7.8.&nbsp;<a name="docbook-DRISchemaReference.html-element:help"></a>help</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N158B0"></a>13.7.8.&nbsp;<a name="docbook-DRISchemaReference.html-element:help"></a>help</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.3"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.5"></a>
@@ -681,7 +681,7 @@
     &lt;/field&gt;
     ...
 &lt;/p&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15867"></a>13.7.9.&nbsp;<a name="docbook-DRISchemaReference.html-element:hi"></a>hi</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N158EB"></a>13.7.9.&nbsp;<a name="docbook-DRISchemaReference.html-element:hi"></a>hi</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Rich-Text-Container.1"></a>
         </p><p>Rich Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.6"></a>
@@ -707,7 +707,7 @@
 	this text is &lt;hi rend="italic"&gt;bold and
 	italic.&lt;/hi&gt;&lt;/hi&gt;</strong></span>
 &lt;/p&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N158F6"></a>13.7.10.&nbsp;<a name="docbook-DRISchemaReference.html-element:instance"></a>instance</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1597A"></a>13.7.10.&nbsp;<a name="docbook-DRISchemaReference.html-element:instance"></a>instance</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.7"></a>
         </p><p>Structural Element</p><p>The <code class="literal">instance</code> element contains the value associated with a form field&iacute;s multiple instances. Fields encoded as an instance should also include the values of each instance as a hidden field. The hidden field should be appended with the index number for the instance. Thus if the field is "firstName" each instance would be named "firstName_1", "firstName_2", "firstName_3", etc...</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:field.5"></a>
@@ -715,7 +715,7 @@
           <a name="docbook-DRISchemaReference.html--element:value.2"></a>
         </p><p>value</p><p>Attributes</p><p>None listed yet.</p><pre class="screen">
 Example needed.
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15927"></a>13.7.11.&nbsp;<a name="docbook-DRISchemaReference.html-element:item"></a>item</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N159AB"></a>13.7.11.&nbsp;<a name="docbook-DRISchemaReference.html-element:item"></a>item</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Rich-Text-Container.2"></a>
         </p><p>Rich Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.8"></a>
@@ -760,7 +760,7 @@ Example needed.
 	&lt;/item&gt;</strong></span>
   ...
 &lt;/list&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N159CB"></a>13.7.12.&nbsp;<a name="docbook-DRISchemaReference.html-element:label"></a>label</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15A4F"></a>13.7.12.&nbsp;<a name="docbook-DRISchemaReference.html-element:label"></a>label</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.4"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.9"></a>
@@ -797,7 +797,7 @@ Example needed.
   &lt;item&gt; This is the third item in the list &lt;/item&gt;
   ...
 &lt;/list&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15A29"></a>13.7.13.&nbsp;<a name="docbook-DRISchemaReference.html-element:list"></a>list</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15AAD"></a>13.7.13.&nbsp;<a name="docbook-DRISchemaReference.html-element:list"></a>list</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.10"></a>
         </p><p>Structural Element</p><p>The <code class="literal">list</code> element is used to display sets of sequential data. It contains an optional <code class="literal">head</code> element, as well as any number of <code class="literal">item</code> and <code class="literal">list</code> elements. <code class="literal">Items</code> contain textual information, while sublists contain other <code class="literal">item</code> or <code class="literal">list</code> elements. An <code class="literal">item</code> can also be associated with a <code class="literal">label</code> element that annotates an item with a number, a textual description of some sort, or a simple bullet. The list type (ordered, bulleted, gloss, etc.) is then determined either by the content of <code class="literal">labels</code> on <code class="literal">items</code> or by an explicit value of the <span class="emphasis"><em>type</em></span> attribute. Note that if <code class="literal">labels</code> are used in conjunction with any <code class="literal">items</code> in a list, all of the <code class="literal">items</code> in that list must have a <code class="literal">label</code>. It is also recommended to avoid mixing <code class="literal">label</code> styles unless an explicit type is specified.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:div.5"></a>
@@ -838,7 +838,7 @@ Example needed.
     ...
   <span class="bold"><strong> &lt;/list&gt;</strong></span>
 &lt;/div&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15B65"></a>13.7.14.&nbsp;<a name="docbook-DRISchemaReference.html-element:meta"></a>META</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15BE9"></a>13.7.14.&nbsp;<a name="docbook-DRISchemaReference.html-element:meta"></a>META</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Top-Level-Container.1"></a>
         </p><p>Top-Level Container</p><p>The <code class="literal">meta</code> element is a top level element and exists directly inside the <code class="literal">document</code> element. It serves as a container element for all metadata associated with a document broken up into categories according to the type of metadata they carry.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:document.2"></a>
@@ -858,7 +858,7 @@ Example needed.
   &lt;body&gt; ... &lt;/body&gt;
   &lt;options&gt; ... &lt;/options&gt;
 &lt;/document&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15BB8"></a>13.7.15.&nbsp;<a name="docbook-DRISchemaReference.html-element:metadata"></a>metadata</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15C3C"></a>13.7.15.&nbsp;<a name="docbook-DRISchemaReference.html-element:metadata"></a>metadata</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.5"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.11"></a>
@@ -887,7 +887,7 @@ Example needed.
     ...
   &lt;/pageMeta&gt;
 &lt;/meta&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15C27"></a>13.7.16.&nbsp;<a name="docbook-DRISchemaReference.html-element:options"></a>OPTIONS</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15CAB"></a>13.7.16.&nbsp;<a name="docbook-DRISchemaReference.html-element:options"></a>OPTIONS</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Top-Level-Container.2"></a>
         </p><p>Top-Level Container</p><p>The <code class="literal">options</code> element is the main container for all actions and navigation options available to the user. It consists of any number of <code class="literal">list</code> elements whose items contain navigation information and actions. While any list of navigational options may be contained in this element, it is suggested that at least the following 5 lists be included.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:document.3"></a>
@@ -937,7 +937,7 @@ Example needed.
     <span class="bold"><strong> &lt;/options&gt;</strong></span>
 
 &lt;/document&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15C66"></a>13.7.17.&nbsp;<a name="docbook-DRISchemaReference.html-element:p"></a>p</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15CEA"></a>13.7.17.&nbsp;<a name="docbook-DRISchemaReference.html-element:p"></a>p</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Rich-Text-Container.3"></a>
         </p><p>Rich Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.12"></a>
@@ -969,7 +969,7 @@ Example needed.
 	&lt;/p&gt;</strong></span>
 
 &lt;/div&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15CE6"></a>13.7.18.&nbsp;<a name="docbook-DRISchemaReference.html-element:pageMeta"></a>pageMeta</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15D6A"></a>13.7.18.&nbsp;<a name="docbook-DRISchemaReference.html-element:pageMeta"></a>pageMeta</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Element"></a>
         </p><p>Metadata Element</p><p>The <code class="literal">pageMeta</code> element contains metadata associated with the document itself. It contains generic <code class="literal">metadata</code> elements to carry the content, and any number of <code class="literal">trail</code> elements to provide information on the user&iacute;s current location in the system. Required and suggested values for <code class="literal">metadata</code> elements contained in <code class="literal">pageMeta</code> include but are not limited to:</p><div class="itemizedlist"><ul type="disc"><li><p> browser (suggested): The user&iacute;s browsing agent as reported to server in the HTTP request.</p></li><li><p> browser.type (suggested): The general browser family as derived form the browser metadata field. Possible values may include "MSIE" (for Microsoft Internet Explorer), "Opera" (for the Opera browser), "Apple" (for Apple web kit based browsers), "Gecko" (for Netscape, Mozilla, and Firefox based browsers), or "Lynx" (for text based browsers).</p></li><li><p> browser.version (suggested): The browser version as reported by HTTP Request.</p></li><li><p> contextPath (required): The base URL of the Digital Repository system.</p></li><li><p> redirect.time (suggested): The time that must elapse before the page is redirected to an address specified by the redirect.url <code class="literal">metadata</code> element.</p></li><li><p> redirect.url (suggested): The URL destination of a redirect page</p></li><li><p> title (required): The title of the document/page that the user currently browsing.</p></li></ul></div><p> See the <code class="literal">metadata</code> and <code class="literal">trail</code> tag entries for more information on their structure. </p><p>Parent<a name="docbook-DRISchemaReference.html--element:meta.2"></a>metaChildren<a name="docbook-DRISchemaReference.html--element:metadata.1"></a>metadata (any)<a name="docbook-DRISchemaReference.html--element:trail.1"></a>trail
 	(any)AttributesNone<pre class="screen">
@@ -1000,7 +1000,7 @@ Example needed.
 
 &lt;/meta&gt;
 </pre>          
-</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15D4B"></a>13.7.19.&nbsp;<a name="docbook-DRISchemaReference.html-element:params"></a>params</h3></div></div></div><p>
+</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15DCF"></a>13.7.19.&nbsp;<a name="docbook-DRISchemaReference.html-element:params"></a>params</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Component"></a>
         </p><p>Structural Component</p><p>The <code class="literal">params</code> element identifies extra parameters used to build a form field. There are several attributes that may be available for this element depending on the field type.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:field.8"></a>
@@ -1021,7 +1021,7 @@ Example needed.
     &lt;/field&gt;
 
 &lt;/p&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15DAD"></a>13.7.20.&nbsp;<a name="docbook-DRISchemaReference.html-element:reference"></a>reference</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15E31"></a>13.7.20.&nbsp;<a name="docbook-DRISchemaReference.html-element:reference"></a>reference</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Reference-Element"></a>
         </p><p>Metadata Reference Element</p><p><code class="literal">reference</code> is a reference element used to access information stored in an extarnal metadata file. The <span class="emphasis"><em>url</em></span> attribute is used to locate the external metadata file. The <span class="emphasis"><em>type</em></span> attribute provides a short limited description of the referenced object's type.</p><p><code class="literal">reference</code> elements can be both contained by <code class="literal">includeSet</code> elements and contain <code class="literal">includeSets</code> themselves, making the structure recursive.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:referenceSet.3"></a>
@@ -1038,7 +1038,7 @@ Example needed.
             ...
             &lt;/includeSet&gt;
          
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15E11"></a>13.7.21.&nbsp;<a name="docbook-DRISchemaReference.html-element:referenceSet"></a>referenceSet</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15E95"></a>13.7.21.&nbsp;<a name="docbook-DRISchemaReference.html-element:referenceSet"></a>referenceSet</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Reference-Element.1"></a>
         </p><p>Metadata Reference Element</p><p>The <code class="literal">referenceSet</code> element is a container of artifact or repository references.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:div.7"></a>
@@ -1068,7 +1068,7 @@ Example needed.
             <span class="bold"><strong> &lt;/referenceSet&gt;</strong></span>
             ...
             &lt;/p&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15E9F"></a>13.7.22.&nbsp;<a name="docbook-DRISchemaReference.html-element:repository"></a>repository</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15F23"></a>13.7.22.&nbsp;<a name="docbook-DRISchemaReference.html-element:repository"></a>repository</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Element.1"></a>
         </p><p>Metadata Element</p><p>The <code class="literal">repository</code> element is used to describe the repository. Its principal component is a set of structural metadata that carrier information on how the repository&iacute;s objects under <code class="literal">objectMeta</code> are related to each other. The principal method of encoding these relationships at the time of this writing is a METS document, although other formats, like RDF, may be employed in the future.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:repositoryMeta.2"></a>
@@ -1079,7 +1079,7 @@ Example needed.
 	url="/metadata/handle/1234/4/mets.xml" /&gt;</strong></span>
 
 &lt;/repositoryMeta&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15EE5"></a>13.7.23.&nbsp;<a name="docbook-DRISchemaReference.html-element:repositoryMeta"></a>repositoryMeta</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15F69"></a>13.7.23.&nbsp;<a name="docbook-DRISchemaReference.html-element:repositoryMeta"></a>repositoryMeta</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Element.2"></a>
         </p><p>Metadata Element</p><p>The <code class="literal">repositoryMeta</code> element contains metadata refernces about the repositories used in the used or referenced in the document. It can contain any number of <code class="literal">repository</code> elements.</p><p>See the <code class="literal">repository</code> tag entry for more information on the structure of <code class="literal">repository</code> elements.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:Meta"></a>
@@ -1100,7 +1100,7 @@ Example needed.
     <span class="bold"><strong> &lt;/repositoryMeta&gt;</strong></span>
 
 &lt;/meta&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15F2E"></a>13.7.24.&nbsp;<a name="docbook-DRISchemaReference.html-element:row"></a>row</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15FB2"></a>13.7.24.&nbsp;<a name="docbook-DRISchemaReference.html-element:row"></a>row</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.13"></a>
         </p><p>Structural Element</p><p>The row element is contained inside a <code class="literal">table</code> and serves as a container of <code class="literal">cell</code> elements. A required <span class="emphasis"><em>role</em></span> attribute determines how the row and its cells are rendered.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:table.3"></a>
@@ -1135,7 +1135,7 @@ Example needed.
     ...
 
 &lt;/table&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N15F93"></a>13.7.25.&nbsp;<a name="docbook-DRISchemaReference.html-element:table"></a>table</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16017"></a>13.7.25.&nbsp;<a name="docbook-DRISchemaReference.html-element:table"></a>table</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.14"></a>
         </p><p>Structural Element</p><p>The <code class="literal">table</code> element is a container for information presented in tabular format. It consists of a set of <code class="literal">row</code> elements and an optional <code class="literal">header</code>.</p><p>Parent</p><p>
           <a name="docbook-DRISchemaReference.html--element:div.8"></a>
@@ -1178,7 +1178,7 @@ Example needed.
     <span class="bold"><strong> &lt;/table&gt;</strong></span>
     ...
 &lt;/div&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16007"></a>13.7.26.&nbsp;<a name="docbook-DRISchemaReference.html-element:trail"></a>trail</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1608B"></a>13.7.26.&nbsp;<a name="docbook-DRISchemaReference.html-element:trail"></a>trail</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.6"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Element.3"></a>
@@ -1203,7 +1203,7 @@ Example needed.
     ...
 
 &lt;/pageMeta&gt;
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1604D"></a>13.7.27.&nbsp;<a name="docbook-DRISchemaReference.html-element:userMeta"></a>userMeta</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N160D1"></a>13.7.27.&nbsp;<a name="docbook-DRISchemaReference.html-element:userMeta"></a>userMeta</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Metadata-Element.4"></a>
         </p><p>Metadata Element</p><p>The <code class="literal">userMeta</code> element contains metadata associated with the user that requested the document. It contains generic <code class="literal">metadata</code> elements, which in turn carry the information. Required and suggested values for <code class="literal">metadata</code> elements contained in <code class="literal">userMeta</code> include but not limited to:</p><div class="itemizedlist"><ul type="disc"><li><p> identifier (suggested): A unique identifier associated with the user.</p></li><li><p> identifier.email (suggested): The requesting user&iacute;s email address.</p></li><li><p> identifier.firstName (suggested): The requesting user&iacute;s first name.</p></li><li><p> identifier.lastName (suggested): The requesting user&iacute;s last name.</p></li><li><p> identifier.logoutURL (suggested): The URL that a user will be taken to when logging out.</p></li><li><p> identifier.url (suggested): A url reference to the user&iacute;s page within the repository.</p></li><li><p> language.RFC3066 (suggested): The requesting user&iacute;s preferred language selection code as describe by RFC3066</p></li><li><p> rights.accessRights (required): Determines the scope of actions that a user can perform in the system. Accepted values are: </p><div class="itemizedlist"><ul type="circle"><li><p> none: The user is either not authenticated or does not have a valid account on the system</p></li><li><p> user: The user is authenticated and has a valid account on the system</p></li><li><p> admin: The user is authenticated and belongs to the system&iacute;s administrative group</p></li></ul></div></li></ul></div><p> See the <code class="literal">metadata</code> tag entry for more information on the structure of <code class="literal">metadata</code> elements. </p><p>Parent<a name="docbook-DRISchemaReference.html--element:meta.3"></a>metaChildren<a name="docbook-DRISchemaReference.html--element:metadata.2"></a>metadata (any)Attributes<div class="variablelist"><dl><dt><span class="term">authenticated</span></dt><dd><p>required</p><p>Accepted values are "yes", "no". Determines whether the user has been authenticated by the system.</p></dd></dl></div>
 <pre class="screen">
@@ -1244,7 +1244,7 @@ Example needed.
 
 &lt;/meta&gt;
 </pre>          
-</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N160BD"></a>13.7.28.&nbsp;<a name="docbook-DRISchemaReference.html-element:value"></a>value</h3></div></div></div><p>
+</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16141"></a>13.7.28.&nbsp;<a name="docbook-DRISchemaReference.html-element:value"></a>value</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Rich-Text-Container.4"></a>
         </p><p>Rich Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.15"></a>
@@ -1272,7 +1272,7 @@ Example needed.
   &lt;/field&gt; 
 &lt;/p&gt;
        
-</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16137"></a>13.7.29.&nbsp;<a name="docbook-DRISchemaReference.html-element:xref"></a>xref</h3></div></div></div><p>
+</pre></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N161BB"></a>13.7.29.&nbsp;<a name="docbook-DRISchemaReference.html-element:xref"></a>xref</h3></div></div></div><p>
           <a name="docbook-DRISchemaReference.html--type:Text-Container.7"></a>
         </p><p>Text Container</p><p>
           <a name="docbook-DRISchemaReference.html--type:Structural-Element.16"></a>
@@ -1291,7 +1291,7 @@ Example needed.
 	link.&lt;/xref&gt;</strong></span>
 
 &lt;/p&gt;
-</pre></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+</pre></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch14.html b/dspace/docs/html/ch14.html
index f7ec5d9382..f89675dda9 100644
--- a/dspace/docs/html/ch14.html
+++ b/dspace/docs/html/ch14.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch13.html" title="Chapter&nbsp;13.&nbsp;DRI Schema Reference"><link rel="next" href="ch15.html" title="Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch13.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch15.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N16191"></a>Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch14.html#N16195">14.1. Changes in DSpace 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1619C">14.1.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N161B9">14.1.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16212">14.2. Changes in DSpace 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16219">14.2.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1626F">14.2.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N162E6">14.3. Changes in DSpace 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N162ED">14.3.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1633A">14.3.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16369">14.4. Changes in DSpace 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16370">14.4.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1637E">14.4.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1638C">14.5. Changes in DSpace 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16393">14.5.1. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1639B">14.6. Changes in DSpace 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N163A2">14.6.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N163C8">14.6.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16409">14.7. Changes in DSpace 1.2.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16410">14.7.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1642D">14.7.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16441">14.7.3. Changes in JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16525">14.8. Changes in DSpace 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1652C">14.8.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16550">14.8.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16564">14.8.3. Changed JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16616">14.9. Changes in DSpace 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1661D">14.9.1. General Improvments</a></span></dt><dt><span class="section"><a href="ch14.html#N16637">14.9.2. Administration</a></span></dt><dt><span class="section"><a href="ch14.html#N16651">14.9.3. Import/Export/OAI</a></span></dt><dt><span class="section"><a href="ch14.html#N1665F">14.9.4. Miscellaneous</a></span></dt><dt><span class="section"><a href="ch14.html#N16673">14.9.5. JSP file changes between 1.1 and 1.2</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1679E">14.10. Changes in DSpace 1.1.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N167A5">14.10.1. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N167BC">14.10.2. Improvements</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N167E6">14.11. Changes in DSpace 1.1</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16195"></a>14.1.&nbsp;<a name="docbook-history.html-version1_5"></a>Changes in DSpace 1.5</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1619C"></a>14.1.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Highly configurable and theme-able new user interface (Manakin).</p></li><li><p> Apache Maven-based modular build system.</p></li><li><p> LNI (Lightweight Network Interface) service. Allows programmatic ingest of content via WebDAV or SOAP.</p></li><li><p> SWORD (Simple Web-service Offering Repository Deposit): repository-standard ingest service using Atom Publishing Protocol.</p></li><li><p> Highly configurable item web submission system. All submission steps are configurable not just metadata pages.</p></li><li><p> Browse functionality allowing customisation of the available indexes via dspace.cfg and pluggable normalisation of the sort strings. Integration with both JSP-UI and XML-UI included.</p></li><li><p> Extensible content event notification service.</p></li><li><p> Generation of Google and HTML sitemaps</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N161B9"></a>14.1.2.&nbsp;Bug fixes and smaller patches</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> New options for ItemImporter to support bitstream permissions and descriptions.</p></li><li><p> 1824710 Fix - Change in Creative Commons RDF.</p></li><li><p> 1794700 Fix - Stat-monthly and stat-report-monthly</p></li><li><p> 1566820 Patch - Authentication code moved to new org.dspace.authenticate package, add IP AUth</p></li><li><p> 1670093 Patch - More stable metadata and schema registry import Option to generate community and collection "strength" as a batch job</p></li><li><p> 1659868 Patch - Improved database level debugging</p></li><li><p> 1620700 Patch - Add Community and Sub-Community to OAI Sets</p></li><li><p> 1679972 Fix - OAIDCCrosswalk NPE and invalid character fix, also invalid output prevented</p></li><li><p> 1549290 Fix - Suggest Features uses hard coded strings</p></li><li><p> 1727034 Fix - Method MetadataField.unique() is incorrect for null values</p></li><li><p> 1614546 Fix - Get rid of unused mets_bitstream_id column</p></li><li><p> 1450491 Patch - i18n configurable multilingualism support</p></li><li><p> 1764069 Patch - Replace "String" with "Integer" in PreparedStatement where needed</p></li><li><p> 1743188 Patch - for Request #1145499 - Move Items</p></li><li><p> 179196 Patch - Oracle SQL in Bitstream Checker</p></li><li><p> 1751638 Patch - Set http disposition header to force download of large bitstreams</p></li><li><p> 1799575 Patch - New EPersonConsumer event consumer</p></li><li><p> 1566572 Patch - Item metadata in XHTML head elements</p></li><li><p> 1589429 Patch - "Self-Named" Media Filters (i.e. MediaFilter Plugins) (updated version of this patch)</p></li><li><p> 1888652 Patch - Statistics Rewritten In Java</p></li><li><p> 1444364 Request - Metadata registry exporter</p></li><li><p> 1221957 Request - Admin browser for withdrawn items</p></li><li><p> 1740454 Fix - Concurrency</p></li><li><p> 1552760 Fix - Submit interface looks bad in Safari</p></li><li><p> 1642563 Patch - bin/update-handle-prefix rewritten in Java</p></li><li><p> 1724330 Fix - Removes "null" being displayed in community-home.jsp</p></li><li><p> 1763535 Patch - Alert DSpace administrator of new user registration</p></li><li><p> 1759438 Patch - Multilingualism Language Switch - DSpace Header</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16212"></a>14.2.&nbsp;<a name="docbook-history.html-version1_4_1"></a>Changes in DSpace 1.4.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16219"></a>14.2.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Error pages now return appropriate HTTP status codes (e.g. 404 not found)</p></li><li><p> Bad filenames in /bitstream/ URLs now result in 404 error -- prevents infinite URL spaces confusing crawlers and bad "persistent" bitstream IDs circulating</p></li><li><p> Prevent infinite URL spaces in HTMLServlet</p></li><li><p> InstallItem no longer sets dc.format.extent, dc.format.mimetype; no longer sets default value for dc.language.iso if one is not present</p></li><li><p> Empty values in drop-down submit fields are not added as empty metadata values</p></li><li><p> API methods for searching epeople and groups</p></li><li><p> Support stats from both 1.3 and 1.4</p></li><li><p> [dspace]/bin/update-handle-prefix now runs index-all</p></li><li><p> Remove cases of System.out from code executed in webapp</p></li><li><p> Change "View Licence" to "View License" in Messages.properties</p></li><li><p> dspace.cfg comments changed to indicate what default.language actually means</p></li><li><p> HandleServlet and BitstreamServlet support If-Modified-Since requests</p></li><li><p> Improved sanity-checking of XSL-based ingest crosswalks</p></li><li><p> Remove thumbnail filename from alt-text</p></li><li><p> Include item title in HTML title element</p></li><li><p> Improvements to help prevent spammers and sploggers</p></li><li><p> Make cleanup() commit outstanding work every 100 iterations</p></li><li><p> Better handling where email send failed due to wrong address for new user</p></li><li><p> Include robots.txt to limit bots navigating author, date and browse by subject pages</p></li><li><p> Add css styles for print media</p></li><li><p> RSS made more configurable and provide system-wide RSS feed, also moves text to Messages.properties</p></li><li><p> Jar file updates (includes required code changes for DSIndexer and DSQuery and new jars fontbox.jar and serializer.jar)</p></li><li><p> Various documentation additions and cleanups</p></li><li><p> XHTML compliance improvements</p></li><li><p> Move w3c valid xhtml boiler image into local repository</p></li><li><p> Remove uncessary Log4j Configuration in CheckerCommand</p></li><li><p> Include Windows CLASSPATH in dsrun.bat</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1626F"></a>14.2.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1604037 - UIUtil.encodeBitstream() now correctly encodes URLs (no longer incorrectly substitutes '+' for spaces in non-query segment</p></li><li><p> 1592984 - Date comparisons strip time in org.dspace.harvest.Harvest</p></li><li><p> 1589902 - Duplicate [field] checking error [on input-forms.xml]</p></li><li><p> 1596952 - Collection Wizard create Template missing schema</p></li><li><p> 1596978 - View unfinished submissions - collection empty</p></li><li><p> 1588625 - Incorrect text on item mapper screen</p></li><li><p> 1597805 - DIDL Crosswalk: wrong resource management</p></li><li><p> 1605635 - NPE in Utils.java</p></li><li><p> 1597504 - Search result page shows shortened query string</p></li><li><p> 1532389 - Item Templates do not work for non-dc fields</p></li><li><p> 1066771 - Metadata edit form dropping DC qualifier</p></li><li><p> 1548738 - Multiple Metadata Schema, schema not shown on edit item page</p></li><li><p> 1589895 - Not possible to add unqualified Metadata Field</p></li><li><p> 1543853 - Statistics do not work in 1.4</p></li><li><p> 1541381 - Browse-by-date and browse-by-title not working</p></li><li><p> 1556947 - NullPointerException when no user selected to del/edit</p></li><li><p> 1554064 - Fix exception handling for ClassCastException in BitstreamServlet</p></li><li><p> 1548865 - Browse errors on withdrawn item</p></li><li><p> 1554056 - Community/collection handle URL with / redirects to homepage</p></li><li><p> 1571490 - UTF-8 encoded characters in licence</p></li><li><p> 1571519 - UTF-8 in statistics</p></li><li><p> 1544807 - Browse-by-Subject/Author paging mechanism broken</p></li><li><p> 1543966 - "Special" groups inside groups bug</p></li><li><p> 1480496 - Cannot turn off "ignore authorization" flag!</p></li><li><p> 1515148 - Community policies not deleting correctly</p></li><li><p> 1556829 - Docs mention old SiteAuthenticator class</p></li><li><p> 1606435 - Workflow text out of context</p></li><li><p> Fix for bitstream authorization timeout</p></li><li><p> Fix to make sure cleanup() doesn't fail with NullPointerException</p></li><li><p> Fix for removeBitstream() failing to update primary bitstream</p></li><li><p> Fix for Advanced Search ignoring conjunctions for arbitrary number of queries</p></li><li><p> Fix minor bug in Harvest.java for Oracle users</p></li><li><p> Fix missing title for news editor page</p></li><li><p> Small Messages.properties modification (change of DSpace copyright text)</p></li><li><p> fix PDFBox tmp file issue</p></li><li><p> Fix HttpServletRequest encoding issues</p></li><li><p> Fix bug in TableRow toString() method where NPE is thrown if tablename not set</p></li><li><p> Update DIDL license and change coding style to DSpace standard</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N162E6"></a>14.3.&nbsp;<a name="docbook-history.html-version1_4"></a>Changes in DSpace 1.4</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N162ED"></a>14.3.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Content verification through periodic checksum checking</p></li><li><p> Support for branded preview image</p></li><li><p> Add/replace Creative Commons in 'edit item' tool</p></li><li><p> Customisable item listing columns and browse indices</p></li><li><p> Script for updating handle prefixes (e.g. for moving from development to production)</p></li><li><p> Configurable boolean search operator</p></li><li><p> Controlled vocabulary patch to provide search on classification terms, and addition of terms during submission.</p></li><li><p> Add 'visibility' element to input-forms.xml</p></li><li><p> Browse by subject feature</p></li><li><p> Log4J enhancement to use XML configuration</p></li><li><p> QueryArgs class can support any number of fields in advanced search.</p></li><li><p> Community names no longer have to be unique</p></li><li><p> Enhanced Windows support</p></li><li><p> Support for multiple (flat) metadata schemas</p></li><li><p> Suggest an item page</p></li><li><p> RSS Feeds</p></li><li><p> Performance enhancements</p></li><li><p> Stackable authentication methods</p></li><li><p> Plug-in manager</p></li><li><p> Pluggable SIP/DIP support and metadata crosswalks</p></li><li><p> Nested groups of e-people</p></li><li><p> Expose METS and MPEG-21 DIDL DIPs via OAI-PMH</p></li><li><p> Configurable Lucene search analyzer (e.g. for Chinese metadata)</p></li><li><p> Support for SMTP servers requiring authentication</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1633A"></a>14.3.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1358197 - Edit Item, empty DC fields not removable</p></li><li><p> 1363633 - Submission step 1 fails when there are no collections</p></li><li><p> 1255264 - Resource policy eperson value was set to wrong column</p></li><li><p> 1380494 - Error deleting an item with multiple metadata schema support</p></li><li><p> 1443649 - Cannot configure unqualified elements for advanced search index</p></li><li><p> 1333687 - Browse-(title|date) fails on withdrawn item</p></li><li><p> 1066713 - Two (sub)communities cannot have one name</p></li><li><p> 1284055 - Two Communities of same name throws error</p></li><li><p> 1035366 - Bitstream size column should be bigint</p></li><li><p> 1352257 - Selecting a Group for GroupToGroup while Creating Collection</p></li><li><p> 1352226 - Navigation and Sorting in Group List (Select Groups) fails</p></li><li><p> 1348276 - Null in collection name causes OAI ListSets to fail</p></li><li><p> 1160898 - dspace_migrate removes Date.Issued from prev published items</p></li><li><p> 1261191 - Malformed METS metadata exported</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16369"></a>14.4.&nbsp;<a name="docbook-history.html-version1_3_2"></a>Changes in DSpace 1.3.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16370"></a>14.4.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> DSpace UI XHTML/WAI compliant</p></li><li><p> Configure metadata fields shown on simple item display</p></li><li><p> Supervisor/workspace help documentation</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1637E"></a>14.4.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Oracle compatibility fixes</p></li><li><p> Item exporter now correctly exports metadata in UTF-8</p></li><li><p> fixed to handle 'null' values passed in</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1638C"></a>14.5.&nbsp;<a name="docbook-history.html-version1_3_1"></a>Changes in DSpace 1.3.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16393"></a>14.5.1.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1252153 - Error on fresh install</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1639B"></a>14.6.&nbsp;<a name="docbook-history.html-version1_3"></a>Changes in DSpace 1.3</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N163A2"></a>14.6.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Initial i18n Support for JSPs - Note: the implementation of this feature required changes to almost all JSP pages</p></li><li><p> LDAP authentication support</p></li><li><p> Log file analysis and report generation</p></li><li><p> Configurable item licence viewing</p></li><li><p> Supervision order/collaborative workspace administrative tools</p></li><li><p> Basic workspace for submissions in progress, with support for supervision</p></li><li><p> SRB storage system option</p></li><li><p> Updated handle server system</p></li><li><p> Database optimisations</p></li><li><p> Latest versions of Xerces, Xalan and OAICAT jars</p></li><li><p> Various documentation additions and cleanups</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N163C8"></a>14.6.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1161459 - ItemExporter fails with Too many open files</p></li><li><p> 1167373 - Email date field not populated</p></li><li><p> 1193948 - New item submit problem</p></li><li><p> 1188132 - NullPointerException when Adding EPerson</p></li><li><p> 1188016 - Cannot Edit an Eperson</p></li><li><p> 1219701 - Unable to open unfinished submission</p></li><li><p> 1206836 - community strengths not reflecting sub-community</p></li><li><p> 1238262 - Submit UI nav/progress buttons no longer show progress</p></li><li><p> 1238276 - Double quote problem in some fields in submit UI</p></li><li><p> 1238277 - format support level not shown in "uploaded file" page</p></li><li><p> 1242548 - Uploading non-existing files</p></li><li><p> 1244743 - Bad lookup key for special case of DC Title in ItemTag.java</p></li><li><p> 1245223 - Subscription Emailer fails</p></li><li><p> 1247508 - Error when browsing item with no content/bitstream collections</p></li><li><p> Set the content type in the HTTP header</p></li><li><p> Fix issue where EPerson edit would not work due to form indexing (partial fix)</p></li><li><p> POST handling in HTMLServlet</p></li><li><p> Missing ContentType directives added to some JSPs</p></li><li><p> Name dependency on Collection Admin and Submitter groups fixed</p></li><li><p> Fixed OAI-PMH XML encoding</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16409"></a>14.7.&nbsp;<a name="docbook-history.html-version1_2_2"></a>Changes in DSpace 1.2.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16410"></a>14.7.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Customisable submission forms added</p></li><li><p> Configurable number of index terms in Lucene for full-text indexing</p></li><li><p> Improved scalability in media filter</p></li><li><p> Submit button on collection pages only appears if user has authorisation</p></li><li><p> PostgreSQL 8.0 compatibility</p></li><li><p> Search scope retention to improve browsing</p></li><li><p> Community and collection strengths displayed</p></li><li><p> Upgraded OAICat software</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1642D"></a>14.7.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Fix for Oracle too many cursors problem.</p></li><li><p> Fix for UTF-8 encoded searches in advanced search.</p></li><li><p> Fix for handling "\" in bitstream names.</p></li><li><p> Fix to prevent delete of "unknown" bitstream format</p></li><li><p> Fix for ItemImport creating new handles for replaced items</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16441"></a>14.7.3.&nbsp;<a name="docbook-history.html-jsp-changes-1_2_1-1_2_2"></a>Changes in JSPs</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch13.html" title="Chapter&nbsp;13.&nbsp;DRI Schema Reference"><link rel="next" href="ch15.html" title="Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch13.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch15.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N16215"></a>Chapter&nbsp;14.&nbsp;<a name="docbook-history.html"></a>DSpace System Documentation: Version History</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch14.html#N1621B">14.1. Changes in DSpace 1.5.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16222">14.1.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1622A">14.1.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16232">14.2. Changes in DSpace 1.5.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16239">14.2.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16241">14.2.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16249">14.3. Changes in DSpace 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16250">14.3.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1626D">14.3.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N162C6">14.4. Changes in DSpace 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N162CD">14.4.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16323">14.4.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1639A">14.5. Changes in DSpace 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N163A1">14.5.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N163EE">14.5.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1641D">14.6. Changes in DSpace 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16424">14.6.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16432">14.6.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16440">14.7. Changes in DSpace 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16447">14.7.1. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1644F">14.8. Changes in DSpace 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16456">14.8.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1647C">14.8.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N164BD">14.9. Changes in DSpace 1.2.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N164C4">14.9.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N164E1">14.9.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N164F5">14.9.3. Changes in JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N165D9">14.10. Changes in DSpace 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N165E0">14.10.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16604">14.10.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16618">14.10.3. Changed JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N166CA">14.11. Changes in DSpace 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N166D1">14.11.1. General Improvments</a></span></dt><dt><span class="section"><a href="ch14.html#N166EB">14.11.2. Administration</a></span></dt><dt><span class="section"><a href="ch14.html#N16705">14.11.3. Import/Export/OAI</a></span></dt><dt><span class="section"><a href="ch14.html#N16713">14.11.4. Miscellaneous</a></span></dt><dt><span class="section"><a href="ch14.html#N16727">14.11.5. JSP file changes between 1.1 and 1.2</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16852">14.12. Changes in DSpace 1.1.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16859">14.12.1. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16870">14.12.2. Improvements</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1689A">14.13. Changes in DSpace 1.1</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1621B"></a>14.1.&nbsp;<a name="docbook-history.html-version1_5_2"></a>Changes in DSpace 1.5.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16222"></a>14.1.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> TBD</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1622A"></a>14.1.2.&nbsp;Bug fixes and smaller patches</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> TBD</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16232"></a>14.2.&nbsp;<a name="docbook-history.html-version1_5_1"></a>Changes in DSpace 1.5.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16239"></a>14.2.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> TBD</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16241"></a>14.2.2.&nbsp;Bug fixes and smaller patches</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> TBD</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16249"></a>14.3.&nbsp;<a name="docbook-history.html-version1_5"></a>Changes in DSpace 1.5</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16250"></a>14.3.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Highly configurable and theme-able new user interface (Manakin).</p></li><li><p> Apache Maven-based modular build system.</p></li><li><p> LNI (Lightweight Network Interface) service. Allows programmatic ingest of content via WebDAV or SOAP.</p></li><li><p> SWORD (Simple Web-service Offering Repository Deposit): repository-standard ingest service using Atom Publishing Protocol.</p></li><li><p> Highly configurable item web submission system. All submission steps are configurable not just metadata pages.</p></li><li><p> Browse functionality allowing customisation of the available indexes via dspace.cfg and pluggable normalisation of the sort strings. Integration with both JSP-UI and XML-UI included.</p></li><li><p> Extensible content event notification service.</p></li><li><p> Generation of Google and HTML sitemaps</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1626D"></a>14.3.2.&nbsp;Bug fixes and smaller patches</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> New options for ItemImporter to support bitstream permissions and descriptions.</p></li><li><p> 1824710 Fix - Change in Creative Commons RDF.</p></li><li><p> 1794700 Fix - Stat-monthly and stat-report-monthly</p></li><li><p> 1566820 Patch - Authentication code moved to new org.dspace.authenticate package, add IP AUth</p></li><li><p> 1670093 Patch - More stable metadata and schema registry import Option to generate community and collection "strength" as a batch job</p></li><li><p> 1659868 Patch - Improved database level debugging</p></li><li><p> 1620700 Patch - Add Community and Sub-Community to OAI Sets</p></li><li><p> 1679972 Fix - OAIDCCrosswalk NPE and invalid character fix, also invalid output prevented</p></li><li><p> 1549290 Fix - Suggest Features uses hard coded strings</p></li><li><p> 1727034 Fix - Method MetadataField.unique() is incorrect for null values</p></li><li><p> 1614546 Fix - Get rid of unused mets_bitstream_id column</p></li><li><p> 1450491 Patch - i18n configurable multilingualism support</p></li><li><p> 1764069 Patch - Replace "String" with "Integer" in PreparedStatement where needed</p></li><li><p> 1743188 Patch - for Request #1145499 - Move Items</p></li><li><p> 179196 Patch - Oracle SQL in Bitstream Checker</p></li><li><p> 1751638 Patch - Set http disposition header to force download of large bitstreams</p></li><li><p> 1799575 Patch - New EPersonConsumer event consumer</p></li><li><p> 1566572 Patch - Item metadata in XHTML head elements</p></li><li><p> 1589429 Patch - "Self-Named" Media Filters (i.e. MediaFilter Plugins) (updated version of this patch)</p></li><li><p> 1888652 Patch - Statistics Rewritten In Java</p></li><li><p> 1444364 Request - Metadata registry exporter</p></li><li><p> 1221957 Request - Admin browser for withdrawn items</p></li><li><p> 1740454 Fix - Concurrency</p></li><li><p> 1552760 Fix - Submit interface looks bad in Safari</p></li><li><p> 1642563 Patch - bin/update-handle-prefix rewritten in Java</p></li><li><p> 1724330 Fix - Removes "null" being displayed in community-home.jsp</p></li><li><p> 1763535 Patch - Alert DSpace administrator of new user registration</p></li><li><p> 1759438 Patch - Multilingualism Language Switch - DSpace Header</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N162C6"></a>14.4.&nbsp;<a name="docbook-history.html-version1_4_1"></a>Changes in DSpace 1.4.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N162CD"></a>14.4.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Error pages now return appropriate HTTP status codes (e.g. 404 not found)</p></li><li><p> Bad filenames in /bitstream/ URLs now result in 404 error -- prevents infinite URL spaces confusing crawlers and bad "persistent" bitstream IDs circulating</p></li><li><p> Prevent infinite URL spaces in HTMLServlet</p></li><li><p> InstallItem no longer sets dc.format.extent, dc.format.mimetype; no longer sets default value for dc.language.iso if one is not present</p></li><li><p> Empty values in drop-down submit fields are not added as empty metadata values</p></li><li><p> API methods for searching epeople and groups</p></li><li><p> Support stats from both 1.3 and 1.4</p></li><li><p> [dspace]/bin/update-handle-prefix now runs index-all</p></li><li><p> Remove cases of System.out from code executed in webapp</p></li><li><p> Change "View Licence" to "View License" in Messages.properties</p></li><li><p> dspace.cfg comments changed to indicate what default.language actually means</p></li><li><p> HandleServlet and BitstreamServlet support If-Modified-Since requests</p></li><li><p> Improved sanity-checking of XSL-based ingest crosswalks</p></li><li><p> Remove thumbnail filename from alt-text</p></li><li><p> Include item title in HTML title element</p></li><li><p> Improvements to help prevent spammers and sploggers</p></li><li><p> Make cleanup() commit outstanding work every 100 iterations</p></li><li><p> Better handling where email send failed due to wrong address for new user</p></li><li><p> Include robots.txt to limit bots navigating author, date and browse by subject pages</p></li><li><p> Add css styles for print media</p></li><li><p> RSS made more configurable and provide system-wide RSS feed, also moves text to Messages.properties</p></li><li><p> Jar file updates (includes required code changes for DSIndexer and DSQuery and new jars fontbox.jar and serializer.jar)</p></li><li><p> Various documentation additions and cleanups</p></li><li><p> XHTML compliance improvements</p></li><li><p> Move w3c valid xhtml boiler image into local repository</p></li><li><p> Remove uncessary Log4j Configuration in CheckerCommand</p></li><li><p> Include Windows CLASSPATH in dsrun.bat</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16323"></a>14.4.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1604037 - UIUtil.encodeBitstream() now correctly encodes URLs (no longer incorrectly substitutes '+' for spaces in non-query segment</p></li><li><p> 1592984 - Date comparisons strip time in org.dspace.harvest.Harvest</p></li><li><p> 1589902 - Duplicate [field] checking error [on input-forms.xml]</p></li><li><p> 1596952 - Collection Wizard create Template missing schema</p></li><li><p> 1596978 - View unfinished submissions - collection empty</p></li><li><p> 1588625 - Incorrect text on item mapper screen</p></li><li><p> 1597805 - DIDL Crosswalk: wrong resource management</p></li><li><p> 1605635 - NPE in Utils.java</p></li><li><p> 1597504 - Search result page shows shortened query string</p></li><li><p> 1532389 - Item Templates do not work for non-dc fields</p></li><li><p> 1066771 - Metadata edit form dropping DC qualifier</p></li><li><p> 1548738 - Multiple Metadata Schema, schema not shown on edit item page</p></li><li><p> 1589895 - Not possible to add unqualified Metadata Field</p></li><li><p> 1543853 - Statistics do not work in 1.4</p></li><li><p> 1541381 - Browse-by-date and browse-by-title not working</p></li><li><p> 1556947 - NullPointerException when no user selected to del/edit</p></li><li><p> 1554064 - Fix exception handling for ClassCastException in BitstreamServlet</p></li><li><p> 1548865 - Browse errors on withdrawn item</p></li><li><p> 1554056 - Community/collection handle URL with / redirects to homepage</p></li><li><p> 1571490 - UTF-8 encoded characters in licence</p></li><li><p> 1571519 - UTF-8 in statistics</p></li><li><p> 1544807 - Browse-by-Subject/Author paging mechanism broken</p></li><li><p> 1543966 - "Special" groups inside groups bug</p></li><li><p> 1480496 - Cannot turn off "ignore authorization" flag!</p></li><li><p> 1515148 - Community policies not deleting correctly</p></li><li><p> 1556829 - Docs mention old SiteAuthenticator class</p></li><li><p> 1606435 - Workflow text out of context</p></li><li><p> Fix for bitstream authorization timeout</p></li><li><p> Fix to make sure cleanup() doesn't fail with NullPointerException</p></li><li><p> Fix for removeBitstream() failing to update primary bitstream</p></li><li><p> Fix for Advanced Search ignoring conjunctions for arbitrary number of queries</p></li><li><p> Fix minor bug in Harvest.java for Oracle users</p></li><li><p> Fix missing title for news editor page</p></li><li><p> Small Messages.properties modification (change of DSpace copyright text)</p></li><li><p> fix PDFBox tmp file issue</p></li><li><p> Fix HttpServletRequest encoding issues</p></li><li><p> Fix bug in TableRow toString() method where NPE is thrown if tablename not set</p></li><li><p> Update DIDL license and change coding style to DSpace standard</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1639A"></a>14.5.&nbsp;<a name="docbook-history.html-version1_4"></a>Changes in DSpace 1.4</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N163A1"></a>14.5.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Content verification through periodic checksum checking</p></li><li><p> Support for branded preview image</p></li><li><p> Add/replace Creative Commons in 'edit item' tool</p></li><li><p> Customisable item listing columns and browse indices</p></li><li><p> Script for updating handle prefixes (e.g. for moving from development to production)</p></li><li><p> Configurable boolean search operator</p></li><li><p> Controlled vocabulary patch to provide search on classification terms, and addition of terms during submission.</p></li><li><p> Add 'visibility' element to input-forms.xml</p></li><li><p> Browse by subject feature</p></li><li><p> Log4J enhancement to use XML configuration</p></li><li><p> QueryArgs class can support any number of fields in advanced search.</p></li><li><p> Community names no longer have to be unique</p></li><li><p> Enhanced Windows support</p></li><li><p> Support for multiple (flat) metadata schemas</p></li><li><p> Suggest an item page</p></li><li><p> RSS Feeds</p></li><li><p> Performance enhancements</p></li><li><p> Stackable authentication methods</p></li><li><p> Plug-in manager</p></li><li><p> Pluggable SIP/DIP support and metadata crosswalks</p></li><li><p> Nested groups of e-people</p></li><li><p> Expose METS and MPEG-21 DIDL DIPs via OAI-PMH</p></li><li><p> Configurable Lucene search analyzer (e.g. for Chinese metadata)</p></li><li><p> Support for SMTP servers requiring authentication</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N163EE"></a>14.5.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1358197 - Edit Item, empty DC fields not removable</p></li><li><p> 1363633 - Submission step 1 fails when there are no collections</p></li><li><p> 1255264 - Resource policy eperson value was set to wrong column</p></li><li><p> 1380494 - Error deleting an item with multiple metadata schema support</p></li><li><p> 1443649 - Cannot configure unqualified elements for advanced search index</p></li><li><p> 1333687 - Browse-(title|date) fails on withdrawn item</p></li><li><p> 1066713 - Two (sub)communities cannot have one name</p></li><li><p> 1284055 - Two Communities of same name throws error</p></li><li><p> 1035366 - Bitstream size column should be bigint</p></li><li><p> 1352257 - Selecting a Group for GroupToGroup while Creating Collection</p></li><li><p> 1352226 - Navigation and Sorting in Group List (Select Groups) fails</p></li><li><p> 1348276 - Null in collection name causes OAI ListSets to fail</p></li><li><p> 1160898 - dspace_migrate removes Date.Issued from prev published items</p></li><li><p> 1261191 - Malformed METS metadata exported</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1641D"></a>14.6.&nbsp;<a name="docbook-history.html-version1_3_2"></a>Changes in DSpace 1.3.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16424"></a>14.6.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> DSpace UI XHTML/WAI compliant</p></li><li><p> Configure metadata fields shown on simple item display</p></li><li><p> Supervisor/workspace help documentation</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16432"></a>14.6.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Oracle compatibility fixes</p></li><li><p> Item exporter now correctly exports metadata in UTF-8</p></li><li><p> fixed to handle 'null' values passed in</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16440"></a>14.7.&nbsp;<a name="docbook-history.html-version1_3_1"></a>Changes in DSpace 1.3.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16447"></a>14.7.1.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1252153 - Error on fresh install</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1644F"></a>14.8.&nbsp;<a name="docbook-history.html-version1_3"></a>Changes in DSpace 1.3</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16456"></a>14.8.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Initial i18n Support for JSPs - Note: the implementation of this feature required changes to almost all JSP pages</p></li><li><p> LDAP authentication support</p></li><li><p> Log file analysis and report generation</p></li><li><p> Configurable item licence viewing</p></li><li><p> Supervision order/collaborative workspace administrative tools</p></li><li><p> Basic workspace for submissions in progress, with support for supervision</p></li><li><p> SRB storage system option</p></li><li><p> Updated handle server system</p></li><li><p> Database optimisations</p></li><li><p> Latest versions of Xerces, Xalan and OAICAT jars</p></li><li><p> Various documentation additions and cleanups</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1647C"></a>14.8.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> 1161459 - ItemExporter fails with Too many open files</p></li><li><p> 1167373 - Email date field not populated</p></li><li><p> 1193948 - New item submit problem</p></li><li><p> 1188132 - NullPointerException when Adding EPerson</p></li><li><p> 1188016 - Cannot Edit an Eperson</p></li><li><p> 1219701 - Unable to open unfinished submission</p></li><li><p> 1206836 - community strengths not reflecting sub-community</p></li><li><p> 1238262 - Submit UI nav/progress buttons no longer show progress</p></li><li><p> 1238276 - Double quote problem in some fields in submit UI</p></li><li><p> 1238277 - format support level not shown in "uploaded file" page</p></li><li><p> 1242548 - Uploading non-existing files</p></li><li><p> 1244743 - Bad lookup key for special case of DC Title in ItemTag.java</p></li><li><p> 1245223 - Subscription Emailer fails</p></li><li><p> 1247508 - Error when browsing item with no content/bitstream collections</p></li><li><p> Set the content type in the HTTP header</p></li><li><p> Fix issue where EPerson edit would not work due to form indexing (partial fix)</p></li><li><p> POST handling in HTMLServlet</p></li><li><p> Missing ContentType directives added to some JSPs</p></li><li><p> Name dependency on Collection Admin and Submitter groups fixed</p></li><li><p> Fixed OAI-PMH XML encoding</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N164BD"></a>14.9.&nbsp;<a name="docbook-history.html-version1_2_2"></a>Changes in DSpace 1.2.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N164C4"></a>14.9.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Customisable submission forms added</p></li><li><p> Configurable number of index terms in Lucene for full-text indexing</p></li><li><p> Improved scalability in media filter</p></li><li><p> Submit button on collection pages only appears if user has authorisation</p></li><li><p> PostgreSQL 8.0 compatibility</p></li><li><p> Search scope retention to improve browsing</p></li><li><p> Community and collection strengths displayed</p></li><li><p> Upgraded OAICat software</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N164E1"></a>14.9.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Fix for Oracle too many cursors problem.</p></li><li><p> Fix for UTF-8 encoded searches in advanced search.</p></li><li><p> Fix for handling "\" in bitstream names.</p></li><li><p> Fix to prevent delete of "unknown" bitstream format</p></li><li><p> Fix for ItemImport creating new handles for replaced items</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N164F5"></a>14.9.3.&nbsp;<a name="docbook-history.html-jsp-changes-1_2_1-1_2_2"></a>Changes in JSPs</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
               <code class="literal">collection-home.jsp</code>
               <span class="emphasis"><em>changed</em></span>
             </p></li><li><p>
@@ -64,7 +64,7 @@
             </p></li><li><p>
               <code class="literal">submit/upload-file-list.jsp</code>
               <span class="emphasis"><em>changed</em></span>
-            </p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16525"></a>14.8.&nbsp;<a name="docbook-history.html-version1_2_1"></a>Changes in DSpace 1.2.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1652C"></a>14.8.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Oracle support added</p></li><li><p> Thumbnails in item view can now be switched off/on</p></li><li><p> Browse and search thumbnail options</p></li><li><p> Improved item importer </p><div class="itemizedlist"><ul type="circle"><li><p> can now import to multiple collections</p></li><li><p> added --test flag to simulate an import, without actually making any changes</p></li><li><p> added --resume flag to try to resume the import in case the import is aborted</p></li></ul></div></li><li><p> Configurable fields for the search index</p></li><li><p> Script for transferring items between DSpace instances</p></li><li><p> Sun library JARs (JavaMail, Java Activation Framework and Servlet) now included in DSpace source code bundle</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16550"></a>14.8.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> A logo to existing collection can now be added. Fixes SF bug #1065933</p></li><li><p> The community logo can now be edited. Fixes SF bug #1035692</p></li><li><p> MediaFilterManager doesn't 'touch' every item every time. Fixes SF bug #1015296</p></li><li><p> Supported formats help page, set the format support level to "known" as default</p></li><li><p> Fixed various database connection pool leaks</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16564"></a>14.8.3.&nbsp;<a name="docbook-history.html-jsp-changes-1_2-1_2_1"></a>Changed JSPs</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
+            </p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N165D9"></a>14.10.&nbsp;<a name="docbook-history.html-version1_2_1"></a>Changes in DSpace 1.2.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N165E0"></a>14.10.1.&nbsp;General Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Oracle support added</p></li><li><p> Thumbnails in item view can now be switched off/on</p></li><li><p> Browse and search thumbnail options</p></li><li><p> Improved item importer </p><div class="itemizedlist"><ul type="circle"><li><p> can now import to multiple collections</p></li><li><p> added --test flag to simulate an import, without actually making any changes</p></li><li><p> added --resume flag to try to resume the import in case the import is aborted</p></li></ul></div></li><li><p> Configurable fields for the search index</p></li><li><p> Script for transferring items between DSpace instances</p></li><li><p> Sun library JARs (JavaMail, Java Activation Framework and Servlet) now included in DSpace source code bundle</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16604"></a>14.10.2.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> A logo to existing collection can now be added. Fixes SF bug #1065933</p></li><li><p> The community logo can now be edited. Fixes SF bug #1035692</p></li><li><p> MediaFilterManager doesn't 'touch' every item every time. Fixes SF bug #1015296</p></li><li><p> Supported formats help page, set the format support level to "known" as default</p></li><li><p> Fixed various database connection pool leaks</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16618"></a>14.10.3.&nbsp;<a name="docbook-history.html-jsp-changes-1_2-1_2_1"></a>Changed JSPs</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p>
               <code class="literal">collection-home</code>
               <span class="emphasis"><em>changed</em></span>
             </p></li><li><p>
@@ -115,7 +115,7 @@
             </p></li><li><p>
               <code class="literal">layout/navbar-admin</code>
               <span class="emphasis"><em>changed</em></span>
-            </p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16616"></a>14.9.&nbsp;<a name="docbook-history.html-version1_2"></a>Changes in DSpace 1.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1661D"></a>14.9.1.&nbsp;General Improvments</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Communities can now contain sub-communities</p></li><li><p> Items may be included in more than one collection</p></li><li><p> Full text extraction and searching for MS Word, PDF, HTML, text documents</p></li><li><p> Thumbnails displayed in item view for items that contain images</p></li><li><p> Configurable MediaFilter tool creates both extracted text and thumbnails</p></li><li><p> Bitstream IDs are now persistent - generated from item's handle and a sequence number</p></li><li><p> Creative Commons licenses can optionally be added to items during web submission process</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16637"></a>14.9.2.&nbsp;Administration</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> If you are logged in as administrator, you see admin buttons on item, collection, and community pages</p></li><li><p> New collection administration wizard</p></li><li><p> Can now administer collection's submitters from collection admin tool</p></li><li><p> Delegated administration - new 'collection editor' role - edits item metadata, manages submitters list, edits collection metadata, links to items from other collections, and can withdraw items</p></li><li><p> Admin UI moved from /admin to /dspace-admin to avoid conflict with Tomcat /admin JSPs</p></li><li><p> New EPerson selector popup makes Group editing much easier</p></li><li><p> 'News' section is now editable using admin UI (no more mucking with JSPs)</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16651"></a>14.9.3.&nbsp;Import/Export/OAI</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> New tool that exports DSpace content in AIPs that use METS XML for metadata (incomplete)</p></li><li><p> OAI - sets are now collections, identified by Handles ('safe' with /, : converted to _)</p></li><li><p> OAI - contributor.author now mapped to oai_dc:creator</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N1665F"></a>14.9.4.&nbsp;Miscellaneous</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Build process streamlined with use of WAR files, symbolic links no longer used, friendlier to later versions of Tomcat</p></li><li><p> MIT-specific aspects of UI removed to avoid confusion</p></li><li><p> Item metadata now rendered to avoid interpreting as HTML (displays as entered)</p></li><li><p> Forms now have no-cache directive to avoid trouble with browser 'back' button</p></li><li><p> Bundles now have 'names' for more structure in item's content</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16673"></a>14.9.5.&nbsp;<a name="docbook-history.html-jsp-file-changes"></a>JSP file changes between 1.1 and 1.2</h3></div></div></div><p>This list generated with <code class="literal">cvs -Q rdiff -s -r dspace-1_1 dspace</code> and a sprinkling of perl.</p><div class="itemizedlist"><ul type="disc"><li><p> Changed: dspace/jsp/collection-home.jsp</p></li><li><p> Changed: dspace/jsp/community-home.jsp</p></li><li><p> Changed: dspace/jsp/community-list.jsp</p></li><li><p> Changed: dspace/jsp/display-item.jsp</p></li><li><p> Changed: dspace/jsp/index.jsp</p></li><li><p> Changed: dspace/jsp/home.jsp</p></li><li><p> Changed: dspace/jsp/styles.css.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-advanced.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-collection-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-community-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-item-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-main.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-policy-edit.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/collection-select.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/community-select.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-collection.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-community.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-dctype.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-eperson.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-format.jsp</p></li><li><p> Moved to dspace/jsp/tools: dspace/jsp/admin/confirm-delete-item.jsp</p></li><li><p> Moved to dspace/jsp/tools: dspace/jsp/admin/confirm-withdraw-item.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/edit-collection.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/edit-community.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/edit-item-form.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/eperson-browse.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/eperson-confirm-delete.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/eperson-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/eperson-main.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/get-item-id.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/group-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/group-eperson-select.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/group-list.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/index.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/item-select.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/list-communities.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/list-dc-types.jsp</p></li><li><p> Removed: dspace/jsp/admin/list-epeople.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/list-formats.jsp</p></li><li><p> Moved to dspace/jsp/tools: dspace/jsp/admin/upload-bitstream.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/upload-logo.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/workflow-abort-confirm.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/workflow-list.jsp</p></li><li><p> Changed: dspace/jsp/browse/authors.jsp</p></li><li><p> Changed: dspace/jsp/browse/items-by-author.jsp</p></li><li><p> Changed: dspace/jsp/browse/items-by-date.jsp</p></li><li><p> Changed: dspace/jsp/browse/no-results.jsp</p></li><li><p> New: dspace-admin/eperson-deletion-error.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/news-edit.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/news-main.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-basicinfo.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-default-item.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-permissions.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-questions.jsp</p></li><li><p> Changed: dspace/jsp/components/contact-info.jsp</p></li><li><p> Changed: dspace/jsp/error/internal.jsp</p></li><li><p> New: dspace/jsp/help/formats.jsp</p></li><li><p> Changed: dspace/jsp/layout/footer-default.jsp</p></li><li><p> Changed: dspace/jsp/layout/header-default.jsp</p></li><li><p> Changed: dspace/jsp/layout/navbar-admin.jsp</p></li><li><p> Changed: dspace/jsp/layout/navbar-default.jsp</p></li><li><p> Changed: dspace/jsp/login/password.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/main.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/perform-task.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/preview-task.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/reject-reason.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/remove-item.jsp</p></li><li><p> Changed: dspace/jsp/register/edit-profile.jsp</p></li><li><p> Changed: dspace/jsp/register/inactive-account.jsp</p></li><li><p> Changed: dspace/jsp/register/new-password.jsp</p></li><li><p> Changed: dspace/jsp/register/registration-form.jsp</p></li><li><p> Changed: dspace/jsp/search/advanced.jsp</p></li><li><p> Changed: dspace/jsp/search/results.jsp</p></li><li><p> Changed: dspace/jsp/submit/cancel.jsp</p></li><li><p> New: dspace/jsp/submit/cc-license.jsp</p></li><li><p> Changed: dspace/jsp/submit/choose-file.jsp</p></li><li><p> New: dspace/jsp/submit/creative-commons.css</p></li><li><p> New: dspace/jsp/submit/creative-commons.jsp</p></li><li><p> Changed: dspace/jsp/submit/edit-metadata-1.jsp</p></li><li><p> Changed: dspace/jsp/submit/edit-metadata-2.jsp</p></li><li><p> Changed: dspace/jsp/submit/get-file-format.jsp</p></li><li><p> Changed: dspace/jsp/submit/initial-questions.jsp</p></li><li><p> Changed: dspace/jsp/submit/progressbar.jsp</p></li><li><p> Changed: dspace/jsp/submit/review.jsp</p></li><li><p> Changed: dspace/jsp/submit/select-collection.jsp</p></li><li><p> Changed: dspace/jsp/submit/show-license.jsp</p></li><li><p> Changed: dspace/jsp/submit/show-uploaded-file.jsp</p></li><li><p> Changed: dspace/jsp/submit/upload-error.jsp</p></li><li><p> Changed: dspace/jsp/submit/upload-file-list.jsp</p></li><li><p> Changed: dspace/jsp/submit/verify-prune.jsp</p></li><li><p> New: dspace/jsp/tools/edit-item-form.jsp</p></li><li><p> New: dspace/jsp/tools/eperson-list.jsp</p></li><li><p> New: dspace/jsp/tools/itemmap-browse.jsp</p></li><li><p> New: dspace/jsp/tools/itemmap-info.jsp</p></li><li><p> New: dspace/jsp/tools/itemmap-main.jsp</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1679E"></a>14.10.&nbsp;<a name="docbook-history.html-version1_1_1"></a>Changes in DSpace 1.1.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N167A5"></a>14.10.1.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> non-administrators can now submit again</p></li><li><p> installations now preserve file creation dates, eliminating confusion with upgrades</p></li><li><p> authorization editing pages no longer create null entries in database, and no longer handles them poorly (no longer gives blank page instead of displaying policies.)</p></li><li><p> registration page Invalid token error page now displayed when an invalid token is received (as opposed to internal server error.) Fixes SF bug #739999</p></li><li><p> eperson admin 'recent submission' links fixed for DSpaces deployed somewhere other than at / (e.g. /dspace).</p></li><li><p> help pages Link to help pages now includes servlet context (e.g. '/dspace'). Fixes SF bug #738399.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N167BC"></a>14.10.2.&nbsp;Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">bin/dspace-info.pl</code>  now checks jsp and asset store files for zero-length files</p></li><li><p><code class="literal">make-release-package</code>  now works with SourceForge CVS</p></li><li><p> eperson editor now doesn't display the spurious text 'null'</p></li><li><p> item exporter now uses Jakarta's cli command line arg parser (much cleaner)</p></li><li><p> item importer improvements: </p><div class="itemizedlist"><ul type="circle"><li><p> now uses Jakarta's cli command line arg parser (much cleaner)</p></li><li><p> imported items can now be routed through a workflow</p></li><li><p> more validation and error messages before import</p></li><li><p> can now use email addresses and handles instead of just database IDs</p></li><li><p> can import an item to a collection with the workflow suppressed</p></li></ul></div></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N167E6"></a>14.11.&nbsp;<a name="docbook-history.html-version1_1"></a>Changes in DSpace 1.1</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Fixed various OAI-related bugs; DSpace's OAI support should now be correct. Note that harvesting is now based on the new Item 'last modified' date (as opposed to the Dublin Core <code class="literal">date.available</code> date.)</p></li><li><p> Fixed Handle support--DSpace now responds to naming authority requests correctly.</p></li><li><p> Multiple bitstream stores can now be specified; this allows DSpace storage to span several disks, and so there is no longer a hard limit on storage.</p></li><li><p> Search improvements: </p><div class="itemizedlist"><ul type="circle"><li><p> New fielded searching UI</p></li><li><p> Search results are now paged</p></li><li><p> Abstracts are indexed</p></li><li><p> Better use of Lucene API; should stop the number of open file handles getting large</p></li></ul></div></li><li><p> Submission UI improvements: </p><div class="itemizedlist"><ul type="circle"><li><p> now insists on a title being specified</p></li><li><p> fixed navigation on file upload page</p></li><li><p> citation &amp; identifier fields for previously published submissions now fixed</p></li></ul></div></li><li><p> Many Unicode fixes to the database and Web user interface</p></li><li><p> Collections can now be deleted</p></li><li><p> Bitstream descriptions (if available) displayed on item display page</p></li><li><p> Modified a couple of servlets to handle invalid parameters better (i.e. to report a suitable error message instead of an internal server error)</p></li><li><p> Item templates now work</p></li><li><p> Fixed registration token expiration problem (they no longer expire.)</p></li></ul></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+            </p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N166CA"></a>14.11.&nbsp;<a name="docbook-history.html-version1_2"></a>Changes in DSpace 1.2</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N166D1"></a>14.11.1.&nbsp;General Improvments</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Communities can now contain sub-communities</p></li><li><p> Items may be included in more than one collection</p></li><li><p> Full text extraction and searching for MS Word, PDF, HTML, text documents</p></li><li><p> Thumbnails displayed in item view for items that contain images</p></li><li><p> Configurable MediaFilter tool creates both extracted text and thumbnails</p></li><li><p> Bitstream IDs are now persistent - generated from item's handle and a sequence number</p></li><li><p> Creative Commons licenses can optionally be added to items during web submission process</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N166EB"></a>14.11.2.&nbsp;Administration</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> If you are logged in as administrator, you see admin buttons on item, collection, and community pages</p></li><li><p> New collection administration wizard</p></li><li><p> Can now administer collection's submitters from collection admin tool</p></li><li><p> Delegated administration - new 'collection editor' role - edits item metadata, manages submitters list, edits collection metadata, links to items from other collections, and can withdraw items</p></li><li><p> Admin UI moved from /admin to /dspace-admin to avoid conflict with Tomcat /admin JSPs</p></li><li><p> New EPerson selector popup makes Group editing much easier</p></li><li><p> 'News' section is now editable using admin UI (no more mucking with JSPs)</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16705"></a>14.11.3.&nbsp;Import/Export/OAI</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> New tool that exports DSpace content in AIPs that use METS XML for metadata (incomplete)</p></li><li><p> OAI - sets are now collections, identified by Handles ('safe' with /, : converted to _)</p></li><li><p> OAI - contributor.author now mapped to oai_dc:creator</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16713"></a>14.11.4.&nbsp;Miscellaneous</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Build process streamlined with use of WAR files, symbolic links no longer used, friendlier to later versions of Tomcat</p></li><li><p> MIT-specific aspects of UI removed to avoid confusion</p></li><li><p> Item metadata now rendered to avoid interpreting as HTML (displays as entered)</p></li><li><p> Forms now have no-cache directive to avoid trouble with browser 'back' button</p></li><li><p> Bundles now have 'names' for more structure in item's content</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16727"></a>14.11.5.&nbsp;<a name="docbook-history.html-jsp-file-changes"></a>JSP file changes between 1.1 and 1.2</h3></div></div></div><p>This list generated with <code class="literal">cvs -Q rdiff -s -r dspace-1_1 dspace</code> and a sprinkling of perl.</p><div class="itemizedlist"><ul type="disc"><li><p> Changed: dspace/jsp/collection-home.jsp</p></li><li><p> Changed: dspace/jsp/community-home.jsp</p></li><li><p> Changed: dspace/jsp/community-list.jsp</p></li><li><p> Changed: dspace/jsp/display-item.jsp</p></li><li><p> Changed: dspace/jsp/index.jsp</p></li><li><p> Changed: dspace/jsp/home.jsp</p></li><li><p> Changed: dspace/jsp/styles.css.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-advanced.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-collection-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-community-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-item-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-main.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/authorize-policy-edit.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/collection-select.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/community-select.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-collection.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-community.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-dctype.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-eperson.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/confirm-delete-format.jsp</p></li><li><p> Moved to dspace/jsp/tools: dspace/jsp/admin/confirm-delete-item.jsp</p></li><li><p> Moved to dspace/jsp/tools: dspace/jsp/admin/confirm-withdraw-item.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/edit-collection.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/edit-community.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/edit-item-form.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/eperson-browse.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/eperson-confirm-delete.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/eperson-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/eperson-main.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/get-item-id.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/group-edit.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/group-eperson-select.jsp</p></li><li><p> Moved to dspace/jsp/tools and changed: dspace/jsp/admin/group-list.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/index.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/item-select.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/list-communities.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/list-dc-types.jsp</p></li><li><p> Removed: dspace/jsp/admin/list-epeople.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/list-formats.jsp</p></li><li><p> Moved to dspace/jsp/tools: dspace/jsp/admin/upload-bitstream.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/upload-logo.jsp</p></li><li><p> Moved to dspace-admin: dspace/jsp/admin/workflow-abort-confirm.jsp</p></li><li><p> Moved to dspace-admin and changed: dspace/jsp/admin/workflow-list.jsp</p></li><li><p> Changed: dspace/jsp/browse/authors.jsp</p></li><li><p> Changed: dspace/jsp/browse/items-by-author.jsp</p></li><li><p> Changed: dspace/jsp/browse/items-by-date.jsp</p></li><li><p> Changed: dspace/jsp/browse/no-results.jsp</p></li><li><p> New: dspace-admin/eperson-deletion-error.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/news-edit.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/news-main.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-basicinfo.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-default-item.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-permissions.jsp</p></li><li><p> New: dspace/jsp/dspace-admin/wizard-questions.jsp</p></li><li><p> Changed: dspace/jsp/components/contact-info.jsp</p></li><li><p> Changed: dspace/jsp/error/internal.jsp</p></li><li><p> New: dspace/jsp/help/formats.jsp</p></li><li><p> Changed: dspace/jsp/layout/footer-default.jsp</p></li><li><p> Changed: dspace/jsp/layout/header-default.jsp</p></li><li><p> Changed: dspace/jsp/layout/navbar-admin.jsp</p></li><li><p> Changed: dspace/jsp/layout/navbar-default.jsp</p></li><li><p> Changed: dspace/jsp/login/password.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/main.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/perform-task.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/preview-task.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/reject-reason.jsp</p></li><li><p> Changed: dspace/jsp/mydspace/remove-item.jsp</p></li><li><p> Changed: dspace/jsp/register/edit-profile.jsp</p></li><li><p> Changed: dspace/jsp/register/inactive-account.jsp</p></li><li><p> Changed: dspace/jsp/register/new-password.jsp</p></li><li><p> Changed: dspace/jsp/register/registration-form.jsp</p></li><li><p> Changed: dspace/jsp/search/advanced.jsp</p></li><li><p> Changed: dspace/jsp/search/results.jsp</p></li><li><p> Changed: dspace/jsp/submit/cancel.jsp</p></li><li><p> New: dspace/jsp/submit/cc-license.jsp</p></li><li><p> Changed: dspace/jsp/submit/choose-file.jsp</p></li><li><p> New: dspace/jsp/submit/creative-commons.css</p></li><li><p> New: dspace/jsp/submit/creative-commons.jsp</p></li><li><p> Changed: dspace/jsp/submit/edit-metadata-1.jsp</p></li><li><p> Changed: dspace/jsp/submit/edit-metadata-2.jsp</p></li><li><p> Changed: dspace/jsp/submit/get-file-format.jsp</p></li><li><p> Changed: dspace/jsp/submit/initial-questions.jsp</p></li><li><p> Changed: dspace/jsp/submit/progressbar.jsp</p></li><li><p> Changed: dspace/jsp/submit/review.jsp</p></li><li><p> Changed: dspace/jsp/submit/select-collection.jsp</p></li><li><p> Changed: dspace/jsp/submit/show-license.jsp</p></li><li><p> Changed: dspace/jsp/submit/show-uploaded-file.jsp</p></li><li><p> Changed: dspace/jsp/submit/upload-error.jsp</p></li><li><p> Changed: dspace/jsp/submit/upload-file-list.jsp</p></li><li><p> Changed: dspace/jsp/submit/verify-prune.jsp</p></li><li><p> New: dspace/jsp/tools/edit-item-form.jsp</p></li><li><p> New: dspace/jsp/tools/eperson-list.jsp</p></li><li><p> New: dspace/jsp/tools/itemmap-browse.jsp</p></li><li><p> New: dspace/jsp/tools/itemmap-info.jsp</p></li><li><p> New: dspace/jsp/tools/itemmap-main.jsp</p></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16852"></a>14.12.&nbsp;<a name="docbook-history.html-version1_1_1"></a>Changes in DSpace 1.1.1</h2></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16859"></a>14.12.1.&nbsp;Bug fixes</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> non-administrators can now submit again</p></li><li><p> installations now preserve file creation dates, eliminating confusion with upgrades</p></li><li><p> authorization editing pages no longer create null entries in database, and no longer handles them poorly (no longer gives blank page instead of displaying policies.)</p></li><li><p> registration page Invalid token error page now displayed when an invalid token is received (as opposed to internal server error.) Fixes SF bug #739999</p></li><li><p> eperson admin 'recent submission' links fixed for DSpaces deployed somewhere other than at / (e.g. /dspace).</p></li><li><p> help pages Link to help pages now includes servlet context (e.g. '/dspace'). Fixes SF bug #738399.</p></li></ul></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="N16870"></a>14.12.2.&nbsp;Improvements</h3></div></div></div><div class="itemizedlist"><ul type="disc"><li><p><code class="literal">bin/dspace-info.pl</code>  now checks jsp and asset store files for zero-length files</p></li><li><p><code class="literal">make-release-package</code>  now works with SourceForge CVS</p></li><li><p> eperson editor now doesn't display the spurious text 'null'</p></li><li><p> item exporter now uses Jakarta's cli command line arg parser (much cleaner)</p></li><li><p> item importer improvements: </p><div class="itemizedlist"><ul type="circle"><li><p> now uses Jakarta's cli command line arg parser (much cleaner)</p></li><li><p> imported items can now be routed through a workflow</p></li><li><p> more validation and error messages before import</p></li><li><p> can now use email addresses and handles instead of just database IDs</p></li><li><p> can import an item to a collection with the workflow suppressed</p></li></ul></div></li></ul></div></div></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1689A"></a>14.13.&nbsp;<a name="docbook-history.html-version1_1"></a>Changes in DSpace 1.1</h2></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> Fixed various OAI-related bugs; DSpace's OAI support should now be correct. Note that harvesting is now based on the new Item 'last modified' date (as opposed to the Dublin Core <code class="literal">date.available</code> date.)</p></li><li><p> Fixed Handle support--DSpace now responds to naming authority requests correctly.</p></li><li><p> Multiple bitstream stores can now be specified; this allows DSpace storage to span several disks, and so there is no longer a hard limit on storage.</p></li><li><p> Search improvements: </p><div class="itemizedlist"><ul type="circle"><li><p> New fielded searching UI</p></li><li><p> Search results are now paged</p></li><li><p> Abstracts are indexed</p></li><li><p> Better use of Lucene API; should stop the number of open file handles getting large</p></li></ul></div></li><li><p> Submission UI improvements: </p><div class="itemizedlist"><ul type="circle"><li><p> now insists on a title being specified</p></li><li><p> fixed navigation on file upload page</p></li><li><p> citation &amp; identifier fields for previously published submissions now fixed</p></li></ul></div></li><li><p> Many Unicode fixes to the database and Web user interface</p></li><li><p> Collections can now be deleted</p></li><li><p> Bitstream descriptions (if available) displayed on item display page</p></li><li><p> Modified a couple of servlets to handle invalid parameters better (i.e. to report a suitable error message instead of an internal server error)</p></li><li><p> Item templates now work</p></li><li><p> Fixed registration token expiration problem (they no longer expire.)</p></li></ul></div></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ch15.html b/dspace/docs/html/ch15.html
index bf108bac1f..8377dd52bc 100644
--- a/dspace/docs/html/ch15.html
+++ b/dspace/docs/html/ch15.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch14.html" title="Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History"><link rel="next" href="ix01.html" title="Index"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch14.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ix01.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N1682A"></a>Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch15.html#N1682E">15.1. Default Dublin Core Metadata Registry</a></span></dt><dt><span class="section"><a href="ch15.html#N16D87">15.2. Default Bitstream Format Registry</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1682E"></a>15.1.&nbsp;<a name="docbook-appendix.html-dublincoreregistry"></a>Default Dublin Core Metadata Registry</h2></div></div></div><div class="informaltable"><table border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch14.html" title="Chapter&nbsp;14.&nbsp;DSpace System Documentation: Version History"><link rel="next" href="ix01.html" title="Index"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch14.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ix01.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N168DE"></a>Chapter&nbsp;15.&nbsp;<a name="docbook-appendix.html"></a>DSpace System Documentation: Appendices</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch15.html#N168E4">15.1. Default Dublin Core Metadata Registry</a></span></dt><dt><span class="section"><a href="ch15.html#N16E3D">15.2. Default Bitstream Format Registry</a></span></dt></dl></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N168E4"></a>15.1.&nbsp;<a name="docbook-appendix.html-dublincoreregistry"></a>Default Dublin Core Metadata Registry</h2></div></div></div><div class="informaltable"><table border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Element</strong></span>
                 </p>
@@ -506,7 +506,7 @@
                 <p></p>
               </td></tr></tbody></table></div><p>
         <a name="docbook-appendix.html-note1"></a>
-      </p><p>&sup1;Used by system: do not remove</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16D87"></a>15.2.&nbsp;<a name="docbook-appendix.html-bitstreamformatregistry"></a>Default Bitstream Format Registry</h2></div></div></div><div class="informaltable"><table border="1"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><td>
+      </p><p>&sup1;Used by system: do not remove</p></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16E3D"></a>15.2.&nbsp;<a name="docbook-appendix.html-bitstreamformatregistry"></a>Default Bitstream Format Registry</h2></div></div></div><div class="informaltable"><table border="1"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><td>
                 <p>
                   <span class="bold"><strong>Mimetype</strong></span>
                 </p>
@@ -964,7 +964,7 @@
                 <p>mov, qt</p>
               </td></tr></tbody></table></div><p>
         <a name="docbook-appendix.html-note2"></a>
-      </p><p>&sup1; Used by system: do not remove</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+      </p><p>&sup1; Used by system: do not remove</p></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/index.html b/dspace/docs/html/index.html
index 9633cb1188..7f252644c2 100644
--- a/dspace/docs/html/index.html
+++ b/dspace/docs/html/index.html
@@ -1,11 +1,13 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>DSpace 1.5.1 Manual</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><meta name="description" content=""><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="next" href="pr01.html" title="Preface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">DSpace 1.5.1 Manual</th></tr><tr><td align="left" width="20%">&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="pr01.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="N10001"></a>DSpace 1.5.1 Manual</h1></div><div><div class="author"><h3 class="author"><span class="surname">The DSpace Foundation</span></h3><div class="affiliation"><div class="address"><p><span style="white-space: pre;"><code class="email">&lt;<a class="email" href="mailto:webmaster@dspace.org">webmaster@dspace.org</a>&gt;</code></span></p></div></div></div></div><div><p class="copyright">Copyright &copy; 2002-2008 
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>DSpace 1.5.2 Manual</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><meta name="description" content=""><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="next" href="pr01.html" title="Preface"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">DSpace 1.5.2 Manual</th></tr><tr><td align="left" width="20%">&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="pr01.html">Next</a></td></tr></table><hr></div><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="N10001"></a>DSpace 1.5.2 Manual</h1></div><div><div class="author"><h3 class="author"><span class="surname">The DSpace Foundation</span></h3><div class="affiliation"><div class="address"><p><span style="white-space: pre;"><code class="email">&lt;<a class="email" href="mailto:webmaster@dspace.org">webmaster@dspace.org</a>&gt;</code></span></p></div></div></div></div><div><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p></div><div><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
         <span class="inlinemediaobject"><img src="http://i.creativecommons.org/l/by/3.0/us/88x31.png"></span>
         Licensed under a Creative Commons Attribution 3.0 United States License
         </a>
-      </p></div></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p></p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">Preface</a></span></dt><dt><span class="chapter"><a href="ch01.html">1. DSpace System Documentation: Introduction</a></span></dt><dt><span class="chapter"><a href="ch02.html">2. DSpace System Documentation: Functional Overview</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N1009D">2.1. Data Model</a></span></dt><dt><span class="section"><a href="ch02.html#N1019F">2.2. Plugin Manager</a></span></dt><dt><span class="section"><a href="ch02.html#N101B0">2.3. Metadata</a></span></dt><dt><span class="section"><a href="ch02.html#N101F1">2.4. Packager Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N10216">2.5. Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N1023B">2.6. E-People and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N10248">2.6.1. E-Person</a></span></dt><dt><span class="section"><a href="ch02.html#N10264">2.6.2. Groups</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10275">2.7. Authentication</a></span></dt><dt><span class="section"><a href="ch02.html#N1028D">2.8. Authorization</a></span></dt><dt><span class="section"><a href="ch02.html#N1036A">2.9. Ingest Process and Workflow</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N103A5">2.9.1. Workflow Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10404">2.10. Supervision and Collaboration</a></span></dt><dt><span class="section"><a href="ch02.html#N1041B">2.11. Handles</a></span></dt><dt><span class="section"><a href="ch02.html#N10440">2.12. Bitstream 'Persistent' Identifiers</a></span></dt><dt><span class="section"><a href="ch02.html#N10460">2.13. Storage Resource Broker (SRB) Support</a></span></dt><dt><span class="section"><a href="ch02.html#N1046F">2.14. Search and Browse</a></span></dt><dt><span class="section"><a href="ch02.html#N1048A">2.15. HTML Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104D4">2.16. OAI Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104F7">2.17. OpenURL Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10508">2.18. Creative Commons Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10515">2.19. Subscriptions</a></span></dt><dt><span class="section"><a href="ch02.html#N10522">2.20. History</a></span></dt><dt><span class="section"><a href="ch02.html#N10531">2.21. Import and Export</a></span></dt><dt><span class="section"><a href="ch02.html#N1053C">2.22. Registration</a></span></dt><dt><span class="section"><a href="ch02.html#N1054D">2.23. Statistics</a></span></dt><dt><span class="section"><a href="ch02.html#N1057A">2.24. Checksum Checker</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch03.html">3. DSpace System Documentation: Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10587">3.1. Prerequisite Software</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10592">3.1.1. UNIX-like OS or Microsoft Windows</a></span></dt><dt><span class="section"><a href="ch03.html#N105A1">3.1.2. Java JDK 5 or later (standard SDK is fine, you don't need J2EE)</a></span></dt><dt><span class="section"><a href="ch03.html#N105AC">3.1.3. Apache Maven 2.0.8 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105BB">3.1.4. Apache Ant 1.6.2 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105CA">3.1.5. Relational Database: (PostgreSQL or Oracle).</a></span></dt><dt><span class="section"><a href="ch03.html#N10634">3.1.6. Servlet Engine: (Jakarta Tomcat 4.x, Jetty, Caucho Resin or equivalent).</a></span></dt><dt><span class="section"><a href="ch03.html#N1067F">3.1.7. Perl (required for [dspace]/bin/dspace-info.pl)</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10685">3.2. Installation Options</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N1068C">3.2.1. Overview of Install Options</a></span></dt><dt><span class="section"><a href="ch03.html#N10729">3.2.2. Overview of DSpace Directories</a></span></dt><dt><span class="section"><a href="ch03.html#N10787">3.2.3. Installation</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N1090F">3.3. Advanced Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10918">3.3.1. 'cron' Jobs</a></span></dt><dt><span class="section"><a href="ch03.html#N10958">3.3.2. Multilingual Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10973">3.3.3. DSpace over HTTPS</a></span></dt><dt><span class="section"><a href="ch03.html#N10AA9">3.3.4. The Handle Server</a></span></dt><dt><span class="section"><a href="ch03.html#N10B44">3.3.5. Google and HTML sitemaps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10B96">3.4. Windows Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10B9D">3.4.1. Pre-requisite Software</a></span></dt><dt><span class="section"><a href="ch03.html#N10BDF">3.4.2. Installation Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10C96">3.5. Checking Your Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10C9F">3.6. Known Bugs</a></span></dt><dt><span class="section"><a href="ch03.html#N10CB4">3.7. Common Problems</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch04.html">4. DSpace System Documentation: Updating a DSpace Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch04.html#N10D39">4.1. Updating From 1.4.2 to 1.5</a></span></dt><dt><span class="section"><a href="ch04.html#N10EB8">4.2. Updating From 1.4.1 to 1.4.2</a></span></dt><dt><span class="section"><a href="ch04.html#N10EC5">4.3. Updating From 1.4 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N10F6E">4.4. Updating From 1.3.2 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N1107C">4.5. Updating From 1.3.1 to 1.3.2</a></span></dt><dt><span class="section"><a href="ch04.html#N110F0">4.6. Updating From 1.2.x to 1.3.x</a></span></dt><dt><span class="section"><a href="ch04.html#N111AF">4.7. Updating From 1.2.1 to 1.2.2</a></span></dt><dt><span class="section"><a href="ch04.html#N1123C">4.8. Updating From 1.2 to 1.2.1</a></span></dt><dt><span class="section"><a href="ch04.html#N112BE">4.9. Updating From 1.1 (or 1.1.1) to 1.2</a></span></dt><dt><span class="section"><a href="ch04.html#N11436">4.10. Updating From 1.1 to 1.1.1</a></span></dt><dt><span class="section"><a href="ch04.html#N11470">4.11. Updating From 1.0.1 to 1.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch05.html">5. DSpace System Documentation: Configuration and Customization</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11542">5.1. General Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N1154B">5.1.1. The dspace.cfg Configuration Properties File</a></span></dt><dt><span class="section"><a href="ch05.html#N11898">5.1.2. Configuring Lucene Search Indexes</a></span></dt><dt><span class="section"><a href="ch05.html#N118E4">5.1.3. Browse Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N119FC">5.1.4. Configuring Media Filters</a></span></dt><dt><span class="section"><a href="ch05.html#N11A42">5.1.5. Wording of E-mail Messages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11A6B">5.2. The Metadata and Bitstream Format Registries</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11A89">5.2.1. Metadata Schema Registry</a></span></dt><dt><span class="section"><a href="ch05.html#N11A97">5.2.2. Metadata Format Registries</a></span></dt><dt><span class="section"><a href="ch05.html#N11AB7">5.2.3. Bitstream Format Registry</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11AD2">5.3. The Default Submission License</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11AE7">5.3.1. Possible Points in a License</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11B1F">5.4. Submission Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N11B2C">5.5. XMLUI Interface Customizations (Manakin)</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11B35">5.5.1. XMLUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11CD8">5.5.2. Configuring Themes and Aspects</a></span></dt><dt><span class="section"><a href="ch05.html#N11D82">5.5.3. Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N11DC7">5.5.4. Creating a New Theme</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11E16">5.6. JSPUI Interface Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11E1F">5.6.1. JSPUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11F12">5.6.2. Configuring Controlled Vocabularies</a></span></dt><dt><span class="section"><a href="ch05.html#N11F7D">5.6.3. Configuring Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N1207F">5.6.4. Customizing the JSP pages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N12150">5.7. Advanced DSpace Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N12159">5.7.1. Checksum Checker</a></span></dt><dt><span class="section"><a href="ch05.html#N1224D">5.7.2. Custom Authentication</a></span></dt><dt><span class="section"><a href="ch05.html#N123C1">5.7.3. Configuring System Statistical Reports</a></span></dt><dt><span class="section"><a href="ch05.html#N12418">5.7.4. Activating Additional OAI-PMH Crosswalks</a></span></dt><dt><span class="section"><a href="ch05.html#N124B1">5.7.5. Configuring Packager Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N124D0">5.7.6. Configuring Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N12660">5.7.7. Creating a new Media/Format Filter</a></span></dt><dt><span class="section"><a href="ch05.html#N12764">5.7.8. Configuration Files for Other Applications</a></span></dt><dt><span class="section"><a href="ch05.html#N127C6">5.7.9. Browse Index Creation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch06.html">6. DSpace System Documentation: Storage Layer</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N12849">6.1. RDBMS</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N128D4">6.1.1. Maintenance and Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N1290D">6.1.2. Configuring the RDBMS Component</a></span></dt></dl></dd><dt><span class="section"><a href="ch06.html#N12962">6.2. Bitstream Store</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N12A59">6.2.1. Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N12A6D">6.2.2. Configuring the Bitstream Store</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch07.html">7. DSpace System Documentation: Directories and Files</a></span></dt><dd><dl><dt><span class="section"><a href="ch07.html#N12AD4">7.1. Overview</a></span></dt><dt><span class="section"><a href="ch07.html#N12AFC">7.2. Source Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12C11">7.3. Installed Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12C66">7.4. Contents of JSPUI Web Application</a></span></dt><dt><span class="section"><a href="ch07.html#N12CA2">7.5. Contents of XMLUI Web Application (aka Manakin)</a></span></dt><dt><span class="section"><a href="ch07.html#N12D16">7.6. Log Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch08.html">8. DSpace System Documentation: Architecture</a></span></dt><dd><dl><dt><span class="section"><a href="ch08.html#N12DF6">8.1. Overview</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch09.html">9. DSpace System Documentation: Application Layer</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N12F43">9.1. Web User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N12F4E">9.1.1. Web UI Files</a></span></dt><dt><span class="section"><a href="ch09.html#N1301C">9.1.2. The Build Process</a></span></dt><dt><span class="section"><a href="ch09.html#N130A0">9.1.3. Servlets and JSPs</a></span></dt><dt><span class="section"><a href="ch09.html#N13153">9.1.4. Custom JSP Tags</a></span></dt><dt><span class="section"><a href="ch09.html#N131F8">9.1.5. Internationalisation</a></span></dt><dt><span class="section"><a href="ch09.html#N132D5">9.1.6. HTML Content in Items</a></span></dt><dt><span class="section"><a href="ch09.html#N1334F">9.1.7. Thesis Blocking</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13365">9.2. OAI-PMH Data Provider</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13424">9.2.1. Sets</a></span></dt><dt><span class="section"><a href="ch09.html#N13433">9.2.2. Unique Identifier</a></span></dt><dt><span class="section"><a href="ch09.html#N1345F">9.2.3. Access control</a></span></dt><dt><span class="section"><a href="ch09.html#N13469">9.2.4. Modification Date (OAI Date Stamp)</a></span></dt><dt><span class="section"><a href="ch09.html#N1346F">9.2.5. 'About' Information</a></span></dt><dt><span class="section"><a href="ch09.html#N13475">9.2.6. Deletions</a></span></dt><dt><span class="section"><a href="ch09.html#N13484">9.2.7. Flow Control (Resumption Tokens)</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N134C8">9.3. Community and Collection Structure Importer</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N134E7">9.3.1. Limitation</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N134F0">9.4. Package Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13509">9.4.1. Ingesting</a></span></dt><dt><span class="section"><a href="ch09.html#N1353D">9.4.2. Disseminating</a></span></dt><dt><span class="section"><a href="ch09.html#N1356A">9.4.3. METS packages</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1358A">9.5. Item Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13593">9.5.1. DSpace simple archive format</a></span></dt><dt><span class="section"><a href="ch09.html#N135D0">9.5.2. Importing Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13608">9.5.3. Exporting Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13622">9.6. Transferring Items Between DSpace Instances</a></span></dt><dt><span class="section"><a href="ch09.html#N13661">9.7. Registering (Not Importing) Bitstreams</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13672">9.7.1. Accessible Storage</a></span></dt><dt><span class="section"><a href="ch09.html#N13690">9.7.2. Registering Items Using the Item Importer</a></span></dt><dt><span class="section"><a href="ch09.html#N13722">9.7.3. Internal Identification and Retrieval of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N1374E">9.7.4. Exporting Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13758">9.7.5. METS Export of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13762">9.7.6. Deleting Registered Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1377A">9.8. METS Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13783">9.8.1. The Export Tool</a></span></dt><dt><span class="section"><a href="ch09.html#N137B4">9.8.2. The AIP Format</a></span></dt><dt><span class="section"><a href="ch09.html#N13857">9.8.3. Limitations</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1386F">9.9. MediaFilters: Transforming DSpace Content</a></span></dt><dt><span class="section"><a href="ch09.html#N1393B">9.10. Sub-Community Management</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch10.html">10. DSpace System Documentation: Business Logic Layer</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13968">10.1. Core Classes</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13975">10.1.1. The Configuration Manager (ConfigurationManager)</a></span></dt><dt><span class="section"><a href="ch10.html#N139BE">10.1.2. Constants</a></span></dt><dt><span class="section"><a href="ch10.html#N139DC">10.1.3. Context</a></span></dt><dt><span class="section"><a href="ch10.html#N13A2A">10.1.4. Email</a></span></dt><dt><span class="section"><a href="ch10.html#N13A42">10.1.5. LogManager</a></span></dt><dt><span class="section"><a href="ch10.html#N13B26">10.1.6. Utils</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13B2F">10.2. Content Management API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13BD9">10.2.1. Other Classes</a></span></dt><dt><span class="section"><a href="ch10.html#N13BFD">10.2.2. Modifications</a></span></dt><dt><span class="section"><a href="ch10.html#N13C82">10.2.3. What's In Memory?</a></span></dt><dt><span class="section"><a href="ch10.html#N13CD2">10.2.4. Dublin Core Metadata</a></span></dt><dt><span class="section"><a href="ch10.html#N13DB3">10.2.5. Support for Other Metadata Schemas</a></span></dt><dt><span class="section"><a href="ch10.html#N13DD2">10.2.6. Packager Plugins</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13E0E">10.3. Plugin Manager</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13E17">10.3.1. Concepts</a></span></dt><dt><span class="section"><a href="ch10.html#N13E46">10.3.2. Using the Plugin Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N13EC6">10.3.3. Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N13F6D">10.3.4. Configuring Plugins</a></span></dt><dt><span class="section"><a href="ch10.html#N1402D">10.3.5. Validating the Configuration</a></span></dt><dt><span class="section"><a href="ch10.html#N1407D">10.3.6. Use Cases</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N140D0">10.4. Workflow System</a></span></dt><dt><span class="section"><a href="ch10.html#N14148">10.5. Administration Toolkit</a></span></dt><dt><span class="section"><a href="ch10.html#N14183">10.6. E-person/Group Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N141CA">10.7. Authorization</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N14253">10.7.1. Special Groups</a></span></dt><dt><span class="section"><a href="ch10.html#N14259">10.7.2. Miscellaneous Authorization Notes</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N1425F">10.8. Handle Manager/Handle Plugin</a></span></dt><dt><span class="section"><a href="ch10.html#N142D7">10.9. Search</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N14336">10.9.1. Our Lucene Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N14348">10.9.2. Indexed Fields</a></span></dt><dt><span class="section"><a href="ch10.html#N143FD">10.9.3. Harvesting API</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N1442C">10.10. Browse API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N144A9">10.10.1. Using the API</a></span></dt><dt><span class="section"><a href="ch10.html#N14508">10.10.2. Index Maintenance</a></span></dt><dt><span class="section"><a href="ch10.html#N14518">10.10.3. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N14533">10.11. History Recorder</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N1455A">10.11.1. Archival Events</a></span></dt><dt><span class="section"><a href="ch10.html#N14590">10.11.2. Serializations</a></span></dt><dt><span class="section"><a href="ch10.html#N1459D">10.11.3. Unique Ids</a></span></dt><dt><span class="section"><a href="ch10.html#N145AD">10.11.4. Storage</a></span></dt><dt><span class="section"><a href="ch10.html#N145C8">10.11.5. Example</a></span></dt><dt><span class="section"><a href="ch10.html#N145E1">10.11.6. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N145EB">10.12. Checksum checker</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch11.html">11. Customizing and Configuring Submission User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14607">11.1. Understanding the Submission Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14614">11.1.1. The Structure of item-submission.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N14643">11.1.2. Defining Steps (&lt;step&gt;) within the item-submission.xml</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N14777">11.2. Reordering/Removing Submission Steps</a></span></dt><dt><span class="section"><a href="ch11.html#N14824">11.3. Assigning a custom Submission Process to a Collection</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14877">11.3.1. Getting A Collection's Handle</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N1489A">11.4. Custom Metadata-entry Pages for Submission</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N1489E">11.4.1. Introduction</a></span></dt><dt><span class="section"><a href="ch11.html#N148C9">11.4.2. Describing Custom Metadata Forms</a></span></dt><dt><span class="section"><a href="ch11.html#N148EC">11.4.3. The Structure of input-forms.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N14B7A">11.4.4. Deploying Your Custom Forms</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N14B97">11.5. Configuring the File Upload step</a></span></dt><dt><span class="section"><a href="ch11.html#N14BC3">11.6. Creating new Submission Steps</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14C5C">11.6.1. Creating a Non-Interactive Step</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch12.html">12. docbook/DRISchemaReference.html</a></span></dt><dt><span class="chapter"><a href="ch13.html">13. DRI Schema Reference</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14C9C">13.1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14CAD">13.1.1. The Purpose of DRI</a></span></dt><dt><span class="section"><a href="ch13.html#N14CB3">13.1.2. The Development of DRI</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14CCF">13.2. DRI in Manakin</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14CD8">13.2.1. Themes</a></span></dt><dt><span class="section"><a href="ch13.html#N14CE4">13.2.2. Aspect Chains</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14CEA">13.3. Common Design Patterns</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14CFC">13.3.1. Localization and Internationalization</a></span></dt><dt><span class="section"><a href="ch13.html#N14D10">13.3.2. Standard attribute triplet</a></span></dt><dt><span class="section"><a href="ch13.html#N14D5E">13.3.3. Structure-oriented markup</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14D64">13.4. Schema Overview</a></span></dt><dt><span class="section"><a href="ch13.html#N14DF7">13.5. Merging of DRI Documents</a></span></dt><dt><span class="section"><a href="ch13.html#N14E9C">13.6. Version Changes</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14EA5">13.6.1. Changes from 1.0 to 1.1</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14ECF">13.7. Element Reference</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N153C8">13.7.1. BODY</a></span></dt><dt><span class="section"><a href="ch13.html#N15407">13.7.2. cell</a></span></dt><dt><span class="section"><a href="ch13.html#N154B9">13.7.3. div</a></span></dt><dt><span class="section"><a href="ch13.html#N155E8">13.7.4. DOCUMENT</a></span></dt><dt><span class="section"><a href="ch13.html#N15634">13.7.5. field</a></span></dt><dt><span class="section"><a href="ch13.html#N1573B">13.7.6. figure</a></span></dt><dt><span class="section"><a href="ch13.html#N157A9">13.7.7. head</a></span></dt><dt><span class="section"><a href="ch13.html#N1582C">13.7.8. help</a></span></dt><dt><span class="section"><a href="ch13.html#N15867">13.7.9. hi</a></span></dt><dt><span class="section"><a href="ch13.html#N158F6">13.7.10. instance</a></span></dt><dt><span class="section"><a href="ch13.html#N15927">13.7.11. item</a></span></dt><dt><span class="section"><a href="ch13.html#N159CB">13.7.12. label</a></span></dt><dt><span class="section"><a href="ch13.html#N15A29">13.7.13. list</a></span></dt><dt><span class="section"><a href="ch13.html#N15B65">13.7.14. META</a></span></dt><dt><span class="section"><a href="ch13.html#N15BB8">13.7.15. metadata</a></span></dt><dt><span class="section"><a href="ch13.html#N15C27">13.7.16. OPTIONS</a></span></dt><dt><span class="section"><a href="ch13.html#N15C66">13.7.17. p</a></span></dt><dt><span class="section"><a href="ch13.html#N15CE6">13.7.18. pageMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15D4B">13.7.19. params</a></span></dt><dt><span class="section"><a href="ch13.html#N15DAD">13.7.20. reference</a></span></dt><dt><span class="section"><a href="ch13.html#N15E11">13.7.21. referenceSet</a></span></dt><dt><span class="section"><a href="ch13.html#N15E9F">13.7.22. repository</a></span></dt><dt><span class="section"><a href="ch13.html#N15EE5">13.7.23. repositoryMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15F2E">13.7.24. row</a></span></dt><dt><span class="section"><a href="ch13.html#N15F93">13.7.25. table</a></span></dt><dt><span class="section"><a href="ch13.html#N16007">13.7.26. trail</a></span></dt><dt><span class="section"><a href="ch13.html#N1604D">13.7.27. userMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N160BD">13.7.28. value</a></span></dt><dt><span class="section"><a href="ch13.html#N16137">13.7.29. xref</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch14.html">14. DSpace System Documentation: Version History</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16195">14.1. Changes in DSpace 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1619C">14.1.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N161B9">14.1.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16212">14.2. Changes in DSpace 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16219">14.2.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1626F">14.2.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N162E6">14.3. Changes in DSpace 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N162ED">14.3.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1633A">14.3.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16369">14.4. Changes in DSpace 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16370">14.4.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1637E">14.4.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1638C">14.5. Changes in DSpace 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16393">14.5.1. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1639B">14.6. Changes in DSpace 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N163A2">14.6.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N163C8">14.6.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16409">14.7. Changes in DSpace 1.2.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16410">14.7.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1642D">14.7.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16441">14.7.3. Changes in JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16525">14.8. Changes in DSpace 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1652C">14.8.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16550">14.8.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16564">14.8.3. Changed JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16616">14.9. Changes in DSpace 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1661D">14.9.1. General Improvments</a></span></dt><dt><span class="section"><a href="ch14.html#N16637">14.9.2. Administration</a></span></dt><dt><span class="section"><a href="ch14.html#N16651">14.9.3. Import/Export/OAI</a></span></dt><dt><span class="section"><a href="ch14.html#N1665F">14.9.4. Miscellaneous</a></span></dt><dt><span class="section"><a href="ch14.html#N16673">14.9.5. JSP file changes between 1.1 and 1.2</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1679E">14.10. Changes in DSpace 1.1.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N167A5">14.10.1. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N167BC">14.10.2. Improvements</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N167E6">14.11. Changes in DSpace 1.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch15.html">15. DSpace System Documentation: Appendices</a></span></dt><dd><dl><dt><span class="section"><a href="ch15.html#N1682E">15.1. Default Dublin Core Metadata Registry</a></span></dt><dt><span class="section"><a href="ch15.html#N16D87">15.2. Default Bitstream Format Registry</a></span></dt></dl></dd><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="ch02.html#N100FC">MIT Libraries' Definitions of Bitstream Format Support Levels</a></dt><dt>2.2. <a href="ch02.html#N1013D">Objects in the DSpace Data Model</a></dt><dt>5.1. <a href="ch05.html#N11583">dspace.cfg Main Properties (Not Complete)</a></dt><dt>7.1. <a href="ch07.html#N12D1F">DSpace Log File Locations</a></dt><dt>8.1. <a href="ch08.html#N12E26">Source Code Packages</a></dt><dt>9.1. <a href="ch09.html#N12F58">Locations of Web UI Source Files</a></dt></dl></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+      </p></div></div><div><div class="abstract"><p class="title"><b>Abstract</b></p><p></p></div></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="preface"><a href="pr01.html">Preface</a></span></dt><dt><span class="chapter"><a href="ch01.html">1. DSpace System Documentation: Introduction</a></span></dt><dt><span class="chapter"><a href="ch02.html">2. DSpace System Documentation: Functional Overview</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N100A1">2.1. Data Model</a></span></dt><dt><span class="section"><a href="ch02.html#N101A3">2.2. Plugin Manager</a></span></dt><dt><span class="section"><a href="ch02.html#N101B4">2.3. Metadata</a></span></dt><dt><span class="section"><a href="ch02.html#N101F5">2.4. Packager Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N1021A">2.5. Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch02.html#N1023F">2.6. E-People and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N1024C">2.6.1. E-Person</a></span></dt><dt><span class="section"><a href="ch02.html#N10268">2.6.2. Groups</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10279">2.7. Authentication</a></span></dt><dt><span class="section"><a href="ch02.html#N10291">2.8. Authorization</a></span></dt><dt><span class="section"><a href="ch02.html#N1036E">2.9. Ingest Process and Workflow</a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#N103A9">2.9.1. Workflow Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch02.html#N10408">2.10. Supervision and Collaboration</a></span></dt><dt><span class="section"><a href="ch02.html#N1041F">2.11. Handles</a></span></dt><dt><span class="section"><a href="ch02.html#N10444">2.12. Bitstream 'Persistent' Identifiers</a></span></dt><dt><span class="section"><a href="ch02.html#N10464">2.13. Storage Resource Broker (SRB) Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10473">2.14. Search and Browse</a></span></dt><dt><span class="section"><a href="ch02.html#N1048E">2.15. HTML Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104D8">2.16. OAI Support</a></span></dt><dt><span class="section"><a href="ch02.html#N104FB">2.17. OpenURL Support</a></span></dt><dt><span class="section"><a href="ch02.html#N1050C">2.18. Creative Commons Support</a></span></dt><dt><span class="section"><a href="ch02.html#N10519">2.19. Subscriptions</a></span></dt><dt><span class="section"><a href="ch02.html#N10526">2.20. History</a></span></dt><dt><span class="section"><a href="ch02.html#N10535">2.21. Import and Export</a></span></dt><dt><span class="section"><a href="ch02.html#N10540">2.22. Registration</a></span></dt><dt><span class="section"><a href="ch02.html#N10551">2.23. Statistics</a></span></dt><dt><span class="section"><a href="ch02.html#N1057E">2.24. Checksum Checker</a></span></dt><dt><span class="section"><a href="ch02.html#N10587">2.25. 
+    		Usage Instrumentation</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch03.html">3. DSpace System Documentation: Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10597">3.1. Prerequisite Software</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N105A2">3.1.1. UNIX-like OS or Microsoft Windows</a></span></dt><dt><span class="section"><a href="ch03.html#N105B1">3.1.2. Java JDK 5 or later (standard SDK is fine, you don't need J2EE)</a></span></dt><dt><span class="section"><a href="ch03.html#N105BC">3.1.3. Apache Maven 2.0.8 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105CB">3.1.4. Apache Ant 1.6.2 or later (Java build tool)</a></span></dt><dt><span class="section"><a href="ch03.html#N105DA">3.1.5. Relational Database: (PostgreSQL or Oracle).</a></span></dt><dt><span class="section"><a href="ch03.html#N10644">3.1.6. Servlet Engine: (Jakarta Tomcat 4.x, Jetty, Caucho Resin or equivalent).</a></span></dt><dt><span class="section"><a href="ch03.html#N1068F">3.1.7. Perl (required for [dspace]/bin/dspace-info.pl)</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10695">3.2. Installation Options</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N1069C">3.2.1. Overview of Install Options</a></span></dt><dt><span class="section"><a href="ch03.html#N10739">3.2.2. Overview of DSpace Directories</a></span></dt><dt><span class="section"><a href="ch03.html#N10797">3.2.3. Installation</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N1091F">3.3. Advanced Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10928">3.3.1. 'cron' Jobs</a></span></dt><dt><span class="section"><a href="ch03.html#N10968">3.3.2. Multilingual Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10983">3.3.3. DSpace over HTTPS</a></span></dt><dt><span class="section"><a href="ch03.html#N10AB9">3.3.4. The Handle Server</a></span></dt><dt><span class="section"><a href="ch03.html#N10B54">3.3.5. Google and HTML sitemaps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10BA6">3.4. Windows Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch03.html#N10BAD">3.4.1. Pre-requisite Software</a></span></dt><dt><span class="section"><a href="ch03.html#N10BEF">3.4.2. Installation Steps</a></span></dt></dl></dd><dt><span class="section"><a href="ch03.html#N10CA6">3.5. Checking Your Installation</a></span></dt><dt><span class="section"><a href="ch03.html#N10CAF">3.6. Known Bugs</a></span></dt><dt><span class="section"><a href="ch03.html#N10CC4">3.7. Common Problems</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch04.html">4. DSpace System Documentation: Updating a DSpace Installation</a></span></dt><dd><dl><dt><span class="section"><a href="ch04.html#N10D4B">4.1. Updating From 1.4.2 to 1.5</a></span></dt><dt><span class="section"><a href="ch04.html#N10ECA">4.2. Updating From 1.4.1 to 1.4.2</a></span></dt><dt><span class="section"><a href="ch04.html#N10ED7">4.3. Updating From 1.4 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N10F80">4.4. Updating From 1.3.2 to 1.4.x</a></span></dt><dt><span class="section"><a href="ch04.html#N1108E">4.5. Updating From 1.3.1 to 1.3.2</a></span></dt><dt><span class="section"><a href="ch04.html#N11102">4.6. Updating From 1.2.x to 1.3.x</a></span></dt><dt><span class="section"><a href="ch04.html#N111C1">4.7. Updating From 1.2.1 to 1.2.2</a></span></dt><dt><span class="section"><a href="ch04.html#N1124E">4.8. Updating From 1.2 to 1.2.1</a></span></dt><dt><span class="section"><a href="ch04.html#N112D0">4.9. Updating From 1.1 (or 1.1.1) to 1.2</a></span></dt><dt><span class="section"><a href="ch04.html#N11448">4.10. Updating From 1.1 to 1.1.1</a></span></dt><dt><span class="section"><a href="ch04.html#N11482">4.11. Updating From 1.0.1 to 1.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch05.html">5. DSpace System Documentation: Configuration and Customization</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11556">5.1. General Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N1155F">5.1.1. The dspace.cfg Configuration Properties File</a></span></dt><dt><span class="section"><a href="ch05.html#N118AC">5.1.2. Configuring Lucene Search Indexes</a></span></dt><dt><span class="section"><a href="ch05.html#N118F8">5.1.3. Browse Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N11A10">5.1.4. Configuring Media Filters</a></span></dt><dt><span class="section"><a href="ch05.html#N11A56">5.1.5. Wording of E-mail Messages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11A7F">5.2. The Metadata and Bitstream Format Registries</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11A9D">5.2.1. Metadata Schema Registry</a></span></dt><dt><span class="section"><a href="ch05.html#N11AAB">5.2.2. Metadata Format Registries</a></span></dt><dt><span class="section"><a href="ch05.html#N11ACB">5.2.3. Bitstream Format Registry</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11AE6">5.3. The Default Submission License</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11AFB">5.3.1. Possible Points in a License</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11B33">5.4. Submission Configuration</a></span></dt><dt><span class="section"><a href="ch05.html#N11B40">5.5. XMLUI Interface Customizations (Manakin)</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11B49">5.5.1. XMLUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11CEC">5.5.2. Configuring Themes and Aspects</a></span></dt><dt><span class="section"><a href="ch05.html#N11D96">5.5.3. Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N11DDB">5.5.4. Creating a New Theme</a></span></dt><dt><span class="section"><a href="ch05.html#N11E2A">5.5.5. Adding Static Content</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N11E4A">5.6. JSPUI Interface Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N11E53">5.6.1. JSPUI Configuration Properties</a></span></dt><dt><span class="section"><a href="ch05.html#N11F46">5.6.2. Configuring Controlled Vocabularies</a></span></dt><dt><span class="section"><a href="ch05.html#N11FB1">5.6.3. Configuring Multilingual Support</a></span></dt><dt><span class="section"><a href="ch05.html#N120B3">5.6.4. Customizing the JSP pages</a></span></dt></dl></dd><dt><span class="section"><a href="ch05.html#N12184">5.7. Advanced DSpace Customizations</a></span></dt><dd><dl><dt><span class="section"><a href="ch05.html#N1218D">5.7.1. Checksum Checker</a></span></dt><dt><span class="section"><a href="ch05.html#N12281">5.7.2. Custom Authentication</a></span></dt><dt><span class="section"><a href="ch05.html#N123F5">5.7.3. Configuring System Statistical Reports</a></span></dt><dt><span class="section"><a href="ch05.html#N1244C">5.7.4. Activating Additional OAI-PMH Crosswalks</a></span></dt><dt><span class="section"><a href="ch05.html#N124E5">5.7.5. Configuring Packager Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N12504">5.7.6. Configuring Crosswalk Plugins</a></span></dt><dt><span class="section"><a href="ch05.html#N12694">5.7.7. Creating a new Media/Format Filter</a></span></dt><dt><span class="section"><a href="ch05.html#N12798">5.7.8. Configuration Files for Other Applications</a></span></dt><dt><span class="section"><a href="ch05.html#N127FA">5.7.9. Browse Index Creation</a></span></dt><dt><span class="section"><a href="ch05.html#N12873">5.7.10. 
+      		Configuring Usage Instrumentation Plugins</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch06.html">6. DSpace System Documentation: Storage Layer</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N128C3">6.1. RDBMS</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N1294E">6.1.1. Maintenance and Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N12987">6.1.2. Configuring the RDBMS Component</a></span></dt></dl></dd><dt><span class="section"><a href="ch06.html#N129DC">6.2. Bitstream Store</a></span></dt><dd><dl><dt><span class="section"><a href="ch06.html#N12AD3">6.2.1. Backup</a></span></dt><dt><span class="section"><a href="ch06.html#N12AE7">6.2.2. Configuring the Bitstream Store</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch07.html">7. DSpace System Documentation: Directories and Files</a></span></dt><dd><dl><dt><span class="section"><a href="ch07.html#N12B50">7.1. Overview</a></span></dt><dt><span class="section"><a href="ch07.html#N12B78">7.2. Source Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12C8D">7.3. Installed Directory Layout</a></span></dt><dt><span class="section"><a href="ch07.html#N12CE2">7.4. Contents of JSPUI Web Application</a></span></dt><dt><span class="section"><a href="ch07.html#N12D1E">7.5. Contents of XMLUI Web Application (aka Manakin)</a></span></dt><dt><span class="section"><a href="ch07.html#N12D92">7.6. Log Files</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch08.html">8. DSpace System Documentation: Architecture</a></span></dt><dd><dl><dt><span class="section"><a href="ch08.html#N12E74">8.1. Overview</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch09.html">9. DSpace System Documentation: Application Layer</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N12FC3">9.1. Web User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N12FCE">9.1.1. Web UI Files</a></span></dt><dt><span class="section"><a href="ch09.html#N1309C">9.1.2. The Build Process</a></span></dt><dt><span class="section"><a href="ch09.html#N13120">9.1.3. Servlets and JSPs</a></span></dt><dt><span class="section"><a href="ch09.html#N131D3">9.1.4. Custom JSP Tags</a></span></dt><dt><span class="section"><a href="ch09.html#N13278">9.1.5. Internationalisation</a></span></dt><dt><span class="section"><a href="ch09.html#N13355">9.1.6. HTML Content in Items</a></span></dt><dt><span class="section"><a href="ch09.html#N133CF">9.1.7. Thesis Blocking</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N133E5">9.2. OAI-PMH Data Provider</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N134A4">9.2.1. Sets</a></span></dt><dt><span class="section"><a href="ch09.html#N134B3">9.2.2. Unique Identifier</a></span></dt><dt><span class="section"><a href="ch09.html#N134DF">9.2.3. Access control</a></span></dt><dt><span class="section"><a href="ch09.html#N134E9">9.2.4. Modification Date (OAI Date Stamp)</a></span></dt><dt><span class="section"><a href="ch09.html#N134EF">9.2.5. 'About' Information</a></span></dt><dt><span class="section"><a href="ch09.html#N134F5">9.2.6. Deletions</a></span></dt><dt><span class="section"><a href="ch09.html#N13504">9.2.7. Flow Control (Resumption Tokens)</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13548">9.3. Community and Collection Structure Importer</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13567">9.3.1. Limitation</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N13570">9.4. Package Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13589">9.4.1. Ingesting</a></span></dt><dt><span class="section"><a href="ch09.html#N135BD">9.4.2. Disseminating</a></span></dt><dt><span class="section"><a href="ch09.html#N135EA">9.4.3. METS packages</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N1360A">9.5. Item Importer and Exporter</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13613">9.5.1. DSpace simple archive format</a></span></dt><dt><span class="section"><a href="ch09.html#N13650">9.5.2. Importing Items</a></span></dt><dt><span class="section"><a href="ch09.html#N13688">9.5.3. Exporting Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N136A2">9.6. Transferring Items Between DSpace Instances</a></span></dt><dt><span class="section"><a href="ch09.html#N136E1">9.7. Registering (Not Importing) Bitstreams</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N136F2">9.7.1. Accessible Storage</a></span></dt><dt><span class="section"><a href="ch09.html#N13710">9.7.2. Registering Items Using the Item Importer</a></span></dt><dt><span class="section"><a href="ch09.html#N137A2">9.7.3. Internal Identification and Retrieval of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N137CE">9.7.4. Exporting Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N137D8">9.7.5. METS Export of Registered Items</a></span></dt><dt><span class="section"><a href="ch09.html#N137E2">9.7.6. Deleting Registered Items</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N137FA">9.8. METS Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch09.html#N13803">9.8.1. The Export Tool</a></span></dt><dt><span class="section"><a href="ch09.html#N13834">9.8.2. The AIP Format</a></span></dt><dt><span class="section"><a href="ch09.html#N138D7">9.8.3. Limitations</a></span></dt></dl></dd><dt><span class="section"><a href="ch09.html#N138EF">9.9. MediaFilters: Transforming DSpace Content</a></span></dt><dt><span class="section"><a href="ch09.html#N139BB">9.10. Sub-Community Management</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch10.html">10. DSpace System Documentation: Business Logic Layer</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N139EA">10.1. Core Classes</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N139F7">10.1.1. The Configuration Manager (ConfigurationManager)</a></span></dt><dt><span class="section"><a href="ch10.html#N13A40">10.1.2. Constants</a></span></dt><dt><span class="section"><a href="ch10.html#N13A5E">10.1.3. Context</a></span></dt><dt><span class="section"><a href="ch10.html#N13AAC">10.1.4. Email</a></span></dt><dt><span class="section"><a href="ch10.html#N13AC4">10.1.5. LogManager</a></span></dt><dt><span class="section"><a href="ch10.html#N13BA8">10.1.6. Utils</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13BB1">10.2. Content Management API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13C5B">10.2.1. Other Classes</a></span></dt><dt><span class="section"><a href="ch10.html#N13C7F">10.2.2. Modifications</a></span></dt><dt><span class="section"><a href="ch10.html#N13D04">10.2.3. What's In Memory?</a></span></dt><dt><span class="section"><a href="ch10.html#N13D54">10.2.4. Dublin Core Metadata</a></span></dt><dt><span class="section"><a href="ch10.html#N13E35">10.2.5. Support for Other Metadata Schemas</a></span></dt><dt><span class="section"><a href="ch10.html#N13E54">10.2.6. Packager Plugins</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N13E90">10.3. Plugin Manager</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N13E99">10.3.1. Concepts</a></span></dt><dt><span class="section"><a href="ch10.html#N13EC8">10.3.2. Using the Plugin Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N13F48">10.3.3. Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N13FEF">10.3.4. Configuring Plugins</a></span></dt><dt><span class="section"><a href="ch10.html#N140AF">10.3.5. Validating the Configuration</a></span></dt><dt><span class="section"><a href="ch10.html#N140FF">10.3.6. Use Cases</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N14152">10.4. Workflow System</a></span></dt><dt><span class="section"><a href="ch10.html#N141CA">10.5. Administration Toolkit</a></span></dt><dt><span class="section"><a href="ch10.html#N14205">10.6. E-person/Group Manager</a></span></dt><dt><span class="section"><a href="ch10.html#N1424C">10.7. Authorization</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N142D5">10.7.1. Special Groups</a></span></dt><dt><span class="section"><a href="ch10.html#N142DB">10.7.2. Miscellaneous Authorization Notes</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N142E1">10.8. Handle Manager/Handle Plugin</a></span></dt><dt><span class="section"><a href="ch10.html#N14359">10.9. Search</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N143B8">10.9.1. Our Lucene Implementation</a></span></dt><dt><span class="section"><a href="ch10.html#N143CA">10.9.2. Indexed Fields</a></span></dt><dt><span class="section"><a href="ch10.html#N1447F">10.9.3. Harvesting API</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N144AE">10.10. Browse API</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N1452B">10.10.1. Using the API</a></span></dt><dt><span class="section"><a href="ch10.html#N1458A">10.10.2. Index Maintenance</a></span></dt><dt><span class="section"><a href="ch10.html#N1459A">10.10.3. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N145B5">10.11. History Recorder</a></span></dt><dd><dl><dt><span class="section"><a href="ch10.html#N145DC">10.11.1. Archival Events</a></span></dt><dt><span class="section"><a href="ch10.html#N14612">10.11.2. Serializations</a></span></dt><dt><span class="section"><a href="ch10.html#N1461F">10.11.3. Unique Ids</a></span></dt><dt><span class="section"><a href="ch10.html#N1462F">10.11.4. Storage</a></span></dt><dt><span class="section"><a href="ch10.html#N1464A">10.11.5. Example</a></span></dt><dt><span class="section"><a href="ch10.html#N14663">10.11.6. Caveats</a></span></dt></dl></dd><dt><span class="section"><a href="ch10.html#N1466D">10.12. Checksum checker</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch11.html">11. Customizing and Configuring Submission User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N1468B">11.1. Understanding the Submission Configuration File</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14698">11.1.1. The Structure of item-submission.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N146C7">11.1.2. Defining Steps (&lt;step&gt;) within the item-submission.xml</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N147FB">11.2. Reordering/Removing Submission Steps</a></span></dt><dt><span class="section"><a href="ch11.html#N148A8">11.3. Assigning a custom Submission Process to a Collection</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N148FB">11.3.1. Getting A Collection's Handle</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N1491E">11.4. Custom Metadata-entry Pages for Submission</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14922">11.4.1. Introduction</a></span></dt><dt><span class="section"><a href="ch11.html#N1494D">11.4.2. Describing Custom Metadata Forms</a></span></dt><dt><span class="section"><a href="ch11.html#N14970">11.4.3. The Structure of input-forms.xml</a></span></dt><dt><span class="section"><a href="ch11.html#N14BFE">11.4.4. Deploying Your Custom Forms</a></span></dt></dl></dd><dt><span class="section"><a href="ch11.html#N14C1B">11.5. Configuring the File Upload step</a></span></dt><dt><span class="section"><a href="ch11.html#N14C47">11.6. Creating new Submission Steps</a></span></dt><dd><dl><dt><span class="section"><a href="ch11.html#N14CE0">11.6.1. Creating a Non-Interactive Step</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch12.html">12. docbook/DRISchemaReference.html</a></span></dt><dt><span class="chapter"><a href="ch13.html">13. DRI Schema Reference</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D20">13.1. Introduction</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D31">13.1.1. The Purpose of DRI</a></span></dt><dt><span class="section"><a href="ch13.html#N14D37">13.1.2. The Development of DRI</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14D53">13.2. DRI in Manakin</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D5C">13.2.1. Themes</a></span></dt><dt><span class="section"><a href="ch13.html#N14D68">13.2.2. Aspect Chains</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14D6E">13.3. Common Design Patterns</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14D80">13.3.1. Localization and Internationalization</a></span></dt><dt><span class="section"><a href="ch13.html#N14D94">13.3.2. Standard attribute triplet</a></span></dt><dt><span class="section"><a href="ch13.html#N14DE2">13.3.3. Structure-oriented markup</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14DE8">13.4. Schema Overview</a></span></dt><dt><span class="section"><a href="ch13.html#N14E7B">13.5. Merging of DRI Documents</a></span></dt><dt><span class="section"><a href="ch13.html#N14F20">13.6. Version Changes</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N14F29">13.6.1. Changes from 1.0 to 1.1</a></span></dt></dl></dd><dt><span class="section"><a href="ch13.html#N14F53">13.7. Element Reference</a></span></dt><dd><dl><dt><span class="section"><a href="ch13.html#N1544C">13.7.1. BODY</a></span></dt><dt><span class="section"><a href="ch13.html#N1548B">13.7.2. cell</a></span></dt><dt><span class="section"><a href="ch13.html#N1553D">13.7.3. div</a></span></dt><dt><span class="section"><a href="ch13.html#N1566C">13.7.4. DOCUMENT</a></span></dt><dt><span class="section"><a href="ch13.html#N156B8">13.7.5. field</a></span></dt><dt><span class="section"><a href="ch13.html#N157BF">13.7.6. figure</a></span></dt><dt><span class="section"><a href="ch13.html#N1582D">13.7.7. head</a></span></dt><dt><span class="section"><a href="ch13.html#N158B0">13.7.8. help</a></span></dt><dt><span class="section"><a href="ch13.html#N158EB">13.7.9. hi</a></span></dt><dt><span class="section"><a href="ch13.html#N1597A">13.7.10. instance</a></span></dt><dt><span class="section"><a href="ch13.html#N159AB">13.7.11. item</a></span></dt><dt><span class="section"><a href="ch13.html#N15A4F">13.7.12. label</a></span></dt><dt><span class="section"><a href="ch13.html#N15AAD">13.7.13. list</a></span></dt><dt><span class="section"><a href="ch13.html#N15BE9">13.7.14. META</a></span></dt><dt><span class="section"><a href="ch13.html#N15C3C">13.7.15. metadata</a></span></dt><dt><span class="section"><a href="ch13.html#N15CAB">13.7.16. OPTIONS</a></span></dt><dt><span class="section"><a href="ch13.html#N15CEA">13.7.17. p</a></span></dt><dt><span class="section"><a href="ch13.html#N15D6A">13.7.18. pageMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15DCF">13.7.19. params</a></span></dt><dt><span class="section"><a href="ch13.html#N15E31">13.7.20. reference</a></span></dt><dt><span class="section"><a href="ch13.html#N15E95">13.7.21. referenceSet</a></span></dt><dt><span class="section"><a href="ch13.html#N15F23">13.7.22. repository</a></span></dt><dt><span class="section"><a href="ch13.html#N15F69">13.7.23. repositoryMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N15FB2">13.7.24. row</a></span></dt><dt><span class="section"><a href="ch13.html#N16017">13.7.25. table</a></span></dt><dt><span class="section"><a href="ch13.html#N1608B">13.7.26. trail</a></span></dt><dt><span class="section"><a href="ch13.html#N160D1">13.7.27. userMeta</a></span></dt><dt><span class="section"><a href="ch13.html#N16141">13.7.28. value</a></span></dt><dt><span class="section"><a href="ch13.html#N161BB">13.7.29. xref</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch14.html">14. DSpace System Documentation: Version History</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N1621B">14.1. Changes in DSpace 1.5.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16222">14.1.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1622A">14.1.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16232">14.2. Changes in DSpace 1.5.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16239">14.2.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16241">14.2.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16249">14.3. Changes in DSpace 1.5</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16250">14.3.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1626D">14.3.2. Bug fixes and smaller patches</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N162C6">14.4. Changes in DSpace 1.4.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N162CD">14.4.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16323">14.4.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1639A">14.5. Changes in DSpace 1.4</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N163A1">14.5.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N163EE">14.5.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1641D">14.6. Changes in DSpace 1.3.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16424">14.6.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16432">14.6.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16440">14.7. Changes in DSpace 1.3.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16447">14.7.1. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1644F">14.8. Changes in DSpace 1.3</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16456">14.8.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N1647C">14.8.2. Bug fixes</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N164BD">14.9. Changes in DSpace 1.2.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N164C4">14.9.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N164E1">14.9.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N164F5">14.9.3. Changes in JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N165D9">14.10. Changes in DSpace 1.2.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N165E0">14.10.1. General Improvements</a></span></dt><dt><span class="section"><a href="ch14.html#N16604">14.10.2. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16618">14.10.3. Changed JSPs</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N166CA">14.11. Changes in DSpace 1.2</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N166D1">14.11.1. General Improvments</a></span></dt><dt><span class="section"><a href="ch14.html#N166EB">14.11.2. Administration</a></span></dt><dt><span class="section"><a href="ch14.html#N16705">14.11.3. Import/Export/OAI</a></span></dt><dt><span class="section"><a href="ch14.html#N16713">14.11.4. Miscellaneous</a></span></dt><dt><span class="section"><a href="ch14.html#N16727">14.11.5. JSP file changes between 1.1 and 1.2</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N16852">14.12. Changes in DSpace 1.1.1</a></span></dt><dd><dl><dt><span class="section"><a href="ch14.html#N16859">14.12.1. Bug fixes</a></span></dt><dt><span class="section"><a href="ch14.html#N16870">14.12.2. Improvements</a></span></dt></dl></dd><dt><span class="section"><a href="ch14.html#N1689A">14.13. Changes in DSpace 1.1</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch15.html">15. DSpace System Documentation: Appendices</a></span></dt><dd><dl><dt><span class="section"><a href="ch15.html#N168E4">15.1. Default Dublin Core Metadata Registry</a></span></dt><dt><span class="section"><a href="ch15.html#N16E3D">15.2. Default Bitstream Format Registry</a></span></dt></dl></dd><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="ch02.html#N10100">MIT Libraries' Definitions of Bitstream Format Support Levels</a></dt><dt>2.2. <a href="ch02.html#N10141">Objects in the DSpace Data Model</a></dt><dt>5.1. <a href="ch05.html#N11597">dspace.cfg Main Properties (Not Complete)</a></dt><dt>7.1. <a href="ch07.html#N12D9B">DSpace Log File Locations</a></dt><dt>8.1. <a href="ch08.html#N12EA4">Source Code Packages</a></dt><dt>9.1. <a href="ch09.html#N12FD8">Locations of Web UI Source Files</a></dt></dl></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/ix01.html b/dspace/docs/html/ix01.html
index 0555dc76e6..aa7576adaf 100644
--- a/dspace/docs/html/ix01.html
+++ b/dspace/docs/html/ix01.html
@@ -1,4 +1,4 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="ch15.html" title="Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Index</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch15.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;</td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="N17243"></a>Index</h2></div></div></div><div class="index"></div></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Index</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="ch15.html" title="Chapter&nbsp;15.&nbsp;DSpace System Documentation: Appendices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Index</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch15.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;</td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h2 class="title"><a name="N172F9"></a>Index</h2></div></div></div><div class="index"></div></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
diff --git a/dspace/docs/html/pr01.html b/dspace/docs/html/pr01.html
index c87e040ef0..265d476ec5 100644
--- a/dspace/docs/html/pr01.html
+++ b/dspace/docs/html/pr01.html
@@ -1,8 +1,8 @@
-<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><meta content="DocBook XSL Stylesheets V1.74.0" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.1 Manual"><link rel="up" href="index.html" title="DSpace 1.5.1 Manual"><link rel="prev" href="index.html" title="DSpace 1.5.1 Manual"><link rel="next" href="ch01.html" title="Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Preface</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="index.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch01.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10026"></a>Preface</h2></div></div></div><p></p></div><HR><p class="copyright">Copyright &copy; 2002-2008 
+<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Preface</title><meta content="DocBook XSL Stylesheets V1.74.3" name="generator"><link rel="home" href="index.html" title="DSpace 1.5.2 Manual"><link rel="up" href="index.html" title="DSpace 1.5.2 Manual"><link rel="prev" href="index.html" title="DSpace 1.5.2 Manual"><link rel="next" href="ch01.html" title="Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Preface</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="index.html">Prev</a>&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;<a accesskey="n" href="ch01.html">Next</a></td></tr></table><hr></div><div class="preface" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="N10026"></a>Preface</h2></div></div></div><p></p></div><HR><p class="copyright">Copyright &copy; 2002-2009 
         <a class="ulink" href="http://www.dspace.org/" target="_top">The DSpace Foundation</a>
       </p><div class="legalnotice"><a name="N10017"></a><p>
         <a class="ulink" href="http://creativecommons.org/licenses/by/3.0/us/" target="_top">
         <span class="inlinemediaobject"><img src="http://i.creativecommons.org/l/by/3.0/us/88x31.png"></span>
         Licensed under a Creative Commons Attribution 3.0 United States License
         </a>
-      </p></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="index.html">Prev</a>&nbsp;</td><td align="center" width="20%">&nbsp;</td><td align="right" width="40%">&nbsp;<a accesskey="n" href="ch01.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">DSpace 1.5.1 Manual&nbsp;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%">&nbsp;Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</td></tr></table></div></body></html>
\ No newline at end of file
+      </p></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="index.html">Prev</a>&nbsp;</td><td align="center" width="20%">&nbsp;</td><td align="right" width="40%">&nbsp;<a accesskey="n" href="ch01.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">DSpace 1.5.2 Manual&nbsp;</td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%">&nbsp;Chapter&nbsp;1.&nbsp;DSpace System Documentation: Introduction</td></tr></table></div></body></html>
\ No newline at end of file
diff --git a/dspace/docs/pdf/DSpace-Manual.pdf b/dspace/docs/pdf/DSpace-Manual.pdf
index 370aa5895d..5b5db8a0b3 100644
Binary files a/dspace/docs/pdf/DSpace-Manual.pdf and b/dspace/docs/pdf/DSpace-Manual.pdf differ