Connexion browser problems and troubleshooting
Last revised: June 18, 2008
Known problems
Internet Explorer 7 and Connexion
Problems with CatExpress
Problems with local holdings maintenance
Problems with controlling headings
Troubleshooting checklist
Known problems
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:
Labels "file could not be located" error message
When trying to view labels, if you get the error message "OCLC Cataloging Label Program. An error occurred with file: [filename and location]. The file could not be located," this may be a problem with the browser cache files. When this occurs, open Tools/Internet Options/General/Temporary Internet Files/Settings/View Files and manually delete the cache.
Labels with diacritics
When printing labels from the Connexion browser with the OCLC Cataloging Label Program, diacritics are displayed and printed incorrectly. The Connexion client handles diacritics correctly. A third-party label program that can handle Unicode can also be used to print labels containing diacritics from a file created in the browser.
Multi-record extractor
There are multiple problems with the multi-record extractor. Until these problems are corrected, libraries should use single record-create extraction.
Special characters and diacritics in CD name and CD My Status cause errors
When you create a constant data (CD) record, avoid using the following special characters and diacritics in either the CD name or optional My status you assign to identify the CD record. These characters can cause errors when you use the CD record (retrieve, save, apply, delete, etc.). For example, errors prevent you from deleting these CD records, either singly (from the full record) or in a group (from a list of CD records). Problems occur because CD records whose names contain special characters cannot be indexed correctly.
| Do not use ... |
|
|
|
|
| Period (full stop) |
. |
|
Ampersand |
& |
| Comma |
, |
|
Pound sign |
# |
| Semi-colon |
; |
|
Double quotation marks |
" " |
| Colon |
: |
|
Apostrophe |
' |
| Underscore |
_ |
|
Percent mark |
% |
| Asterisk |
* |
|
Question mark |
? |
| Plus sign |
+ |
|
Slash |
/ |
To be sure that CD records are problem-free, use only standard letters (upper- and lowercase) and numbers in CD names and My Statuses.
(Updated 20061201)
Automatic sort of bibliographic constant data search results does not work
When you retrieve bibliographic constant data records, the list is not sorted alphabetically by constant data name as it should be. To sort by name, open the Action/Sort list and click Sort By Name.
Connexion sorts words that include diacritics out of order in WorldCat derived and keyword search results
(Partly resolved - for derived search results only - with system changes 20051113)
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 keyword search for lutz, m* returns Lutz, Madeleine, Lütz, Manfred, and Lutz, Marcel, but Lütz, Manfred incorrectly appears first in the sequence.
- 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.
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)
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)
Browsing for a personal name with abbreviated surname -- replace the period with a space in browse query
When browsing for a personal name that ends with a period as part of an abbreviated surname, do not include the period in the browse query. To retrieve the desired heading, substitute a space for the period.
Example:
To browse for the name Harry L., enter the following query:
L , Harry
Not: L., Harry
or: L, Harry
(Added 20080618)
Validation set to None may have implications for offline services
If you have validation set to None for setting holdings (General tab > Admin > Cataloging Options / Validation Levels), 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)
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 list, Validate Record) before exporting or when you have the validation level set to "Full" in the General tab, Preferences, Cataloging Options, under Validation Level Options.
If you used Edit, Validate Record, 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)
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. They 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 retieve 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)
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)
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)
Pathfinder CD: Cannot apply default constant data automatically when creating a pathfinder
When you create a pathfinder record and attempt to include default constant data automatically, your action ends with the misleading error message:
"Your default constant data has been deleted (5462)."
Workaround: Apply your default constant data manually.
Pathfinder default CD: Cannot show Default CD (Pathfinders tab)
When you select Default CD on the Show list (Pathfinders tab), your action ends with a system error message:
"System Failure Page: Unable to successfully complete transaction"
Workaround: Search the Pathfinder constant data file and view your default constant data record.
(Added 20070320)
Internet Explorer 7 and Connexion
Problems using IE7 with Connexion browser: workarounds
OCLC is committed to supporting Internet Explorer 7 for Connexion, with the understanding that IE7 is a new product and may take time to become as stable as Internet Explorer 6. As Connexion issues specifically related to using IE7 are identified, OCLC will work to provide an application change or suggest possible workarounds.
However, since IE7 is a recent release, OCLC does not currently recommend upgrading, except in cases where users need to access another web application that requires features only found in IE7. For those who do wish to consider upgrading to IE7, this document provides information on Connexion issues when running Windows XP. At this time, OCLC has not yet tested IE7 running the Vista operating system.
The attached document describes problems that Connexion browser users may encounter with IE7 and explains a workaround to address each issue.
Workarounds for problems using Connexion with IE7
Problems with CatExpress
Cannot edit records with double quotes in title
When you take the Edit Record action to edit a record that contains double quotation marks in the Title field, blue horizontal lines appear at the top of the record screen. You cannot edit these records in CatExpress.
Workaround: Use the Save to Catalog command to export the record or add it to your MARC Subscription file. Then retrieve the record, add it to your local catalog, and complete editing in your local library system.
(Added 20060908)
Back to top
Problems with local holdings maintenance
Cannot print local holdings constant data records from Actions drop-down list
When you try to print local holdings constant data in display or edit mode using Print on the Actions drop-down list, a blank record prints.
(Added 20060220)
Back to top
Problems with controlling headings
When you attempt to control a heading, Connexion displays an empty Control Headings window and the heading cannot be controlled
This problem occurs when using Internet Explorer 7.0.
Workaround
Before you try to control the heading, in the bibliographic record, delete the ending punctuation. Then try again to control the heading.
Note: The heading-control function automatically supplies the correct punctuation as part of controlling the heading.
(Added 20070212)
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 headings 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 20060719)
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 punctuationit 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.
Cannot control some headings that contain a dollar sign ($)
For example, in bibliographic record #61503673, the 1xx should control as ARN06530665, but instead controls as ARN06740037.
Recommendation: Until this problem is resolved, headings containing a dollar sign should not be uncontrolled.
(Added 20051213)
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. OCLC staff will resolve this inconsistency as part of improvements to Connexion.
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 fields 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.
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
Troubleshooting checklist
The following questions, issues, and instructions may help you pinpoint or resolve problems you encounter while using Connexion browser.
1. Collect information.
The following questions will help you define the problem:
- What are the symptoms?
- When did this problem start?
- Can you recall any exact error message text:?
- Does this function work properly when you use Connexion browser on other computers in your office?
- Has Connexion browser ever worked on this computer without these problems?
- Does the problem occur in the same place every time, such as clicking a particular link or performing a search with specific data?
- Can you provide the HTML source for the screen you were using?
First step (any browser): Right-click within the frame (screen area) that shows the problem, such as record text or a results list; do not right-click on the navigation bar, header bar, jump bar or command list. Then follow the procedure for your browser.
Internet Explorer: On the popup context menu select View Source. In the window containing the HTML code, open the File menu and select Save As. In the Save As dialog box, specify a location and then click Save.
Netscape: On the popup context menu select This Frame. On the submenu select View Frame Source. In the window containing the HTML code, open the File menu and select Save Page As. In the Save As dialog box, specify a location and then click Save.
Submit the source file with your problem report. Screen captures can be useful as well, to document complex error messages or dialog boxes.
- Are you using PopNot or another program that prevents pop-up windows from opening? Such a programs may reside under your browser’s toolbar.
Note: A bug in PopNot prevents it from working properly with some Connexion screens. When you turn off PopNot by right-clicking its icon (so that the light bulb icon is visible on the taskbar but dimmed), the program remains resident and can still cause problems. You must completely exit or stop PopNot to avoid these problems.
2. Verify that you are using supported versions of your operating system and browser.
- For the Microsoft Windows version, click the Start button on the taskbar and look at the left side of the start menu. Or right-click on My Computer, click Properties, and select the General tab; operating system and service pack versions are listed under System.
- For the Netscape browser version, open the Help menu and select About Communicator.
- For the Internet Explorer version, open the Help menu and select About Internet Explorer.
3. Confirm that you are not using the Back button, Refresh button, or Stop button within OCLC Connexion browser.
Using these buttons can cause errors because what appears on your screen does not match what the servers are doing behind the scenes.
4. Check the browser's cache settings.
Using the recommended settings can improve browser performance by instructing the browser to display stored pages, rather than download fresh pages from the server, when revisiting a site.
Recommended cache settings
- Set your browser to refresh Web pages automatically when necessary. Do not specify that the browser refresh a page each time you view it.
- Allocate adequate disk space for the browser cache. 10 MB is recommended. Do not specify zero space for the cache, and avoid allowing it to be larger than 50 MB.
- Do not configure Internet Explorer to clear the cache each time you exit the browser (Supported Netscape browsers have no equivalent setting).
- Retain the browser's History (log of recently visited sites) for 4 days.
- Before changing settings. Before changing cache/history settings, write down your current settings so that you can restore them if the new settings cause problems.
- If you experience problems with Connexion browser or with other web-based applications when using the recommended cache settings, see 6. Resolve caching problems.
Internet Explorer
- On the Tools menu click Internet Options.
- On the General tab, under Temporary Internet Files, click Settings.
- In the Settings dialog box, under Check for newer versions of stored pages, click Automatically.
- Under Amount of disk space to use, type 10 in the text box.
- Then click OK to close the Settings dialog box.
- On the General tab, under History, for Days to keep pages in history, type 4 in the text box.
- On the Advanced tab, under Security (the last group of items in the list), clear (uncheck) the check box labeled Empty Temporary Internet Files folder when browser is closed.
- Click OK to close the Internet Options dialog box.
Netscape
- On the Edit menu click Preferences.
- In the left pane of the Preferences dialog box, under Navigator, click History.
- In the right pane (the History panel), under Browsing history, for Remember visited pages for the last __ days, type 4 in the text box.
- In the left pane of the Preferences dialog box, under Advanced, click Cache.
- In the right pane (the Cache panel), under Set Cache Options, change the number in the text box to 10. Make sure this number is not 0.
- Under Compare the page in the cache to the page on the network, select When the page is out of date.
- Then click OK to apply the changes and close the dialog box.
5. Clear the browser cache.
Note: Work through all of the steps for your browser and then restart your browser; do not restart after each configuration change.
Note: If your institution uses a firewall or proxy server, that program may also have a cache.
- If you experience JavaScript errors immediately after a Connexion release, try refreshing affected pages first, or clear your cache once rather than changing your settings.
- Other symptoms of caching problems include: old data repeatedly appearing; check boxes not remaining selected; and changes not being retained.
- For best browser performance, do not clear the cache more often than necessary.
- If clearing the cache does not solve a persistent caching problem, see 6. Resolve caching problems.
Internet Explorer
- Log off Connexion browser.
- Close all Internet Explorer windows, including popups. This step is essential for your cache to be cleared completely.
- Start just one Internet Explorer window and navigate to a non-OCLC site such as Yahoo or Google. Do not start any other IE windows until after you complete the cache-clearing procedure.
- On the Tools menu click Internet Options.
- On the General tab, under Temporary Internet Files, click the Delete Files button.
- In the Delete Files dialog box, select the Delete all offline content check box and then click OK.
- Click OK to close the Internet Options dialog box.
- Close, and then restart, Internet Explorer.
Netscape
- Log off Connexion browser.
- Close all Netscape windows, including popups. This step is essential for your cache to be cleared completely.
- Start just one Netscape window and navigate to a non-OCLC site such as Yahoo or Google. Do not start any other browser windows until after you complete the cache-clearing procedure.
- On the Edit menu click Preferences.
- In the left panel, under Advanced, click Cache.
- Click the Clear Cache button and then click OK to close the Preferences dialog box.
- Close, and then restart, Netscape.
Note on cache size
By default, recent versions of Internet Explorer assign a very large value for cache size.
In some cases it may be 200 MB or higher. Unless you regularly download many large
video or Flash files, we recommend that you reduce the value for 'Amount of disk space
to use' to 10 MB. This is more than sufficient for most users and greatly reduces browser overhead for maintaining the cache.
Netscape, Mozilla, and Firefox generally default to between 5 and 50 MB of cache. You can accept their defaults unless you experience performance problems.
To improve performance, it may help to change the cache size to 10 MB. A cache that is too large
often causes just as many problems as one that is too small.
6. Resolve caching problems
- If, after using the previously recommended cache settings and occasionally clearing the cache, you observe caching problems, you may need to change cache settings to correct the problem.
- Suggested changes. This section recommends that you set your browser to refresh pages every time you visit a page. Using the settings given in this section slows performance but can improve reliability when a workstation has a cache problem that causes the browser to display expired pages or incorrect data.
- These settings should be compatible with other web-based applications, including the following OCLC services: FirstSearch, NetLibrary, and QuestionPoint.
- Before changing cache settings. Before changing cache settings, write down your current settings so that you can restore them if the new settings cause problems.
Internet Explorer
- On the Tools menu click Internet Options.
- On the General tab, , click Settings.
- In the Settings dialog box, under Check for newer versions of stored pages, click Every visit to the page.
- Then click OK to close the Settings dialog box.
- On the General tab, under Temporary Internet Files, click the Delete Files button.
- In the Delete Files dialog box, select the Delete all offline content check box and then click OK.
- On the Advanced tab, under Security (the last group of items in the list), select (check) the check box labeled Empty Temporary Internet Files folder when browser is closed.
- Click OK to close the Internet Options dialog box.
Netscape
- On the Edit menu click Preferences.
- In the left pane of the Preferences dialog box, under Advanced, click Cache.
- In the right pane (the Cache panel), under Compare the page in the cache to the page on the network, select Every time I visit the page.
- At the top of the Cache panel, click the Clear Cache button.
- Then click OK to apply the changes and close the dialog box.
7. Try an alternative browser.
Switch from Netscape to Internet Explorer; or vice-versa. The latest version of either browser should work, but many versions have quirks that may cause problems in some situations.
8. Does the problem happen only when you perform a specific workflow?
If so, test with the same operating system version and browser version to verify the problem can be duplicated on a separate computer and/or that the problem can be duplicated by your technical staff. If you plan contact OCLC Customer Support, write down the steps that produce the problem (your workflow) so that CSD staff can use the same system and browser versions and follow your exact workflow to verify the problem.
9. Check with your system administrator to determine whether a firewall or proxy server is caching Web sites.
If so, have the administrator exclude any caching for OCLC Web sites. It is preferable to exclude the entire oclc.org domain if the firewall supports this approach. If you cannot exclude the entire domain, exclude the following specific addresses: connexion.oclc.org, illweb.oclc.org, firstsearch.oclc.org, catexpress.oclc.org, psw.oclc.org, www.oclc.org, and questionpoint.org.
10. Check the browser's security and privacy settings.
Internet Explorer
Internet Explorer has security options that you can customize to provide different levels of security for different categories of Web sites. The best strategy is to add the OCLC sites to the Trusted Sites zone so security to other sites is not affected.
- On the Tools menu click Internet Options.
- Choose the Security tab and select the Trusted Sites icon.
- Set the security level to Low.
If security for Trusted Sites is set to Custom, click the Custom Level button. In the Security Settings dialog box, in the Reset to: list, select Low and then click the Reset button.
- Click the Sites button and clear the Require server verification check box.
- Add http://*.oclc.org to the Trusted Sites zone.
- Click OK to exit the Trusted Sites dialog box.
- On the Privacy tab, adjust the setting to Medium or Medium High.
- Click OK to close the Internet Options dialog box.
- Restart Internet Explorer to ensure changes take effect.
Netscape
- On the Edit menu click Preferences.
- In the left panel, click to expand the Advanced item.
- On the Advanced panel, select the Enable Java check box.
- In the left panel, click Scripts & Plugins. On the Scripts & Plugins screen, under Enable JavaScript for, select the Navigator check box.
- In the left panel, click to expand Privacy & Security. Then click the Cookies item.
- In the right panel, select Enable cookies based on privacy settings. The default setting, Medium, works well with Connexion. To check or adjust the privacy setting, click the View button (next to the list of options on the Cookies panel). When finished, click OK to close the Privacy Settings dialog box.
- Click OK to close the Preferences window.
- Restart Netscape to ensure changes take effect.
11. Check the browser's proxy settings, connection options, and other network preferences.
Internet Explorer
- On the Tools menu click Internet Options.
- Click the Connections tab.
- If you are connecting through a local area network, there should be no dial-up sites listed in the Dial-up Settings box. If you are connecting through a dial-up connection, verify the correct connection is selected.
- For a LAN connection, select the LAN Settings button. For a dial-up connection, select the correct connection and click the Settings button.
- Clear the Automatically detect settings, Use automatic configuration script, and Use a proxy server check boxes if they are selected.
- Click OK to close the Internet Options dialog box.
- Restart Internet Explorer to ensure changes take effect.
Netscape
- On the Edit menu click Preferences.
- In the left panel, click to expand the Advanced item.
- Click Proxies.
- On the Proxies screen select Direct Connection to the Internet or add oclc.org to the No proxy for box.
- Click OK to close the Preferences window.
- Restart Netscape to ensure changes take effect.
12. Check that content managers are not being used.
Content managers or filters can interfere with the display of OCLC content. Products such as Cyber Patrol, Net Nanny, Cyber Sitter, SurfWatch, and WebSense filter out or limit content from Web sites based on certain criteria. These products can erroneously deny access to OCLC's Web interfaces. Or they may prevent the use of certain features, producing strange results. In Internet Explorer, check the Content tab in the Internet Options dialog box. Ask your system administrator whether any content managers are in use, and provide addresses for the OCLC Web interfaces you use. All content managers should be disabled while using Connexion browser.
13. Ask your system administrator to rule out network problems.
Administrators can test by using the ping and tracert functions and network troubleshooting tools.
Back to top
Boîte à outils des bibliothécaires
