1 Evergreen 2.11 Release Notes
2 ============================
8 This release contains several bug fixes improving on Evergreen 2.11.5.
10 * Code to prevent a hold already on the Holds Shelf from being
11 transferred to another title.
12 * A fix to a bug that prevented users from scheduling reports with a
13 relative month if the report template used a date that applied the Year +
14 Month transform with the On or After (>=) operator.
15 * A fix to a bug where the max fines threshold was reached prematurely
16 due to the presence of account adjustments.
17 * A check that prevents a SMS message from sending if the SMS carrier
22 We would like to thank the following individuals who contributed code,
23 tests and documentation patches to the 2.11.6 point release of
35 This release is a security release that also contains several other bug
36 fixes improving on Evergreen 2.11.4.
38 Security Issue: XSS Vulnerability in Public Catalog
39 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
40 This release fixes several cross-site scripting (XSS) vulnerabilities
41 in the public catalog. When upgrading, Evergreen administrators should
42 review whether any of the following templates have been customized
43 or overridden. If so, either the template should be replaced with the
44 stock version or the XSS fix (which entails adding the `| html` filter
45 in several places) applied to the customized version.
47 * `Open-ILS/src/templates/opac/parts/locale_picker.tt2`
48 * `Open-ILS/src/templates/opac/parts/login/form.tt2`
49 * `Open-ILS/src/templates/opac/parts/searchbar.tt2`
53 * A fix to remove the Chilifresh patron reviews header for Evergreen sites
54 that do not use Chilifresh.
55 * A fix that marks acquisitions POs as received when all line items on the
56 PO are received or canceled.
57 * A typo fix to the long overdue override permission that prevented staff
58 from being able to override long overdue check ins.
59 * A fix to use a library's configured currency in SIP patron responses
60 instead of always using US dollars.
61 * A fix to SIP timeouts caused by invalid sessions
62 * A fix that allows boolean fields to be recognized in queries to the
64 * A fix to use the correct method during adjust to zero on negative
66 * A correction to the datatype for the Vandelay Default Record Match Set
68 * The removal of the _Keep_ field from MARC Batch Import Item Attributes.
69 The field was not previously implemented.
70 * A fix to set the complete time value for grouped Action/Trigger events
71 when an event's state reach complete, consistent with non-grouped events.
72 * A fix to a bug in the rollover_phone_to_print.pl script that kept failed
73 call files from being moved.
74 * A new index for acq.edi_message that speeds up the check for duplicate
76 * A fix that ensures JSON strings are converted to UTF8, ensuring that
77 non-ASCII data display correctly.
78 * A fix to avoid an erroneous unsaved data popup to appear during MARC
83 We would like to thank the following individuals who contributed code,
84 testing and documentation patches to the 2.11.5 point release of
108 This release contains several bug fixes improving on Evergreen 2.11.3.
110 * A fix to avoid fetching and creating EDI message entries that the
112 * A fix to prevent staff users from marking a long overdue item as lost
113 so that the patron will not be billed twice for the same item.
114 * A fix to the link that is used on the catalog's Library Info page so
115 that links with anchors can be successfully retrieved.
116 * A replacement for the blank fallback image used when the catalog cannot
117 retrieve an added content book cover.
118 * An EDI fix that prevents EDI fetcher from crashing when the vendor
119 supplies a zero-length file.
120 * A fix to an issue where adjusting a bill to zero for a current checkout
121 prematurely closes the transaction.
122 * A fix to encoding problems in MODS output. These problems caused issues
123 when using Zotero with records in the catalog.
124 * A fix to Evergreen self-check to accept the user name value when a barcode
125 regex has been configured for the system.
126 * A fix to duplicate name checking in the patron registration screen so that
127 clicking the "Found x patron(s) with same name" link will retrieve potential
128 duplicate inactive patrons.
129 * A fix to the bower install step used when installing the web staff client.
130 * A fix that marks a hold as fulfilled when staff check out a hold-
131 captured item for a hold whose expire time is in the past.
132 * A change to the acquisitions funding source funds drop down menu so that
133 the menu will now only display active funds and will also display the
134 year alongside the fund.
135 * A fix to a problem where the Current Bills tab of the patron record
136 showed duplicate charges when a check in was done from the Items Out tab.
137 * 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.
138 * A change to the fund year selectors in acq interfaces so that the years
139 are sorted in descending order.
140 * A fix to a billing issue where transactions were not re-opened after
141 they acquired a non-zero balance at check in.
142 * A change to the default pickup library when staff place a hold. The place hold
143 screen will now default to the preferred pickup location for the patron. If the
144 patron does not have a preferred pickup location, it will default to the
145 patron's home library.
146 * The ability to skip the XUL staff client build when in make_release.
147 * A fix that silences a log warning that appears for every checkout where a hard
148 due date is not used.
152 We would like to thank the following individuals who contributed code,
153 testing and documentation patches to the 2.11.4 point release of
180 This is a security release that also contains several other bugfixes improving
181 on Evergreen 2.11.2. All users of Evergreen 2.11.x are recommended to upgrade
182 to 2.11.3 as soon as possible.
184 Security Issue: Credit Processor Stripe Settings Permissions
185 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
186 Unprivileged users can retrieve organizational unit setting values for
187 setting types lacking a "view" permission. When the feature adding
188 Stripe credit card processing was added, the upgrade script neglected
189 to add the VIEW_CREDIT_CARD_PROCESSING permission to the
190 organizational unit setting type. This means that anyone can retrieve
191 and view the settings for Stripe credit card processing.
193 Any system that upgraded from Evergreen version 2.5 to 2.6 is
194 affected. If you use Stripe for credit card processing, it is
195 strongly recommended that you apply this upgrade. Even if you do not
196 use Stripe, applying this upgrade is still recommended. If you did
197 not upgrade from version 2.5 to 2.6 of Evergreen, but started with a
198 later version, applying this upgrade is harmless.
200 If you are not ready to perform a full upgrade, and if you use Stripe,
201 you can protect the settings by running the following two SQL statements:
205 UPDATE config.org_unit_setting_type
206 SET view_perm = (SELECT id FROM permission.perm_list
207 WHERE code = 'VIEW_CREDIT_CARD_PROCESSING' LIMIT 1)
208 WHERE name LIKE 'credit.processor.stripe%' AND view_perm IS NULL;
210 UPDATE config.org_unit_setting_type
211 SET update_perm = (SELECT id FROM permission.perm_list
212 WHERE code = 'ADMIN_CREDIT_CARD_PROCESSING' LIMIT 1)
213 WHERE name LIKE 'credit.processor.stripe%' AND update_perm IS NULL;
216 Missing Upgrade Script Notice
217 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
218 It was recently discovered that the 2.11.2 tarball was missing the
219 upgrade script for 2.11.1. If you upgraded straight to 2.11.2 from
220 2.11.0 or prior, please make sure to apply the
221 2.11.0-2.11.1-upgrade-db.sql before moving on to the 2.11.3 script.
225 Evergreen 2.11.3 also contains the following bugfixes:
227 * A fix to correctly apply floating group settings when performing
229 * An improvement to the speed of looking up patrons by their username;
230 this is particularly important for large databases.
231 * A fix to properly display the contents of temporary lists ('My List') in the
232 public catalog, as well as a fix of the HTML coding of that page.
233 * A fix to the Spanish translation of the public catalog that could
234 cause catalog searches to fail.
235 * A fix of a problem where certain kinds of requests of information
236 about the organizational unit hierarchy to consume all available
237 `open-ils.cstore` backends.
238 * A fix to allow staff to use the 'place another hold' link without
239 running into a user interface loop.
240 * A fix to the 'Edit Due Date' form in the web staff client.
241 * A fix to the definition of the stock 'Full Overlay' merge profile.
242 * A fix to sort billing types in alphabetical order in the web staff
244 * A fix to the display of the popularity score in the public catalog.
245 * A fix to the 'return to grouped search results' link in the public
247 * A fix to allow pre-cat checkouts in the web staff client without requiring
248 a circulation modifier.
249 * A fix to how Action/Trigger event definitions with nullable grouping
250 fields handle null values.
251 * Other typo and documentation fixes.
255 We would like to thank the following individuals who contributed code,
256 testing and documentation patches to the 2.11.3 point release of
279 This release contains several bugfixes improving on Evergreen 2.11.1
281 * A fix to the web client patron interface that changed the holds count in the
282 patron summary from total / available to available / total.
283 * A fix to an issue where the Closed Dates Editor was displaying an extra day of
285 * A fix to the Closed Dates Editor so that it now displays "All Day" when the
286 library is closed for the entire day.
287 * A fix to properly format LC Call numbers in spine label printing.
288 * A fix to a bug that was causing intermittent search failures.
289 * A fix to a bug that was causing search failures for Copy Location Group
291 * A fix to significant increased slowness with holds transfers.
292 * The addition of an index to the action.aged_circulation table to resolve a
293 problem with long-running queries.
294 * A fix to redirects that for one-hit metarecord searches for systems that
295 have enabled the setting to immediately jump to a bib record on one-hit searches.
296 * A fix to the new acquisitions cost field available in the copy editor to
297 resolve an issue where accidentally clearing out the value in the field resulted
299 * A fix to a bug that broke the Alternate Printable Hold Pull List and Vandelay
300 uploads on systems that were running OpenSRF 2.5.
304 We would like to thank the following individuals who contributed code,
305 testing and documentation patches to the 2.11.1 point release of
324 This release contains several bug fixes improving on Evergreen 2.11.0
326 * A fix to that provides alphabetical sorting to the fund selector in
327 the Acquisitions Selection List -> Copies interface.
328 * A fix to the web client check in screen allowing users to click the
329 title of the checked-in item to retrieve the bib record for that item.
330 * The addition of a progress bar that displays when conducting a patron searchin the web client.
331 * A fix to the web client patron interface so that total Items Out in the
332 patron summary now includes overdue and long overdue items. It will also
333 include Lost and Claims Returned items when the appropriate library
335 * A change to the public catalog My Account screen where the font for
336 leading articles will now be smaller when sorting a list by title.
337 * A fix to subject links in the catalog's record summary page so that
338 periods are no longer stripped from resulting subject searches, leading
339 to more accurate results when those links are clicked.
340 * A fix to avoid unint warnings in the logs for prox_cache in
341 open-ils.circ.hold.is_possible.
342 * A fix to rounding errors that occurred when summing owed/paid totals
343 for display in the catalog's credit card payment form.
344 * A change to sort behavior in the My Account screens. Previously, a
345 third click on a column header returned the list to its original sort
346 order. Clicking column headers will now simply toggle the sort
347 between ascending and descending order.
348 * The Permalink option on the catalog's record summary page will now be
349 hidden in the staff client because clicking the link in the client led
350 to no discernible change for users.
351 * A fix to the display of permanent lists in the catalog, which had broken
353 * A fix to the text of a notice that displays when migrating circulation
354 history during the upgrade to 2.10.
355 * An improvement to the performance for the lookup of a user's circ
356 history by adding an index on action.usr_circ_history(usr).
357 * A fix so that when a bib record's fingerprint changes, it gets correctly
358 moved to a different metarecord.
362 We would like to thank the following individuals who contributed code,
363 tests and documentation patches to the 2.11.1 point release of
382 Tablefunc Extension No Longer Required
383 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
384 Changes in the behavior of the connectby function in PostgreSQL 9.5
385 have prompted its removal from the database. It is easier for
386 Evergreen to maintain compatibility with previous versions of
387 PostgreSQL without this function.
389 By eliminating the use of the connectby function, we eliminate the
390 requirement for the tablefunc database extension. It is no longer
391 installed when the database is created. If you are upgrading and wish
392 to remove it from your database, you may run the following statement
393 in the database to drop it:
395 DROP EXTENSION tablefunc;
411 Add Date Header to Action Trigger Email/SMS Templates
412 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
413 The Date: header specified in RFC 2822 has been added to the seed data
414 for the example Action Trigger email and SMS templates, but no attempt
415 has been made to automatically modify existing templates. To add this
416 header (and end any "Why are my library emails from 1969/70?" questions
417 you may have heard) make sure the following lines are in all templates
418 that use the SendEmail or SendSMS reactors:
420 The first is already in most sample templates, but you may need to add
421 it to the top of any custom templates:
424 And this line should be inserted into the header block of each template:
425 `Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]`
431 Support for Ubuntu 16.04
432 ^^^^^^^^^^^^^^^^^^^^^^^^
433 Adds support for Ubuntu Xenial Xerus (16.04).
442 User activity types are now set to transient by default for new
443 Evergreen installs.. This means only the most recent activity entry per
444 user per activity type is retained in the database.
446 This change does not affect existing activity types, which were set to
447 non-transient by default. To make an activity type transient, modify the
448 'Transient' field of the desired type in the staff client under Admin ->
449 Server Administration -> User Activity Types.
451 Setting an activity type to transient means data for a given user will
452 be cleaned up automatically if and when the user performs the activity
453 in question. However, administrators can also force an activity
454 cleanup via SQL. This is useful for ensuring that all old activity
455 data is deleted and for controlling when the cleanup occurs, which
456 may be useful on very large actor.usr_activity tables.
458 To force clean all activity types:
461 ------------------------------------------------------------
462 SELECT actor.purge_usr_activity_by_type(etype.id)
463 FROM config.usr_activity_type etype;
464 ------------------------------------------------------------
466 NOTE: This could take hours to run on a very large actor.usr_activity table.
477 Authority Record Import Updates Editor, Edit Date.
478 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
479 Importing an authority record via MARC Batch Import/Export now causes the
480 authority record's editor and edit_date fields to be updated. The editor
481 value may come from the MARC 905u field or, if none is present, the user
482 performing the import.
487 Authority Propagation Updates Bib Editor / Edit Date
488 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
489 When a bib record is automatically updated as a result of the
490 modification of a linked authority record, the bib record's "Last Edit
491 Date/Time" and "Last Editing User" fields will be updated to match the
492 time of the update and the editor of the modified authority record.
494 A new global flag is available to control this behavior called
495 'ingest.disable_authority_auto_update_bib_meta' ("Authority Automation:
496 Disable automatic authority updates from modifying bib record editor
497 and edit_date"). When enabled, theses fields will not be updated. By
498 default, this setting is disabled.
500 An additional speed improvement is included in this feature. No attempt
501 will be made to update linked bib records when the normalized heading of
502 the modified authority record is unchanged by the authority record update.
507 Bibliographic Record Source Now Copied to 901$s
508 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
509 If a bibliographic record has a source set, the name of that source
510 is now copied to the 901$s whenever the record is created or updated.
511 This allows the source to be used for record matching and MARC
517 Option to Update Bib Source and Edit Details on Record Import
518 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
519 When importing records through the client, users will now have the ability to
520 define whether the bib source, last editor, and last edit date should be updated
521 on a record merge/overlay.
523 In MARC Batch Import / Export, select the _Merge / Overlay_ tab. Each entry in
524 the table has a value in the new _Update bib. source_ column. If that value is
525 True, then the bib source, last editor, and last edit date will be updated.
527 The two system-defined entries have been pre-set to appropriate values (Full
528 Overlay = true; Match-Only Merge = false).
538 Staff Client Honors Aged Circulations
539 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
541 The browser and XUL clients now better represent copy checkout history
542 by honoring and displaying information from aged circulations.
544 * Browser client 'Recent Circ History' and the analogous XUL client
545 'Circulation History' tabs show summary data for aged circulations
546 as well as regular/active circulations. When aged circulation data
547 is displayed, any references to patron names are replaced by the string
548 "<Aged Circulation>".
550 * Browser client 'Circ History List' and the analogous XUL client
551 'Last Few Circulations' tabs behave as above, plus their 'Add
552 Billing' buttons are disabled when displaying aged circulation data.
554 * XUL client 'Retrieve Last Patron' actions from various UI's report,
555 "Item XXX circulation is an aged circulation and has no linked user".
556 Browser client analog uses 'Circ History List' instead; no additional
563 "Canceled Transit" Item Status
564 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
566 Previously, when a transit was aborted, the transited item would either go into
567 "Reshelving" status or would return to whatever status it was in when it went
568 into transit, even when the item itself was in a different status (including
569 "Checked out"). Now, for most transits that get aborted, the item is put into a
570 new status, "Canceled Transit", which signals to staff the actual state of the
571 item. This feature only affects items with a status of "In transit" and does
572 not affect items that were in the following statuses at the time they were sent
583 * Any custom statuses
585 This change should help clear up confusing situations caused by the previous
586 "abort transit" behavior, such as items showing "Available" when they are actually
587 en route, and patrons' items mysteriously disappearing from their accounts and
588 showing "Available" at the item-owning library without evidence of check-in.
593 Copy Status "Is Available" Flag
594 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
596 A new boolean field is now available for copy statuses to indicate when copies
597 having a given status should be considered available. The field has 2 main
600 1. Checking out an "available" copy will no longer result in an override-able
601 "COPY_NOT_AVAILABLE" alert for staff. The copy will checkout without
604 2. "Available" copies will appear in catalog searches where "limit to
605 available" is selected as a search filter.
607 By default, the "Available" and "Reshelving" statuses have the "Is Available"
608 flag set. The flag may be applied to local/custom statuses via the copy
609 status admin interface.
615 Email Checkout Receipts
616 ^^^^^^^^^^^^^^^^^^^^^^^
617 This feature allows patrons to receive checkout receipts through email
618 at the circulation desk in the web client and in the Evergreen self-checkout
619 interface. Patrons need to opt in to receive
620 email receipts by default and must have an email address associated with their
621 account. Opt in can be staff mediated at the time of account creation or in
622 existing accounts. Patrons can also opt in directly in their OPAC account or
623 through patron self-registration. This feature does not affect the behavior of
624 checkouts from the XUL client or SIP2 devices.
626 Patrons can opt in to receive email checkout receipts by default via
627 a new _Email checkout receipts by default_ patron setting.
629 This feature also enhances the patron staging tables so that patron
630 settings can be chosen during self-registration.
632 The web staff interface's checkout screen now includes a "Quick
633 Receipt" button that allows staff members to generate a receipt
639 Set Per-OU Limits on Allowed Payment Amounts
640 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
641 Two new settings have been added to prevent clerks from accidentally clearing
642 all patron bills by scanning a barcode into the Payment Amount field, or
643 accidentally entering the amount without a decimal point (such as you
644 would when using a cash register).
646 Both settings are available via the Library Settings Editor. The _Payment
647 amount threshold for Are You Sure? dialog_ (ui.circ.billing.amount_warn)
648 setting identifies the amount above
649 which staff will be asked if they're sure they want to apply the payment.
650 The _Maximum payment amount allowed_ (ui.circ.billing.amount_limit)
651 setting identifies the maximum amount of
652 money that can be accepted through the staff client.
654 These settings only affect the staff client, not credit
655 cards accepted through the OPAC, or direct API calls
656 from third party tools.
666 Additional Fields Available for Display in Some Interfaces
667 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
668 The holds age protection field will now be available for display in the
669 following interfaces:
671 * Item status list view column picker
672 * Item status alternate view
673 * Holdings maintenance column picker
675 The asset.copy.cost field, which records the amount paid for an item when
676 an invoice is processed, will be available for display in the following
679 * Items status list view column picker
680 * Item status alternate view
692 Merge Notification Preferences Tables in TPAC
693 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
694 The patron notification preference page in the public catalog
695 used to have two tables, separating notification settings
696 based on their source. Since that distinction does not matter
697 to patrons, and since the two tables aren't styled consistently,
698 they are merged together.
703 Improved Holds Screens in My Account
704 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
705 The grids in the My Account _Items on Hold_ and _Holds History_ interfaces are
706 simplified. Data previously contained in their own Activate, Active, and Date
707 Fulfilled columns are now incorporated into the Status column. To further
708 declutter the interface, the holds queue position will only show when the user
709 most needs the information - before the hold has been captured.
711 Distinct CSS classes have also been added for each hold status and each date
712 that could potentially display in these holds interfaces. A new default style
713 highlights the _Available_ status in green and the _Suspended_ status
721 Popularity Boost for Ranking Search Results
722 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
724 This feature uses factors such as circulation and hold activity, record and item age, and item ownership counts to generate popularity badges for bibliographic
725 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.
727 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.
729 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.
731 Finally, there will continue to be a pure _Relevance_ sort option, which is the version that exists today.
733 Administrators can comment out one of the available sort methods by editing the
734 filtersort.tt2 file.A global flag will allow Evergreen sites to select a default sort method.
739 Administrative interfaces to configure badges are only available in the web
740 client. Administrators can also configure badges directly via the database.
742 Available Popularity Parameters available for badges include:
744 * Holds Filled Over Time
745 * Holds Requested Over Time
747 * Circulations Over Time
748 * Current Circulation Count
751 * Holds/Holdable Ratio
752 * Percent of Time Circulating
753 * Bibliographic Record Age (days)
754 * Publication Age (days)
755 * Available On-Line (for e-books, etc)
758 Badges can be configured to apply to a targeted group of bibliographic records
759 based on the following available filters:
762 * Bibliographic source
763 * Circulation modifier
764 * Copy location group
766 Badges can also be be restricted to materials owned by a specific organizational
769 This new feature comes with a starter badge based on the top 97th percentile of
770 holds requested over the past five years.
775 Ratings for records will be displayed in the catalog in the following ways:
777 * On the record result page, the overall average popularity rating is displayed with a label of _Popularity_.
779 * On the record detail page, each individual badge earned by the record is
780 displayed with its rating.
784 * **OPAC Default Sort (opac.default_sort)**: Identifies the default sort method
785 to be used in the catalog.
787 * **Maximum popularity importance multiplier for popularity-adjusted relevance
788 searches (search.max_popularity_importance_multiplier):** A multiplier identifying
789 the importance of popularity in the Popularity-Adjusted Relevance ranked
790 searches. The number should be a decimal ranging between 1.0 and 2.0. The
791 default value is 1.1.
793 More detailed information is available in the TechRef docs directory of the
794 Evergreen source code.
799 Removal of Advanced Hold Options link when part holds are expected
800 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
801 If a user attempts to place a metarecord hold when all eligible copies
802 contain parts, the hold will fail. To help prevent the user from reaching
803 a dead end while placing holds, the *Advanced Hold Options* link is removed
804 from the Place Hold page in cases where all copies on the record contain
805 parts. The *Advanced Hold Options* link will remain for records that have
806 a mix of parted and non-parted copies.
819 Renewals attempted via SIP will now consider whether a penalty is configured
820 to block renewals before blocking the renewal. Previously, any penalty, even
821 if it wasn't set to block renewals, would prevent a renewal from succeeding
828 Treat SIP Location Field as Login Workstation
829 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
830 When using a version of SIPServer that supports the feature,
831 the Location (CP) field of the Login (93) message will be
832 used as the workstation name if supplied. Blank or missing
833 location fields will be ignored. This allows users or reports
834 to determine which selfcheck performed a circulation.
847 Translations in this release have been significantly increased. In
848 particular, Spanish has received a huge update with over 9,000 new
849 translations, Czech has received a sizable update of over 800
850 translations, and additional smaller updates have been added for
851 Arabic, French (Canada), and Armenian.
855 2.11.0 Acknowledgments
856 ----------------------
857 The Evergreen project would like to acknowledge the following
858 organizations that commissioned developments in this release of
862 * Georgia Public Library Service
864 * Pennsylvania Integrated Library System
865 * Pioneer Library System
867 We would also like to thank the following individuals who contributed
868 code, management, translations, documentation patches and tests to this
869 release of Evergreen:
889 We also thank the following organizations whose employees contributed
893 * Central/Wester Massachusetts Automated Resource Sharing
894 * Equinox Software, Inc.
895 * Emerald Data Networks, Inc.
897 * Georgia Public Library Service
898 * King County Library System
900 * Laurentian University
903 * North of Boston Library Exchange
904 * Traverse Area District Library
906 We regret any omissions. If a contributor has been inadvertently
907 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / working / Evergreen.git / blob