Search

Where can I find the names of fields in the delete.item file?
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Where_can_I_find_the_names_of_fields_in_the_delete.item_file%3F
Article Type: Q&A Product: Voyager Product Version: 7.1.0 Question Where can I find the names of column headings in the delete.item file? Answer See the Voyager Technical User’s Guide, Chapter 20, "It...Article Type: Q&A Product: Voyager Product Version: 7.1.0 Question Where can I find the names of column headings in the delete.item file? Answer See the Voyager Technical User’s Guide, Chapter 20, "Item Delete Standard Interface File" for field names. Category: Cataloging Article last edited: 10/8/2013
Acquisition affecting displayHoldings displays in OPAC
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Acquisition_affecting_displayHoldings_displays_in_OPAC
In your displayHoldings.xml, make sure you have something like the following defined: <holdingsTags label="Older Issues:"> <displayTag field="1040" /> </holdingsTags> <holdingsTags label="Other issues...In your displayHoldings.xml, make sure you have something like the following defined: <holdingsTags label="Older Issues:"> <displayTag field="1040" /> </holdingsTags> <holdingsTags label="Other issues:"> <displayTag field="866" indicator1="|" indicator2="0" subfield="az" /> <displayTag field="866" indicator1="|" indicator2="1" subfield="az" /> <displayTag field="866" indicator1="|" indicator2="2" subfield="az" /> <displayTag field="866" indicator1="3" indicator2="0" subfield="az" /> <displayTag…
ACQ:only last item created thru Acq relinks to new mfhd
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/ACQ%3Aonly_last_item_created_thru_Acq_relinks_to_new_mfhd
Description: Bug Report Form for Issue 16384-8273 Module: Acquisitions Release(s) replicated in: 7.1.1 Server Platform(s) affected: Solaris/all PC O/S (if this is PC specific): n/a Browser type & vers...Description: Bug Report Form for Issue 16384-8273 Module: Acquisitions Release(s) replicated in: 7.1.1 Server Platform(s) affected: Solaris/all PC O/S (if this is PC specific): n/a Browser type & version (if WebVoyage): n/a Expected Results: When the line item copy is linked to a different mfhd, any items created through that line item in Acquisitions should automatically be linked to the new holdings record.
holdingsInfo.page settings not applied
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/holdingsInfo.page_settings_not_applied
Problem Symptoms: * Changes to some webvoyage.properties settings not impacting display in WebVoyage. For example: holdingsInfo.page.heading=Record View holdingsInfo.page.label=Bibliographic Details C...Problem Symptoms: * Changes to some webvoyage.properties settings not impacting display in WebVoyage. For example: holdingsInfo.page.heading=Record View holdingsInfo.page.label=Bibliographic Details Cause: This behavior is caused by Known Issue 16384-20465. Display a record from title list in one of your skins. In same skin on server, edit the value for holdingsInfo.page.heading= ; i.e., holdingsInfo.page.heading=This is my record view. Refresh the display in WebVoyage.
SDI: Emails lack BodyN and SearchString variables
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/SDI%3A_Emails_lack_BodyN_and_SearchString_variables
Description: Bug Report Form for Issue 16384-11250 Module(s): WebVoyage, Batch Jobs Server platform(s) affected: Tested on Solaris PC OS (if applicable): N/A Browser & version (if applicable): All Sup...Description: Bug Report Form for Issue 16384-11250 Module(s): WebVoyage, Batch Jobs Server platform(s) affected: Tested on Solaris PC OS (if applicable): N/A Browser & version (if applicable): All Supported Browsers Release(s) replicated in: 7.2.2, 7.1.x, 6.5.4 Last version without bug (if applicable): N/A Expected results: The ability to define a custom body message and SDI URL prefix in the emails generated for SDI Actual results: Though defined, SDI emails lack the text stored in the Body1, …
Bursar:individual refund information transferred in patron mode
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Bursar%3Aindividual_refund_information_transferred_in_patron_mode
Description: Bug Report Form for Issue 16384-14897 Module(s): Bursar Server platform(s) affected: Solaris Release(s) replicated in: 7.1.0-7.2.4 Expected results: When using the –p patron mode, Bursar ...Description: Bug Report Form for Issue 16384-14897 Module(s): Bursar Server platform(s) affected: Solaris Release(s) replicated in: 7.1.0-7.2.4 Expected results: When using the –p patron mode, Bursar transfer should not transfer any specific fine/fee information. In /m1/voyager/xxxdb/sbin, run PBursar using the –p parameter and make sure that the patron from step 1’s patron group is in the config file.
What are values in CIRC_TRANSACTIONS.CHARGE_TYPE?
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/What_are_values_in_CIRC_TRANSACTIONS.CHARGE_TYPE%3F
Article Type: Q&A Product: Voyager Product Version: 7.1.0 Question What are the values of "N" and "O" in the charge_type column in circ_transactions table? Answer The values in the CHARGE_TYPE field i...Article Type: Q&A Product: Voyager Product Version: 7.1.0 Question What are the values of "N" and "O" in the charge_type column in circ_transactions table? Answer The values in the CHARGE_TYPE field indicate whether a charge transaction was an override (O) or did not require an override (N). Category: (Voyager) Article last edited: 10/8/2013
Voyager cfg , ini and tag table files shipped with clients are in read only mode
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Voyager_cfg_%2C_ini_and_tag_table_files_shipped_with_clients_are_in_read_only_mode
Description: Bug Report Form for Issue 16384-7377 Date: July 2009 Module(s): Voyager Clients Release(s) replicated in: 7.1-8.0.0 Expected results: Users should easily be able to edit .cfg ,.ini and ta...Description: Bug Report Form for Issue 16384-7377 Date: July 2009 Module(s): Voyager Clients Release(s) replicated in: 7.1-8.0.0 Expected results: Users should easily be able to edit .cfg ,.ini and tag table files shipped with the clients. Actual results: The .ini and .cfg files, including tag tables, are read only when shipped with the clients. Workflow implications: Staff will edit the file and only realize that they need to change the file properties once they want to save their changes.
Should I create the patron statistical categories or load patron records first?
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Should_I_create_the_patron_statistical_categories_or_load_patron_records_first%3F
Should I create patron statistical categories first, or load patron records first? Patron statistical categories should be implemented in an update to the patron database, as opposed to in the initial...Should I create patron statistical categories first, or load patron records first? Patron statistical categories should be implemented in an update to the patron database, as opposed to in the initial creation of the patron database. In System Administration, create the patron statistical categories as outlined in the System Administration document (Chapter 10). When the SIF is loaded, Voyager uses the codes in the SIF to assign patron statistical categories to patron records.
Record not viewable in WebVoyage
https://knowledge.exlibrisgroup.com/Voyager/Knowledge_Articles/Record_not_viewable_in_WebVoyage
Problem Symptoms: * Record with longer 505 field (>10,000 characters) not displaying in OPAC * Other records are displaying fine Cause: 505 field has too many characters. Log into Cataloging and retri...Problem Symptoms: * Record with longer 505 field (>10,000 characters) not displaying in OPAC * Other records are displaying fine Cause: 505 field has too many characters. Log into Cataloging and retrieve the bibliographic record. Divide 505 field into two or more separate fields, each less than 10,000 characters. "MARC 21 Specification for Record Structure, Character Sets and Exchange Media: Record Structure" http://www.loc.gov/marc/specificatio...crecstruc.html