- Product: Voyager
- Product Version: 8.2.0
- Relevant for Installation Type: Dedicated-Direct; Direct; Local; Total Care
We are preparing to upgrade to Voyager 8.2.0; a SEARCHPARM_conflicts.xls file was generated for one of our search indexes. How do I resolve the conflict for our upgrade?
- FTP SEARCHPARM_conflicts.xls from /m1/voyager/xxxdb/tmp to your PC and open in Microsoft Excel.
- Look at the Index Rules column for your index pairs. This will have several notations:
IX= This is either A, B or C for Authority, Bib or Composite index.
AL= This is the field tag the index is using.
S+= This is the list of subfields included in the search index.
CS= For Composite index definitions, this will list the indexes included in this composite search.
- Compare your existing definition with the default definition for 8.2.0 and choose the one you would like the upgrade to put in place.
- Delete the row for the index you do not wish to keep from the spreadsheet.
- Repeat steps 2-5 for each pair of index definitions in your spreadsheet.
- When all conflicts are resolved, save the revised spreadsheet as SEARCHPARM_resolved.xls in Microsoft Excel 2003 format.
- FTP SEARCHPARM_resolved.xls to /m1/voyager/xxxdb/tmp on the server.
See "Voyager Index Changes" documents for 8.2.0 and 9.2.0.
Index changes for Voyager 9.2.0 require same process described above; for 9.2.0, the files will be named SEARCHPARM_A1XX_conflicts.xls and SEARCHPARM_A1XX_resolved.xls
NOTE: This process was created to prevent custom indexes or local changes to existing indexes from being overwritten without review when a new default definition would otherwise be put in place by the upgrade. If you want the upgrade to put the new default index definitions in place for all of your search indexes, you can ignore this process (i.e., if you have no custom indexes and have never altered any existing indexes). If the upgrade does not find a SEARCHPARM_resolved.xls (or SEARCHPARM_A1XX_resolved.xls) spreadsheet with your selections, it will simply put the 8.2.x (or 9.2.x) default definitions in place.
- Article last edited: 11-Feb-2016