Bootstrap OPAC has replaced Traditional Catalogue in Staff Client

[Jennifer Pringle]

EG master

On the test servers for Bug Squashing Week the traditional catalogue in the staff client (Cataloguing -> Search the Catalogue (Traditional) ) has been replaced with the Bootstrap OPAC. Ideally the Traditional Catalogue should continue to be the old catalogue regardless of whether the bootstrap OPAC is enabled until the old catalogue is fully deprecated and removed.

[Jason Boyer (jboyer)]

Hi Jennifer, The traditional staff opac tries to match the patron OPAC in use at any given time, usually based on host name. Since you mentioned Bug Squashing Week and taking my pattypan server as an example, if you access it as pattypan.evergreencatalog.com you'll see the bootstrap opac when accessing the OPAC or the staff client. Using pattypan-tpac.evergreencatalog.com would revert *both* back to the TPAC. (If it doesn't that's a problem.)

Are you saying that the staff client should use the tpac even if the patron opac is the bootstrap opac?

[Jennifer Pringle (jpringle-u)]

Hi Jason, I think if library staff are still using the traditional catalogue they'll be expecting to see the TPAC, otherwise they'd have switched to using the new catalogue.

The pattypan-tpac.evergreencatalog.com URL works for me to revert to the TPAC so having staff use a different URL would definitely be a workaround to enable staff to access the TPAC in the staff client.

It would be good to hear what people think who are currently using the bootstrap OPAC or planning to in the near future. (We're not planning to implement it in our consortium until 2022.)

[Jason Boyer (jboyer)]

Another thing to keep in mind is that these BSW servers intentionally have the bootstrap opac enabled for testing. Unless sysadmins take extra steps on 3.6 the bootstrap opac won't appear anywhere. And while it's the default in 3.7 it can be disabled by commenting out 1 line in the web server config, so this is unlikely to be an issue in actual staff-facing installations; it's mostly just a problem with the BSW servers. That's why we make both URLs available, so you can test on either interface.