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.4.
11 Security Issue: XSS Vulnerability in Public Catalog
12 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
13 This release fixes several cross-site scripting (XSS) vulnerabilities
14 in the public catalog. When upgrading, Evergreen administrators should
15 review whether any of the following templates have been customized
16 or overridden. If so, either the template should be replaced with the
17 stock version or the XSS fix (which entails adding the `| html` filter
18 in several places) applied to the customized version.
20 * `Open-ILS/src/templates/opac/parts/locale_picker.tt2`
21 * `Open-ILS/src/templates/opac/parts/login/form.tt2`
22 * `Open-ILS/src/templates/opac/parts/searchbar.tt2`
26 * A fix to remove the Chilifresh patron reviews header for Evergreen sites
27 that do not use Chilifresh.
28 * A fix that marks acquisitions POs as received when all line items on the
29 PO are received or canceled.
30 * A typo fix to the long overdue override permission that prevented staff
31 from being able to override long overdue check ins.
32 * A fix to use a library's configured currency in SIP patron responses
33 instead of always using US dollars.
34 * A fix to SIP timeouts caused by invalid sessions
35 * A fix that allows boolean fields to be recognized in queries to the
37 * A fix to use the correct method during adjust to zero on negative
39 * A correction to the datatype for the Vandelay Default Record Match Set
41 * The removal of the _Keep_ field from MARC Batch Import Item Attributes.
42 The field was not previously implemented.
43 * A fix to set the complete time value for grouped Action/Trigger events
44 when an event's state reach complete, consistent with non-grouped events.
45 * A fix to a bug in the rollover_phone_to_print.pl script that kept failed
46 call files from being moved.
47 * A new index for acq.edi_message that speeds up the check for duplicate
49 * A fix that ensures JSON strings are converted to UTF8, ensuring that
50 non-ASCII data display correctly.
51 * A fix to avoid an erroneous unsaved data popup to appear during MARC
56 We would like to thank the following individuals who contributed code,
57 testing and documentation patches to the 2.11.5 point release of
81 This release contains several bug fixes improving on Evergreen 2.11.3.
83 * A fix to avoid fetching and creating EDI message entries that the
85 * A fix to prevent staff users from marking a long overdue item as lost
86 so that the patron will not be billed twice for the same item.
87 * A fix to the link that is used on the catalog's Library Info page so
88 that links with anchors can be successfully retrieved.
89 * A replacement for the blank fallback image used when the catalog cannot
90 retrieve an added content book cover.
91 * An EDI fix that prevents EDI fetcher from crashing when the vendor
92 supplies a zero-length file.
93 * A fix to an issue where adjusting a bill to zero for a current checkout
94 prematurely closes the transaction.
95 * A fix to encoding problems in MODS output. These problems caused issues
96 when using Zotero with records in the catalog.
97 * A fix to Evergreen self-check to accept the user name value when a barcode
98 regex has been configured for the system.
99 * A fix to duplicate name checking in the patron registration screen so that
100 clicking the "Found x patron(s) with same name" link will retrieve potential
101 duplicate inactive patrons.
102 * A fix to the bower install step used when installing the web staff client.
103 * A fix that marks a hold as fulfilled when staff check out a hold-
104 captured item for a hold whose expire time is in the past.
105 * A change to the acquisitions funding source funds drop down menu so that
106 the menu will now only display active funds and will also display the
107 year alongside the fund.
108 * A fix to a problem where the Current Bills tab of the patron record
109 showed duplicate charges when a check in was done from the Items Out tab.
110 * 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.
111 * A change to the fund year selectors in acq interfaces so that the years
112 are sorted in descending order.
113 * A fix to a billing issue where transactions were not re-opened after
114 they acquired a non-zero balance at check in.
115 * A change to the default pickup library when staff place a hold. The place hold
116 screen will now default to the preferred pickup location for the patron. If the
117 patron does not have a preferred pickup location, it will default to the
118 patron's home library.
119 * The ability to skip the XUL staff client build when in make_release.
120 * A fix that silences a log warning that appears for every checkout where a hard
121 due date is not used.
125 We would like to thank the following individuals who contributed code,
126 testing and documentation patches to the 2.11.4 point release of
153 This is a security release that also contains several other bugfixes improving
154 on Evergreen 2.11.2. All users of Evergreen 2.11.x are recommended to upgrade
155 to 2.11.3 as soon as possible.
157 Security Issue: Credit Processor Stripe Settings Permissions
158 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
159 Unprivileged users can retrieve organizational unit setting values for
160 setting types lacking a "view" permission. When the feature adding
161 Stripe credit card processing was added, the upgrade script neglected
162 to add the VIEW_CREDIT_CARD_PROCESSING permission to the
163 organizational unit setting type. This means that anyone can retrieve
164 and view the settings for Stripe credit card processing.
166 Any system that upgraded from Evergreen version 2.5 to 2.6 is
167 affected. If you use Stripe for credit card processing, it is
168 strongly recommended that you apply this upgrade. Even if you do not
169 use Stripe, applying this upgrade is still recommended. If you did
170 not upgrade from version 2.5 to 2.6 of Evergreen, but started with a
171 later version, applying this upgrade is harmless.
173 If you are not ready to perform a full upgrade, and if you use Stripe,
174 you can protect the settings by running the following two SQL statements:
178 UPDATE config.org_unit_setting_type
179 SET view_perm = (SELECT id FROM permission.perm_list
180 WHERE code = 'VIEW_CREDIT_CARD_PROCESSING' LIMIT 1)
181 WHERE name LIKE 'credit.processor.stripe%' AND view_perm IS NULL;
183 UPDATE config.org_unit_setting_type
184 SET update_perm = (SELECT id FROM permission.perm_list
185 WHERE code = 'ADMIN_CREDIT_CARD_PROCESSING' LIMIT 1)
186 WHERE name LIKE 'credit.processor.stripe%' AND update_perm IS NULL;
189 Missing Upgrade Script Notice
190 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
191 It was recently discovered that the 2.11.2 tarball was missing the
192 upgrade script for 2.11.1. If you upgraded straight to 2.11.2 from
193 2.11.0 or prior, please make sure to apply the
194 2.11.0-2.11.1-upgrade-db.sql before moving on to the 2.11.3 script.
198 Evergreen 2.11.3 also contains the following bugfixes:
200 * A fix to correctly apply floating group settings when performing
202 * An improvement to the speed of looking up patrons by their username;
203 this is particularly important for large databases.
204 * A fix to properly display the contents of temporary lists ('My List') in the
205 public catalog, as well as a fix of the HTML coding of that page.
206 * A fix to the Spanish translation of the public catalog that could
207 cause catalog searches to fail.
208 * A fix of a problem where certain kinds of requests of information
209 about the organizational unit hierarchy to consume all available
210 `open-ils.cstore` backends.
211 * A fix to allow staff to use the 'place another hold' link without
212 running into a user interface loop.
213 * A fix to the 'Edit Due Date' form in the web staff client.
214 * A fix to the definition of the stock 'Full Overlay' merge profile.
215 * A fix to sort billing types in alphabetical order in the web staff
217 * A fix to the display of the popularity score in the public catalog.
218 * A fix to the 'return to grouped search results' link in the public
220 * A fix to allow pre-cat checkouts in the web staff client without requiring
221 a circulation modifier.
222 * A fix to how Action/Trigger event definitions with nullable grouping
223 fields handle null values.
224 * Other typo and documentation fixes.
228 We would like to thank the following individuals who contributed code,
229 testing and documentation patches to the 2.11.3 point release of
252 This release contains several bugfixes improving on Evergreen 2.11.1
254 * A fix to the web client patron interface that changed the holds count in the
255 patron summary from total / available to available / total.
256 * A fix to an issue where the Closed Dates Editor was displaying an extra day of
258 * A fix to the Closed Dates Editor so that it now displays "All Day" when the
259 library is closed for the entire day.
260 * A fix to properly format LC Call numbers in spine label printing.
261 * A fix to a bug that was causing intermittent search failures.
262 * A fix to a bug that was causing search failures for Copy Location Group
264 * A fix to significant increased slowness with holds transfers.
265 * The addition of an index to the action.aged_circulation table to resolve a
266 problem with long-running queries.
267 * A fix to redirects that for one-hit metarecord searches for systems that
268 have enabled the setting to immediately jump to a bib record on one-hit searches.
269 * A fix to the new acquisitions cost field available in the copy editor to
270 resolve an issue where accidentally clearing out the value in the field resulted
272 * A fix to a bug that broke the Alternate Printable Hold Pull List and Vandelay
273 uploads on systems that were running OpenSRF 2.5.
277 We would like to thank the following individuals who contributed code,
278 testing and documentation patches to the 2.11.1 point release of
297 This release contains several bug fixes improving on Evergreen 2.11.0
299 * A fix to that provides alphabetical sorting to the fund selector in
300 the Acquisitions Selection List -> Copies interface.
301 * A fix to the web client check in screen allowing users to click the
302 title of the checked-in item to retrieve the bib record for that item.
303 * The addition of a progress bar that displays when conducting a patron searchin the web client.
304 * A fix to the web client patron interface so that total Items Out in the
305 patron summary now includes overdue and long overdue items. It will also
306 include Lost and Claims Returned items when the appropriate library
308 * A change to the public catalog My Account screen where the font for
309 leading articles will now be smaller when sorting a list by title.
310 * A fix to subject links in the catalog's record summary page so that
311 periods are no longer stripped from resulting subject searches, leading
312 to more accurate results when those links are clicked.
313 * A fix to avoid unint warnings in the logs for prox_cache in
314 open-ils.circ.hold.is_possible.
315 * A fix to rounding errors that occurred when summing owed/paid totals
316 for display in the catalog's credit card payment form.
317 * A change to sort behavior in the My Account screens. Previously, a
318 third click on a column header returned the list to its original sort
319 order. Clicking column headers will now simply toggle the sort
320 between ascending and descending order.
321 * The Permalink option on the catalog's record summary page will now be
322 hidden in the staff client because clicking the link in the client led
323 to no discernible change for users.
324 * A fix to the display of permanent lists in the catalog, which had broken
326 * A fix to the text of a notice that displays when migrating circulation
327 history during the upgrade to 2.10.
328 * An improvement to the performance for the lookup of a user's circ
329 history by adding an index on action.usr_circ_history(usr).
330 * A fix so that when a bib record's fingerprint changes, it gets correctly
331 moved to a different metarecord.
335 We would like to thank the following individuals who contributed code,
336 tests and documentation patches to the 2.11.1 point release of
355 Tablefunc Extension No Longer Required
356 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
357 Changes in the behavior of the connectby function in PostgreSQL 9.5
358 have prompted its removal from the database. It is easier for
359 Evergreen to maintain compatibility with previous versions of
360 PostgreSQL without this function.
362 By eliminating the use of the connectby function, we eliminate the
363 requirement for the tablefunc database extension. It is no longer
364 installed when the database is created. If you are upgrading and wish
365 to remove it from your database, you may run the following statement
366 in the database to drop it:
368 DROP EXTENSION tablefunc;
384 Add Date Header to Action Trigger Email/SMS Templates
385 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
386 The Date: header specified in RFC 2822 has been added to the seed data
387 for the example Action Trigger email and SMS templates, but no attempt
388 has been made to automatically modify existing templates. To add this
389 header (and end any "Why are my library emails from 1969/70?" questions
390 you may have heard) make sure the following lines are in all templates
391 that use the SendEmail or SendSMS reactors:
393 The first is already in most sample templates, but you may need to add
394 it to the top of any custom templates:
397 And this line should be inserted into the header block of each template:
398 `Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]`
404 Support for Ubuntu 16.04
405 ^^^^^^^^^^^^^^^^^^^^^^^^
406 Adds support for Ubuntu Xenial Xerus (16.04).
415 User activity types are now set to transient by default for new
416 Evergreen installs.. This means only the most recent activity entry per
417 user per activity type is retained in the database.
419 This change does not affect existing activity types, which were set to
420 non-transient by default. To make an activity type transient, modify the
421 'Transient' field of the desired type in the staff client under Admin ->
422 Server Administration -> User Activity Types.
424 Setting an activity type to transient means data for a given user will
425 be cleaned up automatically if and when the user performs the activity
426 in question. However, administrators can also force an activity
427 cleanup via SQL. This is useful for ensuring that all old activity
428 data is deleted and for controlling when the cleanup occurs, which
429 may be useful on very large actor.usr_activity tables.
431 To force clean all activity types:
434 ------------------------------------------------------------
435 SELECT actor.purge_usr_activity_by_type(etype.id)
436 FROM config.usr_activity_type etype;
437 ------------------------------------------------------------
439 NOTE: This could take hours to run on a very large actor.usr_activity table.
450 Authority Record Import Updates Editor, Edit Date.
451 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
452 Importing an authority record via MARC Batch Import/Export now causes the
453 authority record's editor and edit_date fields to be updated. The editor
454 value may come from the MARC 905u field or, if none is present, the user
455 performing the import.
460 Authority Propagation Updates Bib Editor / Edit Date
461 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
462 When a bib record is automatically updated as a result of the
463 modification of a linked authority record, the bib record's "Last Edit
464 Date/Time" and "Last Editing User" fields will be updated to match the
465 time of the update and the editor of the modified authority record.
467 A new global flag is available to control this behavior called
468 'ingest.disable_authority_auto_update_bib_meta' ("Authority Automation:
469 Disable automatic authority updates from modifying bib record editor
470 and edit_date"). When enabled, theses fields will not be updated. By
471 default, this setting is disabled.
473 An additional speed improvement is included in this feature. No attempt
474 will be made to update linked bib records when the normalized heading of
475 the modified authority record is unchanged by the authority record update.
480 Bibliographic Record Source Now Copied to 901$s
481 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
482 If a bibliographic record has a source set, the name of that source
483 is now copied to the 901$s whenever the record is created or updated.
484 This allows the source to be used for record matching and MARC
490 Option to Update Bib Source and Edit Details on Record Import
491 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
492 When importing records through the client, users will now have the ability to
493 define whether the bib source, last editor, and last edit date should be updated
494 on a record merge/overlay.
496 In MARC Batch Import / Export, select the _Merge / Overlay_ tab. Each entry in
497 the table has a value in the new _Update bib. source_ column. If that value is
498 True, then the bib source, last editor, and last edit date will be updated.
500 The two system-defined entries have been pre-set to appropriate values (Full
501 Overlay = true; Match-Only Merge = false).
511 Staff Client Honors Aged Circulations
512 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
514 The browser and XUL clients now better represent copy checkout history
515 by honoring and displaying information from aged circulations.
517 * Browser client 'Recent Circ History' and the analogous XUL client
518 'Circulation History' tabs show summary data for aged circulations
519 as well as regular/active circulations. When aged circulation data
520 is displayed, any references to patron names are replaced by the string
521 "<Aged Circulation>".
523 * Browser client 'Circ History List' and the analogous XUL client
524 'Last Few Circulations' tabs behave as above, plus their 'Add
525 Billing' buttons are disabled when displaying aged circulation data.
527 * XUL client 'Retrieve Last Patron' actions from various UI's report,
528 "Item XXX circulation is an aged circulation and has no linked user".
529 Browser client analog uses 'Circ History List' instead; no additional
536 "Canceled Transit" Item Status
537 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
539 Previously, when a transit was aborted, the transited item would either go into
540 "Reshelving" status or would return to whatever status it was in when it went
541 into transit, even when the item itself was in a different status (including
542 "Checked out"). Now, for most transits that get aborted, the item is put into a
543 new status, "Canceled Transit", which signals to staff the actual state of the
544 item. This feature only affects items with a status of "In transit" and does
545 not affect items that were in the following statuses at the time they were sent
556 * Any custom statuses
558 This change should help clear up confusing situations caused by the previous
559 "abort transit" behavior, such as items showing "Available" when they are actually
560 en route, and patrons' items mysteriously disappearing from their accounts and
561 showing "Available" at the item-owning library without evidence of check-in.
566 Copy Status "Is Available" Flag
567 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
569 A new boolean field is now available for copy statuses to indicate when copies
570 having a given status should be considered available. The field has 2 main
573 1. Checking out an "available" copy will no longer result in an override-able
574 "COPY_NOT_AVAILABLE" alert for staff. The copy will checkout without
577 2. "Available" copies will appear in catalog searches where "limit to
578 available" is selected as a search filter.
580 By default, the "Available" and "Reshelving" statuses have the "Is Available"
581 flag set. The flag may be applied to local/custom statuses via the copy
582 status admin interface.
588 Email Checkout Receipts
589 ^^^^^^^^^^^^^^^^^^^^^^^
590 This feature allows patrons to receive checkout receipts through email
591 at the circulation desk in the web client and in the Evergreen self-checkout
592 interface. Patrons need to opt in to receive
593 email receipts by default and must have an email address associated with their
594 account. Opt in can be staff mediated at the time of account creation or in
595 existing accounts. Patrons can also opt in directly in their OPAC account or
596 through patron self-registration. This feature does not affect the behavior of
597 checkouts from the XUL client or SIP2 devices.
599 Patrons can opt in to receive email checkout receipts by default via
600 a new _Email checkout receipts by default_ patron setting.
602 This feature also enhances the patron staging tables so that patron
603 settings can be chosen during self-registration.
605 The web staff interface's checkout screen now includes a "Quick
606 Receipt" button that allows staff members to generate a receipt
612 Set Per-OU Limits on Allowed Payment Amounts
613 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
614 Two new settings have been added to prevent clerks from accidentally clearing
615 all patron bills by scanning a barcode into the Payment Amount field, or
616 accidentally entering the amount without a decimal point (such as you
617 would when using a cash register).
619 Both settings are available via the Library Settings Editor. The _Payment
620 amount threshold for Are You Sure? dialog_ (ui.circ.billing.amount_warn)
621 setting identifies the amount above
622 which staff will be asked if they're sure they want to apply the payment.
623 The _Maximum payment amount allowed_ (ui.circ.billing.amount_limit)
624 setting identifies the maximum amount of
625 money that can be accepted through the staff client.
627 These settings only affect the staff client, not credit
628 cards accepted through the OPAC, or direct API calls
629 from third party tools.
639 Additional Fields Available for Display in Some Interfaces
640 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
641 The holds age protection field will now be available for display in the
642 following interfaces:
644 * Item status list view column picker
645 * Item status alternate view
646 * Holdings maintenance column picker
648 The asset.copy.cost field, which records the amount paid for an item when
649 an invoice is processed, will be available for display in the following
652 * Items status list view column picker
653 * Item status alternate view
665 Merge Notification Preferences Tables in TPAC
666 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
667 The patron notification preference page in the public catalog
668 used to have two tables, separating notification settings
669 based on their source. Since that distinction does not matter
670 to patrons, and since the two tables aren't styled consistently,
671 they are merged together.
676 Improved Holds Screens in My Account
677 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
678 The grids in the My Account _Items on Hold_ and _Holds History_ interfaces are
679 simplified. Data previously contained in their own Activate, Active, and Date
680 Fulfilled columns are now incorporated into the Status column. To further
681 declutter the interface, the holds queue position will only show when the user
682 most needs the information - before the hold has been captured.
684 Distinct CSS classes have also been added for each hold status and each date
685 that could potentially display in these holds interfaces. A new default style
686 highlights the _Available_ status in green and the _Suspended_ status
694 Popularity Boost for Ranking Search Results
695 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
697 This feature uses factors such as circulation and hold activity, record and item age, and item ownership counts to generate popularity badges for bibliographic
698 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.
700 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.
702 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.
704 Finally, there will continue to be a pure _Relevance_ sort option, which is the version that exists today.
706 Administrators can comment out one of the available sort methods by editing the
707 filtersort.tt2 file.A global flag will allow Evergreen sites to select a default sort method.
712 Administrative interfaces to configure badges are only available in the web
713 client. Administrators can also configure badges directly via the database.
715 Available Popularity Parameters available for badges include:
717 * Holds Filled Over Time
718 * Holds Requested Over Time
720 * Circulations Over Time
721 * Current Circulation Count
724 * Holds/Holdable Ratio
725 * Percent of Time Circulating
726 * Bibliographic Record Age (days)
727 * Publication Age (days)
728 * Available On-Line (for e-books, etc)
731 Badges can be configured to apply to a targeted group of bibliographic records
732 based on the following available filters:
735 * Bibliographic source
736 * Circulation modifier
737 * Copy location group
739 Badges can also be be restricted to materials owned by a specific organizational
742 This new feature comes with a starter badge based on the top 97th percentile of
743 holds requested over the past five years.
748 Ratings for records will be displayed in the catalog in the following ways:
750 * On the record result page, the overall average popularity rating is displayed with a label of _Popularity_.
752 * On the record detail page, each individual badge earned by the record is
753 displayed with its rating.
757 * **OPAC Default Sort (opac.default_sort)**: Identifies the default sort method
758 to be used in the catalog.
760 * **Maximum popularity importance multiplier for popularity-adjusted relevance
761 searches (search.max_popularity_importance_multiplier):** A multiplier identifying
762 the importance of popularity in the Popularity-Adjusted Relevance ranked
763 searches. The number should be a decimal ranging between 1.0 and 2.0. The
764 default value is 1.1.
766 More detailed information is available in the TechRef docs directory of the
767 Evergreen source code.
772 Removal of Advanced Hold Options link when part holds are expected
773 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
774 If a user attempts to place a metarecord hold when all eligible copies
775 contain parts, the hold will fail. To help prevent the user from reaching
776 a dead end while placing holds, the *Advanced Hold Options* link is removed
777 from the Place Hold page in cases where all copies on the record contain
778 parts. The *Advanced Hold Options* link will remain for records that have
779 a mix of parted and non-parted copies.
792 Renewals attempted via SIP will now consider whether a penalty is configured
793 to block renewals before blocking the renewal. Previously, any penalty, even
794 if it wasn't set to block renewals, would prevent a renewal from succeeding
801 Treat SIP Location Field as Login Workstation
802 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
803 When using a version of SIPServer that supports the feature,
804 the Location (CP) field of the Login (93) message will be
805 used as the workstation name if supplied. Blank or missing
806 location fields will be ignored. This allows users or reports
807 to determine which selfcheck performed a circulation.
820 Translations in this release have been significantly increased. In
821 particular, Spanish has received a huge update with over 9,000 new
822 translations, Czech has received a sizable update of over 800
823 translations, and additional smaller updates have been added for
824 Arabic, French (Canada), and Armenian.
828 2.11.0 Acknowledgments
829 ----------------------
830 The Evergreen project would like to acknowledge the following
831 organizations that commissioned developments in this release of
835 * Georgia Public Library Service
837 * Pennsylvania Integrated Library System
838 * Pioneer Library System
840 We would also like to thank the following individuals who contributed
841 code, management, translations, documentation patches and tests to this
842 release of Evergreen:
862 We also thank the following organizations whose employees contributed
866 * Central/Wester Massachusetts Automated Resource Sharing
867 * Equinox Software, Inc.
868 * Emerald Data Networks, Inc.
870 * Georgia Public Library Service
871 * King County Library System
873 * Laurentian University
876 * North of Boston Library Exchange
877 * Traverse Area District Library
879 We regret any omissions. If a contributor has been inadvertently
880 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / working / Evergreen.git / blob