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:
59 We also thank the following organizations whose employees contributed
63 * Equinox Software, Inc.
64 * King County Library System
65 * Merrimack Valley Library Consortium
70 This release contains several bugfixes improving on Evergreen 2.9.0.
74 * Protects the stock acquisitions cancel reasons from deletion since they
75 are required to properly handle EDI order responses.
76 * Changes the copy location dropdown so that users can view and select copy
77 locations owned outside the workstation branch if they have permission to do so.
78 This fix also adds the copy location's owning org unit to the display.
82 * Allows use of more special characters, including - and +, when
83 entering a library's main email address in the Organizational Units
85 * Fixes an issue where marc_export attempts to call a non-existent field
86 on MARC::Record if an error occurs while exporting authority records.
90 * Fixes the mapping between copies and the target part when using "Merge
91 Selected" in the Monographic Parts interface.
92 * Fixes an issue with the horizontal scrollbar bar in the MARC import
93 queue inspector so the focus no longer jumps to the top of the screen
94 when attempting to use the scrollbar.
95 * Hides the staff-client saved searches header from screen readers when
96 using the public catalog in non-staff mode.
100 * When placing a hold via the staff client and clicking Advanced Hold
101 Options, fixes an issue where the barcode field populated with the
102 staff member's barcode.
103 * Fixes an issue where some holds with a higher proximity were
104 preferred over holds with a lower proximity because the list of
105 proximities of elgible copies was sorting ASCIIbetically instead of
107 * Adds a delete flag for monographic parts, fixes staff client errors that
108 were previously caused by deleted parts, and cancels any holds attached to
110 * Fixes an internal error that appeared when trying to renew an item on the
111 booking resource list through the public catalog. Users will now get a message
112 saying they do not have permission to renew the item.
117 * Fixes an issue where unclosed phrase searches returned zero results and
118 tied up the open-ils.storage process.
119 * Fixes an issue where phrase searches were ignoring modifiers used in relevance
120 ranking, leading to poorly-ranked results.
121 * Fixes an issue where parameters weren't properly maintained when
122 searching by copy location group.
126 * Adds support for UTF-8 in the Reports interface.
130 We would like to thank the following individuals who contributed
131 code and documentation patches to the 2.9.1. point release of Evergreen:
150 We also thank the following organizations whose employees contributed
153 * Berklee College of Music
155 * British Columbia Libraries Cooperative
157 * Emerald Data Networks, Inc.
158 * Equinox Software, Inc.
159 * Georgia Public Library Service
160 * Lake Agassiz Regional Library
161 * Laurentian University
162 * Massachusetts Library Network Cooperative
163 * Merrimack Valley Library Consortium
165 * Northwest Regional Library System
166 * Pohjois-Karjalan Tietotekniikkakeskus Oy
167 * Rodgers Memorial Library
169 We regret any omissions. If a contributor has been inadvertantly
170 missed, please open a bug at http://bugs.launchpad.net/evergreen/
176 Remove Script-Based Circulation Configuration
177 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
179 Evergreen no longer supports script-based circulation policies. All
180 policies must now be managed within the Local Administration ->
181 Circulation Policies, Hold Policies, and related interfaces.
184 Remove open-ils.penalty service
185 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
187 Evergreen no longer uses the 'open-ils.penalty' service. It is safe
188 (though not required) to remove the following XML chunks from
189 /openils/conf/opensrf.xml after stopping services.
192 ----------------------------------------------------------------------------
194 <!-- first element -->
197 <keepalive>3</keepalive>
198 <stateless>1</stateless>
199 <language>perl</language>
200 <implementation>OpenILS::Application::Penalty</implementation>
201 <max_requests>99</max_requests>
203 <max_requests>1000</max_requests>
204 <unix_log>open-ils.penalty_unix.log</unix_log>
205 <unix_sock>open-ils.penalty_unix.sock</unix_sock>
206 <unix_pid>open-ils.penalty_unix.pid</unix_pid>
207 <min_children>1</min_children>
208 <max_children>15</max_children>
209 <min_spare_children>1</min_spare_children>
210 <max_spare_children>5</max_spare_children>
213 <patron_penalty>penalty/patron_penalty.js</patron_penalty>
214 <script_path>LIBDIR/javascript</script_path>
215 <script_path>LOCALSTATEDIR</script_path>
216 <script_path>LOCALSTATEDIR/catalog</script_path>
220 <!-- second element -->
222 <appname>open-ils.penalty</appname>
223 ----------------------------------------------------------------------------
226 Removal of deprecated "JSPAC" interface
227 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
229 The deprecated Javascript OPAC interface known as "JSPAC" is no
230 longer included in Evergreen as of this release.
232 With the understanding that local sites may have made use of
233 existing parts of the old JSPAC interface -- especially images and
234 CSS -- no attempt is made at upgrade time to automatically remove
235 the existing files from disk.
237 When upgrading, you may wish to remove "index.xml" from your Apache
238 DirectoryIndex directives.
240 The following directories, xml, js, and css files were formerly part
241 of JSPAC, and you may be able to safely remove them from your system
242 after verifying that they and their contents are no longer required:
244 - web/opac/common/css/
245 - web/opac/common/js/dtree.js
246 - web/opac/common/xml/
247 - web/opac/extras/bbags.js
248 - web/opac/extras/bbags.xml
249 - web/opac/skin/default/js/
250 - web/opac/skin/default/xml/
253 The list of images removed in this change is lengthy, and not
257 Removal of legacy selfcheck interface
258 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
260 The legacy selfcheck interface is no longer included in Evergreen as
263 This interface was formerly located at a URL ending in
264 extras/selfcheck/selfcheck.xml
266 No attempt is made at upgrade time to automatically remove this
269 It is recommended that you remove this interface and its associated
270 configuration after performing an upgrade:
272 (paths relative to Evergreen web root)
274 - opac/extras/selfcheck/selfcheck.css
275 - opac/extras/selfcheck/selfcheck.js
276 - opac/extras/selfcheck/selfcheck.xml
277 - opac/extras/selfcheck/selfcheck_print.css
279 You can also remove the related Apache configuration block starting
283 <LocationMatch .*/selfcheck.xml>
295 Improved reporting of progress during purchase order activation
296 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
297 The progress dialog that is displayed when activating a purchase
298 order now displays more information, particularly during the asset
299 creation phase. It is now also updated in a more linear fashion;
300 making it less likely for it to appear that the activation has
306 ==== "Blanket" Orders
308 "Blanket" orders allow staff to invoice an encumbered amount multiple times,
309 paying off the charge over a period of time. The work flow supported by this
310 development assumes staff does not need to track the individual contents of
311 the order, only the amounts encumbered and invoiced in bulk.
315 . Staff creates PO with a Direct Charge of "Popular Fiction 2015" and
316 a charge type of "Blanket Order".
317 . The amount entered for the charge equals the total amount expected
318 to be charged over the duration of the order.
319 . When a shipment of "Popular Fiction" items arrive, staff creates an
320 invoice from the "Popular Fiction 2015" PO page and enters the amount
321 billed/paid for the received shipment under the "Popular Fiction 2015"
322 charge in the invoice.
323 . When the final shipment arrives, staff select the 'Final invoice
324 for Blanket Order' option on the invoice screen to mark the PO as
325 'received' and drop any remaining encumbrances to $0.
326 .. Alternatively, if the PO needs to be finalized without creating
327 a final invoice, staff can use the new 'Finalize Blanket Order'
328 option on the PO page.
330 ===== New Components/Terminology/Concepts
332 * Invoice Item Types have a new flag called 'blanket', available under
333 Admin -> Server Administration -> Acq -> Invoice Item Types in the
335 * Any direct charge using a 'blanket' item type will create a long-lived
336 charge that can be invoiced multiple times.
337 * Such a charge is considered open until its purchase order is "finalized"
339 * "Finalizing" a PO changes the PO's state to 'received' (assuming there are
340 no pending lineitems on the PO) and fully dis-encumbers all blanket charges
341 on the PO by setting the fund_debit amount to $0 on the original fund_debit
343 * Invoicing a 'blanket' charge does the following under the covers:
344 .. Create an invoice_item to track the payment
345 .. Create a new fund_debit to implement the payment whose amount matches the
347 .. Subtract the invoiced amount from the fund_debit linked to the original
348 'blanket' po_item, thus reducing the amount encumbered on the charge as
349 a whole by the invoiced amount.
350 * A PO can have multiple blanket charges. E.g. you could have a blanket
351 order for "Popular Fiction 2015" and a second charge for "Pop Fiction
352 2015 Taxes" to track / pay taxes over time on a blanket charge.
353 * A PO can have a mix of lineitems, non-blanket charges, and blanket charges.
354 * A 'blanket' Invoice Item Type cannot also be a 'prorate' type, since it's
355 nonsensical. Blanket items are encumbered, whereas prorated items are
356 only paid at invoice time and never encumbered.
368 Examples in Apache configuration for "No Image"
369 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
370 There are now commented out examples for custom images to be used when
371 "no image" is present in the catalog for cover art. The included examples
372 are for small/medium/large jacket image art in the event they are not
373 found by the configured Added Content module.
378 Pre-Expiration A/T Event Definition
379 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
380 A new Action Trigger event definition ("30 Day Account Expiration Courtesy
381 Notice") for sending alerts to users before their accounts are expired has
382 been added. This is intended to give users time to renew their account before
383 they lose access to library services.
388 Improved caching of web server templates
389 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
390 Template Toolkit processors used by Apache are now cached for
391 better performance (by virtue of thereby being able to take advantage
392 of Template Toolkit's internal caching mechanism). In addition, the
393 *compiled* versions of the templates themselves can be cached to
394 provide an additional performance boost.
396 Two Apache virtualhost configuration variables are added to
397 control caching of compiled templates:
399 * `OILSWebCompiledTemplateCache` - specifies location on the
400 web server filesystem to store compiled templates.
401 * `OILSWebTemplateStatTTL` - specifies number of seconds before
402 checking to see if a newer version of a cached template is
405 As a result of the caching changes, it is now necessary for
406 Evergreen administrators to reload Apache to ensure that a change
407 to (say) TPAC templates becomes visible.
417 Display Authority Subject Heading Thesaurus Value
418 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
420 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.
422 *A Library of Congress list of thesaurus values:*
425 * '' = Alternate no attempt to code
426 * a = Library of Congress Subject Headings
427 * b = LC subject headings for children's literature
428 * c = Medical Subject Headings
429 * d = National Agricultural Library subject authority file
430 * k = Canadian Subject Headings
432 * r = Art and Architecture Thesaurus
433 * s = Sears List of Subject Headings
434 * v = Repertoire de vedettes-matiere
436 * | = No attempt to code
441 Importing Statistical Categories
442 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
443 You can now retrieve statistical categories (stat cats) from the MARC
444 record and apply them to the items in Evergreen. When importing or
445 overlaying items through the Vandelay MARC batch import process, edit
446 your Holdings Import Profile to tell Evergreen which subfield contains
447 your stat cat data. That subfield in your MARC records should be
448 formatted like the following:
451 CATEGORY 1|VALUE 1||CATEGORY 2|VALUE 2
454 Notice that the pipe character '|' is used to separate each category
455 from its value, and two pipes separate each pair of category values.
457 If you are overlaying existing copies which already have stat cats
458 attached to them, the overlay process will keep those values unless the
459 incoming copies contain updated values for matching categories.
464 Remove the ‡biblios.net Z39.50 target from seed data
465 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
466 The Z39.50 target at z3950.biblios.net/bibliographic has not worked
467 for years, so its service definition is no longer provided in the
468 seed data for new installations of Evergreen.
470 Users of existing Evergreen systems should consider removing
471 the Z39.50 definition for ‡biblios.net. This can be done from
472 Admin | Server Administration | Z39.50 Servers in the staff
478 SKOS for coded values
479 ^^^^^^^^^^^^^^^^^^^^^
480 Some vocabularies used (or which could be used) for stock
481 record attributes and coded value maps in Evergreen are
482 published on the web using SKOS. The record attributes system
483 can now associate Linked Data URIs with specific attribute
484 values. In particular, seed data supplying URIs for the
485 RDA Content Type, Media Type, and Carrier Type in this release.
487 This is an experimental, "under-the-hood" feature that will be built
488 upon in subsuquent releases.
493 MARC Tag-table Service
494 ^^^^^^^^^^^^^^^^^^^^^^
495 The tag tables for the web staff client MARC editor are
496 now stored in the database rather than a separate XML
497 tooltips file as used by the XUL MARC editor. The tag-table
498 service, which is part of the web staff client sprint 2
499 preview in this release, has the following features:
501 - specifies whether (sub)fields are optional or mandatory
502 - specifies whether (sub)fields are repeatable or not
503 - a coded value map can be associated with a subfield to
504 establish a controlled vocabulary for that subfield
505 - MARC field and subfield definitions can be overridden
506 by institutions further down in the organizational unit
507 hierarchy. This allows, for example, a library to specify
508 definitions for local MARC tags.
509 - values supplied by the tag-table service are used to
510 populate values in context menus in the web staff client
513 The initial seed data for the in-database tag table is
514 derived from the current tooltips XML file.
519 Web staff client cataloging preview
520 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
521 The web staff client now includes additional functionality
522 to support cataloging and item maintenance, including:
525 - the service backing the authority headings chooser now
526 has the ability to filter the browse by subject thesaurus
527 - Z39.50 search and record import
528 - improvements to copy and record bucket functionality
529 - embedding the link checker interface
530 - embedding the MARC batch import/export interface
531 - the web staff volume/copy editor
533 Nearly all of the cataloging functionality available in the XUL
534 staff client is now present in the web staff client with the
535 exception of printing spine labels. Nonetheless, the web staff
536 client remains a preview and is not recommended for production use.
546 Conditional Negative Balances
547 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
548 Evergreen sites will now have more control over whether a negative balance can
549 be applied to a user's billing record and when that negative balance can be
550 applied. Through a series of Library Settings, a site can prohibit negative
551 balances on bills or can allow those negative balances to be applied for a
552 specific period of time after a lost or overdue bill is charged to the user.
553 Sites can set a default for all types of bills or can apply distinct settings
554 for lost bills and for overdue fines. The more specific settings will override
557 Sites that opt to allow negative balances for a specific period of time must
558 1) enable the relevant "prohibit negative balances" setting(s) and 2) specify
559 the time period in the relevant Negative Balance Interval setting(s).
561 In addition to the new library settings, the system now has a new account
562 adjustment payment type. This payment type will be utilized for libraries
563 prohibiting negative balances to replace the previous voiding behavior that
564 caused the negative balances to occur. The account adjustment payment type will
565 also be used for all libraries, regardless of the state of negative balance
566 settings, in cases where overdue fines are adjusted when an overdue item is
569 An _Adjust to Zero_ option has been added to the bills interface of the patron
570 record. This option will always adjust the selected bill to a zero balance.
571 It can also be used to easily clear a negative balance from the patron's
572 record. A user must have the new ADJUST_BILLS permission to see and use this
575 This new feature also changes the behavior for the client option to void a bill
576 from the patron record. If a user does not have the VOID_BILLING permission, the
577 option to void bills will be hidden in the bills interface and in the Full
578 Details view of a specific bill.
580 To truly remove the ability to produce negative balances on a transaction,
581 administrators need to 1) enable the relevant setting in the Library Settings
582 Editor and 2) remove the VOID_BILLING permission from staff accounts since
583 manual voiding will continue to produce negative balances.
587 * Negative Balance Interval (Default) (bill.negative_balance_interval_default)
588 * Negative Balance Interval for Lost (bill.negative_balance_interval_on_lost) -
589 * Negative Balance Interval for Overdues (bill.negative_balance_interval_on_overdues
590 * Prohibit negative balance on bills (Default) (bill.prohibit_negative_balance_default)
591 * Prohibit negative balance on bills for lost materials (bill.prohibit_negative_balance_on_lost)
592 * Prohibit negative balance on bills for overdue materials (bill.prohibit_negative_balance_on_overdues)
601 Selfcheck Inactivity Warning
602 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
604 The Selfcheck interface now warns patrons when they are about to be
605 logged out due to inactivity 20 seconds prior to logging them out.
607 The inactivity timeout is also reset with each checkout to avoid timeouts
608 while checking out lots of items.
613 User Registration Includes Inactive Accounts in Dupe Search
614 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
615 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.
625 Link in catalog to clear Added Content cache
626 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
627 On the catalog's record summary page, there is now a link for staff that
628 allow them to forcibly clear the cache for the Added Content for that
629 record. This is helpful if the Added Content retrieved the wrong
630 cover jacket art, summary, etc. and caches the wrong result.
635 Disable Google Analytics in Staff Client
636 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
637 In the staff client interface, Google Analytics for the web catalog is
638 now disabled by default. This was a preventive measure to reduce the
639 potential risks for leaking patron information.
644 Move Acquisitions Admin Menu
645 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
646 In the staff client interface, the Acquisitions Administration menu is
647 now directly accessible from the main "Admin" menu instead of
648 living under "Server Administration". It has also been renamed as "Acquisitions
659 Account Expiration Date in My Account
660 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
661 The Account Expiration Date has been added to the catalog's My Account display
662 on the main Account Summary page and the Account Preferences page. This should
663 help patrons with figuring out when their accounts are due to expire before
664 they actually expire.
668 Change to Available Copies Display
669 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
670 The _Show_ link in the available copies area of the record summary will now
671 display for any org unit that owns a copy of a particular title, even if all
672 those copies are unavailable. The _Show_ link will not display if a) the copy
673 display is already scoped to that org unit or b) the org unit does not own
676 The language has also been changed to read "x of y copies available at z
683 Column sorting in circulation screens
684 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
686 Sorting of selected columns is now available in the *Items Checked Out*, *Check Out History*,
689 * Clicking on the appropriate column heads now sorts the contents from
690 ``ascending'' to ``descending'' to ``no sort''. (The ``no sort'' restores the
691 original list as presented in the screen.)
693 * The sort indicator (an up or down arrow) is placed to the right
694 of the column head, as appropriate.
696 * The combined *Title/Author* column in the *Items Checked Out* screen is now separated into two
697 independently sortable columns (Title and Author).
699 * Title sorting is done with the non-filing characters (leading ``the'', ``a'',
700 ``an'', and other langugage equivalents) removed. The leading articles are rendered in
701 a smaller font, so as to keep the main entry prominent. In
702 addition to the non-filing characters removed for the sort, leading
703 non-alphanumeric characters are ignored in the sort.
708 New bib source variable for catalog customization
709 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
710 For bibliographic records, there is a "bib source" that can be
711 associated with every record. This source is now available as a
712 variable that can be used behind the scenes when customizing
713 the online catalog. The new bib source variables do not present
714 themselves in the catalog display by default.
719 New class attribute for e-resource links
720 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
721 In the catalog, links to electronic resources now have a link class
722 attribute of "uri_link" to make them easier to customize or build
723 additional services upon.
729 Removal of deprecated "JSPAC" interface
730 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
732 The deprecated Javascript OPAC interface known as "JSPAC" is no
733 longer included in Evergreen as of this release.
735 With the understanding that local sites may have made use of
736 existing parts of the old JSPAC interface -- especially images and
737 CSS -- no attempt is made at upgrade time to automatically remove
738 the existing files from disk.
740 When upgrading, you may wish to remove "index.xml" from your Apache
741 DirectoryIndex directives.
743 The following directories, xml, js, and css files were formerly part
744 of JSPAC, and you may be able to safely remove them from your system
745 after verifying that they and their contents are no longer required:
747 - web/opac/common/css/
748 - web/opac/common/js/dtree.js
749 - web/opac/common/xml/
750 - web/opac/extras/bbags.js
751 - web/opac/extras/bbags.xml
752 - web/opac/skin/default/js/
753 - web/opac/skin/default/xml/
756 The list of images removed in this change is lengthy, and not
762 Removal of legacy selfcheck interface
763 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
765 The legacy selfcheck interface is no longer included in Evergreen as
768 This interface was formerly located at a URL ending in
769 extras/selfcheck/selfcheck.xml
771 No attempt is made at upgrade time to automatically remove this
774 It is recommended that you remove this interface and its associated
775 configuration after performing an upgrade:
777 (paths relative to Evergreen web root)
779 - opac/extras/selfcheck/selfcheck.css
780 - opac/extras/selfcheck/selfcheck.js
781 - opac/extras/selfcheck/selfcheck.xml
782 - opac/extras/selfcheck/selfcheck_print.css
784 You can also remove the related Apache configuration block starting
788 <LocationMatch .*/selfcheck.xml>
795 The Evergreen project would like to acknowledge the following
796 organizations who commissioned developments in this release of
799 * Georgia Public Library Service
800 * Grand Rapids Public Library
801 * Kenton County Public Library
802 * King County Library System
803 * Massachusetts Library Network Cooperative
806 * Pennsylvania Integrated Library System
808 We would also like to thank the following individuals who contributed
809 code, documentation patches and tests to this release of Evergreen:
841 We also thank the following organizations whose employees contributed
844 * Anderson County Library
845 * Berklee College of Music
847 * British Columbia Libraries Cooperative
850 * Central/Western Massachusetts Automated Resource Sharing
851 * Emerald Data Networks, Inc.
852 * Equinox Software, Inc.
853 * Georgia Public Library Service
854 * Grand Rapids Public Library
855 * Indiana State Library
856 * King County Library System
857 * Lake Agassiz Regional Library
858 * Laurentian University
859 * Linn-Benton Community College
860 * Massachusetts Library Network Cooperative
861 * Merrimack Valley Library Consortium
863 * Northwest Regional Library System
865 * Traverse Area District Library
867 We regret any omissions. If a contributor has been inadvertantly
868 missed, please open a bug at http://bugs.launchpad.net/evergreen/