HomeTroubleshooting Evergreen 3.1Printer Friendly Version

Troubleshooting Evergreen 3.1

These are the known issues, questions, and resources to help NC Cardinal library staff troubleshoot issues with Evergreen 3.1

1. Known Issues

1.1. Known Issues with Evergreen 3.1

Below is a list of known issues with Evergreen 3.1. These are generally issues that are being addressed in the continued development of Evergreen. If there are bugs associated with the issue, you can learn more information about the bug and expected fix timeline by following the bug link to Launchpad. Add heat  to the bugs you would like to see fixed quickly. Just create an Ubuntu account (if you don't have one already), click on the little yellow circle,

and choose "Yes, it affects me".


SummaryStatusDateBug Link
Archived Penalties/Messages Does Not Respect Date Range


https://bugs.launchpad.net/evergreen/+bug/1775940
Some Columns Are Not Sortable in the Web Client


https://bugs.launchpad.net/evergreen/+bug/1437104
Keyboard shortcuts work differently depending on which screen - OPAC or staff client side


https://bugs.launchpad.net/evergreen/+bug/1437106

https://bugs.launchpad.net/evergreen/+bug/1622358

https://bugs.launchpad.net/evergreen/+bug/1697003

Family Patron Groups Listings


https://bugs.launchpad.net/evergreen/+bug/1642036
Merging Patrons in Collections


https://bugs.launchpad.net/evergreen/+bug/1810854
Pull List Printing


https://bugs.launchpad.net/evergreen/+bug/1749502
Editing Call Numbers from Item Status (Edit Volume Screen is blocked out)


https://bugs.launchpad.net/evergreen/+bug/1795478

https://bugs.launchpad.net/evergreen/+bug/1746536

Selecting and Sorting the Holds Shelf Information Has Limitations


https://bugs.launchpad.net/evergreen/+bug/1712854
Parent/Guardian Field Has Been Renamed on Patron Registration Form


https://bugs.launchpad.net/evergreen/+bug/1762480
Copy Alerts Transferred to Web Client and No Longer in XUL Staff Client


https://bugs.launchpad.net/evergreen/+bug/1676608
https://bugs.launchpad.net/evergreen/+bug/1783421
Limited/Incorrect MARC Information Display in Catalog Search Results


https://bugs.launchpad.net/evergreen/+bug/1770454

https://bugs.launchpad.net/evergreen/+bug/1791662

Receiving "Blank Screen" When Using Catalog Searching Features


https://bugs.launchpad.net/evergreen/+bug/1797923
Receiving Green Screen When Attempting To Place Holds


https://bugs.launchpad.net/evergreen/+bug/1737808
Inconsistent Search Results for E-book


https://bugs.launchpad.net/evergreen/+bug/1798910
Updating User Permission Groups

https://bugs.launchpad.net/evergreen/+bug/979922
Receiving "Unhandled Error" Update Alert in XUL Staff Client

(New functionality, not a bug)
Remaining Renewals Decrease When Manual  Refresh Is Needed to Complete a Renewal Transaction

https://bugs.launchpad.net/evergreen/+bug/1803753

Unable To Hide the "Credits Available" Field in the 3.1.6 Web Client

https://bugs.launchpad.net/evergreen/+bug/1803765

A Long List of Billing Ids Display in Void Billing Confirmation Message

https://bugs.launchpad.net/evergreen/+bug/1698865
Unable to Delete Pending Patrons Using the Web Client



https://bugs.launchpad.net/evergreen/+bug/1737800
Unable to Delete Call Number Prefixes and Suffixes

https://bugs.launchpad.net/evergreen/+bug/1713120 

Placing Multiple Holds in My List Leads to Error

https://bugs.launchpad.net/evergreen/+bug/1687319

Problems cloning & running reports in web client with templates created in XUL



https://bugs.launchpad.net/evergreen/+bug/1642344
https://bugs.launchpad.net/evergreen/+bug/1796945

You may also be interested Sitka's Known Issues page at: https://bc.libraries.coop/support/sitka/evergreen-upgrade/

Web Client Issues

Resolving Firewall Issues Which Caused the "White Screen of Death"

A library system reported issues accessing the 3.1 test environment, using any workstation or device connected to their internet.

This appeared to be the known "White Screen of Death" where the top green bar shows, but the screen below it was blank. Our first step in troubleshooting was to work through some documentation created by Mobius and Geiorgia Pines on how to address the issue. 

http://libraries.missourievergreen.org/content/white-screen-death-hatchchrome

https://pines.georgialibraries.org/dokuwiki/doku.php?id=admin:workstations:troubleshooting

We learned that an older version of Internet Explorer or Microsoft Edge were the only web browsers that would sometimes allow brief access to the 3.1 test environment. (Chrome is the recommended browser.) 

We confirmed that both Firefox and Chrome were updated and using the most recent versions. We confirmed that Hatch was installed and enabled. We confirmed that the Java Runtime Environment was up to date. 

We went through the steps in Georgia Pines documentations and cleared the cache and cookies, refreshing the screens (Ctrl + Shift + R) and restarting web browsers. Still no success. 

Next, we opened the Chrome browser console (F12) to see if we could find any error messages that would point us in the right direction of the issue. We saw several error messages about access to next.nccardinal.org:7682 (which indicates port 7682) After looking at the firewall configuration we were able to conclude that although port 7682 had been opened on their firewall, the Intrusion Protection System thought that the traffic on port 7682 was a security threat.  The Library System was able to determine that the issues was tied to Application Control in the Sonicwall, specifically under the Proxy Access category Encrypted Key Exchange. Once they were able to point the category to exclude the Content Filter Allowed Domains list, the issue was resolved.

Try doing a hard refresh by clicking on the F12 button which brings up developer tools on the right side of the screen (ignore that). Right click on the refresh button next to the little home icon on the upper left of the browser window and select Empty Cache and Hard Reload.


Archived Penalties/Messages Does Not Respect Date Range

https://bugs.launchpad.net/evergreen/+bug/1775940


Some Columns Are Not Sortable in the Web Client

https://bugs.launchpad.net/evergreen/+bug/1437104


Keyboard shortcuts work differently depending on which screen - OPAC or staff client side -

https://bugs.launchpad.net/evergreen/+bug/1437106
https://bugs.launchpad.net/evergreen/+bug/1622358
https://bugs.launchpad.net/evergreen/+bug/1697003

Listing of Family Patron Groups

https://bugs.launchpad.net/evergreen/+bug/1642036

The listing of family patron groups requires a screen refresh to populate. A line item has to be checked in order to see any Action menu options. The Balance Owed column does not have the expected dollar sign. 


Merging Patrons in Collections

https://bugs.launchpad.net/evergreen/+bug/1810854

Cannot merge two patron accounts (assigned to the same person at the same library system) when one of the accounts is in collections.

Printing the Pull List

https://bugs.launchpad.net/evergreen/+bug/1749502

Configurations made to columns within the Pull List are not reflected on the printed Pull List when using the "Print Full List" option located in the top left corner of the Holds Pull screen. To appropriately print the Pull List displaying all configurations, you must use the "Print Full Grid" found after selecting the drop down arrow in the top right corner of the Holds Pull List screen. However, the Print Full Grid does not respect the order selections made in the Local Administration>Copy Location Order list. Recommend printing the Pull List from the XUL staff client to get full functionality.

Editing Call Numbers from Item Status (Edit Volume Screen is blocked out)

https://bugs.launchpad.net/evergreen/+bug/1795478

https://bugs.launchpad.net/evergreen/+bug/1746536

When attempting to edit call numbers using the item attribute area in the XUL client or in the volumes area of the web client, the actual edit volume screen does not display.


Identifying Library Branch Locations for Holds and Transits Using 3.1 Web Client

To identify your library, register your workstation by selecting your location from the drop down. For example, the image below displays a workstation that is registered for "Perry_Main"



Selecting and Sorting the Holds Shelf Information Has Limitations

https://bugs.launchpad.net/evergreen/+bug/1712854

 Columns found in the Holds Shelf list of 3.1 are not sortable or quickly resized. Also, popular columns used in 2.12, such as "Cancel Cause" or "Circulating Library" are not available within 3.1. If printing, you can export an Excel spreadsheet to sort alphabetically by patron name or use the XUL staff client for full functionality until the bug is fixed.


Parent/Guardian Field Has Been Renamed on Patron Registration Form

https://bugs.launchpad.net/evergreen/+bug/1762480

The Parent/Guardian field found on the Patron Registration form within 2.12 is not present in the 3.1 web client. The field has been renamed to "Secondary Identification" and after testing, seems to operate the same as Parent/Guardian in 2.12


Clearing Cache Also Clears Workstation Information and Column Configuration

Clearing cache to resolve certain issues in the 3.1 web client, such as the "White Screen of Death", also clears registered workstations and returns column configurations to original settings.


Labels For Several Functions Have Changed

The former "Actions for this record" label for the dropdown menu has been shortened to "Actions". The word "attributes" is no longer used for editing the item record, however you can select Edit>Items from the Actions dropdown menu. If you are used to editing multiple items using the "Manage Copy Bucket" option in 2.12, now by clicking on Cataloging>Copy Buckets, you will be directed to the copy bucket "manager" screen, although the word "manager" is no longer used.


Copy Alerts Transferred to Web Client and No Longer in XUL Staff Client

In 3.1, the code for copy alerts was completely revamped. As part of our upgrade process to 3.1.6, the existing alert messages were converted from the old code in 2.12 to the Webby code in 3.1, creating these "new" alert messages in the web client. So, the existing alerts that were in 2.12 at the time of the upgrade are now visible and editable only in the web client. MOBIUS has reported that 438,000 alerts were converted as both checkin and checkout messages.

This is the wishlist "bug" for the new feature: https://bugs.launchpad.net/evergreen/+bug/1676608

These are the permissions that Circulators, Circ Supers, Catalogers, and Cat Supers now have:

CREATE_COPY_ALERT – Consortium 
VIEW_COPY_ALERT – Consortium 
UPDATE_COPY_ALERT – Consortium 
DELETE_COPY_ALERT – System (I found a bug reported for 3.0, so we may need to adjust this to Consortium after testing: https://bugs.launchpad.net/evergreen/+bug/1783421)


Copy Alert Types and Copy Alert Suppression are under Local Admin in the web client, but not in the staff client, so only option is to administer from the web client. These permissions are granted to Local Admin & System Admin at System level:

ADMIN_COPY_ALERT_TYPE
CREATE_COPY_ALERT_TYPE
UPDATE_COPY_ALERT_TYPE
DELETE_COPY_ALERT_TYPE
ADMIN_COPY_ALERT_SUPPRESS
CREATE_COPY_ALERT_SUPPRESS
UPDATE_COPY_ALERT_SUPPRESS
DELETE_COPY_ALERT_SUPPRESS
ADMIN_COPY_ALERT

We can adjust these as needed, if we find that they are not working as anticipated in all use cases.


When editing a copy, you should see the Manage button in the Edit Items interface.


You can also see the Manage button for copy alerts in the Item Status screen.


https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_1.html

It appears that the documentation team has not caught up with this feature, but Equinox has posted some information here:

http://esilibrary.com/copy-alerts/#sthash.u4BCxsUg.dpbs


Limited/Incorrect MARC Information Display in Catalog Search Results

We have learned that the new code in 3.1 that created search highlighting seems to be interfering with the expected display of the MARC information in the catalog search results in the web client. There are several bugs reporting this issue with regard to subject headings: 

https://bugs.launchpad.net/evergreen/+bug/1770454 

https://bugs.launchpad.net/evergreen/+bug/1791662 

But, these may not capture the full picture. Thanks to several intrepid catalogers who have reported these issues.

Special thanks to Melisa Gomb from Henderson for providing this list of issues with screenshots in the attached Search Results pdf: 

  1. 6XX Subject heading tags do not break into their separate subfields in the OPAC view, therefore clicking on one only searches the narrowest term.
  2. Series information from the 8XXs field disappears, showing only the 490 field’s information. The 8XX’s field is the more important of the two as it is an authorized heading.
  3. The Physical Description 300 tag changes. The cataloger view displays correctly but the OPAC view breaks into 2+ lines and also adds additional unneeded information. We have determined it duplicates the 245 subfield h General Material Designator when present, but we have not determined where it is getting the additional information. (Possibly the 007, 008, or one of the 3XXs?)
  4. The 520 Summary tag loses its subfield c Assigning Source.
  5. Multiple fields are being repeated in several different places.
    1. 526 Study Program Information Note is repeated under General Note
    2. 546 Language Note is repeated under General Note
    3. 511 Participant or Performer Note is repeated below the 245 Title/Author and 700 Added Authors, and it is turned into one search string hyperlink if selected. This appears in both views.
  6. The 245 Title field’s subfields are reorganized in search results.
  7. The 505 Formatted Contents Notes are not displaying when there is more than one entry in the MARC.
  8. Periodically the 600s are being alphabetized.

We are discussing options that we might be able to employ as a consortium to mitigate the situation until bug fixes are implemented, but it is unlikely be a quick or easy solution.


Receiving "Blank Screen" When Using Catalog Searching Features

https://bugs.launchpad.net/evergreen/+bug/1797923

In the Web Client, when using both the “Search Catalog” located on the Home Screen and the “Search the Catalog” feature found in the “Search” tab located in the top green menu bar, staff receive a blank screen, with no error message. Staff have also reported that the Home screen will sometimes reload, instead of providing search results. We have had reports that refreshing the screen in the browser can sometimes resolve the problem.


Receiving Green Screen When Attempting To Place Holds

https://bugs.launchpad.net/evergreen/+bug/1737808

Staff receive a “green screen”( large green box) when placing holds using the web client


Inconsistent Search Results for E-books

https://bugs.launchpad.net.evergreen/+bug/1798910

Staff have reported receiving incorrect search results when using catalog search features in both the XUL and web clients of 3.1.6. When using the same isbn for catalog searches, results should be the same. Instead, each search provides results that differ dramatically. For example, staff have reported receiving different results when using the same isbn to conduct a search limited to a specific library systems, a search including the entire NC Cardinal consortium, and when conducting searches using z39.50. 


Updating User Permission Groups

https://bugs.launchpad.net/evergreen/+bug/979922

When changing a new user account to a full privileged account using the 3.1.6 web client, if the patron has two items checked out at the time of the change, staff will receive the “Max Threshold” penalty message when attempting to check out more books to the patron’ account. This message remains even after manually refreshing your web browser or logging out and logging back into the web client.

To resolve this issue, staff must manually remove the max threshold penalty message by opening the patron account and clicking on “message.” The applied penalty should display there, giving staff the option to remove it.


Receiving "Unhandled Error" Update Alert in XUL Staff Client

Cataloging Staff have reported receiving an update alert entitled “Unhandled Error” when attempting to update MARC records using the XUL client since migrating to 3.1.

This message has been identified by MOBIUS as a indicator to when invalid changes have been made to a MARC record. This message is cryptic and does not identify which field(s) are in error.

To identify invalid fields, one method of troubleshooting would be to open the record and make no changes, and save it. Then make one small change and save the record again. Continue making small changes and saving after each change until all needed changes have been made. If you receive an error message while attempting to save one of the changes, then the issue is the change that you made directly before you saved. Evaluate your changes and see if you can correct any ill formatted MARC.


Remaining Renewals Decrease When Manual Refresh Is Needed to Complete a Renewal Transaction

https://bugs.launchpad.net/evergreen/+bug/1803753

When a renewal transaction requires the screen to be refreshed in the 3.1.6 web client, it decreases the number of remaining renewals inaccurately. For Example, a patron with 2 renewals checked out an item with a original due date of 10/15 . On 10/27, staff renewed the item for the patron, which should have left the patron with 1 renewal remaining. However, while attempting to renew the item, the screen freezes and a refresh is needed to continue the renewal action. After refreshing the screen, staff are able to continue with the renewal process but notice that another renewal was used while the screen refreshed, leaving the patron with 0 renewal, instead of the expected 1 renewal.


Unable To Hide the “Credits Available” Field in the 3.1.6 Web Client

https://bugs.launchpad.net/evergreen/+bug/1803765

When using the 3.1.6 web client, staff are unable to hide the “credits available” field found within patron accounts, under the “Bill” tab. In the 2.12 staff client, staff had the option of hiding the “credits available” field if the credits functionality was not utilized by the library. Is it possible to add the feature of “ hiding” the Credits Available field to the 3.1.6 web client for those libraries that do not offer patron credits?



A Long List of Billing Ids Display in Void Billing Confirmation Message

https://bugs.launchpad.net/evergreen/+bug/1698865

When voiding a bill, the confirmation message displays the entire list of billing id numbers for the money.billing rows in the database.


Unable to Delete Pending Patrons Using the Web Client

https://bugs.launchpad.net/evergreen/+bug/1737800

The 3.1 Web Client does not offer a manual deletion option for pending patrons. To delete pending patrons, the web client relies on the  library setting — OPAC: Patron Self-Reg. Expire Interval. This setting allows each library to set the amount of time after which pending patron accounts should be deleted.


Placing Multiple Holds in My List Leads to Error

https://bugs.launchpad.net/evergreen/+bug/1687319

When placing multiple holds from “My List” using the OPAC, the hold is placed successfully, but selecting “continue” at the bottom of the screen returns a 404 Error Message.


Problems cloning & running reports in web client with templates created in XUL  

Bug 1642344 documents the original issues for which a fix was released in version 3.1.6 (our version). However, these problems are still outstanding in bug 1796945.

Cloning process seems fine. Without updating anything the template can be saved.

When running reports from the cloned templates, there were errors complaining either lacking field in Group By or missing From clause.

When cloning the templates, removing then putting back the complained fields solved the issue.

It seems the issue is related to how the tables are joined. See the screenshot. Nearly all our templates starting from Item table leading to Call Number > Bib > Simple Record Exact are affected.

From Item table to Shelving Location or Copy Status tables sometimes have the issue, too.

https://bugs.launchpad.net/evergreen/+bug/1642344
https://bugs.launchpad.net/evergreen/+bug/1796945

For now, we recommend using XUL to clone and run templates originally created in XUL. We will need to evaluate the status of this bug at the time of our upgrade to a new version, as the proposed fix release is version 3.4.









1.2. Questions and Answers

Question: Please explain the difference between the XUL staff client and the web browser client.

Answer: The XUL staff client is software based and is what we have always used to access Evergreen up to this point. XUL Runner is outdated and Evergreen is replacing it with web-based functionality. The web browser client does not require software to access the NC Cardinal database. We recommend only using the Chrome browser for the web client.  


Question: Will the web client work on an iPad Pro?

Answer: There are some known issues with the web client and Apple products. Debbie Luchenbill has been able to get it to work on her Mac desktop. Blake Graham-Henderson reported that Chrome is really just Safari on Apple products and the Evergreen community has reported problems with using on iPads.


Question: Will keyboard shortcuts still work in the web client? 

Answer: Yes, they will


Question: Can we still use the staff client for cataloging and administrative functions?

Answer: Yes, we are recommending that you use only circulation functions in the web client for now, and the staff client for the other functions (acquisitions, administration, cataloging, serials, etc.).


Question: Is it possible to add multiple volumes and copies for any branch in your system?

Answer: Yes, it is possible by choosing a different volume-owning location and clicking the "Add Volume" button (button in left corner of screenshot). Then, you can select the number of copies for each branch.



Question: Will self-checks continue to work with Evergreen is the same fashion going forward or will configuration changes be required?

Answer: Yes. At this point, we are expecting present self-checks to interact with Evergreen in the same fashion. Self-checks operate using SIP connection and with the SIP not changing, your self-checks should not be affected with the migration to 3.1. I will be sure to keep you posted if anything changes.


Question: Will all library systems GoLive at the same time?

Answer: All library systems will process their offline transactions at the start of Monday morning, October 15th, and will be able to golive afterwards.


User Interface

Question: When selecting from a list, is it possible to highlight multiple lines by using the Shift key?

Answer: Yes, you can click within the line (but not on the checkbox or hyperlinked text) and use the Shift or Control keys to highlight multiple lines. This will check the selection box automatically and you can choose the desired action from the Actions dropdown menu.


Question: Clicking and dragging column width is much better than the current method of expanding/shrinking arrows. Will these be changed?

Answer: Not in the near future, as far as we know.


Question: How can we add things like patron name to the holds shelf grid?

Answer: The column picker in now a down arrow on the right edge on the Actions bar. Click on the down arrow and select the desired field to add or subtract from the list grid. 


Question: Is there a simplified pull list print option in the web client?

Answer: No, but you can select the columns you want to be the highest priority and your list will sort based on those. There is a Print Full Grid action in the web staff client holds pull list to allow staff to print the entire pull list as it displays on the screen. This change also changes the Export CSV action to an Export Full CSV option, which allows you to download as an Excel spreadsheet.

The Simplified Pull List still exists in the XUL staff client, so you may want to print the hold pull list from the XUL staff client, as it will now display subfields 245$n and $p in the title field to make it easier for staff to distinguish between different parts or seasons in a series. 


Question: In 3.1, when accessing the Transit List found in Local Administration, all options displayed are available to staff regardless of their permissions. In 2.12, majority of these options were only available to individuals with an admin password. Once migrated to 3.1, will all options continue to be accessible to all or like 2.12, will permissions go back into affect limiting individuals without appropriate permissions?

 Answer: After migrating to 3.1, all current permissions will go back into affect, limiting access to those without appropriate permissions.


Question: In 3.1, is there a way to only have to set the disable highlighting once per workstation?

Answer: No. This action is not considered "sticky" and will have to be done each time when needed.


Working With Patron Accounts

Question: For batch editing patrons, will there be separate permissions for batch patron edits and deleting patrons?

Answer: The patron batch permissions (and all other new permissions) will be allocated as a part of the larger staff permissions project


Question: When searching for a patron by name (new feature) in the hold screen, will the notification methods carry over after selecting the patron?

Answer: The notifications will either fill in based on the patron preferences previously selected/saved in their account or can be set or changed by staff or patrons when placing the hold.


Question: When checking out to patrons with fines, will the red highlight indicating items checked out with associated fines display in 3.1 as in 2.12

Answer: Yes, the feature of highlighting items with associated fines that are still checked out will be available in 3.1. Also like in 2.12, the Bills tab will automatically open.


Administration


Question: Does the web client have responsive design?

Answer: No, it is expected in version 3.2


Question: Do you know if there will be any changes to SIP in this version? Or will the server IP address change?

Answer: No change


Question: Hatch: My understanding is that it saves both print settings and column settings. Is that correct?

Answer: This issue is in flux. The code to move ALL of these settings onto the server is done and might already be merged. That feature is going to be part of 3.2 so it won't happen for you until you upgrade again in the future. The direct answer is: Hatch has three things it can do (listed in Administration ->
Print / Storage Service ("Hatch"))

(a) Use Hatch For Printing
(b) Store Local Settings in Hatch
(c) Store Offline Transaction Data in Hatch
If item (b) if enabled, should store the column preferences in Hatch. This means that if the browser cache is deleted, you should be able to hook Hatch back up, and poof, the settings are restored.


Question: It seems like there is a default "out of the can" set of column configurations, and that it is possible to save and export column settings. The working group is concerned about column configuration being a pain point for the transition. Could we configure a default "best practice" set of column configurations that everyone would get unless they changed them?

Answer: Sorry, this is code development and not a feature in Evergreen to change. It's not a realistic timeline to implement such a code change.


Question: Will/can column configurations or receipt configurations set up in "next" persist for the upgrade?

Answer: Any settings that anyone makes on the (next) server will not work on the production server because the URL's are different. The URL is how Hatch settings are divided.


Question: If I copy our current templates to a word document, will I be able to paste them back into the new system and locally save each?

Answer: No, the printer configurations for the software client are formatted differently than the templates used in the web client. Documentation on configuring receipt templates in the web client can be found here: 

https://nccardinalsupport.org/index.php?pg=kb.page&id=329


Question: Is there a way to add the Parent-Child library system relationship on transit and hold transit slips?

Answer: Cardinal can set up a new default consortium-wide code within the transit and hold transit slips to incorporate the Parent-Child relationship for libraries. Remember that while the default templates can be created for the consortium, coding on the local end for individual system verbiage will need to be done on all workstations within a branch, system. Template files are stored on each workstation that code has been applied.


Question: How long will we be using XUL for cataloging and acquisitions?

Answer: At least until 3.2 upgrade since 3.1 is still too buggy.


Question: How about library settings, circ rules, and other admin functions? Do you have recommendations for using XUL or Webby?

Answer: For library settings, circulation rules, and other admin functions, you would be able to use Webby at this time.



1.3. Release Notes

Please read over the release notes for new features and bug fixes:

3.0 series

https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_0.html

3.1 series

https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_1.html


3.1.2 Improvements from Kathy Lussier's announcement on 5/29/18

Cataloging

  • The MARC editor now handles 008 fields better.
  • Adds spaces between subfields when suggesting a call number for a new volume.
  • MarcXML exports from the MARC Batch Import/Export ? Export Records screen now downloads the file, rather than opening it in the browser.
  • The Item Status Circulation Library column now displays a shortname rather than the full library name.
  • The Item Status Remaining Renewals column now displays correctly.
  • The Item Status now has a “Last Renewal Workstation” column available.
  • Fixes the circulation counts displayed in Item Status Details.
  • Fixes an issue where multiple copies with different values for required statistical categories could not be edited and saved in batch.
  • Adds an option to remove floating in the copy editor.
  • Fixes an issue with the floating dropdown in the copy editor.
  • Fixes a problem in which the copy template didn’t properly copy certain objects.
  • Reduces the number of API calls that the MARC Editor requires.

Circulation

  • Fixes an issue that prevented the offline patron registration screen from loading.
  • Fixes an issue with searching patrons by permission group.
  • The barcodes in the patron search are now clickable.
  • Staff members can now manually override the patron juvenile flag value, regardless of the patron’s date of birth.
  • Checkboxes on patron registration screen are now properly aligned with other fields.
  • The user permission group dropdowns in the patron registration, edit, and search interfaces now have scrollbars.
  • The date picker on the checkout screen is now hidden unless circ staff activates a specific due date option.
  • The check-in screen now includes a copy status column.
  • The Merge Patrons interface now displays the date of birth.
  • The user bucket screen now displays the Bucket ID.
  • The payment button on patron bills screen is now inactive if the Payment Received field is blank.
  • The Bill History receipt now includes a Finish date and a Last Payment date.
  • When a patron summary contains an image of the patron, that image tag now has a null alt attribute to remove it from the flow of a screen reader.
  • Corrects an issue that caused the transit dialog to show the wrong branch.
  • Corrects an issue with printing transit lists.
  • “Find another target” on transiting hold no longer leaves the copy “in-transit”.
  • The images now display to distinguish hold and transit slips.
  • The Clearable Holds list printout now only shows holds that have expired.
  • Restores the call number prefix and suffix fields to the holds pull list.
  • The documentation at the top of the hold shelf slip template adds patron.alias.
  • The cursor in the in-house use screen now automatically goes to the barcode field.
  • The in-house use screen now shows a copy status column.
  • Adds support for converting change to patron credit in the patron bills interface, consistent with the XUL feature.
  • Fixes a bug that caused pickup/request library fields to be blank sometimes.
  • Fixes a bug in the offline org unit tree.

Command-line system administration

  • The novelist entry in eg_vhost.conf includes two new parameters.
  • Corrects an issue with the –max-sleep argument on the action_trigger_runner.pl support script.
  • Corrects an issue with how the eg_pbx_allocator.pl script detects an existing lock file.
  • The 3.0.2-3.0.3 upgrade script disables triggers before recalculating bib visibility.

Public catalog

  • Fixes an issue that caused records with located URIs to be retrieved in Copy Location and Copy Location Group searches.
  • Fixes an error message that appeared in the search box in the public catalog while placing hold after an advanced search.
  • Restores the display of copy information for the user’s preferred library in the public catalog.
  • Fixes regression errors in the search results page.
  • Removes redundant call numbers from the Show More Details search results.
  • The cast field in the catalog is now taken from the 511 field when first indicator = 1, rather than the 508.
  • Fixes a display issue caused by editing holds.

Serials

  • Fixes an issue that prevented users from searching for receivable issues using Database ID or ISSN in the Serials Batch Receive interface.

General

  • Adds some padding to the bottom of Web Client interfaces.
  • Logins now honor all org unit timeout settings.
  • Evergreen will now identify and handle invalid timezones.
  • Fixes an issue where a column header in some interfaces were automatically highlighted in green when retrieving the interface.
  • The parts column in the Item Status screen now displays parts data.

Additionally, the following improvements were added to the 3.1.2 maintenance release:

  • Removes an error that got thrown in the Holdings View when a call number contains no copy.
  • The order of the Z39.50 servers on the Z39.50 import screen no longer relies on capitalization.
  • Author and contributor names are no longer highlighted in search results when the user has turned off highlighting.
  • Repairs broken author search links on the catalog record page.
  • Pins AngularJS support to version 1.6, which prevents unsupported AngularJS versions (such as 1.7) from breaking the build process.

1.4. RFID

Solution for RFID Targeting Login Window in Evergreen Staff Client

  • Exit out of Evergreen completely
  • Close any other software on the computer
  • Make sure rfid pad is up and reading items
  • Put a tagged item on the pad, so that you get a pop-up asking where you want the number to go
  • Only then can you log into Evergreen (leaving the item in place - critical)
  • Once both windows for EG are open, go back to the 3M window, which should ask you to choose one of the EG windows
  • Make sure you choose the splash screen as the active window (NOT the login window)

2. Connection to Evergreen

2.1. Latency Test for Connection Issues

New Latency Tester Tool


The Evergreen 3.1 Web Staff Client now includes a section called Tests linked from Administration → Workstation. The Tests page houses a simple tool that can be used to test the latency of the websocket connection between the client and the server (via the opensrf.echo service).





This page displays which Evergreen host server is being queried. Upon hitting the blue "Start Test" button for the first time, it will issue 10 sequentially fired requests in order to get a solid initial average. Clicking the button a second time will take one more measurement and recalculate the average latency. The results can be copied to clipboard for troubleshooting purposes and also cleared from display.