1 Evergreen 2.9 Release Notes
2 ===========================
8 This release contains several bugfixes improving on Evergreen 2.9.3
10 * Fixes a bug where phrase searching in the catalog failed when the phrase
11 started or ended with puntuation.
12 * Silences unnecessary warnings emitted for libraries using extending grace
14 * Removes support for Debian Squeeze now that its long-term support period
19 We would like to thank the following individuals who contributed
20 code and documentation patches to the 2.9.4 point release of Evergreen:
27 We also thank the following organizations whose employees contributed
30 * Berklee College of Music
31 * Equinox Software, Inc.
37 This release contains several bugfixes improving on Evergreen 2.9.2.
41 * Adds EDI Cancel Code 85 to the acquisitions cancel reason table.
42 * Fixes an issue where the "Expand All" button in selection lists was not
44 * Fixes an issue where deletable reasons from the acquisitions Cancel Reasons
45 table could not be deleted.
49 * Improves sorting in holdings maintenance so that copies sort first by parts
54 * Fixes an issue where the wrong last billing type and last billing note were
55 displaying for some transactions.
56 * Now calculates credit payments as integers to avoid rounding errors with
57 large sets of small billings.
58 * Fixes an issue in the patron record where staff was unable to retrieve the
59 Message Center interface after visiting the Triggered Events page and vice
61 * Now displays the short version of a title on the Place Holds screen when
62 placing metabib holds to reduce instances where the wrong title/format
67 * Fixes an issue where detailed search results showed parts for items that
69 * Changes the e-mail address check on password reset requests so that it is no
70 longer case sensitive.
71 * Fixes a problem where users were unable to navigate through multiple pages of
73 * Removes undefined values from ISBN and ISSN arrays to prevent empty requests
74 from being sent to added content providers.
75 * Fixes an issue where the kids catalog was not displaying title information
76 after hold placement or after adding a title to a list.
77 * Corrects the kids catalog holds notification default preferences to allow for
78 SMS text messaging options.
83 * Modifies the way SIP2 clients parse dates so that a patron's date of birth is
85 * Fixes an issue where the Selfcheck fines receipt templated printed all open
86 billable transactions, regardless of whether it had bills associated with it.
87 * Fixes an issue that prevented Selfcheck's "Print List" for holds view from
92 We would like to thank the following individuals who contributed
93 code and documentation patches to the 2.9.3 point release of Evergreen:
109 We also thank the following organizations whose employees contributed
113 * Equinox Software, Inc.
115 * Georgia Public Library Service
116 * King County Library System
117 * Lake Agassiz Regional Library
118 * Merrimack Valley Library Consortium
120 * Northwest Regional Library System
124 This release contains several bugfixes improving on Evergreen 2.9.1.
126 Acquisitions / Cataloging
127 ~~~~~~~~~~~~~~~~~~~~~~~~~
128 * Allows the Z39.50 itnerface and the acquisitions MARC Federated Search
129 interface to search the UPC index of the local catalog if Z39.50 is configured
130 to search that field.
131 * Fixes an issue where spaces in a PO name cause the system to improperly
132 process EDI response messages.
136 * Fixes a problem where the balance owed was miscalculated when a row
137 was deleted from money.billing.
138 * Fixes an issue where credit card payments made via PayflowPro failed because
139 Evergreen does not install the PayflowPro module by default.
140 * Changes credit card payment behavior so that the patron's billing address will
141 be read when the patron has no mailing address. If all address fields are
142 properly set by the API caller except the country and the
143 patron has no addresses, the system will attempt to determine the country from
144 library settings. If insufficient address data is provided, the system will
145 return an invalid params Event.
146 * Modifies the reasons for various void/adjust events to more accurately reflect
147 the reason why a fine/fee was removed from a patron's record.
151 * Fixes an issue where the reset password link was displaying even on systems
152 that had disabled the ability to reset passwords.
153 * Fixes an issue where the journal type search did not work when entering it as
154 the second or third input on the advanced search screen.
155 * Fixes an issue where catalog translations were broken by creating separate
156 directories for the catalog and web staff client translations.
160 * Changes marc_export to only print "waiting for input" when running
165 We would like to thank the following individuals who contributed
166 code and documentation patches to the 2.9.2 point release of Evergreen:
176 We also thank the following organizations whose employees contributed
180 * Equinox Software, Inc.
181 * King County Library System
182 * Merrimack Valley Library Consortium
187 This release contains several bugfixes improving on Evergreen 2.9.0.
191 * Protects the stock acquisitions cancel reasons from deletion since they
192 are required to properly handle EDI order responses.
193 * Changes the copy location dropdown so that users can view and select copy
194 locations owned outside the workstation branch if they have permission to do so.
195 This fix also adds the copy location's owning org unit to the display.
199 * Allows use of more special characters, including - and +, when
200 entering a library's main email address in the Organizational Units
202 * Fixes an issue where marc_export attempts to call a non-existent field
203 on MARC::Record if an error occurs while exporting authority records.
207 * Fixes the mapping between copies and the target part when using "Merge
208 Selected" in the Monographic Parts interface.
209 * Fixes an issue with the horizontal scrollbar bar in the MARC import
210 queue inspector so the focus no longer jumps to the top of the screen
211 when attempting to use the scrollbar.
212 * Hides the staff-client saved searches header from screen readers when
213 using the public catalog in non-staff mode.
217 * When placing a hold via the staff client and clicking Advanced Hold
218 Options, fixes an issue where the barcode field populated with the
219 staff member's barcode.
220 * Fixes an issue where some holds with a higher proximity were
221 preferred over holds with a lower proximity because the list of
222 proximities of elgible copies was sorting ASCIIbetically instead of
224 * Adds a delete flag for monographic parts, fixes staff client errors that
225 were previously caused by deleted parts, and cancels any holds attached to
227 * Fixes an internal error that appeared when trying to renew an item on the
228 booking resource list through the public catalog. Users will now get a message
229 saying they do not have permission to renew the item.
234 * Fixes an issue where unclosed phrase searches returned zero results and
235 tied up the open-ils.storage process.
236 * Fixes an issue where phrase searches were ignoring modifiers used in relevance
237 ranking, leading to poorly-ranked results.
238 * Fixes an issue where parameters weren't properly maintained when
239 searching by copy location group.
243 * Adds support for UTF-8 in the Reports interface.
247 We would like to thank the following individuals who contributed
248 code and documentation patches to the 2.9.1 point release of Evergreen:
267 We also thank the following organizations whose employees contributed
270 * Berklee College of Music
272 * British Columbia Libraries Cooperative
274 * Emerald Data Networks, Inc.
275 * Equinox Software, Inc.
276 * Georgia Public Library Service
277 * Lake Agassiz Regional Library
278 * Laurentian University
279 * Massachusetts Library Network Cooperative
280 * Merrimack Valley Library Consortium
282 * Northwest Regional Library System
283 * Pohjois-Karjalan Tietotekniikkakeskus Oy
284 * Rodgers Memorial Library
286 We regret any omissions. If a contributor has been inadvertantly
287 missed, please open a bug at http://bugs.launchpad.net/evergreen/
293 Remove Script-Based Circulation Configuration
294 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
296 Evergreen no longer supports script-based circulation policies. All
297 policies must now be managed within the Local Administration ->
298 Circulation Policies, Hold Policies, and related interfaces.
301 Remove open-ils.penalty service
302 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
304 Evergreen no longer uses the 'open-ils.penalty' service. It is safe
305 (though not required) to remove the following XML chunks from
306 /openils/conf/opensrf.xml after stopping services.
309 ----------------------------------------------------------------------------
311 <!-- first element -->
314 <keepalive>3</keepalive>
315 <stateless>1</stateless>
316 <language>perl</language>
317 <implementation>OpenILS::Application::Penalty</implementation>
318 <max_requests>99</max_requests>
320 <max_requests>1000</max_requests>
321 <unix_log>open-ils.penalty_unix.log</unix_log>
322 <unix_sock>open-ils.penalty_unix.sock</unix_sock>
323 <unix_pid>open-ils.penalty_unix.pid</unix_pid>
324 <min_children>1</min_children>
325 <max_children>15</max_children>
326 <min_spare_children>1</min_spare_children>
327 <max_spare_children>5</max_spare_children>
330 <patron_penalty>penalty/patron_penalty.js</patron_penalty>
331 <script_path>LIBDIR/javascript</script_path>
332 <script_path>LOCALSTATEDIR</script_path>
333 <script_path>LOCALSTATEDIR/catalog</script_path>
337 <!-- second element -->
339 <appname>open-ils.penalty</appname>
340 ----------------------------------------------------------------------------
343 Removal of deprecated "JSPAC" interface
344 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
346 The deprecated Javascript OPAC interface known as "JSPAC" is no
347 longer included in Evergreen as of this release.
349 With the understanding that local sites may have made use of
350 existing parts of the old JSPAC interface -- especially images and
351 CSS -- no attempt is made at upgrade time to automatically remove
352 the existing files from disk.
354 When upgrading, you may wish to remove "index.xml" from your Apache
355 DirectoryIndex directives.
357 The following directories, xml, js, and css files were formerly part
358 of JSPAC, and you may be able to safely remove them from your system
359 after verifying that they and their contents are no longer required:
361 - web/opac/common/css/
362 - web/opac/common/js/dtree.js
363 - web/opac/common/xml/
364 - web/opac/extras/bbags.js
365 - web/opac/extras/bbags.xml
366 - web/opac/skin/default/js/
367 - web/opac/skin/default/xml/
370 The list of images removed in this change is lengthy, and not
374 Removal of legacy selfcheck interface
375 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
377 The legacy selfcheck interface is no longer included in Evergreen as
380 This interface was formerly located at a URL ending in
381 extras/selfcheck/selfcheck.xml
383 No attempt is made at upgrade time to automatically remove this
386 It is recommended that you remove this interface and its associated
387 configuration after performing an upgrade:
389 (paths relative to Evergreen web root)
391 - opac/extras/selfcheck/selfcheck.css
392 - opac/extras/selfcheck/selfcheck.js
393 - opac/extras/selfcheck/selfcheck.xml
394 - opac/extras/selfcheck/selfcheck_print.css
396 You can also remove the related Apache configuration block starting
400 <LocationMatch .*/selfcheck.xml>
412 Improved reporting of progress during purchase order activation
413 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
414 The progress dialog that is displayed when activating a purchase
415 order now displays more information, particularly during the asset
416 creation phase. It is now also updated in a more linear fashion;
417 making it less likely for it to appear that the activation has
423 ==== "Blanket" Orders
425 "Blanket" orders allow staff to invoice an encumbered amount multiple times,
426 paying off the charge over a period of time. The work flow supported by this
427 development assumes staff does not need to track the individual contents of
428 the order, only the amounts encumbered and invoiced in bulk.
432 . Staff creates PO with a Direct Charge of "Popular Fiction 2015" and
433 a charge type of "Blanket Order".
434 . The amount entered for the charge equals the total amount expected
435 to be charged over the duration of the order.
436 . When a shipment of "Popular Fiction" items arrive, staff creates an
437 invoice from the "Popular Fiction 2015" PO page and enters the amount
438 billed/paid for the received shipment under the "Popular Fiction 2015"
439 charge in the invoice.
440 . When the final shipment arrives, staff select the 'Final invoice
441 for Blanket Order' option on the invoice screen to mark the PO as
442 'received' and drop any remaining encumbrances to $0.
443 .. Alternatively, if the PO needs to be finalized without creating
444 a final invoice, staff can use the new 'Finalize Blanket Order'
445 option on the PO page.
447 ===== New Components/Terminology/Concepts
449 * Invoice Item Types have a new flag called 'blanket', available under
450 Admin -> Server Administration -> Acq -> Invoice Item Types in the
452 * Any direct charge using a 'blanket' item type will create a long-lived
453 charge that can be invoiced multiple times.
454 * Such a charge is considered open until its purchase order is "finalized"
456 * "Finalizing" a PO changes the PO's state to 'received' (assuming there are
457 no pending lineitems on the PO) and fully dis-encumbers all blanket charges
458 on the PO by setting the fund_debit amount to $0 on the original fund_debit
460 * Invoicing a 'blanket' charge does the following under the covers:
461 .. Create an invoice_item to track the payment
462 .. Create a new fund_debit to implement the payment whose amount matches the
464 .. Subtract the invoiced amount from the fund_debit linked to the original
465 'blanket' po_item, thus reducing the amount encumbered on the charge as
466 a whole by the invoiced amount.
467 * A PO can have multiple blanket charges. E.g. you could have a blanket
468 order for "Popular Fiction 2015" and a second charge for "Pop Fiction
469 2015 Taxes" to track / pay taxes over time on a blanket charge.
470 * A PO can have a mix of lineitems, non-blanket charges, and blanket charges.
471 * A 'blanket' Invoice Item Type cannot also be a 'prorate' type, since it's
472 nonsensical. Blanket items are encumbered, whereas prorated items are
473 only paid at invoice time and never encumbered.
485 Examples in Apache configuration for "No Image"
486 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
487 There are now commented out examples for custom images to be used when
488 "no image" is present in the catalog for cover art. The included examples
489 are for small/medium/large jacket image art in the event they are not
490 found by the configured Added Content module.
495 Pre-Expiration A/T Event Definition
496 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
497 A new Action Trigger event definition ("30 Day Account Expiration Courtesy
498 Notice") for sending alerts to users before their accounts are expired has
499 been added. This is intended to give users time to renew their account before
500 they lose access to library services.
505 Improved caching of web server templates
506 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
507 Template Toolkit processors used by Apache are now cached for
508 better performance (by virtue of thereby being able to take advantage
509 of Template Toolkit's internal caching mechanism). In addition, the
510 *compiled* versions of the templates themselves can be cached to
511 provide an additional performance boost.
513 Two Apache virtualhost configuration variables are added to
514 control caching of compiled templates:
516 * `OILSWebCompiledTemplateCache` - specifies location on the
517 web server filesystem to store compiled templates.
518 * `OILSWebTemplateStatTTL` - specifies number of seconds before
519 checking to see if a newer version of a cached template is
522 As a result of the caching changes, it is now necessary for
523 Evergreen administrators to reload Apache to ensure that a change
524 to (say) TPAC templates becomes visible.
534 Display Authority Subject Heading Thesaurus Value
535 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
537 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.
539 *A Library of Congress list of thesaurus values:*
542 * '' = Alternate no attempt to code
543 * a = Library of Congress Subject Headings
544 * b = LC subject headings for children's literature
545 * c = Medical Subject Headings
546 * d = National Agricultural Library subject authority file
547 * k = Canadian Subject Headings
549 * r = Art and Architecture Thesaurus
550 * s = Sears List of Subject Headings
551 * v = Repertoire de vedettes-matiere
553 * | = No attempt to code
558 Importing Statistical Categories
559 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
560 You can now retrieve statistical categories (stat cats) from the MARC
561 record and apply them to the items in Evergreen. When importing or
562 overlaying items through the Vandelay MARC batch import process, edit
563 your Holdings Import Profile to tell Evergreen which subfield contains
564 your stat cat data. That subfield in your MARC records should be
565 formatted like the following:
568 CATEGORY 1|VALUE 1||CATEGORY 2|VALUE 2
571 Notice that the pipe character '|' is used to separate each category
572 from its value, and two pipes separate each pair of category values.
574 If you are overlaying existing copies which already have stat cats
575 attached to them, the overlay process will keep those values unless the
576 incoming copies contain updated values for matching categories.
581 Remove the ‡biblios.net Z39.50 target from seed data
582 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
583 The Z39.50 target at z3950.biblios.net/bibliographic has not worked
584 for years, so its service definition is no longer provided in the
585 seed data for new installations of Evergreen.
587 Users of existing Evergreen systems should consider removing
588 the Z39.50 definition for ‡biblios.net. This can be done from
589 Admin | Server Administration | Z39.50 Servers in the staff
595 SKOS for coded values
596 ^^^^^^^^^^^^^^^^^^^^^
597 Some vocabularies used (or which could be used) for stock
598 record attributes and coded value maps in Evergreen are
599 published on the web using SKOS. The record attributes system
600 can now associate Linked Data URIs with specific attribute
601 values. In particular, seed data supplying URIs for the
602 RDA Content Type, Media Type, and Carrier Type in this release.
604 This is an experimental, "under-the-hood" feature that will be built
605 upon in subsuquent releases.
610 MARC Tag-table Service
611 ^^^^^^^^^^^^^^^^^^^^^^
612 The tag tables for the web staff client MARC editor are
613 now stored in the database rather than a separate XML
614 tooltips file as used by the XUL MARC editor. The tag-table
615 service, which is part of the web staff client sprint 2
616 preview in this release, has the following features:
618 - specifies whether (sub)fields are optional or mandatory
619 - specifies whether (sub)fields are repeatable or not
620 - a coded value map can be associated with a subfield to
621 establish a controlled vocabulary for that subfield
622 - MARC field and subfield definitions can be overridden
623 by institutions further down in the organizational unit
624 hierarchy. This allows, for example, a library to specify
625 definitions for local MARC tags.
626 - values supplied by the tag-table service are used to
627 populate values in context menus in the web staff client
630 The initial seed data for the in-database tag table is
631 derived from the current tooltips XML file.
636 Web staff client cataloging preview
637 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
638 The web staff client now includes additional functionality
639 to support cataloging and item maintenance, including:
642 - the service backing the authority headings chooser now
643 has the ability to filter the browse by subject thesaurus
644 - Z39.50 search and record import
645 - improvements to copy and record bucket functionality
646 - embedding the link checker interface
647 - embedding the MARC batch import/export interface
648 - the web staff volume/copy editor
650 Nearly all of the cataloging functionality available in the XUL
651 staff client is now present in the web staff client with the
652 exception of printing spine labels. Nonetheless, the web staff
653 client remains a preview and is not recommended for production use.
663 Conditional Negative Balances
664 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
665 Evergreen sites will now have more control over whether a negative balance can
666 be applied to a user's billing record and when that negative balance can be
667 applied. Through a series of Library Settings, a site can prohibit negative
668 balances on bills or can allow those negative balances to be applied for a
669 specific period of time after a lost or overdue bill is charged to the user.
670 Sites can set a default for all types of bills or can apply distinct settings
671 for lost bills and for overdue fines. The more specific settings will override
674 Sites that opt to allow negative balances for a specific period of time must
675 1) enable the relevant "prohibit negative balances" setting(s) and 2) specify
676 the time period in the relevant Negative Balance Interval setting(s).
678 In addition to the new library settings, the system now has a new account
679 adjustment payment type. This payment type will be utilized for libraries
680 prohibiting negative balances to replace the previous voiding behavior that
681 caused the negative balances to occur. The account adjustment payment type will
682 also be used for all libraries, regardless of the state of negative balance
683 settings, in cases where overdue fines are adjusted when an overdue item is
686 An _Adjust to Zero_ option has been added to the bills interface of the patron
687 record. This option will always adjust the selected bill to a zero balance.
688 It can also be used to easily clear a negative balance from the patron's
689 record. A user must have the new ADJUST_BILLS permission to see and use this
692 This new feature also changes the behavior for the client option to void a bill
693 from the patron record. If a user does not have the VOID_BILLING permission, the
694 option to void bills will be hidden in the bills interface and in the Full
695 Details view of a specific bill.
697 To truly remove the ability to produce negative balances on a transaction,
698 administrators need to 1) enable the relevant setting in the Library Settings
699 Editor and 2) remove the VOID_BILLING permission from staff accounts since
700 manual voiding will continue to produce negative balances.
704 * Negative Balance Interval (Default) (bill.negative_balance_interval_default)
705 * Negative Balance Interval for Lost (bill.negative_balance_interval_on_lost) -
706 * Negative Balance Interval for Overdues (bill.negative_balance_interval_on_overdues
707 * Prohibit negative balance on bills (Default) (bill.prohibit_negative_balance_default)
708 * Prohibit negative balance on bills for lost materials (bill.prohibit_negative_balance_on_lost)
709 * Prohibit negative balance on bills for overdue materials (bill.prohibit_negative_balance_on_overdues)
718 Selfcheck Inactivity Warning
719 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
721 The Selfcheck interface now warns patrons when they are about to be
722 logged out due to inactivity 20 seconds prior to logging them out.
724 The inactivity timeout is also reset with each checkout to avoid timeouts
725 while checking out lots of items.
730 User Registration Includes Inactive Accounts in Dupe Search
731 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
732 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.
742 Link in catalog to clear Added Content cache
743 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
744 On the catalog's record summary page, there is now a link for staff that
745 allow them to forcibly clear the cache for the Added Content for that
746 record. This is helpful if the Added Content retrieved the wrong
747 cover jacket art, summary, etc. and caches the wrong result.
752 Disable Google Analytics in Staff Client
753 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
754 In the staff client interface, Google Analytics for the web catalog is
755 now disabled by default. This was a preventive measure to reduce the
756 potential risks for leaking patron information.
761 Move Acquisitions Admin Menu
762 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
763 In the staff client interface, the Acquisitions Administration menu is
764 now directly accessible from the main "Admin" menu instead of
765 living under "Server Administration". It has also been renamed as "Acquisitions
776 Account Expiration Date in My Account
777 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
778 The Account Expiration Date has been added to the catalog's My Account display
779 on the main Account Summary page and the Account Preferences page. This should
780 help patrons with figuring out when their accounts are due to expire before
781 they actually expire.
785 Change to Available Copies Display
786 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
787 The _Show_ link in the available copies area of the record summary will now
788 display for any org unit that owns a copy of a particular title, even if all
789 those copies are unavailable. The _Show_ link will not display if a) the copy
790 display is already scoped to that org unit or b) the org unit does not own
793 The language has also been changed to read "x of y copies available at z
800 Column sorting in circulation screens
801 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
803 Sorting of selected columns is now available in the *Items Checked Out*, *Check Out History*,
806 * Clicking on the appropriate column heads now sorts the contents from
807 ``ascending'' to ``descending'' to ``no sort''. (The ``no sort'' restores the
808 original list as presented in the screen.)
810 * The sort indicator (an up or down arrow) is placed to the right
811 of the column head, as appropriate.
813 * The combined *Title/Author* column in the *Items Checked Out* screen is now separated into two
814 independently sortable columns (Title and Author).
816 * Title sorting is done with the non-filing characters (leading ``the'', ``a'',
817 ``an'', and other langugage equivalents) removed. The leading articles are rendered in
818 a smaller font, so as to keep the main entry prominent. In
819 addition to the non-filing characters removed for the sort, leading
820 non-alphanumeric characters are ignored in the sort.
825 New bib source variable for catalog customization
826 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
827 For bibliographic records, there is a "bib source" that can be
828 associated with every record. This source is now available as a
829 variable that can be used behind the scenes when customizing
830 the online catalog. The new bib source variables do not present
831 themselves in the catalog display by default.
836 New class attribute for e-resource links
837 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
838 In the catalog, links to electronic resources now have a link class
839 attribute of "uri_link" to make them easier to customize or build
840 additional services upon.
846 Removal of deprecated "JSPAC" interface
847 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
849 The deprecated Javascript OPAC interface known as "JSPAC" is no
850 longer included in Evergreen as of this release.
852 With the understanding that local sites may have made use of
853 existing parts of the old JSPAC interface -- especially images and
854 CSS -- no attempt is made at upgrade time to automatically remove
855 the existing files from disk.
857 When upgrading, you may wish to remove "index.xml" from your Apache
858 DirectoryIndex directives.
860 The following directories, xml, js, and css files were formerly part
861 of JSPAC, and you may be able to safely remove them from your system
862 after verifying that they and their contents are no longer required:
864 - web/opac/common/css/
865 - web/opac/common/js/dtree.js
866 - web/opac/common/xml/
867 - web/opac/extras/bbags.js
868 - web/opac/extras/bbags.xml
869 - web/opac/skin/default/js/
870 - web/opac/skin/default/xml/
873 The list of images removed in this change is lengthy, and not
879 Removal of legacy selfcheck interface
880 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
882 The legacy selfcheck interface is no longer included in Evergreen as
885 This interface was formerly located at a URL ending in
886 extras/selfcheck/selfcheck.xml
888 No attempt is made at upgrade time to automatically remove this
891 It is recommended that you remove this interface and its associated
892 configuration after performing an upgrade:
894 (paths relative to Evergreen web root)
896 - opac/extras/selfcheck/selfcheck.css
897 - opac/extras/selfcheck/selfcheck.js
898 - opac/extras/selfcheck/selfcheck.xml
899 - opac/extras/selfcheck/selfcheck_print.css
901 You can also remove the related Apache configuration block starting
905 <LocationMatch .*/selfcheck.xml>
912 The Evergreen project would like to acknowledge the following
913 organizations who commissioned developments in this release of
916 * Georgia Public Library Service
917 * Grand Rapids Public Library
918 * Kenton County Public Library
919 * King County Library System
920 * Massachusetts Library Network Cooperative
923 * Pennsylvania Integrated Library System
925 We would also like to thank the following individuals who contributed
926 code, documentation patches and tests to this release of Evergreen:
958 We also thank the following organizations whose employees contributed
961 * Anderson County Library
962 * Berklee College of Music
964 * British Columbia Libraries Cooperative
967 * Central/Western Massachusetts Automated Resource Sharing
968 * Emerald Data Networks, Inc.
969 * Equinox Software, Inc.
970 * Georgia Public Library Service
971 * Grand Rapids Public Library
972 * Indiana State Library
973 * King County Library System
974 * Lake Agassiz Regional Library
975 * Laurentian University
976 * Linn-Benton Community College
977 * Massachusetts Library Network Cooperative
978 * Merrimack Valley Library Consortium
980 * Northwest Regional Library System
982 * Traverse Area District Library
984 We regret any omissions. If a contributor has been inadvertantly
985 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / Evergreen.git / blob