[open-ils-commits] [GIT] Evergreen ILS branch rel_2_10 updated. fbde8557841828132e266468a1a99ec8b3b448bd

Evergreen Git git at git.evergreen-ils.org
Thu Mar 3 15:09:02 EST 2016


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, rel_2_10 has been updated
       via  fbde8557841828132e266468a1a99ec8b3b448bd (commit)
      from  595d00f74757dcd1a4bcb4c2b393bdc7a82c5497 (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 fbde8557841828132e266468a1a99ec8b3b448bd
Author: Galen Charlton <gmc at esilibrary.com>
Date:   Wed Mar 2 21:55:03 2016 -0500

    clear slate of release notes for new features
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>

diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq-li-paid-label.txt b/docs/RELEASE_NOTES_NEXT/Acquisitions/acq-li-paid-label.txt
deleted file mode 100644
index 231cd07..0000000
--- a/docs/RELEASE_NOTES_NEXT/Acquisitions/acq-li-paid-label.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-PO Lineitem "paid" label
-^^^^^^^^^^^^^^^^^^^^^^^^
-A new "paid" label appears along the bottom of each lineitem in the PO 
-display when every non-canceled copy on the lineitem has been invoiced.
diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/debits-paid-on-invoice-close.adoc b/docs/RELEASE_NOTES_NEXT/Acquisitions/debits-paid-on-invoice-close.adoc
deleted file mode 100644
index 23ea9e7..0000000
--- a/docs/RELEASE_NOTES_NEXT/Acquisitions/debits-paid-on-invoice-close.adoc
+++ /dev/null
@@ -1,8 +0,0 @@
-Disencumber Funds on Invoice Close
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Fund debits linked to an invoice are now marked as paid (encumbrance=false)
-when the invoice is marked as closed/complete instead of at invoice create
-time.  This is particularly useful for EDI invoices which may be 
-created well in advance of receipt and payment.
-
diff --git a/docs/RELEASE_NOTES_NEXT/Acquisitions/po-actions-selector.adoc b/docs/RELEASE_NOTES_NEXT/Acquisitions/po-actions-selector.adoc
deleted file mode 100644
index 4602acf..0000000
--- a/docs/RELEASE_NOTES_NEXT/Acquisitions/po-actions-selector.adoc
+++ /dev/null
@@ -1,9 +0,0 @@
-PO Actions Selector Always Visible
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The actions selector is now always visible in the purchase order view,
-even when no lineitems exist.  With this, users can print PO's that
-only contain direct charges.
-
-The custom "Add Brief Record" button is no longer present, since the
-same action is accessible via the now-visible selector.
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/DB_Application_Name_Option.adoc b/docs/RELEASE_NOTES_NEXT/Administration/DB_Application_Name_Option.adoc
deleted file mode 100644
index 640fa96..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/DB_Application_Name_Option.adoc
+++ /dev/null
@@ -1,8 +0,0 @@
-Set application name when connecting to database
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The services that connect directly to the PostgreSQL database
-(and Clark Kent) now look for an application_name parameter
-as part of the database login credentials specified in
-`opensrf.xml`.  If present, the value is used to set the
-application name Pg connection value; this in turn shows up in
-the Postgres `pg_stat_activity` table and Pg's logs.
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/In_AT_telephony_configuration.adoc b/docs/RELEASE_NOTES_NEXT/Administration/In_AT_telephony_configuration.adoc
deleted file mode 100644
index 76e86ad..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/In_AT_telephony_configuration.adoc
+++ /dev/null
@@ -1,39 +0,0 @@
-Configure multiple telephony servers via Action/Trigger
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-If you are using the AstCall Action/Trigger reactor
-to generate callfiles to send to an Asterisk server, until
-now the only place to specify the relevant configuration
-was in `opensrf.xml`. However, this restricted an Evergreen
-consortium to using only one Asterisk instance.
-
-Now, the telephony parameters can also be specified as 
-A/T event parameters, allowing per-library configuration.
-
-.Telephony parameters
-|===
-| Name | Example value
-
-| enabled
-| 0
-
-| driver
-| "SIP"
-
-| channels
-| ["Zap/1", "Zap/2", "IAX/user:secret at widgets.biz"]
-
-| host
-| "localhost"
-
-| port
-| "10080"
-
-| user
-| "evergreen"
-
-| pw
-| "evergreen"
-
-| callfile_lines
-| ["MaxRetries: 3", "RetryTime: 60", "WaitTime: 30", "Archive: 1", "Extension: 10"]
-|===
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/NewPatronNotice.txt b/docs/RELEASE_NOTES_NEXT/Administration/NewPatronNotice.txt
deleted file mode 100644
index 4606e99..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/NewPatronNotice.txt
+++ /dev/null
@@ -1,15 +0,0 @@
-New Patron Action Trigger Notice
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-A new Action Trigger event definition ("New User Created Welcome Notice") 
-has been added that will allow you to send a notice after a new patron has 
-been created, based on the actor.usr create-date field.
-
-This notice can be used for various tasks.
-
-  * Sending a welcome email to new patrons to market Library services.
-  * Confirm that a new patron email address is correct.
-  * Generate postal notices to send a welcome packet to new patrons.
-
-Enable this event in the staff client at *Admin* -> *Local Administration* 
--> *Notifications / Action Triggers*.
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/drop-cc-columns.txt b/docs/RELEASE_NOTES_NEXT/Administration/drop-cc-columns.txt
deleted file mode 100644
index 194964c..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/drop-cc-columns.txt
+++ /dev/null
@@ -1,66 +0,0 @@
-UPGRADE NOTES - Credit Card Receipts and Privacy
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-To improve privacy and security, Evergreen now stores less data 
-about credit card transactions.  The following fields are no 
-longer stored:
-
- * cc_type
- * cc_first_name
- * cc_last_name
- * expire_month
- * expire_year
-
-NOTE: All existing data within these fields will be deleted during
-the upgrade.  Reports using this data will no longer function.
-
-Additionally, a tool has been added to Evergreen for clearing the 
-last 4 digits of the credit payment from the database after payments
-reach a certain age.
-
-Print/Email Templates
-+++++++++++++++++++++
-
-The stock print and email payment templates have been modified to no 
-longer use these fields, but only when the existing templates matched
-the stock templates.  If local changes have been applied, it will
-be necessary to modify local templates to avoid referencing these
-fields which no longer exist.
-
-Any templates whose hook is "money.format.payment_receipt.print" or 
-"money.format.payment_receipt.email" may need modification.  In stock
-Evergreen, these are templates:
-
-1. "money.payment_receipt.email" (stock id 29)
-2. "money.payment_receipt.print" (stock id 30)
-
-Example diff:
-
-[source,diff]
----------------------------------------------
--  [% CASE "credit_card_payment" %]credit card (
--      [%- SET cc_chunks = mp.credit_card_payment.cc_number.replace(' ','').chunk(4); -%]
--      [%- cc_chunks.slice(0, -1+cc_chunks.max).join.replace('\S','X') -%] 
--      [% cc_chunks.last -%]
--      exp [% mp.credit_card_payment.expire_month %]/[% mp.credit_card_payment.expire_year -%]
--  )
-+  [% CASE "credit_card_payment" %]credit card
-+  [%- IF mp.credit_card_payment.cc_number %] ([% mp.credit_card_payment.cc_number %])[% END %]
----------------------------------------------
-
-Clearing the Last 4 of the CC Number
-++++++++++++++++++++++++++++++++++++
-
-To active automatic CC number clearing, add the following to opensrf's
-crontab.  Change timing to suit.
-
-[source,sh]
----------------------------------------------
-5  4  * * *   . ~/.bashrc && $EG_BIN_DIR/clear_cc_number.srfsh
----------------------------------------------
-
-The default retention age is 1 year, but this can be changed by modifying
-clear_cc_number.srfsh (typically found in /openils/bin/).  Replace "1 year"
-with the age of your choice.
-
-
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/juv-to-adult.adoc b/docs/RELEASE_NOTES_NEXT/Administration/juv-to-adult.adoc
deleted file mode 100644
index 55c0ea8..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/juv-to-adult.adoc
+++ /dev/null
@@ -1,9 +0,0 @@
-Juvenile-to-Adult Batch Script Honors Org Unit Setting
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The batch juv_to_adult.srfsh script, which is typically run via CRON,
-that is responsible for toggling a patron from juvenile to adult now
-honors the age value set in the org unit setting named "Juvenile Age
-Threshold" (global.juvenile_age_threshold).  When no org setting value
-is present at a given patron's home library, the value passed in to the
-script will be used as a default.
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/new_hold_copy_ratio_reporting_source.adoc b/docs/RELEASE_NOTES_NEXT/Administration/new_hold_copy_ratio_reporting_source.adoc
deleted file mode 100644
index 8ab77e1..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/new_hold_copy_ratio_reporting_source.adoc
+++ /dev/null
@@ -1,20 +0,0 @@
-New Reporting Source for Hold/Copy Ratios
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-A new reporting source is added, "Hold/Copy Ratio per Bib
-and Pickup Library (and Descendants)", that, for each bib
-that has a hold request on it or any of its components,
-calculates the following:
-
- * active holds at each OU (including the OU's descendants)
- * holdable copies at each OU (and its descendants)
- * the ratio of the above two counts
- * counts and ratio across the entire consortium
-
-This source differs from the "Hold/Copy Ratio per Bib
-and Pickup Library" source by including all descendants
-of the organization unit one is filtering on.
-
-One use case is allowing a multi-branch system within an
-Evergreen consortium that doesn't do full resource sharing
-to readily calculate whether additional copies should be
-purchased for that system.
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/password-storage.lp1468422.adoc b/docs/RELEASE_NOTES_NEXT/Administration/password-storage.lp1468422.adoc
deleted file mode 100644
index bb6206c..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/password-storage.lp1468422.adoc
+++ /dev/null
@@ -1,120 +0,0 @@
-Improved Password Management and Authentication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Evergreen user passwords are now stored with additional layers of 
-encryption and may only be accessed directly by the database, not
-the application layer.
-
-All API changes are backwards compatible with existing 3rd-party
-clients.
-
-Migrating Passwords
-+++++++++++++++++++
-
-Passwords are migrated for each user automatically the first time a user
-logs in under the new setup.  However, it is also possible to force
-password migration for a given user via a database function:
-
-[source,sql]
-------------------------------------------------------------
--- actor.migrate_passwd() will only migrate un-migrated 
--- accounts, but it's faster to avoid any re-migration attempts.
-SELECT actor.migrate_passwd(au.id)
-FROM actor.usr au
-    LEFT JOIN actor.passwd pw ON (pw.usr = au.id)
-WHERE pw.usr IS NULL; 
-------------------------------------------------------------
-
-Using this, admins could perform manual batch updates to force all
-users to use the new, more secure passwords, regardless of when or
-whether a patron logs back into the system.  
-
-Beware that doing this for all users in the a large database will 
-take some time and should proably be performed in batches.  (On 
-Bill's test VM it took 14 seconds to migrate 233 users).
-
-open-ils.auth_internal
-++++++++++++++++++++++
-To support the new storage mechanism, a new Evergreen service has
-been added called "open-ils.auth_internal".  This service runs on
-the private OpenSRF/XMPP domain and is used to store authenticated 
-user data in the authentication cache.  
-
-This is a required service and changes to opensrf.xml (typically 
-/openils/conf/opensrf.xml) are needed to run the new service.
-
-.Modifying opensrf.xml
-* A new <open-ils.auth_internal> app stanza is added to define the 
-  new service
-* Cache timeout settings are moved from the app stanza for open-ils.auth
-  into open-ils.auth_internal
-* open-ils.auth_internal is added to the set of running services for the 
-  domain.
-
-Example diff:
-
-[source,diff]
----------------------------------------------------------------------
-diff --git a/Open-ILS/examples/opensrf.xml.example b/Open-ILS/examples/opensrf.xml.example
-index 3b47481..59f737a 100644
---- a/Open-ILS/examples/opensrf.xml.example
-+++ b/Open-ILS/examples/opensrf.xml.example
-@@ -424,6 +424,29 @@ vim:et:ts=4:sw=4:
-                 </unix_config>
-                 <app_settings>
-                     <!-- defined app-specific settings here -->
-+                    <auth_limits>
-+                        <seed>30</seed> <!-- amount of time a seed request is valid for -->
-+                        <block_time>90</block_time> <!-- amount of time since last auth or seed request to save failure counts -->
-+                        <block_count>10</block_count> <!-- number of failures before blocking access -->
-+                    </auth_limits>
-+                </app_settings>
-+            </open-ils.auth>
-+
-+            <!-- Internal authentication server -->
-+            <open-ils.auth_internal>
-+                <keepalive>5</keepalive>
-+                <stateless>1</stateless>
-+                <language>c</language>
-+                <implementation>oils_auth_internal.so</implementation>
-+                <unix_config>
-+                    <max_requests>1000</max_requests>
-+                    <min_children>1</min_children>
-+                    <max_children>15</max_children>
-+                    <min_spare_children>1</min_spare_children>
-+                    <max_spare_children>5</max_spare_children>
-+                </unix_config>
-+                <app_settings>
-+                    <!-- defined app-specific settings here -->
-                     <default_timeout>
-                         <!-- default login timeouts based on login type -->
-                         <opac>420</opac>
-@@ -431,13 +454,10 @@ vim:et:ts=4:sw=4:
-                         <temp>300</temp>
-                         <persist>2 weeks</persist>
-                     </default_timeout>
--                    <auth_limits>
--                        <seed>30</seed> <!-- amount of time a seed request is valid for -->
--                        <block_time>90</block_time> <!-- amount of time since last auth or seed request to save failure counts -->
--                        <block_count>10</block_count> <!-- number of failures before blocking access -->
--                    </auth_limits>
-                 </app_settings>
--            </open-ils.auth>
-+            </open-ils.auth_internal>
-+
-+
- 
-             <!-- Authentication proxy server -->
-             <open-ils.auth_proxy>
-@@ -1177,6 +1197,7 @@ vim:et:ts=4:sw=4:
-                 <appname>open-ils.circ</appname> 
-                 <appname>open-ils.actor</appname> 
-                 <appname>open-ils.auth</appname> 
-+                <appname>open-ils.auth_internal</appname>
-                 <appname>open-ils.auth_proxy</appname> 
-                 <appname>open-ils.storage</appname>  
-                 <appname>open-ils.justintime</appname>  
----------------------------------------------------------------------
-
-
-
-
diff --git a/docs/RELEASE_NOTES_NEXT/Administration/sortable_html_reports.adoc b/docs/RELEASE_NOTES_NEXT/Administration/sortable_html_reports.adoc
deleted file mode 100644
index 539a576..0000000
--- a/docs/RELEASE_NOTES_NEXT/Administration/sortable_html_reports.adoc
+++ /dev/null
@@ -1,6 +0,0 @@
-Sortable HTML reports
-^^^^^^^^^^^^^^^^^^^^^
-HTML reports can now be sorted by clicking on the header for a given column.
-Clicking on the header toggles between sorting the column in ascending and
-descending order. Note that sorting is available only when there are
-at most 10,000 rows of output.
diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/add_additional_fixed_fields.txt b/docs/RELEASE_NOTES_NEXT/Cataloging/add_additional_fixed_fields.txt
deleted file mode 100644
index 8d26e61..0000000
--- a/docs/RELEASE_NOTES_NEXT/Cataloging/add_additional_fixed_fields.txt
+++ /dev/null
@@ -1,13 +0,0 @@
-Additional Fixed Fields
-^^^^^^^^^^^^^^^^^^^^^^^
-The AccM, Comp, CrTp, EntW, Cont, FMus, LTxt, Orig, Part, Proj, Relf, SpFm,
-SrTp, Tech, and TrAr fixed fields have been defined and coded value maps added
-so they can also be used for Advanced Searches or adding to Composite Value Maps.
-
-Note that AccM, Cont, LTxt, Relf, and SpFm are  compositite values based on
-the values of "helper" fields like AccM(1), AccM(2), and so on. These positional
-fields can be ignored.
-
-Coded value maps have also been added for Cont, Ctry, and DtSt, and the Time field
-has been defined. All of these fields are now available in the Fixed Field Editor
-when editing the appropriate records.
diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/export_non_imported_records.adoc b/docs/RELEASE_NOTES_NEXT/Cataloging/export_non_imported_records.adoc
deleted file mode 100644
index 9c755c0..0000000
--- a/docs/RELEASE_NOTES_NEXT/Cataloging/export_non_imported_records.adoc
+++ /dev/null
@@ -1,7 +0,0 @@
-Quickly export non-imported records
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-When inspecting a queue in MARC Batch Import/Export, there is now
-a link to download to MARC file any records in the queue that were
-not imported into the catalog.  This allows catalogers to quickly
-manipulate the records that failed to import using an external
-tool, then attempt to import then again.
diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/link_personal_name_title_series_entries.adoc b/docs/RELEASE_NOTES_NEXT/Cataloging/link_personal_name_title_series_entries.adoc
deleted file mode 100644
index bda6661..0000000
--- a/docs/RELEASE_NOTES_NEXT/Cataloging/link_personal_name_title_series_entries.adoc
+++ /dev/null
@@ -1,5 +0,0 @@
-Link personal name/title series added entries
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The authority linker script now supports linking the MARC21
-field 800 (series added entry - personal name) to authority
-records.
diff --git a/docs/RELEASE_NOTES_NEXT/Cataloging/marc_stream_imp_auth.adoc b/docs/RELEASE_NOTES_NEXT/Cataloging/marc_stream_imp_auth.adoc
deleted file mode 100644
index 17639f4..0000000
--- a/docs/RELEASE_NOTES_NEXT/Cataloging/marc_stream_imp_auth.adoc
+++ /dev/null
@@ -1,45 +0,0 @@
-MARC stream importer authority records and repairs
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-The MARC stream importer script, commonly used with external 
-services like OCLC Connexion, is now capable of importing authority
-records in addition to bib records.  A single running instance of
-the script can import either type of record, based on the record
-leader.
-
-New Options
-+++++++++++
-
- * --auth-merge-profile
- * --auth-queue
- * --bib-import-no-match
- * --bib-auto-overlay-exact
- * --bib-auto-overlay-1match
- * --bib-auto-overlay-best-match
- * --auth-import-no-match
- * --auth-auto-overlay-exact
- * --auth-auto-overlay-1match
- * --auth-auto-overlay-best-match
-
-Deprecated Options
-++++++++++++++++++
-
-The following options still work and map to the "bib" equivalent
-of the option, however a deprecation warning message is generated 
-when the script is started.
-
- * --import-no-match
- * --auto-overlay-exact
- * --auto-overlay-1match
- * --auto-overlay-best-match
-
-No Longer Supported Options
-+++++++++++++++++++++++++++
-
---import-by-queue is no longer supported.  This option serves no
-particular purpose and is a bad idea when re-using the same queue over
-and over as most people do, because queue bloat will increase run times.
-
---noqueue (AKA "direct import") is no longer supported.  All imports go
-through Vandelay now.
-
diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/more-visible-parts.adoc b/docs/RELEASE_NOTES_NEXT/Circulation/more-visible-parts.adoc
deleted file mode 100644
index b9f198f..0000000
--- a/docs/RELEASE_NOTES_NEXT/Circulation/more-visible-parts.adoc
+++ /dev/null
@@ -1,13 +0,0 @@
-Alternate Parts Selection Display When Placing Holds
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Users often miss the list of parts on the Place Holds screen, leading to many
-title-level holds on records where only one or two libraries may have
-'unparted' copies.
-
-A new option is available to change this display so that a part is selected
-via radio buttons instead of the traditional dropdown menu. This display
-increases the visibility of parts on the Place Holds screen and also
-forces users to make an explicit choice.
-
-To enable the alternate display, set the enable.radio.parts option to 'true'
-in parts/config.tt2.
diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/native_web_staff_client_patron_editor.adoc b/docs/RELEASE_NOTES_NEXT/Circulation/native_web_staff_client_patron_editor.adoc
deleted file mode 100644
index 99c5f62..0000000
--- a/docs/RELEASE_NOTES_NEXT/Circulation/native_web_staff_client_patron_editor.adoc
+++ /dev/null
@@ -1,13 +0,0 @@
-Web staff client patron editor
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The web staff interface now includes a patron editor/registration form
-that is written using AngularJS, leading to faster and more responsive
-patron editing.  This feature is currently available in preview mode, but
-supports the following actions:
-
-  * adding and editing base patron records and addresses
-  * setting statistical categories
-  * editing secondary groups
-  * cloning patron records
-  * duplicate detection
-  * surveys
diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/non_activate_copy_transit_msg.txt b/docs/RELEASE_NOTES_NEXT/Circulation/non_activate_copy_transit_msg.txt
deleted file mode 100644
index 0bc8d2b..0000000
--- a/docs/RELEASE_NOTES_NEXT/Circulation/non_activate_copy_transit_msg.txt
+++ /dev/null
@@ -1,17 +0,0 @@
-==== Non-Active Status Copy Transit Message ====
-
-After copy checkin, if the copy is in-transit, display a special
-message in the transit alert dialog and in the printed transit receipt
-(optionally, via macro) if the copy is in (or, rather, will be once it
-arrives at its destination) a non-active copy status.
-
-===== Upgrade Notes =====
-
- * To add the new message to the transit slip, add the
-   'transit_copy_status_msg' MACRO.
- * To remove the new message from the alert dialog, remove the 
-   'staff.circ.utils.transit.copy_status_message' string property
-   from 'Open-ILS/xul/staff_client/server/locale/LOCALE/circ.properties'
- * For a list of non-active copy statuses, see in the staff client
-   under Admin -> Server Administration -> Copy Statuses.
-
diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/restrict_opt_in.adoc b/docs/RELEASE_NOTES_NEXT/Circulation/restrict_opt_in.adoc
deleted file mode 100644
index 5046293..0000000
--- a/docs/RELEASE_NOTES_NEXT/Circulation/restrict_opt_in.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-Selectively disallow opt-in based on patron's home library
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-A new org unit setting has been added which enables a library to prevent their
-patrons from being opted in at other libraries.
-
-For example, consider the following org unit hierarchy:
-
-       Org Units          Depth
-
-          CONS              0
-           |
-      +-----+-----+
-      |           |
-     SYS1        SYS2       1
-      |           |
-   +--+--+     +--+--+
-   |     |     |     |
-  BR1   BR2   BR3   BR4     2
-
-Suppose that SYS1 wishes to prevent its patrons from being opted in at SYS2.
-To accomplish this, it sets the value of the "Restrict patron opt-in to home
-library and related orgs at specified depth" setting to 1, meaning that patrons
-at SYS1 libraries at or below that depth in the org tree cannot be opted in by
-libraries outside that part of the org tree.  Thus, BR1 patrons can be opted in
-at BR2, but not at BR3 or BR4.
-
-(This setting is distinct from the "Patron Opt-In Boundary" setting, which
-merely determines the depth at which Evergreen prompts for the patron to opt
-in.)
-
-New Library Setting
-+++++++++++++++++++
-  * Restrict patron opt-in to home library and related orgs at specified depth (org.restrict_opt_to_depth)
diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt b/docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt
deleted file mode 100644
index 08ef46a..0000000
--- a/docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt
+++ /dev/null
@@ -1,30 +0,0 @@
-Standing Penalty Ignore Proximity
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Standing penalties now have an ignore_proximity field that takes an
-integer value.  When set, the value of this field represents the
-proximity from the user's home organizational unit where this penalty
-will be ignored for purposes of circulation and holds.  Typical values
-for this field would be 0, 1, or 2 when using a standard hierarchy of
-Consortium -> System -> Branch -> Sublibrary/Bookmoblie.  A value of 1
-would cause the penalty to be ignored at the user's home organization
-unit, it's parent and/or immediate child.  A value of 2 should cause
-it to be ignored at the above as well as all sibling organizational
-units to the user's home.  In all cases, a value of zero causes the
-penalty to be ignored at the user's home and to apply at all other
-organizational units.  If the value of this field is left unset (or
-set to a negative value), the penalty will still take effect
-everywhere using the normal organizational unit and depth values.  If
-you use a custom hierarchy, you will need to figure out any values
-greater than 0 on your own.
-
-The ignore_proximity does not affect where penalties are applied. It
-is used when determining whether or not a penalty blocks an activity
-at the current organizational unit or the organizational unit that
-owns the copy involved in the current transaction.  For instance, if
-you set the ignore_proximity to 0 on patron exceeds overdue fines,
-then the patron will still be able to place holds on and checkout
-copies owned by their home organizational unit at their home
-organizational unit.  They will not, however, be able to receive
-copies from other organizational units, nor use other organizational
-units as a patron.
diff --git a/docs/RELEASE_NOTES_NEXT/Circulation/user-circ-history.adoc b/docs/RELEASE_NOTES_NEXT/Circulation/user-circ-history.adoc
deleted file mode 100644
index 168d753..0000000
--- a/docs/RELEASE_NOTES_NEXT/Circulation/user-circ-history.adoc
+++ /dev/null
@@ -1,54 +0,0 @@
-Patron Checkout History Stored in a Dedicated Table
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Patron checkout history is now stored in separate, dedicated database 
-table instead of being derived from the main circulation data.  This
-allows us to age/anonymize circulations more aggressively, since they 
-no longer need to stick around in cases where they represent a patron's
-opt-in checkout history.
-
-This has a number of patron privacy implications.
-
- * Minimal metadata is stored in the new patron checkout history table, 
-   so once the corresponding circulation is aged, the full set of 
-   circulation metadata is no longer linked to a patron's reading history.
-   ** It is limited to checkout date, due date, checkin date, and copy data.
- * Staff can no longer report on a patron's reading history.  
-   ** While it is possible to build aggregate reports on reading history 
-      data, it is not possible to report on which user an entry in the
-      history table belongs to.  (The 'usr' column is hidden from the 
-      reporter).
- * Staff can no longer retrieve a patron's reading history via API.  Only
-   the user that owns the history data can access it.
- * Though not implemented as part of this change, it will now be possible
-   with future development to truly remove specific items from a patron's
-   checkout history.
-
-TPAC Patron History Disable Warning
-+++++++++++++++++++++++++++++++++++
-
-When disabling checkout and/or holds history in the TPAC Search and
-History Preferences tab, patrons will be warned that the operation is
-irreversible when history data exists that will be deleted as part of 
-the update.
-
-Upgrade Notes
-+++++++++++++
-
-Administrators should verify the CSV export of checkout history works after
-deploying this change.  If local changes were made to the CSV template,
-the template will not be updated as part of this deployment.  The stock 
-template was modified to handle gracefully NULL values for checkin_time.
-
-For example:
-
-[source,diff]
-------------------------------------------------------------------------
--    Returned: [% date.format(helpers.format_date(circ.checkin_time), '%Y-%m-%d') %]
-+    Returned: [%
-+        date.format(
-+            helpers.format_date(circ.checkin_time), '%Y-%m-%d') 
-+            IF circ.checkin_time; 
-+    %]
-------------------------------------------------------------------------
-
diff --git a/docs/RELEASE_NOTES_NEXT/Client/column-picker-holds-count.adoc b/docs/RELEASE_NOTES_NEXT/Client/column-picker-holds-count.adoc
deleted file mode 100644
index feadc17..0000000
--- a/docs/RELEASE_NOTES_NEXT/Client/column-picker-holds-count.adoc
+++ /dev/null
@@ -1,11 +0,0 @@
-Holds Count Column Picker Option
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-A new column picker option showing the number of holds for a given item will
-now be available in various interfaces displaying item information, including
-the patron's Items Out tab and the Item Status, Check Out, Check In, Renew
-Item and Record In-House Use screens.
-
-Note: Because the holds count is generated from the hold_copy_map, newly-added
-items and items in a non-holdable status will not display accurate hold counts
-until 24 hours after they have been added to the system or moved to a holdable
-copy status.
diff --git a/docs/RELEASE_NOTES_NEXT/Development/remove_unused_methods.adoc b/docs/RELEASE_NOTES_NEXT/Development/remove_unused_methods.adoc
deleted file mode 100644
index 945b93d..0000000
--- a/docs/RELEASE_NOTES_NEXT/Development/remove_unused_methods.adoc
+++ /dev/null
@@ -1,8 +0,0 @@
-Removal of unused methods
-^^^^^^^^^^^^^^^^^^^^^^^^^
-The following public methods, which were both broken and not in use,
-are removed:
-
- * `open-ils.actor.org_unit.closed_date.create`
- * `open-ils.actor.org_unit.closed_date.delete`
-
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/Adjust_copy_sort_order.adoc b/docs/RELEASE_NOTES_NEXT/OPAC/Adjust_copy_sort_order.adoc
deleted file mode 100644
index beb174a..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/Adjust_copy_sort_order.adoc
+++ /dev/null
@@ -1,11 +0,0 @@
-Include parts label when sorting copies in the public catalog
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The list of copies on the record details page now includes
-the part label in the default sort order.
-
-Specifically, copies are now sorted by (in order), org unit, then
-call number, then part label sortkey, then copy number, and
-finally barcode.
-
-Previously, the hierarchy was org unit, then call number,
-then copy number, and finally barcode
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/Expand_unAPI.adoc b/docs/RELEASE_NOTES_NEXT/OPAC/Expand_unAPI.adoc
deleted file mode 100644
index f4cc7c8..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/Expand_unAPI.adoc
+++ /dev/null
@@ -1,64 +0,0 @@
-Expand unAPI API
-^^^^^^^^^^^^^^^^
-Evergreen's unAPI support now includes access to many more
-record types. For example, the following URL would fetch
-bib 267 in MODS32 along with holdings, volume, copy,
-and record attribute information:
-
-https://example.org/opac/extras/unapi?id=tag::U2@bre/267{holdings_xml,acn,acp,mra}&format=mods32
-
-To access the new unAPI features, the unAPI ID should have the
-following form:
-
-  * +tag::U2 at +
-  * followed by class name, which may be
-    * +bre+ (bibs)
-    * +biblio_record_entry_feed+ (multiple bibs)
-    * +acl+ (copy locations)
-    * +acn+ (volumes)
-    * +acnp+ (call number prefixes)
-    * +acns+ (call number suffixes)
-    * +acp+ (copies)
-    * +acpn+ (copy notes)
-    * +aou+ (org units)
-    * +ascecm+ (copy stat cat entries)
-    * +auri+ (located URIs)
-    * +bmp+ (monographic parts)
-    * +cbs+ (bib sources)
-    * +ccs+ (copy statuses)
-    * +circ+ (loan checkout and due dates)
-    * +holdings_xml+ (holdings)
-    * +mmr+ (metarecords)
-    * +mmr_holdings_xml+ (metarecords with holdings)
-    * +mmr_mra+ (metarecords with record attributes)
-    * +mra+ (record attributes)
-    * +sbsum+ (serial basic summaries)
-    * +sdist+ (serial distributions)
-    * +siss+ (serial issues)
-    * +sisum+ (serial index summaries)
-    * +sitem+ (serial items)
-    * +sssum+ (serial supplement summaries)
-    * +sstr+ (serial streams)
-    * +ssub+ (serial subscriptions)
-    * +sunit+ (serial units)
-  * followed by +/+
-  * followed by a record identifier (or in the case of
-    the +biblio_record_entry_feed+ class, multiple IDs separated
-    by commas)
-  * followed, optionally, by limit and offset in square brackets
-  * followed, optionally, by a comma-separated list of "includes"
-    enclosed in curly brackets.  The list list of includes is
-    the same as the list of classes with the following addition:
-    * +bre.extern+ (information from the non-MARC parts of a bib
-      record)
-   * followed, optionally, by +/+ and org unit; "-" signifies
-     the top of the org unit tree
-   * followed, optionally, by +/+ and org unit depth
-   * followed, optionally, by +/+ and a path. If the path
-     is +barcode+ and the class is +acp+, the record ID is taken
-     to be a copy barcode rather than a copy ID; for example, in
-     +tag::U2 at acp/ACQ140{acn,bre,mra}/-/0/barcode+, +ACQ140+ is
-     meant to be a copy barcode.
-   * followed, optionally, by +&format=+ and the format in which the record
-     should be retrieved. If this part is omitted, the list of available 
-     formats will be retrieved. 
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/Genre_index.txt b/docs/RELEASE_NOTES_NEXT/OPAC/Genre_index.txt
deleted file mode 100644
index e603624..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/Genre_index.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-New Form/Genre Search and Facet Index
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The stock indexing definitions now include a search and facet index on the
-form/genre field (tag 655). This allows genre links in the public catalog
-record display to retrieve works in the same genre. The public catalog genre
-links will no longer display content from the 659 MARC fields. 
-
-The genre facet will also display by default in the public catalog.  A partial
-reingest during upgrade is required to use this index.
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt b/docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt
deleted file mode 100644
index bd0c7ea..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt
+++ /dev/null
@@ -1,14 +0,0 @@
-Limit number of facets retrieved during search
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-Catalog search now sets a limit on the number of facets retrieved
-per defined facet field. Setting a limit is useful so that
-`open-ils.cstore backends don't end up needlessly consuming
-memory when fetching facets for a large result set; if a broad
-search retrieves over 10,000 author facets (say), even the most
-persistant user is not going to actually look at all of them. Fetching
-fewer facets can also slightly speed up generation of search results.
-
-The limit is controlled by a new global flag, `search.max_facets_per_field`,
-whose label is "Search: maximum number of facet values to retrieve for
-each facet field".  The default limit value is 1,000, but lower values
-(e.g., 100) are perhaps even better for most catalogs.
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/depth_toggle.txt b/docs/RELEASE_NOTES_NEXT/OPAC/depth_toggle.txt
deleted file mode 100644
index 8a3153a..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/depth_toggle.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-Search Scope Depth Selection
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-A common usage of the catalog is to do a search in a restricted scope,
-like a local library. When the results are lacking, the search is repeated in a
-consortium-wide scope.  This feature provides an optional button and checkbox
-to alter the depth of the search to a defined level.
-
-This feature can be turned off from config.tt2.
-
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/edit_circ_history b/docs/RELEASE_NOTES_NEXT/OPAC/edit_circ_history
deleted file mode 100644
index ea4c60c..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/edit_circ_history
+++ /dev/null
@@ -1,10 +0,0 @@
-Editable Borrowing History
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can delete titles that you do not wish to appear in your Check Out History. 
-
- * In "My Account", click on the "Items Checked Out" tab, then the "Check Out History" sub-tab.
- * Check off the items you wish to conceal.
- * Click the Go button next to the "Delete Selected Titles" drop-down box.
- * Click OK in the pop-up to confirm your deletion.  Choose carefully, as there is no "undo".
-
-Deleted titles will also not appear in the downloaded CSV file.
diff --git a/docs/RELEASE_NOTES_NEXT/OPAC/exclude-electronic-limiter.adoc b/docs/RELEASE_NOTES_NEXT/OPAC/exclude-electronic-limiter.adoc
deleted file mode 100644
index 302c69b..0000000
--- a/docs/RELEASE_NOTES_NEXT/OPAC/exclude-electronic-limiter.adoc
+++ /dev/null
@@ -1,9 +0,0 @@
-Limiter to exclude electronic resources
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-A limiter to exclude electronic resources from search results is now available
-on the advanced search screen and from the search results page. This limiter
-will exclude any search results with an item form of o or s. This limiter
-will be applied on top of any other format limiters used in the search.
-
-The checkboxes are disabled by default; to display them in both places, please
-toggle the 'ctx.exclude_electronic_checkbox' setting in config.tt2.

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

Summary of changes:
 .../Acquisitions/acq-li-paid-label.txt             |    4 -
 .../Acquisitions/debits-paid-on-invoice-close.adoc |    8 --
 .../Acquisitions/po-actions-selector.adoc          |    9 --
 .../Administration/DB_Application_Name_Option.adoc |    8 --
 .../In_AT_telephony_configuration.adoc             |   39 -------
 .../Administration/NewPatronNotice.txt             |   15 ---
 .../Administration/drop-cc-columns.txt             |   66 -----------
 .../Administration/juv-to-adult.adoc               |    9 --
 .../new_hold_copy_ratio_reporting_source.adoc      |   20 ----
 .../Administration/password-storage.lp1468422.adoc |  120 --------------------
 .../Administration/sortable_html_reports.adoc      |    6 -
 .../Cataloging/add_additional_fixed_fields.txt     |   13 --
 .../Cataloging/export_non_imported_records.adoc    |    7 -
 .../link_personal_name_title_series_entries.adoc   |    5 -
 .../Cataloging/marc_stream_imp_auth.adoc           |   45 --------
 .../Circulation/more-visible-parts.adoc            |   13 --
 .../native_web_staff_client_patron_editor.adoc     |   13 --
 .../Circulation/non_activate_copy_transit_msg.txt  |   17 ---
 .../Circulation/restrict_opt_in.adoc               |   33 ------
 .../standing_penalty_ignore_proximity.txt          |   30 -----
 .../Circulation/user-circ-history.adoc             |   54 ---------
 .../Client/column-picker-holds-count.adoc          |   11 --
 .../Development/remove_unused_methods.adoc         |    8 --
 .../OPAC/Adjust_copy_sort_order.adoc               |   11 --
 docs/RELEASE_NOTES_NEXT/OPAC/Expand_unAPI.adoc     |   64 -----------
 docs/RELEASE_NOTES_NEXT/OPAC/Genre_index.txt       |    9 --
 .../OPAC/Limit_number_of_facets_retrieved.txt      |   14 ---
 docs/RELEASE_NOTES_NEXT/OPAC/depth_toggle.txt      |    9 --
 docs/RELEASE_NOTES_NEXT/OPAC/edit_circ_history     |   10 --
 .../OPAC/exclude-electronic-limiter.adoc           |    9 --
 30 files changed, 0 insertions(+), 679 deletions(-)
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Acquisitions/acq-li-paid-label.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Acquisitions/debits-paid-on-invoice-close.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Acquisitions/po-actions-selector.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/DB_Application_Name_Option.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/In_AT_telephony_configuration.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/NewPatronNotice.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/drop-cc-columns.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/juv-to-adult.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/new_hold_copy_ratio_reporting_source.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/password-storage.lp1468422.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Administration/sortable_html_reports.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Cataloging/add_additional_fixed_fields.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Cataloging/export_non_imported_records.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Cataloging/link_personal_name_title_series_entries.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Cataloging/marc_stream_imp_auth.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/more-visible-parts.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/native_web_staff_client_patron_editor.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/non_activate_copy_transit_msg.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/restrict_opt_in.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/standing_penalty_ignore_proximity.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Circulation/user-circ-history.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Client/column-picker-holds-count.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/Development/remove_unused_methods.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/Adjust_copy_sort_order.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/Expand_unAPI.adoc
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/Genre_index.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/Limit_number_of_facets_retrieved.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/depth_toggle.txt
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/edit_circ_history
 delete mode 100644 docs/RELEASE_NOTES_NEXT/OPAC/exclude-electronic-limiter.adoc


hooks/post-receive
-- 
Evergreen ILS




More information about the open-ils-commits mailing list