1 Evergreen 2_9 Release Notes
2 ===========================
9 Remove Script-Based Circulation Configuration
10 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12 Evergreen no longer supports script-based circulation policies. All
13 policies must now be managed within the Local Administration ->
14 Circulation Policies, Hold Policies, and related interfaces.
17 Remove open-ils.penalty service
18 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 Evergreen no longer uses the 'open-ils.penalty' service. It is safe
21 (though not required) to remove the following XML chunks from
22 /openils/conf/opensrf.xml after stopping services.
25 ----------------------------------------------------------------------------
27 <!-- first element -->
30 <keepalive>3</keepalive>
31 <stateless>1</stateless>
32 <language>perl</language>
33 <implementation>OpenILS::Application::Penalty</implementation>
34 <max_requests>99</max_requests>
36 <max_requests>1000</max_requests>
37 <unix_log>open-ils.penalty_unix.log</unix_log>
38 <unix_sock>open-ils.penalty_unix.sock</unix_sock>
39 <unix_pid>open-ils.penalty_unix.pid</unix_pid>
40 <min_children>1</min_children>
41 <max_children>15</max_children>
42 <min_spare_children>1</min_spare_children>
43 <max_spare_children>5</max_spare_children>
46 <patron_penalty>penalty/patron_penalty.js</patron_penalty>
47 <script_path>LIBDIR/javascript</script_path>
48 <script_path>LOCALSTATEDIR</script_path>
49 <script_path>LOCALSTATEDIR/catalog</script_path>
53 <!-- second element -->
55 <appname>open-ils.penalty</appname>
56 ----------------------------------------------------------------------------
59 Removal of deprecated "JSPAC" interface
60 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
62 The deprecated Javascript OPAC interface known as "JSPAC" is no
63 longer included in Evergreen as of this release.
65 With the understanding that local sites may have made use of
66 existing parts of the old JSPAC interface -- especially images and
67 CSS -- no attempt is made at upgrade time to automatically remove
68 the existing files from disk.
70 When upgrading, you may wish to remove "index.xml" from your Apache
71 DirectoryIndex directives.
73 The following directories, xml, js, and css files were formerly part
74 of JSPAC, and you may be able to safely remove them from your system
75 after verifying that they and their contents are no longer required:
77 - web/opac/common/css/
78 - web/opac/common/js/dtree.js
79 - web/opac/common/xml/
80 - web/opac/extras/bbags.js
81 - web/opac/extras/bbags.xml
82 - web/opac/skin/default/js/
83 - web/opac/skin/default/xml/
86 The list of images removed in this change is lengthy, and not
90 Removal of legacy selfcheck interface
91 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
93 The legacy selfcheck interface is no longer included in Evergreen as
96 This interface was formerly located at a URL ending in
97 extras/selfcheck/selfcheck.xml
99 No attempt is made at upgrade time to automatically remove this
102 It is recommended that you remove this interface and its associated
103 configuration after performing an upgrade:
105 (paths relative to Evergreen web root)
107 - opac/extras/selfcheck/selfcheck.css
108 - opac/extras/selfcheck/selfcheck.js
109 - opac/extras/selfcheck/selfcheck.xml
110 - opac/extras/selfcheck/selfcheck_print.css
112 You can also remove the related Apache configuration block starting
116 <LocationMatch .*/selfcheck.xml>
130 Improved reporting of progress during purchase order activation
131 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
132 The progress dialog that is displayed when activating a purchase
133 order now displays more information, particularly during the asset
134 creation phase. It is now also updated in a more linear fashion;
135 making it less likely for it to appear that the activation has
141 ==== "Blanket" Orders
143 "Blanket" orders allow staff to invoice an encumbered amount multiple times,
144 paying off the charge over a period of time. The work flow supported by this
145 development assumes staff does not need to track the individual contents of
146 the order, only the amounts encumbered and invoiced in bulk.
150 . Staff creates PO with a Direct Charge of "Popular Fiction 2015" and
151 a charge type of "Blanket Order".
152 . The amount entered for the charge equals the total amount expected
153 to be charged over the duration of the order.
154 . When a shipment of "Popular Fiction" items arrive, staff creates an
155 invoice from the "Popular Fiction 2015" PO page and enters the amount
156 billed/paid for the received shipment under the "Popular Fiction 2015"
157 charge in the invoice.
158 . When the final shipment arrives, staff select the 'Final invoice
159 for Blanket Order' option on the invoice screen to mark the PO as
160 'received' and drop any remaining encumbrances to $0.
161 .. Alternatively, if the PO needs to be finalized without creating
162 a final invoice, staff can use the new 'Finalize Blanket Order'
163 option on the PO page.
165 ===== New Components/Terminology/Concepts
167 * Invoice Item Types have a new flag called 'blanket', available under
168 Admin -> Server Administration -> Acq -> Invoice Item Types in the
170 * Any direct charge using a 'blanket' item type will create a long-lived
171 charge that can be invoiced multiple times.
172 * Such a charge is considered open until its purchase order is "finalized"
174 * "Finalizing" a PO changes the PO's state to 'received' (assuming there are
175 no pending lineitems on the PO) and fully dis-encumbers all blanket charges
176 on the PO by setting the fund_debit amount to $0 on the original fund_debit
178 * Invoicing a 'blanket' charge does the following under the covers:
179 .. Create an invoice_item to track the payment
180 .. Create a new fund_debit to implement the payment whose amount matches the
182 .. Subtract the invoiced amount from the fund_debit linked to the original
183 'blanket' po_item, thus reducing the amount encumbered on the charge as
184 a whole by the invoiced amount.
185 * A PO can have multiple blanket charges. E.g. you could have a blanket
186 order for "Popular Fiction 2015" and a second charge for "Pop Fiction
187 2015 Taxes" to track / pay taxes over time on a blanket charge.
188 * A PO can have a mix of lineitems, non-blanket charges, and blanket charges.
189 * A 'blanket' Invoice Item Type cannot also be a 'prorate' type, since it's
190 nonsensical. Blanket items are encumbered, whereas prorated items are
191 only paid at invoice time and never encumbered.
203 Examples in Apache configuration for "No Image"
204 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
205 There are now commented out examples for custom images to be used when
206 "no image" is present in the catalog for cover art. The included examples
207 are for small/medium/large jacket image art in the event they are not
208 found by the configured Added Content module.
213 Pre-Expiration A/T Event Definition
214 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
215 A new Action Trigger event definition ("30 Day Account Expiration Courtesy
216 Notice") for sending alerts to users before their accounts are expired has
217 been added. This is intended to give users time to renew their account before
218 they lose access to library services.
223 Improved caching of web server templates
224 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
225 Template Toolkit processors used by Apache are now cached for
226 better performance (by virtue of thereby being able to take advantage
227 of Template Toolkit's internal caching mechanism). In addition, the
228 *compiled* versions of the templates themselves can be cached to
229 provide an additional performance boost.
231 Two Apache virtualhost configuration variables are added to
232 control caching of compiled templates:
234 * `OILSWebCompiledTemplateCache` - specifies location on the
235 web server filesystem to store compiled templates.
236 * `OILSWebTemplateStatTTL` - specifies number of seconds before
237 checking to see if a newer version of a cached template is
240 As a result of the caching changes, it is now necessary for
241 Evergreen administrators to reload Apache to ensure that a change
242 to (say) TPAC templates becomes visible.
252 Display Authority Subject Heading Thesaurus Value
253 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
255 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.
257 *A Library of Congress list of thesaurus values:*
260 * '' = Alternate no attempt to code
261 * a = Library of Congress Subject Headings
262 * b = LC subject headings for children's literature
263 * c = Medical Subject Headings
264 * d = National Agricultural Library subject authority file
265 * k = Canadian Subject Headings
267 * r = Art and Architecture Thesaurus
268 * s = Sears List of Subject Headings
269 * v = Repertoire de vedettes-matiere
271 * | = No attempt to code
276 Importing Statistical Categories
277 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
278 You can now retrieve statistical categories (stat cats) from the MARC
279 record and apply them to the items in Evergreen. When importing or
280 overlaying items through the Vandelay MARC batch import process, edit
281 your Holdings Import Profile to tell Evergreen which subfield contains
282 your stat cat data. That subfield in your MARC records should be
283 formatted like the following:
286 CATEGORY 1|VALUE 1||CATEGORY 2|VALUE 2
289 Notice that the pipe character '|' is used to separate each category
290 from its value, and two pipes separate each pair of category values.
292 If you are overlaying existing copies which already have stat cats
293 attached to them, the overlay process will keep those values unless the
294 incoming copies contain updated values for matching categories.
299 Remove the ‡biblios.net Z39.50 target from seed data
300 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
301 The Z39.50 target at z3950.biblios.net/bibliographic has not worked
302 for years, so its service definition is no longer provided in the
303 seed data for new installations of Evergreen.
305 Users of existing Evergreen systems should consider removing
306 the Z39.50 definition for ‡biblios.net. This can be done from
307 Admin | Server Administration | Z39.50 Servers in the staff
313 SKOS for coded values
314 ^^^^^^^^^^^^^^^^^^^^^
315 Some vocabularies used (or which could be used) for stock
316 record attributes and coded value maps in Evergreen are
317 published on the web using SKOS. The record attributes system
318 can now associate Linked Data URIs with specific attribute
319 values. In particular, seed data supplying URIs for the
320 RDA Content Type, Media Type, and Carrier Type in this release.
322 This is an experimental, "under-the-hood" feature that will be built
323 upon in subsuquent releases.
328 MARC Tag-table Service
329 ^^^^^^^^^^^^^^^^^^^^^^
330 The tag tables for the web staff client MARC editor are
331 now stored in the database rather than a separate XML
332 tooltips file as used by the XUL MARC editor. The tag-table
333 service, which is part of the web staff client sprint 2
334 preview in this release, has the following features:
336 - specifies whether (sub)fields are optional or mandatory
337 - specifies whether (sub)fields are repeatable or not
338 - a coded value map can be associated with a subfield to
339 establish a controlled vocabulary for that subfield
340 - MARC field and subfield definitions can be overridden
341 by institutions further down in the organizational unit
342 hierarchy. This allows, for example, a library to specify
343 definitions for local MARC tags.
344 - values supplied by the tag-table service are used to
345 populate values in context menus in the web staff client
348 The initial seed data for the in-database tag table is
349 derived from the current tooltips XML file.
354 Web staff client cataloging preview
355 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
356 The web staff client now includes additional functionality
357 to support cataloging and item maintenance, including:
360 - the service backing the authority headings chooser now
361 has the ability to filter the browse by subject thesaurus
362 - Z39.50 search and record import
363 - improvements to copy and record bucket functionality
364 - embedding the link checker interface
365 - embedding the MARC batch import/export interface
366 - the web staff volume/copy editor
368 Nearly all of the cataloging functionality available in the XUL
369 staff client is now present in the web staff client with the
370 exception of printing spine labels. Nonetheless, the web staff
371 client remains a preview and is not recommended for production use.
381 Conditional Negative Balances
382 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
383 Evergreen sites will now have more control over whether a negative balance can
384 be applied to a user's billing record and when that negative balance can be
385 applied. Through a series of Library Settings, a site can prohibit negative
386 balances on bills or can allow those negative balances to be applied for a
387 specific period of time after a lost or overdue bill is charged to the user.
388 Sites can set a default for all types of bills or can apply distinct settings
389 for lost bills and for overdue fines. The more specific settings will override
392 Sites that opt to allow negative balances for a specific period of time must
393 1) enable the relevant "prohibit negative balances" setting(s) and 2) specify
394 the time period in the relevant Negative Balance Interval setting(s).
396 In addition to the new library settings, the system now has a new account
397 adjustment payment type. This payment type will be utilized for libraries
398 prohibiting negative balances to replace the previous voiding behavior that
399 caused the negative balances to occur. The account adjustment payment type will
400 also be used for all libraries, regardless of the state of negative balance
401 settings, in cases where overdue fines are adjusted when an overdue item is
404 An _Adjust to Zero_ option has been added to the bills interface of the patron
405 record. This option will always adjust the selected bill to a zero balance.
406 It can also be used to easily clear a negative balance from the patron's
407 record. A user must have the new ADJUST_BILLS permission to see and use this
410 This new feature also changes the behavior for the client option to void a bill
411 from the patron record. If a user does not have the VOID_BILLING permission, the
412 option to void bills will be hidden in the bills interface and in the Full
413 Details view of a specific bill.
415 To truly remove the ability to produce negative balances on a transaction,
416 administrators need to 1) enable the relevant setting in the Library Settings
417 Editor and 2) remove the VOID_BILLING permission from staff accounts since
418 manual voiding will continue to produce negative balances.
422 * Negative Balance Interval (Default) (bill.negative_balance_interval_default)
423 * Negative Balance Interval for Lost (bill.negative_balance_interval_on_lost) -
424 * Negative Balance Interval for Overdues (bill.negative_balance_interval_on_overdues
425 * Prohibit negative balance on bills (Default) (bill.prohibit_negative_balance_default)
426 * Prohibit negative balance on bills for lost materials (bill.prohibit_negative_balance_on_lost)
427 * Prohibit negative balance on bills for overdue materials (bill.prohibit_negative_balance_on_overdues)
436 Selfcheck Inactivity Warning
437 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
439 The Selfcheck interface now warns patrons when they are about to be
440 logged out due to inactivity 20 seconds prior to logging them out.
442 The inactivity timeout is also reset with each checkout to avoid timeouts
443 while checking out lots of items.
448 User Registration Includes Inactive Accounts in Dupe Search
449 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
450 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.
460 Link in catalog to clear Added Content cache
461 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
462 On the catalog's record summary page, there is now a link for staff that
463 allow them to forcibly clear the cache for the Added Content for that
464 record. This is helpful if the Added Content retrieved the wrong
465 cover jacket art, summary, etc. and caches the wrong result.
470 Disable Google Analytics in Staff Client
471 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
472 In the staff client interface, Google Analytics for the web catalog is
473 now disabled by default. This was a preventive measure to reduce the
474 potential risks for leaking patron information.
479 Move Acquisitions Admin Menu
480 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
481 In the staff client interface, the Acquisitions Administration menu is
482 now directly accessible from the main "Admin" menu instead of
483 living under "Server Administration". It has also been renamed as "Acquisitions
494 Account Expiration Date in My Account
495 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
496 The Account Expiration Date has been added to the catalog's My Account display
497 on the main Account Summary page and the Account Preferences page. This should
498 help patrons with figuring out when their accounts are due to expire before
499 they actually expire.
503 Change to Available Copies Display
504 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
505 The _Show_ link in the available copies area of the record summary will now
506 display for any org unit that owns a copy of a particular title, even if all
507 those copies are unavailable. The _Show_ link will not display if a) the copy
508 display is already scoped to that org unit or b) the org unit does not own
511 The language has also been changed to read "x of y copies available at z
518 Column sorting in circulation screens
519 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
521 Sorting of selected columns is now available in the *Items Checked Out*, *Check Out History*,
524 * Clicking on the appropriate column heads now sorts the contents from
525 ``ascending'' to ``descending'' to ``no sort''. (The ``no sort'' restores the
526 original list as presented in the screen.)
528 * The sort indicator (an up or down arrow) is placed to the right
529 of the column head, as appropriate.
531 * The combined *Title/Author* column in the *Items Checked Out* screen is now separated into two
532 independently sortable columns (Title and Author).
534 * Title sorting is done with the non-filing characters (leading ``the'', ``a'',
535 ``an'', and other langugage equivalents) removed. The leading articles are rendered in
536 a smaller font, so as to keep the main entry prominent. In
537 addition to the non-filing characters removed for the sort, leading
538 non-alphanumeric characters are ignored in the sort.
543 New bib source variable for catalog customization
544 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
545 For bibliographic records, there is a "bib source" that can be
546 associated with every record. This source is now available as a
547 variable that can be used behind the scenes when customizing
548 the online catalog. The new bib source variables do not present
549 themselves in the catalog display by default.
554 New class attribute for e-resource links
555 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
556 In the catalog, links to electronic resources now have a link class
557 attribute of "uri_link" to make them easier to customize or build
558 additional services upon.
564 Removal of deprecated "JSPAC" interface
565 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
567 The deprecated Javascript OPAC interface known as "JSPAC" is no
568 longer included in Evergreen as of this release.
570 With the understanding that local sites may have made use of
571 existing parts of the old JSPAC interface -- especially images and
572 CSS -- no attempt is made at upgrade time to automatically remove
573 the existing files from disk.
575 When upgrading, you may wish to remove "index.xml" from your Apache
576 DirectoryIndex directives.
578 The following directories, xml, js, and css files were formerly part
579 of JSPAC, and you may be able to safely remove them from your system
580 after verifying that they and their contents are no longer required:
582 - web/opac/common/css/
583 - web/opac/common/js/dtree.js
584 - web/opac/common/xml/
585 - web/opac/extras/bbags.js
586 - web/opac/extras/bbags.xml
587 - web/opac/skin/default/js/
588 - web/opac/skin/default/xml/
591 The list of images removed in this change is lengthy, and not
597 Removal of legacy selfcheck interface
598 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
600 The legacy selfcheck interface is no longer included in Evergreen as
603 This interface was formerly located at a URL ending in
604 extras/selfcheck/selfcheck.xml
606 No attempt is made at upgrade time to automatically remove this
609 It is recommended that you remove this interface and its associated
610 configuration after performing an upgrade:
612 (paths relative to Evergreen web root)
614 - opac/extras/selfcheck/selfcheck.css
615 - opac/extras/selfcheck/selfcheck.js
616 - opac/extras/selfcheck/selfcheck.xml
617 - opac/extras/selfcheck/selfcheck_print.css
619 You can also remove the related Apache configuration block starting
623 <LocationMatch .*/selfcheck.xml>
630 The Evergreen project would like to acknowledge the following
631 organizations who commissioned developments in this release of
634 * Georgia Public Library Service
635 * Grand Rapids Public Library
636 * Kenton County Public Library
637 * King County Library System
638 * Massachusetts Library Network Cooperative
641 * Pennsylvania Integrated Library System
643 We would also like to thank the following individuals who contributed
644 code, documentation patches and tests to this release of Evergreen:
676 We also thank the following organizations whose employees contributed
679 * Anderson County Library
680 * Berklee College of Music
682 * British Columbia Libraries Cooperative
685 * Central/Western Massachusetts Automated Resource Sharing
686 * Emerald Data Networks, Inc.
687 * Equinox Software, Inc.
688 * Georgia Public Library Service
689 * Grand Rapids Public Library
690 * Indiana State Library
691 * King County Library System
692 * Lake Agassiz Regional Library
693 * Laurentian University
694 * Linn-Benton Community College
695 * Massachusetts Library Network Cooperative
696 * Merrimack Valley Library Consortium
698 * Northwest Regional Library System
700 * Traverse Area District Library
702 We regret any omissions. If a contributor has been inadvertantly
703 missed, please open a bug at http://bugs.launchpad.net/evergreen/