1 Evergreen 2.11 Release Notes
2 ============================
10 This release of Evergreen contains a fix to the _Hold/Copy Ratio per Bib
11 and Pickup Library (and Descendants)_ data source. Report templates using
12 this data source will need to be re-created to improve accuracy of the
13 data reported from this source.
17 This release contains several bug fixes improving on Evergreen 2.11.6
19 * Improvements to CSS to silence some Mozilla extension warnings.
20 * A fix to a failure to update targeted circulations when utilzing the recall
22 * The addition of text wrapping in the copy details table on the bib
23 record to prevent contents from falling off the page.
24 * A fix to the adjust to zero option so that it can be applied correctly
26 * A fix to the "Hold/Copy Ratio per Bib and Pickup Library
27 (and Descendants)" data source so that it will now include counts of eligible
28 copies at locations that are not a pickup library for bib's holds.
32 We would like to thank the following individuals who contributed code,
33 tests and documentation patches to the 2.11.7 point release of
48 This release contains several bug fixes improving on Evergreen 2.11.5.
50 * Code to prevent a hold already on the Holds Shelf from being
51 transferred to another title.
52 * A fix to a bug that prevented users from scheduling reports with a
53 relative month if the report template used a date that applied the Year +
54 Month transform with the On or After (>=) operator.
55 * A fix to a bug where the max fines threshold was reached prematurely
56 due to the presence of account adjustments.
57 * A check that prevents a SMS message from sending if the SMS carrier
62 We would like to thank the following individuals who contributed code,
63 tests and documentation patches to the 2.11.6 point release of
75 This release is a security release that also contains several other bug
76 fixes improving on Evergreen 2.11.4.
78 Security Issue: XSS Vulnerability in Public Catalog
79 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
80 This release fixes several cross-site scripting (XSS) vulnerabilities
81 in the public catalog. When upgrading, Evergreen administrators should
82 review whether any of the following templates have been customized
83 or overridden. If so, either the template should be replaced with the
84 stock version or the XSS fix (which entails adding the `| html` filter
85 in several places) applied to the customized version.
87 * `Open-ILS/src/templates/opac/parts/locale_picker.tt2`
88 * `Open-ILS/src/templates/opac/parts/login/form.tt2`
89 * `Open-ILS/src/templates/opac/parts/searchbar.tt2`
93 * A fix to remove the Chilifresh patron reviews header for Evergreen sites
94 that do not use Chilifresh.
95 * A fix that marks acquisitions POs as received when all line items on the
96 PO are received or canceled.
97 * A typo fix to the long overdue override permission that prevented staff
98 from being able to override long overdue check ins.
99 * A fix to use a library's configured currency in SIP patron responses
100 instead of always using US dollars.
101 * A fix to SIP timeouts caused by invalid sessions
102 * A fix that allows boolean fields to be recognized in queries to the
104 * A fix to use the correct method during adjust to zero on negative
106 * A correction to the datatype for the Vandelay Default Record Match Set
108 * The removal of the _Keep_ field from MARC Batch Import Item Attributes.
109 The field was not previously implemented.
110 * A fix to set the complete time value for grouped Action/Trigger events
111 when an event's state reach complete, consistent with non-grouped events.
112 * A fix to a bug in the rollover_phone_to_print.pl script that kept failed
113 call files from being moved.
114 * A new index for acq.edi_message that speeds up the check for duplicate
116 * A fix that ensures JSON strings are converted to UTF8, ensuring that
117 non-ASCII data display correctly.
118 * A fix to avoid an erroneous unsaved data popup to appear during MARC
123 We would like to thank the following individuals who contributed code,
124 testing and documentation patches to the 2.11.5 point release of
148 This release contains several bug fixes improving on Evergreen 2.11.3.
150 * A fix to avoid fetching and creating EDI message entries that the
152 * A fix to prevent staff users from marking a long overdue item as lost
153 so that the patron will not be billed twice for the same item.
154 * A fix to the link that is used on the catalog's Library Info page so
155 that links with anchors can be successfully retrieved.
156 * A replacement for the blank fallback image used when the catalog cannot
157 retrieve an added content book cover.
158 * An EDI fix that prevents EDI fetcher from crashing when the vendor
159 supplies a zero-length file.
160 * A fix to an issue where adjusting a bill to zero for a current checkout
161 prematurely closes the transaction.
162 * A fix to encoding problems in MODS output. These problems caused issues
163 when using Zotero with records in the catalog.
164 * A fix to Evergreen self-check to accept the user name value when a barcode
165 regex has been configured for the system.
166 * A fix to duplicate name checking in the patron registration screen so that
167 clicking the "Found x patron(s) with same name" link will retrieve potential
168 duplicate inactive patrons.
169 * A fix to the bower install step used when installing the web staff client.
170 * A fix that marks a hold as fulfilled when staff check out a hold-
171 captured item for a hold whose expire time is in the past.
172 * A change to the acquisitions funding source funds drop down menu so that
173 the menu will now only display active funds and will also display the
174 year alongside the fund.
175 * A fix to a problem where the Current Bills tab of the patron record
176 showed duplicate charges when a check in was done from the Items Out tab.
177 * A fix that hides the option to add to My Lists from the staff client since this functionality does not work as expected in the staff client.
178 * A change to the fund year selectors in acq interfaces so that the years
179 are sorted in descending order.
180 * A fix to a billing issue where transactions were not re-opened after
181 they acquired a non-zero balance at check in.
182 * A change to the default pickup library when staff place a hold. The place hold
183 screen will now default to the preferred pickup location for the patron. If the
184 patron does not have a preferred pickup location, it will default to the
185 patron's home library.
186 * The ability to skip the XUL staff client build when in make_release.
187 * A fix that silences a log warning that appears for every checkout where a hard
188 due date is not used.
192 We would like to thank the following individuals who contributed code,
193 testing and documentation patches to the 2.11.4 point release of
220 This is a security release that also contains several other bugfixes improving
221 on Evergreen 2.11.2. All users of Evergreen 2.11.x are recommended to upgrade
222 to 2.11.3 as soon as possible.
224 Security Issue: Credit Processor Stripe Settings Permissions
225 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
226 Unprivileged users can retrieve organizational unit setting values for
227 setting types lacking a "view" permission. When the feature adding
228 Stripe credit card processing was added, the upgrade script neglected
229 to add the VIEW_CREDIT_CARD_PROCESSING permission to the
230 organizational unit setting type. This means that anyone can retrieve
231 and view the settings for Stripe credit card processing.
233 Any system that upgraded from Evergreen version 2.5 to 2.6 is
234 affected. If you use Stripe for credit card processing, it is
235 strongly recommended that you apply this upgrade. Even if you do not
236 use Stripe, applying this upgrade is still recommended. If you did
237 not upgrade from version 2.5 to 2.6 of Evergreen, but started with a
238 later version, applying this upgrade is harmless.
240 If you are not ready to perform a full upgrade, and if you use Stripe,
241 you can protect the settings by running the following two SQL statements:
245 UPDATE config.org_unit_setting_type
246 SET view_perm = (SELECT id FROM permission.perm_list
247 WHERE code = 'VIEW_CREDIT_CARD_PROCESSING' LIMIT 1)
248 WHERE name LIKE 'credit.processor.stripe%' AND view_perm IS NULL;
250 UPDATE config.org_unit_setting_type
251 SET update_perm = (SELECT id FROM permission.perm_list
252 WHERE code = 'ADMIN_CREDIT_CARD_PROCESSING' LIMIT 1)
253 WHERE name LIKE 'credit.processor.stripe%' AND update_perm IS NULL;
256 Missing Upgrade Script Notice
257 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258 It was recently discovered that the 2.11.2 tarball was missing the
259 upgrade script for 2.11.1. If you upgraded straight to 2.11.2 from
260 2.11.0 or prior, please make sure to apply the
261 2.11.0-2.11.1-upgrade-db.sql before moving on to the 2.11.3 script.
265 Evergreen 2.11.3 also contains the following bugfixes:
267 * A fix to correctly apply floating group settings when performing
269 * An improvement to the speed of looking up patrons by their username;
270 this is particularly important for large databases.
271 * A fix to properly display the contents of temporary lists ('My List') in the
272 public catalog, as well as a fix of the HTML coding of that page.
273 * A fix to the Spanish translation of the public catalog that could
274 cause catalog searches to fail.
275 * A fix of a problem where certain kinds of requests of information
276 about the organizational unit hierarchy to consume all available
277 `open-ils.cstore` backends.
278 * A fix to allow staff to use the 'place another hold' link without
279 running into a user interface loop.
280 * A fix to the 'Edit Due Date' form in the web staff client.
281 * A fix to the definition of the stock 'Full Overlay' merge profile.
282 * A fix to sort billing types in alphabetical order in the web staff
284 * A fix to the display of the popularity score in the public catalog.
285 * A fix to the 'return to grouped search results' link in the public
287 * A fix to allow pre-cat checkouts in the web staff client without requiring
288 a circulation modifier.
289 * A fix to how Action/Trigger event definitions with nullable grouping
290 fields handle null values.
291 * Other typo and documentation fixes.
295 We would like to thank the following individuals who contributed code,
296 testing and documentation patches to the 2.11.3 point release of
319 This release contains several bugfixes improving on Evergreen 2.11.1
321 * A fix to the web client patron interface that changed the holds count in the
322 patron summary from total / available to available / total.
323 * A fix to an issue where the Closed Dates Editor was displaying an extra day of
325 * A fix to the Closed Dates Editor so that it now displays "All Day" when the
326 library is closed for the entire day.
327 * A fix to properly format LC Call numbers in spine label printing.
328 * A fix to a bug that was causing intermittent search failures.
329 * A fix to a bug that was causing search failures for Copy Location Group
331 * A fix to significant increased slowness with holds transfers.
332 * The addition of an index to the action.aged_circulation table to resolve a
333 problem with long-running queries.
334 * A fix to redirects that for one-hit metarecord searches for systems that
335 have enabled the setting to immediately jump to a bib record on one-hit searches.
336 * A fix to the new acquisitions cost field available in the copy editor to
337 resolve an issue where accidentally clearing out the value in the field resulted
339 * A fix to a bug that broke the Alternate Printable Hold Pull List and Vandelay
340 uploads on systems that were running OpenSRF 2.5.
344 We would like to thank the following individuals who contributed code,
345 testing and documentation patches to the 2.11.1 point release of
364 This release contains several bug fixes improving on Evergreen 2.11.0
366 * A fix to that provides alphabetical sorting to the fund selector in
367 the Acquisitions Selection List -> Copies interface.
368 * A fix to the web client check in screen allowing users to click the
369 title of the checked-in item to retrieve the bib record for that item.
370 * The addition of a progress bar that displays when conducting a patron searchin the web client.
371 * A fix to the web client patron interface so that total Items Out in the
372 patron summary now includes overdue and long overdue items. It will also
373 include Lost and Claims Returned items when the appropriate library
375 * A change to the public catalog My Account screen where the font for
376 leading articles will now be smaller when sorting a list by title.
377 * A fix to subject links in the catalog's record summary page so that
378 periods are no longer stripped from resulting subject searches, leading
379 to more accurate results when those links are clicked.
380 * A fix to avoid unint warnings in the logs for prox_cache in
381 open-ils.circ.hold.is_possible.
382 * A fix to rounding errors that occurred when summing owed/paid totals
383 for display in the catalog's credit card payment form.
384 * A change to sort behavior in the My Account screens. Previously, a
385 third click on a column header returned the list to its original sort
386 order. Clicking column headers will now simply toggle the sort
387 between ascending and descending order.
388 * The Permalink option on the catalog's record summary page will now be
389 hidden in the staff client because clicking the link in the client led
390 to no discernible change for users.
391 * A fix to the display of permanent lists in the catalog, which had broken
393 * A fix to the text of a notice that displays when migrating circulation
394 history during the upgrade to 2.10.
395 * An improvement to the performance for the lookup of a user's circ
396 history by adding an index on action.usr_circ_history(usr).
397 * A fix so that when a bib record's fingerprint changes, it gets correctly
398 moved to a different metarecord.
402 We would like to thank the following individuals who contributed code,
403 tests and documentation patches to the 2.11.1 point release of
422 Tablefunc Extension No Longer Required
423 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
424 Changes in the behavior of the connectby function in PostgreSQL 9.5
425 have prompted its removal from the database. It is easier for
426 Evergreen to maintain compatibility with previous versions of
427 PostgreSQL without this function.
429 By eliminating the use of the connectby function, we eliminate the
430 requirement for the tablefunc database extension. It is no longer
431 installed when the database is created. If you are upgrading and wish
432 to remove it from your database, you may run the following statement
433 in the database to drop it:
435 DROP EXTENSION tablefunc;
451 Add Date Header to Action Trigger Email/SMS Templates
452 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
453 The Date: header specified in RFC 2822 has been added to the seed data
454 for the example Action Trigger email and SMS templates, but no attempt
455 has been made to automatically modify existing templates. To add this
456 header (and end any "Why are my library emails from 1969/70?" questions
457 you may have heard) make sure the following lines are in all templates
458 that use the SendEmail or SendSMS reactors:
460 The first is already in most sample templates, but you may need to add
461 it to the top of any custom templates:
464 And this line should be inserted into the header block of each template:
465 `Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]`
471 Support for Ubuntu 16.04
472 ^^^^^^^^^^^^^^^^^^^^^^^^
473 Adds support for Ubuntu Xenial Xerus (16.04).
482 User activity types are now set to transient by default for new
483 Evergreen installs.. This means only the most recent activity entry per
484 user per activity type is retained in the database.
486 This change does not affect existing activity types, which were set to
487 non-transient by default. To make an activity type transient, modify the
488 'Transient' field of the desired type in the staff client under Admin ->
489 Server Administration -> User Activity Types.
491 Setting an activity type to transient means data for a given user will
492 be cleaned up automatically if and when the user performs the activity
493 in question. However, administrators can also force an activity
494 cleanup via SQL. This is useful for ensuring that all old activity
495 data is deleted and for controlling when the cleanup occurs, which
496 may be useful on very large actor.usr_activity tables.
498 To force clean all activity types:
501 ------------------------------------------------------------
502 SELECT actor.purge_usr_activity_by_type(etype.id)
503 FROM config.usr_activity_type etype;
504 ------------------------------------------------------------
506 NOTE: This could take hours to run on a very large actor.usr_activity table.
517 Authority Record Import Updates Editor, Edit Date.
518 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
519 Importing an authority record via MARC Batch Import/Export now causes the
520 authority record's editor and edit_date fields to be updated. The editor
521 value may come from the MARC 905u field or, if none is present, the user
522 performing the import.
527 Authority Propagation Updates Bib Editor / Edit Date
528 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
529 When a bib record is automatically updated as a result of the
530 modification of a linked authority record, the bib record's "Last Edit
531 Date/Time" and "Last Editing User" fields will be updated to match the
532 time of the update and the editor of the modified authority record.
534 A new global flag is available to control this behavior called
535 'ingest.disable_authority_auto_update_bib_meta' ("Authority Automation:
536 Disable automatic authority updates from modifying bib record editor
537 and edit_date"). When enabled, theses fields will not be updated. By
538 default, this setting is disabled.
540 An additional speed improvement is included in this feature. No attempt
541 will be made to update linked bib records when the normalized heading of
542 the modified authority record is unchanged by the authority record update.
547 Bibliographic Record Source Now Copied to 901$s
548 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
549 If a bibliographic record has a source set, the name of that source
550 is now copied to the 901$s whenever the record is created or updated.
551 This allows the source to be used for record matching and MARC
557 Option to Update Bib Source and Edit Details on Record Import
558 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
559 When importing records through the client, users will now have the ability to
560 define whether the bib source, last editor, and last edit date should be updated
561 on a record merge/overlay.
563 In MARC Batch Import / Export, select the _Merge / Overlay_ tab. Each entry in
564 the table has a value in the new _Update bib. source_ column. If that value is
565 True, then the bib source, last editor, and last edit date will be updated.
567 The two system-defined entries have been pre-set to appropriate values (Full
568 Overlay = true; Match-Only Merge = false).
578 Staff Client Honors Aged Circulations
579 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
581 The browser and XUL clients now better represent copy checkout history
582 by honoring and displaying information from aged circulations.
584 * Browser client 'Recent Circ History' and the analogous XUL client
585 'Circulation History' tabs show summary data for aged circulations
586 as well as regular/active circulations. When aged circulation data
587 is displayed, any references to patron names are replaced by the string
588 "<Aged Circulation>".
590 * Browser client 'Circ History List' and the analogous XUL client
591 'Last Few Circulations' tabs behave as above, plus their 'Add
592 Billing' buttons are disabled when displaying aged circulation data.
594 * XUL client 'Retrieve Last Patron' actions from various UI's report,
595 "Item XXX circulation is an aged circulation and has no linked user".
596 Browser client analog uses 'Circ History List' instead; no additional
603 "Canceled Transit" Item Status
604 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
606 Previously, when a transit was aborted, the transited item would either go into
607 "Reshelving" status or would return to whatever status it was in when it went
608 into transit, even when the item itself was in a different status (including
609 "Checked out"). Now, for most transits that get aborted, the item is put into a
610 new status, "Canceled Transit", which signals to staff the actual state of the
611 item. This feature only affects items with a status of "In transit" and does
612 not affect items that were in the following statuses at the time they were sent
623 * Any custom statuses
625 This change should help clear up confusing situations caused by the previous
626 "abort transit" behavior, such as items showing "Available" when they are actually
627 en route, and patrons' items mysteriously disappearing from their accounts and
628 showing "Available" at the item-owning library without evidence of check-in.
633 Copy Status "Is Available" Flag
634 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
636 A new boolean field is now available for copy statuses to indicate when copies
637 having a given status should be considered available. The field has 2 main
640 1. Checking out an "available" copy will no longer result in an override-able
641 "COPY_NOT_AVAILABLE" alert for staff. The copy will checkout without
644 2. "Available" copies will appear in catalog searches where "limit to
645 available" is selected as a search filter.
647 By default, the "Available" and "Reshelving" statuses have the "Is Available"
648 flag set. The flag may be applied to local/custom statuses via the copy
649 status admin interface.
655 Email Checkout Receipts
656 ^^^^^^^^^^^^^^^^^^^^^^^
657 This feature allows patrons to receive checkout receipts through email
658 at the circulation desk in the web client and in the Evergreen self-checkout
659 interface. Patrons need to opt in to receive
660 email receipts by default and must have an email address associated with their
661 account. Opt in can be staff mediated at the time of account creation or in
662 existing accounts. Patrons can also opt in directly in their OPAC account or
663 through patron self-registration. This feature does not affect the behavior of
664 checkouts from the XUL client or SIP2 devices.
666 Patrons can opt in to receive email checkout receipts by default via
667 a new _Email checkout receipts by default_ patron setting.
669 This feature also enhances the patron staging tables so that patron
670 settings can be chosen during self-registration.
672 The web staff interface's checkout screen now includes a "Quick
673 Receipt" button that allows staff members to generate a receipt
679 Set Per-OU Limits on Allowed Payment Amounts
680 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
681 Two new settings have been added to prevent clerks from accidentally clearing
682 all patron bills by scanning a barcode into the Payment Amount field, or
683 accidentally entering the amount without a decimal point (such as you
684 would when using a cash register).
686 Both settings are available via the Library Settings Editor. The _Payment
687 amount threshold for Are You Sure? dialog_ (ui.circ.billing.amount_warn)
688 setting identifies the amount above
689 which staff will be asked if they're sure they want to apply the payment.
690 The _Maximum payment amount allowed_ (ui.circ.billing.amount_limit)
691 setting identifies the maximum amount of
692 money that can be accepted through the staff client.
694 These settings only affect the staff client, not credit
695 cards accepted through the OPAC, or direct API calls
696 from third party tools.
706 Additional Fields Available for Display in Some Interfaces
707 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
708 The holds age protection field will now be available for display in the
709 following interfaces:
711 * Item status list view column picker
712 * Item status alternate view
713 * Holdings maintenance column picker
715 The asset.copy.cost field, which records the amount paid for an item when
716 an invoice is processed, will be available for display in the following
719 * Items status list view column picker
720 * Item status alternate view
732 Merge Notification Preferences Tables in TPAC
733 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
734 The patron notification preference page in the public catalog
735 used to have two tables, separating notification settings
736 based on their source. Since that distinction does not matter
737 to patrons, and since the two tables aren't styled consistently,
738 they are merged together.
743 Improved Holds Screens in My Account
744 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
745 The grids in the My Account _Items on Hold_ and _Holds History_ interfaces are
746 simplified. Data previously contained in their own Activate, Active, and Date
747 Fulfilled columns are now incorporated into the Status column. To further
748 declutter the interface, the holds queue position will only show when the user
749 most needs the information - before the hold has been captured.
751 Distinct CSS classes have also been added for each hold status and each date
752 that could potentially display in these holds interfaces. A new default style
753 highlights the _Available_ status in green and the _Suspended_ status
761 Popularity Boost for Ranking Search Results
762 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
764 This feature uses factors such as circulation and hold activity, record and item age, and item ownership counts to generate popularity badges for bibliographic
765 records. Each badge will have a five-point scale, where more points indicates a more popular record. The average of the badge points earned by each record will constitute a "popularity rating". The number and types of badges will break ties for average popularity, and relevance will sort items with like popularity.
767 A new sort axis of popularity is created to sort first on the weighted average popularity of each record, followed by the query-specific relevance available today. A new option is created in the drop-down called _Most Popular_ that sorts on the combination of "activity metric" (aka badge ranking, aka popularity) first and then the existing, stock relevance ranking when those are equal. For instance, given two records that both have a badge ranking of "4.5", they sort in the order of the query relevance ranking that is calculated today as a tie breaker. Those two records will sort above other records with lower badge rankings regardless of what today's relevance ranking says about them.
769 In addition, a new sort axis of _Popularity-Adjusted Relevance_ is created that augments the normal Relevance sort with a normalized popularity value by multiplying the base relevance by a value controlled by a new global flag, generally set to a decimal number between 1 and 2.
771 Finally, there will continue to be a pure _Relevance_ sort option, which is the version that exists today.
773 Administrators can comment out one of the available sort methods by editing the
774 filtersort.tt2 file.A global flag will allow Evergreen sites to select a default sort method.
779 Administrative interfaces to configure badges are only available in the web
780 client. Administrators can also configure badges directly via the database.
782 Available Popularity Parameters available for badges include:
784 * Holds Filled Over Time
785 * Holds Requested Over Time
787 * Circulations Over Time
788 * Current Circulation Count
791 * Holds/Holdable Ratio
792 * Percent of Time Circulating
793 * Bibliographic Record Age (days)
794 * Publication Age (days)
795 * Available On-Line (for e-books, etc)
798 Badges can be configured to apply to a targeted group of bibliographic records
799 based on the following available filters:
802 * Bibliographic source
803 * Circulation modifier
804 * Copy location group
806 Badges can also be be restricted to materials owned by a specific organizational
809 This new feature comes with a starter badge based on the top 97th percentile of
810 holds requested over the past five years.
815 Ratings for records will be displayed in the catalog in the following ways:
817 * On the record result page, the overall average popularity rating is displayed with a label of _Popularity_.
819 * On the record detail page, each individual badge earned by the record is
820 displayed with its rating.
824 * **OPAC Default Sort (opac.default_sort)**: Identifies the default sort method
825 to be used in the catalog.
827 * **Maximum popularity importance multiplier for popularity-adjusted relevance
828 searches (search.max_popularity_importance_multiplier):** A multiplier identifying
829 the importance of popularity in the Popularity-Adjusted Relevance ranked
830 searches. The number should be a decimal ranging between 1.0 and 2.0. The
831 default value is 1.1.
833 More detailed information is available in the TechRef docs directory of the
834 Evergreen source code.
839 Removal of Advanced Hold Options link when part holds are expected
840 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
841 If a user attempts to place a metarecord hold when all eligible copies
842 contain parts, the hold will fail. To help prevent the user from reaching
843 a dead end while placing holds, the *Advanced Hold Options* link is removed
844 from the Place Hold page in cases where all copies on the record contain
845 parts. The *Advanced Hold Options* link will remain for records that have
846 a mix of parted and non-parted copies.
859 Renewals attempted via SIP will now consider whether a penalty is configured
860 to block renewals before blocking the renewal. Previously, any penalty, even
861 if it wasn't set to block renewals, would prevent a renewal from succeeding
868 Treat SIP Location Field as Login Workstation
869 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
870 When using a version of SIPServer that supports the feature,
871 the Location (CP) field of the Login (93) message will be
872 used as the workstation name if supplied. Blank or missing
873 location fields will be ignored. This allows users or reports
874 to determine which selfcheck performed a circulation.
887 Translations in this release have been significantly increased. In
888 particular, Spanish has received a huge update with over 9,000 new
889 translations, Czech has received a sizable update of over 800
890 translations, and additional smaller updates have been added for
891 Arabic, French (Canada), and Armenian.
895 2.11.0 Acknowledgments
896 ----------------------
897 The Evergreen project would like to acknowledge the following
898 organizations that commissioned developments in this release of
902 * Georgia Public Library Service
904 * Pennsylvania Integrated Library System
905 * Pioneer Library System
907 We would also like to thank the following individuals who contributed
908 code, management, translations, documentation patches and tests to this
909 release of Evergreen:
929 We also thank the following organizations whose employees contributed
933 * Central/Wester Massachusetts Automated Resource Sharing
934 * Equinox Software, Inc.
935 * Emerald Data Networks, Inc.
937 * Georgia Public Library Service
938 * King County Library System
940 * Laurentian University
943 * North of Boston Library Exchange
944 * Traverse Area District Library
946 We regret any omissions. If a contributor has been inadvertently
947 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / working / Evergreen.git / blob