1 Evergreen 2.9 Release Notes
2 ===========================
8 This release contains several bugfixes improving on Evergreen 2.9.1.
10 Acquisitions / Cataloging
11 ~~~~~~~~~~~~~~~~~~~~~~~~~
12 * Allows the Z39.50 itnerface and the acquisitions MARC Federated Search
13 interface to search the UPC index of the local catalog if Z39.50 is configured
15 * Fixes an issue where spaces in a PO name cause the system to improperly
16 process EDI response messages.
20 * Fixes a problem where the balance owed was miscalculated when a row
21 was deleted from money.billing.
22 * Fixes an issue where credit card payments made via PayflowPro failed because
23 Evergreen does not install the PayflowPro module by default.
24 * Changes credit card payment behavior so that the patron's billing address will
25 be read when the patron has no mailing address. If all address fields are
26 properly set by the API caller except the country and the
27 patron has no addresses, the system will attempt to determine the country from
28 library settings. If insufficient address data is provided, the system will
29 return an invalid params Event.
30 * Modifies the reasons for various void/adjust events to more accurately reflect
31 the reason why a fine/fee was removed from a patron's record.
35 * Fixes an issue where the reset password link was displaying even on systems
36 that had disabled the ability to reset passwords.
37 * Fixes an issue where the journal type search did not work when entering it as
38 the second or third input on the advanced search screen.
39 * Fixes an issue where catalog translations were broken by creating separate
40 directories for the catalog and web staff client translations.
44 * Changes marc_export to only print "waiting for input" when running
49 We would like to thank the following individuals who contributed
50 code and documentation patches to the 2.9.1. point release of Evergreen:
60 We also thank the following organizations whose employees contributed
64 * Equinox Software, Inc.
65 * King County Library System
66 * Merrimack Valley Library Consortium
71 This release contains several bugfixes improving on Evergreen 2.9.0.
75 * Protects the stock acquisitions cancel reasons from deletion since they
76 are required to properly handle EDI order responses.
77 * Changes the copy location dropdown so that users can view and select copy
78 locations owned outside the workstation branch if they have permission to do so.
79 This fix also adds the copy location's owning org unit to the display.
83 * Allows use of more special characters, including - and +, when
84 entering a library's main email address in the Organizational Units
86 * Fixes an issue where marc_export attempts to call a non-existent field
87 on MARC::Record if an error occurs while exporting authority records.
91 * Fixes the mapping between copies and the target part when using "Merge
92 Selected" in the Monographic Parts interface.
93 * Fixes an issue with the horizontal scrollbar bar in the MARC import
94 queue inspector so the focus no longer jumps to the top of the screen
95 when attempting to use the scrollbar.
96 * Hides the staff-client saved searches header from screen readers when
97 using the public catalog in non-staff mode.
101 * When placing a hold via the staff client and clicking Advanced Hold
102 Options, fixes an issue where the barcode field populated with the
103 staff member's barcode.
104 * Fixes an issue where some holds with a higher proximity were
105 preferred over holds with a lower proximity because the list of
106 proximities of elgible copies was sorting ASCIIbetically instead of
108 * Adds a delete flag for monographic parts, fixes staff client errors that
109 were previously caused by deleted parts, and cancels any holds attached to
111 * Fixes an internal error that appeared when trying to renew an item on the
112 booking resource list through the public catalog. Users will now get a message
113 saying they do not have permission to renew the item.
118 * Fixes an issue where unclosed phrase searches returned zero results and
119 tied up the open-ils.storage process.
120 * Fixes an issue where phrase searches were ignoring modifiers used in relevance
121 ranking, leading to poorly-ranked results.
122 * Fixes an issue where parameters weren't properly maintained when
123 searching by copy location group.
127 * Adds support for UTF-8 in the Reports interface.
131 We would like to thank the following individuals who contributed
132 code and documentation patches to the 2.9.1. point release of Evergreen:
151 We also thank the following organizations whose employees contributed
154 * Berklee College of Music
156 * British Columbia Libraries Cooperative
158 * Emerald Data Networks, Inc.
159 * Equinox Software, Inc.
160 * Georgia Public Library Service
161 * Lake Agassiz Regional Library
162 * Laurentian University
163 * Massachusetts Library Network Cooperative
164 * Merrimack Valley Library Consortium
166 * Northwest Regional Library System
167 * Pohjois-Karjalan Tietotekniikkakeskus Oy
168 * Rodgers Memorial Library
170 We regret any omissions. If a contributor has been inadvertantly
171 missed, please open a bug at http://bugs.launchpad.net/evergreen/
177 Remove Script-Based Circulation Configuration
178 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
180 Evergreen no longer supports script-based circulation policies. All
181 policies must now be managed within the Local Administration ->
182 Circulation Policies, Hold Policies, and related interfaces.
185 Remove open-ils.penalty service
186 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
188 Evergreen no longer uses the 'open-ils.penalty' service. It is safe
189 (though not required) to remove the following XML chunks from
190 /openils/conf/opensrf.xml after stopping services.
193 ----------------------------------------------------------------------------
195 <!-- first element -->
198 <keepalive>3</keepalive>
199 <stateless>1</stateless>
200 <language>perl</language>
201 <implementation>OpenILS::Application::Penalty</implementation>
202 <max_requests>99</max_requests>
204 <max_requests>1000</max_requests>
205 <unix_log>open-ils.penalty_unix.log</unix_log>
206 <unix_sock>open-ils.penalty_unix.sock</unix_sock>
207 <unix_pid>open-ils.penalty_unix.pid</unix_pid>
208 <min_children>1</min_children>
209 <max_children>15</max_children>
210 <min_spare_children>1</min_spare_children>
211 <max_spare_children>5</max_spare_children>
214 <patron_penalty>penalty/patron_penalty.js</patron_penalty>
215 <script_path>LIBDIR/javascript</script_path>
216 <script_path>LOCALSTATEDIR</script_path>
217 <script_path>LOCALSTATEDIR/catalog</script_path>
221 <!-- second element -->
223 <appname>open-ils.penalty</appname>
224 ----------------------------------------------------------------------------
227 Removal of deprecated "JSPAC" interface
228 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
230 The deprecated Javascript OPAC interface known as "JSPAC" is no
231 longer included in Evergreen as of this release.
233 With the understanding that local sites may have made use of
234 existing parts of the old JSPAC interface -- especially images and
235 CSS -- no attempt is made at upgrade time to automatically remove
236 the existing files from disk.
238 When upgrading, you may wish to remove "index.xml" from your Apache
239 DirectoryIndex directives.
241 The following directories, xml, js, and css files were formerly part
242 of JSPAC, and you may be able to safely remove them from your system
243 after verifying that they and their contents are no longer required:
245 - web/opac/common/css/
246 - web/opac/common/js/dtree.js
247 - web/opac/common/xml/
248 - web/opac/extras/bbags.js
249 - web/opac/extras/bbags.xml
250 - web/opac/skin/default/js/
251 - web/opac/skin/default/xml/
254 The list of images removed in this change is lengthy, and not
258 Removal of legacy selfcheck interface
259 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
261 The legacy selfcheck interface is no longer included in Evergreen as
264 This interface was formerly located at a URL ending in
265 extras/selfcheck/selfcheck.xml
267 No attempt is made at upgrade time to automatically remove this
270 It is recommended that you remove this interface and its associated
271 configuration after performing an upgrade:
273 (paths relative to Evergreen web root)
275 - opac/extras/selfcheck/selfcheck.css
276 - opac/extras/selfcheck/selfcheck.js
277 - opac/extras/selfcheck/selfcheck.xml
278 - opac/extras/selfcheck/selfcheck_print.css
280 You can also remove the related Apache configuration block starting
284 <LocationMatch .*/selfcheck.xml>
296 Improved reporting of progress during purchase order activation
297 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
298 The progress dialog that is displayed when activating a purchase
299 order now displays more information, particularly during the asset
300 creation phase. It is now also updated in a more linear fashion;
301 making it less likely for it to appear that the activation has
307 ==== "Blanket" Orders
309 "Blanket" orders allow staff to invoice an encumbered amount multiple times,
310 paying off the charge over a period of time. The work flow supported by this
311 development assumes staff does not need to track the individual contents of
312 the order, only the amounts encumbered and invoiced in bulk.
316 . Staff creates PO with a Direct Charge of "Popular Fiction 2015" and
317 a charge type of "Blanket Order".
318 . The amount entered for the charge equals the total amount expected
319 to be charged over the duration of the order.
320 . When a shipment of "Popular Fiction" items arrive, staff creates an
321 invoice from the "Popular Fiction 2015" PO page and enters the amount
322 billed/paid for the received shipment under the "Popular Fiction 2015"
323 charge in the invoice.
324 . When the final shipment arrives, staff select the 'Final invoice
325 for Blanket Order' option on the invoice screen to mark the PO as
326 'received' and drop any remaining encumbrances to $0.
327 .. Alternatively, if the PO needs to be finalized without creating
328 a final invoice, staff can use the new 'Finalize Blanket Order'
329 option on the PO page.
331 ===== New Components/Terminology/Concepts
333 * Invoice Item Types have a new flag called 'blanket', available under
334 Admin -> Server Administration -> Acq -> Invoice Item Types in the
336 * Any direct charge using a 'blanket' item type will create a long-lived
337 charge that can be invoiced multiple times.
338 * Such a charge is considered open until its purchase order is "finalized"
340 * "Finalizing" a PO changes the PO's state to 'received' (assuming there are
341 no pending lineitems on the PO) and fully dis-encumbers all blanket charges
342 on the PO by setting the fund_debit amount to $0 on the original fund_debit
344 * Invoicing a 'blanket' charge does the following under the covers:
345 .. Create an invoice_item to track the payment
346 .. Create a new fund_debit to implement the payment whose amount matches the
348 .. Subtract the invoiced amount from the fund_debit linked to the original
349 'blanket' po_item, thus reducing the amount encumbered on the charge as
350 a whole by the invoiced amount.
351 * A PO can have multiple blanket charges. E.g. you could have a blanket
352 order for "Popular Fiction 2015" and a second charge for "Pop Fiction
353 2015 Taxes" to track / pay taxes over time on a blanket charge.
354 * A PO can have a mix of lineitems, non-blanket charges, and blanket charges.
355 * A 'blanket' Invoice Item Type cannot also be a 'prorate' type, since it's
356 nonsensical. Blanket items are encumbered, whereas prorated items are
357 only paid at invoice time and never encumbered.
369 Examples in Apache configuration for "No Image"
370 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
371 There are now commented out examples for custom images to be used when
372 "no image" is present in the catalog for cover art. The included examples
373 are for small/medium/large jacket image art in the event they are not
374 found by the configured Added Content module.
379 Pre-Expiration A/T Event Definition
380 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
381 A new Action Trigger event definition ("30 Day Account Expiration Courtesy
382 Notice") for sending alerts to users before their accounts are expired has
383 been added. This is intended to give users time to renew their account before
384 they lose access to library services.
389 Improved caching of web server templates
390 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
391 Template Toolkit processors used by Apache are now cached for
392 better performance (by virtue of thereby being able to take advantage
393 of Template Toolkit's internal caching mechanism). In addition, the
394 *compiled* versions of the templates themselves can be cached to
395 provide an additional performance boost.
397 Two Apache virtualhost configuration variables are added to
398 control caching of compiled templates:
400 * `OILSWebCompiledTemplateCache` - specifies location on the
401 web server filesystem to store compiled templates.
402 * `OILSWebTemplateStatTTL` - specifies number of seconds before
403 checking to see if a newer version of a cached template is
406 As a result of the caching changes, it is now necessary for
407 Evergreen administrators to reload Apache to ensure that a change
408 to (say) TPAC templates becomes visible.
418 Display Authority Subject Heading Thesaurus Value
419 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
421 There is now a new column in the *Manage Authorities* search results. Each result row now displays each authority's thesaurus value with a "Thes: " prefix. In the authority MARC editor interface the thesaurus value corresponds to the "Subject Heading Thesaurus" fixed field (http://www.loc.gov/marc/authority/ad008.html) labeled “Subj”. For example, a value of "Thes: a" means that the authority is a Library of Congress Subject Heading, and a value of "Thes: k" means the authority is a Canadian Subject Heading.
423 *A Library of Congress list of thesaurus values:*
426 * '' = Alternate no attempt to code
427 * a = Library of Congress Subject Headings
428 * b = LC subject headings for children's literature
429 * c = Medical Subject Headings
430 * d = National Agricultural Library subject authority file
431 * k = Canadian Subject Headings
433 * r = Art and Architecture Thesaurus
434 * s = Sears List of Subject Headings
435 * v = Repertoire de vedettes-matiere
437 * | = No attempt to code
442 Importing Statistical Categories
443 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
444 You can now retrieve statistical categories (stat cats) from the MARC
445 record and apply them to the items in Evergreen. When importing or
446 overlaying items through the Vandelay MARC batch import process, edit
447 your Holdings Import Profile to tell Evergreen which subfield contains
448 your stat cat data. That subfield in your MARC records should be
449 formatted like the following:
452 CATEGORY 1|VALUE 1||CATEGORY 2|VALUE 2
455 Notice that the pipe character '|' is used to separate each category
456 from its value, and two pipes separate each pair of category values.
458 If you are overlaying existing copies which already have stat cats
459 attached to them, the overlay process will keep those values unless the
460 incoming copies contain updated values for matching categories.
465 Remove the ‡biblios.net Z39.50 target from seed data
466 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
467 The Z39.50 target at z3950.biblios.net/bibliographic has not worked
468 for years, so its service definition is no longer provided in the
469 seed data for new installations of Evergreen.
471 Users of existing Evergreen systems should consider removing
472 the Z39.50 definition for ‡biblios.net. This can be done from
473 Admin | Server Administration | Z39.50 Servers in the staff
479 SKOS for coded values
480 ^^^^^^^^^^^^^^^^^^^^^
481 Some vocabularies used (or which could be used) for stock
482 record attributes and coded value maps in Evergreen are
483 published on the web using SKOS. The record attributes system
484 can now associate Linked Data URIs with specific attribute
485 values. In particular, seed data supplying URIs for the
486 RDA Content Type, Media Type, and Carrier Type in this release.
488 This is an experimental, "under-the-hood" feature that will be built
489 upon in subsuquent releases.
494 MARC Tag-table Service
495 ^^^^^^^^^^^^^^^^^^^^^^
496 The tag tables for the web staff client MARC editor are
497 now stored in the database rather than a separate XML
498 tooltips file as used by the XUL MARC editor. The tag-table
499 service, which is part of the web staff client sprint 2
500 preview in this release, has the following features:
502 - specifies whether (sub)fields are optional or mandatory
503 - specifies whether (sub)fields are repeatable or not
504 - a coded value map can be associated with a subfield to
505 establish a controlled vocabulary for that subfield
506 - MARC field and subfield definitions can be overridden
507 by institutions further down in the organizational unit
508 hierarchy. This allows, for example, a library to specify
509 definitions for local MARC tags.
510 - values supplied by the tag-table service are used to
511 populate values in context menus in the web staff client
514 The initial seed data for the in-database tag table is
515 derived from the current tooltips XML file.
520 Web staff client cataloging preview
521 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
522 The web staff client now includes additional functionality
523 to support cataloging and item maintenance, including:
526 - the service backing the authority headings chooser now
527 has the ability to filter the browse by subject thesaurus
528 - Z39.50 search and record import
529 - improvements to copy and record bucket functionality
530 - embedding the link checker interface
531 - embedding the MARC batch import/export interface
532 - the web staff volume/copy editor
534 Nearly all of the cataloging functionality available in the XUL
535 staff client is now present in the web staff client with the
536 exception of printing spine labels. Nonetheless, the web staff
537 client remains a preview and is not recommended for production use.
547 Conditional Negative Balances
548 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
549 Evergreen sites will now have more control over whether a negative balance can
550 be applied to a user's billing record and when that negative balance can be
551 applied. Through a series of Library Settings, a site can prohibit negative
552 balances on bills or can allow those negative balances to be applied for a
553 specific period of time after a lost or overdue bill is charged to the user.
554 Sites can set a default for all types of bills or can apply distinct settings
555 for lost bills and for overdue fines. The more specific settings will override
558 Sites that opt to allow negative balances for a specific period of time must
559 1) enable the relevant "prohibit negative balances" setting(s) and 2) specify
560 the time period in the relevant Negative Balance Interval setting(s).
562 In addition to the new library settings, the system now has a new account
563 adjustment payment type. This payment type will be utilized for libraries
564 prohibiting negative balances to replace the previous voiding behavior that
565 caused the negative balances to occur. The account adjustment payment type will
566 also be used for all libraries, regardless of the state of negative balance
567 settings, in cases where overdue fines are adjusted when an overdue item is
570 An _Adjust to Zero_ option has been added to the bills interface of the patron
571 record. This option will always adjust the selected bill to a zero balance.
572 It can also be used to easily clear a negative balance from the patron's
573 record. A user must have the new ADJUST_BILLS permission to see and use this
576 This new feature also changes the behavior for the client option to void a bill
577 from the patron record. If a user does not have the VOID_BILLING permission, the
578 option to void bills will be hidden in the bills interface and in the Full
579 Details view of a specific bill.
581 To truly remove the ability to produce negative balances on a transaction,
582 administrators need to 1) enable the relevant setting in the Library Settings
583 Editor and 2) remove the VOID_BILLING permission from staff accounts since
584 manual voiding will continue to produce negative balances.
588 * Negative Balance Interval (Default) (bill.negative_balance_interval_default)
589 * Negative Balance Interval for Lost (bill.negative_balance_interval_on_lost) -
590 * Negative Balance Interval for Overdues (bill.negative_balance_interval_on_overdues
591 * Prohibit negative balance on bills (Default) (bill.prohibit_negative_balance_default)
592 * Prohibit negative balance on bills for lost materials (bill.prohibit_negative_balance_on_lost)
593 * Prohibit negative balance on bills for overdue materials (bill.prohibit_negative_balance_on_overdues)
602 Selfcheck Inactivity Warning
603 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
605 The Selfcheck interface now warns patrons when they are about to be
606 logged out due to inactivity 20 seconds prior to logging them out.
608 The inactivity timeout is also reset with each checkout to avoid timeouts
609 while checking out lots of items.
614 User Registration Includes Inactive Accounts in Dupe Search
615 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
616 When registering a user, the system checks to see if there are already exiting users with the same name, address, email, etc. Now this duplicate user search includes inactive users so that matches can be re-activated if desired, rather than creating duplicate accounts.
626 Link in catalog to clear Added Content cache
627 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
628 On the catalog's record summary page, there is now a link for staff that
629 allow them to forcibly clear the cache for the Added Content for that
630 record. This is helpful if the Added Content retrieved the wrong
631 cover jacket art, summary, etc. and caches the wrong result.
636 Disable Google Analytics in Staff Client
637 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
638 In the staff client interface, Google Analytics for the web catalog is
639 now disabled by default. This was a preventive measure to reduce the
640 potential risks for leaking patron information.
645 Move Acquisitions Admin Menu
646 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
647 In the staff client interface, the Acquisitions Administration menu is
648 now directly accessible from the main "Admin" menu instead of
649 living under "Server Administration". It has also been renamed as "Acquisitions
660 Account Expiration Date in My Account
661 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
662 The Account Expiration Date has been added to the catalog's My Account display
663 on the main Account Summary page and the Account Preferences page. This should
664 help patrons with figuring out when their accounts are due to expire before
665 they actually expire.
669 Change to Available Copies Display
670 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
671 The _Show_ link in the available copies area of the record summary will now
672 display for any org unit that owns a copy of a particular title, even if all
673 those copies are unavailable. The _Show_ link will not display if a) the copy
674 display is already scoped to that org unit or b) the org unit does not own
677 The language has also been changed to read "x of y copies available at z
684 Column sorting in circulation screens
685 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
687 Sorting of selected columns is now available in the *Items Checked Out*, *Check Out History*,
690 * Clicking on the appropriate column heads now sorts the contents from
691 ``ascending'' to ``descending'' to ``no sort''. (The ``no sort'' restores the
692 original list as presented in the screen.)
694 * The sort indicator (an up or down arrow) is placed to the right
695 of the column head, as appropriate.
697 * The combined *Title/Author* column in the *Items Checked Out* screen is now separated into two
698 independently sortable columns (Title and Author).
700 * Title sorting is done with the non-filing characters (leading ``the'', ``a'',
701 ``an'', and other langugage equivalents) removed. The leading articles are rendered in
702 a smaller font, so as to keep the main entry prominent. In
703 addition to the non-filing characters removed for the sort, leading
704 non-alphanumeric characters are ignored in the sort.
709 New bib source variable for catalog customization
710 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
711 For bibliographic records, there is a "bib source" that can be
712 associated with every record. This source is now available as a
713 variable that can be used behind the scenes when customizing
714 the online catalog. The new bib source variables do not present
715 themselves in the catalog display by default.
720 New class attribute for e-resource links
721 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
722 In the catalog, links to electronic resources now have a link class
723 attribute of "uri_link" to make them easier to customize or build
724 additional services upon.
730 Removal of deprecated "JSPAC" interface
731 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
733 The deprecated Javascript OPAC interface known as "JSPAC" is no
734 longer included in Evergreen as of this release.
736 With the understanding that local sites may have made use of
737 existing parts of the old JSPAC interface -- especially images and
738 CSS -- no attempt is made at upgrade time to automatically remove
739 the existing files from disk.
741 When upgrading, you may wish to remove "index.xml" from your Apache
742 DirectoryIndex directives.
744 The following directories, xml, js, and css files were formerly part
745 of JSPAC, and you may be able to safely remove them from your system
746 after verifying that they and their contents are no longer required:
748 - web/opac/common/css/
749 - web/opac/common/js/dtree.js
750 - web/opac/common/xml/
751 - web/opac/extras/bbags.js
752 - web/opac/extras/bbags.xml
753 - web/opac/skin/default/js/
754 - web/opac/skin/default/xml/
757 The list of images removed in this change is lengthy, and not
763 Removal of legacy selfcheck interface
764 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
766 The legacy selfcheck interface is no longer included in Evergreen as
769 This interface was formerly located at a URL ending in
770 extras/selfcheck/selfcheck.xml
772 No attempt is made at upgrade time to automatically remove this
775 It is recommended that you remove this interface and its associated
776 configuration after performing an upgrade:
778 (paths relative to Evergreen web root)
780 - opac/extras/selfcheck/selfcheck.css
781 - opac/extras/selfcheck/selfcheck.js
782 - opac/extras/selfcheck/selfcheck.xml
783 - opac/extras/selfcheck/selfcheck_print.css
785 You can also remove the related Apache configuration block starting
789 <LocationMatch .*/selfcheck.xml>
796 The Evergreen project would like to acknowledge the following
797 organizations who commissioned developments in this release of
800 * Georgia Public Library Service
801 * Grand Rapids Public Library
802 * Kenton County Public Library
803 * King County Library System
804 * Massachusetts Library Network Cooperative
807 * Pennsylvania Integrated Library System
809 We would also like to thank the following individuals who contributed
810 code, documentation patches and tests to this release of Evergreen:
842 We also thank the following organizations whose employees contributed
845 * Anderson County Library
846 * Berklee College of Music
848 * British Columbia Libraries Cooperative
851 * Central/Western Massachusetts Automated Resource Sharing
852 * Emerald Data Networks, Inc.
853 * Equinox Software, Inc.
854 * Georgia Public Library Service
855 * Grand Rapids Public Library
856 * Indiana State Library
857 * King County Library System
858 * Lake Agassiz Regional Library
859 * Laurentian University
860 * Linn-Benton Community College
861 * Massachusetts Library Network Cooperative
862 * Merrimack Valley Library Consortium
864 * Northwest Regional Library System
866 * Traverse Area District Library
868 We regret any omissions. If a contributor has been inadvertantly
869 missed, please open a bug at http://bugs.launchpad.net/evergreen/