Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Q&A

    Aleph

    Our library offices are now closed. Is there a way of accessing  Aleph remotely?

    Aleph GUI access can be controlled by the $alephe_tab/server_ip_allowed.  You could (temporarily) change the "P" (PC server) line in server_ip_allowed to allow access from additional IP addresses.  Note that the ./xxx50/tab/tab_attr_sub_library also controls certain circulation functions via ip-addresses and may, similarly, need to be changed.

    Voyager

    We can't access the CAT or ACQ clients through the Cloud. If we load the clients onto a personal laptop, can Ex Libris open access so people can connect using their personal ISP?

    Clients can be run over a campus VPN.  Talk with your I.T. staff about the kind of VPN used on campus, and if it provides fixed IPs or an IP range for computers.  Fixed IP addresses are required for the server firewall rules in the Ex Libris Cloud environment. Also discuss capacity with I.T. staff to make sure the VPN can handle an increased load. If a campus VPN is not available, talk to I.T. staff about using Windows Remote Desktop to access the Voyager clients.

    Access to hosted Voyager servers for running the clients and/or connecting via SSH/SFTP is restricted to specific institutional or campus IP addresses. These campus IP addresses are white-listed in the Ex Libris hosted server firewall.  All other addresses are blocked from access to keep your system and library information secure.

    You should contact your local/campus I.T. Department for additional help in accessing Voyager remotely.

    Links to additional information can be found in the Ex Libris Knowledge Center: Basic information on running the Voyager clients on a hosted server from off-campus.

    Our member libraries are inundating us with requests to bulk renew or bulk update the due dates of charged items to the end of their expected closures. Short of using macros, is there a way to do this? Can Ex Libris help with running operations on the Oracle tables?

    The Voyager Support team has compiled some articles containing advice to help you manage items on loan and communications with borrowers during this unprecedented crisis. Those tips are available in the Ex Libris Knowledge Center:

    Advice on contingency planning for Voyager services in case of campus shutdown and/or changes for telecommuting and Ensure materials due on days library is closed (Voyager calendar exception dates) do not come due on those days

    Is there a way to extend the due dates via a batch job, so we don't have to do it one-by-one for each individual patron?

    Voyager does not have a batch job to extend due dates, however, the Voyager Support Team has compiled a list of ways to manage items that were checked out prior to the COVID-19 situation. Please review the advice in this article on the Knowledge Center for more information: Advice on contingency planning for Voyager services in case of campus shutdown and/or changes for telecommuting.

    Remember to document any changes you make so that you can undo them later.

    Our library is closed to the public (we are still open to students, staff, and faculty). Since our public patrons don't have access to our campus how can we adjust our Overdue notices?

    The information supplied in patron email notices can be edited -- see: What can be customized in Voyager email notices? 

    It is also possible to temporarily stop sending out patron notices (Overdue, Recall, Fine/Fee (new), Hold Recall Available, Hold Recall Cancelled, Courtesy) -- see: What happens if you run a job on the server but don't build the reports or notices in Reporter

    o    If Circulation Notices are not Built/Run through Reporter, no notices will go out to patrons

      • If notices are not built/run, the crcnotes.printlocationcode.inp file will continue to grow; it is advisable to periodically move off this file (to something like crcnotes.printlocationcode.20200313) so it doesn't become too large

    o    If the 'Email' option is unchecked for a particular type of notice (in SysAdmin>Circulation>Policy Definitions>policy containing Circ Happening Location of transaction>Patron tab, per patron group), when writing to the crcnotes.printlocationcode.inp file, the row will not have an email address

      • If the row in the .inp file doesn't have an email address, it will be set to print when notices are built/run; any unwanted notices do not need to be sent to patrons (and can also be set to print to .pdf so nothing is physically printed)

    You may also want to review the advice in this article to see if other changes should be applied: Advice on contingency planning for Voyager services in case of campus shutdown and/or changes for telecommuting.

    Remember to document any changes you make so that you can undo them later.

     

    • Was this article helpful?