Downloads of v


Last Update:

21 Apr 2021

Package Maintainer(s):

Software Author(s):

  • OCLC Online Computer Library Center
  • Inc.


connexion OCLC MARC library worldcat metadata

OCLC Connexion® Client

  • 1
  • 2
  • 3 | Updated: 21 Apr 2021



Downloads of v



Software Author(s):

  • OCLC Online Computer Library Center
  • Inc.

  • 1
  • 2
  • 3
OCLC Connexion® Client

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install OCLC Connexion® Client, run the following command from the command line or from PowerShell:


To upgrade OCLC Connexion® Client, run the following command from the command line or from PowerShell:


To uninstall OCLC Connexion® Client, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade connexion -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade connexion -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure connexion installed
    name: connexion
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'connexion' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: connexion,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller connexion
   Name     = 'connexion'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'connexion':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install connexion version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 21 Apr 2021.


OCLC Connexion® is your access to the OCLC (Online Computer Library Center) system for cataloging.

Catalogers can use the Connexion client for the following functions:

  • Customize WorldCat search and browse index lists
  • Create and edit bibliographic records, including constant data
  • Open MARC field Help from Bibliographic Formats and Standards for immediate field descriptions as you catalog
  • Use authority records and control headings in bibliographic records
  • Take OCLC actions on records
  • Take OCLC actions on multiple records selected in a list
  • Export records
  • Print labels
  • Import records
  • Open OCLC system news
  • Report errors in bibliographic and authority records to OCLC quality control staff
  • Search the Library of Congress (LC) authority file
  • Complete Name Authority Cooperative Program (NACO) activities
  • Conduct peer reviews of records
  • Open a WebDewey-only session
  • Access your library’s OCLC usage statistics
  • Insert data from cited records automatically
  • Select validation options for setting holdings and exporting
  • Open a local holdings maintenance browser window to maintain local holdings records for WorldCat records
  • Catalog electronic resources by automatically extracting metadata and creating a preliminary workform
  • Search for superseded LC authority history records; opening LC distributed authority record from a history record and vice versa
  • Open guided entry windows to edit or insert fields 006, 541, or 583
  • Display a record in a “Find in a Library” view in
  • Export bibliographic records using either MARC 21 (default) or one of the following Dublin Core record standards
    • For export, select Dublin Core Qualified, Dublin Core Simple, OCLC Dublin Core Qualified, or OCLC Dublin Core Simple
    • For import, select Dublin Core Qualified or Dublin Core SimpleNote: Dublin Core standards are structured in XML
  • Access SCIPIO records describing art and rare book sales catalogs for sales from the late sixteenth century to the present
  • Catalog offline and online
  • Validate records offline
  • Use local save files as well as your library’s online save file
  • Create local constant data records, as well as online constant data, to insert often used MARC-formatted content
  • Batch process WorldCat and LC authority file searches
  • Batch process OCLC actions on records, including exports and label printing
  • Batch process setting or deleting holdings by OCLC number without first downloading the records
  • Create text strings to insert frequently used data
  • Write macros or use a macro recorder to automate frequent tasks
  • Use the client’s built-in label printing capability
  • Print local accessions lists
  • Create multiple user profiles (sets of client options) to catalog for more than one library
  • Check spelling in records
  • Choice of multiple language for the interface
  • Supports all Unicode scripts through Unicode version 8.0.0.
  • Automatically transliterate romanized data in Arabic and Persian records to Arabic script data (two ways)
  • Validate MARC-8 characters separately from record validation
  • Convert invalid CJK characters to MARC-8 automatically
  • Upload digital files to a CONTENTdm collection and automatically add field 856 to the WorldCat record that contains the URL to open the digital content (for authorized CONTENTdm users with correct setup only)
  • Define a startup action or macro to run each time you open the client
  • Use quick tools for entering command line WorldCat searches and for using and managing text strings and user tools
  • Set up a Z39.50 access to your library's integrated local system (ILS) to retrieve local bibliographic records
  • Install and use RLIN21 keyboards for entering Arabic, Cyrillic, Hebrew, and Latin scripts
  • Add variant name headings using MARC-8 non-Latin character sets to LC authority file records

$ErrorActionPreference = 'Stop'

[array]$key = Get-UninstallRegistryKey -SoftwareName "OCLC Connexion client*"

if ($key.Count -eq 1) {
   $GUID = "{$($key[0].UninstallString.split('{')[-1])"
   $UninstallArgs = @{
      Statements    = "/x $GUID /qn /norestart /l*v `"$($env:TEMP)\$($env:chocolateyPackageName).$($env:chocolateyPackageVersion).Uninstall.log`""
      ExeToRun      = 'msiexec'
      validExitCodes= @(0, 3010, 1605, 1614, 1641)
   Start-ChocolateyProcessAsAdmin @UninstallArgs

} elseif ($key.Count -gt 1) {
   Throw "Multiple installs found.  Could not safely uninstall OCLC Connexion client!"
} else {
   Write-Host "OCLC Connexion client not found.  It may have been uninstalled through other actions."

$ErrorActionPreference = 'Stop'

$WorkSpace = Join-Path $env:TEMP "$env:ChocolateyPackageName.$env:chocolateyPackageVersion"

$WebFileArgs = @{
   packageName  = $env:ChocolateyPackageName
   FileFullPath = Join-Path $WorkSpace "$env:ChocolateyPackageName.exe"
   Url          = ''
   Checksum     = '07dbb0e9a856ac9f336aff51145bd58547b2d9abb29b946841914d1e62036768'
   ChecksumType = 'sha256'
   GetOriginalFileName = $true

$PackedInstaller = Get-ChocolateyWebFile @WebFileArgs

$UnzipArgs = @{
   PackageName  = $env:ChocolateyPackageName
   FileFullPath = $PackedInstaller
   Destination  = $env:ChocolateyPackageFolder

Get-ChocolateyUnzip @UnzipArgs

$InstallArgs = @{
   PackageName    = $env:ChocolateyPackageName
   File           = (Get-ChildItem -Path $env:ChocolateyPackageFolder -Filter '*.msi').FullName
   fileType       = 'msi'
   silentArgs     = "/qn /norestart /l*v `"$($env:TEMP)\$($env:ChocolateyPackageName).$($env:chocolateyPackageVersion).MsiInstall.log`" ALLUSERS=1"
   validExitCodes = @(0, 3010, 1641)

Install-ChocolateyInstallPackage @InstallArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
OCLC Connexion® Client 178 Tuesday, April 7, 2020 Approved
OCLC Connexion® Client 2.63 385 Saturday, March 23, 2019 Approved
Discussion for the OCLC Connexion® Client Package

Ground Rules:

  • This discussion is only about OCLC Connexion® Client and the OCLC Connexion® Client package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or OCLC Connexion® Client, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus