Search

Overcommit/expend blocks show incorrect values
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Overcommitexpend_blocks_show_incorrect_values
Block messages for overcommit/expend show incorrect information. Issue VYG-4495 is resolved for Voyager 9.1.0 and higher. Acquisitions > Ledgers and Funds > Create ledger with allocated fund. Purchase...Block messages for overcommit/expend show incorrect information. Issue VYG-4495 is resolved for Voyager 9.1.0 and higher. Acquisitions > Ledgers and Funds > Create ledger with allocated fund. Purchase Orders > Create a purchase order (PO) with line item that has a price of $2000. Ledger/fund name - % needed to override: 201d Allocation increase: $0.00' "Allocation increase" should show $1000.00 and "% needed to override" 200 in this case, and "201d" should show "201%"
Drop-down for font size in Cataloging only goes up to 12
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Drop-down_for_font_size_in_Cataloging_only_goes_up_to_12
A font size larger than 12 (14, 18, 24) can be typed in and used by the client, and retained as the choice after the client gets restarted. Larger font sizes are supported in Cataloging for Voyager 9....A font size larger than 12 (14, 18, 24) can be typed in and used by the client, and retained as the choice after the client gets restarted. Larger font sizes are supported in Cataloging for Voyager 9.1.0 and higher, but the options in the font size drop-down in Options > Preferences > Colors/Fonts remain the same. Operators can type in a font size up to 72 which will be applied to variable fields in MARC format records displayed in the client.
Record set names with reserved characters not allowing Export
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Record_set_names_with_reserved_characters_not_allowing_Export
Problem Symptoms: * Click Export from Record Sets area and nothing happens * Click Export from Record Sets area and ** Export Record Set To Disk window opens but adds .dslr extension and won't allow S...Problem Symptoms: * Click Export from Record Sets area and nothing happens * Click Export from Record Sets area and ** Export Record Set To Disk window opens but adds .dslr extension and won't allow Save; or ** Export Record Set To Disk window opens, adds correct .txt extension and on Save gives error, "{file name} The file name is not valid."
OPAC Search Log has incorrect Client Type entries
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/OPAC_Search_Log_has_incorrect_Client_Type_entries
Issue VYG-4757 is resolved in Voyager 9.1.0 and higher.
What regens does the VIK perform for upgrade to Voyager 9.1.0?
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/What_regens_does_the_VIK_perform_for_upgrade_to_Voyager_9.1.0%3F
Article Type: Q&A Product: Voyager Product Version: 9.1 Question What regens does the VIK perform for upgrade to Voyager 9.1.0? Answer Regens required to upgrade to a particular version may vary based...Article Type: Q&A Product: Voyager Product Version: 9.1 Question What regens does the VIK perform for upgrade to Voyager 9.1.0? Answer Regens required to upgrade to a particular version may vary based on the current version being upgraded. For Voyager 9.1.0, the VIK will perform keyword, headings and bib text regens. Category: (Voyager) - Voyager Subject: Voyager Article last edited: 12/22/2014
Where does piece identifier map from in EDI invoice?
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Where_does_piece_identifier_map_from_in_EDI_invoice%3F
What elements map from the EDI invoice to the piece identifier field? For serials, the piece identifier field is populated from IMD+L+085 (invoicing period start volume/issue) and IMD+L+086 (invoicing...What elements map from the EDI invoice to the piece identifier field? For serials, the piece identifier field is populated from IMD+L+085 (invoicing period start volume/issue) and IMD+L+086 (invoicing period end volume/issue). Example for serials: This in the EDI invoice IMD+L+085+:::109(01/14)' IMD+L+086+:::109(12/14)' will map to this in the piece identifier field on the Voyager invoice 109(01/14)-109(12/14)
SMS messages fail with error 500
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/SMS_messages_fail_with_error_500
exception java.lang.ArrayIndexOutOfBoundsException: 1 ... * Corresponding Tomcat catalina.out log shows: SEVERE: Servlet.service() for servlet [SmsProxyHttp] in context with path [/core-sms-proxy] thr...exception java.lang.ArrayIndexOutOfBoundsException: 1 ... * Corresponding Tomcat catalina.out log shows: SEVERE: Servlet.service() for servlet [SmsProxyHttp] in context with path [/core-sms-proxy] threw exception java.lang.ArrayIndexOutOfBoundsException: 1 ... Cause API Id is missing from the <ProviderPassword/> tag in SmsProxyConf.xml Resolution * The <ProviderPassword/> tag for <Institution> configurations in SmsProxyConf.xml, must contain both the password and the API-Id separated by a colon…
SysAdmin Doc reports deselecting locations in Owning Libraries
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/SysAdmin_Doc_reports_deselecting_locations_in_Owning_Libraries
Description: Bug Report Form for Issue 16384-8338 Module(s): System Administration User’s Guide Expected results: The System Administration User’s Guide should explain that locations cannot be deselec...Description: Bug Report Form for Issue 16384-8338 Module(s): System Administration User’s Guide Expected results: The System Administration User’s Guide should explain that locations cannot be deselected from Owning Libraries; locations must be assigned to another owning library, at which point they are automatically deselected from the original owning library. The System Administration User’s Guide erroneously states that locations can be deselected from Owning Libraries.
Data in global headings change tables not removed when Name/Title record deleted
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Data_in_global_headings_change_tables_not_removed_when_NameTitle_record_deleted
Problem Symptoms: * Name/Title auth record deleted & data for heading remains in Global Headings Change (GHC) Queue Cause: This behavior is the result of VYG-4762 / 16384-4881 Resolution: Issue VYG-47...Problem Symptoms: * Name/Title auth record deleted & data for heading remains in Global Headings Change (GHC) Queue Cause: This behavior is the result of VYG-4762 / 16384-4881 Resolution: Issue VYG-4762 is not reproducible in Voyager 9.1.0. Update Name/Title in Authority record so normal heading will change and be queued to GHCQ. Note heading change data for record remains in HEADING_CHANGE_QUEUE, HEADING_CHANGE, and HEADING_CHANGE_FIELDS 9.
Detailed Line Item Standard Number applied to both printed POs and EDI?
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Detailed_Line_Item_Standard_Number_applied_to_both_printed_POs_and_EDI%3F
Product: Voyager Product Version: 9.1 Relevant for Installation Type: Total Care; Dedicated-Direct; Direct; Local Question On the Acquisitions Detailed Line Item: Bib Record Tab, is the Standard Numbe...Product: Voyager Product Version: 9.1 Relevant for Installation Type: Total Care; Dedicated-Direct; Direct; Local Question On the Acquisitions Detailed Line Item: Bib Record Tab, is the Standard Number applied to both printed POs and EDI? Answer Yes. Article last edited: 20-Nov-2017
Bulk Export via WebAdmin fails with "Failure opening input file"
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Bulk_Export_via_WebAdmin_fails_with_%22Failure_opening_input_file%22
The server, on the other hand, does not know that text that comes after the space is still part of the file name. In Voyager 9.1.0 and higher, files submitted via WebAdmin retain their file names (pre...The server, on the other hand, does not know that text that comes after the space is still part of the file name. In Voyager 9.1.0 and higher, files submitted via WebAdmin retain their file names (previously, the system had assigned a file name instead). So, when a file name contains a space, the server is unable to process and complete the job. Note that the file name is truncated where the space occurs. Submit via WebAdmin; this time, file can be read and the job completes successfully.