1 Evergreen 2.11 Release Notes
2 ============================
8 This release contains a bug fix improving on Evergreen 2.11.8.
10 * The option to add a title to My List is removed from Group Formats and
11 Editions searches where the option never worked correctly due to a bad id.
15 We would like to thank the following individuals who contributed code,
16 tests and documentation patches to the 2.11.9 point release of
25 This release contains several bug fixes improving on Evergreen 2.11.7.
27 * Hides the _Hold is Behind Circ Desk_ checkbox in the XUL client's patron
28 registration screen for those libraries that have not enabled Behind Desk Pickup
29 support via the Library Settings Editor
30 * Adds a missing error string that appears when marking an item damaged from
32 * Changes the hold request form so that it no longer defaults to the first SMS
33 carrier for text notifications.
34 * Adds a requirement for users to enter a phone/SMS number when they have
35 enabled that notification method on the hold request form.
36 * Changes the URL pointing to catalog images, CSS and javascript files to a full
37 absolute URL instead of the relative URL previously used. This change fixes an
38 issue with the Open Graph image property, which requires a full URL.
39 * Fixes an issue where payment amounts sent to Stripe can be one cent less than
40 the actual Evergreen payment.
44 We would like to thank the following individuals who contributed code,
45 tests and documentation patches to the 2.11.8 point release of
59 This release of Evergreen contains a fix to the _Hold/Copy Ratio per Bib
60 and Pickup Library (and Descendants)_ data source. Report templates using
61 this data source will need to be re-created to improve accuracy of the
62 data reported from this source.
66 This release contains several bug fixes improving on Evergreen 2.11.6
68 * Improvements to CSS to silence some Mozilla extension warnings.
69 * A fix to a failure to update targeted circulations when utilzing the recall
71 * The addition of text wrapping in the copy details table on the bib
72 record to prevent contents from falling off the page.
73 * A fix to the adjust to zero option so that it can be applied correctly
75 * A fix to the "Hold/Copy Ratio per Bib and Pickup Library
76 (and Descendants)" data source so that it will now include counts of eligible
77 copies at locations that are not a pickup library for bib's holds.
81 We would like to thank the following individuals who contributed code,
82 tests and documentation patches to the 2.11.7 point release of
97 This release contains several bug fixes improving on Evergreen 2.11.5.
99 * Code to prevent a hold already on the Holds Shelf from being
100 transferred to another title.
101 * A fix to a bug that prevented users from scheduling reports with a
102 relative month if the report template used a date that applied the Year +
103 Month transform with the On or After (>=) operator.
104 * A fix to a bug where the max fines threshold was reached prematurely
105 due to the presence of account adjustments.
106 * A check that prevents a SMS message from sending if the SMS carrier
111 We would like to thank the following individuals who contributed code,
112 tests and documentation patches to the 2.11.6 point release of
124 This release is a security release that also contains several other bug
125 fixes improving on Evergreen 2.11.4.
127 Security Issue: XSS Vulnerability in Public Catalog
128 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
129 This release fixes several cross-site scripting (XSS) vulnerabilities
130 in the public catalog. When upgrading, Evergreen administrators should
131 review whether any of the following templates have been customized
132 or overridden. If so, either the template should be replaced with the
133 stock version or the XSS fix (which entails adding the `| html` filter
134 in several places) applied to the customized version.
136 * `Open-ILS/src/templates/opac/parts/locale_picker.tt2`
137 * `Open-ILS/src/templates/opac/parts/login/form.tt2`
138 * `Open-ILS/src/templates/opac/parts/searchbar.tt2`
142 * A fix to remove the Chilifresh patron reviews header for Evergreen sites
143 that do not use Chilifresh.
144 * A fix that marks acquisitions POs as received when all line items on the
145 PO are received or canceled.
146 * A typo fix to the long overdue override permission that prevented staff
147 from being able to override long overdue check ins.
148 * A fix to use a library's configured currency in SIP patron responses
149 instead of always using US dollars.
150 * A fix to SIP timeouts caused by invalid sessions
151 * A fix that allows boolean fields to be recognized in queries to the
153 * A fix to use the correct method during adjust to zero on negative
155 * A correction to the datatype for the Vandelay Default Record Match Set
157 * The removal of the _Keep_ field from MARC Batch Import Item Attributes.
158 The field was not previously implemented.
159 * A fix to set the complete time value for grouped Action/Trigger events
160 when an event's state reach complete, consistent with non-grouped events.
161 * A fix to a bug in the rollover_phone_to_print.pl script that kept failed
162 call files from being moved.
163 * A new index for acq.edi_message that speeds up the check for duplicate
165 * A fix that ensures JSON strings are converted to UTF8, ensuring that
166 non-ASCII data display correctly.
167 * A fix to avoid an erroneous unsaved data popup to appear during MARC
172 We would like to thank the following individuals who contributed code,
173 testing and documentation patches to the 2.11.5 point release of
197 This release contains several bug fixes improving on Evergreen 2.11.3.
199 * A fix to avoid fetching and creating EDI message entries that the
201 * A fix to prevent staff users from marking a long overdue item as lost
202 so that the patron will not be billed twice for the same item.
203 * A fix to the link that is used on the catalog's Library Info page so
204 that links with anchors can be successfully retrieved.
205 * A replacement for the blank fallback image used when the catalog cannot
206 retrieve an added content book cover.
207 * An EDI fix that prevents EDI fetcher from crashing when the vendor
208 supplies a zero-length file.
209 * A fix to an issue where adjusting a bill to zero for a current checkout
210 prematurely closes the transaction.
211 * A fix to encoding problems in MODS output. These problems caused issues
212 when using Zotero with records in the catalog.
213 * A fix to Evergreen self-check to accept the user name value when a barcode
214 regex has been configured for the system.
215 * A fix to duplicate name checking in the patron registration screen so that
216 clicking the "Found x patron(s) with same name" link will retrieve potential
217 duplicate inactive patrons.
218 * A fix to the bower install step used when installing the web staff client.
219 * A fix that marks a hold as fulfilled when staff check out a hold-
220 captured item for a hold whose expire time is in the past.
221 * A change to the acquisitions funding source funds drop down menu so that
222 the menu will now only display active funds and will also display the
223 year alongside the fund.
224 * A fix to a problem where the Current Bills tab of the patron record
225 showed duplicate charges when a check in was done from the Items Out tab.
226 * 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.
227 * A change to the fund year selectors in acq interfaces so that the years
228 are sorted in descending order.
229 * A fix to a billing issue where transactions were not re-opened after
230 they acquired a non-zero balance at check in.
231 * A change to the default pickup library when staff place a hold. The place hold
232 screen will now default to the preferred pickup location for the patron. If the
233 patron does not have a preferred pickup location, it will default to the
234 patron's home library.
235 * The ability to skip the XUL staff client build when in make_release.
236 * A fix that silences a log warning that appears for every checkout where a hard
237 due date is not used.
241 We would like to thank the following individuals who contributed code,
242 testing and documentation patches to the 2.11.4 point release of
269 This is a security release that also contains several other bugfixes improving
270 on Evergreen 2.11.2. All users of Evergreen 2.11.x are recommended to upgrade
271 to 2.11.3 as soon as possible.
273 Security Issue: Credit Processor Stripe Settings Permissions
274 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
275 Unprivileged users can retrieve organizational unit setting values for
276 setting types lacking a "view" permission. When the feature adding
277 Stripe credit card processing was added, the upgrade script neglected
278 to add the VIEW_CREDIT_CARD_PROCESSING permission to the
279 organizational unit setting type. This means that anyone can retrieve
280 and view the settings for Stripe credit card processing.
282 Any system that upgraded from Evergreen version 2.5 to 2.6 is
283 affected. If you use Stripe for credit card processing, it is
284 strongly recommended that you apply this upgrade. Even if you do not
285 use Stripe, applying this upgrade is still recommended. If you did
286 not upgrade from version 2.5 to 2.6 of Evergreen, but started with a
287 later version, applying this upgrade is harmless.
289 If you are not ready to perform a full upgrade, and if you use Stripe,
290 you can protect the settings by running the following two SQL statements:
294 UPDATE config.org_unit_setting_type
295 SET view_perm = (SELECT id FROM permission.perm_list
296 WHERE code = 'VIEW_CREDIT_CARD_PROCESSING' LIMIT 1)
297 WHERE name LIKE 'credit.processor.stripe%' AND view_perm IS NULL;
299 UPDATE config.org_unit_setting_type
300 SET update_perm = (SELECT id FROM permission.perm_list
301 WHERE code = 'ADMIN_CREDIT_CARD_PROCESSING' LIMIT 1)
302 WHERE name LIKE 'credit.processor.stripe%' AND update_perm IS NULL;
305 Missing Upgrade Script Notice
306 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
307 It was recently discovered that the 2.11.2 tarball was missing the
308 upgrade script for 2.11.1. If you upgraded straight to 2.11.2 from
309 2.11.0 or prior, please make sure to apply the
310 2.11.0-2.11.1-upgrade-db.sql before moving on to the 2.11.3 script.
314 Evergreen 2.11.3 also contains the following bugfixes:
316 * A fix to correctly apply floating group settings when performing
318 * An improvement to the speed of looking up patrons by their username;
319 this is particularly important for large databases.
320 * A fix to properly display the contents of temporary lists ('My List') in the
321 public catalog, as well as a fix of the HTML coding of that page.
322 * A fix to the Spanish translation of the public catalog that could
323 cause catalog searches to fail.
324 * A fix of a problem where certain kinds of requests of information
325 about the organizational unit hierarchy to consume all available
326 `open-ils.cstore` backends.
327 * A fix to allow staff to use the 'place another hold' link without
328 running into a user interface loop.
329 * A fix to the 'Edit Due Date' form in the web staff client.
330 * A fix to the definition of the stock 'Full Overlay' merge profile.
331 * A fix to sort billing types in alphabetical order in the web staff
333 * A fix to the display of the popularity score in the public catalog.
334 * A fix to the 'return to grouped search results' link in the public
336 * A fix to allow pre-cat checkouts in the web staff client without requiring
337 a circulation modifier.
338 * A fix to how Action/Trigger event definitions with nullable grouping
339 fields handle null values.
340 * Other typo and documentation fixes.
344 We would like to thank the following individuals who contributed code,
345 testing and documentation patches to the 2.11.3 point release of
368 This release contains several bugfixes improving on Evergreen 2.11.1
370 * A fix to the web client patron interface that changed the holds count in the
371 patron summary from total / available to available / total.
372 * A fix to an issue where the Closed Dates Editor was displaying an extra day of
374 * A fix to the Closed Dates Editor so that it now displays "All Day" when the
375 library is closed for the entire day.
376 * A fix to properly format LC Call numbers in spine label printing.
377 * A fix to a bug that was causing intermittent search failures.
378 * A fix to a bug that was causing search failures for Copy Location Group
380 * A fix to significant increased slowness with holds transfers.
381 * The addition of an index to the action.aged_circulation table to resolve a
382 problem with long-running queries.
383 * A fix to redirects that for one-hit metarecord searches for systems that
384 have enabled the setting to immediately jump to a bib record on one-hit searches.
385 * A fix to the new acquisitions cost field available in the copy editor to
386 resolve an issue where accidentally clearing out the value in the field resulted
388 * A fix to a bug that broke the Alternate Printable Hold Pull List and Vandelay
389 uploads on systems that were running OpenSRF 2.5.
393 We would like to thank the following individuals who contributed code,
394 testing and documentation patches to the 2.11.1 point release of
413 This release contains several bug fixes improving on Evergreen 2.11.0
415 * A fix to that provides alphabetical sorting to the fund selector in
416 the Acquisitions Selection List -> Copies interface.
417 * A fix to the web client check in screen allowing users to click the
418 title of the checked-in item to retrieve the bib record for that item.
419 * The addition of a progress bar that displays when conducting a patron searchin the web client.
420 * A fix to the web client patron interface so that total Items Out in the
421 patron summary now includes overdue and long overdue items. It will also
422 include Lost and Claims Returned items when the appropriate library
424 * A change to the public catalog My Account screen where the font for
425 leading articles will now be smaller when sorting a list by title.
426 * A fix to subject links in the catalog's record summary page so that
427 periods are no longer stripped from resulting subject searches, leading
428 to more accurate results when those links are clicked.
429 * A fix to avoid unint warnings in the logs for prox_cache in
430 open-ils.circ.hold.is_possible.
431 * A fix to rounding errors that occurred when summing owed/paid totals
432 for display in the catalog's credit card payment form.
433 * A change to sort behavior in the My Account screens. Previously, a
434 third click on a column header returned the list to its original sort
435 order. Clicking column headers will now simply toggle the sort
436 between ascending and descending order.
437 * The Permalink option on the catalog's record summary page will now be
438 hidden in the staff client because clicking the link in the client led
439 to no discernible change for users.
440 * A fix to the display of permanent lists in the catalog, which had broken
442 * A fix to the text of a notice that displays when migrating circulation
443 history during the upgrade to 2.10.
444 * An improvement to the performance for the lookup of a user's circ
445 history by adding an index on action.usr_circ_history(usr).
446 * A fix so that when a bib record's fingerprint changes, it gets correctly
447 moved to a different metarecord.
451 We would like to thank the following individuals who contributed code,
452 tests and documentation patches to the 2.11.1 point release of
471 Tablefunc Extension No Longer Required
472 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
473 Changes in the behavior of the connectby function in PostgreSQL 9.5
474 have prompted its removal from the database. It is easier for
475 Evergreen to maintain compatibility with previous versions of
476 PostgreSQL without this function.
478 By eliminating the use of the connectby function, we eliminate the
479 requirement for the tablefunc database extension. It is no longer
480 installed when the database is created. If you are upgrading and wish
481 to remove it from your database, you may run the following statement
482 in the database to drop it:
484 DROP EXTENSION tablefunc;
500 Add Date Header to Action Trigger Email/SMS Templates
501 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
502 The Date: header specified in RFC 2822 has been added to the seed data
503 for the example Action Trigger email and SMS templates, but no attempt
504 has been made to automatically modify existing templates. To add this
505 header (and end any "Why are my library emails from 1969/70?" questions
506 you may have heard) make sure the following lines are in all templates
507 that use the SendEmail or SendSMS reactors:
509 The first is already in most sample templates, but you may need to add
510 it to the top of any custom templates:
513 And this line should be inserted into the header block of each template:
514 `Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]`
520 Support for Ubuntu 16.04
521 ^^^^^^^^^^^^^^^^^^^^^^^^
522 Adds support for Ubuntu Xenial Xerus (16.04).
531 User activity types are now set to transient by default for new
532 Evergreen installs.. This means only the most recent activity entry per
533 user per activity type is retained in the database.
535 This change does not affect existing activity types, which were set to
536 non-transient by default. To make an activity type transient, modify the
537 'Transient' field of the desired type in the staff client under Admin ->
538 Server Administration -> User Activity Types.
540 Setting an activity type to transient means data for a given user will
541 be cleaned up automatically if and when the user performs the activity
542 in question. However, administrators can also force an activity
543 cleanup via SQL. This is useful for ensuring that all old activity
544 data is deleted and for controlling when the cleanup occurs, which
545 may be useful on very large actor.usr_activity tables.
547 To force clean all activity types:
550 ------------------------------------------------------------
551 SELECT actor.purge_usr_activity_by_type(etype.id)
552 FROM config.usr_activity_type etype;
553 ------------------------------------------------------------
555 NOTE: This could take hours to run on a very large actor.usr_activity table.
566 Authority Record Import Updates Editor, Edit Date.
567 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
568 Importing an authority record via MARC Batch Import/Export now causes the
569 authority record's editor and edit_date fields to be updated. The editor
570 value may come from the MARC 905u field or, if none is present, the user
571 performing the import.
576 Authority Propagation Updates Bib Editor / Edit Date
577 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
578 When a bib record is automatically updated as a result of the
579 modification of a linked authority record, the bib record's "Last Edit
580 Date/Time" and "Last Editing User" fields will be updated to match the
581 time of the update and the editor of the modified authority record.
583 A new global flag is available to control this behavior called
584 'ingest.disable_authority_auto_update_bib_meta' ("Authority Automation:
585 Disable automatic authority updates from modifying bib record editor
586 and edit_date"). When enabled, theses fields will not be updated. By
587 default, this setting is disabled.
589 An additional speed improvement is included in this feature. No attempt
590 will be made to update linked bib records when the normalized heading of
591 the modified authority record is unchanged by the authority record update.
596 Bibliographic Record Source Now Copied to 901$s
597 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
598 If a bibliographic record has a source set, the name of that source
599 is now copied to the 901$s whenever the record is created or updated.
600 This allows the source to be used for record matching and MARC
606 Option to Update Bib Source and Edit Details on Record Import
607 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
608 When importing records through the client, users will now have the ability to
609 define whether the bib source, last editor, and last edit date should be updated
610 on a record merge/overlay.
612 In MARC Batch Import / Export, select the _Merge / Overlay_ tab. Each entry in
613 the table has a value in the new _Update bib. source_ column. If that value is
614 True, then the bib source, last editor, and last edit date will be updated.
616 The two system-defined entries have been pre-set to appropriate values (Full
617 Overlay = true; Match-Only Merge = false).
627 Staff Client Honors Aged Circulations
628 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
630 The browser and XUL clients now better represent copy checkout history
631 by honoring and displaying information from aged circulations.
633 * Browser client 'Recent Circ History' and the analogous XUL client
634 'Circulation History' tabs show summary data for aged circulations
635 as well as regular/active circulations. When aged circulation data
636 is displayed, any references to patron names are replaced by the string
637 "<Aged Circulation>".
639 * Browser client 'Circ History List' and the analogous XUL client
640 'Last Few Circulations' tabs behave as above, plus their 'Add
641 Billing' buttons are disabled when displaying aged circulation data.
643 * XUL client 'Retrieve Last Patron' actions from various UI's report,
644 "Item XXX circulation is an aged circulation and has no linked user".
645 Browser client analog uses 'Circ History List' instead; no additional
652 "Canceled Transit" Item Status
653 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
655 Previously, when a transit was aborted, the transited item would either go into
656 "Reshelving" status or would return to whatever status it was in when it went
657 into transit, even when the item itself was in a different status (including
658 "Checked out"). Now, for most transits that get aborted, the item is put into a
659 new status, "Canceled Transit", which signals to staff the actual state of the
660 item. This feature only affects items with a status of "In transit" and does
661 not affect items that were in the following statuses at the time they were sent
672 * Any custom statuses
674 This change should help clear up confusing situations caused by the previous
675 "abort transit" behavior, such as items showing "Available" when they are actually
676 en route, and patrons' items mysteriously disappearing from their accounts and
677 showing "Available" at the item-owning library without evidence of check-in.
682 Copy Status "Is Available" Flag
683 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
685 A new boolean field is now available for copy statuses to indicate when copies
686 having a given status should be considered available. The field has 2 main
689 1. Checking out an "available" copy will no longer result in an override-able
690 "COPY_NOT_AVAILABLE" alert for staff. The copy will checkout without
693 2. "Available" copies will appear in catalog searches where "limit to
694 available" is selected as a search filter.
696 By default, the "Available" and "Reshelving" statuses have the "Is Available"
697 flag set. The flag may be applied to local/custom statuses via the copy
698 status admin interface.
704 Email Checkout Receipts
705 ^^^^^^^^^^^^^^^^^^^^^^^
706 This feature allows patrons to receive checkout receipts through email
707 at the circulation desk in the web client and in the Evergreen self-checkout
708 interface. Patrons need to opt in to receive
709 email receipts by default and must have an email address associated with their
710 account. Opt in can be staff mediated at the time of account creation or in
711 existing accounts. Patrons can also opt in directly in their OPAC account or
712 through patron self-registration. This feature does not affect the behavior of
713 checkouts from the XUL client or SIP2 devices.
715 Patrons can opt in to receive email checkout receipts by default via
716 a new _Email checkout receipts by default_ patron setting.
718 This feature also enhances the patron staging tables so that patron
719 settings can be chosen during self-registration.
721 The web staff interface's checkout screen now includes a "Quick
722 Receipt" button that allows staff members to generate a receipt
728 Set Per-OU Limits on Allowed Payment Amounts
729 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
730 Two new settings have been added to prevent clerks from accidentally clearing
731 all patron bills by scanning a barcode into the Payment Amount field, or
732 accidentally entering the amount without a decimal point (such as you
733 would when using a cash register).
735 Both settings are available via the Library Settings Editor. The _Payment
736 amount threshold for Are You Sure? dialog_ (ui.circ.billing.amount_warn)
737 setting identifies the amount above
738 which staff will be asked if they're sure they want to apply the payment.
739 The _Maximum payment amount allowed_ (ui.circ.billing.amount_limit)
740 setting identifies the maximum amount of
741 money that can be accepted through the staff client.
743 These settings only affect the staff client, not credit
744 cards accepted through the OPAC, or direct API calls
745 from third party tools.
755 Additional Fields Available for Display in Some Interfaces
756 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
757 The holds age protection field will now be available for display in the
758 following interfaces:
760 * Item status list view column picker
761 * Item status alternate view
762 * Holdings maintenance column picker
764 The asset.copy.cost field, which records the amount paid for an item when
765 an invoice is processed, will be available for display in the following
768 * Items status list view column picker
769 * Item status alternate view
781 Merge Notification Preferences Tables in TPAC
782 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
783 The patron notification preference page in the public catalog
784 used to have two tables, separating notification settings
785 based on their source. Since that distinction does not matter
786 to patrons, and since the two tables aren't styled consistently,
787 they are merged together.
792 Improved Holds Screens in My Account
793 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
794 The grids in the My Account _Items on Hold_ and _Holds History_ interfaces are
795 simplified. Data previously contained in their own Activate, Active, and Date
796 Fulfilled columns are now incorporated into the Status column. To further
797 declutter the interface, the holds queue position will only show when the user
798 most needs the information - before the hold has been captured.
800 Distinct CSS classes have also been added for each hold status and each date
801 that could potentially display in these holds interfaces. A new default style
802 highlights the _Available_ status in green and the _Suspended_ status
810 Popularity Boost for Ranking Search Results
811 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
813 This feature uses factors such as circulation and hold activity, record and item age, and item ownership counts to generate popularity badges for bibliographic
814 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.
816 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.
818 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.
820 Finally, there will continue to be a pure _Relevance_ sort option, which is the version that exists today.
822 Administrators can comment out one of the available sort methods by editing the
823 filtersort.tt2 file.A global flag will allow Evergreen sites to select a default sort method.
828 Administrative interfaces to configure badges are only available in the web
829 client. Administrators can also configure badges directly via the database.
831 Available Popularity Parameters available for badges include:
833 * Holds Filled Over Time
834 * Holds Requested Over Time
836 * Circulations Over Time
837 * Current Circulation Count
840 * Holds/Holdable Ratio
841 * Percent of Time Circulating
842 * Bibliographic Record Age (days)
843 * Publication Age (days)
844 * Available On-Line (for e-books, etc)
847 Badges can be configured to apply to a targeted group of bibliographic records
848 based on the following available filters:
851 * Bibliographic source
852 * Circulation modifier
853 * Copy location group
855 Badges can also be be restricted to materials owned by a specific organizational
858 This new feature comes with a starter badge based on the top 97th percentile of
859 holds requested over the past five years.
864 Ratings for records will be displayed in the catalog in the following ways:
866 * On the record result page, the overall average popularity rating is displayed with a label of _Popularity_.
868 * On the record detail page, each individual badge earned by the record is
869 displayed with its rating.
873 * **OPAC Default Sort (opac.default_sort)**: Identifies the default sort method
874 to be used in the catalog.
876 * **Maximum popularity importance multiplier for popularity-adjusted relevance
877 searches (search.max_popularity_importance_multiplier):** A multiplier identifying
878 the importance of popularity in the Popularity-Adjusted Relevance ranked
879 searches. The number should be a decimal ranging between 1.0 and 2.0. The
880 default value is 1.1.
882 More detailed information is available in the TechRef docs directory of the
883 Evergreen source code.
888 Removal of Advanced Hold Options link when part holds are expected
889 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
890 If a user attempts to place a metarecord hold when all eligible copies
891 contain parts, the hold will fail. To help prevent the user from reaching
892 a dead end while placing holds, the *Advanced Hold Options* link is removed
893 from the Place Hold page in cases where all copies on the record contain
894 parts. The *Advanced Hold Options* link will remain for records that have
895 a mix of parted and non-parted copies.
908 Renewals attempted via SIP will now consider whether a penalty is configured
909 to block renewals before blocking the renewal. Previously, any penalty, even
910 if it wasn't set to block renewals, would prevent a renewal from succeeding
917 Treat SIP Location Field as Login Workstation
918 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
919 When using a version of SIPServer that supports the feature,
920 the Location (CP) field of the Login (93) message will be
921 used as the workstation name if supplied. Blank or missing
922 location fields will be ignored. This allows users or reports
923 to determine which selfcheck performed a circulation.
936 Translations in this release have been significantly increased. In
937 particular, Spanish has received a huge update with over 9,000 new
938 translations, Czech has received a sizable update of over 800
939 translations, and additional smaller updates have been added for
940 Arabic, French (Canada), and Armenian.
944 2.11.0 Acknowledgments
945 ----------------------
946 The Evergreen project would like to acknowledge the following
947 organizations that commissioned developments in this release of
951 * Georgia Public Library Service
953 * Pennsylvania Integrated Library System
954 * Pioneer Library System
956 We would also like to thank the following individuals who contributed
957 code, management, translations, documentation patches and tests to this
958 release of Evergreen:
978 We also thank the following organizations whose employees contributed
982 * Central/Wester Massachusetts Automated Resource Sharing
983 * Equinox Software, Inc.
984 * Emerald Data Networks, Inc.
986 * Georgia Public Library Service
987 * King County Library System
989 * Laurentian University
992 * North of Boston Library Exchange
993 * Traverse Area District Library
995 We regret any omissions. If a contributor has been inadvertently
996 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / working / Evergreen.git / blob