This commit is contained in:
Jeffrey Trimble
2010-06-13 12:04:52 +00:00
parent 74ee897cfd
commit 5bc0ebde25
3 changed files with 15 additions and 15 deletions

View File

@@ -22,15 +22,15 @@
<book> <book>
<bookinfo> <bookinfo>
<title>DSpace Manual</title> <title>DSpace Manual</title>
<subtitle>Release 1.6.1</subtitle> <subtitle>Release 1.6.2</subtitle>
<author> <author>
<surname>DuraSpace</surname> <surname>DuraSpace</surname>
<affiliation> <affiliation>
<address><email>webmaster@dspace.org</email></address> <address><email>webmaster@dspace.org</email></address>
</affiliation> </affiliation>
</author> </author>
<edition>1.6.1</edition> <edition>1.6.2</edition>
<pubdate>2010-05-21 12:00:00 EST</pubdate> <pubdate>2010-06-13 08:00:00 EST</pubdate>
<copyright> <copyright>
<year>2002-2010</year> <year>2002-2010</year>
<holder> <holder>
@@ -51,8 +51,8 @@
</legalnotice> </legalnotice>
<revhistory> <revhistory>
<revision> <revision>
<revnumber>Version 1.6.1 </revnumber> <revnumber>Version 1.6.2 </revnumber>
<date>This text generated: 2010-05-21 12:00:00 EST EST</date> <date>This text generated: 2010-06-13 08:00:00 EST EST</date>
<authorinitials>JAT</authorinitials> <authorinitials>JAT</authorinitials>
</revision> </revision>
</revhistory> </revhistory>
@@ -63,8 +63,8 @@
<preface> <preface>
<title>Preface</title> <title>Preface</title>
<para/> <para/>
<para>Welcome to Release 1.6.1. This is a "fix" release. The committers have volunteered many hours to fix, re-write and contribute new software code for this release. Documentation has been updated. No new features have been added to this release.</para> <para>Welcome to Release 1.6.2. This is a "fix" release. The committers have volunteered many hours to fix, re-write and contribute new software code for this release. Documentation has been updated. No new features have been added to this release.</para>
<para>The following is a list of the new features included (not an exhaustive list) for release 1.6.0 and are also contained in 1.6.1:</para> <para>The following is a list of the new features included (not an exhaustive list) for release 1.6.0 and are also contained in 1.6.2:</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para>SOLR Statistics.</para> <para>SOLR Statistics.</para>

View File

@@ -652,7 +652,7 @@ $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keysize
<section remap="h4"> <section remap="h4">
<title>Updating Existing Handle Prefixes</title> <title>Updating Existing Handle Prefixes</title>
<para>If you need to update the handle prefix on items created before the CNRI registration process you can run the <literal>[dspace]/bin/update-handle-prefix script</literal>. 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:</para> <para>If you need to update the handle prefix on items created before the CNRI registration process you can run the <literal>[dspace]/bin/update-handle-prefix script</literal>. 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:</para>
<screen>[dspace]/bin/update-handle-prefix 123456789 1303 <screen>[dspace]/bin/dspace update-handle-prefix 123456789 1303
</screen> </screen>
<para>This script 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.</para> <para>This script 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.</para>
</section> </section>

View File

@@ -6,7 +6,7 @@
<para>It is always recommended that when performing an upgrade that the user should use a Development or Test instance or server in order to minimize downtime. You should note any problems you have encountered (and also how to resolve them) before attempting to upgrade your production instance or server. It also gives you a chance to &quot;practice&quot; at the upgrade. (And practice makes perfect.)</para> <para>It is always recommended that when performing an upgrade that the user should use a Development or Test instance or server in order to minimize downtime. You should note any problems you have encountered (and also how to resolve them) before attempting to upgrade your production instance or server. It also gives you a chance to &quot;practice&quot; at the upgrade. (And practice makes perfect.)</para>
</warning> </warning>
<section remap="h2"> <section remap="h2">
<title><anchor id="docbook-update-html-16_161" xreflabel="Upgrading from 1.6 to 1.6.1"/>Upgrading from 1.6 to 1.6.1</title> <title><anchor id="docbook-update-html-16_161" xreflabel="Upgrading from 1.6 to 1.6.1"/>Upgrading from 1.6 to 1.6.x</title>
<para>In the notes below <literal>[dspace]</literal> refers to the install directory for your existing DSpace installation, and <literal>[dspace-source]</literal> to the source directory for DSpace 1.6.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</para> <para>In the notes below <literal>[dspace]</literal> refers to the install directory for your existing DSpace installation, and <literal>[dspace-source]</literal> to the source directory for DSpace 1.6.1. Whenever you see these path references, be sure to replace them with the actual path names on your local system.</para>
<orderedlist> <orderedlist>
<listitem> <listitem>
@@ -55,7 +55,7 @@ ant -Dconfig=[dspace]/config/dspace.cfg update</screen>
<listitem> <listitem>
<para><emphasis role="bold">Run Registry Format Update for CC License.</emphasis></para> <para><emphasis role="bold">Run Registry Format Update for CC License.</emphasis></para>
<para>Creative Commons licenses have been assigned the wrong mime-type in past versions of DSpace. Even if you are not currently using CC Licenses, you should update your Bitstream Format Registry to include a new entry with the proper mime-type. To update your registry, run the following command:</para> <para>Creative Commons licenses have been assigned the wrong mime-type in past versions of DSpace. Even if you are not currently using CC Licenses, you should update your Bitstream Format Registry to include a new entry with the proper mime-type. To update your registry, run the following command:</para>
<para><literal>[dspace]/bin/dsrun org.dspace.administrator.RegistryLoader -b bitstream [dspace-source]/dspace/etc/upgrades/15-16/new-bitstream-formats.xml</literal></para> <para><literal>dspace]/bin/dspace registry-loader -bitstream [dspace]/etc/upgrades/15-16/new-bitstream-formats.xml</literal></para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">Update the Database.</emphasis></para> <para><emphasis role="bold">Update the Database.</emphasis></para>
@@ -628,7 +628,7 @@ mvn -U clean package</screen>
<listitem> <listitem>
<para><emphasis role="bold">Update Registry for the CC License.</emphasis></para> <para><emphasis role="bold">Update Registry for the CC License.</emphasis></para>
<para>If you use the CC License, an incorrect mime-type type is being assigned. You will need to run the following step:</para> <para>If you use the CC License, an incorrect mime-type type is being assigned. You will need to run the following step:</para>
<para><literal>[dspace]/bin/dsrun org.dspace.administrator.RegistryLoader -b bitstream [dspace-source]/dspace/etc/upgrades/15-16/new-bitstream-formats.xml</literal></para> <para><literal>dspace]/bin/dspace registry-loader -bitstream [dspace]/etc/upgrades/15-16/new-bitstream-formats.xml </literal></para>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">Update the database</emphasis>. The database schema needs to be updated to accommodate changes to the database. SQL files contain the relevant updates are provided. Please note that if you have made any local customizations to the database schema, you should consult these updates and make sure they will work for you.</para> <para><emphasis role="bold">Update the database</emphasis>. The database schema needs to be updated to accommodate changes to the database. SQL files contain the relevant updates are provided. Please note that if you have made any local customizations to the database schema, you should consult these updates and make sure they will work for you.</para>
@@ -683,8 +683,8 @@ ant -Dconfig=[dspace]/config/dspace.cfg update</screen>
</listitem> </listitem>
<listitem> <listitem>
<para><emphasis role="bold">Rolling Log Appender Upgrade</emphasis>. You will want to upgrade your logs to the new format to use the SOLR Statistics now included with DSpace. While the commands for this are found in Chapter 8, here is the steps needed to be performed.</para> <para><emphasis role="bold">Rolling Log Appender Upgrade</emphasis>. You will want to upgrade your logs to the new format to use the SOLR Statistics now included with DSpace. While the commands for this are found in Chapter 8, here is the steps needed to be performed.</para>
<screen>[dspace]/bin/dspace stat-log-converter -i <emphasis>input file name</emphasis> -o <emphasis>output file name</emphasis> -m <emphasis>(if you have more than one</emphasis> dspace.log<emphasis> file)</emphasis> <screen>[dspace]/bin/dspace stats-log-converter -i <emphasis>input file name</emphasis> -o <emphasis>output file name</emphasis> -m <emphasis>(if you have more than one</emphasis> dspace.log<emphasis> file)</emphasis>
[dspace]/bin/dspace stat-log-importer -i <emphasis>input file name (probably the output name from above)</emphasis> -m [dspace]/bin/dspace stats-log-importer -i <emphasis>input file name (probably the output name from above)</emphasis> -m
</screen> </screen>
<para>The user is highly recommend to see Section 8.14 <link linkend="docbook-sys_admin.html-log-converter">DSpace Log Converter</link>.</para> <para>The user is highly recommend to see Section 8.14 <link linkend="docbook-sys_admin.html-log-converter">DSpace Log Converter</link>.</para>
</listitem> </listitem>