Connexion client known issues

Notification you are not using the newest version of Connexion client

Some users are reporting after a Windows security feature update, they are seeing a pop up notification that says, "A new version of the Connexion client is available. You must upgrade to the new version before the announced cutoff date to continue using the client."

2.63 version will continue to be supported. 

Workaround: Close the pop up notification. 

2.63 version will continue to be supported.    

Affects: 2.63

Macro slowness and freezing  

Some users have reported issues when working with macros that use dialog screens that have caused macros to run slow or crash. 

Workaround: Restarting Connexion client may help with macro slowness.

Affects: 2.63, 3.1

RDA Toolkit direct field link resolves to login screen 

When the RDA Toolkit field help link is used within the bibliographic record editor, the link would resolve to the main RDA Toolkit login screen instead of directly to the specific field page.

Workaround: Login to the RDA Toolkit web page and navigate to the field page.

Affects: 2.63

1. Navigate to Tools > Options > Export.
2. From the Export tab, select OCLC Gateway export from the Destinations list and then click Edit.
3. From the OCLC Gateway Export - Local System Settings window, check and correct settings if needed.

Affects: 3.1, 2.63

The first time you use the client shortcut icon () on the desktop to open the client after upgrading, you may get an error that prevents the shortcut from working

1. Navigate to the Connex.exe file in X:\Program Files\OCLC\Connexion\Program\ (X = the letter of your hard drive).
2. Right-click the Connex.exe file, and then click Create Shortcut.
3. Drag the shortcut to the desktop. It becomes an icon.
4. Right-click the original shortcut icon that did not work and click Delete to remove it from the desktop.

 Note: Even when the graphics are missing, you can still select a character from the list.

 Note: OCLC recommends uninstalling before you upgrade to prevent possible problems like this one.

When you upgrade the client without first uninstalling, in the window where you select an option to install for everyone who uses the workstation or just for you, you must select the same option you selected during your original installation. If you don't and the client becomes inoperable, you must uninstall and re-install the new version.

To determine which selection you made for the original client installation, check the location of the OCLC Connexion client desktop shortcut:

• If you selected installation for you only, OCLC Connexion Client is listed in X:\Documents and Settings\[your username] \Desktop, where X = the letter of your hard drive.
• If you selected installation for everyone, OCLC Connexion Client is listed in X:\Documents and Settings\All Users\Desktop.

Affects: 2.63

• UpdateVersion.xml
• InstallCustomAction.InstallState
• AppUpdate.log

To run the client in the users group, follow this one-time procedure:

1. Log on to your workstation as Administrator.
2. Add the User to the Administrators group.
3. Log on as the User.
4. Start the client. A series of progress bars will appear. When the progress bars finish processing, the client will open.
5. Remove the User from the Administrators group.
6. Log on as the User. Restart the client. You do not have to repeat this procedure.

Affects: 2.63

In the Expanded list, both the [100] and [700] relate to the first record in the Root list, and E3 and E4, that have a period prior to the $t are represented in the second entry in the root list that contains a period at the end of the $a.

Affects: 2.63

Example: Enter sca pn:L , Harry. Do not enter L., Harry or L, Harry.

Affects: 2.63

Affects: 2.63

• A personal name derived search for lutz,m, results in the following order of records retrieved: Lutzki, Moses, Lutzky, M., Lutzky, Morton, Lütze, Max, Lützeler, Marga.
• A personal name keyword search for lutz, m* returns Lutz, Madeleine, Lütz, Manfred, and Lutz, Marcel, but Lütz, Manfred incorrectly appears first in the sequence.

1. In the client only, you can click the column heading in the list to re-sort, although the re-sort is not always 100% correct.
   Or
2. In the client or browser, browse (scan an index) for the term instead–Connexion normalizes the headings by removing the diacritics, so the results display correctly.

Affects: 2.63

Example: Browse for authors, english in the topicals index. Browse for authors english in the LCSH index.

Affects: 2.63

Workaround: Enter the text you want to add to the 250 field in a tag that is not often used, and then change the tag number to 250 after you apply constant data.

Affects: 2.63, 3.1

• Use the local save file to export records
  Or
• Use batch export if exporting from the online save file

Affects: 2.63

• Open the record you want to remove and select Delete Record from the Action menu.
  Or
• Refresh the online save file screen each time you delete records from the title list.

Affects: 2.63

If you used Edit, Validate, you can go ahead and export with no problem. If you have the validation level set to "Full," change it to "Basic" and then export the record.

Affects: 2.63

• LCSH entered correctly: Indigenous peoples--France--Colonies
• Controlled LCSH: Indigenous peoples--Colonies--France

There are situations in which art and architecture headings are presented as controllable, but when a user attempts to insert them the heading is not successfully inserted into the bibliographic record. This is due to the complex treatment of art and architecture headings in LCSH.

An example of this is when attempting to control the heading:

650 Architecture ǂz Australia ǂx History ǂy 21st century

The following headings are presented in the Control Headings window:
Architecture ‡z Australia ‡x History. [650 Fully-controlled]
Architecture ‡x History. [650]
Architecture ‡x History ‡y 21st century. >> Architecture, Modern ‡y 21st century. [650]
Architecture. [650]
Architecture, Modern. [650]
‡x History [Subdivision record]
‡y 21st century. [Subdivision record]
‡z Australia [Subdivision record]

Headings are presented with the option to either Modify Heading or Insert Heading. But at this time, the correct heading is not among the available options.

1. In the display window, one of your options is the heading missing the ending subject, (e.g., Architecture ‡z Australia ‡x History. [650 Fully-controlled]).
2. Click Modify Heading.
3. In the window, you should then see your subfield ‡y 21st century. Click Append to Heading beside it. The string is now formatted correctly.
4. Click Insert Heading to insert the controlled heading into the bibliographic record.

650 0Isreal-Arab Border Conflicts, 1949-$z Lebanon

These are cases when a pre-coordinated authority record ends in an open date (and includes a hyphen) and contains a geographic subdivision.

Currently, when attempting to control headings of this type online, the controlled inserted record in the bibliographic record appears as:

650 [blank]0      Israel-Arab Border Conflicts, 1949-‡z z Lebanon.

A workaround for this problem is to add another subdivision that requires the Controlled Heading Window to open:

For example, enter the heading:

650 [blank]0      Israel-Arab Border Conflicts, 1949-‡v Periodicals ‡z Lebanon

When the list of headings is presented, the line number associated with the correct form (Israel-Arab Border Conflicts, 1949- ǂz Lebanon) and the heading will be inserted without the incorrect character between the $z and Lebanon.

• If the authority record is not punctuated correctly, then the controlled heading in the bibliographic record will contain the same incorrect punctuation.
• In this case, OCLC prefers that you control the heading that contains the incorrect punctuation and then report the incorrectly punctuated authority record to authfile@oclc.org.

• An application, process, or Windows itself shut down abnormally during a file write operation
  This usually happens when something goes wrong while the file is being saved. The problem could be internet connectivity if the program is signed in to a service, or your computer suddenly loses power. Other problems include network issues, available computer resources, another running app or unstable process. If any of these things interrupt the process of writing to the file, the entire file may not be written or the hard drive “table of contents” does not get updated.
• A physical hard drive is fragmented
  This only applies to physical hard drives. Solid state drives are not affected. A fragmented hard drive creates more pieces in which the options.xml file will be stored. If the disk is defragmented, and the file can be stored in contiguous clusters, the write time to put the file back is reduced.
• Antivirus software
  Occasionally, antivirus software will register a false positive on the options.xml file, deleting it when the client closes and releases the file.
• Windows folder redirection is storing all AppData settings on a shared network
  Under certain circumstances, having the AppData settings on a shared network will cause an individual user’s options.xml file to be deleted each time they close and reopen the client.

Affects: 2.63

Workaround: Click the Windows menu, and then click either Tile Horizontally or Tile Vertically.

Affects: 2.63

Workaround: If you are having difficulty opening an external web page, you can copy the web address from the Properties dialog, which is available on the right-click menu for the web link. To open the website, you can then copy this information and paste it directly into address field for your browser. You can also search for the content on the OCLC Support site or open the links from the documentation that is found on the Connexion Support Web site.

Affects: 2.63

Workaround: Click the Connexion client button in the task bar, and then press and hold the Windows key () on your keyboard while you click the <Up arrow> key.

Affects: 2.63, 3.1

Workaround: Derive a new record from the Z39.50 imported record and then add to WorldCat using Update Holdings.

Affects: 2.63, 3.1