mirror of
https://github.com/DSpace/DSpace.git
synced 2025-10-15 22:13:08 +00:00
17a2ad5b27
git-svn-id: http://scm.dspace.org/svn/repo/dspace/trunk@4764 9c30dcfa-912a-0410-8fc2-9e0234be79fd
169 lines
56 KiB
HTML
169 lines
56 KiB
HTML
<html><head><META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 12. DSpace System Documentation: Application Layer</title><meta content="DocBook XSL Stylesheets V1.75.2" name="generator"><link rel="home" href="index.html" title="DSpace Manual"><link rel="up" href="index.html" title="DSpace Manual"><link rel="prev" href="ch11.html" title="Chapter 11. DSpace System Documentation: Architecture"><link rel="next" href="ch13.html" title="Chapter 13. DSpace System Documentation: Business Logic Layer"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF" marginwidth="5m"><div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter 12. DSpace System Documentation: Application Layer</th></tr><tr><td align="left" width="20%"><a accesskey="p" href="ch11.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch13.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 12. DSpace System Documentation: Application Layer"><div class="titlepage"><div><div><h2 class="title"><a name="N1684F"></a>Chapter 12. <a name="docbook-application.html"></a>DSpace System Documentation: Application Layer</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch12.html#N1685B">12.1. Web User Interface</a></span></dt><dd><dl><dt><span class="section"><a href="ch12.html#N16866">12.1.1. Web UI Files</a></span></dt><dt><span class="section"><a href="ch12.html#N1693D">12.1.2. The Build Process</a></span></dt><dt><span class="section"><a href="ch12.html#N169C1">12.1.3. Servlets and JSPs</a></span></dt><dt><span class="section"><a href="ch12.html#N16A74">12.1.4. Custom JSP Tags</a></span></dt><dt><span class="section"><a href="ch12.html#N16B19">12.1.5. Internationalization</a></span></dt><dd><dl><dt><span class="section"><a href="ch12.html#N16BAB">12.1.5.1. Message Key Convention</a></span></dt><dt><span class="section"><a href="ch12.html#N16BEC">12.1.5.2. Which Languages are currently supported?</a></span></dt></dl></dd><dt><span class="section"><a href="ch12.html#N16BF6">12.1.6. HTML Content in Items</a></span></dt><dt><span class="section"><a href="ch12.html#N16C70">12.1.7. Thesis Blocking</a></span></dt></dl></dd><dt><span class="section"><a href="ch12.html#N16C86">12.2. OAI-PMH Data Provider</a></span></dt><dd><dl><dt><span class="section"><a href="ch12.html#N16D45">12.2.1. Sets</a></span></dt><dt><span class="section"><a href="ch12.html#N16D54">12.2.2. Unique Identifier</a></span></dt><dt><span class="section"><a href="ch12.html#N16D80">12.2.3. Access control</a></span></dt><dt><span class="section"><a href="ch12.html#N16D8A">12.2.4. Modification Date (OAI Date Stamp)</a></span></dt><dt><span class="section"><a href="ch12.html#N16D90">12.2.5. 'About' Information</a></span></dt><dt><span class="section"><a href="ch12.html#N16D96">12.2.6. Deletions</a></span></dt><dt><span class="section"><a href="ch12.html#N16DA5">12.2.7. Flow Control (Resumption Tokens)</a></span></dt></dl></dd><dt><span class="section"><a href="ch12.html#N16DE8">12.3. DSpace Command Launcher</a></span></dt><dd><dl><dt><span class="section"><a href="ch12.html#N16DF1">12.3.1. Older Versions</a></span></dt><dt><span class="section"><a href="ch12.html#N16DFF">12.3.2. Command Launcher Structure</a></span></dt></dl></dd></dl></div><p>
|
||
<a class="link" href="ch11.html#docbook-architecture.html">Back to architecture overview</a>
|
||
</p><div class="section" title="12.1. Web User Interface"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N1685B"></a>12.1. <a name="docbook-application.html-webui"></a>Web User Interface</h2></div></div><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" title="12.1.1. Web UI Files"><div class="titlepage"><div><div><h3 class="title"><a name="N16866"></a>12.1.1. Web UI Files</h3></div></div><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.5, the deployment has changed. The build systems has moved to a maven-based system enabling the various projects (JSPUI, XMLUI, etc.) into separate projects. The system still uses the familar 'Ant' to deploy the webapps in later stages.</p><div class="table"><a name="N1686C"></a><p class="title"><b>Table 12.1. 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>
|
||
</td><td>
|
||
<p>
|
||
<span class="bold"><strong>Description</strong></span>
|
||
</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Web UI source files</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/filters</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Servlet Filters (Servlet 2.3 spec)</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/jsptag</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Custom JSP tag class files</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/servlet</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Servlets for main Web UI (controllers)</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/servlet/admin</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Servlets that comprise the administration part of the Web UI</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-api/src/main/java/org/dspace/app/webui/util/</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Miscellaneous classes used by the servlets and filters</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui</code>
|
||
</p>
|
||
</td><td>
|
||
<p>The JSP files</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace/modules/jspui/src/main/webapp</code>
|
||
</p>
|
||
</td><td>
|
||
<p>This is where you place customized versions of JSPs—see <a class="link" href="ch06.html#docbook-jspui.html">6. JSPUI Configuration and Customization</a></p>
|
||
</td></tr><tr><td>
|
||
<p><code class="literal">[dspace-source]/dspace/modules/xmlui/src/main/webapp</code></p>
|
||
</td><td>
|
||
<p>This is where you place customizations for the Manakin interface—see <a class="link" href="ch07.html#docbook-xmlui.html">7. Manakin [XMLUI] Configuration and Customization</a></p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source/dspace/modules/jspui/src/main/resources</code>
|
||
</p>
|
||
</td><td>
|
||
<p>This is where you can place you customize version of the <code class="literal">Messages.properties</code> file.</p>
|
||
</td></tr><tr><td>
|
||
<p>
|
||
<code class="literal">[dspace-source]/dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/dspace-tags.tld</code>
|
||
</p>
|
||
</td><td>
|
||
<p>Custom DSpace JSP tag descriptor</p>
|
||
</td></tr></tbody></table></div></div><br class="table-break"><p>. </p><p>. </p></div><div class="section" title="12.1.2. The Build Process"><div class="titlepage"><div><div><h3 class="title"><a name="N1693D"></a>12.1.2. <a name="docbook-application.html-webui_build"></a>The Build Process</h3></div></div><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 class="itemizedlist" type="disc"><li class="listitem"><p> All the DSpace source code is compiled.</p></li><li class="listitem"><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 class="listitem"><p> The JSPs are all copied to <code class="literal">[dspace-source]/build/jsp</code></p></li><li class="listitem"><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 class="listitem"><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 class="itemizedlist" type="disc"><li class="listitem"><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 class="listitem"><p><code class="literal">WEB-INF/classes</code> -- the compiled DSpace classes</p></li><li class="listitem"><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 class="listitem"><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 class="listitem"><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" title="12.1.3. Servlets and JSPs"><div class="titlepage"><div><div><h3 class="title"><a name="N169C1"></a>12.1.3. Servlets and JSPs</h3></div></div><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 class="orderedlist" type="1"><li class="listitem"><p> An HTTP request is received from a browser</p></li><li class="listitem"><p> The appropriate servlet is invoked, and processes the request by invoking the DSpace business logic layer public API</p></li><li class="listitem"><p> Depending on the outcome of the processing, the servlet invokes the appropriate JSP</p></li><li class="listitem"><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 class="itemizedlist" type="disc"><li class="listitem"><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 class="listitem"><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" title="12.1.4. Custom JSP Tags"><div class="titlepage"><div><div><h3 class="title"><a name="N16A74"></a>12.1.4. Custom JSP Tags</h3></div></div><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"><BODY></code>tag. Thus the content of each JSP is nested inside a <code class="literal"><dspace:layout></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>
|
||
</span></dt><dd><p>Can only be used inside a <code class="literal">layout</code> tag, and can only be used once per JSP. The content between the start and end <code class="literal">sidebar</code> tags is rendered in a column on the right-hand side of the HTML page. The contents can contain further JSP tags and Java 'scriptlets'.</p></dd><dt><span class="term">
|
||
<code class="literal">date</code>
|
||
</span></dt><dd><p>Displays the date represented by an <code class="literal">org.dspace.content.DCDate</code> object. Just the one representation of date is rendered currently, but this could use the user's browser preferences to display a localized date in the future.</p></dd><dt><span class="term">
|
||
<code class="literal">include</code>
|
||
</span></dt><dd><p>Obsolete, simple tag, similar to <code class="literal">jsp:include</code>. In versions prior to DSpace 1.2, this tag would use the locally modified version of a JSP if one was installed in jsp/local. As of 1.2, the build process now performs this function, however this tag is left in for backwards compatibility.</p></dd><dt><span class="term">
|
||
<code class="literal">item</code>
|
||
</span></dt><dd><p>Displays an item record, including Dublin Core metadata and links to the bitstreams within it. Note that the displaying of the bitstream links is simplistic, and does not take into account any of the bundling structure. This is because DSpace does not have a fully-fledged dissemination architectural piece yet.</p><p>Displaying an item record is done by a tag rather than a JSP for two reasons: Firstly, it happens in several places (when verifying an item record during submission or workflow review, as well as during standard item accesses), and secondly, displaying the item turns out to be mostly code-work rather than HTML anyway. Of course, the disadvantage of doing it this way is that it is slightly harder to customize exactly what is displayed from an item record; it is necessary to edit the tag code (<code class="literal">org.dspace.app.webui.jsptag.ItemTag</code>). Hopefully a better solution can be found in the future.</p></dd><dt><span class="term"><code class="literal">itemlist</code>, <code class="literal">collectionlist</code>, <code class="literal">communitylist</code></span></dt><dd><p>These tags display ordered sequences of items, collections and communities, showing minimal information but including a link to the page containing full details. These need to be used in HTML tables.</p></dd><dt><span class="term">
|
||
<code class="literal">popup</code>
|
||
</span></dt><dd><p>This tag is used to render a link to a pop-up page (typically a help page.) If Javascript is available, the link will either open or pop to the front any existing DSpace pop-up window. If Javascript is not available, a standard HTML link is displayed that renders the link destination in a window named '<code class="literal">dspace.popup</code>'. In graphical browsers, this usually opens a new window or re-uses an existing window of that name, but if a window is re-used it is not 'raised' which might confuse the user. In text browsers, following this link will simply replace the current page with the destination of the link. This obviously means that Javascript offers the best functionality, but other browsers are still supported.</p></dd><dt><span class="term">
|
||
<code class="literal">selecteperson</code>
|
||
</span></dt><dd><p>A tag which produces a widget analogous to HTML <code class="literal"><SELECT></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" title="12.1.5. Internationalization"><div class="titlepage"><div><div><h3 class="title"><a name="N16B19"></a>12.1.5. <a name="docbook-application.html-i18n"></a>Internationalization</h3></div></div><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"><H1>Search Results</H1></pre><p>NEW:</p><pre class="screen"><H1><fmt:message key="jsp.search.results.title"/></H1></pre><p>This message can now be changed using the <code class="literal">config/language-packs/Messages.properties</code> file. (This must be done at build-time: <code class="literal">Messages.properties</code> is placed in the <code class="literal">dspace.war</code> Web application file.)</p><pre class="screen">jsp.search.results.title = Search Results</pre><p>Phrases may have parameters to be passed in, to make the job of translating easier, reduce the number of 'keys' and to allow translators to make the translated text flow more appropriately for the target language.</p><p>OLD:</p><pre class="screen"><P>Results <%= r.getFirst() %> to <%= r.getLast() %> of <%=r.getTotal() %></P></pre><p>NEW:</p><pre class="screen"><fmt:message key="jsp.search.results.text">
|
||
<fmt:param><%= r.getFirst() %></fmt:param>
|
||
<fmt:param><%= r.getLast() %></fmt:param>
|
||
<fmt:param><%= r.getTotal() %></fmt:param>
|
||
</fmt:message></pre><p>(Note: JSTL 1.0 does not seem to allow JSP <%= %> expressions to be passed in as values of attribute in <fmt:param value=""/>)</p><p>The above would appear in the <code class="literal">Messages_xx.properties</code> file as:</p><pre class="screen">jsp.search.results.text = Results {0}-{1} of {2} </pre><p>Introducing number parameters that should be formatted according to the locale used makes no difference in the message key compared to atring parameters:</p><pre class="screen">jsp.submit.show-uploaded-file.size-in-bytes = {0} bytes</pre><p>In the JSP using this key can be used in the way belov:</p><pre class="screen"><fmt:message key="jsp.submit.show-uploaded-file.size-in-bytes">
|
||
<fmt:param><fmt:formatNumber><%= bitstream.getSize()%></fmt:formatNumber></fmt:param>
|
||
</fmt:message>
|
||
</pre><p>(Note: JSTL offers a way to include numbers in the message keys as <code class="literal">jsp.foo.key = {0,number} bytes</code>. Setting the parameter as <code class="literal"><fmt:param value="${variable}" /></code> workes when <code class="literal">variable</code> is a single variable name and doesn't work when trying to use a method's return value instead: <code class="literal">bitstream.getSize()</code>. Passing the number as string (or using the <%= %> expression) also does not work.)</p><p>Multiple <code class="literal">Messages.properties</code> can be created for different languages. See <a class="ulink" href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/ResourceBundle.html#getBundle(java.lang.String,%20java.util.Locale,%20java.lang.ClassLoader)" target="_top">ResourceBundle.getBundle</a>. e.g. you can add German and Canadian French translations:</p><pre class="screen">Messages_de.properties
|
||
Messages_fr_CA.properties</pre><p>The end user's browser settings determine which language is used. The English language file <code class="literal">Messages.properties</code> (or the default server locale) will be used as a default if there's no language bundle for the end user's preferred language. (Note that the English file is not called <code class="literal">Messages_en.properties</code> -- this is so it is always available as a default, regardless of server configuration.)</p><p>The <code class="literal">dspace:layout</code> tag has been updated to allow dictionary keys to be passed in for the titles. It now has two new parameters: <code class="literal">titlekey</code> and <code class="literal">parenttitlekey</code>. So where before you'd do:</p><pre class="screen"><dspace:layout title="Here"
|
||
parentlink="/mydspace"
|
||
parenttitle="My DSpace">
|
||
</pre><p>You now do:</p><pre class="screen"><dspace:layout titlekey="jsp.page.title"
|
||
parentlink="/mydspace"
|
||
parenttitlekey="jsp.mydspace">
|
||
|
||
</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" title="12.1.5.1. Message Key Convention"><div class="titlepage"><div><div><h4 class="title"><a name="N16BAB"></a>12.1.5.1. Message Key Convention</h4></div></div><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</pre><p>Other common words/phrases are brought out into 'general' parameters if they relate to a set (directory) of JSPs, e.g.</p><pre class="screen">jsp.tools.general.delete = Delete</pre><p>Phrases that relate <span class="bold"><strong>strongly</strong></span> to a topic (eg. MyDSpace) but used in many JSPs outside the particular directory are more convenient to be cross-referenced. For example one could use the key below in <code class="literal">jsp/submit/saved.jsp</code> to provide a link back to the user's <span class="emphasis"><em>MyDSpace</em></span>:</p><p>
|
||
<span class="emphasis"><em>(Cross-referencing of keys <span class="bold"><strong>in general</strong></span> is not a good idea as it may make maintenance more difficult. But in some cases it has more advantages as the meaning is obvious.)</em></span>
|
||
</p><pre class="screen">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" title="12.1.5.2. Which Languages are currently supported?"><div class="titlepage"><div><div><h4 class="title"><a name="N16BEC"></a>12.1.5.2. Which Languages are currently supported?</h4></div></div><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" title="12.1.6. HTML Content in Items"><div class="titlepage"><div><div><h3 class="title"><a name="N16BF6"></a>12.1.6. HTML Content in Items</h3></div></div><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
|
||
chapter3.html
|
||
figure1.gif
|
||
figure2.jpg
|
||
figure3.gif
|
||
figure4.jpg
|
||
figure5.gif
|
||
figure6.gif</pre><p>The Bundle's primary bitstream field would point to the contents.html Bitstream, which we know is HTML (check the format MIME type) and so we know which to serve up first.</p><p>The HTML servlet employs a trick to serve up HTML documents without actually modifying the HTML or other files themselves. Say someone is looking at <code class="literal">contents.html</code> from the above example, the URL in their browser will look like this:</p><pre class="screen">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="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"><IMG SRC="images/figure1.gif"></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
|
||
^^^^^^^
|
||
Strip this</pre><p>BUT all the filenames (regardless of directory names) must be unique. For example, this wouldn't work:</p><pre class="screen">contents.html
|
||
chapter1.html
|
||
chapter2.html
|
||
chapter1_images/figure.gif
|
||
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" title="12.1.7. Thesis Blocking"><div class="titlepage"><div><div><h3 class="title"><a name="N16C70"></a>12.1.7. Thesis Blocking</h3></div></div><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" title="12.2. OAI-PMH Data Provider"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16C86"></a>12.2. <a name="docbook-application.html-oai"></a>OAI-PMH Data Provider</h2></div></div><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="ch12.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
|
||
</pre><p>It is this URL that should be registered with <a class="ulink" href="http://www.openarchives.org/" target="_top">www.openarchives.org</a>. Note that you can easily change the '<code class="literal">request</code>' portion of the URL by editing <code class="literal">[dspace-source]/etc/oai-web.xml</code> and rebuilding and deploying <code class="literal">oai.war</code>.</p><p>DSpace provides implementations of the OAICat interfaces <code class="literal">AbstractCatalog</code>, <code class="literal">RecordFactory</code> and <code class="literal">Crosswalk</code> that interface with the DSpace content management API and harvesting API (in the search subsystem).</p><p>Only the basic <code class="literal">oai_dc</code> unqualified Dublin Core metadata set export is enabled by default; this is particularly easy since all items have qualified Dublin Core metadata. When this metadata is harvested, the qualifiers are simply stripped; for example, <code class="literal">description.abstract</code> is exposed as unqualified <code class="literal">description</code>. The <code class="literal">description.provenance</code> field is hidden, as this contains private information about the submitter and workflow reviewers of the item, including their e-mail addresses. Additionally, to keep in line with OAI community practices, values of <code class="literal">contributor.author</code> are exposed as <code class="literal">creator</code> values.</p><p>Other metadata formats are supported as well, using other <code class="literal">Crosswalk</code> implementations; consult the <code class="literal">oaicat.properties</code> file described below. To enable a format, simply uncomment the lines beginning with <code class="literal">Crosswalks.*</code>. Multiple formats are allowed, and the current list includes, in addition to unqualified DC: MPEG DIDL, METS, MODS. There is also an incomplete, experimental qualified DC.</p><p>Note that the current simple DC implementation (<code class="literal">org.dspace.app.oai.OAIDCCrosswalk</code>) does not currently strip out any invalid XML characters that may be lying around in the data. If your database contains a DC value with, for example, some ASCII control codes (form feed etc.) this may cause OAI harvesters problems. This should rarely occur, however. XML entities (such as <code class="literal">></code>) are encoded (e.g. to <code class="literal">&gt;</code>)</p><p>In addition to the implementations of the OAICat interfaces, there are two configuration files relevant to OAI support:</p><div class="variablelist"><dl><dt><span class="term">
|
||
<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" title="12.2.1. Sets"><div class="titlepage"><div><div><h3 class="title"><a name="N16D45"></a>12.2.1. Sets</h3></div></div><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" title="12.2.2. Unique Identifier"><div class="titlepage"><div><div><h3 class="title"><a name="N16D54"></a>12.2.2. Unique Identifier</h3></div></div><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" title="12.2.3. Access control"><div class="titlepage"><div><div><h3 class="title"><a name="N16D80"></a>12.2.3. Access control</h3></div></div><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" title="12.2.4. Modification Date (OAI Date Stamp)"><div class="titlepage"><div><div><h3 class="title"><a name="N16D8A"></a>12.2.4. Modification Date (OAI Date Stamp)</h3></div></div><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" title="12.2.5. 'About' Information"><div class="titlepage"><div><div><h3 class="title"><a name="N16D90"></a>12.2.5. 'About' Information</h3></div></div><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" title="12.2.6. Deletions"><div class="titlepage"><div><div><h3 class="title"><a name="N16D96"></a>12.2.6. Deletions</h3></div></div><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" title="12.2.7. Flow Control (Resumption Tokens)"><div class="titlepage"><div><div><h3 class="title"><a name="N16DA5"></a>12.2.7. Flow Control (Resumption Tokens)</h3></div></div><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" title="12.3. DSpace Command Launcher"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="N16DE8"></a>12.3. <a name="docbook-application.html-command-launcher"></a>DSpace Command Launcher</h2></div></div><div></div></div><p>Introduced in Release 1.6, the DSpace Command Launcher brings together the various command and scripts into a standard-practice for running CLI runtime programs.</p><div class="section" title="12.3.1. Older Versions"><div class="titlepage"><div><div><h3 class="title"><a name="N16DF1"></a>12.3.1. Older Versions</h3></div></div><div></div></div><p>Prior to Release 1.6, there were various scripts written that masked a more manual approach to running CLI programs. The user had to issue <code class="literal">[dspace]/bin/dsrun</code> and then java class that ran that program. With release 1.5, scripts were written to mask the <code class="literal">[dspace]/bin/dsrun</code> command. We have left the java class in the System Administration section since it does have value for debugging purposes and for those who wish to learn about DSpace
|
||
programming or wish to customize the code at any time.</p></div><div class="section" title="12.3.2. Command Launcher Structure"><div class="titlepage"><div><div><h3 class="title"><a name="N16DFF"></a>12.3.2. Command Launcher Structure</h3></div></div><div></div></div><p>There are two components to the command launcher: the dspace script and the launcher.xml. The DSpace command calls a java class which in turn refers to <code class="literal">launcher.xml</code> that is stored in the <code class="literal">[dspace]/config</code> directory</p><p><code class="literal">launcher.xml</code> is made of several components:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="literal"><command></code> begins the stanza for a comand</p></li><li class="listitem"><p><code class="literal"><name></code><span class="emphasis"><em><code class="literal">name of command</code></em></span><code class="literal"></name></code> the name of the command that you would use.</p></li><li class="listitem"><p><code class="literal"><description></code><span class="emphasis"><em><code class="literal">the description of the command</code></em></span><code class="literal"></description></code></p></li><li class="listitem"><p><code class="literal"><step> </step></code> User arguments are parsed and tested.</p></li><li class="listitem"><p><code class="literal"><class></code><span class="emphasis"><em><code class="literal"><the java class that is being used to run the CLI program></code></em></span><code class="literal"></class></code></p></li></ul></div><p>Prior to release 1.5 if one wanted to regenerate the browse index, one would have to issue the following commands manually:</p><pre class="screen">[dspace]/bin/dsrun org.dspace.browse.IndexBrowse -f -r
|
||
[dspace]/bin/dsrun org.dspace.browse.ItemCounter
|
||
[dspace]/bin/dsrun org.dspace.search.DSIndexer</pre><p>In release 1.5 a script was written and in release 1.6 the command <code class="literal">[dspace]/bin/dspace index-init</code> replaces the script. The stanza from <code class="literal">launcher.xml</code> show us how one can build more commands if needed:</p><pre class="screen"><command>
|
||
<name>index-update</name>
|
||
<description>Update the search and browse indexes</description>
|
||
<step passuserargs="false">
|
||
<class>org.dspace.browse.IndexBrowse</class>
|
||
<argument>-i</argument>
|
||
</step>
|
||
<step passuserargs="false">
|
||
<class>org.dspace.browse.ItemCounter</class>
|
||
</step>
|
||
<step passuserargs="false">
|
||
<class>org.dspace.search.DSIndexer</class>
|
||
</step>
|
||
</command></pre><p>.</p></div></div></div><HR><p class="copyright">Copyright <20> 2002-2010
|
||
<a class="ulink" href="http://www.duraspace.org/" target="_top">The DuraSpace Foundation</a>
|
||
</p><div class="legalnotice" title="Legal Notice"><a name="N1001D"></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>
|
||
</a>
|
||
</p><p>Licensed under a Creative Commons Attribution 3.0 United States License</p></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch11.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="ch13.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%">Chapter 11. DSpace System Documentation: Architecture </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> Chapter 13. DSpace System Documentation: Business Logic Layer</td></tr></table></div></body></html> |