1 Evergreen 3.2 Release Notes
2 ===========================
9 This release contains bug fixes improving on Evergreen 3.2.7.
10 All bug fixes refer to the web staff client unless otherwise specified.
18 * Accessibility improvements to the date picker calendar button (https://bugs.launchpad.net/evergreen/+bug/1796903[Bug #1796903])
19 * Blank values in CSV grid downloads now show as blank instead of reading 'null' (https://bugs.launchpad.net/evergreen/+bug/1766982[Bug #1766982])
20 * Fixes invalid language codes in the staff client and KPAC (https://bugs.launchpad.net/evergreen/+bug/1802593[Bug #1802593])
21 * Fixes display issue with menus at certain screen resolutions (https://bugs.launchpad.net/evergreen/+bug/1813078[Bug 1813078])
22 * Removes duplicate columns from several grids (https://bugs.launchpad.net/evergreen/+bug/1683385[Bug 1683385])
23 * Adds a login failed message to the Angular sign in screen when appropriate (https://bugs.launchpad.net/evergreen/+bug/1834969[Bug 1834969])
28 * Adds fund year to Distribution Formula fund dropdown menu (https://bugs.launchpad.net/evergreen/+bug/1329920[Bug 1329920])
33 * Extra whitespace in 856$9 subfields no longer prevents located URIs from being displayed in electronic resource records. (https://bugs.launchpad.net/evergreen/+bug/1722827[Bug #1722827])
34 * Fixes issue in Item Status import where spaces or empty lines in barcode files caused an import failure (https://bugs.launchpad.net/evergreen/+bug/1798187[Bug #1798187])
35 * The Item Status list and detail views now have the same actions available. (https://bugs.launchpad.net/evergreen/+bug/1775920[Bug #1775920])
36 * Adds record summary display to merge records (https://bugs.launchpad.net/evergreen/+bug/1739292[Bug #1739292])
37 * Fixes issue in Bucket grids where grid configurations were not saving correctly (https://bugs.launchpad.net/evergreen/+bug/1805895[Bug# 1805895])
38 * "Local catalog" is now at the top of the list of Z39.50 sources. (https://bugs.launchpad.net/evergreen/+bug/1787676[Bug #1787676])
39 * Fixes issue with authority_control_field.pl script (https://bugs.launchpad.net/evergreen/+bug/1650409[Bug #1650409])
40 * Fixes an issue with the "Retrieve Last Bib Record" action. (https://bugs.launchpad.net/evergreen/+bug/1830424[Bug #1830424])
41 * Fixes an issue with the Edit buttons in the Merge Records interface. (https://bugs.launchpad.net/evergreen/+bug/1836229[Bug #1836229])
42 * Fixes an issue with the _Clear_ button in the holdings template editor. (https://bugs.launchpad.net/evergreen/+bug/1803584[Bug #1803584])
48 * Fixes slowness issues with checkin and checkout grids (https://bugs.launchpad.net/evergreen/+bug/1777207[Bug #1777207])
49 * Fixes an issue that allowed staff to renew items to dates in the past. (https://bugs.launchpad.net/evergreen/+bug/1034058[Bug #1034058])
50 * Fixes an error that occured when checking in lost items when a certain setting was enabled. (https://bugs.launchpad.net/evergreen/+bug/1511765[Bug #1511765])
51 * Fixes an issue that caused the money summary to be missing from the patron record Bills tab. (https://bugs.launchpad.net/evergreen/+bug/1800484[Bug #1800484])
52 * Multiple improvements to the Mark Damaged Popup. (Bugs https://bugs.launchpad.net/evergreen/+bug/1759864[#1759864] and https://bugs.launchpad.net/evergreen/+bug/1742523[#1742523])
57 * Updates to the Angular client's .editorconfig file. (https://bugs.launchpad.net/evergreen/+bug/1838136[Bug #1838136])
62 * Accessibility improvements to form fields. (https://bugs.launchpad.net/evergreen/+bug/1735768[Bug #1735768])
67 * Users can now hard code a list of filter values in a report template (https://bugs.launchpad.net/evergreen/+bug/1785061[Bug #1785061])
68 * Fixes an issue that caused column labels to re-sort when deleting fields in a template. (https://bugs.launchpad.net/evergreen/+bug/1751800[Bug #1751800])
69 * Fixes column type for Billing Totals and Billing Paid columns (https://bugs.launchpad.net/evergreen/+bug/1681930[Bug #1681930])
74 We would like to thank the following individuals who contributed code,
75 testing and documentation patches to the 3.2.8 point release of
107 This release contains bug fixes improving on Evergreen 3.2.6.
108 All bug fixes refer to the web staff client unless otherwise specified.
115 * Corrects a rounding error that caused fines to exceed the max fines
117 (https://bugs.launchpad.net/evergreen/+bug/1704819[Bug #1704819])
118 * Corrects an issue with printing Items Out receipts
119 (https://bugs.launchpad.net/evergreen/+bug/1790896[Bug #1790896])
120 * SIP Visa payments are now recorded as credit card, rather than cash
122 (https://bugs.launchpad.net/evergreen/+bug/1796942[Bug #1796942])
123 * Converting change to patron credit no longer requires staff members
124 to refresh the screen to see the new credit
125 (https://bugs.launchpad.net/evergreen/+bug/1775639[Bug #1775639])
126 * The patron summary now includes tooltips that were available in
128 (https://bugs.launchpad.net/evergreen/+bug/1772206[Bug #1772206])
129 * The patron holds grid now includes a SMS Carrier column
130 (https://bugs.launchpad.net/evergreen/+bug/1748265[Bug #1748265])
131 * When registering a new patron from Pending Patrons, the address
132 type dropdown now supports a default value
133 (https://bugs.launchpad.net/evergreen/+bug/1816180[Bug #1816180])
134 * The Items Out grid now includes a Monograph Parts column
135 (https://bugs.launchpad.net/evergreen/+bug/1789257[Bug #1789257])
136 * The annotate checkbox on the bill payment screen is now sticky
137 (https://bugs.launchpad.net/evergreen/+bug/1759343[Bug #1759343])
138 * Group member details grid settings can now be saved
139 (https://bugs.launchpad.net/evergreen/+bug/1774707[Bug #1774707])
140 * The patron registration date of birth field can now display a
142 (https://bugs.launchpad.net/evergreen/+bug/1819181[Bug #1819181])
147 * The MARC editor displays a warning when a cataloger attempts to
148 close the tab without saving
149 (https://bugs.launchpad.net/evergreen/+bug/1538678[Bug #1538678])
150 * The MARC editor displays a warning when permissions issues
151 prevent a record from saving
152 (https://bugs.launchpad.net/evergreen/+bug/1693580[Bug #1693580])
153 * The holdings editor saves default values more consistently
154 (https://bugs.launchpad.net/evergreen/+bug/1812900[Bug #1812900])
155 * The flat-text editor now uses a monospace font
156 (https://bugs.launchpad.net/evergreen/+bug/1817601[Bug #1817601])
157 * Statistical categories and their entries are now alphabetized in the
158 holdings editor (Bugs
159 https://bugs.launchpad.net/evergreen/+bug/1744386[Bug #1744386] and
160 https://bugs.launchpad.net/evergreen/+bug/1777184[Bug #1777184])
161 * The holdings editor now lists monograph parts in reverse alphabetical
163 (https://bugs.launchpad.net/evergreen/+bug/1760893[Bug #1760893])
164 * Buckets created from the MARC Batch Import process are now available
165 in the MARC Batch Edit interface
166 (https://bugs.launchpad.net/evergreen/+bug/1440890[Bug #1440890])
167 * The record bucket interface only displays the Merge action when
168 multiple records are selected
169 (https://bugs.launchpad.net/evergreen/+bug/1760599[Bug #1760599])
170 * Fixes an issue with the displayed number of items out
171 (https://bugs.launchpad.net/evergreen/+bug/1770217[Bug #1770217])
176 * Fixes conflicting dependency information caused be the release of
178 (https://bugs.launchpad.net/evergreen/+bug/1830972[Bug #1830972])
179 * Angular grids include several new accessibility features and
181 (https://bugs.launchpad.net/evergreen/+bug/1816480[Bug #1816480])
182 * The menu in the top right corner is now named "Logout and more..."
183 (https://bugs.launchpad.net/evergreen/+bug/1796914[Bug #1796914])
184 * Several dropdown menus now require less scrolling
185 (https://bugs.launchpad.net/evergreen/+bug/1669120[Bug #1669120])
191 * Avoids Internal Server Errors on search result page
192 (https://bugs.launchpad.net/evergreen/+bug/1155706[Bug #1155706])
193 * Double clicking the Place Hold button can no longer result in
195 (https://bugs.launchpad.net/evergreen/+bug/1029601[Bug #1029601])
200 * Adds a more user-friendly interface for boolean filters
201 (https://bugs.launchpad.net/evergreen/+bug/1642337[Bug #1642337])
203 System administration
204 ^^^^^^^^^^^^^^^^^^^^^
206 * Improves consistency in terminology in the Local Administration
208 (https://bugs.launchpad.net/evergreen/+bug/1776913[Bug #1776913])
209 * The Library Settings Editor now displays some example timezones
210 for the lib.timezone setting
211 (https://bugs.launchpad.net/evergreen/+bug/1817332[Bug #1817332])
215 * Fixes an automated test related to translations and internationalization
216 (https://bugs.launchpad.net/evergreen/+bug/1768987[Bug #1768987])
221 * Adds some foreign key functions that may be missing from your database
222 (https://bugs.launchpad.net/evergreen/+bug/1772028[Bug #1772028])
227 We would like to thank the following individuals who contributed code,
228 testing and documentation patches to the 3.2.7 point release of
262 This release contains bug fixes improving on Evergreen 3.2.5.
263 All bug fixes refer to the web staff client unless otherwise specified.
271 * Fixes a compatibility problem with the Item Status screen related to
272 JavaScript arrow functions
273 (https://bugs.launchpad.net/evergreen/+bug/1821196[Bug #1821196])
278 * Fixes a bug in the Booking URL path that failed with newer Apache
279 (https://bugs.launchpad.net/evergreen/+bug/1823387[Bug #1823387])
284 * Fixes a display bug with the patron record Group Members list
285 (https://bugs.launchpad.net/evergreen/+bug/1642036[Bug #1642036])
286 * Fixes title sort on the patron Items Out Screen
287 (https://bugs.launchpad.net/evergreen/+bug/1782014[Bug #1782014])
288 * Fixes a refresh bug on the catalog record Holds View tab when moving between
289 records (https://bugs.launchpad.net/evergreen/+bug/1792188[Bug #1792188])
290 * Fixes the ability to place holds from item buckets
291 (https://bugs.launchpad.net/evergreen/+bug/1806394[Bug #1806394])
296 * Fixes a bug where copy templates would not apply properly
297 (https://bugs.launchpad.net/evergreen/+bug/1788680[Bug #1788680])
298 * Fixes the default cursor focus on the holdings editor
299 (https://bugs.launchpad.net/evergreen/+bug/1752968[Bug #1752968])
300 * Fixes a bug that failed to honor the "Retain empty bib records"
301 (cat.bib.keep_on_empty) setting when transferring items
302 (https://bugs.launchpad.net/evergreen/+bug/1333893[Bug #1333893])
303 * Fixes a bug that failed to include deleted bib records in TCN search
304 (https://bugs.launchpad.net/evergreen/+bug/1813633[Bug #1813633])
306 System administration
307 ^^^^^^^^^^^^^^^^^^^^^
309 * Added database indexes to speed up purging of Action Trigger event output
310 fields (https://bugs.launchpad.net/evergreen/+bug/1778940[Bug #1778940])
311 * Fixes the help text in action_trigger_aggregator.pl related to the remote-acct
312 argument (https://bugs.launchpad.net/evergreen/+bug/1803729[Bug #1803729])
313 * Adds a missing page title for the Closed Dates Editor
314 (https://bugs.launchpad.net/evergreen/+bug/1814943[Bug #1814943])
315 * Adds a missing page title for the Statistical Popularity Badges admin page
316 (https://bugs.launchpad.net/evergreen/+bug/1826890[Bug #1826890])
321 We would like to thank the following individuals who contributed code,
322 testing and documentation patches to the 3.2.6 point release of
331 * Blake Graham-Henderson
349 This release contains bug fixes improving on Evergreen 3.2.4.
350 All bug fixes refer to the web staff client unless otherwise specified.
358 * Improves the web client splash screen by linking the images along with their links
359 (https://bugs.launchpad.net/evergreen/+bug/1802662[Bug #1802662])
364 * Allows the Title Hold screen to remember previously selected pickup library
365 (https://bugs.launchpad.net/evergreen/+bug/1665534[Bug #1665534])
366 * Sorting improvements for printing the Holds Pull List
367 (https://bugs.launchpad.net/evergreen/+bug/1749502[Bug #1749502])
368 * Better display for non-catalogued checkouts in the offline checkout preview
369 pane (https://bugs.launchpad.net/evergreen/+bug/1818576[Bug #1818576])
374 * Fixes a bug that changed subfield order in bib record after editing a linked
375 authority (https://bugs.launchpad.net/evergreen/+bug/712490[Bug #712490])
376 * Allows opening multiple selected items in Item Status screen from the Holdings
377 View (https://bugs.launchpad.net/evergreen/+bug/1734775[Bug #1734775])
378 * Adds missing "Deleted?" column choice to Record Buckets
379 (https://bugs.launchpad.net/evergreen/+bug/1746360[Bug #1746360])
380 * Fixes the batch Call Number label field on the Call Number editor to populate
381 from the MARC record (https://bugs.launchpad.net/evergreen/+bug/1793196[Bug
383 * Fixes a bug to allow editing the call number label for some but not all
384 attached items (https://bugs.launchpad.net/evergreen/+bug/1794588[Bug
386 * Fixes the sort order of Parts on the Holdings View
387 (https://bugs.launchpad.net/evergreen/+bug/1800178[Bug #1800178])
388 * Adds missing action "Find Originating Acquisition" to Cataloging actions menu
389 (https://bugs.launchpad.net/evergreen/+bug/1705497[Bug #1705497])
390 * Keeps the Item Status screen updated after editing items
391 (https://bugs.launchpad.net/evergreen/+bug/1721109[Bug #1721109])
392 * Fixes a bug with the "checked" state of the Item note "Public Note" checkbox
393 (https://bugs.launchpad.net/evergreen/+bug/1778571[Bug #1778571])
394 * Fixes a bug with Item Alert counts in the Holdings view
395 (https://bugs.launchpad.net/evergreen/+bug/1798628[Bug #1798628])
396 * Improved display when merging bib records from a bucket (side by side, with
397 optional holdings) (https://bugs.launchpad.net/evergreen/+bug/1739293[Bug
399 * Fixes issues where edits to MARC records would fail to save during merge
400 (https://bugs.launchpad.net/evergreen/+bug/1776736[Bug #1776736])
402 System administration
403 ^^^^^^^^^^^^^^^^^^^^^
405 * Web client (websocket) logins are now properly tracked as user activity
406 (https://bugs.launchpad.net/evergreen/+bug/1818153[Bug #1818153])
407 * Fixes some log warnings related to Holds Depth
408 (https://bugs.launchpad.net/evergreen/+bug/1667497[Bug #1667497])
409 * Fixes a bug in the fine generator related to Bookings
410 (https://bugs.launchpad.net/evergreen/+bug/1819796[Bug #1819796])
411 * Fixes the Group Penalty Threshold link under the Local Administration menu
412 (https://bugs.launchpad.net/evergreen/+bug/1812389[Bug #1812389])
413 * Fixes a typo in seed data and all related PO files for translation
414 (https://bugs.launchpad.net/evergreen/+bug/1759238[Bug #1759238])
415 * Fixes an error in the sitemap_generator script when using the shortname
416 parameter (https://bugs.launchpad.net/evergreen/+bug/1808006[Bug #1808006])
421 We would like to thank the following individuals who contributed code,
422 testing and documentation patches to the 3.2.5 point release of
454 This release contains bug fixes improving on Evergreen 3.2.3.
455 All bug fixes refer to the web staff client unless otherwise specified.
463 * Adds appropriate alt text to the Evergreen splash page (https://bugs.launchpad.net/evergreen/+bug/1802594[Bug #1802594])
464 * The public catalog search box now only autofocuses when searching is the main purpose of the page (https://bugs.launchpad.net/evergreen/+bug/1796225[Bug #1796225])
469 * Fixes an issue that prevented purchase orders to not open in a new tab (https://bugs.launchpad.net/evergreen/+bug/1813290[Bug #1813290])
474 * The Billing History grids now save their configuration in the database (https://bugs.launchpad.net/evergreen/+bug/1806709[Bug #1806709])
479 * Catalogers can now set the Bib Source in the Z39.50 Overlay and Import interfaces (https://bugs.launchpad.net/evergreen/+bug/1727345[Bug #1727345])
480 * Fixes an issue where publishers display in the publication date column in copy buckets (https://bugs.launchpad.net/evergreen/+bug/1812698[Bug #1812698])
481 * Electronic reources no longer display a call number called _##URI##_ in the Volume Editor (https://bugs.launchpad.net/evergreen/+bug/1752665[Bug #1752665])
482 * Spine/pocket label templates can now include circulation library and owning library (https://bugs.launchpad.net/evergreen/+bug/1726568[Bug #1726568])
488 * Fixes an issue where external documentation links can open in the reports module (https://bugs.launchpad.net/evergreen/+bug/1784893[Bug #1784893])
489 * Fixes an issue where publishers display as a publication date in reports (https://bugs.launchpad.net/evergreen/+bug/1812698[Bug #1812698])
494 * Staff users can now set their prefered default Advanced Search pane (https://bugs.launchpad.net/evergreen/+bug/1799963[Bug #1799963])
495 * The public catalog search box now only autofocuses when searching is the main purpose of the page (https://bugs.launchpad.net/evergreen/+bug/1796225[Bug #1796225])
497 System administration
498 ^^^^^^^^^^^^^^^^^^^^^
500 * The _DELETE_COPY_ALERT_ permission no longer needs to be granted on the consortium level (https://bugs.launchpad.net/evergreen/+bug/1783421[Bug #1783421])
505 * The angular client now uses Angular 7 (https://bugs.launchpad.net/evergreen/+bug/1801984[Bug #1801984])
506 * The angular client grid actions can now be disabled depending on the criteria of which rows are selected (https://bugs.launchpad.net/evergreen/+bug/1808268[Bug #1808268])
507 * Angular client pages now display their own titles in the browser tab, rather than _AngEG_ (https://bugs.launchpad.net/evergreen/+bug/1813647[Bug #1813647])
512 We would like to thank the following individuals who contributed code,
513 tests and documentation patches to the 3.2.4 point release of
536 This release contains bug fixes improving on Evergreen 3.2.3.
537 All bug fixes refer to the staff client unless otherwise specified.
545 * Hatch is now deprecated for local data storage. Hatch is
546 still recommended for printing in certain situations.
551 * The new `edi_order_pusher.pl` now only pushes purchase orders
552 with a state of "on-order", to prevent older purchase orders
553 from being unintentionally pushed to vendors.
558 * The Z39.50 and record bucket interfaces now open relevant
559 catalog records in new tabs.
560 * Fixes a bug that prevented batch importing authority records.
561 * The template dropdown in the holdings editor now provides more
562 space to accommodate longer template names.
563 * The drop-down of copy tag types in the Manage Copy Tags dialog
564 now includes the owning library of the copy tag type.
569 * Fixes an issue with recalling checked-out materials.
570 * Added several missing columns to the patron bills grid.
571 * Corrected the display of the Bill Type column in the patron bills grid.
572 * Clarified the names of the "Billing Location" and "Grocery Billing
573 Location" columns in the patron bills grid.
574 * The Bill Full Details grid now includes a billing location column
575 for both circulation and grocery bills, as well as the owning library for
577 * The Billing History transactions grid now remembers any changes that
578 users make to the column settings.
579 * Fixes an issue with printing multiple copies of bills.
580 * Fixes an issue with saving self-registered patron accounts.
581 * Staff can now delete self-registered patron accounts.
583 System administration
584 ^^^^^^^^^^^^^^^^^^^^^
586 * Fixes the marc_stream_importer to be compatible with Vandelay session
588 * Includes an accessibility improvement for the Acquisitions
589 Administration interfaces.
594 We would like to thank the following individuals who contributed code,
595 tests and documentation patches to the 3.2.3 point release of
600 * Andrea Buntz Neiman
618 This release contains bug fixes improving on Evergreen 3.2.1.
619 All bug fixes refer to the web staff client unless otherwise specified.
627 * Fixes a bug that blocked logging in from mobile browsers
628 * Fixes a readability issue with mobile menus
629 * Fixes performance issue related to grid tooltips.
630 * Fixes an issue that caused some grid columns to appear
636 * Improves the functionality of setting a default tab of a bib record
637 * The web client now remembers the most recently selected copy template
638 * Adds help tips to Print Item Labels Settings tab
639 * If you add or edit copies and/or volumes from the Holdings View tab,
640 the view now automatically refreshes to show your changes.
641 * Provides an upgrade to MODS 3.3 for older Evergreen installations.
642 * Improves usability of Z39.50 MARC View.
648 * Fixes a daylight savings time-related circulation bug.
649 * Fixes a bug that caused deleted items to show up on the holds shelf.
650 * Staff can now place multiple email addresses into the patron registration/
651 edit form, depending on the value of the `ui.patron.edit.au.email.regex`
653 * Fixes an issue with the offline circulation module.
654 * When merging two users, the non-lead account is now completely purged from
655 the database, rather than simply being marked as deleted.
656 * Fixes a bug which prevented the canceling of holds from the title
662 * Removes incorrect copy counts from metarecord search results pages
663 * Electronic resources now display in the browse interfaces
664 * Restores ability to request password resets
666 System administration
667 ^^^^^^^^^^^^^^^^^^^^^
669 * The example Apache 2.4 configuration now enables remoteip.
670 * Improves syntax in the fm_idl file.
675 We would like to thank the following individuals who contributed code,
676 tests and documentation patches to the 3.2.2 point release of
700 This release contains bug fixes improving on Evergreen 3.2.0.
705 * Adds several columns to the items out grid.
706 * Adds the ability to copy patron addresses to the clipboard.
707 * Fixes several issues with adding new items and call numbers.
708 * Adds links to catalog records from the query and pending tabs of the Record Buckets interface.
709 * Corrects the date format used in several bucket interfaces.
710 * Adds a loading spinner to interfaces that are embedded in the web staff client via iframe
711 (such as the catalog).
712 * The new Angular 6 interfaces now use the correct favicon.
716 We would like to thank the following individuals who contributed code,
717 tests and documentation patches to the 3.2.1 point release of
738 Disabling of Legacy XUL Staff Client
739 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
740 The legacy XUL staff client is no longer supported in Evergreen
741 3.2.x and the server-side installation no longer supports a
742 direct connection by a version XUL client by default. *All
743 users of Evergreen 3.2.x are strongly urged to complete their
744 switch to the web staff client as part of upgrading to 3.2.x.*
746 Evergreen administrators who for some reason continue to wish
747 to deploy the XUL staff client can do so at their risk by
748 supplying `STAFF_CLIENT_STAMP_ID` during the `make install` step
749 and using `make_release` to create installers for the staff client.
750 However, no community support will be provided for the XUL client.
757 Existing Acquisitions report templates that reference the invoice 'complete'
758 field should be modified to check whether the new close_date field is NOT NULL
761 At deploy time, all invoices with a 'complete' value of TRUE will have their
762 'close_date' field set to NOW. A value is required, since this field is
763 now the source of whether an invoice is open or closed.
765 However, no values will be applied to the closed_by field for already closed
769 Angular6 Base Application
770 ~~~~~~~~~~~~~~~~~~~~~~~~~
772 System Admin Upgrade Notes
773 ^^^^^^^^^^^^^^^^^^^^^^^^^^
775 Like the AngularJS application, Evergreen releases will come with all
776 web browser staff client code pre-compiled. Admins only need to add an
777 Apache configuration change.
779 Add the following stanza to /etc/apache2/eg_vhost.conf.
782 --------------------------------------------------------------------------
783 RewriteCond %{REQUEST_URI} ^/eg2/
784 RewriteCond %{REQUEST_URI} !^/eg2/([a-z]{2}-[A-Z]{2})/
785 RewriteRule ^/eg2/(.*) https://%{HTTP_HOST}/eg2/en-US/$1 [R=307,L]
787 <Directory "/openils/var/web/eg2/en-US">
788 FallbackResource /eg2/en-US/index.html
790 --------------------------------------------------------------------------
792 For multi-locale sites, see the bottom section of
793 Open-ILS/examples/apache[_24]/eg_vhost.conf.in for a sample fr-CA
794 configuration. The section starts with "/eg2/ client setup and locale
797 Developer Upgrade Notes
798 ^^^^^^^^^^^^^^^^^^^^^^^
800 Developers building Angular code on existing installations need to update
801 their version of NodeJS by re-running the -developer prereqs installer.
804 --------------------------------------------------------------------------
805 sudo make -f Open-ILS/src/extras/Makefile.install <osname>-developer
806 --------------------------------------------------------------------------
809 Asynchronous Vandelay Imports
810 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
812 Users of NGINX as a reverse proxy may need to set a suitable
813 `client_max_body_size` value in the NGINX configuration so that large
814 MARC record uploads are not truncated. Note that this would have
815 always been necessary, but since this feature allows larger files
816 to be more reliably queued and imported, the need to set `client_max_body_size`
817 became more apparent.
820 Browser Client Settings & Preferences Stored on the Server
821 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
823 A new permission APPLY_WORKSTATION_SETTING has been added to control who
824 may apply values to workstation settings. Use something like the following
825 to apply the permission to all staff accounts (mileage may vary):
828 --------------------------------------------------------------------------
829 INSERT INTO permission.grp_perm_map (grp, perm, depth)
831 (SELECT id FROM permission.grp_tree WHERE name = 'Staff'), -- name may vary
832 (SELECT id FROM permission.perm_list WHERE code =
833 'APPLY_WORKSTATION_SETTING'),
836 --------------------------------------------------------------------------
838 Workstation setting types matching values previously stored in the browser
839 (via localStorage or Hatch) are created as part of this feature. During
840 upgrade, admins should consider whether any of these new setting types
841 should be transferred to user and/or org unit settings instead. Setting
842 type changes can be made at any time, but when a setting type is deleted
843 all of its data is deleted, so a change in type means re-applying the
844 settings in the browser client.
846 Values stored in the browser will automatically migrate to server settings
847 as each setting is accessed in the browser client. Once migrated, the
848 in-browser copies are deleted.
850 If a setting type does not exist where the browser expects one, the
851 value is stored in-browser instead and a warning is issued in the console.
863 Auto-Cancel Line items When All Copies Are Canceled
864 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
865 When a copy (line item detail) is canceled through the Acquisitions interface,
866 the parent line item is also canceled if all copies for that line item are also
867 canceled. The cancel reason given will come from:
869 . The cancel reason for the just-canceled copy if it's a Keep Debits true
871 . The cancel reason from any other copy on the lineitem that has a Keep
872 Debits true cancel reason.
873 . The cancel reason for the just-canceled copy if no copies have a Keep
874 Debits true cancel reason.
877 Invoice Closed Date and Closed By Fields
878 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
879 Acquisitions invoices have 2 new fields:
881 * Close Date -- This is set to the time when the ACQ user clicks the "Close"
882 button in the invoice interface.
883 ** This field 'replaces' the existing 'complete' field. An invoice is
884 considered complete if a close date value is set.
885 * Closed By -- This is set to the logged in staff user who performs the
888 As with the now-defunct 'complete' field, but new fields are cleared in the
889 event an invoice is reopened.
891 These new fields are visible in the invoice interface under the
892 'Show Details' action for closed invoices.
894 Upgrading Invoice Reports
895 +++++++++++++++++++++++++
897 Existing report templates that reference the invoice 'complete' field
898 should be modified to check whether the new close_date field is NOT NULL
901 Other Upgrade Considerations
902 ++++++++++++++++++++++++++++
904 At deploy time, all invoices with a 'complete' value of TRUE will have their
905 'close_date' field set to NOW. A value is required, since this field is
906 now the source of whether an invoice is open or closed.
908 However, no values will be applied to the closed_by field for already closed
913 Patron Acquisitions Requests
914 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
916 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.
923 Hold Targeter Script has been Replaced
924 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
926 The original hold_targeter.pl script has been renamed to
927 "hold_targeter_legacy.pl", and the new-style hold targeting
928 script has been renamed to "hold_targeter.pl". Administrators
929 will want to change their crontab files to reflect this.
933 ---------------------------------------------------------------------
934 -*/15 * * * * . ~/.bashrc && $EG_BIN_DIR/hold_targeter.pl $SRF_CORE
935 ---------------------------------------------------------------------
939 -----------------------------------------------------------------------------------
940 -*/15 * * * * . ~/.bashrc && $EG_BIN_DIR/hold_targeter.pl --osrf-config
942 -----------------------------------------------------------------------------------
944 The sample crontab file at `Open-ILS/examples/crontab.example` reflects
952 Angular6 Base Application
953 ^^^^^^^^^^^^^^^^^^^^^^^^^
954 With Evergreen 3.2, we introduce the initial infrastructure for
955 migrating to a new version of Angular. The structure of the new code
956 is quite different from the AngularJS code and it runs as a separate
957 application which communicates with the AngularJS app via shared storage
958 and in-page URLs that link back and forth between the two.
960 For this release, users will only be directed to the new Angular site
961 when navigating to Administration => Acquisitions Administration. Once
962 on this page, some of the admin interfaces will presented as Angular6
963 interfaces, while others will direct users back to the AngularJS
964 application. The Angular6 interfaces are the simpler, grid-based
967 Acquisitions Admin Angular6 Interfaces
968 ++++++++++++++++++++++++++++++++++++++
973 * Claim Policy Actions
981 * Invoice Payment Method
983 * Line Item MARC Attribute Definitions
985 System Admin Upgrade Notes
986 ++++++++++++++++++++++++++
988 Like the AngularJS application, Evergreen releases will come with all
989 web browser staff client code pre-compiled. Admins only need to add an
990 Apache configuration change.
992 Add the following stanza to /etc/apache2/eg_vhost.conf.
995 --------------------------------------------------------------------------
996 RewriteCond %{REQUEST_URI} ^/eg2/
997 RewriteCond %{REQUEST_URI} !^/eg2/([a-z]{2}-[A-Z]{2})/
998 RewriteRule ^/eg2/(.*) https://%{HTTP_HOST}/eg2/en-US/$1 [R=307,L]
1000 <Directory "/openils/var/web/eg2/en-US">
1001 FallbackResource /eg2/en-US/index.html
1003 --------------------------------------------------------------------------
1005 For multi-locale sites, see the bottom section of
1006 Open-ILS/examples/apache[_24]/eg_vhost.conf.in for a sample fr-CA
1007 configuration. The section starts with "/eg2/ client setup and locale
1010 Developer Upgrade Notes
1011 +++++++++++++++++++++++
1013 Developers building Angular code on existing installations need to update
1014 their version of NodeJS by re-running the -developer prereqs installer.
1017 --------------------------------------------------------------------------
1018 sudo make -f Open-ILS/src/extras/Makefile.install <osname>-developer
1019 --------------------------------------------------------------------------
1025 Add UPC to z39.50 search for OCLC and LOC
1026 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1027 Add UPC as a search attribute for both OCLC and LOC targets in
1028 z39.50 for cataloging.
1031 Asynchronous Vandelay Imports
1032 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1034 Vandelay imports are now monitored from the browser client asynchronously,
1035 meaning the client requests updates from the server instead of waiting for
1036 the server to respond to the original import request. This changes allows
1037 for incremental progress updates in the browser client.
1042 This adds a new database table vandelay.session_tracker for tracking
1043 in-progress vandelay upload activity. A new tracker row is added for
1044 each of "upload", "enqueue", and "import" actions, linked for a given
1045 session by the value stored in the "session_key" field.
1047 The table tracks other potentially useful data, like the staff member
1048 and workstation where the action was performed.
1052 Users of NGINX as a reverse proxy may need to set a suitable
1053 `client_max_body_size` value in the NGINX configuration so that large
1054 MARC record uploads are not truncated. Note that this would have
1055 always been necessary, but since this feature allows larger files
1056 to be more reliably queued and imported, the need to set `client_max_body_size`
1057 became more apparent.
1062 Support for Last Inventory Date
1063 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1064 Evergreen now provides an option to add an inventory date to items to facilitate
1065 the process of performing inventory in libraries. Staff can add an inventory
1066 date to an item in one of the following ways:
1067 * From the check in screen, there is now an Update Inventory check in modifier.
1068 When selected, scanned barcodes will have the current date/time added as the
1069 inventory date while the item is checked in.
1070 * From the Item Status screen, an action is available to add the current
1071 date/time as the inventory date to selected items.
1073 This new feature will also store the workstation that was used when the
1074 inventory date was updated.
1078 Parallel Ingest with pingest.pl
1079 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1080 A program named pingest.pl is now installed to allow faster bibliographic record
1081 ingest. It performs ingest in parallel so that multiple batches can
1082 be done simultaneously. It operates by splitting the records to be
1083 ingested up into batches and running all of the ingest methods on each
1084 batch. You may pass in options to control how many batches are run at
1085 the same time, how many records there are per batch, and which ingest
1088 NOTE: The browse ingest is presently done in a single process over all
1089 of the input records as it cannot run in parallel with itself. It
1090 does, however, run in parallel with the other ingests.
1092 Command Line Options
1093 ++++++++++++++++++++
1094 pingest.pl accepts the following command line options:
1097 The server where PostgreSQL runs (either host name or IP address).
1098 The default is read from the PGHOST environment variable or
1102 The port that PostgreSQL listens to on host. The default is read
1103 from the PGPORT environment variable or 5432.
1106 The database to connect to on the host. The default is read from
1107 the PGDATABASE environment variable or "evergreen."
1110 The username for database connections. The default is read from
1111 the PGUSER environment variable or "evergreen."
1114 The password for database connections. The default is read from
1115 the PGPASSWORD environment variable or "evergreen."
1118 Number of records to process per batch. The default is 10,000.
1121 Max number of worker processes (i.e. the number of batches to
1122 process simultaneously). The default is 8.
1129 Skip the selected reingest component.
1132 Start processing at this record ID.
1135 Stop processing when this record ID is reached.
1138 Read record IDs to reingest from standard input. This option
1139 conflicts with --start-id and/or --end-id.
1142 Stop processing after this many total seconds have passed. The
1143 default is to run until all records have been processed.
1150 View Authority Record by Database ID
1151 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1153 A new interface allows catalogers to retrieve a specific
1154 authority record using its database ID. Catalogers can
1155 find those IDs in subfield $0 of matching fields in
1156 bibliographic records.
1158 To use the new authority record viewer:
1160 . Click *Cataloging -> Retrieve Authority Record by ID*.
1161 . Type in the ID number of the authority record you are
1162 interested in. Don't include any prefixes, just the ID
1165 . View or edit the authority record as needed.
1174 Autorenewal of Loans
1175 ^^^^^^^^^^^^^^^^^^^^
1176 Circulation policies in Evergreen can now be configured to automatically renew
1177 certain items checked out on patron accounts. Circulations will be renewed
1178 automatically up to a custom limit (the `max_auto_renewal` field) and patrons
1179 will not need to log in to their OPAC accounts or ask library staff to manually
1182 Two new action triggers have been added to Evergreen that permit the Auto-Renew
1183 feature. They can be found, configured, and enabled in Administration>Local
1184 Administration>Notifications/Action Triggers. They are named **Autorenew** and
1185 **AutorenewNotify**.
1187 The **Autorenew** A/T definition uses the `checkout.due` hook to automatically
1188 validate and renew (in the reactor) circulations on the day they are due,
1189 grouped by user. The output events of this definition is is the input used by
1190 the related **AutorenewNotify** A/T that simply uses a new hook called
1191 `autorenewal` to notify patrons via email of their currently due or
1194 In the webstaff's Patron Items Out page, the new column `AutoRenewalsRemaining`
1195 indicates how many autorenewals are available for a particular circulation.
1201 Emergency Closing Handler
1202 ^^^^^^^^^^^^^^^^^^^^^^^^
1204 Staff are provided with interfaces and mechanisms to create library closings
1205 that, in addition to affecting future circulation and booking due dates, and
1206 hold shelf expirations, will automatically move existing circulation and booking
1207 due dates and hold shelf expiration times. This new functionality is
1208 conceptually described as Emergency Closings and business logic implementing it
1209 as the Emergency Closing Handler. It contains additions and adjustments to the
1210 user interface, business logic, and database layers. Access to this
1211 functionality is available through the Closed Dates Editor interface in the
1212 staff client which has been ported to AngularJS.
1217 This development has created new business logic code to inspect, in real time,
1218 existing circulation, booking, and hold records, and modify such date and time
1219 stamps so that the circulation, booking, or hold will end in the same state it
1220 would have if the closing had existed at the time the circulation or booking
1221 occurred, or the hold was placed and captured. Of specific note, hourly loans
1222 will have their due date adjusted to be the end of the day following the
1225 When the Emergency Closing is saved, any fines accrued during the closing may be
1226 voided, as settings dictate, with the exception of circulations that have been
1227 marked as LOST or LONG OVERDUE. That is, even for LOST and LONG OVERDUE
1228 circulations with due dates that fall within the Emergency Closing, no fine
1229 adjustment will be applied. Emergency Closing processing is permanent, and
1230 cannot be rolled back.
1232 This functionality is explicitly initiated by staff action. If staff do not
1233 request an Emergency Closing, existing circulations, bookings, and holds will
1234 not be processed and adjusted. However, if staff request any Closing that starts
1235 nearer in time than the length of the longest circulation duration configured
1236 for use in the Evergreen instance they will be prompted with the option to
1237 create the closing as an Emergency Closing.
1239 Action/Trigger hooks have been created for circulations and bookings that are
1240 adjusted by the Emergency Closing Handler. These will facilitate the creation of
1241 notifications to patrons that the due date has changed and to alert them to
1242 potential changes in accrued fines.
1244 Booking start dates are explicitly ignored in this implementation. Because an
1245 Emergency Closing is, by its nature, an unexpected event, it will be up to staff
1246 to address any bookings which intersect with a new Emergency Closings. Reports
1247 can be used to identify booking start dates that overlap with a closing and that
1248 may require staff intervention.
1250 Staff requesting and Emergency Closing must have the new EMERGENCY_CLOSING
1251 permission. Some text describing the feature.
1257 Patron Preferred Name and Name Search Keywords
1258 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1263 Adds a new set of patron preferred name fields for prefix, first,
1264 middle, last, and suffix allowing patrons to provide preferred name
1265 information. Preferred names are optional and each acts as an overlay
1266 to the analogous primary name field, making it possible to provide
1267 preferred name values for individual fields.
1269 For example, a patron named William Erickson may have a preferred first
1270 name (pref_first_given_name) of Bill, in which case the preferred name
1271 would be Bill Erickson. Note a preferred last name is not required in
1272 this case as the code uses primary name values as defaults when not
1273 replaced with a preferred version.
1275 * Patrons will see primary names displayed in the catalog when set.
1276 * Staff will see both primary name and preferred name in the patron
1278 * Patron searches for any given name field will search both the primary
1279 and preferred name data.
1280 * Preferred name fields are available in Action/Trigger templates and
1281 are present in various patron-focused print templates.
1286 Adds a new field to store miscellaneous patron name search terms. These
1287 values are only for searching and do not appear in any interfaces, apart
1288 from the patron summary side bar and the patron edit UI.
1290 Included is a new search field in the patron search UI which searches
1291 keyword values and all other name fields. It's essentially a global patron
1292 name keyword search.
1300 Disabling of legacy XUL staff client
1301 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1302 The legacy XUL staff client is no longer supported in Evergreen
1303 3.2.x and the server-side installation no longer supports a
1304 direct connection by a version XUL client by default. All
1305 users of Evergreen 3.2.x are strongly urged to complete their
1306 switch to the web staff client as part of upgrading to 3.2.x.
1308 Evergreen administrators who for some reason continue to wish
1309 to deploy the XUL staff client can do so at their risk by
1310 supplying `STAFF_CLIENT_STAMP_ID` during the `make install` step
1311 and using `make_release` to create installers for the staff client.
1312 However, no community support will be provided for the XUL client.
1317 Permission Group Display Entries
1318 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1319 In some cases, it is useful to have the ability to reorder permission, or to make
1320 only specific groups available in the permission group selector for specific
1321 Org Units. An interface has been made available to allow this.
1323 Group Tree Display Entry Interface
1324 ++++++++++++++++++++++++++++++++++
1326 Permission Group Display Entries can be reordered, added, or removed via
1327 _Administration -> Local Admin -> Permission Tree Display Entries_.
1328 Select the Org Unit you wish to edit the entries in.
1330 Entries may be added using the Add functionality, creating entries based
1331 on permission groups that have not been added to the tree for the Org
1332 Unit you wish to add them to.
1334 image::media/pgtde_01.png[Group Tree Display Entry Admin UI]
1338 Moving an entry will shift its position up or down in the patron profile
1339 selector for a given Org Unit.
1342 * Press either the *Move Up* or *Move Down* button. The entry will be
1343 moved up or down, accordingly.
1344 * Click *Save* to save your edits.
1346 NOTE: You may only move up or down entries that have sibling entries.
1350 If you want a particular Org Unit to not have access to specific
1351 entries, you may remove an entry. Removing an entry will remove it from
1352 view. The entry will be removed from the database.
1354 * Select an entry and press the *Remove* button.
1358 You may add entries from permission groups that are not currently
1359 reflected in the permission group tree. This is useful for moving
1360 entries to different parents, or making them root entries.
1362 image::media/pgtde_02.png[Add Entry modal]
1364 * If desired, select an entry to be used as the parent entry.
1365 * Press the *Add* button.
1366 * Select a permission group from the dropdown.
1367 * If you've selected a parent entry, you may check the *Add Root Entry*
1368 box to override that parent and add the entry on the root level.
1369 * If you did not select a parent entry, the entry will be added on the root
1374 Browser Client Settings & Preferences Stored on the Server
1375 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1376 Browser client settings and preferences that should persist over time are
1377 now stored as settings on the server. This allows settings to follow
1378 users and workstations and reduces problems associated with losing settings
1379 as a result of clearing browser data.
1381 The browser client honors setting values stored as user settings, workstation
1382 settings, and org unit settings, depending on which setting types are
1388 * No setting can be both a user and workstation setting. They are mutually
1390 * Any setting can be an org unit setting in addition to being a user or
1391 workstation setting.
1396 Read-only settings are useful for defining values that staff can use but
1397 not modify. For example, admins may wish to prevent users from locally
1398 modifying the grid configuration for a given interface so it remains
1399 consistent for all users.
1401 A setting is read-only when an org unit setting type exists (regardless of
1402 whether a value is applied) and no user or workstation setting type exists.
1404 Server-Stored Workstation Settings Workstation Admin View
1405 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1407 There's a new "Server Workstation Prefs" tab to the stored preferences
1408 workstation admin interface. From here, users can view which
1409 preferences are stored as server-stored workstation preferences and
1410 delete select values.
1415 A new permission APPLY_WORKSTATION_SETTING has been added to control who
1416 may apply values to workstation settings. Use something like the following
1417 to apply the permission to all staff accounts (mileage may vary):
1420 --------------------------------------------------------------------------
1421 INSERT INTO permission.grp_perm_map (grp, perm, depth)
1423 (SELECT id FROM permission.grp_tree WHERE name = 'Staff'), -- name may vary
1424 (SELECT id FROM permission.perm_list WHERE code = 'APPLY_WORKSTATION_SETTING'),
1427 --------------------------------------------------------------------------
1429 Workstation setting types matching values previously stored in the browser
1430 (via localStorage or Hatch) are created as part of this feature. During
1431 upgrade, admins should consider whether any of these new setting types
1432 should be transferred to user and/or org unit settings instead. Setting
1433 type changes can be made at any time, but when a setting type is deleted
1434 all of its data is deleted, so a change in type means re-applying the
1435 settings in the browser client.
1437 Values stored in the browser will automatically migrate to server settings
1438 as each setting is accessed in the browser client. Once migrated, the
1439 in-browser copies are deleted.
1441 If a setting type does not exist where the browser expects one, the
1442 value is stored in-browser instead and a warning is issued in the console.
1445 More consistent terminology in the client
1446 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1447 Terminology has been updated in the staff client so that we consistently use
1448 the same name to describe the same thing. The following updates have been made:
1450 * The term 'item' is now consistently used to describe the barcoded entity
1451 that had been previously been called both an 'item' and a 'copy'. As a result,
1452 we now use the terms 'item buckets', 'item tags', and 'item alerts'.
1453 * The term 'volume' is no longer used in the client, with the exception of
1454 serials, where the term is used to describe serial volumes. The term 'call
1455 number' will replace volume in most other places.
1456 * 'Holdings' is a more general term used to describe a combination of items
1458 * The term 'Shelving Location' is used consistently in favor of 'Copy
1469 Batch Actions In the Public Catalog
1470 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1471 The public catalog now displays checkboxes on the bibliographic and
1472 metarecord constituents results pages. Selecting one or more titles
1473 by using the checkboxes will dynamically add those title to the
1474 temporary list, which is now renamed the cart.
1476 Above the results lists there is now a bar with a select-all checkbox,
1477 a link to the cart management page that also indicates the number of
1478 of titles in the cart, and a link to remove from the cart titles that
1479 are selected on the currently displayed results page.
1481 The search bar now includes an icon of a cart and displays the number
1482 of titles currently in the cart. Next to that icon is a menu of cart
1485 The cart actions available are Place Hold, Print Title Details,
1486 Email Title Details, Add Cart to Saved List, and Clear Cart. In the
1487 web staff client, the cart actions also include Add Cart to Bucket.
1488 When an action is selected from this menu, the user is given an
1489 opportunity to confirm the action and to optionally empty the cart
1490 when the action is complete. The action is applied to all titles
1493 Clicking on the cart icon brings the user to a page listing the
1494 titles in the cart. From there, the user can select specific records
1495 to request, print, email, add to a list, or remove from the cart.
1497 The list of actions on the record details page now provides separate
1498 links for adding the title to a cart or to a permanent list.
1500 The permanent list management page in the public catalog now also
1501 includes batch print and email actions.
1503 Additional information
1504 ++++++++++++++++++++++
1505 * The checkboxes do not display on the metarecord results page, as
1506 metarecords currently cannot be put into carts or lists.
1507 * The checkboxes are displayed only if JavaScript is enabled. However,
1508 users can still add items to the cart and perform batch actions on
1509 the cart and on lists.
1510 * A template `config.tt2` setting, `ctx.max_cart_size`, can be used to
1511 set a soft limit on the number of titles that can be added to the
1512 cart. If this limit is reached, checkboxes to add more records to the
1513 cart are disabled unless existing titles in the cart are removed
1514 first. The default value for this setting is 500.
1519 This patch adds to the public catalog two routes that return JSON
1522 * `GET /eg/opac/api/mylist/add?record=45`
1523 * `GET /eg/opac/api/mylist/delete?record=45`
1525 The JSON response is a hash containing a mylist key pointing to the list
1526 of bib IDs of contents of the cart.
1528 The record parameter can be repeated to allow adding or removing
1529 records as an atomic operation. Note that this change also now available
1530 to `/eg/opac/mylist/{add,delete}`
1532 More generally, this adds a way for EGWeb context loaders to specify that
1533 a response should be emitted as JSON rather than rendering an HTML
1534 page using `Template::Toolkit`.
1536 Specifically, if the context as munged by the context loader contains
1537 a `json_response` key, the contents of that key will to provide a
1538 JSON response. The `json_response_cookie` key, if present, can be used
1539 to set a cookie as part of the response.
1541 Template Toolkit processing is bypassed entirely when emitting a JSON
1542 response, so the context loader would be entirely responsible for
1543 localization of strings in the response meant for direct human
1549 New class for searchbar when on the homepage
1550 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1552 This adds the `.searchbar-home` class to the div that contains the searchbar
1553 when on the homepage. This allows sites to customize the searchbar differently
1554 on the homepage than in other places the search bar appears (for example,
1555 offering a large, Google-style search bar on the homepage only).
1560 To make customization easier, the username hint on the OPAC login page ("Please
1561 include leading zeros...") has been moved to a separate TT2 template. If you
1562 have customized the hint text, you will need to add your modifications to
1569 The Evergreen project would like to acknowledge the following
1570 organizations that commissioned developments in this release of
1573 * BC Libraries Cooperative
1574 * Consortium Of Ohio Libraries
1576 * Georgia Public Library Service
1577 * Indiana State Library
1578 * Lake Agassiz Regrional Library
1580 * North Texas Library Consortium
1581 * Northwest Regional Library
1582 * Pennsylvania Integrated Library System
1583 * South Carolina State Library
1585 We would also like to thank the following individuals who contributed
1586 code, translations, documentations patches and tests to this release of
1591 * Andrea Buntz Neiman
1600 * Blake Graham-Henderson
1601 * Francisco J Guel-Mendoza
1619 We also thank the following organizations whose employees contributed
1622 * BC Libraries Cooperative
1625 * Equinox Open Library Initiative
1626 * Government of Manitoba
1627 * Kenton County Public Library
1628 * King County Library System
1629 * Linn-Benton Community College
1633 We regret any omissions. If a contributor has been inadvertently
1634 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / Evergreen.git / blob