1 Evergreen 3.0 Release Notes
2 ===========================
8 This release contains several bug fixes improving on Evergreen 3.0.1:
10 * Fixes several issues related to the display of located URIs in search
12 * Setting `opac_visible` to false for a copy location group now hides only
13 the location group itself, rather than also hiding every single copy in the
15 * Fixes a bug that prevented the copy editor from displaying the _fine level_
16 and _loan duration_ fields.
17 * The "Edit Items" grid action in the Item Status interface will now open
18 in the combined volume/copy editor in batch. This makes the behavior
19 consistent with the "Edit Selected Items" grid action in the copy
21 * Staff members are now required to choose a billing type when creating a
22 bill on a user account.
23 * The Web client now provides staff users with an alert and option to
24 override when an item with the Lost and Paid status is checked in.
25 * Fixes a bug where the Web client offline circ interface was not able
26 to set its working location.
27 * Fixes an issue that prevented the ADMIN_COPY_TAG permission from being
29 * The MARC editor in the Web staff client now presents bib sources in
31 * Both circulation and grocery bills are now printed when a staff user selects
32 a patron account and clicks "Print Bills".
33 * Fixes an issue in the XUL serials interface the "Receive move/selected"
34 action from succeeding.
35 * Fixes a typo in the user password testing interface.
40 This release contains several bug fixes improving on Evergreen 3.0.1:
42 * Copy templates created in XUL Holdings Maintenance will now be
43 automatically converted and displayed in the web staff client's
45 * The list of report templates now includes a column indicating whether
46 the template was originally created in the XUL staff client or the web
47 staff client; staff need to know this since report templates created in
48 one interface cannot be edited in the other.
49 * Call number prefixes and suffixes are now displayed in various grids
50 in the web staff client, including
51 ** Pending Copy Buckets
53 ** Checkin/Capture Holds
55 ** Patron Bills History
62 ** Bib Record View Holds
64 * Many patron fields have been redacted from the web staff client's patron
65 and record holds grids, leaving patron name, username, and ID.
66 * Fixes two bugs where patron records could fail to be saved upon editing.
67 * The web staff patron editor now better warns staff users about
68 duplicate names, IDs, phone numbers, and email addresses.
69 * Human readable labels are now displayed for certain fields in standing
71 * The patron summary in the web staff client now correctly displays
72 primary and secondary ID values.
73 * The web staff client's billing full details page now displays
74 information about the staff user that created a payment.
75 * The web staff client now requires staff users to explicitly set a
76 billing type when adding a manual bill.
77 * The web staff client's patron bill annotation modal now works.
78 * Patron barcode search completion in the web staff client now allows
79 the user to select from all of the matching patron records.
80 * The Hold Shelf Slip print template in the web staff client now has
81 access to the call number.
82 * The Checkout Receipt print template in the web staff client now can
83 include summary financial information, incuding current balance, total
84 paid on outstanding fines, and total owed.
85 * The web staff print templates for current and historical bills can
86 now include copy barcode and title.
87 * Fixes a bug that resulted in some catalog searches unexpectedly
89 * Fixes a bug that resulted in catalog searches that specify a location
90 limit returning incorrect results.
91 * Fixes a bug where deleted copies could make records visible in the
93 * Fixes a bug where certain queries on copies used in the public catalog
95 * Fixes a bug place a hold request in the public catalog could result
96 in "forgetting" the type and library of the user's previous search.
97 * The web staff client now respects staff user session timeouts, and
98 will log out all open tabs if a user's session has timed out.
99 * The web staff Z39.50 page will now give the staff user an alert if
100 they attempt to import a record with a duplicate TCN.
101 * Fixes a bug that prevented copy notes, copy tags, and copy bucket
102 entries from being deleted.
103 * Fixes a bug that made using the volume/copy editor to change a copy's
105 * The administration interface for hard due dates now ensures that
106 new (or edited) ceiling dates have their time component set to end
107 of day, resolving an issue where ceiling dates would not be applied
108 during the ceiling date itself.
109 * The web staff client can now include dynamic information in browser
110 tab titles, e.g., "Smith, Jane - Checkout".
111 * The Concerto sample data set now includes data allowing for testing
112 placing holds on monographic parts.
113 * Asset merging during bibliographic record merging now correctly
114 recognizes call number prefixes and suffixes and deletes disused
116 * Fixes a bug where displaying user surveys could result in PCRUD
118 * Fixes a bug where pg_restore of an Evergreen database could fail
119 to create certain indexes on the `actor.usr` table.
123 We would like to thank the following individuals who contributed code,
124 tests and documentation patches to the 3.0.2 point release of
155 This release contains several bug fixes improving on Evergreen 3.0.0
157 * Fixes a bug in the web staff client that prevented initials from being
158 stored with copy notes.
159 * Adds billing types that may have been missed by systems that were
160 running Evergreen prior to the 1.4 release.
161 * Fixes a web staff client bug with the CSV export option available from
162 the Import Queue in the MARC Batch Import/Export interface.
163 * Adds the missing copy alert field in the web client's volume/copy
165 * Fixes a bug where the setting to require date of birth in patron
166 registration was not being honored in the web staff client.
167 * Fixes a bug in the web staff client patron registration form where the
168 password wasn't generating from the last four digits of the patron's
170 * Fixes an issue in the web staff client where the complete barcode did
171 not display in some interfaces when partial barcodes were scanned.
172 * Fixes an HTML error in the new copy tags that display on the record
174 * Fixes a web staff client bug where recording a large number of in-house
175 uses at one time doesn't display a confirmation dialog once it hits the
177 * Adds a _Print Full Grid_ action in the web staff client
178 holds pull list to allow staff to print the entire pull list as it
179 displays on the screen. This change also changes the _Export CSV_ action
180 to an _Export Full CSV_ option.
181 * Fixes an issue with the Patron Messages interface that prevented it
182 from saving column configuration changes in the web staff client.
183 * Fixes a bug in the web staff client where a billing prompt did not
184 correctly display after marking an item damaged in those systems that
185 have enabled the setting to bill for damaged items.
186 * Adds an option to the specific due date feature that allows saving
187 that due date until logout. This allows all circulations from a given
188 workstation to be due on the same date.
192 We would like to thank the following individuals who contributed code,
193 tests and documentation patches to the 3.0.1 point release of
215 The minimum version of PostgreSQL required to run Evergreen 3.0 is
216 PostgreSQL 9.4. Evergreen 3.0 also requires OpenSRF 3.0.0 or later.
218 Change to Names of Shared Libraries
219 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
220 OpenSRF 3.0 changes how the shared libraries for services written in
221 C are named. If upgrading from an earlier version of Evergreen,
222 `opensrf.xml` should be edited so that shared library file names
223 listed in the `<implementation>` tag start with "lib". For example,
226 ---------------------------------------------------------------------
228 <language>C</language>
229 <implementation>oils_cstore.so</implementation>
230 ---------------------------------------------------------------------
232 should be changed to:
235 ---------------------------------------------------------------------
237 <language>C</language>
238 <implementation>liboils_cstore.so</implementation>
239 ---------------------------------------------------------------------
241 SIP Bugfix Requires SIPServer Upgrade
242 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
244 The fix for Launchpad Bug 1542495: "OpenILS::SIP::clean_text() can
245 crash" requires that you also upgrade SIPServer with the fix for
246 Launchpad Bug 1463943: "Non-ascii Unicode characters in messages cause
247 SIP client problems." This means that if you use SIP2 with Evergreen,
248 you must also upgrade SIPServer to the latest commit in the Git
249 repository. Conversely, if you upgrade SIPServer to the latest commit
250 in Git, you must also upgrade Evergreen or, at least, apply the patch
251 for Launchpad Bug 1542495. These two patches are complementary and
252 cannot be applied independently of one another.
254 `open-ils.auth.login`
255 ~~~~~~~~~~~~~~~~~~~~~
256 The new `open-ils.auth.login` API must be added to the list of `<log_protect>`
257 API's in the `opensrf_core.xml` file.
262 ---------------------------------------------------------------------
263 --- a/Open-ILS/examples/opensrf_core.xml.example
264 +++ b/Open-ILS/examples/opensrf_core.xml.example
265 @@ -180,6 +180,7 @@ Example OpenSRF bootstrap configuration file for Evergreen
267 <match_string>open-ils.auth.authenticate.verify</match_string>
268 <match_string>open-ils.auth.authenticate.complete</match_string>
269 + <match_string>open-ils.auth.login</match_string>
270 <match_string>open-ils.auth_proxy.login</match_string>
271 <match_string>open-ils.actor.patron.password_reset.commit</match_string>
272 <match_string>open-ils.actor.user.password</match_string>
273 ---------------------------------------------------------------------
277 Administrators of Evergreen who use RTL locales and who have customized
278 `style-rtl.css.tt2` should now incorporate their customizations into
281 Multi-Time Zone Installations
282 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
284 For Evergreen consortia that span more than one time zone, the following
285 query will adjust all historical, unaged circulations so
286 that if their due date field is pushed to the end of the day, it is done
287 in the circulating library's time zone, and not the server time zone.
289 It is safe to run this after any change to library time zones.
291 Running this is not required, as no code before this change has
292 depended on the time string of '23:59:59'. It is also not necessary
293 if all of your libraries are in the same time zone, and that time zone
294 is the same as the database's configured time zone.
303 for ou_id in select id from actor.org_unit loop
304 for new_tz in select oils_json_to_text(value) from actor.org_unit_ancestor_setting('lib.timezone',ou_id) loop
305 if new_tz is not null then
306 update action.circulation
307 set due_date = (due_date::timestamp || ' ' || new_tz)::timestamptz
308 where circ_lib = ou_id
309 and substring((due_date at time zone new_tz)::time::text from 1 for 8) <> '23:59:59';
318 Deprecation of XUL staff client
319 -------------------------------
320 Starting with the release of 3.0.0, patches that fix XUL bugs will not
321 be merged into master or backported unless they meet one or more of
322 the following conditions:
324 a. the bug is a security issue
325 b. the bug involves the destruction of data
326 c. the bug is a regression of functionality in the XUL staff client
327 introduced by other work done to Evergreen
329 Under no circumstances will XUL staff client feature enhancements be merged.
331 This policy will continue through the 3.0.x and 3.1.x maintenance
332 release cycles, and will become moot upon the release of 3.2.0, when
333 the XUL staff client is slated to be entirely removed.
342 Evergreen 3.0 features a new, modern staff client that runs in the web browser
343 and can be used on desktop and mobile devices. All functional areas of the
344 system, including circulation, cataloging, acquisitions, serials, reports,
345 booking, administration, and offline circulation, are available in the new staff
346 client. Chrome and Firefox are officially supported for use with the web client.
348 Library staff will no longer need to download separate software to perform most
349 actions in Evergreen. A Chrome plugin called Hatch will be available as a
350 separate installation for workstations that require seamless, dialog-free
351 printing to multiple printers.
353 In addition to adding more portability and stability, the new staff client also
354 presents a cleaner and more modern interface for users. By virtue of running in
355 a browser, actions that users are accustomed to performing on other web sites
356 should now be available in the Evergreen client.
358 The old, XUL client will continue to be available to allow for a gradual
359 transition to the browser-based client, but no new features will be added. The
360 old client will totally be removed from Evergreen in the Fall 2018 3.2.0
370 New EDI Order Generator
371 ^^^^^^^^^^^^^^^^^^^^^^^
376 . New database tables exist for configuring vendor-specific EDI order
380 ** List of EDI order generation toggles, e.g. "INCLUDE_COPIES" to add
383 ** Collection of `edi_attr`s. Each edi_account may be linked to one
385 ** One `edi_attr_set` per known vendor is added to the stock data, matching
386 the stock configuration found in the JEDI template.
387 * `acq.edi_attr_set_map`
388 ** Link between `edi_attr`s and `edi_attr_set`s.
390 . EDI Attribute Sets are manged via a new (browser client only) configuration
391 interface at 'Administration -> Acquisitions Administration -> EDI
394 . Each `acq.edi_account` should be linked to an `acq.edi_attr_set`. If a link
395 is not set, default values will be used. Links between an EDI account
396 and an attribute set are managed in the EDI Accounts configuration
399 . Local modifications to the stock EG JEDI template are managed by modifying
400 and/or adding additional `edi_att_set`s as needed.
402 . A new `edi_order_pusher.pl` script is added which replaces the functionality
403 of `edi_pusher.pl`. `edi_pusher.pl` is still available.
405 . After moving to `edi_order_pusher.pl`, the JEDI Action/Trigger event
406 definition is no longer required and can be disabled.
411 EDI accounts have a new boolean field 'Use EDI Attributes' (`use_attrs`) that
412 specifies whether PO's generated via the account should be built using
413 EDI attributes or fall back to traditional JEDI A/T template generation.
415 This allows sites to activate EDI attributes on a per-account basis, making
416 it possible to migrate piecemeal to EDI attributes. For the initial roll
417 out of this new feature, no accounts will be configured to use EDI
418 attributes by default.
424 3 Day Courtesy Notice by SMS
425 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
426 New optional SMS text notification to be sent out 3 days prior to the due
427 date of any circulating item for patrons who have an SMS text number and
428 carrier stored in their accounts. This action trigger is disabled by default,
429 but can be enabled and modified by going into 'Administration -> Local Administration ->
430 Notifications / Action Triggers'.
432 You may wish to make use of granularity so that these messages are batched
433 and sent at the same time each day.
438 Add Description Field to Circulation and Hold Configuration Entries
439 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
440 The circulation and hold policy configuration rules now each have a
441 description field. This allows administrators to add comments to
442 describe the purpose of each rule.
447 Apache Internal Port Configuration Option
448 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
449 Apache configuration now supports a new variable which allows admins to
450 specify the port used by Apache to handle HTTP traffic. The value is
451 used for HTTP requests routed from Perl handlers back to the same Apache
452 instance, like added content requests. Use this when running Apache
453 with a non-standard port, typical with a proxy setup. Defaults to "80".
456 -------------------------------------------------------------------
459 PerlSetVar OILSWebInternalHTTPPort "7080"
462 -------------------------------------------------------------------
467 Configurable Bib Record Display Fields
468 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
470 'Administration -> Server Administration -> MARC Search/Facet Fields' have 2 new configuration
471 fields: 'Display Field?' and 'Display XPath'.
473 When 'Display Field' is set to true, data from the field will be extracted
474 from each record and added to a new table of display data for each bib
477 If a value is present in the 'Display XPath' field, this XPath will be
478 applied to the extracted data *after* the base XPath (from the 'XPath'
479 field) is applied to each field.
481 This data acts as a replacement for the various and sundry ways bib record
482 data is currently extracted, including inline XPath in the TPAC, reporter
483 views, real-time 'MVR' compilation from MODS, etc. and will be available
484 to the user interface, notification templates, etc. for rendering bib
487 The browser client gets a new service 'egBibDisplay' which is capable
488 of translating the display field data from various formats into
489 data more suitable for JavaScript usage.
491 The database gets 3 new views for representing display data in various
494 * `metabib.flat_display_entry`
495 ** List of all display fields linked to their configuration.
496 * `metabib.compressed_display_entry`
497 ** Same as `metabib.flat_display_entry` except there's one row
498 per display field type, with 'multi' rows compressed into
499 JSON arrays. Non-multi fields are represented as JSON
501 * `metabib.wide_display_entry`
502 ** Tabular view of display field data, one column per well-known
503 field. Values are represented JSON, consistent with
504 `metabib.flat_display_entry`. The view does *not* contain locally
505 configured display fields, as each field must be encoded in
506 the view and IDL definition. This is essentially a replacement
507 for `reporter.simple_record`.
512 After making changes to display field configuration, it's possible to
513 reingest only display field data in the database using the following:
516 ---------------------------------------------------------------------
517 SELECT metabib.reingest_metabib_field_entries(id, TRUE, FALSE, TRUE, TRUE,
518 (SELECT ARRAY_AGG(id)::INT[] FROM config.metabib_field WHERE display_field))
519 FROM biblio.record_entry WHERE NOT deleted AND id > 0;
520 ---------------------------------------------------------------------
526 Fix COPY_STATUS_LONGOVERDUE.override Permission Typo
527 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
528 The existing permission was incorrectly created with a code of
529 `COPY_STATUS_LONGOVERDUE.override`, while the event thrown requires a
530 permission with a code of `COPY_STATUS_LONG_OVERDUE.override`. This
531 update changes the permission code to match what the event requires.
537 Hold Targeter V2 Repairs and Improvements
538 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
539 * Make the batch targeter more resilient to a single-hold failure.
540 * Additional batch targeter info logging.
541 * Set `OSRF_LOG_CLIENT` in `hold_targeter_v2.pl` for log tracing
542 * Removes the confusingly named `--target-all` option
543 ** The same behavior can be achieved by using `--retarget-interval "0s"`
544 * Removes `--skip-viable` (see `--soft-retarget-interval` below)
546 New --next-check-interval Option
547 ++++++++++++++++++++++++++++++++
548 Specify how long after the current run time the targeter will retarget
549 the currently affected holds. Applying a specific interval is useful
550 when the retarget-interval is shorter than the time between targeter
553 For example, if the targeter is run nightly at midnight with a
554 `--retarget-interval 36h`, you would set `--next-check-interval` to `48hr`,
555 since the holds won't be processed again until 48 hours later. This
556 ensures that the org unit closed date checks are looking at the correct
559 This setting overrides the default behavior of calculating the next
560 retarget time from the retarget-interval.
562 New --soft-retarget-interval Option
563 +++++++++++++++++++++++++++++++++++
564 This is a replacement for (and rebranding of) the `--skip-viable` option.
565 The new option allows for time-based soft-targeting instead simple binary
566 on/off soft-targeting.
568 How soft-targeting works:
570 * Update hold copy maps for all affected holds
571 * Holds with viable targets (on the pull list) are otherwise left alone.
572 * Holds without viable targets are retargeted in the usual manner.
578 New marc_export --descendants Option
579 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
581 The `marc_export` script has a new option, `--descendants`. This option
582 takes one argument of an organizational unit shortname. It works much
583 like the existing `--library` option except that it is aware of the
584 org. tree and will export records with holdings at the specified
585 organizational unit and all of its descendants. This is handy if you
586 want to export the records for all of the branches of a system. You
587 can do that by specifying this option and the system's shortname,
588 instead of specifying multiple `--library` options for each branch.
590 The `--descendants` option can be repeated, as the `--library` option can.
591 All of the specified org. units and their descendants will be included
592 in the output. It can also be combined with individual `--library`
593 options when necessary.
598 RTL and LTR Public Catalog Stylesheets Merged
599 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
600 The RTL stylesheet for the public catalog,
601 `templates/opac/css/style-rtl.css.tt2`, has been merged into the LTR
602 one (`templates/opac/css/style.css.tt2`). The combined stylesheet
603 template will provide RTL or LTR styles based on the value of
604 the `rtl` flag of the active locale. An `rtl` variable is also available
605 in the template to allow the correct style to be chosen.
610 Miscellaneous Improvements
611 ^^^^^^^^^^^^^^^^^^^^^^^^^^
613 * If a filter is in effect in the Library Settings Editor,
614 the filter will continue to be applied after a user
615 changes the selected library.
616 * Copy templates used for serials now correctly link to age
617 protection rules and MARC item type values (for the
618 "Circ as Type" field). During upgrade, the database update
619 will set to NULL any age protection and circ as type fields
620 in serial copy templates that do not point to defined values.
625 Obsolete Internal Flag Removed
626 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
628 An obsolete and unused `ingest.disable_metabib_field_entry` internal
629 flag was removed from the `config.internal_flags` table. It was
630 rendered obsolete by the addition of the 3 flags to control the
631 browse, search, and facet indexing.
636 Tweaks to Caching/Expiry of Public Catalog Assets
637 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
638 The default cache expiration time for static assets (e.g.,
639 CSS, image, and JavaScript files) in the public catalog and
640 the Kid's PAC has been increased to one year. Links to all
641 such assets now have a cache-busting value tacked on as a
642 query parameter. This value is refreshed when `autogen.sh` is
643 run, but it can also be manually set by adjusting the
644 `ctx.cache_key` Template Toolkit variable.
649 Action/Trigger Events Data Purging
650 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
652 Action/Trigger event definitions have a new field called 'Retention
653 Interval'. When an optional interval value is applied, events and
654 template output data linked to the event definition will be deleted
655 from the database once they reach the specified age.
657 Retention Interval Restrictions for Passive Hooks
658 +++++++++++++++++++++++++++++++++++++++++++++++++
660 Restrictions are placed on retention interval values for event definitions
661 using passive hooks to prevent data from being deleted while it's still
662 needed by the system.
664 The presence of event data is how the system knows not to send duplicate
665 events. As long as a scenario exists where a duplicate event may be
666 generated, the events must be retained.
668 To apply a retention interval value to a passive-hook event definition:
670 * The event definition must have a max_delay value.
671 * The retention interval must be larger than the difference between
672 the `delay` and `max_delay` values.
674 For example, if the `delay` is 7 days and `max_delay` is 10 days, the retention
675 interval must be greater than 3 days to ensure no duplicate events are
676 created between the first event on day 7 and the end of the event validity
682 A new `purge_at_events.sh` script is installed in the bin directory
683 (typically `/openils/bin`) which should be added to CRON for regular
686 NOTE: On large data sets, this script can take a long time to run and
687 create higher than normal I/O load as it churns though the event and
688 event_output tables. You may wish to run the script by hand the first
689 time so it can be monitored. It can be run in psql like so:
692 ---------------------------------------------------------------
693 SELECT action_trigger.purge_events();
694 ---------------------------------------------------------------
696 NOTE: On *very* large data sets (10s to 100s of millions of event and
697 event_output rows), it may be advisable to first repopulate the `event`
698 and `event_output` tables with only the desired data before starting
699 regular purges. This can be done, for example, using the copy to temp
700 table, truncate source table, repopulate source table from temp table
701 approach. This will be much faster than the `purge_events()` function
702 in cases where most of the data will be purged.
707 A number of `action_trigger.hook` entries which have always been treated
708 as active hooks, though are configured as passive hooks, have been
709 updated to properly reflect the non-passive-ness. This allows for
710 simpler configuration of their retention interval values.
716 Remove JSPAC Redirects
717 ^^^^^^^^^^^^^^^^^^^^^^
718 Future versions of Evergreen will no longer contain automatic redirects
719 from JSPAC URLs to TPAC URLs, with the exception of `myopac.xml`, given
720 that the JSPAC is no longer supported. Existing sites, however, may
721 wish to retain JSPAC redirects in their Apache configuration files since
722 JSPAC URLs may still be used in the wild to access their catalogs.
724 The original JSPAC URL redirects are all retained in the file
725 `Open-ILS/examples/jspac_redirects.conf` for reference.
735 New open-ils.auth.login API
736 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
737 The `open-ils.auth` service has a new API for requesting an authentication
738 token. It performs the same steps as the
739 `open-ils.auth.authenticate.init` and `.complete` APIs in a single call,
740 using the bare password. No intermediate password hashing is required.
742 The paramaters are the same as the `.complete` call with a few modifications.
744 1. Using the generic 'identifier' parameter in combination with the
745 'org' parameter allows the API to reliably determine if an identifier
746 value is a username or barcode. The caller is no longer required to
747 make that determination up front.
749 2. The 'nonce' parameter is no longer used.
755 Batch Patron Contact Invalidation
756 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
757 The following methods are used to mark patron contact fields
758 as invalid by moving the invalid value to a standing penalty:
760 * `open-ils.actor.invalidate.email`
761 * `open-ils.actor.invalidate.day_phone`
762 * `open-ils.actor.invalidate.evening_phone`
763 * `open-ils.actor.invalidate.other_phone`
765 These methods now accept a fifth argument specifying the value
766 of the contact field, e.g., a specific phone number or email
767 address. If supplied, and if a specific patron ID (the first
768 argument) is not supplied, all patrons with that specific contact
769 value will have it marked invalid.
779 Pure-SQL catalog searching
780 ^^^^^^^^^^^^^^^^^^^^^^^^^^
781 Public and staff catalog search is now both more accurate and faster
782 by redesigning how the visibility of records is calculated.
792 Authority Record and Headings Browse Improvements
793 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
794 Various improvements are made to support for authority records
795 and headings browsing:
797 * The MARC to MADS XSLT stylesheet is now used as part of parsing
798 headings from authority records. Since the MODS and MADS stylesheets
799 extract headings in similar ways, duplicate browse entries are now
800 much less likely to occur.
801 * A new configuration table, `authority.heading_field`, is now used
802 to specify how headings should be extracted from authority records.
803 * Related headings can now be identified as narrower or broader when
804 browsing in the public catalog.
805 * See references are now more reliably included in the browse list.
806 * Scope (public) notes now display only under the main heading.
807 * There is now a global flag, Display related headings (see-also) in browse,
808 that can be used to control whether related headings (see-alsos) are
809 displayed in the public catalog list.
810 * A complete set of thesauruses are now included in the seed data. Thesauruses
811 can now be identified using short and long codes.
812 * The labels for see and see-also references in the public catalog are
813 a bit more patron-friendly, and can now be tweaked via TPAC template
814 customization in the browse.tt2 file.
820 Copy Tags and Digital Bookplates
821 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
822 Copy tags will allow staff to apply custom, pre-defined labels or tags
823 to copies. Copy tags are searchable in both the staff client and public
824 catalog. This feature was designed to be used for Digital Bookplates to
825 attach donation or memorial information to copies, but may be used for
826 broader purposes to tag items.
828 Each copy tag can either be publicly-visible or visible only to staff.
829 Copy tags also have types that can be used for restricting catalog
830 searches on copy tags to particular types.
832 Copy tags are displayed in the copy table in the record summary page in
833 the public catalog, and a new library setting can be used to add
834 a "Digital Bookplate" search field. Copy tags can also be used
835 as a search filter, e.g.,
837 * `copy_tag(bookplate, jane smith)`: search for records that have a
838 copy tag of type 'bookplate' whose value contains 'jane smith'.
839 * `copy_tag(*, jane smith)`: search for records that have a
840 copy tag of any type whose value contains 'jane smith'.
842 All staff-side interfaces related to copy tags exist only in the web
843 staff client. There are two new administration interfaces for managing
844 copy tags and copy tag types. The copy editor now has a 'Copy Tags'
845 button for applying copy tags to copies; that interface can also be
846 used to create new copy tags on the fly. Furthermore, the copy buckets
847 interface now has an 'Apply Tags' action for assigning tags to groups
853 Two new permission are included:
855 * `ADMIN_COPY_TAG_TYPES`: required to create a new tag type under
856 'Administration -> Server Administration -> Copy Tag Types'
857 * `ADMIN_COPY_TAG`: required to create a new tag under
858 'Administration -> Local Administration -> Copy Tags'
860 The existing permission `UPDATE_COPY` controls whether or not a user
861 can link copies to tags.
865 A new library setting, 'Enable Digital Bookplate Search', controls
866 whether to display a 'Digital Bookplate' field in the search index
867 drop-downs in the catalog. A 'Digital Bookplate' search will include
868 all records that have a copy that matches the tag specified by the user.
869 It should be noted that this library setting does not affect the
870 display of copy tags on the catalog record summary page.
875 Include Call Number Prefixes and Suffixes in Export and Z39.50 output
876 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
877 The call number prefix and suffix, when present, are now included in
878 subfields $k and $m of the 852 field when running `marc_export` with
879 the `--items` switch. Similarly, when using Evergreen as a Z39.50
880 server configured to embed item data in 852 fields, the affixes are now
881 included in subfields $k and $m.
891 Batch Editing of Patron Records
892 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
893 There is a now a new interface analogous to the Copy Bucket interface
894 to select and group a set of users into a User Bucket.
895 The addition of users to a User Bucket is possible from the Patron Search
896 interface by the use of a new grid Action, and directly on the User Bucket
897 interface by user barcode. It is also possible to add users to a User
898 Bucket by uploading a text file that contains a list of user barcodes.
900 From this interface it is possible to perform a set of specific batch update
901 operations on user records.
906 These fields can now be changed in batch via an action on the User Bucket
907 grid if the staff user has the `UPDATE_USER` permission:
910 * Primary Permission Group (group application permissions consulted)
912 * Home Library (`UPDATE_USER` checked against both old and new value)
913 * Privilege Expiration Date
914 * Barred flag (`BAR_PATRON` permission consulted)
915 * Internet Access Level
917 Changes made in this interface can be rolled back.
919 As a batch process, rather than a direct edit, this mechanism explicitly skips
920 processing of Action/Trigger event definitions for user update.
925 The batch edit mechanism also allows for the batch deletion of user. The staff
926 user must have both the `UPDATE_USER` and `DELETE_USER` permissions.
928 Changes made in this interface can be rolled back.
930 As a batch process, rather than a direct edit, this mechanism explicitly skips
931 processing of Action/Trigger event definitions for user deletion.
933 This mechanism does not use the Purge User functionality, but instead simply
934 marks the users as deleted.
936 Editing Statistical Category Entries
937 ++++++++++++++++++++++++++++++++++++
939 All users in the bucket can have their Statistical Category Entries
940 modified. Unlike user data field updates, modification of Statistical
941 Category Entries is permanent and cannot be rolled back.
943 As a batch process, rather than a direct edit, this mechanism explicitly skips
944 processing of Action/Trigger event definitions for user update.
946 New Service Requirement
947 +++++++++++++++++++++++
949 This new functionality makes use of the QStore service (`open-ils.qstore`), which was previously
950 unused in production. If this service has been removed from the configuration
951 of a live Evergreen instances, it will need to be added back in order for
952 batch user editing to succeed.
957 Honor Timezone of the Acting Library
958 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
963 * Display day-granular due dates in the circulating library's timezone.
964 * Only display the date portion of the due date for day-granular circulations.
965 * Display the full timestamp, in the client's timezone rather than the circulation library's, for hourly circulations.
966 * Provide infrastructure for more advanced formatting of timestamps.
967 * Override the built-in AngularJS date filter with an implementation that uses moment.js, providing consistency and better standards compliance.
972 This is a followup to the work done for 2.12, where we added the ability
973 for the client to specify a timezone in which timestamps should be interpreted
974 in business logic and the database.
976 Most specifically, this work focuses on circulation due dates and the closed
977 date editor. Due dates, where displayed using stock templates (including
978 receipt templates) and used for fine calculation, are now manipulated in the
979 library's configured timezone. This is controlled by the new 'lib.timezone'
980 setting available via the Library Settings Editor, loaded from the server when
981 required. Additionally, closings are recorded in the library's timezone so that
982 due date calculation is more accurate. The closed date editor is also
983 taught how to display closings in the
984 closed library's timezone. Closed date entries also explicitly record if they
985 are a full day closing, or a multi-day closing. This significantly simplifies
986 the editor, and may be useful in other contexts.
988 To accomplish this, we use the moment.js library and the moment-timezone addon.
989 This is necessary because the stock AngularJS date filter does not understand
990 locale-aware timezone values, which are required to support DST. A simple
991 mapper translates the differences in format values from AngularJS date to
994 Of special note are a set of new filters used for formatting timestamps under
995 certain circumstances. The new egOrgDateInContext, egOrgDate, and egDueDate
996 filters provide the functionality, and autogrid is enhanced to make use of
997 these where applicable. egGrid and egGridField are also taught to accept
998 default and field-specific options for applying date filters. These filters may
999 be useful in other or related contexts.
1001 The egDueDate filter, used for all existing displays of due date via Angular
1002 code, intentionally interprets timestamps in two different ways WRT timezone,
1003 based on the circulation duration. If the duration is day-granular (that is,
1004 the number of seconds in the duration is divisible by 86,400, or 24 hours worth
1005 of seconds) then the date is interpreted as being in the circulation library's
1006 timezone. If it is an hourly loan (any duration that does not meet the
1007 day-granular criterium) then it is instead displayed in the client's timezone,
1008 just as all other timestamps currently are, because of the previous Evergreen
1011 The public catalog is adjusted to always display the due date in the circulating
1012 library's timezone. Because the public catalog displays only the date portion of the due
1013 date field, this difference is currently considered acceptable. If this proves
1014 to be a problem in the future, a minor adjustment can be made to match the
1015 egDueDate filter logic.
1017 Now that due dates are globally stored in the configured timezone of the
1018 circulating library, the automatic adjustment to day-granular due dates needs
1019 to take those timezones into account.
1021 An optional SQL command is provided by the upgrade script to retroactively
1022 adjust existing due dates after library configuration is complete.
1028 Enhancements to Hard Due Date Functionality
1029 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1030 It will now be possible to delete Hard Due Date Values for dates that have
1031 passed. Also, the Hard Due Date updater will no longer change Ceiling Dates
1032 to a past date. This allows editing Ceiling Dates directly in a Hard Due Date
1033 as well as scheduling Ceiling Date changes via Hard Due Date Values.
1038 Patron Search by Birth Date
1039 ^^^^^^^^^^^^^^^^^^^^^^^^^^^
1040 * Now you can include the patron birth year and/or birth month and/or
1041 birth day when searching for patrons using the web staff client.
1042 * Day and month values are exact matches. E.g. month "1" (or "01")
1043 matches January, "12" matches December.
1044 * Year searches are "contains" searches. E.g. year "15" matches 2015,
1045 1915, 1599, etc. For exact matches use the full 4-digit year.
1049 Patron Search from Place Hold
1050 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1051 This feature allows staff members, when placing a
1052 hold on behalf of a patron in the web staff client, to search for
1053 patrons by names and other searchable patron information, rather than
1054 relying on barcode alone. In particular, after performing a catalog
1055 search or going to a specific bib record and clicking the 'Place Hold'
1056 button, the form now includes a 'Patron Search' button. This button
1057 will open a dialog allowing the staff member search for and select
1063 Retrieve Recent Patrons
1064 ^^^^^^^^^^^^^^^^^^^^^^^
1066 Adds a new library setting 'Number of Retrievable Recent Patrons'
1067 ('ui.staff.max_recent_patrons') that specifies the number of recently
1068 retrieved patrons that can be re-fetched from the staff client.
1070 A value of 0 means no recent patrons can be retrieved.
1071 A value greater than 1 means staff will be able to retrieve multiple
1072 recent patrons via a new Circulation 'Retrieve Recent Patrons' menu entry.
1074 The default value is 1 for backwards compatibility.
1081 Fuller title in XUL client Simplified Pull List
1082 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1083 The Simplified Pull List in the XUL client will now display subfields 245$n and
1084 $p in the title field. The addition will make it easier for staff to distinguish
1085 between different parts or seasons in a series.
1091 Transit Cancel Time and Terminology Change
1092 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1097 Previously, Evergreen deleted canceled (aborted) transits from the database. Now
1098 the rows in `action.transit_copy`, `action.hold_transit_copy`, and `action.reservation_transit_copy`
1099 are preserved in the database, though still not visible to the end user in the staff client.
1100 This allows for better tracking of when transits are canceled for the purposes of knowing
1101 which staff member canceled the transit, etc.
1103 NOTE: This change may require the re-creation of transit reports to filter out canceled
1104 transits from the results. Cloning the template and adding a 'Base Filter' of 'Cancel Time
1105 Is NULL' will suffice.
1107 "Canceled Transit" Terminology Change
1108 +++++++++++++++++++++++++++++++++++++
1110 The term "abort" has been replaced with "cancel" in all of the affected user interfaces.
1111 For internal continuity, however, the following permission codes have not changed:
1114 * `ABORT_REMOTE_TRANSIT`
1115 * `ABORT_TRANSIT_ON_LOST`
1116 * `ABORT_TRANSIT_ON_MISSING`
1124 Offline Circulation Available in Web Staff Client
1125 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1126 Offline circulation is now available in the web staff client. In order to use the
1127 offline interface, users must first log into the web staff client, perform
1128 a patron search, select a user from the results, and open the patron editor
1129 interface to collect all the relevent configuration information for the
1130 workstation. In addition, the offline interface available from the Circulation
1131 menu provides a 'Download block list' button for users who are logged in.
1133 As is the case in the old staff client, users can check materials in and out,
1134 renew items, and create new patron accounts while offline. The patron fields
1135 available in the offline patron registration editor are the same ones that
1136 are available to staff when working online.
1140 Add Circ Modifier to Record Detail Page in Staff TPAC
1141 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1142 The circulation modifier field is added to the table of copies to make
1143 more information available to staff without having to open
1150 Date+Time Format Settings for Web Client
1151 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1153 This change deprecates the existing 'Format Dates' and 'Format Times' settings
1154 and adds two settings for use with the webstaff client:
1156 * 'Format Dates with this pattern'
1157 * 'Format Date+Time with this pattern'
1159 These settings use format strings as documented here:
1161 https://docs.angularjs.org/api/ng/filter/date
1163 There is overlap with how the Dojo formats worked, but also some differences.
1165 The original 'Format Dates' and 'Format Times' settings worked together, but the
1166 new settings work independently. Certain field elements will use one, and
1167 certain field elements will use the other. These distinctions are hard-coded
1168 in the various UI templates, with the idea being that timestamp fields in
1169 which the date component alone is sufficient information (for example, date of birth)
1170 will use the 'Format Dates' setting. Fields where the time component is
1171 important (for example, checkout time) will use the 'Format Date+Time' setting.
1173 When the settings 'Format Dates' and 'Format Date+Time' are unset, we will default
1174 to "shortDate" (M/d/yy) and "short" (M/d/yy h:mm a), respectively.
1180 Global Option to Remove Sound for a Specific Event
1181 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1182 A new `nosound.wav` file has been added to the web client. The file can be used
1183 to globally disable audio alerts for a specific event on an Evergreen system.
1185 For example, to silence the alert that sounds after a successful patron search:
1189 mkdir -p /openils/var/web/audio/notifications/success/patron/
1190 cd /openils/var/web/audio/notifications/success/patron/
1191 ln -s ../../nosound.wav by_search.wav
1198 The official Evergreen manual has been split into eight new manuals, each
1199 designed for a specific audience. This new approach is designed to make
1200 the documentation more readable and usable.
1202 The specific audiences for the new manuals are:
1204 * Acquisitions staff
1207 * Public services staff who use the public catalog
1209 * System administrators who use the command line
1210 * System administrators who use the Web client
1211 * System administrators and programmers who wish to integrate Evergreen
1212 with other technologies
1214 All manuals are available at http://docs.evergreen-ils.org
1220 Improvements to ebook API
1221 ^^^^^^^^^^^^^^^^^^^^^^^^^
1223 Evergreen now supports checking out and placing holds on
1224 OverDrive and OneClickdigital ebook titles from within the public
1225 catalog. This is an experimental feature. It is not recommended for production
1226 use without careful testing.
1228 When ebook integration is enabled, a "Check Out E-Item" link will be
1229 displayed when viewing an ebook title from a supported vendor in the
1230 catalog. Clicking on the link allows the user to check out and download
1231 that title from the vendor directly within the catalog.
1233 If no copies are available for the title, a "Place Hold on E-Item" link
1234 is displayed instead, and the user may place a hold on the title. (Note
1235 that some vendors require the user's account to have an email address
1236 before permitting a hold.)
1238 My Account includes the ability to view current ebook checkouts and
1239 holds, download already-checked-out titles, and cancel holds.
1241 For API integration to work, you need to request API access from the
1242 vendor, and the vendor must have a way of authenticating your patrons.
1243 Your Evergreen system also needs to be configured for ebook API
1244 integration, following the instructions in the command line system
1245 administration manual
1248 This feature assumes that you are importing MARC records supplied by the
1249 vendor into your Evergreen system, using Vandelay or some other MARC
1250 import method. This feature does not search the vendor's online
1251 collections or automatically import vendor records into your system; it
1252 merely augments records that are already in Evergreen.
1254 Improvements to Bill Payment Pages
1255 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1256 The bill payment pages in the public catalog have been revamped
1259 * use the term "charges" instead of "fees"
1260 * include images of credit cards accepted
1261 * make the default print receipt template match other itemized receipts;
1262 note that this change is not automatically applied when upgrading.
1263 * display billing type
1264 * add button to pay only selected charges
1265 * reformat the credit card number input page
1271 Clickable Copy Locations
1272 ^^^^^^^^^^^^^^^^^^^^^^^^
1273 Adds a URL field to the copy locations editor. When a URL is entered in this field,
1274 the associated copy location will display as a link in the public catalog summary display.
1275 This link can be useful for retrieving maps or other directions to the copy
1276 location to aid users in finding material.
1281 Download Checkout History CSV Fixed for Large Number of Circulations
1282 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1283 Downloading checkout history as a CSV from My Account has been fixed
1284 for users with a large circulation history. Previously, this would
1285 time out for patrons with more than 100 or so circulations.
1287 This feature no longer uses the action/trigger mechanism and the public catalog
1288 now generates the CSV directly. The old action/trigger code is still
1289 present in the database and should be removed at some point in the
1295 Google Books Preview Rewrite
1296 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1297 The Google Books Preview functionality in record detail pages has been
1298 rewritten to modernize its style and optimize its performance:
1300 * The Dojo JavaScript framework is no longer used, saving approximately
1301 150K of JavaScript and CSS and four network requests per page load.
1302 * The Embedded Viewer is not loaded unless a possible preview is found,
1303 saving more network and memory overhead.
1304 * The Google Books Loader is used to load the Embedded Viewer instead of the
1305 https://productforums.google.com/forum/#!topic/books-api/lZrq5cWKrTo;context-place=forum/books-api[deprecated
1307 * All variables are self-contained and do not pollute the global namespace.
1308 * Event listeners are registered to handle clicks, rather than attaching
1309 `href="javascript:function()"` to <a> elements.
1310 * Book previews are displayed in a panel sized according to the viewport
1311 of the browser, improving its appearance on both mobile and desktop
1313 * The rewritten code is now served up directly from
1314 `/js/ui/default/opac/ac_google_books.js` rather than as a TT2 template.
1319 jQuery for the Public Catalog
1320 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1321 This release adds optional support for jQuery in the public catalog. This support
1322 is enabled by setting the `ctx.want_jquery` variable to a true value in the
1323 `config.tt2` template.
1329 New Popularity Parameters
1330 ^^^^^^^^^^^^^^^^^^^^^^^^^
1331 New popularity parameters for in-house use over time and for count of distinct
1332 organizational units that own a title are now available. Evergreen sites
1333 can use these parameters to create new statistical popularity badges for
1334 sorting in the catalog by Most Popular or by Popularity-Adjusted Relevance.
1336 The in-house use parameters will apply a badge to titles that have the most
1337 in-house use activity over time. The organizational unit count parameter
1338 will apply a badge to titles owned by the most number of libraries in a
1339 consortium. Ownership is determined by the copy's circulation library.
1344 Option to Suspend Holds at the Time They are Placed
1345 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1346 Users now have the option to suspend a hold at the same time they place the
1347 hold. The 'Place Hold' screen has a checkbox that can be enabled for users
1348 who want to suspend a hold at the time it is placed. There is also an option
1349 to set the activation date at the same time. This option is also available
1350 when placing holds on a batch of titles from 'My List' and will apply to
1351 all the titles in the batch.
1362 Fix to reporter.classic_current_circ View
1363 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1364 The `reporter.classic_current_circ` view, which is part of some
1365 extra views defined in `Open-ILS/src/sql/Pg/example.reporter-extension.sql`,
1366 has been fixed to not exclude loans for patrons who do not have a
1367 billing address set. Users of this view should rerun
1368 `Open-ILS/src/sql/Pg/example.reporter-extension.sql` during upgrade.
1373 New Report Source Table Allowing Report of "Last" Deleted copy
1374 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1376 This source table allows you to construct a clever aggregate report template
1377 which will report bibliographic IDs where a library or a group of libraries
1378 no longer have a copy attached but *had* a copy attached. This is especially
1379 useful when a holdings sync is required with an external vendor.
1382 Instructions for creating a report template with this source:
1384 * Create a new report template using "Library Holdings Count with Deleted" as the source
1385 * Add "Has Only Deleted Copies 0/1" (Min) to the Aggregate Filters -> Change Value to "1"
1386 * Add "Last Edit Date" (Max) to Aggregate Filters. In Aggregate Filters, change the operator to "Between"
1387 * Add Circulation Library -> "Organizational Unit ID" to Base Filters, with the Raw Data transform. In the list of Base Filters, change the operator to "In list"
1388 * Add "Bib ID" to Displayed Fields
1389 * Add "Last Edit Date" to Displayed Fields and Change Transform to Max
1390 * Add "Has Only Deleted Copies 0/1" to Displayed Fields and Change Transform to Min
1391 * Add "Total copies attached" to Displayed Fields and Change Transform to Sum
1394 This template will only output bibliographic IDs where all of the copies for the specified branch(es)
1395 are deleted. Furthermore, it will only output bibs whose copies were edited (deleted) during the
1396 specified date range. Unfortunately the user will have to manually type the date range without the date
1397 picker. This view will also allow you to answer questions like "Show me bibs where I have one visible
1398 copy and more than two deleted copies."
1403 Add Provider to Provider Note Link
1404 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1405 The Provider reporting source now includes a link to the Provider Note reporting source.
1410 Link ILS User and Working Location Reporting Sources
1411 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1412 The Working Location reporting source now has labels
1413 and it is now linked to the ILS User reporting source, allowing
1414 reports to display or filter on staff working location.
1419 New Circulation Report Source "All Circulation Combined Types"
1420 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1422 This report source will allow you to create a single report template for all of the following:
1425 * In-house uses of non-cataloged items
1427 * Circulations of non-cataloged items
1429 To distinguish between these different types of library use, it's important to display these columns
1430 in your report templates:
1439 Reports Template Searching
1440 ^^^^^^^^^^^^^^^^^^^^^^^^^^
1441 A new form appears along the top of the reports interface for searching
1442 report templates. Once found, typical template actions (e.g. create new
1443 report) are available from within the results interface.
1445 Searches may be performed across selected (visible) folders or all
1446 folders visible to the logged in user.
1448 Searches are case-insensitive, any word order, with left-anchored words.
1449 All searched words must appear in at least one of the searched fields.
1454 * Searching for 'stat cat' matches:
1456 ** statistical category
1457 ** categories, statistical
1458 ** patrons (stat cat)
1459 * Searching for 'stat cat' does not match:
1461 *** both words must be present in the searched field(s)
1463 *** location contains 'cat' but it's not left-anchored.
1468 The templates, reports, and output interfaces now support paging via
1469 new 'Next', 'Prev', and 'Start' links next to the output limit selector.
1481 Web Staff Client Serials Module
1482 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1483 The serials module has been ported over to the web staff
1484 client, implementing a unified serials interface that combines
1485 ideas from both the serial control view and alternate serials
1486 control view from the old staff client.
1488 In addition to carrying over functionality that was available
1489 in the old staff client, several new features are included:
1491 * the ability to save prediction pattern codes as templates
1492 that can be shared and reused within an Evergreen database
1493 * a more streamlined interface for managing subscriptions,
1494 distributions, and streams
1495 * it is no longer necessary to create a starting issue in
1496 order to predict a run of issues; the dialog box for
1497 generating a set of predicted issues now lets you specify
1498 the starting point directly.
1499 * the ability to more directly edit MFHDs
1501 The new serials interfaces can be accessed from the record
1502 details page via a Serials drop-down button that links to
1503 a subscription management page, a quick-receive action, and
1504 a MFHD management page. There is also a new 'Serials Administration'
1505 page where prediction pattern and serial copy templates can
1516 SIP Bugfix Changes How Encoding Is Determined in Configuration
1517 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
1519 The combined fix for the above mentioned SIP bugs alters the way that
1520 SIPServer looks up the output encoding in the configuration file (typically
1521 `oils_sip.xml`). SIPServer now looks for the encoding in the following
1524 1. An +encoding+ attribute on the +account+ element for the currently active SIP account.
1525 2. The +encoding+ element that is a child of the +institution+ element of the currently active SIP account.
1526 3. The +encoding+ element that is a child of the +implementation_config+ element that is itself a child of the +institution+ element of the currently active SIP account.
1527 4. If none of the above exist, then the default encoding (ASCII) is used.
1529 Number 3 is provided to ease the transition to the new code. It is
1530 the current location of the +encoding+ element in the sample
1531 configuration file and as such, where it is likely to be found in
1532 actual files. It is recommended that you alter your configuration to
1533 move this element out of the +implementation_config+ element and into
1534 its parent +institution+ element. Ideally, SIPServer should *not* look into
1535 the implementation config, and this check may be removed at some time
1543 Web Client Acknowledgments
1544 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
1546 The project to develop a new browser-based web client launched four
1547 years ago at the September 2013 Evergreen developer hack-a-way when the
1548 developer community voted to move away from the XUL client and explore other
1549 platforms. The first web client preview became available in Evergreen 2.7 when
1550 circulation was available in the new platform.
1552 The browser-based client is available due to the work of many coders, testers,
1553 bug reporters, documentors, translators, project managers, spec writers, funders
1554 and other contributors over the past four years.
1556 The Evergreen project would like to acknowledge the following organizations
1557 that funded development of the Web Staff Client:
1560 * British Columbia Libraries Cooperative
1561 * Consortium of Ohio Libraries
1563 * Georgia Public Library Service
1564 * Grand Rapids Public Library
1566 * Kenton County Public Library
1567 * King County Library System
1570 * Pennsylvania Integrated Library System
1571 * Pioneer Library System
1574 The Evergreen project would also like to thank the following individuals who
1575 contributed code, translations, documentation patches, tests, bug reports,
1576 technical specifications, and project management to the Web Staff Client:
1613 * Freddy Enrique Pelayo Huapalla
1639 Evergreen 3.0 Acknowledgments
1640 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1642 The Evergreen project would like to acknowledge the following
1643 organizations that commissioned developments in this release of
1647 * British Columbia Libraries Cooperative (BC Sitka)
1649 * Georgia Public Library Service
1650 * King County Library System
1652 * Pennsylvania Integrated Library System
1653 * Pioneer Library System
1655 We would also like to thank the following individuals who contributed
1656 code, translations, documentation patches, and tests to this release of
1705 We also thank the following organizations whose employees contributed
1708 * British Columba Libraries Cooperative
1712 * Emerald Data Networks, Inc.
1713 * Equinox Open Library Initiative
1715 * Grand Rapids Public Library
1716 * Indiana State Library
1718 * King County Library System
1719 * Lake Agassiz Regional Library
1720 * Laurentian University
1721 * Linn-Benton Community College
1723 * Merrimack Valley Library Consortium
1725 * North of Boston Library Exchange
1726 * Pennsylvania Integrated Library System
1727 * Pohjois-Karjalan Tietotekniikkakeskus Oy
1729 * Traverse Area District Library
1731 We regret any omissions. If a contributor has been inadvertently
1732 missed, please open a bug at http://bugs.launchpad.net/evergreen/