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 * Fixes issue in Bucket grids where grid configurations were not saving correctly (https://bugs.launchpad.net/evergreen/+bug/1805895[Bug# 1805895])
37 * "Local catalog" is now at the top of the list of Z39.50 sources. (https://bugs.launchpad.net/evergreen/+bug/1787676[Bug #1787676])
38 * Fixes issue with authority_control_field.pl script (https://bugs.launchpad.net/evergreen/+bug/1650409[Bug #1650409])
39 * Fixes an issue with the "Retrieve Last Bib Record" action. (https://bugs.launchpad.net/evergreen/+bug/1830424[Bug #1830424])
40 * Fixes an issue with the Edit buttons in the Merge Records interface. (https://bugs.launchpad.net/evergreen/+bug/1836229[Bug #1836229])
41 * Fixes an issue with the _Clear_ button in the holdings template editor. (https://bugs.launchpad.net/evergreen/+bug/1803584[Bug #1803584])
47 * Fixes slowness issues with checkin and checkout grids (https://bugs.launchpad.net/evergreen/+bug/1777207[Bug #1777207])
48 * Fixes an issue that allowed staff to renew items to dates in the past. (https://bugs.launchpad.net/evergreen/+bug/1034058[Bug #1034058])
49 * 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])
50 * 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])
51 * 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])
56 * Updates to the Angular client's .editorconfig file. (https://bugs.launchpad.net/evergreen/+bug/1838136[Bug #1838136])
61 * Accessibility improvements to form fields. (https://bugs.launchpad.net/evergreen/+bug/1735768[Bug #1735768])
66 * Users can now hard code a list of filter values in a report template (https://bugs.launchpad.net/evergreen/+bug/1785061[Bug #1785061])
67 * 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])
68 * Fixes column type for Billing Totals and Billing Paid columns (https://bugs.launchpad.net/evergreen/+bug/1681930[Bug #1681930])
73 We would like to thank the following individuals who contributed code,
74 testing and documentation patches to the 3.2.8 point release of
106 This release contains bug fixes improving on Evergreen 3.2.6.
107 All bug fixes refer to the web staff client unless otherwise specified.
114 * Corrects a rounding error that caused fines to exceed the max fines
116 (https://bugs.launchpad.net/evergreen/+bug/1704819[Bug #1704819])
117 * Corrects an issue with printing Items Out receipts
118 (https://bugs.launchpad.net/evergreen/+bug/1790896[Bug #1790896])
119 * SIP Visa payments are now recorded as credit card, rather than cash
121 (https://bugs.launchpad.net/evergreen/+bug/1796942[Bug #1796942])
122 * Converting change to patron credit no longer requires staff members
123 to refresh the screen to see the new credit
124 (https://bugs.launchpad.net/evergreen/+bug/1775639[Bug #1775639])
125 * The patron summary now includes tooltips that were available in
127 (https://bugs.launchpad.net/evergreen/+bug/1772206[Bug #1772206])
128 * The patron holds grid now includes a SMS Carrier column
129 (https://bugs.launchpad.net/evergreen/+bug/1748265[Bug #1748265])
130 * When registering a new patron from Pending Patrons, the address
131 type dropdown now supports a default value
132 (https://bugs.launchpad.net/evergreen/+bug/1816180[Bug #1816180])
133 * The Items Out grid now includes a Monograph Parts column
134 (https://bugs.launchpad.net/evergreen/+bug/1789257[Bug #1789257])
135 * The annotate checkbox on the bill payment screen is now sticky
136 (https://bugs.launchpad.net/evergreen/+bug/1759343[Bug #1759343])
137 * Group member details grid settings can now be saved
138 (https://bugs.launchpad.net/evergreen/+bug/1774707[Bug #1774707])
139 * The patron registration date of birth field can now display a
141 (https://bugs.launchpad.net/evergreen/+bug/1819181[Bug #1819181])
146 * The MARC editor displays a warning when a cataloger attempts to
147 close the tab without saving
148 (https://bugs.launchpad.net/evergreen/+bug/1538678[Bug #1538678])
149 * The MARC editor displays a warning when permissions issues
150 prevent a record from saving
151 (https://bugs.launchpad.net/evergreen/+bug/1693580[Bug #1693580])
152 * The holdings editor saves default values more consistently
153 (https://bugs.launchpad.net/evergreen/+bug/1812900[Bug #1812900])
154 * The flat-text editor now uses a monospace font
155 (https://bugs.launchpad.net/evergreen/+bug/1817601[Bug #1817601])
156 * Statistical categories and their entries are now alphabetized in the
157 holdings editor (Bugs
158 https://bugs.launchpad.net/evergreen/+bug/1744386[Bug #1744386] and
159 https://bugs.launchpad.net/evergreen/+bug/1777184[Bug #1777184])
160 * The holdings editor now lists monograph parts in reverse alphabetical
162 (https://bugs.launchpad.net/evergreen/+bug/1760893[Bug #1760893])
163 * Buckets created from the MARC Batch Import process are now available
164 in the MARC Batch Edit interface
165 (https://bugs.launchpad.net/evergreen/+bug/1440890[Bug #1440890])
166 * The record bucket interface only displays the Merge action when
167 multiple records are selected
168 (https://bugs.launchpad.net/evergreen/+bug/1760599[Bug #1760599])
169 * Fixes an issue with the displayed number of items out
170 (https://bugs.launchpad.net/evergreen/+bug/1770217[Bug #1770217])
175 * Fixes conflicting dependency information caused be the release of
177 (https://bugs.launchpad.net/evergreen/+bug/1830972[Bug #1830972])
178 * Angular grids include several new accessibility features and
180 (https://bugs.launchpad.net/evergreen/+bug/1816480[Bug #1816480])
181 * The menu in the top right corner is now named "Logout and more..."
182 (https://bugs.launchpad.net/evergreen/+bug/1796914[Bug #1796914])
183 * Several dropdown menus now require less scrolling
184 (https://bugs.launchpad.net/evergreen/+bug/1669120[Bug #1669120])
190 * Avoids Internal Server Errors on search result page
191 (https://bugs.launchpad.net/evergreen/+bug/1155706[Bug #1155706])
192 * Double clicking the Place Hold button can no longer result in
194 (https://bugs.launchpad.net/evergreen/+bug/1029601[Bug #1029601])
199 * Adds a more user-friendly interface for boolean filters
200 (https://bugs.launchpad.net/evergreen/+bug/1642337[Bug #1642337])
202 System administration
203 ^^^^^^^^^^^^^^^^^^^^^
205 * Improves consistency in terminology in the Local Administration
207 (https://bugs.launchpad.net/evergreen/+bug/1776913[Bug #1776913])
208 * The Library Settings Editor now displays some example timezones
209 for the lib.timezone setting
210 (https://bugs.launchpad.net/evergreen/+bug/1817332[Bug #1817332])
214 * Fixes an automated test related to translations and internationalization
215 (https://bugs.launchpad.net/evergreen/+bug/1768987[Bug #1768987])
220 * Adds some foreign key functions that may be missing from your database
221 (https://bugs.launchpad.net/evergreen/+bug/1772028[Bug #1772028])
226 We would like to thank the following individuals who contributed code,
227 testing and documentation patches to the 3.2.7 point release of
261 This release contains bug fixes improving on Evergreen 3.2.5.
262 All bug fixes refer to the web staff client unless otherwise specified.
270 * Fixes a compatibility problem with the Item Status screen related to
271 JavaScript arrow functions
272 (https://bugs.launchpad.net/evergreen/+bug/1821196[Bug #1821196])
277 * Fixes a bug in the Booking URL path that failed with newer Apache
278 (https://bugs.launchpad.net/evergreen/+bug/1823387[Bug #1823387])
283 * Fixes a display bug with the patron record Group Members list
284 (https://bugs.launchpad.net/evergreen/+bug/1642036[Bug #1642036])
285 * Fixes title sort on the patron Items Out Screen
286 (https://bugs.launchpad.net/evergreen/+bug/1782014[Bug #1782014])
287 * Fixes a refresh bug on the catalog record Holds View tab when moving between
288 records (https://bugs.launchpad.net/evergreen/+bug/1792188[Bug #1792188])
289 * Fixes the ability to place holds from item buckets
290 (https://bugs.launchpad.net/evergreen/+bug/1806394[Bug #1806394])
295 * Fixes a bug where copy templates would not apply properly
296 (https://bugs.launchpad.net/evergreen/+bug/1788680[Bug #1788680])
297 * Fixes the default cursor focus on the holdings editor
298 (https://bugs.launchpad.net/evergreen/+bug/1752968[Bug #1752968])
299 * Fixes a bug that failed to honor the "Retain empty bib records"
300 (cat.bib.keep_on_empty) setting when transferring items
301 (https://bugs.launchpad.net/evergreen/+bug/1333893[Bug #1333893])
302 * Fixes a bug that failed to include deleted bib records in TCN search
303 (https://bugs.launchpad.net/evergreen/+bug/1813633[Bug #1813633])
305 System administration
306 ^^^^^^^^^^^^^^^^^^^^^
308 * Added database indexes to speed up purging of Action Trigger event output
309 fields (https://bugs.launchpad.net/evergreen/+bug/1778940[Bug #1778940])
310 * Fixes the help text in action_trigger_aggregator.pl related to the remote-acct
311 argument (https://bugs.launchpad.net/evergreen/+bug/1803729[Bug #1803729])
312 * Adds a missing page title for the Closed Dates Editor
313 (https://bugs.launchpad.net/evergreen/+bug/1814943[Bug #1814943])
314 * Adds a missing page title for the Statistical Popularity Badges admin page
315 (https://bugs.launchpad.net/evergreen/+bug/1826890[Bug #1826890])
320 We would like to thank the following individuals who contributed code,
321 testing and documentation patches to the 3.2.6 point release of
330 * Blake Graham-Henderson
348 This release contains bug fixes improving on Evergreen 3.2.4.
349 All bug fixes refer to the web staff client unless otherwise specified.
357 * Improves the web client splash screen by linking the images along with their links
358 (https://bugs.launchpad.net/evergreen/+bug/1802662[Bug #1802662])
363 * Allows the Title Hold screen to remember previously selected pickup library
364 (https://bugs.launchpad.net/evergreen/+bug/1665534[Bug #1665534])
365 * Sorting improvements for printing the Holds Pull List
366 (https://bugs.launchpad.net/evergreen/+bug/1749502[Bug #1749502])
367 * Better display for non-catalogued checkouts in the offline checkout preview
368 pane (https://bugs.launchpad.net/evergreen/+bug/1818576[Bug #1818576])
373 * Fixes a bug that changed subfield order in bib record after editing a linked
374 authority (https://bugs.launchpad.net/evergreen/+bug/712490[Bug #712490])
375 * Allows opening multiple selected items in Item Status screen from the Holdings
376 View (https://bugs.launchpad.net/evergreen/+bug/1734775[Bug #1734775])
377 * Adds missing "Deleted?" column choice to Record Buckets
378 (https://bugs.launchpad.net/evergreen/+bug/1746360[Bug #1746360])
379 * Fixes the batch Call Number label field on the Call Number editor to populate
380 from the MARC record (https://bugs.launchpad.net/evergreen/+bug/1793196[Bug
382 * Fixes a bug to allow editing the call number label for some but not all
383 attached items (https://bugs.launchpad.net/evergreen/+bug/1794588[Bug
385 * Fixes the sort order of Parts on the Holdings View
386 (https://bugs.launchpad.net/evergreen/+bug/1800178[Bug #1800178])
387 * Adds missing action "Find Originating Acquisition" to Cataloging actions menu
388 (https://bugs.launchpad.net/evergreen/+bug/1705497[Bug #1705497])
389 * Keeps the Item Status screen updated after editing items
390 (https://bugs.launchpad.net/evergreen/+bug/1721109[Bug #1721109])
391 * Fixes a bug with the "checked" state of the Item note "Public Note" checkbox
392 (https://bugs.launchpad.net/evergreen/+bug/1778571[Bug #1778571])
393 * Fixes a bug with Item Alert counts in the Holdings view
394 (https://bugs.launchpad.net/evergreen/+bug/1798628[Bug #1798628])
395 * Improved display when merging bib records from a bucket (side by side, with
396 optional holdings) (https://bugs.launchpad.net/evergreen/+bug/1739293[Bug
398 * Fixes issues where edits to MARC records would fail to save during merge
399 (https://bugs.launchpad.net/evergreen/+bug/1776736[Bug #1776736])
401 System administration
402 ^^^^^^^^^^^^^^^^^^^^^
404 * Web client (websocket) logins are now properly tracked as user activity
405 (https://bugs.launchpad.net/evergreen/+bug/1818153[Bug #1818153])
406 * Fixes some log warnings related to Holds Depth
407 (https://bugs.launchpad.net/evergreen/+bug/1667497[Bug #1667497])
408 * Fixes a bug in the fine generator related to Bookings
409 (https://bugs.launchpad.net/evergreen/+bug/1819796[Bug #1819796])
410 * Fixes the Group Penalty Threshold link under the Local Administration menu
411 (https://bugs.launchpad.net/evergreen/+bug/1812389[Bug #1812389])
412 * Fixes a typo in seed data and all related PO files for translation
413 (https://bugs.launchpad.net/evergreen/+bug/1759238[Bug #1759238])
414 * Fixes an error in the sitemap_generator script when using the shortname
415 parameter (https://bugs.launchpad.net/evergreen/+bug/1808006[Bug #1808006])
420 We would like to thank the following individuals who contributed code,
421 testing and documentation patches to the 3.2.5 point release of
453 This release contains bug fixes improving on Evergreen 3.2.3.
454 All bug fixes refer to the web staff client unless otherwise specified.
462 * Adds appropriate alt text to the Evergreen splash page (https://bugs.launchpad.net/evergreen/+bug/1802594[Bug #1802594])
463 * 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])
468 * Fixes an issue that prevented purchase orders to not open in a new tab (https://bugs.launchpad.net/evergreen/+bug/1813290[Bug #1813290])
473 * The Billing History grids now save their configuration in the database (https://bugs.launchpad.net/evergreen/+bug/1806709[Bug #1806709])
478 * Catalogers can now set the Bib Source in the Z39.50 Overlay and Import interfaces (https://bugs.launchpad.net/evergreen/+bug/1727345[Bug #1727345])
479 * Fixes an issue where publishers display in the publication date column in copy buckets (https://bugs.launchpad.net/evergreen/+bug/1812698[Bug #1812698])
480 * Electronic reources no longer display a call number called _##URI##_ in the Volume Editor (https://bugs.launchpad.net/evergreen/+bug/1752665[Bug #1752665])
481 * Spine/pocket label templates can now include circulation library and owning library (https://bugs.launchpad.net/evergreen/+bug/1726568[Bug #1726568])
487 * Fixes an issue where external documentation links can open in the reports module (https://bugs.launchpad.net/evergreen/+bug/1784893[Bug #1784893])
488 * Fixes an issue where publishers display as a publication date in reports (https://bugs.launchpad.net/evergreen/+bug/1812698[Bug #1812698])
493 * Staff users can now set their prefered default Advanced Search pane (https://bugs.launchpad.net/evergreen/+bug/1799963[Bug #1799963])
494 * 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])
496 System administration
497 ^^^^^^^^^^^^^^^^^^^^^
499 * The _DELETE_COPY_ALERT_ permission no longer needs to be granted on the consortium level (https://bugs.launchpad.net/evergreen/+bug/1783421[Bug #1783421])
504 * The angular client now uses Angular 7 (https://bugs.launchpad.net/evergreen/+bug/1801984[Bug #1801984])
505 * 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])
506 * Angular client pages now display their own titles in the browser tab, rather than _AngEG_ (https://bugs.launchpad.net/evergreen/+bug/1813647[Bug #1813647])
511 We would like to thank the following individuals who contributed code,
512 tests and documentation patches to the 3.2.4 point release of
535 This release contains bug fixes improving on Evergreen 3.2.3.
536 All bug fixes refer to the staff client unless otherwise specified.
544 * Hatch is now deprecated for local data storage. Hatch is
545 still recommended for printing in certain situations.
550 * The new `edi_order_pusher.pl` now only pushes purchase orders
551 with a state of "on-order", to prevent older purchase orders
552 from being unintentionally pushed to vendors.
557 * The Z39.50 and record bucket interfaces now open relevant
558 catalog records in new tabs.
559 * Fixes a bug that prevented batch importing authority records.
560 * The template dropdown in the holdings editor now provides more
561 space to accommodate longer template names.
562 * The drop-down of copy tag types in the Manage Copy Tags dialog
563 now includes the owning library of the copy tag type.
568 * Fixes an issue with recalling checked-out materials.
569 * Added several missing columns to the patron bills grid.
570 * Corrected the display of the Bill Type column in the patron bills grid.
571 * Clarified the names of the "Billing Location" and "Grocery Billing
572 Location" columns in the patron bills grid.
573 * The Bill Full Details grid now includes a billing location column
574 for both circulation and grocery bills, as well as the owning library for
576 * The Billing History transactions grid now remembers any changes that
577 users make to the column settings.
578 * Fixes an issue with printing multiple copies of bills.
579 * Fixes an issue with saving self-registered patron accounts.
580 * Staff can now delete self-registered patron accounts.
582 System administration
583 ^^^^^^^^^^^^^^^^^^^^^
585 * Fixes the marc_stream_importer to be compatible with Vandelay session
587 * Includes an accessibility improvement for the Acquisitions
588 Administration interfaces.
593 We would like to thank the following individuals who contributed code,
594 tests and documentation patches to the 3.2.3 point release of
599 * Andrea Buntz Neiman
617 This release contains bug fixes improving on Evergreen 3.2.1.
618 All bug fixes refer to the web staff client unless otherwise specified.
626 * Fixes a bug that blocked logging in from mobile browsers
627 * Fixes a readability issue with mobile menus
628 * Fixes performance issue related to grid tooltips.
629 * Fixes an issue that caused some grid columns to appear
635 * Improves the functionality of setting a default tab of a bib record
636 * The web client now remembers the most recently selected copy template
637 * Adds help tips to Print Item Labels Settings tab
638 * If you add or edit copies and/or volumes from the Holdings View tab,
639 the view now automatically refreshes to show your changes.
640 * Provides an upgrade to MODS 3.3 for older Evergreen installations.
641 * Improves usability of Z39.50 MARC View.
647 * Fixes a daylight savings time-related circulation bug.
648 * Fixes a bug that caused deleted items to show up on the holds shelf.
649 * Staff can now place multiple email addresses into the patron registration/
650 edit form, depending on the value of the `ui.patron.edit.au.email.regex`
652 * Fixes an issue with the offline circulation module.
653 * When merging two users, the non-lead account is now completely purged from
654 the database, rather than simply being marked as deleted.
655 * Fixes a bug which prevented the canceling of holds from the title
661 * Removes incorrect copy counts from metarecord search results pages
662 * Electronic resources now display in the browse interfaces
663 * Restores ability to request password resets
665 System administration
666 ^^^^^^^^^^^^^^^^^^^^^
668 * The example Apache 2.4 configuration now enables remoteip.
669 * Improves syntax in the fm_idl file.
674 We would like to thank the following individuals who contributed code,
675 tests and documentation patches to the 3.2.2 point release of
699 This release contains bug fixes improving on Evergreen 3.2.0.
704 * Adds several columns to the items out grid.
705 * Adds the ability to copy patron addresses to the clipboard.
706 * Fixes several issues with adding new items and call numbers.
707 * Adds links to catalog records from the query and pending tabs of the Record Buckets interface.
708 * Corrects the date format used in several bucket interfaces.
709 * Adds a loading spinner to interfaces that are embedded in the web staff client via iframe
710 (such as the catalog).
711 * The new Angular 6 interfaces now use the correct favicon.
715 We would like to thank the following individuals who contributed code,
716 tests and documentation patches to the 3.2.1 point release of
737 Disabling of Legacy XUL Staff Client
738 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
739 The legacy XUL staff client is no longer supported in Evergreen
740 3.2.x and the server-side installation no longer supports a
741 direct connection by a version XUL client by default. *All
742 users of Evergreen 3.2.x are strongly urged to complete their
743 switch to the web staff client as part of upgrading to 3.2.x.*
745 Evergreen administrators who for some reason continue to wish
746 to deploy the XUL staff client can do so at their risk by
747 supplying `STAFF_CLIENT_STAMP_ID` during the `make install` step
748 and using `make_release` to create installers for the staff client.
749 However, no community support will be provided for the XUL client.
756 Existing Acquisitions report templates that reference the invoice 'complete'
757 field should be modified to check whether the new close_date field is NOT NULL
760 At deploy time, all invoices with a 'complete' value of TRUE will have their
761 'close_date' field set to NOW. A value is required, since this field is
762 now the source of whether an invoice is open or closed.
764 However, no values will be applied to the closed_by field for already closed
768 Angular6 Base Application
769 ~~~~~~~~~~~~~~~~~~~~~~~~~
771 System Admin Upgrade Notes
772 ^^^^^^^^^^^^^^^^^^^^^^^^^^
774 Like the AngularJS application, Evergreen releases will come with all
775 web browser staff client code pre-compiled. Admins only need to add an
776 Apache configuration change.
778 Add the following stanza to /etc/apache2/eg_vhost.conf.
781 --------------------------------------------------------------------------
782 RewriteCond %{REQUEST_URI} ^/eg2/
783 RewriteCond %{REQUEST_URI} !^/eg2/([a-z]{2}-[A-Z]{2})/
784 RewriteRule ^/eg2/(.*) https://%{HTTP_HOST}/eg2/en-US/$1 [R=307,L]
786 <Directory "/openils/var/web/eg2/en-US">
787 FallbackResource /eg2/en-US/index.html
789 --------------------------------------------------------------------------
791 For multi-locale sites, see the bottom section of
792 Open-ILS/examples/apache[_24]/eg_vhost.conf.in for a sample fr-CA
793 configuration. The section starts with "/eg2/ client setup and locale
796 Developer Upgrade Notes
797 ^^^^^^^^^^^^^^^^^^^^^^^
799 Developers building Angular code on existing installations need to update
800 their version of NodeJS by re-running the -developer prereqs installer.
803 --------------------------------------------------------------------------
804 sudo make -f Open-ILS/src/extras/Makefile.install <osname>-developer
805 --------------------------------------------------------------------------
808 Asynchronous Vandelay Imports
809 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
811 Users of NGINX as a reverse proxy may need to set a suitable
812 `client_max_body_size` value in the NGINX configuration so that large
813 MARC record uploads are not truncated. Note that this would have
814 always been necessary, but since this feature allows larger files
815 to be more reliably queued and imported, the need to set `client_max_body_size`
816 became more apparent.
819 Browser Client Settings & Preferences Stored on the Server
820 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
822 A new permission APPLY_WORKSTATION_SETTING has been added to control who
823 may apply values to workstation settings. Use something like the following
824 to apply the permission to all staff accounts (mileage may vary):
827 --------------------------------------------------------------------------
828 INSERT INTO permission.grp_perm_map (grp, perm, depth)
830 (SELECT id FROM permission.grp_tree WHERE name = 'Staff'), -- name may vary
831 (SELECT id FROM permission.perm_list WHERE code =
832 'APPLY_WORKSTATION_SETTING'),
835 --------------------------------------------------------------------------
837 Workstation setting types matching values previously stored in the browser
838 (via localStorage or Hatch) are created as part of this feature. During
839 upgrade, admins should consider whether any of these new setting types
840 should be transferred to user and/or org unit settings instead. Setting
841 type changes can be made at any time, but when a setting type is deleted
842 all of its data is deleted, so a change in type means re-applying the
843 settings in the browser client.
845 Values stored in the browser will automatically migrate to server settings
846 as each setting is accessed in the browser client. Once migrated, the
847 in-browser copies are deleted.
849 If a setting type does not exist where the browser expects one, the
850 value is stored in-browser instead and a warning is issued in the console.
862 Auto-Cancel Line items When All Copies Are Canceled
863 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
864 When a copy (line item detail) is canceled through the Acquisitions interface,
865 the parent line item is also canceled if all copies for that line item are also
866 canceled. The cancel reason given will come from:
868 . The cancel reason for the just-canceled copy if it's a Keep Debits true
870 . The cancel reason from any other copy on the lineitem that has a Keep
871 Debits true cancel reason.
872 . The cancel reason for the just-canceled copy if no copies have a Keep
873 Debits true cancel reason.
876 Invoice Closed Date and Closed By Fields
877 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
878 Acquisitions invoices have 2 new fields:
880 * Close Date -- This is set to the time when the ACQ user clicks the "Close"
881 button in the invoice interface.
882 ** This field 'replaces' the existing 'complete' field. An invoice is
883 considered complete if a close date value is set.
884 * Closed By -- This is set to the logged in staff user who performs the
887 As with the now-defunct 'complete' field, but new fields are cleared in the
888 event an invoice is reopened.
890 These new fields are visible in the invoice interface under the
891 'Show Details' action for closed invoices.
893 Upgrading Invoice Reports
894 +++++++++++++++++++++++++
896 Existing report templates that reference the invoice 'complete' field
897 should be modified to check whether the new close_date field is NOT NULL
900 Other Upgrade Considerations
901 ++++++++++++++++++++++++++++
903 At deploy time, all invoices with a 'complete' value of TRUE will have their
904 'close_date' field set to NOW. A value is required, since this field is
905 now the source of whether an invoice is open or closed.
907 However, no values will be applied to the closed_by field for already closed
912 Patron Acquisitions Requests
913 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
915 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.
922 Hold Targeter Script has been Replaced
923 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
925 The original hold_targeter.pl script has been renamed to
926 "hold_targeter_legacy.pl", and the new-style hold targeting
927 script has been renamed to "hold_targeter.pl". Administrators
928 will want to change their crontab files to reflect this.
932 ---------------------------------------------------------------------
933 -*/15 * * * * . ~/.bashrc && $EG_BIN_DIR/hold_targeter.pl $SRF_CORE
934 ---------------------------------------------------------------------
938 -----------------------------------------------------------------------------------
939 -*/15 * * * * . ~/.bashrc && $EG_BIN_DIR/hold_targeter.pl --osrf-config
941 -----------------------------------------------------------------------------------
943 The sample crontab file at `Open-ILS/examples/crontab.example` reflects
951 Angular6 Base Application
952 ^^^^^^^^^^^^^^^^^^^^^^^^^
953 With Evergreen 3.2, we introduce the initial infrastructure for
954 migrating to a new version of Angular. The structure of the new code
955 is quite different from the AngularJS code and it runs as a separate
956 application which communicates with the AngularJS app via shared storage
957 and in-page URLs that link back and forth between the two.
959 For this release, users will only be directed to the new Angular site
960 when navigating to Administration => Acquisitions Administration. Once
961 on this page, some of the admin interfaces will presented as Angular6
962 interfaces, while others will direct users back to the AngularJS
963 application. The Angular6 interfaces are the simpler, grid-based
966 Acquisitions Admin Angular6 Interfaces
967 ++++++++++++++++++++++++++++++++++++++
972 * Claim Policy Actions
980 * Invoice Payment Method
982 * Line Item MARC Attribute Definitions
984 System Admin Upgrade Notes
985 ++++++++++++++++++++++++++
987 Like the AngularJS application, Evergreen releases will come with all
988 web browser staff client code pre-compiled. Admins only need to add an
989 Apache configuration change.
991 Add the following stanza to /etc/apache2/eg_vhost.conf.
994 --------------------------------------------------------------------------
995 RewriteCond %{REQUEST_URI} ^/eg2/
996 RewriteCond %{REQUEST_URI} !^/eg2/([a-z]{2}-[A-Z]{2})/
997 RewriteRule ^/eg2/(.*) https://%{HTTP_HOST}/eg2/en-US/$1 [R=307,L]
999 <Directory "/openils/var/web/eg2/en-US">
1000 FallbackResource /eg2/en-US/index.html
1002 --------------------------------------------------------------------------
1004 For multi-locale sites, see the bottom section of
1005 Open-ILS/examples/apache[_24]/eg_vhost.conf.in for a sample fr-CA
1006 configuration. The section starts with "/eg2/ client setup and locale
1009 Developer Upgrade Notes
1010 +++++++++++++++++++++++
1012 Developers building Angular code on existing installations need to update
1013 their version of NodeJS by re-running the -developer prereqs installer.
1016 --------------------------------------------------------------------------
1017 sudo make -f Open-ILS/src/extras/Makefile.install <osname>-developer
1018 --------------------------------------------------------------------------
1024 Add UPC to z39.50 search for OCLC and LOC
1025 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1026 Add UPC as a search attribute for both OCLC and LOC targets in
1027 z39.50 for cataloging.
1030 Asynchronous Vandelay Imports
1031 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1033 Vandelay imports are now monitored from the browser client asynchronously,
1034 meaning the client requests updates from the server instead of waiting for
1035 the server to respond to the original import request. This changes allows
1036 for incremental progress updates in the browser client.
1041 This adds a new database table vandelay.session_tracker for tracking
1042 in-progress vandelay upload activity. A new tracker row is added for
1043 each of "upload", "enqueue", and "import" actions, linked for a given
1044 session by the value stored in the "session_key" field.
1046 The table tracks other potentially useful data, like the staff member
1047 and workstation where the action was performed.
1051 Users of NGINX as a reverse proxy may need to set a suitable
1052 `client_max_body_size` value in the NGINX configuration so that large
1053 MARC record uploads are not truncated. Note that this would have
1054 always been necessary, but since this feature allows larger files
1055 to be more reliably queued and imported, the need to set `client_max_body_size`
1056 became more apparent.
1061 Support for Last Inventory Date
1062 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1063 Evergreen now provides an option to add an inventory date to items to facilitate
1064 the process of performing inventory in libraries. Staff can add an inventory
1065 date to an item in one of the following ways:
1066 * From the check in screen, there is now an Update Inventory check in modifier.
1067 When selected, scanned barcodes will have the current date/time added as the
1068 inventory date while the item is checked in.
1069 * From the Item Status screen, an action is available to add the current
1070 date/time as the inventory date to selected items.
1072 This new feature will also store the workstation that was used when the
1073 inventory date was updated.
1077 Parallel Ingest with pingest.pl
1078 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1079 A program named pingest.pl is now installed to allow faster bibliographic record
1080 ingest. It performs ingest in parallel so that multiple batches can
1081 be done simultaneously. It operates by splitting the records to be
1082 ingested up into batches and running all of the ingest methods on each
1083 batch. You may pass in options to control how many batches are run at
1084 the same time, how many records there are per batch, and which ingest
1087 NOTE: The browse ingest is presently done in a single process over all
1088 of the input records as it cannot run in parallel with itself. It
1089 does, however, run in parallel with the other ingests.
1091 Command Line Options
1092 ++++++++++++++++++++
1093 pingest.pl accepts the following command line options:
1096 The server where PostgreSQL runs (either host name or IP address).
1097 The default is read from the PGHOST environment variable or
1101 The port that PostgreSQL listens to on host. The default is read
1102 from the PGPORT environment variable or 5432.
1105 The database to connect to on the host. The default is read from
1106 the PGDATABASE environment variable or "evergreen."
1109 The username for database connections. The default is read from
1110 the PGUSER environment variable or "evergreen."
1113 The password for database connections. The default is read from
1114 the PGPASSWORD environment variable or "evergreen."
1117 Number of records to process per batch. The default is 10,000.
1120 Max number of worker processes (i.e. the number of batches to
1121 process simultaneously). The default is 8.
1128 Skip the selected reingest component.
1131 Start processing at this record ID.
1134 Stop processing when this record ID is reached.
1137 Read record IDs to reingest from standard input. This option
1138 conflicts with --start-id and/or --end-id.
1141 Stop processing after this many total seconds have passed. The
1142 default is to run until all records have been processed.
1149 View Authority Record by Database ID
1150 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1152 A new interface allows catalogers to retrieve a specific
1153 authority record using its database ID. Catalogers can
1154 find those IDs in subfield $0 of matching fields in
1155 bibliographic records.
1157 To use the new authority record viewer:
1159 . Click *Cataloging -> Retrieve Authority Record by ID*.
1160 . Type in the ID number of the authority record you are
1161 interested in. Don't include any prefixes, just the ID
1164 . View or edit the authority record as needed.
1173 Autorenewal of Loans
1174 ^^^^^^^^^^^^^^^^^^^^
1175 Circulation policies in Evergreen can now be configured to automatically renew
1176 certain items checked out on patron accounts. Circulations will be renewed
1177 automatically up to a custom limit (the `max_auto_renewal` field) and patrons
1178 will not need to log in to their OPAC accounts or ask library staff to manually
1181 Two new action triggers have been added to Evergreen that permit the Auto-Renew
1182 feature. They can be found, configured, and enabled in Administration>Local
1183 Administration>Notifications/Action Triggers. They are named **Autorenew** and
1184 **AutorenewNotify**.
1186 The **Autorenew** A/T definition uses the `checkout.due` hook to automatically
1187 validate and renew (in the reactor) circulations on the day they are due,
1188 grouped by user. The output events of this definition is is the input used by
1189 the related **AutorenewNotify** A/T that simply uses a new hook called
1190 `autorenewal` to notify patrons via email of their currently due or
1193 In the webstaff's Patron Items Out page, the new column `AutoRenewalsRemaining`
1194 indicates how many autorenewals are available for a particular circulation.
1200 Emergency Closing Handler
1201 ^^^^^^^^^^^^^^^^^^^^^^^^
1203 Staff are provided with interfaces and mechanisms to create library closings
1204 that, in addition to affecting future circulation and booking due dates, and
1205 hold shelf expirations, will automatically move existing circulation and booking
1206 due dates and hold shelf expiration times. This new functionality is
1207 conceptually described as Emergency Closings and business logic implementing it
1208 as the Emergency Closing Handler. It contains additions and adjustments to the
1209 user interface, business logic, and database layers. Access to this
1210 functionality is available through the Closed Dates Editor interface in the
1211 staff client which has been ported to AngularJS.
1216 This development has created new business logic code to inspect, in real time,
1217 existing circulation, booking, and hold records, and modify such date and time
1218 stamps so that the circulation, booking, or hold will end in the same state it
1219 would have if the closing had existed at the time the circulation or booking
1220 occurred, or the hold was placed and captured. Of specific note, hourly loans
1221 will have their due date adjusted to be the end of the day following the
1224 When the Emergency Closing is saved, any fines accrued during the closing may be
1225 voided, as settings dictate, with the exception of circulations that have been
1226 marked as LOST or LONG OVERDUE. That is, even for LOST and LONG OVERDUE
1227 circulations with due dates that fall within the Emergency Closing, no fine
1228 adjustment will be applied. Emergency Closing processing is permanent, and
1229 cannot be rolled back.
1231 This functionality is explicitly initiated by staff action. If staff do not
1232 request an Emergency Closing, existing circulations, bookings, and holds will
1233 not be processed and adjusted. However, if staff request any Closing that starts
1234 nearer in time than the length of the longest circulation duration configured
1235 for use in the Evergreen instance they will be prompted with the option to
1236 create the closing as an Emergency Closing.
1238 Action/Trigger hooks have been created for circulations and bookings that are
1239 adjusted by the Emergency Closing Handler. These will facilitate the creation of
1240 notifications to patrons that the due date has changed and to alert them to
1241 potential changes in accrued fines.
1243 Booking start dates are explicitly ignored in this implementation. Because an
1244 Emergency Closing is, by its nature, an unexpected event, it will be up to staff
1245 to address any bookings which intersect with a new Emergency Closings. Reports
1246 can be used to identify booking start dates that overlap with a closing and that
1247 may require staff intervention.
1249 Staff requesting and Emergency Closing must have the new EMERGENCY_CLOSING
1250 permission. Some text describing the feature.
1256 Patron Preferred Name and Name Search Keywords
1257 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1262 Adds a new set of patron preferred name fields for prefix, first,
1263 middle, last, and suffix allowing patrons to provide preferred name
1264 information. Preferred names are optional and each acts as an overlay
1265 to the analogous primary name field, making it possible to provide
1266 preferred name values for individual fields.
1268 For example, a patron named William Erickson may have a preferred first
1269 name (pref_first_given_name) of Bill, in which case the preferred name
1270 would be Bill Erickson. Note a preferred last name is not required in
1271 this case as the code uses primary name values as defaults when not
1272 replaced with a preferred version.
1274 * Patrons will see primary names displayed in the catalog when set.
1275 * Staff will see both primary name and preferred name in the patron
1277 * Patron searches for any given name field will search both the primary
1278 and preferred name data.
1279 * Preferred name fields are available in Action/Trigger templates and
1280 are present in various patron-focused print templates.
1285 Adds a new field to store miscellaneous patron name search terms. These
1286 values are only for searching and do not appear in any interfaces, apart
1287 from the patron summary side bar and the patron edit UI.
1289 Included is a new search field in the patron search UI which searches
1290 keyword values and all other name fields. It's essentially a global patron
1291 name keyword search.
1299 Disabling of legacy XUL staff client
1300 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1301 The legacy XUL staff client is no longer supported in Evergreen
1302 3.2.x and the server-side installation no longer supports a
1303 direct connection by a version XUL client by default. All
1304 users of Evergreen 3.2.x are strongly urged to complete their
1305 switch to the web staff client as part of upgrading to 3.2.x.
1307 Evergreen administrators who for some reason continue to wish
1308 to deploy the XUL staff client can do so at their risk by
1309 supplying `STAFF_CLIENT_STAMP_ID` during the `make install` step
1310 and using `make_release` to create installers for the staff client.
1311 However, no community support will be provided for the XUL client.
1316 Permission Group Display Entries
1317 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1318 In some cases, it is useful to have the ability to reorder permission, or to make
1319 only specific groups available in the permission group selector for specific
1320 Org Units. An interface has been made available to allow this.
1322 Group Tree Display Entry Interface
1323 ++++++++++++++++++++++++++++++++++
1325 Permission Group Display Entries can be reordered, added, or removed via
1326 _Administration -> Local Admin -> Permission Tree Display Entries_.
1327 Select the Org Unit you wish to edit the entries in.
1329 Entries may be added using the Add functionality, creating entries based
1330 on permission groups that have not been added to the tree for the Org
1331 Unit you wish to add them to.
1333 image::media/pgtde_01.png[Group Tree Display Entry Admin UI]
1337 Moving an entry will shift its position up or down in the patron profile
1338 selector for a given Org Unit.
1341 * Press either the *Move Up* or *Move Down* button. The entry will be
1342 moved up or down, accordingly.
1343 * Click *Save* to save your edits.
1345 NOTE: You may only move up or down entries that have sibling entries.
1349 If you want a particular Org Unit to not have access to specific
1350 entries, you may remove an entry. Removing an entry will remove it from
1351 view. The entry will be removed from the database.
1353 * Select an entry and press the *Remove* button.
1357 You may add entries from permission groups that are not currently
1358 reflected in the permission group tree. This is useful for moving
1359 entries to different parents, or making them root entries.
1361 image::media/pgtde_02.png[Add Entry modal]
1363 * If desired, select an entry to be used as the parent entry.
1364 * Press the *Add* button.
1365 * Select a permission group from the dropdown.
1366 * If you've selected a parent entry, you may check the *Add Root Entry*
1367 box to override that parent and add the entry on the root level.
1368 * If you did not select a parent entry, the entry will be added on the root
1373 Browser Client Settings & Preferences Stored on the Server
1374 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1375 Browser client settings and preferences that should persist over time are
1376 now stored as settings on the server. This allows settings to follow
1377 users and workstations and reduces problems associated with losing settings
1378 as a result of clearing browser data.
1380 The browser client honors setting values stored as user settings, workstation
1381 settings, and org unit settings, depending on which setting types are
1387 * No setting can be both a user and workstation setting. They are mutually
1389 * Any setting can be an org unit setting in addition to being a user or
1390 workstation setting.
1395 Read-only settings are useful for defining values that staff can use but
1396 not modify. For example, admins may wish to prevent users from locally
1397 modifying the grid configuration for a given interface so it remains
1398 consistent for all users.
1400 A setting is read-only when an org unit setting type exists (regardless of
1401 whether a value is applied) and no user or workstation setting type exists.
1403 Server-Stored Workstation Settings Workstation Admin View
1404 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1406 There's a new "Server Workstation Prefs" tab to the stored preferences
1407 workstation admin interface. From here, users can view which
1408 preferences are stored as server-stored workstation preferences and
1409 delete select values.
1414 A new permission APPLY_WORKSTATION_SETTING has been added to control who
1415 may apply values to workstation settings. Use something like the following
1416 to apply the permission to all staff accounts (mileage may vary):
1419 --------------------------------------------------------------------------
1420 INSERT INTO permission.grp_perm_map (grp, perm, depth)
1422 (SELECT id FROM permission.grp_tree WHERE name = 'Staff'), -- name may vary
1423 (SELECT id FROM permission.perm_list WHERE code = 'APPLY_WORKSTATION_SETTING'),
1426 --------------------------------------------------------------------------
1428 Workstation setting types matching values previously stored in the browser
1429 (via localStorage or Hatch) are created as part of this feature. During
1430 upgrade, admins should consider whether any of these new setting types
1431 should be transferred to user and/or org unit settings instead. Setting
1432 type changes can be made at any time, but when a setting type is deleted
1433 all of its data is deleted, so a change in type means re-applying the
1434 settings in the browser client.
1436 Values stored in the browser will automatically migrate to server settings
1437 as each setting is accessed in the browser client. Once migrated, the
1438 in-browser copies are deleted.
1440 If a setting type does not exist where the browser expects one, the
1441 value is stored in-browser instead and a warning is issued in the console.
1444 More consistent terminology in the client
1445 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1446 Terminology has been updated in the staff client so that we consistently use
1447 the same name to describe the same thing. The following updates have been made:
1449 * The term 'item' is now consistently used to describe the barcoded entity
1450 that had been previously been called both an 'item' and a 'copy'. As a result,
1451 we now use the terms 'item buckets', 'item tags', and 'item alerts'.
1452 * The term 'volume' is no longer used in the client, with the exception of
1453 serials, where the term is used to describe serial volumes. The term 'call
1454 number' will replace volume in most other places.
1455 * 'Holdings' is a more general term used to describe a combination of items
1457 * The term 'Shelving Location' is used consistently in favor of 'Copy
1468 Batch Actions In the Public Catalog
1469 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1470 The public catalog now displays checkboxes on the bibliographic and
1471 metarecord constituents results pages. Selecting one or more titles
1472 by using the checkboxes will dynamically add those title to the
1473 temporary list, which is now renamed the cart.
1475 Above the results lists there is now a bar with a select-all checkbox,
1476 a link to the cart management page that also indicates the number of
1477 of titles in the cart, and a link to remove from the cart titles that
1478 are selected on the currently displayed results page.
1480 The search bar now includes an icon of a cart and displays the number
1481 of titles currently in the cart. Next to that icon is a menu of cart
1484 The cart actions available are Place Hold, Print Title Details,
1485 Email Title Details, Add Cart to Saved List, and Clear Cart. In the
1486 web staff client, the cart actions also include Add Cart to Bucket.
1487 When an action is selected from this menu, the user is given an
1488 opportunity to confirm the action and to optionally empty the cart
1489 when the action is complete. The action is applied to all titles
1492 Clicking on the cart icon brings the user to a page listing the
1493 titles in the cart. From there, the user can select specific records
1494 to request, print, email, add to a list, or remove from the cart.
1496 The list of actions on the record details page now provides separate
1497 links for adding the title to a cart or to a permanent list.
1499 The permanent list management page in the public catalog now also
1500 includes batch print and email actions.
1502 Additional information
1503 ++++++++++++++++++++++
1504 * The checkboxes do not display on the metarecord results page, as
1505 metarecords currently cannot be put into carts or lists.
1506 * The checkboxes are displayed only if JavaScript is enabled. However,
1507 users can still add items to the cart and perform batch actions on
1508 the cart and on lists.
1509 * A template `config.tt2` setting, `ctx.max_cart_size`, can be used to
1510 set a soft limit on the number of titles that can be added to the
1511 cart. If this limit is reached, checkboxes to add more records to the
1512 cart are disabled unless existing titles in the cart are removed
1513 first. The default value for this setting is 500.
1518 This patch adds to the public catalog two routes that return JSON
1521 * `GET /eg/opac/api/mylist/add?record=45`
1522 * `GET /eg/opac/api/mylist/delete?record=45`
1524 The JSON response is a hash containing a mylist key pointing to the list
1525 of bib IDs of contents of the cart.
1527 The record parameter can be repeated to allow adding or removing
1528 records as an atomic operation. Note that this change also now available
1529 to `/eg/opac/mylist/{add,delete}`
1531 More generally, this adds a way for EGWeb context loaders to specify that
1532 a response should be emitted as JSON rather than rendering an HTML
1533 page using `Template::Toolkit`.
1535 Specifically, if the context as munged by the context loader contains
1536 a `json_response` key, the contents of that key will to provide a
1537 JSON response. The `json_response_cookie` key, if present, can be used
1538 to set a cookie as part of the response.
1540 Template Toolkit processing is bypassed entirely when emitting a JSON
1541 response, so the context loader would be entirely responsible for
1542 localization of strings in the response meant for direct human
1548 New class for searchbar when on the homepage
1549 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1551 This adds the `.searchbar-home` class to the div that contains the searchbar
1552 when on the homepage. This allows sites to customize the searchbar differently
1553 on the homepage than in other places the search bar appears (for example,
1554 offering a large, Google-style search bar on the homepage only).
1559 To make customization easier, the username hint on the OPAC login page ("Please
1560 include leading zeros...") has been moved to a separate TT2 template. If you
1561 have customized the hint text, you will need to add your modifications to
1568 The Evergreen project would like to acknowledge the following
1569 organizations that commissioned developments in this release of
1572 * BC Libraries Cooperative
1573 * Consortium Of Ohio Libraries
1575 * Georgia Public Library Service
1576 * Indiana State Library
1577 * Lake Agassiz Regrional Library
1579 * North Texas Library Consortium
1580 * Northwest Regional Library
1581 * Pennsylvania Integrated Library System
1582 * South Carolina State Library
1584 We would also like to thank the following individuals who contributed
1585 code, translations, documentations patches and tests to this release of
1590 * Andrea Buntz Neiman
1599 * Blake Graham-Henderson
1600 * Francisco J Guel-Mendoza
1618 We also thank the following organizations whose employees contributed
1621 * BC Libraries Cooperative
1624 * Equinox Open Library Initiative
1625 * Government of Manitoba
1626 * Kenton County Public Library
1627 * King County Library System
1628 * Linn-Benton Community College
1632 We regret any omissions. If a contributor has been inadvertently
1633 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / working / Evergreen.git / blob