1 Evergreen 2.11 Release Notes
2 ============================
9 This release contains several bug fixes improving on Evergreen 2.11.4.
11 * A fix to remove the Chilifresh patron reviews header for Evergreen sites
12 that do not use Chilifresh.
13 * A fix that marks acquisitions POs as received when all line items on the
14 PO are received or canceled.
15 * A typo fix to the long overdue override permission that prevented staff
16 from being able to override long overdue check ins.
17 * A fix to use a library's configured currency in SIP patron responses
18 instead of always using US dollars.
19 * A fix to SIP timeouts caused by invalid sessions
20 * A fix that allows boolean fields to be recognized in queries to the
22 * A fix to use the correct method during adjust to zero on negative
24 * A correction to the datatype for the Vandelay Default Record Match Set
26 * The removal of the _Keep_ field from MARC Batch Import Item Attributes.
27 The field was not previously implemented.
28 * A fix to set the complete time value for grouped Action/Trigger events
29 when an event's state reach complete, consistent with non-grouped events.
30 * A fix to a bug in the rollover_phone_to_print.pl script that kept failed
31 call files from being moved.
32 * A new index for acq.edi_message that speeds up the check for duplicate
34 * A fix that ensures JSON strings are converted to UTF8, ensuring that
35 non-ASCII data display correctly.
36 * A fix to avoid an erroneous unsaved data popup to appear during MARC
41 We would like to thank the following individuals who contributed code,
42 testing and documentation patches to the 2.11.5 point release of
66 This release contains several bug fixes improving on Evergreen 2.11.3.
68 * A fix to avoid fetching and creating EDI message entries that the
70 * A fix to prevent staff users from marking a long overdue item as lost
71 so that the patron will not be billed twice for the same item.
72 * A fix to the link that is used on the catalog's Library Info page so
73 that links with anchors can be successfully retrieved.
74 * A replacement for the blank fallback image used when the catalog cannot
75 retrieve an added content book cover.
76 * An EDI fix that prevents EDI fetcher from crashing when the vendor
77 supplies a zero-length file.
78 * A fix to an issue where adjusting a bill to zero for a current checkout
79 prematurely closes the transaction.
80 * A fix to encoding problems in MODS output. These problems caused issues
81 when using Zotero with records in the catalog.
82 * A fix to Evergreen self-check to accept the user name value when a barcode
83 regex has been configured for the system.
84 * A fix to duplicate name checking in the patron registration screen so that
85 clicking the "Found x patron(s) with same name" link will retrieve potential
86 duplicate inactive patrons.
87 * A fix to the bower install step used when installing the web staff client.
88 * A fix that marks a hold as fulfilled when staff check out a hold-
89 captured item for a hold whose expire time is in the past.
90 * A change to the acquisitions funding source funds drop down menu so that
91 the menu will now only display active funds and will also display the
92 year alongside the fund.
93 * A fix to a problem where the Current Bills tab of the patron record
94 showed duplicate charges when a check in was done from the Items Out tab.
95 * 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.
96 * A change to the fund year selectors in acq interfaces so that the years
97 are sorted in descending order.
98 * A fix to a billing issue where transactions were not re-opened after
99 they acquired a non-zero balance at check in.
100 * A change to the default pickup library when staff place a hold. The place hold
101 screen will now default to the preferred pickup location for the patron. If the
102 patron does not have a preferred pickup location, it will default to the
103 patron's home library.
104 * The ability to skip the XUL staff client build when in make_release.
105 * A fix that silences a log warning that appears for every checkout where a hard
106 due date is not used.
110 We would like to thank the following individuals who contributed code,
111 testing and documentation patches to the 2.11.4 point release of
138 This is a security release that also contains several other bugfixes improving
139 on Evergreen 2.11.2. All users of Evergreen 2.11.x are recommended to upgrade
140 to 2.11.3 as soon as possible.
142 Security Issue: Credit Processor Stripe Settings Permissions
143 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
144 Unprivileged users can retrieve organizational unit setting values for
145 setting types lacking a "view" permission. When the feature adding
146 Stripe credit card processing was added, the upgrade script neglected
147 to add the VIEW_CREDIT_CARD_PROCESSING permission to the
148 organizational unit setting type. This means that anyone can retrieve
149 and view the settings for Stripe credit card processing.
151 Any system that upgraded from Evergreen version 2.5 to 2.6 is
152 affected. If you use Stripe for credit card processing, it is
153 strongly recommended that you apply this upgrade. Even if you do not
154 use Stripe, applying this upgrade is still recommended. If you did
155 not upgrade from version 2.5 to 2.6 of Evergreen, but started with a
156 later version, applying this upgrade is harmless.
158 If you are not ready to perform a full upgrade, and if you use Stripe,
159 you can protect the settings by running the following two SQL statements:
163 UPDATE config.org_unit_setting_type
164 SET view_perm = (SELECT id FROM permission.perm_list
165 WHERE code = 'VIEW_CREDIT_CARD_PROCESSING' LIMIT 1)
166 WHERE name LIKE 'credit.processor.stripe%' AND view_perm IS NULL;
168 UPDATE config.org_unit_setting_type
169 SET update_perm = (SELECT id FROM permission.perm_list
170 WHERE code = 'ADMIN_CREDIT_CARD_PROCESSING' LIMIT 1)
171 WHERE name LIKE 'credit.processor.stripe%' AND update_perm IS NULL;
174 Missing Upgrade Script Notice
175 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
176 It was recently discovered that the 2.11.2 tarball was missing the
177 upgrade script for 2.11.1. If you upgraded straight to 2.11.2 from
178 2.11.0 or prior, please make sure to apply the
179 2.11.0-2.11.1-upgrade-db.sql before moving on to the 2.11.3 script.
183 Evergreen 2.11.3 also contains the following bugfixes:
185 * A fix to correctly apply floating group settings when performing
187 * An improvement to the speed of looking up patrons by their username;
188 this is particularly important for large databases.
189 * A fix to properly display the contents of temporary lists ('My List') in the
190 public catalog, as well as a fix of the HTML coding of that page.
191 * A fix to the Spanish translation of the public catalog that could
192 cause catalog searches to fail.
193 * A fix of a problem where certain kinds of requests of information
194 about the organizational unit hierarchy to consume all available
195 `open-ils.cstore` backends.
196 * A fix to allow staff to use the 'place another hold' link without
197 running into a user interface loop.
198 * A fix to the 'Edit Due Date' form in the web staff client.
199 * A fix to the definition of the stock 'Full Overlay' merge profile.
200 * A fix to sort billing types in alphabetical order in the web staff
202 * A fix to the display of the popularity score in the public catalog.
203 * A fix to the 'return to grouped search results' link in the public
205 * A fix to allow pre-cat checkouts in the web staff client without requiring
206 a circulation modifier.
207 * A fix to how Action/Trigger event definitions with nullable grouping
208 fields handle null values.
209 * Other typo and documentation fixes.
213 We would like to thank the following individuals who contributed code,
214 testing and documentation patches to the 2.11.3 point release of
237 This release contains several bugfixes improving on Evergreen 2.11.1
239 * A fix to the web client patron interface that changed the holds count in the
240 patron summary from total / available to available / total.
241 * A fix to an issue where the Closed Dates Editor was displaying an extra day of
243 * A fix to the Closed Dates Editor so that it now displays "All Day" when the
244 library is closed for the entire day.
245 * A fix to properly format LC Call numbers in spine label printing.
246 * A fix to a bug that was causing intermittent search failures.
247 * A fix to a bug that was causing search failures for Copy Location Group
249 * A fix to significant increased slowness with holds transfers.
250 * The addition of an index to the action.aged_circulation table to resolve a
251 problem with long-running queries.
252 * A fix to redirects that for one-hit metarecord searches for systems that
253 have enabled the setting to immediately jump to a bib record on one-hit searches.
254 * A fix to the new acquisitions cost field available in the copy editor to
255 resolve an issue where accidentally clearing out the value in the field resulted
257 * A fix to a bug that broke the Alternate Printable Hold Pull List and Vandelay
258 uploads on systems that were running OpenSRF 2.5.
262 We would like to thank the following individuals who contributed code,
263 testing and documentation patches to the 2.11.1 point release of
282 This release contains several bug fixes improving on Evergreen 2.11.0
284 * A fix to that provides alphabetical sorting to the fund selector in
285 the Acquisitions Selection List -> Copies interface.
286 * A fix to the web client check in screen allowing users to click the
287 title of the checked-in item to retrieve the bib record for that item.
288 * The addition of a progress bar that displays when conducting a patron searchin the web client.
289 * A fix to the web client patron interface so that total Items Out in the
290 patron summary now includes overdue and long overdue items. It will also
291 include Lost and Claims Returned items when the appropriate library
293 * A change to the public catalog My Account screen where the font for
294 leading articles will now be smaller when sorting a list by title.
295 * A fix to subject links in the catalog's record summary page so that
296 periods are no longer stripped from resulting subject searches, leading
297 to more accurate results when those links are clicked.
298 * A fix to avoid unint warnings in the logs for prox_cache in
299 open-ils.circ.hold.is_possible.
300 * A fix to rounding errors that occurred when summing owed/paid totals
301 for display in the catalog's credit card payment form.
302 * A change to sort behavior in the My Account screens. Previously, a
303 third click on a column header returned the list to its original sort
304 order. Clicking column headers will now simply toggle the sort
305 between ascending and descending order.
306 * The Permalink option on the catalog's record summary page will now be
307 hidden in the staff client because clicking the link in the client led
308 to no discernible change for users.
309 * A fix to the display of permanent lists in the catalog, which had broken
311 * A fix to the text of a notice that displays when migrating circulation
312 history during the upgrade to 2.10.
313 * An improvement to the performance for the lookup of a user's circ
314 history by adding an index on action.usr_circ_history(usr).
315 * A fix so that when a bib record's fingerprint changes, it gets correctly
316 moved to a different metarecord.
320 We would like to thank the following individuals who contributed code,
321 tests and documentation patches to the 2.11.1 point release of
340 Tablefunc Extension No Longer Required
341 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
342 Changes in the behavior of the connectby function in PostgreSQL 9.5
343 have prompted its removal from the database. It is easier for
344 Evergreen to maintain compatibility with previous versions of
345 PostgreSQL without this function.
347 By eliminating the use of the connectby function, we eliminate the
348 requirement for the tablefunc database extension. It is no longer
349 installed when the database is created. If you are upgrading and wish
350 to remove it from your database, you may run the following statement
351 in the database to drop it:
353 DROP EXTENSION tablefunc;
369 Add Date Header to Action Trigger Email/SMS Templates
370 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
371 The Date: header specified in RFC 2822 has been added to the seed data
372 for the example Action Trigger email and SMS templates, but no attempt
373 has been made to automatically modify existing templates. To add this
374 header (and end any "Why are my library emails from 1969/70?" questions
375 you may have heard) make sure the following lines are in all templates
376 that use the SendEmail or SendSMS reactors:
378 The first is already in most sample templates, but you may need to add
379 it to the top of any custom templates:
382 And this line should be inserted into the header block of each template:
383 `Date: [%- date.format(date.now, '%a, %d %b %Y %T -0000', gmt => 1) %]`
389 Support for Ubuntu 16.04
390 ^^^^^^^^^^^^^^^^^^^^^^^^
391 Adds support for Ubuntu Xenial Xerus (16.04).
400 User activity types are now set to transient by default for new
401 Evergreen installs.. This means only the most recent activity entry per
402 user per activity type is retained in the database.
404 This change does not affect existing activity types, which were set to
405 non-transient by default. To make an activity type transient, modify the
406 'Transient' field of the desired type in the staff client under Admin ->
407 Server Administration -> User Activity Types.
409 Setting an activity type to transient means data for a given user will
410 be cleaned up automatically if and when the user performs the activity
411 in question. However, administrators can also force an activity
412 cleanup via SQL. This is useful for ensuring that all old activity
413 data is deleted and for controlling when the cleanup occurs, which
414 may be useful on very large actor.usr_activity tables.
416 To force clean all activity types:
419 ------------------------------------------------------------
420 SELECT actor.purge_usr_activity_by_type(etype.id)
421 FROM config.usr_activity_type etype;
422 ------------------------------------------------------------
424 NOTE: This could take hours to run on a very large actor.usr_activity table.
435 Authority Record Import Updates Editor, Edit Date.
436 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
437 Importing an authority record via MARC Batch Import/Export now causes the
438 authority record's editor and edit_date fields to be updated. The editor
439 value may come from the MARC 905u field or, if none is present, the user
440 performing the import.
445 Authority Propagation Updates Bib Editor / Edit Date
446 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
447 When a bib record is automatically updated as a result of the
448 modification of a linked authority record, the bib record's "Last Edit
449 Date/Time" and "Last Editing User" fields will be updated to match the
450 time of the update and the editor of the modified authority record.
452 A new global flag is available to control this behavior called
453 'ingest.disable_authority_auto_update_bib_meta' ("Authority Automation:
454 Disable automatic authority updates from modifying bib record editor
455 and edit_date"). When enabled, theses fields will not be updated. By
456 default, this setting is disabled.
458 An additional speed improvement is included in this feature. No attempt
459 will be made to update linked bib records when the normalized heading of
460 the modified authority record is unchanged by the authority record update.
465 Bibliographic Record Source Now Copied to 901$s
466 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
467 If a bibliographic record has a source set, the name of that source
468 is now copied to the 901$s whenever the record is created or updated.
469 This allows the source to be used for record matching and MARC
475 Option to Update Bib Source and Edit Details on Record Import
476 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
477 When importing records through the client, users will now have the ability to
478 define whether the bib source, last editor, and last edit date should be updated
479 on a record merge/overlay.
481 In MARC Batch Import / Export, select the _Merge / Overlay_ tab. Each entry in
482 the table has a value in the new _Update bib. source_ column. If that value is
483 True, then the bib source, last editor, and last edit date will be updated.
485 The two system-defined entries have been pre-set to appropriate values (Full
486 Overlay = true; Match-Only Merge = false).
496 Staff Client Honors Aged Circulations
497 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
499 The browser and XUL clients now better represent copy checkout history
500 by honoring and displaying information from aged circulations.
502 * Browser client 'Recent Circ History' and the analogous XUL client
503 'Circulation History' tabs show summary data for aged circulations
504 as well as regular/active circulations. When aged circulation data
505 is displayed, any references to patron names are replaced by the string
506 "<Aged Circulation>".
508 * Browser client 'Circ History List' and the analogous XUL client
509 'Last Few Circulations' tabs behave as above, plus their 'Add
510 Billing' buttons are disabled when displaying aged circulation data.
512 * XUL client 'Retrieve Last Patron' actions from various UI's report,
513 "Item XXX circulation is an aged circulation and has no linked user".
514 Browser client analog uses 'Circ History List' instead; no additional
521 "Canceled Transit" Item Status
522 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
524 Previously, when a transit was aborted, the transited item would either go into
525 "Reshelving" status or would return to whatever status it was in when it went
526 into transit, even when the item itself was in a different status (including
527 "Checked out"). Now, for most transits that get aborted, the item is put into a
528 new status, "Canceled Transit", which signals to staff the actual state of the
529 item. This feature only affects items with a status of "In transit" and does
530 not affect items that were in the following statuses at the time they were sent
541 * Any custom statuses
543 This change should help clear up confusing situations caused by the previous
544 "abort transit" behavior, such as items showing "Available" when they are actually
545 en route, and patrons' items mysteriously disappearing from their accounts and
546 showing "Available" at the item-owning library without evidence of check-in.
551 Copy Status "Is Available" Flag
552 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
554 A new boolean field is now available for copy statuses to indicate when copies
555 having a given status should be considered available. The field has 2 main
558 1. Checking out an "available" copy will no longer result in an override-able
559 "COPY_NOT_AVAILABLE" alert for staff. The copy will checkout without
562 2. "Available" copies will appear in catalog searches where "limit to
563 available" is selected as a search filter.
565 By default, the "Available" and "Reshelving" statuses have the "Is Available"
566 flag set. The flag may be applied to local/custom statuses via the copy
567 status admin interface.
573 Email Checkout Receipts
574 ^^^^^^^^^^^^^^^^^^^^^^^
575 This feature allows patrons to receive checkout receipts through email
576 at the circulation desk in the web client and in the Evergreen self-checkout
577 interface. Patrons need to opt in to receive
578 email receipts by default and must have an email address associated with their
579 account. Opt in can be staff mediated at the time of account creation or in
580 existing accounts. Patrons can also opt in directly in their OPAC account or
581 through patron self-registration. This feature does not affect the behavior of
582 checkouts from the XUL client or SIP2 devices.
584 Patrons can opt in to receive email checkout receipts by default via
585 a new _Email checkout receipts by default_ patron setting.
587 This feature also enhances the patron staging tables so that patron
588 settings can be chosen during self-registration.
590 The web staff interface's checkout screen now includes a "Quick
591 Receipt" button that allows staff members to generate a receipt
597 Set Per-OU Limits on Allowed Payment Amounts
598 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
599 Two new settings have been added to prevent clerks from accidentally clearing
600 all patron bills by scanning a barcode into the Payment Amount field, or
601 accidentally entering the amount without a decimal point (such as you
602 would when using a cash register).
604 Both settings are available via the Library Settings Editor. The _Payment
605 amount threshold for Are You Sure? dialog_ (ui.circ.billing.amount_warn)
606 setting identifies the amount above
607 which staff will be asked if they're sure they want to apply the payment.
608 The _Maximum payment amount allowed_ (ui.circ.billing.amount_limit)
609 setting identifies the maximum amount of
610 money that can be accepted through the staff client.
612 These settings only affect the staff client, not credit
613 cards accepted through the OPAC, or direct API calls
614 from third party tools.
624 Additional Fields Available for Display in Some Interfaces
625 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
626 The holds age protection field will now be available for display in the
627 following interfaces:
629 * Item status list view column picker
630 * Item status alternate view
631 * Holdings maintenance column picker
633 The asset.copy.cost field, which records the amount paid for an item when
634 an invoice is processed, will be available for display in the following
637 * Items status list view column picker
638 * Item status alternate view
650 Merge Notification Preferences Tables in TPAC
651 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
652 The patron notification preference page in the public catalog
653 used to have two tables, separating notification settings
654 based on their source. Since that distinction does not matter
655 to patrons, and since the two tables aren't styled consistently,
656 they are merged together.
661 Improved Holds Screens in My Account
662 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
663 The grids in the My Account _Items on Hold_ and _Holds History_ interfaces are
664 simplified. Data previously contained in their own Activate, Active, and Date
665 Fulfilled columns are now incorporated into the Status column. To further
666 declutter the interface, the holds queue position will only show when the user
667 most needs the information - before the hold has been captured.
669 Distinct CSS classes have also been added for each hold status and each date
670 that could potentially display in these holds interfaces. A new default style
671 highlights the _Available_ status in green and the _Suspended_ status
679 Popularity Boost for Ranking Search Results
680 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
682 This feature uses factors such as circulation and hold activity, record and item age, and item ownership counts to generate popularity badges for bibliographic
683 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.
685 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.
687 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.
689 Finally, there will continue to be a pure _Relevance_ sort option, which is the version that exists today.
691 Administrators can comment out one of the available sort methods by editing the
692 filtersort.tt2 file.A global flag will allow Evergreen sites to select a default sort method.
697 Administrative interfaces to configure badges are only available in the web
698 client. Administrators can also configure badges directly via the database.
700 Available Popularity Parameters available for badges include:
702 * Holds Filled Over Time
703 * Holds Requested Over Time
705 * Circulations Over Time
706 * Current Circulation Count
709 * Holds/Holdable Ratio
710 * Percent of Time Circulating
711 * Bibliographic Record Age (days)
712 * Publication Age (days)
713 * Available On-Line (for e-books, etc)
716 Badges can be configured to apply to a targeted group of bibliographic records
717 based on the following available filters:
720 * Bibliographic source
721 * Circulation modifier
722 * Copy location group
724 Badges can also be be restricted to materials owned by a specific organizational
727 This new feature comes with a starter badge based on the top 97th percentile of
728 holds requested over the past five years.
733 Ratings for records will be displayed in the catalog in the following ways:
735 * On the record result page, the overall average popularity rating is displayed with a label of _Popularity_.
737 * On the record detail page, each individual badge earned by the record is
738 displayed with its rating.
742 * **OPAC Default Sort (opac.default_sort)**: Identifies the default sort method
743 to be used in the catalog.
745 * **Maximum popularity importance multiplier for popularity-adjusted relevance
746 searches (search.max_popularity_importance_multiplier):** A multiplier identifying
747 the importance of popularity in the Popularity-Adjusted Relevance ranked
748 searches. The number should be a decimal ranging between 1.0 and 2.0. The
749 default value is 1.1.
751 More detailed information is available in the TechRef docs directory of the
752 Evergreen source code.
757 Removal of Advanced Hold Options link when part holds are expected
758 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
759 If a user attempts to place a metarecord hold when all eligible copies
760 contain parts, the hold will fail. To help prevent the user from reaching
761 a dead end while placing holds, the *Advanced Hold Options* link is removed
762 from the Place Hold page in cases where all copies on the record contain
763 parts. The *Advanced Hold Options* link will remain for records that have
764 a mix of parted and non-parted copies.
777 Renewals attempted via SIP will now consider whether a penalty is configured
778 to block renewals before blocking the renewal. Previously, any penalty, even
779 if it wasn't set to block renewals, would prevent a renewal from succeeding
786 Treat SIP Location Field as Login Workstation
787 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
788 When using a version of SIPServer that supports the feature,
789 the Location (CP) field of the Login (93) message will be
790 used as the workstation name if supplied. Blank or missing
791 location fields will be ignored. This allows users or reports
792 to determine which selfcheck performed a circulation.
805 Translations in this release have been significantly increased. In
806 particular, Spanish has received a huge update with over 9,000 new
807 translations, Czech has received a sizable update of over 800
808 translations, and additional smaller updates have been added for
809 Arabic, French (Canada), and Armenian.
813 2.11.0 Acknowledgments
814 ----------------------
815 The Evergreen project would like to acknowledge the following
816 organizations that commissioned developments in this release of
820 * Georgia Public Library Service
822 * Pennsylvania Integrated Library System
823 * Pioneer Library System
825 We would also like to thank the following individuals who contributed
826 code, management, translations, documentation patches and tests to this
827 release of Evergreen:
847 We also thank the following organizations whose employees contributed
851 * Central/Wester Massachusetts Automated Resource Sharing
852 * Equinox Software, Inc.
853 * Emerald Data Networks, Inc.
855 * Georgia Public Library Service
856 * King County Library System
858 * Laurentian University
861 * North of Boston Library Exchange
862 * Traverse Area District Library
864 We regret any omissions. If a contributor has been inadvertently
865 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / working / Evergreen.git / blob