Upgrade to Evergreen 3.1: progress report (Saturday PM)

[Daniel Scott]

I started the upgrade process around 8:00 PM Friday night, and finished the main part of the Evergreen upgrade this morning at approximately 3:00 AM.

The catalogue appears to be working well. Let me know if you see anything wrong with your skins! One known issue, however, is that the LDAP authentication for Laurentian users does *not* seem to be working. I'll be looking more into that over the weekend, as I put a few hours into it already without getting anywhere (other than a lack of sleep).

The bibliographic records have all been reingested, which (amongst other things) enables the new "highlight your search query terms in the search results" functionality to work in the catalogue.

The legacy staff client appears to be working well. You will likely be prompted to upgrade your legacy staff client the next time you connect--but if you need a fresh copy for some reason, you can get it from https://clients.concat.ca/ (as always).

The exciting new web-based staff client is available at https://<yourhostname>/eg/staff - so, for example, at https://laurentian.concat.ca/eg/staff for Laurentian users, https://uhearst.concat.ca/eg/staff for Hearst users, https://nosm.concat.ca/eg/staff for NOSM users, etc. You might find the documentation sections on "Cataloguing" and "Circulation" for Evergreen 3.1 at http://docs.evergreen-ils.org/ helpful as much of the documentation has been updated to reflect the web-based staff client. The core functionality appears to work on both Firefox and Chrome.

To get the most out of the web-based staff client, however, you'll need to install something called "Hatch"--this supports settings for printing receipts, labels, etc. This in turn requires both a Java JRE and a browser extension for Chrome (currently this is the only officially supported browser, although support for Firefox is close). The Hatch installer for Windows is linked from the Evergreen downloads page at https://evergreen-ils.org/egdownloads/ , as are the instructions for installing Hatch and the Chrome extension

I have confirmed Z39.50 support is working, as is SIP support; however, until I hear back from our RFID users at the School of Architecture, I can't be 100% sure that the flavour of SIP that we're running still meets the RFID system's expectations.

Thanks,

Dan

--

Dan Scott
Associate Librarian & Chair, Library and Archives
Bibliothécaire agrégé & Directeur, Bibliothèque et archives
Laurentian University / Université Laurentienne
Phone: 705-675-1151 x3315

[Daniel Scott]

Updates:

• LDAP authentication for Laurentian users is fixed. It looks like IT Services modified its requirements for authentication, which caused a problem at the same time. Odd coincidence! I've manually gone through the accounts of all users who were unable to log in since Saturday morning and renewed items for those that had items due on June 4th or shortly after.
  
• I've confirmed that the legacy staff client will automatically download an upgrade, and that the upgrade does work--although the first time I started it, it froze for a minute or two with a "Not responding" Windows message, before eventually allowing me to log in. Odd.
• The authority records are now being reingested, which will likely take all of today and most of tomorrow to finish. Anything involving authorities will not work until this reingest finishes, as the corresponding database tables are essentially exclusively locked for the reingest.
  
• I've been reindexing tables and performing other basic database maintenance with the goal of ensuring that there is no reason for the database to slow down.
• I have confirmed that courtesy reminder and overdue notices are still being sent.
• I have confirmed that reports are still running.
  

We'll see what happens tomorrow once everyone is using the system, however. Fingers crossed!

[Michael McArthur]

Hey Dan - Having a heck of a time getting call # labels to print properly.  Are there any templates for just call #s?  The default at the moment is a pocket label. 

[dsc...@laurentian.ca]

On Tuesday, 5 June 2018 11:57:36 UTC-4, Michael McArthur wrote:
> Hey Dan - Having a heck of a time getting call # labels to print properly.  Are there any templates for just call #s?  The default at the moment is a pocket label. 

Hi Michael:

Assuming you're using the new web staff client, from the "Print Item Labels" screen you can:

0. Enter a name for the template in the "Template" text box.
1. Go into the "Call Number Template -> Call Number Template" edit section
2. Scroll to the very bottom and cut out the "Pocket Label contents" section (inside the <pre>...</pre> tags)
3. Click "Save" to save your label template
4. Click "Apply" to apply your label template
5. Click "Print"

You can also export a saved label template from that screen, or import a template that someone else created.

The BC Libraries Co-operative have some more extensive documentation about this at http://docs.libraries.coop/sitka/spine-label.html#_configuring_label_printing

Hope this helps!

[dsc...@laurentian.ca]

I sat down with Marlene (one of our cataloguers) today to walk through the process and generated a template, including settings for font size and margins, that worked nicely for our Dymo LabelWriter 450 through the Chrome web browser's print dialogue.

You can download the template from https://drive.google.com/open?id=152FhTtKPrT3lO43CxtjnQRT7EVvPQOgE and then import it, if you want to try our spine label approach.

Note that you will have to tweak the "More settings" part of the Chrome print dialog to ensure that you are printing to 30347 labels (if you're using the 1" x 1.25" label stock), with no margins. And when you print a label, for us it will try to print a blank second page; you can change that to print just page 1. (I recognize that last part isn't ideal but in the short-term it works...)