[open-ils-commits] [GIT] Evergreen ILS branch master updated. d8080c3df085ef97b11deb23a9c67f2a2cf82a59

Evergreen Git git at git.evergreen-ils.org
Mon Sep 24 17:17:54 EDT 2018


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Evergreen ILS".

The branch, master has been updated
       via  d8080c3df085ef97b11deb23a9c67f2a2cf82a59 (commit)
       via  1830cf6b7a2dc83f2f2a2b027f1e35cb4cd986a2 (commit)
       via  861a750946844bb8642addeba7ca1832c0f98639 (commit)
      from  25f60b4e7d9ba78cb96cd177659c8f82493287e2 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d8080c3df085ef97b11deb23a9c67f2a2cf82a59
Author: Remington Steed <rjs7 at calvin.edu>
Date:   Mon Sep 24 17:14:39 2018 -0400

    Docs: Add Upgrade Notes to release notes
    
    This commit copies relevant sections of the release notes into the
    Upgrade Notes section.
    
    A few paragraphs are also reformatted into lines of appropriate length.
    
    Signed-off-by: Remington Steed <rjs7 at calvin.edu>

diff --git a/docs/RELEASE_NOTES_3_2.adoc b/docs/RELEASE_NOTES_3_2.adoc
index bc37d72..4754197 100644
--- a/docs/RELEASE_NOTES_3_2.adoc
+++ b/docs/RELEASE_NOTES_3_2.adoc
@@ -6,7 +6,123 @@ Evergreen 3.2 Release Notes
 Upgrade notes
 -------------
 
-TODO
+Disabling of Legacy XUL Staff Client
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The legacy XUL staff client is no longer supported in Evergreen
+3.2.x and the server-side installation no longer supports a
+direct connection by a version XUL client by default.  *All
+users of Evergreen 3.2.x are strongly urged to complete their
+switch to the web staff client as part of upgrading to 3.2.x.*
+
+Evergreen administrators who for some reason continue to wish
+to deploy the XUL staff client can do so at their risk by
+supplying `STAFF_CLIENT_STAMP_ID` during the `make install` step
+and using `make_release` to create installers for the staff client.
+However, no community support will be provided for the XUL client.
+
+
+
+Acq Invoice Reports
+~~~~~~~~~~~~~~~~~~~
+
+Existing Acquisitions report templates that reference the invoice 'complete'
+field should be modified to check whether the new close_date field is NOT NULL
+instead.
+
+At deploy time, all invoices with a 'complete' value of TRUE will have their
+'close_date' field set to NOW.  A value is required, since this field is
+now the source of whether an invoice is open or closed.
+
+However, no values will be applied to the closed_by field for already closed
+invoices.
+
+
+Angular6 Base Application
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+System Admin Upgrade Notes
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Like the AngularJS application, Evergreen releases will come with all
+web browser staff client code pre-compiled.  Admins only need to add an
+Apache configuration change.
+
+Add the following stanza to /etc/apache2/eg_vhost.conf.
+
+[source,conf]
+--------------------------------------------------------------------------
+RewriteCond %{REQUEST_URI}  ^/eg2/
+RewriteCond %{REQUEST_URI}  !^/eg2/([a-z]{2}-[A-Z]{2})/
+RewriteRule ^/eg2/(.*) https://%{HTTP_HOST}/eg2/en-US/$1 [R=307,L]
+
+<Directory "/openils/var/web/eg2/en-US">
+    FallbackResource /eg2/en-US/index.html
+</Directory>
+--------------------------------------------------------------------------
+
+For multi-locale sites, see the bottom section of
+Open-ILS/examples/apache[_24]/eg_vhost.conf.in for a sample fr-CA
+configuration.  The section starts with "/eg2/ client setup and locale
+configuration"
+
+Developer Upgrade Notes
+^^^^^^^^^^^^^^^^^^^^^^^
+
+Developers building Angular code on existing installations need to update
+their version of NodeJS by re-running the -developer prereqs installer.
+
+[source,sh]
+--------------------------------------------------------------------------
+sudo make -f Open-ILS/src/extras/Makefile.install <osname>-developer
+--------------------------------------------------------------------------
+
+
+Asynchronous Vandelay Imports
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Users of NGINX as a reverse proxy may need to set a suitable
+`client_max_body_size` value in the NGINX configuration so that large
+MARC record uploads are not truncated. Note that this would have
+always been necessary, but since this feature allows larger files
+to be more reliably queued and imported, the need to set `client_max_body_size`
+became more apparent.
+
+
+Browser Client Settings & Preferences Stored on the Server
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+A new permission APPLY_WORKSTATION_SETTING has been added to control who
+may apply values to workstation settings.  Use something like the following
+to apply the permission to all staff accounts (mileage may vary):
+
+[source,sh]
+--------------------------------------------------------------------------
+INSERT INTO permission.grp_perm_map (grp, perm, depth)
+VALUES (
+    (SELECT id FROM permission.grp_tree WHERE name = 'Staff'), -- name may vary
+    (SELECT id FROM permission.perm_list WHERE code =
+'APPLY_WORKSTATION_SETTING'),
+    0 -- or 1, 2, etc.
+);
+--------------------------------------------------------------------------
+
+Workstation setting types matching values previously stored in the browser
+(via localStorage or Hatch) are created as part of this feature.  During
+upgrade, admins should consider whether any of these new setting types
+should be transferred to user and/or org unit settings instead.  Setting
+type changes can be made at any time, but when a setting type is deleted
+all of its data is deleted, so a change in type means re-applying the
+settings in the browser client.
+
+Values stored in the browser will automatically migrate to server settings
+as each setting is accessed in the browser client.  Once migrated, the
+in-browser copies are deleted.
+
+If a setting type does not exist where the browser expects one, the
+value is stored in-browser instead and a warning is issued in the console.
+
+
+
 
 New Features
 ------------
@@ -356,23 +472,54 @@ indicates how many autorenewals are available for a particular circulation.
 Emergency Closing Handler
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
-Staff are provided with interfaces and mechanisms to create library closings that, in addition to affecting future circulation and booking due dates, and hold shelf expirations, will automatically move existing circulation and booking due dates and hold shelf expiration times. This new functionality is conceptually described as Emergency Closings and business logic implementing it as the Emergency Closing Handler. It contains additions and adjustments to the user interface, business logic, and database layers. Access to this functionality is available through the Closed Dates Editor interface in the staff client which has been ported to AngularJS.
+Staff are provided with interfaces and mechanisms to create library closings
+that, in addition to affecting future circulation and booking due dates, and
+hold shelf expirations, will automatically move existing circulation and booking
+due dates and hold shelf expiration times. This new functionality is
+conceptually described as Emergency Closings and business logic implementing it
+as the Emergency Closing Handler. It contains additions and adjustments to the
+user interface, business logic, and database layers. Access to this
+functionality is available through the Closed Dates Editor interface in the
+staff client which has been ported to AngularJS.
 
 Overview
 ++++++++
 
-This development has created new business logic code to inspect, in real time, existing circulation, booking, and hold records, and modify such date and time stamps so that the circulation, booking, or hold will end in the same state it would have if the closing had existed at the time the circulation or booking occurred, or the hold was placed and captured. Of specific note, hourly loans will have their due date adjusted to be the end of the day following the closing.
+This development has created new business logic code to inspect, in real time,
+existing circulation, booking, and hold records, and modify such date and time
+stamps so that the circulation, booking, or hold will end in the same state it
+would have if the closing had existed at the time the circulation or booking
+occurred, or the hold was placed and captured. Of specific note, hourly loans
+will have their due date adjusted to be the end of the day following the
+closing.
 
-When the Emergency Closing is saved, any fines accrued during the closing may be voided, as settings dictate, with the exception of circulations that have been marked as LOST or LONG OVERDUE. That is, even for LOST and LONG OVERDUE circulations with due dates that fall within the Emergency Closing, no fine adjustment will be applied. Emergency Closing processing is permanent, and cannot be rolled back.
+When the Emergency Closing is saved, any fines accrued during the closing may be
+voided, as settings dictate, with the exception of circulations that have been
+marked as LOST or LONG OVERDUE. That is, even for LOST and LONG OVERDUE
+circulations with due dates that fall within the Emergency Closing, no fine
+adjustment will be applied. Emergency Closing processing is permanent, and
+cannot be rolled back.
 
-This functionality is explicitly initiated by staff action. If staff do not request an Emergency Closing, existing circulations, bookings, and holds will not be processed and adjusted. However, if staff request any Closing that starts nearer in time than the length of the longest circulation duration configured for use in the Evergreen instance they will be prompted with the option to create the closing as an Emergency Closing.
+This functionality is explicitly initiated by staff action. If staff do not
+request an Emergency Closing, existing circulations, bookings, and holds will
+not be processed and adjusted. However, if staff request any Closing that starts
+nearer in time than the length of the longest circulation duration configured
+for use in the Evergreen instance they will be prompted with the option to
+create the closing as an Emergency Closing.
 
-Action/Trigger hooks have been created for circulations and bookings that are adjusted by the Emergency Closing Handler. These will facilitate the creation of notifications to patrons that the due date has changed and to alert them to potential changes in accrued fines.
+Action/Trigger hooks have been created for circulations and bookings that are
+adjusted by the Emergency Closing Handler. These will facilitate the creation of
+notifications to patrons that the due date has changed and to alert them to
+potential changes in accrued fines.
 
-Booking start dates are explicitly ignored in this implementation. Because an Emergency Closing is, by its nature, an unexpected event, it will be up to staff to address any bookings which intersect with a new Emergency Closings. Reports can be used to identify booking start dates that overlap with a closing and that may require staff intervention.
+Booking start dates are explicitly ignored in this implementation. Because an
+Emergency Closing is, by its nature, an unexpected event, it will be up to staff
+to address any bookings which intersect with a new Emergency Closings. Reports
+can be used to identify booking start dates that overlap with a closing and that
+may require staff intervention.
 
-Staff requesting and Emergency Closing must have the new EMERGENCY_CLOSING permission.
-Some text describing the feature.
+Staff requesting and Emergency Closing must have the new EMERGENCY_CLOSING
+permission.  Some text describing the feature.
 
 
 
@@ -640,7 +787,7 @@ Additional information
 Developer notes
 +++++++++++++++
 
-This patch adds the the public catalog two routes that return JSON
+This patch adds to the public catalog two routes that return JSON
 rather than HTML:
 
 * `GET /eg/opac/api/mylist/add?record=45`
@@ -673,12 +820,10 @@ consumption.
 New class for searchbar when on the homepage
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-This adds the `.searchbar-home` class to the div that
-contains the searchbar when on the homepage.  This allows
-sites to customize the searchbar differently on the
-homepage than in other places the
-search bar appears (for example, offering a large,
-Google-style search bar on the homepage only).
+This adds the `.searchbar-home` class to the div that contains the searchbar
+when on the homepage.  This allows sites to customize the searchbar differently
+on the homepage than in other places the search bar appears (for example,
+offering a large, Google-style search bar on the homepage only).
 
 
 Username Login Hint

commit 1830cf6b7a2dc83f2f2a2b027f1e35cb4cd986a2
Author: Remington Steed <rjs7 at calvin.edu>
Date:   Mon Sep 24 15:53:04 2018 -0400

    Update Release Notes for 3.2-rc
    
    Add new release notes. Also, slight reorganization to the
    acknowledgements section (move organizations to appropriate section, fix
    sorting of COOL, use consistent name for BC Libraries).
    
    Signed-off-by: Remington Steed <rjs7 at calvin.edu>

diff --git a/docs/RELEASE_NOTES_3_2.adoc b/docs/RELEASE_NOTES_3_2.adoc
index d0a6765..bc37d72 100644
--- a/docs/RELEASE_NOTES_3_2.adoc
+++ b/docs/RELEASE_NOTES_3_2.adoc
@@ -71,6 +71,36 @@ Patron Acquisitions Requests
 The existing interface for staff-mediated patron acquisition requests has been replaced in the web staff client with a re-implementation written in AngularJS, with some minor bug fixes (including access from the Patron interface) and other improvements.
 
 
+
+Administration
+~~~~~~~~~~~~~~
+
+Hold Targeter Script has been Replaced
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The original hold_targeter.pl script has been renamed to
+"hold_targeter_legacy.pl", and the new-style hold targeting
+script has been renamed to "hold_targeter.pl".  Administrators
+will want to change their crontab files to reflect this.
+
+.Previous Syntax
+[source,bash]
+---------------------------------------------------------------------
+-*/15 * * * *   . ~/.bashrc && $EG_BIN_DIR/hold_targeter.pl $SRF_CORE
+---------------------------------------------------------------------
+
+.New Syntax
+[source,bash]
+-----------------------------------------------------------------------------------
+-*/15 * * * *   . ~/.bashrc && $EG_BIN_DIR/hold_targeter.pl --osrf-config
+$SRF_CORE
+-----------------------------------------------------------------------------------
+
+The sample crontab file at `Open-ILS/examples/crontab.example` reflects
+this change.
+
+
+
 Architecture
 ~~~~~~~~~~~~
 
@@ -536,6 +566,21 @@ If a setting type does not exist where the browser expects one, the
 value is stored in-browser instead and a warning is issued in the console.
 
 
+More consistent terminology in the client
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Terminology has been updated in the staff client so that we consistently use
+the same name to describe the same thing. The following updates have been made:
+
+  * The term 'item' is now consistently used to describe the barcoded entity
+that had been previously been called both an 'item' and a 'copy'. As a result,
+we now use the terms 'item buckets', 'item tags', and 'item alerts'.
+  * The term 'volume' is no longer used in the client, with the exception of
+serials, where the term is used to describe serial volumes. The term 'call
+number' will replace volume in most other places.
+  *'Holdings' is a more general term used to describe a combination of items
+and call numbers.
+  * The term 'Shelving Location' is used consistently in favor of 'Copy
+Location.'
 
 
 
@@ -651,7 +696,8 @@ The Evergreen project would like to acknowledge the following
 organizations that commissioned developments in this release of
 Evergreen:
 
-* BC Library Cooperative 
+* BC Libraries Cooperative
+* Consortium Of Ohio Libraries
 * CW MARS
 * Georgia Public Library Service
 * Indiana State Library
@@ -659,7 +705,6 @@ Evergreen:
 * MassLNC
 * North Texas Library Consortium
 * Northwest Regional Library
-* Consortium of Ohio Libraries
 * Pennsylvania Integrated Library System
 * South Carolina State Library
 
@@ -669,7 +714,6 @@ Evergreen:
 
 * Felicia Beaudry
 * Jason Boyer
-* BC Libraries Cooperative
 * Andrea Buntz Neiman
 * Eva Cerninakova
 * Galen Charlton
@@ -679,7 +723,6 @@ Evergreen:
 * Jason Etheridge
 * Lynn Floyd
 * Jeff Godin
-* Government of Manitoba
 * Blake Graham-Henderson
 * Francisco J Guel-Mendoza
 * Kyle Huckins
@@ -702,10 +745,11 @@ Evergreen:
 We also thank the following organizations whose employees contributed
 patches:
 
-* British Columbia Libraries Cooperative
+* BC Libraries Cooperative
 * Calvin College
 * Catalyte
 * Equinox Open Library Initiative
+* Government of Manitoba
 * Kenton County Public Library
 * King County Library System
 * Linn-Benton Community College

commit 861a750946844bb8642addeba7ca1832c0f98639
Author: Remington Steed <rjs7 at calvin.edu>
Date:   Mon Sep 24 15:15:46 2018 -0400

    Docs: Fix two minor errors in docs
    
      - Fix an AsciiDoc heading syntax error
      - Fix a grammatical error (repeated "the")
    
    Signed-off-by: Remington Steed <rjs7 at calvin.edu>

diff --git a/docs/RELEASE_NOTES_3_2.adoc b/docs/RELEASE_NOTES_3_2.adoc
index 7faa19b..d0a6765 100644
--- a/docs/RELEASE_NOTES_3_2.adoc
+++ b/docs/RELEASE_NOTES_3_2.adoc
@@ -16,7 +16,7 @@ Acquisitions
 ~~~~~~~~~~~~
 
 Auto-Cancel Line items When All Copies Are Canceled
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 When a copy (line item detail) is canceled through the Acquisitions interface, 
 the parent line item is also canceled if all copies for that line item are also 
 canceled.  The cancel reason given will come from:
diff --git a/docs/acquisitions/selection_lists_po.adoc b/docs/acquisitions/selection_lists_po.adoc
index 54af0eb..d714128 100644
--- a/docs/acquisitions/selection_lists_po.adoc
+++ b/docs/acquisitions/selection_lists_po.adoc
@@ -211,7 +211,7 @@ Cancel/delay reasons now appear on the worksheet and the printable purchase orde
 ========================
 When all the copies of a line item are canceled through the Acquisitions interface,
 the parent lineitem is also canceled. The cancel reason will be calculated based
-on the settings of the 
+on the settings of:
   
 . The cancel reason for the last copy to be canceled copy if the cancel reason's
 _Keep Debits_ setting is true.

-----------------------------------------------------------------------

Summary of changes:
 docs/RELEASE_NOTES_3_2.adoc               |  233 ++++++++++++++++++++++++++---
 docs/acquisitions/selection_lists_po.adoc |    2 +-
 2 files changed, 212 insertions(+), 23 deletions(-)


hooks/post-receive
-- 
Evergreen ILS


More information about the open-ils-commits mailing list