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