Differences

This shows you the differences between two versions of the page.

--- en:release:3.09_release_notes [2018/12/13 05:44] – [Content Encoding Error when visiting the local solr servlet page] anupama
+++ en:release:3.09_release_notes [2019/03/19 05:50] – [GLI Java Web Start application (replacement for GLI Applet) - Additional Steps] anupama
@@ Line 94: / Line 94: @@
   * **the recommended "//PDFv2Plugin//"**, which will contain the new functionality and should handle a greater range of PDF versions, including the newer ones that the old ''pdftohtml'' (now used by PDFv1Plugin) can't handle. The "PDFBox conversion" facility has been moved to the new PDFv2Plugin, but is now invisible: it will be triggered automatically depending on the "convert_to" format that you select when you Configure the PDFv2Plugin. PDFv2Plugin also uses additional conversion tools in the background to support the additional output formats.
-For the eventual 3.09 release, the old PDFPlugin that you're familiar with, the one which has the ''pdfbox_conversion'' flag but also makes use of the old ''pdftohtml'' tool behind the scenes, will hang around with a deprecated warning, to allow people to port over their collections and keep rebuilding with the old settings or to rebuild their collection with one of the 2 new PDF plugins. However, **new collections will have the //PDFv2Plugin// in the Document Plugins pipeline by default, for GS3, and PDFv1Plugin by default for GS2, since GS2 doesn't come with the PDFbox extension out of the box.** So GS2 users will have to manually add in PDFv2Plugin in place of PDFv1Plugin for new collections, after setting up the pdfbox extension. But then it should work as usual.
+For the eventual 3.09 release, the old PDFPlugin that you're familiar with, the one which has the ''pdfbox_conversion'' flag but also makes use of the old ''pdftohtml'' tool behind the scenes, will hang around with a deprecated warning, to allow people to port over their collections and keep rebuilding with the old settings or to rebuild their collection with one of the 2 new PDF plugins. However, **new collections will have the //PDFv2Plugin// in the Document Plugins pipeline by default for GS3, and PDFv1Plugin by default for GS2, since GS2 doesn't come with the PDFbox extension out of the box.** So GS2 users will have to manually add in PDFv2Plugin in place of PDFv1Plugin for new collections, after setting up the pdfbox extension. But then it should work as usual.
@@ Line 231: / Line 231: @@
 ===GLI Java Web Start application (replacement for GLI Applet) - Additional Steps===
-Many browsers have stopped supporting Java applets, while Microsoft's Internet Explorer, and perhaps Microsoft Edge, still support it. For this reason, 3.09's GLI is now no longer provided as an applet, but has been converted into a Java Web Start application.
+Many browsers have stopped supporting Java applets including Microsoft Edge, though Microsoft's Internet Explorer still supported it. For this reason, 3.09's GLI is now no longer provided as an applet, but has been converted into a Java Web Start application.
 Instructions for using the GLI Java Web Start, which works over the JNLP protocol, are below.
@@ Line 243: / Line 243: @@
   - You need to associate JNLP files with Java Web Start (''jre/bin/javaws'').
       * On Windows, create the association in the usual way: when you first access the GLI Web Start application through Greenstone, a JNLP file called "GLIappWebStart.jnlp" will be offered for launching or download. If JavaWS is not already the default application to open JNLP files with, rightclick on the downloaded GLIappWebStart.jnlp file and choose ''Launch/Open with ...''. Browse to your Greenstone3's ''packages/jre/bin/javaws.exe'' or any installed Java's ''jre/bin/javaws.exe'' to use Java's Web Start application as the launcher.
-      * For Linux, create a file with ''.desktop'' extension (e.g. "javawebstart.desktop") containing the following and save this file into ''~/.local/share/applications'':\\ <code># This file makes Ubuntu associate .jnlp files with Java Web Start (javaws)
+      * For Linux, create a file with ''.desktop'' extension (e.g. "javawebstart.desktop") containing the following, **edit the path to javaws**, and save this file into ''~/.local/share/applications'':\\ <code># This file makes Ubuntu associate .jnlp files with Java Web Start (javaws)
 # This file should be adjusted and then copied into ~/.local/share/applications
 # as a file with .desktop extension, e.g. javawebstart.desktop
@@ Line 251: / Line 251: @@
 Name=Java 7 Web Start
 Comment=Java 7 Web Start
-Exec=/home/greenstone/Desktop/linux/jre/bin/javaws %u
+Exec=/EDIT-THIS-PATH-TO-YOUR-JAVA-JRE/bin/javaws %u
 Terminal=false
 Type=Application
@@ Line 258: / Line 258: @@
 MimeType=application/x-java-jnlp-file;
 </code>
-  - Launch the Java Control Panel by running ''jre/bin/javacpl.exe'' on Windows or ''jre/bin/ControlPanel'' on Linux. (GS3 binaries now include a JRE in the ''packages'' folder if you want to use the bundled JRE.) In the Java Control Panel, go to the ''Security'' tab, set Security level to ''High'' if not already set. Click ''Edit Site List'', and then press ''Add'' to add the //host:port// that the GS3 will run on. Remember, to be accessible to the outside world, the host can't be "localhost", but would be the hostname of your machine or public IP.
+  - Launch the Java Control Panel by running ''jre/bin/javacpl.exe'' on Windows, or ''jre/bin/jcontrol'' (formerly jre/bin/ControlPanel) on Linux. (GS3 binaries now include a JRE in the ''packages'' folder if you want to use the bundled JRE.) In the Java Control Panel, go to the ''Security'' tab, set Security level to ''High'' if not already set. Click ''Edit Site List'', and then press ''Add'' to add the //host:port// that the GS3 will run on. Remember, to be accessible to the outside world, the host can't be "localhost", but would be the hostname of your machine or public IP.
-  - Once the GS3 code is compiled up, start up the GS3 web server and visit your DL library home page, ''http://[hostname]:8383/greenstone3/library''.
+  - Make the GLI link on the home page active: Open web/interfaces/default/transform/pages/home.xsl for editing, find the line <code>
-  - Since you have set up the JNLP file association in a previous step, you can now click on the "The Librarian Interface" link and your browser should offer to save or launch a file called ''GLIapplet.jnlp''. If the browser is able to successfully launch it, Java Web Start will be used to run the GLI application indicated by the JNLP file. If launching through the browser is not possible, then choose to save the JNLP file. It will download the file to a temporary user area (like C:\Users\<user>\AppData\Local\Temp on windows). And then you can rightclick on the downloaded GLIappWebStart.jnlp file, to launch it with the Java Web Start program you already associated with this file type.
+<!--<gslib:libraryInterfaceLink/><br/><br/>-->
+</code> and remove the comments. i.e. change it to <code>
+<gslib:libraryInterfaceLink/><br/><br/>
+</code>
+  - (Re)Start the GS3 web server and visit your DL library home page, ''http://[hostname]:8383/greenstone3/library''.
+  - Since you have set up the JNLP file association in a previous step, you can now click on the "The Librarian Interface" link and your browser should offer to save or launch a file called ''GLIappWebStart.jnlp''. Click ''Open With'' and in the dropdown box beside it, one of the launcher applications, at least on Windows, should be the "Java(TM) Web Start Launcher" application (javaws.exe) that you associated with .jnlp file extensions. Choose that application as the launcher. If the browser is able to successfully launch ''GLIappWebStart.jnlp'', then Java Web Start will be used to run the GLI application indicated by the JNLP file. If launching through the browser is not possible, for example, if the launcher application is not listed, as may happen on Linux machines, then choose to save the JNLP file. It will download the file to a temporary user area (like C:\Users\<user>\AppData\Local\Temp on windows). And then you can rightclick on the downloaded GLIappWebStart.jnlp file, to launch it with the Java Web Start program you already associated with this file type. This way should work on both Linux and Windows.
   - After authorising the GLI to run, the JNLP version of the GLI Applet will eventually run and behave like the usual client-GLI (and like the old GLI applet) from this point onward.
@@ Line 278: / Line 283: @@
   * Better way to run processes from GLI will avoid some occasional and unexpected errors when GLI runs perl scripts
   * Bug fixes to file locking issues on Windows when using Lucene as indexer
-  * Patch to SOLR extension to circumvent SIGPIPE errors on large collections
+  * **SOLR updates and bugfixes:**
+    * Patch to SOLR extension to circumvent SIGPIPE errors on large collections
+    * fixed bug where multiple metadata values for a single field were concatenated into a single facet term
+    * fixed some/all search handling
+    * Russian morphology analyzer replaced by more efficient version.
+    * Added russian morphology analyzer configuration into solr-jdbm-demo collection
+    * Standard SOLR highlighter replaced with the faster FastVectorHighlighter
   * Patches to perl code upgrading perl syntax to work with newer versions of perl
+  * GLI updates:
+    * The GLI Applet has been converted to a Java WebStart Application. Java Web Start not supported from Java 9 or onwards. To use the JRE bundled with your Greenstone, ensure no custom installed System Java is in the environment.
+    * GEMS can now launch in languages other than English
 ===== IMPORTANT information =====
@@ Line 428: / Line 442: @@
 ===== Updated Translations =====
-Thanks to the following people for new and updated translations since 3.09:
+Thanks to the following people for new and updated translations since 3.08:
+  *Lavji Zala for Gujarati translations