Differences

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

--- en:release:3.12_release_notes [2025/06/11 09:45] – old revision restored (2025/06/11 09:20) anupama
+++ en:release:3.12_release_notes [2025/06/27 01:55] (current) – kjdon
@@ Line 45: / Line 45: @@
 ===Windows Notes ===
-  *  There is increased security for downloaded binary installers from newer versions of Windows 10 onwards.
+  *  There is increased security for downloaded binary installers from newer versions of Windows 10 onwards.\\ After double clicking on the binary, you may first see Windows pop up a blue dialog ensuring you approve the installation. If you see the blue popup, click //more info// and then the button //Run anyway// that appears. Eventually, the Green splash screen of the installer should appear.
-After double clicking on the binary, you may first see Windows pop up a blue dialog ensuring you approve the installation. If you see the blue popup, click <i>more info<i> and then the button <i>Run anyway</i> that appears. Eventually, the Green splash screen of the installer should appear.
   *  For slightly older versions of Windows 10, the procedure may be different. After double-clicking, if the green installer splash screen doesn't appear after a few seconds, then right click on the installer executable, choose Properties, go to the General tab and at the bottom (in the Security section) look for a tick box labelled Unblock and tick this.
@@ Line 95: / Line 94: @@
 ===== Important Changes and Bug Fixes for 3.12 =====
-  * **Tomcat Upgrade:** Tomcat has been upgraded to 8.5.99. This allows the specification of partitioned SameSite=none Cookies. This is necessary if you are running greenstone in an iframe.
+  * **Tomcat Upgrade:** Tomcat has been upgraded to 8.5.99. This gives a few optimisations, and allows the specification of partitioned SameSite=none Cookies. This is necessary if you are running greenstone in an iframe.
-Edit resources/tomcat/greenstone3.xml.in and uncomment the relevant CookieProcessor line.
+    * To use Greenstone in an iframe: Edit resources/tomcat/greenstone3.xml.in and uncomment the relevant CookieProcessor line.
+    * See the [[en:user_advanced:gs3_server|Greenstone 3 Tomcat server]] page for more details about Tomcat and some configuration options.
   * GS3.12 continues to require a minimum Java version of 1.8, which is also the version that continues to be bundled in the releases. See also [[#java_80362_issues| notes about Java 8 update 362]].
-  * **GLI Changes: the Files tab.**
+  * **GLI Changes: the Files tab.** Added mainly to support Webswing GLI users, the Files tab gives a view of the entire collection - unlike the Gather tab, which just shows the import folder. Using the Files tab, a user can add resources, xsl files, javascript etc to their collection. Previously this would have required logging in to the server and uploading files.
   * **Collage and Phind applets now webswing applications:** support for applets was discontinued by the popular web browsers. The useful applets //Phind// and //Collage// are now back and available for use again, having being ported as webswing applications.
@@ Line 106: / Line 106: @@
   * **perl-with-cpan bundled:** perl 5.32.1 (5.32.1.1 on windows, 32 bit) is now bundled with Greenstone 3.12 and includes specific cpan libraries that Greenstone makes use of. Greenstone's bundled perl-with-cpan can be found in your GS3.12 installation's ''bin/darwin/perl'' for Mac, ''bin/linux/perl'' for Linux and in ''bin/windows/strawberry-perl/perl'' for windows.
+  * **-metadata_mapping_file option for plugins:** - using a set of rules specified in a csv file, a plugin can generate new metadata values through manipulation of existing metadata. See greenstone3/gs2build/etc/metadata_mapping_file.csv for a sample file. This is available for all plugins - set the -metadata_mapping_file option to the name of a CSV files of rules. This file can be located in greenstone3/gs2build/etc (available for all collections) or in a collection's etc folder (just for that collection)
 ===== Updated Translations =====
@@ Line 112: / Line 113: @@
   * Tigran Zargaryan for Armenian translations
-  * Diego Spano for Spanich translations
+  * Diego Spano for Spanish translations
+  * Julian Fox for Italian translations
+  * Lavji Zala for Gujarati translations
+  * Upcoming: John Rose, Emmanuel Ngoi, Yvan Arnaud and Sandraghassen Subbaraya Pillai for French translations
@@ Line 177: / Line 181: @@
 ==== Useful information ====
-  * To convert a collection's ''collect.cfg'' file to its GS3 equivalent, see [[en:user:gs2_to_gs3#using_a_remote_greenstone_server|here]] for details.
+  * To convert a collection's ''collect.cfg'' file to its GS3 equivalent, see [[en:user:gs2_to_gs3|here]] for details.
   * When you've built a collection of documents, you may discover that there appears to be a copy of all these documents in the collection's //import//, //archives// and //index// subfolders and wonder whether Greenstone could really be so inefficient with disk space as to keep 3 copies of everything. As it happens though, Greenstone uses **hard-links** both on Linux and **Windows**, in order to keep just one set of your documents. Then it simply hardlinks to these, instead of making copies. By default, Windows doesn't show you when files on your filesystem are hard-linked. If you choose to install the Windows extension application [[http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html|Link Shell Extension (LSE)]], it will put red arrows on files that are hard linked.