Skip to page content

Connexion : Assistance technique, formation et documentation : Connexion client known problems

Connexion client problems and troubleshooting

Last revised: April 29, 2008

Jump to: Upgrading | Searching | Editing | Constant data | Saving records | Validating | Creating records | Importing | Taking actions | Labels | Batch processing | Controlling headings | Transliteration, diacritics, non-Latin scripts | Macros | SCIPIO | Other | Problems resolved in versions 2.00 and 2.10

Problems in Version 2.10

See the latest posted problem.

Upgrading

The first time you run the client after installing/upgrading to the next version, the client desktop icon for opening the program may not work

This problem may occur if you run the Connexion client under Windows XP or Vista using a User security level (not local administrator).

Workaround: Create your own client desktop icon:

  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 file, and then click Create Shortcut.
  3. Drag the shortcut to the desktop. It becomes an icon.
  4. Optional. To shorten or change the name of the icon, single-click the text attached to the icon, and then single-click again to select and edit the text.
  5. Optional. Right-click the original shortcut icon that did not work and click Delete to remove it from the desktop. Deleting a shortcut from the desktop does not delete the software.

Note: This workaround has also been added to Getting Started with OCLC Connexion Client in the section on downloading and installing.

(Added 20070727)

You may be denied access to OCLC files after you upgrade, preventing you from running the client

You may receive an "Access denied" error the first time you run the client after installing. The error message lists a file starting in the X:\Program Files\OCLC\Connexion\Program folder and may list others. Access may be denied to the following files, among others:

  • 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 Adminstrators group.
  6. Log on as the User. Restart the client. You do not have to repeat this procedure.

(Added 20060929)

During upgrade, installation fails; you are asked for Connexion.msi path

In some cases, the upgrade installation might fail with a message asking the path to your Connexion.msi file. To resolve, download and run the Windows Installer Cleanup Utility.

The installation program may re-run the first time you open the client after installing the client-only software

If this problem occurs, it happens only the first time you run the new version. The problem does not affect the client's performance.

(Added 20080211; removed from Getting Started)

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

This problem may occur only for those who use Windows XP or Vista and run the client under a User security level. If this happens, create a new shortcut and delete the non-functional one:

  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.

    Tip: To shorten or change the name of the icon you created, single-click the text attached to the icon, and then single-click again to select and edit the text.

(Added 20080211; removed from Getting Started)

If you do not uninstall the client before upgrading, changing the "Install for everyone or just for you" setting during upgrade makes the client inoperable

Please note that 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.
(Added 20080211; removed from Getting Started)

The client may be missing the graphical diacritics and special characters selection box after you upgrade if you did not uninstall the previous client version

The Enter Diacritics and Special Characters window (Edit > Enter Diacritics) has both pictures of diacritics and characters and a drop-down list of their names, from either of which you can choose a character to enter in a record or a search. If you are missing the graphics in this window, close the client and all open programs, and then close down and re-start your workstation. (Note: Even when the graphics are missing, you can still select a character from the list.)

(Added 20080211)

An OCLC Gateway export destination you set up before upgrading may not work after upgrading if you did not uninstall the previous client version

If you set up an OCLC Gateway export destination in a previous version of the client, but export does not behave as expected after you upgrade, check or reset options in Tools > Options > Export:

  1. In the Export tab, select the OCLC Gateway export by name in the Destinations list and click Edit.
  2. In the OCLC Gateway Export - Local System Settings window, check and correct settings if needed.

(Added 20080211)

Back to top

Searching

Connexion sorts words that include diacritics out of order in WorldCat derived and keyword search results
(Partly resolved with system changes November 2005 - resolved for derived search results only)

When WorldCat derived and keyword search results include words with diacritics, the records sort out of sequence with words that do not have diacritics, whether you use the client or the browser interface.

Examples:

  • 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.

Workarounds: (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.

(Added 20050822)

Incorrect record counts in browse results for authority records

Browse results for authority records display headings and record counts from a list that the system does not update immediately when authority records are added or replaced. In the past, updates were immediate but caused an adverse effect on overall system response time. This was formerly a problem with WorldCat search results. OCLC is working on database architecture and indexing to overcome this problem for authority browse results, while balancing the need to provide reasonable system response time for searching.

(Added 20060202)

Caution: Copying and pasting browse terms that contain diacritics to browse the LC authority file may prevent Connexion from normalizing results correctly

If you paste terms that contain diacritics into the client from another program or file to browse the LC names and subjects authority file, Connexion may not be able to normalize the results correctly.

(Added 20050822)

Caution: Whether to retain or omit a comma in a browse term for the LC names and subjects authority file depends on the index you browse

Retain a comma in a term you use to browse the LC authority file only when you browse the personal name index and the topical index. Exclude a comma from a term when you browse the LCSH index.

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

(Added 20050822)

WorldCat group list headings may include records that do not match the group heading (document type) but actually are correctly retrieved by your search

Currently, records that meet specific requirements (presence of 856 with appropriate indicators) are given the primary document type of Internet Resources, but Connexion group lists do not yet include Internet Resources as a separate group heading. Instead, Internet resource records are included under Books in group lists, regardless of how the fixed field is coded. These groupings are for display purposes only, and reflect the actual format of the records, except for the inclusion of these Internet resources in any format.

For example, the search pb:naxos and hl:trios and mt:rec retrieves records for streaming video that are grouped under the Books format, even though the records are in the sound recordings format, with 006 fields for electronic resource/computer files, an 007 for sound recordings, and an 007 for the computer file.

OCLC is working on resolving this situation. For now, you can limit a search to non-Internet items (not mt:url) to retrieve and display non-Internet items under the "correct" format heading in a group list. If you intend to retrieve both Internet and non-Internet items, be aware that any Internet resource records that match the search will be found under the Books format if you get a WorldCat group list.

(Added 20051216)

The first time you display a WorldCat record using a new user profile, the record window is not maximized in the client window.

The first WorldCat record displayed using a new user profile is a truncated view in the upper left part of the work area in the client window. To maximize the record window, use Window, Tile Vertically or Tile Horizontally.

(Added 20060614)

CJK script searches enclosed in double quotation marks are not working correctly

Enclosing a WorldCat search string in quotation marks ("[search string"]) retrieves only records containing the exact search string matched character by character. Currently, however, if the search string is a CJK script string, the results include both records containing the exact string (correct) and records containing each character in the string (treated as a word) (incorrect).

(Added 20070308)

Back to top

Editing

Overwrite/insert editing mode changes incorrectly

Sometimes the editing mode shifts incorrectly in the client from overwrite to insert or vice versa. So far, the cause, circumstances, and frequency of this problem are undetermined.

Highlight with mouse from right to left to delete a field may shift data in next field

Has been added as a "Caution" to client documentation and Help.

(Updated 20051219)

Edit a record, then save it, and then lock the record. Your edits are lost.

The client gives no warning but does not retain your edits in this workflow scenario.

(Added 20061214)

Back to top

Constant data

Save constant data from the local save file to the online save file fails if online record already has a record with the same name

Has been added as a "Caution" to client documentation and Help.

(Updated 20051219)

For online constant data (CD) only, diacritics and special characters in CD name and CD My Status cause errors

Has been added as a "Caution" to client documentation and Help in topic about creating constant data, along with a list of the error-causing characters.

(Updated 20061214)

Back to top

Saving records

None

Back to top

Validating

Validation set to None may have implications for offline services

If you have validation set to None for setting holdings (Tools > Options > General / Validation Options), invalid characters in records will not produce an error message when you update holdings on an existing record or delete your holdings. However, the system will convert invalid characters to fill characters in your archive files. This may affect your MARC subscription or local database creation.

(Added 20051113)

Back to top

Creating records

None

Back to top

Importing records

None

Back to top

Taking actions

Inappropriate message may appear when exporting authority records

On occasion, you may receive the following message when you export authority records: "This main entry exists in another authority record: LCCN=n ######## ARN=oca########." You receive the message as a result of a process that normalizes the main entry to help reduce duplicate records. Currently, tags are not considered in the normalization process.

The message occurs when you validate the record (Edit, Validate) before exporting or when you have the validation level set to "Full" in the Tools, Options, General tab (click Validation Level Options).

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.

(Updated 20051219)

False error message may result from system duplicate detection when new authority records are added or master records are replaced

The system uses NACO Normalization rules to match the 1XX heading of any record you want to add or replace against the 1XX and 4XX name headings to detect duplicates. However, the system incorrectly ignores the first comma in subfield a, which results in an incorrect validation error message—This main entry exists in another authority record: LCCN=xx xxxxx ARN=ocaxxxxx. If you receive this message as a result of this problem, and the new/replace heading is not a duplicate, click OK to close the message, and simply re-issue the Add or Replace command to successfully add or replace the record.

(Added 20060614)

Back to top

Labels

None

Back to top

Batch processing

None

Back to top

Controlling headings

Control headings software may make a substitution when you try to control a name/title heading that has no associated authority record

In some cases, when you attempt to control a name/title heading that is not represented by an authority record, the controlling software identifies subject subdivision authority records that match elements of the title portion of the heading.

For example, for the heading Alcock, John, 1715-1806. t Voluntaries, m organs, r D major, the control headings feature wants to change m organs to x Organs, as shown in the image below:

The workaround for this problem is to tag the heading as a 710 heading, which will open a single control window instead of the multi-control window, where you can control the heading as shown in the four images below:

Image 1 - Following the attempt to control the heading, the unmatched name/title heading is presented in the Normalized Query Terms box:

_________________________________________________________________________________

_________________________________________________________________________________

Image 2 - Remove (copy or cut) the title portion of the heading, leaving only the name portion of the heading in the Normalized Query Terms box. After removing the title portion, the system returns corresponding matches for the name portion:

_________________________________________________________________________________

_________________________________________________________________________________

Image 3 - To append the uncontrolled title information, click Modify Heading (see image 2) to move the controlled name into the area illustrated. In the New Query Terms box, enter the title information, and then click Modify Heading to append the uncontrolled data to the controlled heading:

_________________________________________________________________________________

_________________________________________________________________________________

Image 4 - To move the partially controlled heading into the bibliographic record, click Insert Selected Authority:

_________________________________________________________________________________

_________________________________________________________________________________

When the process is complete and the heading is inserted into the bibliographic record, the tag is correctly changed from 710 to 700:

(Added 20071220)

Partially controlled headings in bibliographic records appear as completely controlled headings

The text of the entire field of controlled headings in bibliographic records appears as a link to the controlling authority record (blue underlined text), even if the heading is only partly controlled. This is a display problem only. The link continues to work as it should: If you click the controlled part of the heading, the authority record opens; if you click a part of a heading that appears to be controlled but is not, the authority record does not open.

Example: In the bibliographic record with OCLC number 69679978, the 830 field shown below incorrectly appears to be fully controlled. The volume designation (‡v Beiheft 142) is not controlled; if you click that subfield, the authority record does not open.

830  0 Beihefte zur Zeitschrift fürdie neutestamentliche Wissenschaft und die Kunde der älteren Kirche; ‡v Beiheft 142.

(Added 20070216)

When you attempt to control a heading, Connexion displays an empty Control Headings window and the heading cannot be controlled

This problem occurs if you use Internet Explorer 7.0.

Workaround: Before you try to control the heading, in the bibliographic record, delete the ending punctuation, and then try to control the heading again. The control headings process automatically supplies the correct punctuation.

(Added 20070216)

Using control headings commands may cause an error

Occasionally, when you control a single heading or control all headings in a record via the commands Edit, Control Headings, All (or <Shift><F11>) or Edit, Control Headings, Single (or <F11>), you get an error message that no controllable fields were found in the record.

Re-executing the command usually works.

After controlling a heading, you find that the $x (or $v) is incorrectly changed. The Control Headings window did not open when you used the control heading command. Instead, the incorrect heading was automatically inserted into the bibliographic record

In most cases, this scenario results from the presence of a pre-coordinated authority record. Because the system tries to match the heading to the fullest form, normalization finds the full heading and changes $x to $v (or vice versa).

Workaround/Example: You can block the system from finding the fullest match upon the initial query.

For example, if you control the heading Education $v Exhibitions, the system changes it incorrectly to Education $x Exhibitions based on the authority record sh 85041006.

To block this match, in the record, enter the heading with a typographical error in the subdivision (for example, $v Exxhibitions ) and then control the heading. The error you introduced prevents a match to the incorrect heading. Instead, the Control Headings window opens.

In the list of headings, click Modify Heading next to the heading Education to move the controlled portion of the heading into the modified heading area.

In the New Query box, enter $v Exhibitions , and click Match Best. You now have the following choices:

Click Append to Heading next to the correct subdivision, $v Exhibitions, to complete the heading, and then click Insert Heading to insert it into the bibliographic record

(Updated 20060718)

Punctuation: After controlling a heading, the punctuation in the controlled heading differs from the punctuation entered, and/or from the punctuation present in the authority record.

When controlling headings, the system matches headings against the authority file. This matching process invokes a normalization process, which collapses all punctuation and spaces, removes subfield delimiters and codes, and is not case sensitive. If more than a single authority record is used to create a heading (e.g., in particular subject headings) or a single authority record is used to control part of a heading (e.g., corporate bodies), the system adds/deletes punctuation between controlled/uncontrolled subfields. Some name authority headings are in the 'old' style that incorrectly ends in terminal punctuation, and some name authority headings end with a period that is part of an abbreviation.

This normalization process is the reason headings that are not matched but appear in the Query Box lack punctuation—it was removed as part of the normalization process. In addition, when headings are ‘Appended’ as part of the controlling process, the software programs that apply punctuation are not invoked until the command ‘Insert Heading’ is selected.

For most types of headings, the results of the applied punctuation are correct.  However, there are some types of materials, in particular uniform titles for music and manuscripts, for which punctuation rules yield incorrect results. The majority of the incorrect applications involve punctuation preceding and following $n in uniform titles. Other type of headings with known problems in the handling of punctuation include: punctuation for personal names that contain a two letter initialism and precede $q or $c, respectively, and punctuation for corporate name subject headings that end in an abbreviation and are followed by $v or $x.

Workaround

If punctuation is incorrectly altered when you control a heading, uncontrol the heading, correct the punctuation, and leave the heading uncontrolled.

Tag flips: The control process returns a controlled heading in which the tag has mysteriously changed.

When controlling headings, the system matches headings against the authority file.The matching process invokes a normalization process, which collapses all punctuation and subfield codes and is not case-sensitive. Nor does normalization retain the tag information associated with the heading. The matching process finds the fullest match possible, but inevitably, the results of normalization, combined with finding the fullest match, may occasionally produce unexpected matches.

For example, the problem occurs when you control the geographic-tagged subject heading Taiwan $v Periodicals. In this case, the normalized heading is taiwanperiodicals. When matched against the Library of Congress Authority File, the heading matches a topical subject heading Taiwan periodicals. The system automatically inserts the heading into the bibliographic record and flips the tag from 651 to 650. This phenomenon is due in part to normalization, but also to the structure of LCSH; an authority record does not exist for the complete geographic heading Taiwan and the form subdivision $v Periodicals.

The goal of automatically controlling headings is to achieve balance between the matching process and normalization and still assist users as much as possible with correcting tags, indicators, and subfield coding. One area that requires balance is determining when a heading is properly coded. A common error is mistagging headings--e.g. 650 fields that should be tagged as 651 fields. Another common tagging error is coding headings for fictitious characters as 600 fields, when they should be tagged as 650 fields. Review results carefully when you control headings, knowing that the process can yield unexpected results.

Workaround

The geographic heading with the form subdivision can be controlled by blocking the automatic link to the topical heading. To block this match, in the record, enter the heading with a typographical error in one or both of the subdivisions (for example, $v Periodicalx) and then control the heading. The error prevents a match to the incorrect heading. Instead, the Control Headings window opens.

In the list of headings, click Modify Heading next to the heading Taiwan to move the controlled portion of the heading into the modified heading area.

In the New Query box, enter $v Periodicals, and click Match Best.

Click Append to Heading next to the correct subdivision, $v Periodicals, and then click Insert Heading to insert it into the bibliographic record.

(Updated 20060608)

Name subject heading uncontrollable

The ability to partially control some types of name-subject headings (6xx fields) differs from the functionality to control name headings tagged as a main or added entry.

Example:
610 20 OCLC. $b Migration Information Programme

This heading is not represented by an authority record, nor is the parent body ($a OCLC) a candidate for controlling when tagged as a name-subject heading.

However, when the same heading is tagged as a main or added entry (110 or 710), the parent body ($a OCLC) can be controlled. The difference is due to the processes used to support the multi-control functionality.

(Updated 20060608)

Series headings

Currently, only series headings coded as 8xx are candidates for controlling. While series headings are access points, the primary function of the 4xx fields is to reflect the transcription of series statement on an item, and secondarily to provide access as a series added entry. Currently, if 440 fields were controlled, the 'correct' 440 heading text could be incorrectly changed to the new heading in the authority record. This would result in the loss of the field's primary function of transcribing the series statement as found on the item.

Series headings in 8XX fields

Although 8XX fields are controllable, if an authority record does not exist for the title part of a series name title heading in fields 800, 810, 811, or 83X, and you try to partially control the heading (in addition to leaving the $v uncontrolled), the tag automatically flips from 8XX to 7XX.

(Added 20071025)

Cannot control headings when the main heading and subdivision are the same

You cannot control a heading that repeats the same text as main heading and subdivision, as in the following example:

Example: 650 [blank] 0 History $x Study and teaching (Higher) $z Poland $x History

Currently, there is no workaround. You must leave headings uncontrolled when the main heading and subdivision are the same text.

Back to top

Transliteration, diacritics, non-Latin scripts

Using the keystroke shortcut <Ctrl><D> to enter a subfield delimiter and code in non-Latin script data may not switch you back to the language/keyboard you were using, as it should, or may switch you to a different language.

When you are entering non-Latin script data and use <Ctrl><D> to automatically switch to the English keyboard and back for entering a subfield delimiter and code, the client may not switch you back to the keyboard you were using after you enter the delimiter and code. You may remain in the English keyboard or you may be in a different keyboard.

To switch to the keyboard you need, click the language indicator in the Windows system tray (small blue box with two-letter codes), and then click the language/keyboard you need, or select by using the Windows default keystroke Left <Shift><Alt> to cycle through the language indicator list.

(Added 20070727)

In Connexion client version 2.00 and higher, the Microsoft Input Method Editor (MS IME) for Korean does not convert an existing Korean hangul character into a hancha or Chinese character

If you convert a hangul syllable into a hancha or Chinese character immediately after you enter it, the conversion works correctly. The conversion does not work if you highlight an existing hangul syllable and then try to convert. The IME does not allow you to choose a Chinese character. The problem occurs with hangul syllables in records; it does not occur when you convert a hangul syllable in the WorldCat quick search box on the toolbar (or in a text box in the Search WorldCat dialog).

Workaround: Copy the hangul syllable you want to convert and paste into the WorldCat quick search text box, convert it to a Chinese character, and then and copy and paste back into the record.

(Added 20070622)

The Arabic transliteration tool handles some characters incorrectly

The list of incorrect characters has been added as a "Caution" in client documentation and Help.

(Updated 20051219)

Other Persian transliteration problems

The Persian transliterator:

  • Treats the romanized "th" as one character, Theh 062B. It should be treated as two characters, Teh 062A and Heh 0647.
  • Does not transliterate characters following the romanized miagkii znak (prime mark) correctly.

(Added 20070222)

Some diacritics/characters do not display correctly for those who use Arial Unicode MS font in Microsoft Office 2000

The version of Arial Unicode MS font included in Office 2000 (or lower versions) may cause some characters to display incorrectly. The problem has occurred, for example, with some diacritics and special characters in Vietnamese text. Upgrading to Microsoft Office 2003, which installs a version of the Arial Unicode MS font that includes a more complete character set for display, appears to solve the problem.

(Added 20060317)

Back to top

Macros

None

Back to top

SCIPIO

Error messages about taking actions on SCIPIO IRs or SCIPIO master records that involve non-SCIPIO master records do not explain the error

If you are profiled for SCIPIO and IR records (institution records), you may get an error message when you validate, replace, add, or move a SCIPIO IR or replace a SCIPIO master record when the action involves a non-SCIPIO master record. The error message is too generic: You are not authorized to [do an action]... or simply [Action] failed.

For example, errors will occur if you move a SCIPIO IR (that is, an IR with scipio in 042 subfield a) to a non-SCIPIO master record or replace a SCIPIO master record that has SCIPIO IRs attached with a non-SCIPIO master record or add a SCIPIO IR to a non-SCIPIO master record.

Note: Although SCIPIO IRs cannot be attached to non-SCIPIO master records, you can attach non-SCIPIO IRs to SCIPIO master records.

(Added 20070910)

Back to top

Other

MARC Field Help for authority records does not work

In the client, you can click Help > MARC Field Help (or press <Shift><F1>) to open a description of the field where the cursor is located in an authority record. Previously, the description opened in MARC 21 Format for Authority Data on the Library of Congress Web site. These links to authority MARC field descriptions are broken. The links cannot be fixed until the next Connexion client release (estimated time for next release to be announced later).

Workaround: In the meanwhile, you can go directly to MARC 21 Format for Authority Data at http://www.loc.gov/marc/authority/ and then click the link that opens the field description you want.

Note: MARC Field Help for bibliographic records works as always.

(Added 20080428)

Catalogers can use Connexion client 2.00 and higher via a Citrix thin client, with caution and with some limitations

OCLC has completed limited testing using version 2.00 under Citrix access. Though most functionality appears to work under testing conditions, except the two functions listed below, OCLC does not guarantee that the client will work for everyone under Citrix, since server and system configurations vary from library to library.

The following are known limitations of using the client under Citrix:

  • You cannot use macros (although staff at one library reported that their Citrix implementation contractor developed a customized way for them to use macros).
  • Writing data to a file may not work. Examples of writing to files in the client include exporting records to a file and printing records, labels, or an accession list to a file. Writing data to a file under Citrix creates files on your remote server. Depending on the location of the files, you may not have access to them. Resulting error messages are "exceptions" that do not explain that this is the problem.

(Added 20070727)

Updating holdings on records imported into the client via Z39.50 (Tools menu) does not work

If you use Update Holdings to add a Z39.50-retrieved local system record to WorldCat (the client imports the record as a workform), you receive a message that field 001 is missing the OCLC number. As a workform, the record should not have an OCLC number in field 001. This is a system error.

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

(Added 20070727)

Back to top

Problems resolved in versions 2.00 and 2.10

Multiple ISBNs in records are not saved to the online save file
(Resolved with February 2007 system installation)

When you save a record that has both a 10-digit ISBN and its equivalent 13-digit ISBN to the online save file, one of the numbers disappears. Both numbers are retained when records are saved to the local file.

When you take an action on an online save file record, such as Update (Action menu) or Validate (Edit menu), both ISBNs are restored.

To export these records: If you have the validation level set to None or Basic (None = default) in Tools, Options, General / Validation Level Options, you must validate the records before exporting to restore both ISBNs.

(Added 20070119; updated 20070219)

Using the Z39.50 connection in the client to retrieve and display a local system record may not work
(Resolved in 2.10)

When you set up and use the client Z39.50 connection (Tools > Z39.50 commands) to retrieve and import a local system record into the client, you may not be able to display the record or you may display only a partial record with truncated data due to a translation problem in the client. A patch to resolve this issue is now available. To install the patch:

  1. Close the Connexion client if it is open.
  2. In Windows Explorer, navigate to the CatRecordLib.dll file in X:\Program Files\OCLC\Connexion\Program\CatRecordLib.dll (X = the letter of your hard drive).
  3. Right-click the file, and then click Delete to delete the existing file.
  4. Open your Internet browser to http://psw.oclc.org and click Software Downloads in the list of links on the left.
  5. Type your OCLC authorization and password and click Enter.
  6. On the Software download page, double-click the Connexion client Z39.50 record display patch link.
  7. In the File Download window, click Save to save the download file to your workstation or to a server.
  8. In the Save As dialog, expand the Save in list, and select a location to save the file. Then click Save.
  9. In Windows Explorer, open the folder where you saved the patch and double-click to unzip the CatRecordLib.zip file.
  10. In the WinZip window, click Extract.
  11. In the Extract window, navigate to X :\Program Files\OCLC\Connexion\Program\ and click the Extract button.
  12. Close the Extract window.

    Caution: You may need to shut down and restart your workstation to enable the client to recognize the new file.

Note: Because the Z39.50 protocol does not support Unicode, you cannot import local system records into the client that contain Bengali, Devanagari, Tamil, or Thai script, even though the client supports these scripts.

(Updated 20070907)

SCIPIO: Display of Date of Sale in WorldCat truncated lists is in the same format as in the record
(Resolved in 2.10)

In the next version of Connexion client, the date of sale will display in the format yyyy-mm-dd.

(Added 20070910)

SCIPIO: The identification of a SCIPIO record is missing in WorldCat truncated lists
(Resolved in 2.10)

In the next version of Connexion client, the letter S will appear in the L (Contributing library) column of truncated lists to identify SCIPIO records.

(Added 20070910)

SCIPIO: The name of a SCIPIO-specific index in client index dropdown lists is inaccurate
(Resolved in 2.10)

In the next version of the client, the name of the SCIPIO indexes cx:, cx=, and cxw= (word, phrase, and whole phrase versions of the index, respectively) will change to SCIPIO - Seller/Subject. In the current version (2.00), the name is SCIPIO - Collector or Seller in the index lists of the Search WorldCat and Browse WorldCat windows.

Tips:

  • Expand the index list. By default, the client displays the ten most used indexes in the index lists of the Search WorldCat and Browse WorldCat windows. To find the SCIPIO-specific indexes, click the (plus[/minus]) button above the index list to expand to the complete list. Scroll the alphabetical list to find the indexes by name, all preceded with SCIPIO.
  • Alternative: Add SCIPIO indexes to short list. Click the button next to the plus/minus button to open the Customize Short List of Indexes window. Add SCIPIO indexes to the short list and/or move them to the top for quicker access.

    (Added 20070910)

SCIPIO: Column label in WorldCat SCIPIO-limited group list is inaccurate
(Resolved in 2.10)

When you limit WorldCat searches to SCIPIO records (Cataloging, Search, WorldCat; click Settings) and the result is a group list, results are grouped by date of sale in the SCIPIO records, not by date of publication. The date column should be labeled Date of Sale. In 2.00, the column is labeled Dates. In the next client version the label will be changed to Date of Sale.

(Added 20070910)

Microsoft® Vista operating system not supported
(Resolved in 2.00)

The Connexion client is not supported for use with Windows Vista at this time. OCLC expects to support Windows Vista with version 2.00 of the Connexion client, which is planned for release mid-year.

(Added 20070131)

Toolbar buttons for some menu commands are missing from the Toolbar Editor
(Resolved in 2.00)

Any toolbar buttons you previously added to your toolbar are still present in 1.70. However, the following toolbar buttons are missing from the Toolbar Editor:

  • Tools, CJK E-Dictionary
  • Tools, Launch Local Holdings Maintenance
  • Tools, Check Spelling
  • View, Pinned
  • View, Align Right
  • View, Back
  • View, Forward
  • View, Previous 100 Records
  • View, Next 100 Records
  • View, Previous Group
  • View, Next Group

You cannot add these buttons to the toolbar in 1.70. If you remove any of them from the toolbar in 1.70, the only way to re-add is to click Reset in the Toolbar Editor window. These toolbar buttons will be restored to the Toolbar Editor in the next client version.

Workaround for 1.70: Use the menu command or an assigned keystroke for any of the above menu items, or assign to a user tool via Tools, User Tools or via the User Tools Quick Tool on the toolbar.

(Added 20070102; revised 20070112)

Problem in 1.72 only: Batch reports for exporting and for other record actions do not include non-Latin script data
(Resolved in 2.00)

Normally, when you batch process exporting and/or other record actions for records with non-Latin title fields, the batch report shows both Latin script and non-Latin script titles if linked together, or the report shows only the non-Latin script title if it is in an unlinked field 245. In 1.72, non-Latin script titles do not display in these reports.

Note: Batch reports for searches are not affected; those reports display non-Latin data, if present.

(Added 20070412)

If non-Latin script and romanized linked fields are included in the fields-to-delete-for-export option, only the romanized field is deleted from exported records
(Resolved in 2.00)

If you set tag numbers for fields to delete from records you export (Tools, Options, Export; click Export Options), and then export records that have linked non-Latin script fields and romanized (Latin-script equivalent) fields which you specified to be omitted from exported records, only the romanized field is omitted. The non-Latin script field remains in the exported record. You must manually delete the field in your local system.

(Added 20060621)

If the Export command causes a dialog box to open, the hour glass does not go away when you use the Export toolbar button to send the Export action
(Resolved in 2.00)

Anytime the Export command causes a dialog box to display, the hour glass that indicates "action in progress" does not go away when you use the Export toolbar button, , to send the Export command. This problem does not occur when you use the Export menu command on the Action menu or the keystroke <F5>. It only occurs if you use the toolbar button.

You can make the hour glass go away and close the dialog box by:

  • Pressing the keystroke for closing a window: <Ctrl><F4>.
  • Pressing <Enter> in the dialog box after the focus has changed from the Cancel button to the Close button.
  • Double-clicking a button in the dialog box.

(Added 20070111)

In Connexion client version 1.72 only, the Microsoft Input Method Editor (MS IME) for Korean does not always correctly support hangul script for entering or editing data in records
(Resolved in 2.00)

If you use the Korean MS IME to enter or edit Korean script data, entering "hanja" script works as it should, but entering or editing "hangul" script sometimes works incorrectly. The problem occurs with hangul script data in records; it does not occur when you enter hangul script data in the WorldCat quick search box on the toolbar (or in a text box in the Search WorldCat dialog).

Workaround: Enter hangul script data in the WorldCat quick search text box, and then cut (<Ctrl><X>) or copy (<Ctrl><C>) from the text box and paste (<Ctrl><V>) into the record.

(Added 20070326)

Under certain circumstances, the system adds an extra space in field 010 that causes a validation problem
(Resolved in 2.00)

An error message, 010 occurrence 1, $a occurrence 1 - too long, occurs when you validate an authority record that has a 4-digit year in both LCCNs in field 010 (for example, n 2003084660 ‡z no2002084160). The error message occurs because the system incorrectly adds an extra space between the end of the ‡a LCCN and the next subfield mark in the 010.

There is no workaround for this problem in the client; however, you can log on to Connexion using the browser to update authority records that are impacted by the incorrect extra space in field 010.

(Added 20070227)

Back to top