1 Evergreen 2.11 Release Notes
2 ============================
8 This release contains several bug fixes improving on Evergreen 2.11.7.
10 * Hides the _Hold is Behind Circ Desk_ checkbox in the XUL client's patron
11 registration screen for those libraries that have not enabled Behind Desk Pickup
12 support via the Library Settings Editor
13 * Adds a missing error string that appears when marking an item damaged from
15 * Changes the hold request form so that it no longer defaults to the first SMS
16 carrier for text notifications.
17 * Adds a requirement for users to enter a phone/SMS number when they have
18 enabled that notification method on the hold request form.
19 * Changes the URL pointing to catalog images, CSS and javascript files to a full
20 absolute URL instead of the relative URL previously used. This change fixes an
21 issue with the Open Graph image property, which requires a full URL.
22 * Fixes an issue where payment amounts sent to Stripe can be one cent less than
23 the actual Evergreen payment.
27 We would like to thank the following individuals who contributed code,
28 tests and documentation patches to the 2.11.8 point release of
42 This release of Evergreen contains a fix to the _Hold/Copy Ratio per Bib
43 and Pickup Library (and Descendants)_ data source. Report templates using
44 this data source will need to be re-created to improve accuracy of the
45 data reported from this source.
49 This release contains several bug fixes improving on Evergreen 2.11.6
51 * Improvements to CSS to silence some Mozilla extension warnings.
52 * A fix to a failure to update targeted circulations when utilzing the recall
54 * The addition of text wrapping in the copy details table on the bib
55 record to prevent contents from falling off the page.
56 * A fix to the adjust to zero option so that it can be applied correctly
58 * A fix to the "Hold/Copy Ratio per Bib and Pickup Library
59 (and Descendants)" data source so that it will now include counts of eligible
60 copies at locations that are not a pickup library for bib's holds.
64 We would like to thank the following individuals who contributed code,
65 tests and documentation patches to the 2.11.7 point release of
80 This release contains several bug fixes improving on Evergreen 2.11.5.
82 * Code to prevent a hold already on the Holds Shelf from being
83 transferred to another title.
84 * A fix to a bug that prevented users from scheduling reports with a
85 relative month if the report template used a date that applied the Year +
86 Month transform with the On or After (>=) operator.
87 * A fix to a bug where the max fines threshold was reached prematurely
88 due to the presence of account adjustments.
89 * A check that prevents a SMS message from sending if the SMS carrier
94 We would like to thank the following individuals who contributed code,
95 tests and documentation patches to the 2.11.6 point release of
107 This release is a security release that also contains several other bug
108 fixes improving on Evergreen 2.11.4.
110 Security Issue: XSS Vulnerability in Public Catalog
111 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
112 This release fixes several cross-site scripting (XSS) vulnerabilities
113 in the public catalog. When upgrading, Evergreen administrators should
114 review whether any of the following templates have been customized
115 or overridden. If so, either the template should be replaced with the
116 stock version or the XSS fix (which entails adding the `| html` filter
117 in several places) applied to the customized version.
119 * `Open-ILS/src/templates/opac/parts/locale_picker.tt2`
120 * `Open-ILS/src/templates/opac/parts/login/form.tt2`
121 * `Open-ILS/src/templates/opac/parts/searchbar.tt2`
125 * A fix to remove the Chilifresh patron reviews header for Evergreen sites
126 that do not use Chilifresh.
127 * A fix that marks acquisitions POs as received when all line items on the
128 PO are received or canceled.
129 * A typo fix to the long overdue override permission that prevented staff
130 from being able to override long overdue check ins.
131 * A fix to use a library's configured currency in SIP patron responses
132 instead of always using US dollars.
133 * A fix to SIP timeouts caused by invalid sessions
134 * A fix that allows boolean fields to be recognized in queries to the
136 * A fix to use the correct method during adjust to zero on negative
138 * A correction to the datatype for the Vandelay Default Record Match Set
140 * The removal of the _Keep_ field from MARC Batch Import Item Attributes.
141 The field was not previously implemented.
142 * A fix to set the complete time value for grouped Action/Trigger events
143 when an event's state reach complete, consistent with non-grouped events.
144 * A fix to a bug in the rollover_phone_to_print.pl script that kept failed
145 call files from being moved.
146 * A new index for acq.edi_message that speeds up the check for duplicate
148 * A fix that ensures JSON strings are converted to UTF8, ensuring that
149 non-ASCII data display correctly.
150 * A fix to avoid an erroneous unsaved data popup to appear during MARC
155 We would like to thank the following individuals who contributed code,
156 testing and documentation patches to the 2.11.5 point release of
180 This release contains several bug fixes improving on Evergreen 2.11.3.
182 * A fix to avoid fetching and creating EDI message entries that the
184 * A fix to prevent staff users from marking a long overdue item as lost
185 so that the patron will not be billed twice for the same item.
186 * A fix to the link that is used on the catalog's Library Info page so
187 that links with anchors can be successfully retrieved.
188 * A replacement for the blank fallback image used when the catalog cannot
189 retrieve an added content book cover.
190 * An EDI fix that prevents EDI fetcher from crashing when the vendor
191 supplies a zero-length file.
192 * A fix to an issue where adjusting a bill to zero for a current checkout
193 prematurely closes the transaction.
194 * A fix to encoding problems in MODS output. These problems caused issues
195 when using Zotero with records in the catalog.
196 * A fix to Evergreen self-check to accept the user name value when a barcode
197 regex has been configured for the system.
198 * A fix to duplicate name checking in the patron registration screen so that
199 clicking the "Found x patron(s) with same name" link will retrieve potential
200 duplicate inactive patrons.
201 * A fix to the bower install step used when installing the web staff client.
202 * A fix that marks a hold as fulfilled when staff check out a hold-
203 captured item for a hold whose expire time is in the past.
204 * A change to the acquisitions funding source funds drop down menu so that
205 the menu will now only display active funds and will also display the
206 year alongside the fund.
207 * A fix to a problem where the Current Bills tab of the patron record
208 showed duplicate charges when a check in was done from the Items Out tab.
209 * 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.
210 * A change to the fund year selectors in acq interfaces so that the years
211 are sorted in descending order.
212 * A fix to a billing issue where transactions were not re-opened after
213 they acquired a non-zero balance at check in.
214 * A change to the default pickup library when staff place a hold. The place hold
215 screen will now default to the preferred pickup location for the patron. If the
216 patron does not have a preferred pickup location, it will default to the
217 patron's home library.
218 * The ability to skip the XUL staff client build when in make_release.
219 * A fix that silences a log warning that appears for every checkout where a hard
220 due date is not used.
224 We would like to thank the following individuals who contributed code,
225 testing and documentation patches to the 2.11.4 point release of
252 This is a security release that also contains several other bugfixes improving
253 on Evergreen 2.11.2. All users of Evergreen 2.11.x are recommended to upgrade
254 to 2.11.3 as soon as possible.
256 Security Issue: Credit Processor Stripe Settings Permissions
257 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
258 Unprivileged users can retrieve organizational unit setting values for
259 setting types lacking a "view" permission. When the feature adding
260 Stripe credit card processing was added, the upgrade script neglected
261 to add the VIEW_CREDIT_CARD_PROCESSING permission to the
262 organizational unit setting type. This means that anyone can retrieve
263 and view the settings for Stripe credit card processing.
265 Any system that upgraded from Evergreen version 2.5 to 2.6 is
266 affected. If you use Stripe for credit card processing, it is
267 strongly recommended that you apply this upgrade. Even if you do not
268 use Stripe, applying this upgrade is still recommended. If you did
269 not upgrade from version 2.5 to 2.6 of Evergreen, but started with a
270 later version, applying this upgrade is harmless.
272 If you are not ready to perform a full upgrade, and if you use Stripe,
273 you can protect the settings by running the following two SQL statements:
277 UPDATE config.org_unit_setting_type
278 SET view_perm = (SELECT id FROM permission.perm_list
279 WHERE code = 'VIEW_CREDIT_CARD_PROCESSING' LIMIT 1)
280 WHERE name LIKE 'credit.processor.stripe%' AND view_perm IS NULL;
282 UPDATE config.org_unit_setting_type
283 SET update_perm = (SELECT id FROM permission.perm_list
284 WHERE code = 'ADMIN_CREDIT_CARD_PROCESSING' LIMIT 1)
285 WHERE name LIKE 'credit.processor.stripe%' AND update_perm IS NULL;
288 Missing Upgrade Script Notice
289 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
290 It was recently discovered that the 2.11.2 tarball was missing the
291 upgrade script for 2.11.1. If you upgraded straight to 2.11.2 from
292 2.11.0 or prior, please make sure to apply the
293 2.11.0-2.11.1-upgrade-db.sql before moving on to the 2.11.3 script.
297 Evergreen 2.11.3 also contains the following bugfixes:
299 * A fix to correctly apply floating group settings when performing
301 * An improvement to the speed of looking up patrons by their username;
302 this is particularly important for large databases.
303 * A fix to properly display the contents of temporary lists ('My List') in the
304 public catalog, as well as a fix of the HTML coding of that page.
305 * A fix to the Spanish translation of the public catalog that could
306 cause catalog searches to fail.
307 * A fix of a problem where certain kinds of requests of information
308 about the organizational unit hierarchy to consume all available
309 `open-ils.cstore` backends.
310 * A fix to allow staff to use the 'place another hold' link without
311 running into a user interface loop.
312 * A fix to the 'Edit Due Date' form in the web staff client.
313 * A fix to the definition of the stock 'Full Overlay' merge profile.
314 * A fix to sort billing types in alphabetical order in the web staff
316 * A fix to the display of the popularity score in the public catalog.
317 * A fix to the 'return to grouped search results' link in the public
319 * A fix to allow pre-cat checkouts in the web staff client without requiring
320 a circulation modifier.
321 * A fix to how Action/Trigger event definitions with nullable grouping
322 fields handle null values.
323 * Other typo and documentation fixes.
327 We would like to thank the following individuals who contributed code,
328 testing and documentation patches to the 2.11.3 point release of
351 This release contains several bugfixes improving on Evergreen 2.11.1
353 * A fix to the web client patron interface that changed the holds count in the
354 patron summary from total / available to available / total.
355 * A fix to an issue where the Closed Dates Editor was displaying an extra day of
357 * A fix to the Closed Dates Editor so that it now displays "All Day" when the
358 library is closed for the entire day.
359 * A fix to properly format LC Call numbers in spine label printing.
360 * A fix to a bug that was causing intermittent search failures.
361 * A fix to a bug that was causing search failures for Copy Location Group
363 * A fix to significant increased slowness with holds transfers.
364 * The addition of an index to the action.aged_circulation table to resolve a
365 problem with long-running queries.
366 * A fix to redirects that for one-hit metarecord searches for systems that
367 have enabled the setting to immediately jump to a bib record on one-hit searches.
368 * A fix to the new acquisitions cost field available in the copy editor to
369 resolve an issue where accidentally clearing out the value in the field resulted
371 * A fix to a bug that broke the Alternate Printable Hold Pull List and Vandelay
372 uploads on systems that were running OpenSRF 2.5.
376 We would like to thank the following individuals who contributed code,
377 testing and documentation patches to the 2.11.1 point release of
396 This release contains several bug fixes improving on Evergreen 2.11.0
398 * A fix to that provides alphabetical sorting to the fund selector in
399 the Acquisitions Selection List -> Copies interface.
400 * A fix to the web client check in screen allowing users to click the
401 title of the checked-in item to retrieve the bib record for that item.
402 * The addition of a progress bar that displays when conducting a patron searchin the web client.
403 * A fix to the web client patron interface so that total Items Out in the
404 patron summary now includes overdue and long overdue items. It will also
405 include Lost and Claims Returned items when the appropriate library
407 * A change to the public catalog My Account screen where the font for
408 leading articles will now be smaller when sorting a list by title.
409 * A fix to subject links in the catalog's record summary page so that
410 periods are no longer stripped from resulting subject searches, leading
411 to more accurate results when those links are clicked.
412 * A fix to avoid unint warnings in the logs for prox_cache in
413 open-ils.circ.hold.is_possible.
414 * A fix to rounding errors that occurred when summing owed/paid totals
415 for display in the catalog's credit card payment form.
416 * A change to sort behavior in the My Account screens. Previously, a
417 third click on a column header returned the list to its original sort
418 order. Clicking column headers will now simply toggle the sort
419 between ascending and descending order.
420 * The Permalink option on the catalog's record summary page will now be
421 hidden in the staff client because clicking the link in the client led
422 to no discernible change for users.
423 * A fix to the display of permanent lists in the catalog, which had broken
425 * A fix to the text of a notice that displays when migrating circulation
426 history during the upgrade to 2.10.
427 * An improvement to the performance for the lookup of a user's circ
428 history by adding an index on action.usr_circ_history(usr).
429 * A fix so that when a bib record's fingerprint changes, it gets correctly
430 moved to a different metarecord.
434 We would like to thank the following individuals who contributed code,
435 tests and documentation patches to the 2.11.1 point release of
454 Tablefunc Extension No Longer Required
455 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
456 Changes in the behavior of the connectby function in PostgreSQL 9.5
457 have prompted its removal from the database. It is easier for
458 Evergreen to maintain compatibility with previous versions of
459 PostgreSQL without this function.
461 By eliminating the use of the connectby function, we eliminate the
462 requirement for the tablefunc database extension. It is no longer
463 installed when the database is created. If you are upgrading and wish
464 to remove it from your database, you may run the following statement
465 in the database to drop it:
467 DROP EXTENSION tablefunc;
483 Add Date Header to Action Trigger Email/SMS Templates
484 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
485 The Date: header specified in RFC 2822 has been added to the seed data
486 for the example Action Trigger email and SMS templates, but no attempt
487 has been made to automatically modify existing templates. To add this
488 header (and end any "Why are my library emails from 1969/70?" questions
489 you may have heard) make sure the following lines are in all templates
490 that use the SendEmail or SendSMS reactors:
492 The first is already in most sample templates, but you may need to add
493 it to the top of any custom templates:
496 And this line should be inserted into the header block of each template:
497 `Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]`
503 Support for Ubuntu 16.04
504 ^^^^^^^^^^^^^^^^^^^^^^^^
505 Adds support for Ubuntu Xenial Xerus (16.04).
514 User activity types are now set to transient by default for new
515 Evergreen installs.. This means only the most recent activity entry per
516 user per activity type is retained in the database.
518 This change does not affect existing activity types, which were set to
519 non-transient by default. To make an activity type transient, modify the
520 'Transient' field of the desired type in the staff client under Admin ->
521 Server Administration -> User Activity Types.
523 Setting an activity type to transient means data for a given user will
524 be cleaned up automatically if and when the user performs the activity
525 in question. However, administrators can also force an activity
526 cleanup via SQL. This is useful for ensuring that all old activity
527 data is deleted and for controlling when the cleanup occurs, which
528 may be useful on very large actor.usr_activity tables.
530 To force clean all activity types:
533 ------------------------------------------------------------
534 SELECT actor.purge_usr_activity_by_type(etype.id)
535 FROM config.usr_activity_type etype;
536 ------------------------------------------------------------
538 NOTE: This could take hours to run on a very large actor.usr_activity table.
549 Authority Record Import Updates Editor, Edit Date.
550 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
551 Importing an authority record via MARC Batch Import/Export now causes the
552 authority record's editor and edit_date fields to be updated. The editor
553 value may come from the MARC 905u field or, if none is present, the user
554 performing the import.
559 Authority Propagation Updates Bib Editor / Edit Date
560 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
561 When a bib record is automatically updated as a result of the
562 modification of a linked authority record, the bib record's "Last Edit
563 Date/Time" and "Last Editing User" fields will be updated to match the
564 time of the update and the editor of the modified authority record.
566 A new global flag is available to control this behavior called
567 'ingest.disable_authority_auto_update_bib_meta' ("Authority Automation:
568 Disable automatic authority updates from modifying bib record editor
569 and edit_date"). When enabled, theses fields will not be updated. By
570 default, this setting is disabled.
572 An additional speed improvement is included in this feature. No attempt
573 will be made to update linked bib records when the normalized heading of
574 the modified authority record is unchanged by the authority record update.
579 Bibliographic Record Source Now Copied to 901$s
580 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
581 If a bibliographic record has a source set, the name of that source
582 is now copied to the 901$s whenever the record is created or updated.
583 This allows the source to be used for record matching and MARC
589 Option to Update Bib Source and Edit Details on Record Import
590 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
591 When importing records through the client, users will now have the ability to
592 define whether the bib source, last editor, and last edit date should be updated
593 on a record merge/overlay.
595 In MARC Batch Import / Export, select the _Merge / Overlay_ tab. Each entry in
596 the table has a value in the new _Update bib. source_ column. If that value is
597 True, then the bib source, last editor, and last edit date will be updated.
599 The two system-defined entries have been pre-set to appropriate values (Full
600 Overlay = true; Match-Only Merge = false).
610 Staff Client Honors Aged Circulations
611 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
613 The browser and XUL clients now better represent copy checkout history
614 by honoring and displaying information from aged circulations.
616 * Browser client 'Recent Circ History' and the analogous XUL client
617 'Circulation History' tabs show summary data for aged circulations
618 as well as regular/active circulations. When aged circulation data
619 is displayed, any references to patron names are replaced by the string
620 "<Aged Circulation>".
622 * Browser client 'Circ History List' and the analogous XUL client
623 'Last Few Circulations' tabs behave as above, plus their 'Add
624 Billing' buttons are disabled when displaying aged circulation data.
626 * XUL client 'Retrieve Last Patron' actions from various UI's report,
627 "Item XXX circulation is an aged circulation and has no linked user".
628 Browser client analog uses 'Circ History List' instead; no additional
635 "Canceled Transit" Item Status
636 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
638 Previously, when a transit was aborted, the transited item would either go into
639 "Reshelving" status or would return to whatever status it was in when it went
640 into transit, even when the item itself was in a different status (including
641 "Checked out"). Now, for most transits that get aborted, the item is put into a
642 new status, "Canceled Transit", which signals to staff the actual state of the
643 item. This feature only affects items with a status of "In transit" and does
644 not affect items that were in the following statuses at the time they were sent
655 * Any custom statuses
657 This change should help clear up confusing situations caused by the previous
658 "abort transit" behavior, such as items showing "Available" when they are actually
659 en route, and patrons' items mysteriously disappearing from their accounts and
660 showing "Available" at the item-owning library without evidence of check-in.
665 Copy Status "Is Available" Flag
666 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
668 A new boolean field is now available for copy statuses to indicate when copies
669 having a given status should be considered available. The field has 2 main
672 1. Checking out an "available" copy will no longer result in an override-able
673 "COPY_NOT_AVAILABLE" alert for staff. The copy will checkout without
676 2. "Available" copies will appear in catalog searches where "limit to
677 available" is selected as a search filter.
679 By default, the "Available" and "Reshelving" statuses have the "Is Available"
680 flag set. The flag may be applied to local/custom statuses via the copy
681 status admin interface.
687 Email Checkout Receipts
688 ^^^^^^^^^^^^^^^^^^^^^^^
689 This feature allows patrons to receive checkout receipts through email
690 at the circulation desk in the web client and in the Evergreen self-checkout
691 interface. Patrons need to opt in to receive
692 email receipts by default and must have an email address associated with their
693 account. Opt in can be staff mediated at the time of account creation or in
694 existing accounts. Patrons can also opt in directly in their OPAC account or
695 through patron self-registration. This feature does not affect the behavior of
696 checkouts from the XUL client or SIP2 devices.
698 Patrons can opt in to receive email checkout receipts by default via
699 a new _Email checkout receipts by default_ patron setting.
701 This feature also enhances the patron staging tables so that patron
702 settings can be chosen during self-registration.
704 The web staff interface's checkout screen now includes a "Quick
705 Receipt" button that allows staff members to generate a receipt
711 Set Per-OU Limits on Allowed Payment Amounts
712 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
713 Two new settings have been added to prevent clerks from accidentally clearing
714 all patron bills by scanning a barcode into the Payment Amount field, or
715 accidentally entering the amount without a decimal point (such as you
716 would when using a cash register).
718 Both settings are available via the Library Settings Editor. The _Payment
719 amount threshold for Are You Sure? dialog_ (ui.circ.billing.amount_warn)
720 setting identifies the amount above
721 which staff will be asked if they're sure they want to apply the payment.
722 The _Maximum payment amount allowed_ (ui.circ.billing.amount_limit)
723 setting identifies the maximum amount of
724 money that can be accepted through the staff client.
726 These settings only affect the staff client, not credit
727 cards accepted through the OPAC, or direct API calls
728 from third party tools.
738 Additional Fields Available for Display in Some Interfaces
739 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
740 The holds age protection field will now be available for display in the
741 following interfaces:
743 * Item status list view column picker
744 * Item status alternate view
745 * Holdings maintenance column picker
747 The asset.copy.cost field, which records the amount paid for an item when
748 an invoice is processed, will be available for display in the following
751 * Items status list view column picker
752 * Item status alternate view
764 Merge Notification Preferences Tables in TPAC
765 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
766 The patron notification preference page in the public catalog
767 used to have two tables, separating notification settings
768 based on their source. Since that distinction does not matter
769 to patrons, and since the two tables aren't styled consistently,
770 they are merged together.
775 Improved Holds Screens in My Account
776 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
777 The grids in the My Account _Items on Hold_ and _Holds History_ interfaces are
778 simplified. Data previously contained in their own Activate, Active, and Date
779 Fulfilled columns are now incorporated into the Status column. To further
780 declutter the interface, the holds queue position will only show when the user
781 most needs the information - before the hold has been captured.
783 Distinct CSS classes have also been added for each hold status and each date
784 that could potentially display in these holds interfaces. A new default style
785 highlights the _Available_ status in green and the _Suspended_ status
793 Popularity Boost for Ranking Search Results
794 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
796 This feature uses factors such as circulation and hold activity, record and item age, and item ownership counts to generate popularity badges for bibliographic
797 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.
799 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.
801 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.
803 Finally, there will continue to be a pure _Relevance_ sort option, which is the version that exists today.
805 Administrators can comment out one of the available sort methods by editing the
806 filtersort.tt2 file.A global flag will allow Evergreen sites to select a default sort method.
811 Administrative interfaces to configure badges are only available in the web
812 client. Administrators can also configure badges directly via the database.
814 Available Popularity Parameters available for badges include:
816 * Holds Filled Over Time
817 * Holds Requested Over Time
819 * Circulations Over Time
820 * Current Circulation Count
823 * Holds/Holdable Ratio
824 * Percent of Time Circulating
825 * Bibliographic Record Age (days)
826 * Publication Age (days)
827 * Available On-Line (for e-books, etc)
830 Badges can be configured to apply to a targeted group of bibliographic records
831 based on the following available filters:
834 * Bibliographic source
835 * Circulation modifier
836 * Copy location group
838 Badges can also be be restricted to materials owned by a specific organizational
841 This new feature comes with a starter badge based on the top 97th percentile of
842 holds requested over the past five years.
847 Ratings for records will be displayed in the catalog in the following ways:
849 * On the record result page, the overall average popularity rating is displayed with a label of _Popularity_.
851 * On the record detail page, each individual badge earned by the record is
852 displayed with its rating.
856 * **OPAC Default Sort (opac.default_sort)**: Identifies the default sort method
857 to be used in the catalog.
859 * **Maximum popularity importance multiplier for popularity-adjusted relevance
860 searches (search.max_popularity_importance_multiplier):** A multiplier identifying
861 the importance of popularity in the Popularity-Adjusted Relevance ranked
862 searches. The number should be a decimal ranging between 1.0 and 2.0. The
863 default value is 1.1.
865 More detailed information is available in the TechRef docs directory of the
866 Evergreen source code.
871 Removal of Advanced Hold Options link when part holds are expected
872 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
873 If a user attempts to place a metarecord hold when all eligible copies
874 contain parts, the hold will fail. To help prevent the user from reaching
875 a dead end while placing holds, the *Advanced Hold Options* link is removed
876 from the Place Hold page in cases where all copies on the record contain
877 parts. The *Advanced Hold Options* link will remain for records that have
878 a mix of parted and non-parted copies.
891 Renewals attempted via SIP will now consider whether a penalty is configured
892 to block renewals before blocking the renewal. Previously, any penalty, even
893 if it wasn't set to block renewals, would prevent a renewal from succeeding
900 Treat SIP Location Field as Login Workstation
901 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
902 When using a version of SIPServer that supports the feature,
903 the Location (CP) field of the Login (93) message will be
904 used as the workstation name if supplied. Blank or missing
905 location fields will be ignored. This allows users or reports
906 to determine which selfcheck performed a circulation.
919 Translations in this release have been significantly increased. In
920 particular, Spanish has received a huge update with over 9,000 new
921 translations, Czech has received a sizable update of over 800
922 translations, and additional smaller updates have been added for
923 Arabic, French (Canada), and Armenian.
927 2.11.0 Acknowledgments
928 ----------------------
929 The Evergreen project would like to acknowledge the following
930 organizations that commissioned developments in this release of
934 * Georgia Public Library Service
936 * Pennsylvania Integrated Library System
937 * Pioneer Library System
939 We would also like to thank the following individuals who contributed
940 code, management, translations, documentation patches and tests to this
941 release of Evergreen:
961 We also thank the following organizations whose employees contributed
965 * Central/Wester Massachusetts Automated Resource Sharing
966 * Equinox Software, Inc.
967 * Emerald Data Networks, Inc.
969 * Georgia Public Library Service
970 * King County Library System
972 * Laurentian University
975 * North of Boston Library Exchange
976 * Traverse Area District Library
978 We regret any omissions. If a contributor has been inadvertently
979 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / Evergreen.git / blob