1 Evergreen 3.1 Release Notes
2 ===========================
8 This release contains bug fixes improving on Evergreen 3.1.3. Note that
9 all bug fixes refer to the web staff client unless otherwise specified.
14 * Fixes right-click issues with the Web client grids
15 * Fixes an issue with the Default SMS Carrier in the patron edit form.
16 * Fixes an issue that allowed overdue notices to be sent to a patron
17 whose long overdue item has been paid for.
18 * Checking in precat items now displays the "Route to Cataloging" alert each
19 time the item is checked in.
20 * Fixes an issue in which the Adjust to Zero feature
21 does not close a checked-in lost circ.
22 * Deleted copies that are still checked out can now be checked in.
23 * Fixes a mislabeled column in the patron checkout grid.
24 * Fixes an error with the missing pieces functionality.
25 * Courier codes now display in the transit slip receipt preview.
26 * The Item Status grid now displays OU shortnames instead of full names
27 for the "Circulation Library" column.
28 * The Volume/Copy editor now allows users to remove a value from the Age
29 Hold Protection field.
30 * Barcode completion now works in copy buckets.
31 * The Z39.50 interface now notices when another record has been marked
33 * Fixes a display issue for the Remove MARC Field Groups checkboxes in
35 * Fixes a performance issue for the Validate button in the MARC Editor.
36 * Fixes an incorrect close tag in the Print Item Labels toolbar.
37 * Better scoping of copy tags in search results.
38 * Electronic Resource links now open in a new tab.
39 * Fixes an issue with the fiscal year close-out operation.
43 We would like to thank the following individuals who contributed code,
44 tests and documentation patches to the 3.1.4 point release of
67 This release contains bug fixes improving on Evergreen 3.1.2. Note that
68 all bug fixes refer to the web staff client unless otherwise specified.
73 * Fixes specific cases in which deleted records appear in search results.
74 * Fixes a performance issue with deleting patrons.
75 * The hold shelf dialog popup now lists the patron's notification
77 * Fixes an issue that prevented editing items when a monograph part
79 * Patron information is now available for use in the bills_current
80 and bills_historical receipt templates.
81 * The browser's "This page may contain unsaved data" warning now
82 appears when users click the update
83 expire date button in a patron account and attempt to navigate away
85 * The holds tab of the patron record now includes a monograph part
87 * The barcode box in the checkout screen
88 no longer hovers above patron record tabs when
89 staff users scroll down.
90 * Fixes an issue with the date of birth in the patron edit scren.
91 * The patron account bills grid are now color-coded by the item's
93 * Fixes an issue with the dropdown of billing type options.
94 * The Item Status screen now includes as a floating group column.
98 We would like to thank the following individuals who contributed code,
99 tests and documentation patches to the 3.1.3 point release of
102 * BC Libraries Cooperative
109 * Blake Graham-Henderson
129 This release contains bug fixes improving on Evergreen 3.1.1. Note that
130 all bug fixes refer to the web staff client unless otherwise specified.
138 * The MARC editor now handles 008 fields better.
139 * Adds spaces between subfields when suggesting a call
140 number for a new volume.
141 * MarcXML exports from the MARC Batch Import/Export ->
142 Export Records screen now downloads the file, rather than opening
144 * The Item Status Circulation Library column now displays a
145 shortname rather than the full library name.
146 * The Item Status Remaining Renewals column now displays
148 * The Item Status now has a "Last Renewal Workstation" column
150 * Fixes the circulation counts displayed in Item Status Details.
151 * Removes an error that got thrown in the Holdings View when a call number
153 * Fixes an issue where multiple copies with different values for required
154 statistical categories could not be edited and saved in batch.
155 * Add an option to remove floating in the copy editor.
156 * Fixes an issue with the floating dropdown in the copy editor.
157 * Fixes a problem in which the copy template didn't properly copy
159 * Reduces the number of API calls that the MARC Editor requires.
160 * The order of the Z39.50 servers on the Z39.50 import screen
161 no longer relies on capitalization.
166 * Fixes an issue that prevented the offline patron registration
168 * Fixes an issue with searching patrons by permission group.
169 * The barcodes in the patron search are now clickable.
170 * Staff members can now manually override the patron juvenile
171 flag value, regardless of the patron's date of birth.
172 * Checkboxes on patron registration screen are now properly aligned
174 * The user permission group dropdowns in the patron registration,
175 edit, and search interfaces now have scrollbars.
176 * The date picker on the checkout screen is now hidden unless
177 circ staff activates a specific due date option.
178 * The check-in screen now includes a copy status column.
179 * The Merge Patrons interface now displays the date of birth.
180 * The user bucket screen now displays the Bucket ID.
181 * The payment button on patron bills screen is now inactive if the
182 Payment Received field is blank.
183 * The Bill History receipt now includes a Finish date and a Last
185 * When a patron summary contains an image of the patron,
186 that image tag now has a null alt attribute to remove it from
187 the flow of a screen reader.
188 * Corrects an issue that caused the transit dialog to show the
190 * Corrects an issue with printing transit lists.
191 * "Find another target" on transiting hold no longer leaves the
193 * The images now display to distinguish hold and transit slips.
194 * The Clearable Holds list printout now only shows holds that have
196 * Restores the call number prefix and suffix fields to the holds
198 * The documentation at the top of the hold shelf slip template
200 * The cursor in the in-house use screen now automatically goes
201 to the barcode field.
202 * The in-house use screen now shows a copy status column.
203 * Add support for converting change to patron credit in the patron bills
204 interface, consistent with the XUL feature.
205 * Fixes a bug that caused pickup/request library fields to be
207 * Fixes a bug in the offline org unit tree.
209 Command-line system administration
210 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
212 * The novelist entry in `eg_vhost.conf` includes two new
214 * Corrects an issue with the `--max-sleep` argument on the
215 `action_trigger_runner.pl` support script.
216 * Corrects an issue with how the `eg_pbx_allocator.pl` script
217 detects an existing lock file.
218 * The 3.0.2-3.0.3 upgrade script disables triggers before
219 recalculating bib visibility.
224 * Fixes an issue that caused records with located URIs to be
225 retrieved in Copy Location and Copy Location Group searches.
226 * Fixes an error message that appeared in the search box
227 in the public catalog while placing hold after an advanced search.
228 * Restores the display of copy information for the user's
229 preferred library in the public catalog.
230 * Author and contributor names are no longer highlighted in
231 search results when the user has turned off highlighting.
232 * Fixes regression errors in the search results page.
233 * Removes redundant call numbers from the Show More Details
235 * The cast field in the catalog is now taken from the 511 field
236 when first indicator = 1, rather than the 508.
237 * Fixes a display issue caused by editing holds.
238 * Repairs broken author search links on the catalog record page.
243 * Fixes an issue that prevented users from searching for
244 receivable issues using Database ID or ISSN in the Serials
245 Batch Receive interface.
249 * Pins AngularJS support to version 1.6, which prevents unsupported
250 AngularJS versions (such as 1.7) from breaking the build process.
251 * Adds some padding to the bottom of Web Client interfaces.
252 * Logins now honor all org unit timeout settings.
253 * Evergreen will now identify and handle invalid timezones.
254 * Fixes an issue where a column header in some interfaces were automatically
255 highlighted in green when retrieving the interface.
256 * The parts column in the Item Status screen now displays parts data.
261 We would like to thank the following individuals who contributed code,
262 tests and documentation patches to the 3.1.2 point release of
298 This release contains bug fixes improving on Evergreen 3.1.0.
300 * Fixes a performance issue with the Patron Billing History screen and
301 other screens that cause Flattener.pm to re-create joins
303 * Fixes an issue that prevented patron alerts from showing to staff at
305 * Corrects the "Holdable" attribute display on the Item Status detailed
307 * Fixes the ability to delete multiple copies from Item Status.
311 We would like to thank the following individuals who contributed code,
312 tests and documentation patches to the 3.1.1 point release of
327 Like many major Evergreen upgrades, 3.1 requires a full reingest of your
328 bibliographic records before the system is usable again. While a basic reingest
329 is included at the end of the upgrade script, it happens after the main
330 COMMIT, so it is safe to cancel that and run the required reingest as you see
331 fit (e.g. via pingest.pl).
340 New Latency Tester Tool
341 ^^^^^^^^^^^^^^^^^^^^^^^
342 The Evergreen Web Staff Client now includes a section called *Tests* linked from
343 *Administration -> Workstation*. The *Tests* page houses a simple tool
344 that can be used to test the latency of the websocket connection between the
345 client and the server (via the `opensrf.echo` service).
347 This page displays which Evergreen host server is being queried. Upon hitting
348 the blue "Start Test" button for the first time, it will issue 10 sequentially
349 fired requests in order to get a solid initial average. Clicking the button a
350 second time will take one more measurement and recalculate the average
351 latency. The results can be copied to clipboard for troubleshooting purposes
352 and also cleared from display.
354 marc_export --uris option
355 ^^^^^^^^^^^^^^^^^^^^^^^^^
356 The marc_export support script now has a `--uris` option (short form:
357 `-u`) to export records with located URIs (i.e. electronic resources). When
358 used by itself, it will export only records that have located URIs. When
359 used in conjunction with `--items`, it will add records with located URIs
360 but no items/copies to the output. If combined with a `--library` or
361 `--descendants` option, this option will limit its output to those
362 records with URIs at the designated libraries. The best way to use
363 this option is in combination with the `--items` and one of the
364 `--library` or `--descendants` options to export *all* of a library's
365 holdings both physical and electronic.
371 Sample Data Includes Surveys
372 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
373 The Concerto sample data set now includes patron surveys, questions,
374 answers, and responses.
376 Virtual Index Definitions
377 ^^^^^^^^^^^^^^^^^^^^^^^^^
378 The practical purpose of Virtual Index Definitions is to supply an Evergreen
379 administrator with the ability to control the weighting and field inclusion of
380 values in the general keyword index, commonly referred to as "the blob,"
381 without requiring tricky configuration that has subtle semantics, an
382 over-abundance of index definitions which can slow search generally, or the
383 need to reingest all records on a regular basis as experiments are performed
384 and the configuration refined. Significant results of recasting keyword indexes
385 as a set of one or more Virtual Index Definitions will be simpler search
386 configuration management, faster search speed overall, and more practical
387 reconfiguration and adjustment as needed.
389 Previously, in order to provide field-specific weighting to
390 keyword matches against titles or authors, an administrator must duplicate many
391 other index definitions and supply overriding weights to those duplicates. This
392 not only complicates configuration, but slows down record ingest as well as
393 search. It is also fairly ineffective at achieving the goal of weighted keyword
394 fields. Virtual Index Definitions will substantially alleviate the need for
395 these workarounds and their consequences.
397 * A Virtual Index Definition does not require any configuration for
398 extracting bibliographic data from records, but instead can become a sink for
399 data collected by other index definitions, which is then colocated together to
400 supply a search target made up of the separately extracted data. Virtual Index
401 Definitions are effectively treated as aggregate definitions, matching across
402 all values extracted from constituent non-virtual index definitions. They can
403 further make use of the Combined class functionality to colocate all values in a
404 class together for matching even across virtual fields.
406 * Configuration allows for weighting of constituent index definitions that
407 participate in a Virtual Index Definition. This weighting is separate from the
408 weighting supplied when the index definition itself is a search target.
410 * The Evergreen QueryParser driver returns the list of fields actually
411 searched using every user-supplied term set, including constituent expansion
412 when a Virtual Index Definition is searched. In particular, this will facilitate
413 Search Term Highlighting described below.
415 * Stock configuration changes make use of pre-existing, non-virtual index
416 definitions mapped to new a Virtual Index Definition that implements the
417 functionality provided by the `keyword|keyword` index definition. The
418 `keyword|keyword` definition is left in place for the time being, until more data
419 can be gathered about the real-world effect of removing it entirely and
420 replacing it with Virtual Index Definition mappings.
422 * New system administration functions will be created to facilitate
423 modification of Virtual Index Definition mapping, avoiding the need for a full
424 reingest when existing index definitions are added or removed from a virtual
427 Increased use of Metabib Display Fields
428 +++++++++++++++++++++++++++++++++++++++
429 We use Metabib Display Fields (newly available in 3.0) to render catalog search
430 results, intermediate metarecord results, and record detail pages. This requires
431 the addition of several new Metabib Display Field definitions, as well as Perl
432 services to gather and render the data.
434 We also use more Metabib Display Fields in the client. As a result,
435 bibliographic fields will display in proper case in more client interfaces and
436 in Evergreen reports.
440 A new AngularJS "MARC Search/Facet Fields" interface has been created to replace
441 the Dojo version, and both have been extended to support Virtual Index
442 Definition data supplier mapping and weighting.
444 Settings & Permissions
445 ++++++++++++++++++++++
446 The new Virtual Index Definition data supplier mapping table,
447 `config.metabib_field_virtual_map`, requires the same permissions as the
448 MARC Search/Facet Fields interface: CREATE_METABIB_FIELD, UPDATE_METABIB_FIELD,
449 DELETE_METABIB_FIELD, or ADMIN_METABIB_FIELD for all actions
453 There now exist several new database tables and functions primarily in support
454 of search highlighting. Additionally, the QueryParser driver for Evergreen has
455 been augmented to be able to return a data structure describing how the search
456 was performed, in a way that allows a separate support API to gather a
457 highlighted version of the Display Field data for a given record.
461 By default, the following fields will be weighted more heavily in keyword
462 searches. Administrators can change these defaults by changing the values in the
463 "All searchable fields" virtual index in the "MARC Search/Facet Fields"
467 * Main title (a new index limited to the words in the 245a)
471 In addition, note indexes and the physical description index will receive
472 less weight in default keyword searches.
474 Re-ingest or Indexing Dependencies
475 ++++++++++++++++++++++++++++++++++
476 With the addition and modification of many Index Definitions, a full reingest is
477 recommended. However, search will continue to work as it did previously
478 for those records that have not yet been reingested. Therefore a slow, rolling
479 reingest is recommended.
481 Performance Implications or Concerns
482 ++++++++++++++++++++++++++++++++++++
483 Because the Metabib Display Fields infrastructure will eventually replace
484 functionality that is significantly more CPU-intensive in the various forms of
485 XML parsing, XSLT transformation, XPath calculation, and
486 Metabib Virtual Record construction, it is expected that the overall CPU load
487 will be reduced by this development, and ideally the overall time required to
488 perform and render a search will likewise drop. It is unlikely that the speed
489 increase will be visible to users on a per-search basis, but that search in
490 aggregate will become a smaller consumer of resources.
498 When 2 or more bib records are merged, all records involved are stamped
499 with a new `merge_date` value. For any bib record, this field indicates
500 the last time it was involved in a merge. At the same time, all
501 subordinate records (i.e. those deleted as a product of the merge) are
502 stamped with a `merged_to` value indicating which bib record the source
503 record was merged with.
505 In the browser client bib record display, a warning alert now appears
506 along the top of the page (below the Deleted alert) indicating when a
507 record was used in a merge, when it was merged, and which record it was
508 merge with, rendered as a link to the target record.
514 Alternate Patron Hold Pickup
515 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
516 This feature adds a bit of convenience to a common task: checking out
517 an item on hold to another patron (typically a family member or helper).
519 When you checkout the item, you will get a pop-up window with warnings associated
520 with this item. The "ITEM_ON_HOLDS_SHELF" message is now expanded to
522 * Let you know the name of the person who had placed the hold.
523 * Give you the option (in the form of a checkbox) of cancelling the
524 hold placed by the above-named patron. (Checked = Cancel the hold;
525 Unchecked = Leave the hold in place)
527 The initial value of the checkbox is derived from the
528 `circ.clear_hold_on_checkout` organizational setting.
530 If the operator has CANCEL_HOLD privilege, then if the checkbox is checked and
531 the checkout is allowed to proceed, the hold will be cancelled with a note that
532 the item was checked out to another patron.
534 This feature is available in the browser-based staff client.
536 New Patron Billing Statement
537 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
538 The Evergreen web staff client now includes a patron billing statement,
539 which summarizes a patron's bills, credits and payments in a familiar
540 layout. This can be found on the "Statement" tab of the Patron Bill
541 Details page. (From the Patron Bills page, double-click a row to view
542 its details, or choose "Full Details" from the Actions menu.)
544 Enhanced Billing Timestamp Support
545 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
546 Previously, billings had to make do with a single timestamp attempting
547 to fill two different roles. In the case of an overdue fine, the
548 timestamp represented the *end* of the fine period for that billing,
549 while for all other fines, the timestamp was merely the time the bill
550 was created. This setup generally worked, but not without confusion,
551 and limited our ability to understand and process the data.
553 Billings will now have up to three timestamps: a create date, and when
554 applicable, a fine period start and a fine period end. This clarifies
555 and simplifies things like backdating, retrospective fine generation,
556 account balancing for negative balance avoidance, and billing timeline
559 Copy Alerts and Suppression Matrix
560 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
561 The Copy Alerts feature allows library staff to add customized alert
562 messages to copies. The copy alerts will appear when a specific event
563 takes place, such as when the copy is checked in, checked out, or
564 renewed. Alerts can be temporary or persistent: temporary alerts will be
565 disabled after the initial alert and acknowledgement from staff, while
566 persistent alerts will display each time the alert event takes place.
567 Copy Alerts can be configured to display at the circulating or owning
568 library only or, alternatively, when the library at which the alert
569 event takes place is not the circulating or owning library. Copy Alerts
570 can also be configured to provide options for the next copy status that
571 should be applied to an item. Library administrators will have the
572 ability to create and customize Copy Alert Types and to suppress copy
573 alerts at specific org units.
575 Copy alerts can be added via the volume/creator and the check in,
576 check out, and renew pages. Copy alerts can also be managed at the
579 Copy alert types can be managed via the Copy Alert Types page in
580 Local Administration, and suppression of them can be administered
581 via the Copy Alert Suppression page under Local Administration.
583 Place Multiple Holds At Once
584 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
585 Users with the appropriate permissions now have the ability to place multiple
586 title/metarecords holds at once. This feature is especially beneficial for book
587 clubs and reading groups, which need to place holds on multiple copies of a
590 In order to use the feature:
592 * Set the _Maximum number of duplicate holds allowed_ Library Setting
593 (`circ.holds.max_duplicate_holds`) to a number higher than 1
594 * Log in as a user with the CREATE_DUPLICATE_HOLDS
596 When placing a title or metarecord hold, a _Number of copies_ field will
597 display for these users. This field is not available when placing part, volume
600 This feature does not change the way in which the system fills holds. The
601 multiple holds will fill in the same way that they would if the user had placed
602 multiple holds separately.
604 New Notice Columns in Items Out Grid
605 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
606 The grid in the patron "items out" page in the Evergreen web staff client has two new
607 columns indicating the number of notifications generated for a given loan and the date of
608 the most recent notification. These columns will allow circulation staff to better respond to
609 patron questions about whether they were sent notification about an overdue item.
611 The columns are based on the number of completed Action Trigger events on the
612 loan that have a 'checkout.due' hook. In other words, they would include overdue
613 and courtesy notices.
615 A new library setting, "Exclude Courtesy Notices from Patrons Itemsout Notices Count",
616 if set will cause the notice count and date fields to exclude courtesy notices.
618 Patron Email Addresses Now Clickable In Web Staff Client
619 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
620 Adds a mailto link to the patron's email in their profile so it can
621 be clicked to send and email to the patron. No new settings or
622 permissions are included in this feature.
624 Pickup Library for Staff-placed Holds
625 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
626 Adds a new library setting, _circ.staff_placed_holds_fallback_to_ws_ou_,
627 that helps determine the hold pickup library in cases where patrons don't
628 have a preferred hold pickup library in their account and a staff member
629 is placing the hold on their behalf.
631 * When this setting is true and the patron doesn't have a preferred
632 library listed, the hold pickup library will default to the
633 workstation's organizational unit.
634 * When this setting is false and the patron doesn't have a preferred
635 library listed, the hold pickup library will default to the
636 patron's home library.
641 Search Term Highlighting
642 ^^^^^^^^^^^^^^^^^^^^^^^^
643 Evergreen now highlights search terms on the public catalog's main search
644 results page, the record detail page, and intermediate pages such as metarecord
645 grouped results page. Highlighting search terms will help the user determine why
646 a particular record (or set of records) was retrieved.
648 Highlighting of matched terms uses the same stemming used to accomplish the
649 search, as configured per field and class.
651 This feature will help the user more quickly determine the relevance of a
652 particular record by calling their attention to search terms in context. Lastly,
653 it will help familiarize the user with how records are searched, including which
654 fields are searched as well as exposing concepts like stemming.
656 You can turn off search term highlighting by uncommenting the line
657 `search.no_highlight = 1;` in `config.tt2`.
659 When highlighting is generally enabled, it may be turned on or off on a per-page
660 basis through the use of a UI component which will request the page again
661 without highlighting.
663 Highlighting of terms uses Template::Toolkit-driven CSS. A generic CSS class
664 identifying a highlighted term, along with CSS classes identifying the search
665 class and each search field are available for use for customization of the
666 highlighting. A stock CSS template is provided as a baseline upon which sites
670 Copy Location Filter Displays for System Searches
671 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
672 The Shelving Location filter now displays on the advanced search page when
673 a search is scoped to a library system, not just to an individual branch. If
674 a library system is selected as the Search Library, the shelving location
675 limiter will display any shelving location that is owned by the selected system
676 or by the consortium. It will NOT display shelving locations owned by child
679 Multi-source Attributes
680 ^^^^^^^^^^^^^^^^^^^^^^^
681 We now allow record attribute definitions to extract data using more than
682 one strategy (XPath, tag+subfield, fixed field, etc.) as long as the values
683 from various sources would, after normalization, have the same shape.
687 This change allows us to configure multilingual search, by extracting values
688 from both the 008 controlfield and the 041 datafield. Because the values
689 in each can be normalized to the same controlled list (and, in practice, are
690 already from the same normalized value set), catalog searches can now use normal
691 boolean search semantics to find records with various combinations of
694 E.g., in the concerto test data:
696 * `keyword: piano item_lang(eng) item_lang(ita)`
699 Optional Display of Badges in Catalog
700 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
701 A new setting controls whether badges (popularity, etc.) are displayed
702 in the catalog. If you do not wish badges to be displayed, set the
703 `ctx.hide_badge_scores` setting to "true" in `config.tt2`.
709 Fixes to patron name/username search indexes
710 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
711 When using pg_restore to restore an Evergreen database, some of the
712 indexes used to speed up patron searches on names and usernames
715 This release fixes the underlying issue and re-creates the indexes
720 When using pg_restore to restore an affected database, the
721 "unaccent" indexes on actor.usr would not be created due to an
722 unqualified function reference in `evergreen.unaccent_and_squash`.
724 The function will be replaced to resolve the search path issue,
725 and the following indexes on actor.usr will be dropped and then
728 * actor_usr_first_given_name_unaccent_idx;
729 * actor_usr_second_given_name_unaccent_idx;
730 * actor_usr_family_name_unaccent_idx;
731 * actor_usr_usrname_unaccent_idx;
733 This will be done even if the indexes are already present, and may
734 take a few minutes on a database with many patrons.
737 3.1.0 Acknowledgments
738 ---------------------
739 The Evergreen project would like to acknowledge the following
740 organizations that commissioned developments in this release of
743 * Albany Public Library (Oregon)
744 * Consortium of Ohio Libraries
746 * Indiana State Library
747 * Georgia Public Library Service
748 * Hagerstown - Jefferson Township Library
749 * Linn-Benton Community College
751 * Pennsylvania Integrated Library System
752 * Sage Library System
753 * Union County Public Library (Indiana)
755 We would also like to thank the following individuals who contributed
756 code, translations, documentations patches and tests to this release of
783 We also thank the following organizations whose employees contributed
787 * British Columbia Libraries Cooperative
790 * Equinox Open Library Initiative
791 * Georgia Public Library Service
792 * Greater Clarks Hill Regional Library System
793 * Jordanian Library and Information Association
794 * King County Library System
796 * Linn-Benton Community College
799 * Traverse Area District Library
801 We regret any omissions. If a contributor has been inadvertently
802 missed, please open a bug at http://bugs.launchpad.net/evergreen/
projects / Evergreen.git / blob