Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Publishing to OCLC

    Translatable
    To configure publishing to OCLC, you must have one of the following roles:
    • Catalog Administrator
    • Repository Administrator
    • General System Administrator
    If you are transitioning to Alma production from an environment where you have been synchronizing your records with OCLC WorldCat, see Transitioning to Alma Production from a Previous System that was used to Synchronize with OCLC WorldCat for important instructions.
    Alma provides support for you to automatically synchronize the following with the information available for your institution/library in the OCLC WorldCat catalog:
    • Bibliographic records with embedded holdings information or holdings information only
    • Electronic holdings
    For importing records from OCLC, see Importing Records from OCLC Connexion.

    Overview of Publishing to OCLC

    Publishing to OCLC exports records to a predefined FTP location from which OCLC retrieves them and synchronizes them with the WorldCat records. For information about publishing to OCLC in a collaborative network implementing a Network Zone, see the note in Managing Records in a Network Zone.
    Bibliographic records whose associated holdings records have been deleted are published as deleted records.

    When Records are Exported

    A record is exported in the following cases:
    • The record was changed or added since the last export job ran, or a staff user has manually selected the record to be exported, which is also known as forced export. (Select Force export to WorldCat from the MD Editor’s Tools > Set Management Tags menu).
      Changes include any modifications to a bibliographic record and any information that enriches it (such as holdings and item changes) according to the configuration of the publishing profile that you use such as the Publish bibliographic record (DataSync) to OCLC publishing profile or the Publish your Local Holdings Records (LHRs) to OCLC publishing profile (see the procedure Publishing Print Holdings to OCLC for more information).
    • These changes apply to both the Publish bibliographic record (DataSync) to OCLC publishing profile process and the Publish your Local Holdings Records (LHRs) to OCLC publishing profile process. In both of these processes, the published entity includes information from the bibliographic record, holdings, and items (though, not necessarily all of them). Changes include modifications that influence the published entity.
    • The record is set to Publish bib/Publish holdings only in the MD Editor (Tools > Set Management Tags > Export to WorldCat).
      Export to WorldCat Options in the MD Editor
      See Export to WorldCat in MD Editor – Tools Menu for more information.
      Regardless of the presence of an OCLC control number in the 035 field, records with and without an OCLC control number are published to OCLC if they are flagged/marked to be published to OCLC. However, when using the built-in Publish your Local Holdings Records (LHRs) to OCLC publishing profile, only holdings records related to a bibliographic record with an OCLC control number in the 035 field are published to OCLC when the bibliographic record is flagged/marked to be published to OCLC.
      Use the Tag sync external catalog advanced search parameter to locate records that are marked for publishing (see Performing an Advanced Search for a Repository Item for more information)
    • The appropriate publishing profiles have been properly defined and enabled. See Publishing Print Holdings to OCLC and Publishing Electronic Holdings to OCLC for more information regarding print and electronic publishing profiles.
    The Publish Bibliographic Record value for the publish to external catalog (OCLC) management tag is the default value in the following scenarios:
    • MD Editor (new bibliographic record and copy cataloging)
    • Quick cataloging (new item, new portfolio, and Fulfillment citation)
    • Order a bibliographic record from the Community Zone
    • Simple view - copy to catalog / link

    Publishing Related Records to OCLC

    The Alma publishing to OCLC process supports handling related records when the Publish bibliographic record (DataSync) to OCLC and the Publish your Local Holdings Records (LHRs) to OCLC publishing profiles are run. Holdings information for bibliographic records that are part of a bound-with relationship is properly published to provide an accurate representation of the inventory at the holdings library. New for May!
    See Configuring Related Records for Physical Inventory for more information regarding related records.
    When you catalog related records (create or delete), the MMS - Build Record Relations job needs to run first before the related record information can be published to OCLC. The MMS - Build Record Relations job is scheduled to run once per day. See Viewing All Scheduled Jobs for more information.

    Initial Publishing Activities with OCLC

    Prior to running your ongoing automatic synchronization process with OCLC, you need to communicate with OCLC and coordinate your configuration requirements.
    To complete your initial publishing activities:
    1. Contact OCLC and obtain an institution code symbol. If you want a specific library to have its own separate code symbol, overriding the institution symbol, you must coordinate this with OCLC and map the library code to the assigned symbol in the INSTITUTION_EXTERNAL_SYMBOL mapping table (Resource Management > Resource Configuration > Configuration Menu > Institution OCLC Symbol).
    2. Open a synchronization project with OCLC. Each such project has a project ID, which is used for data transfer activities between the institution/library and OCLC.
    3. Contact OCLC and obtain a collection ID.
    4. Configure an S/FTP connection to be used by Alma and OCLC. See Configuring S/FTP Connections. You need to select MVS for the FTP Server Type parameter in your S/FTP configuration.
      FTP Server Type Parameter in the S/FTP Configuration
      The OCLC publishing integration profile requires an S/FTP connection configured for passive mode. Ensure that FTP Passive Mode is checked in the FTP connection used for this profile.
    5. If you want to synchronize bibliographic records with embedded holdings information with the information available for your institution/library in the OCLC WorldCat catalog, you must define the field in the bibliographic record that will be used to contain holdings information and how the fields of the holdings records are to be mapped to this bibliographic field and subfields. These mappings are defined in the Map Holdings fields into Bib record OCLC mapping table (Resource Management > Resource Configuration > Configuration Menu > Map Holdings fields into Bib record OCLC).
      For example, if you want to replace the 900 b field/subfield in the OCLC bibliographic records with the 852 a field/subfield in your Alma holdings records, you would define the following mapping:
      Map Holdings Fields into Bib Records in OCLC
      You can enter any number as the targetCode.
      This information is provided to OCLC when the synchronization project is opened and is used by Alma to enrich the bibliographic records with holdings information in a way that OCLC is able to interpret.
      When you publish to OCLC, the 852 $a is set to/replaced by the institutional symbol (as specified in the OCLC institution symbol parameter in the publishing profile) or the library institutional symbol (defined in Resource Management > Resource Configuration > Configuration Menu > Record Export section > Institution OCLC Symbol) when the 852 $b matches one of the mapping table’s keys. See step 1.
    6. Customize one of the following types of print publishing profiles provided in Alma or create an electronic publishing profile to meet your requirements:
      • Publish bibliographic record (DataSync) to OCLC – Use this profile to synchronize bibliographic records with embedded holdings information with the information available for your institution/library in the OCLC WorldCat catalog.
      • Publish your local holdings records (LHRs) to OCLC – Use this profile to synchronize holdings information only with the holdings information available for your institution/library in the OCLC WorldCat catalog.
      See the procedures Publishing Print Holdings to OCLC and Publishing Electronic Holdings to OCLC for more information.

    Publishing Print Holdings to OCLC

    Synchronizing your libraries’ print holdings from Alma to WorldCat can be accomplished with the Publish bibliographic record (DataSync) to OCLC or Publish your local holdings records (LHRs) to OCLC publishing profiles provided with Alma. Refer to the following procedure to tailor either of these profiles for your use. A scheduled job for Publishing to OCLC - Bibliographic Records is created.
    To configure an OCLC print publishing profile:
    1. On the Publishing Profiles page (Resource Management > Resource Configuration > Configuration Menu > Record Export > Publishing Profiles), choose either Publish bibliographic record (DataSync) to OCLC or Publish your holdings records (LHRs) to OCLC (see Initial Publishing Activities with OCLC) and select Actions > Edit. The Publishing Profile Details page opens.
      Publishing Profile Details Page
    2. Complete the parameters on the Publishing Profile Details page. Use the table below for a description of these parameters.
      Publishing Profile Details Page Parameters (OCLC)
      Parameter Description
      Profile Details section:
      Profile name Modify the name to meet your requirements.
      Profile description Modify the description to further identify this profile.
      OCLC institution symbol Enter the institution/library code symbol previously agreed upon with OCLC (see the configuration process outline above).
      Project ID Enter the synchronization project ID previously agreed upon with OCLC (see the configuration process outline above).
      Collection ID Enter the collection ID previously agreed upon with OCLC (see the configuration process outline above). If this field is populated, the published file name will include the institution symbol and collection ID. If this field is not populated, the published file name will not include the collection ID. For information as to when this is required by OCLC, contact OCLC.
      Publishing mode: Incremental Use this option to publish your ongoing OCLC record changes in Alma to the FTP server that is used for OCLC publishing and ultimately to OCLC for processing. The incremental schedule of the publishing job is determined by the scheduling option that you select in the OCLC publishing profile. This publishing mode is intended to be run on a regular basis.
      Publishing mode: Baseline Select this one-time-use option if you are an institution that is migrating from a different ILS where OCLC records have been maintained and exchanged with OCLC, and the goal is to continue the exchange of records with OCLC on the Alma system from where the other ILS left off (using the existing OCLC account that was used with the previous ILS).
      This option is intended for use – once – immediately after the database is migrated to Alma and before any OCLC records are changed in Alma. This option publishes the whole set of OCLC records (that is, all the records that are marked for publishing to OCLC as described in When Records are Exported) to an Alma publishing index (an internal manifestation of the set in Alma specific to Baseline publishing to OCLC), but does not create any files on the FTP server used for OCLC publishing. Once the publishing job completes, Alma automatically sets the Publishing mode in the OCLC publishing profile to Incremental for the ongoing incremental publishing updates with OCLC.
      The scheduling and running of the Baseline publishing job should be incorporated into the process immediately following the Alma cutover to production.
      Publishing mode: Full Alma publishes all the OCLC records (that is, all the records that are marked for publishing to OCLC as described in When Records are Exported) to the FTP server used for OCLC publishing. This option is intended for institutions that create a new OCLC account for processing records for the first time (such as libraries that did not work with OCLC publishing in their previous system before Alma) or for sites that did work with OCLC previously, but have decided to undertake a full reclamation project with OCLC in order to republish all records from Alma to OCLC, again. Once the publishing job completes, Alma automatically sets the Publishing mode in the OCLC publishing profile to Incremental for the ongoing incremental publishing updates with OCLC.
      Submission Format section:
      FTP configuration From the drop-down list, select the name of the S/FTP connection that you previously defined for use with OCLC. For detailed information on FTP requirements, see http://www.oclc.org/support/services...ration.en.html.
      Subdirectory Enter a subdirectory of the path specified when creating the S/FTP connection. For example, if you specified Alma in the Sub-directory field during S/FTP connection configuration and you enter OCLC in this field, the data is exported to the Alma/OCLC directory.
      Status Select Active.
      Scheduling From the drop-down list, select one of the scheduling options that are preconfigured by Ex Libris staff. If you select Not scheduled, the export job for this publishing profile will not run until you select a different scheduling option from the drop-down list for this profile
      OCLC retrieves the data from the FTP directory every night at about 2:00 AM (Eastern Standard Time). The publishing process should be scheduled so that it does not interfere with OCLC’s data collection process.
    3. Click Email Notifications to specify which users and email addresses will receive email notifications when the publishing job has completed.
      Email Notifications for Scheduled Jobs Page
    4. Select the users that you want to receive email notifications.
      1. Click Add User.
        Add User Dialog Box
      2. Click the browse icon in the User field to search for and select a user name.
      3. Select the Send on Success and/or Send on Error options to specify when the email notification is to be sent to the user.
      4. Click Add to include additional users, click Add and Close to add the user and also close the dialog box, or click Close to exit the dialog box.
    5. Select the email addresses that you want to receive email notifications.
      1. Click Add Email Address.
        Add Email Address Dialog Box
      2. In the Email address field, enter an email address.
      3. Select the Send on Success and/or Send on Error options to specify when the email notification will be sent to the email address.
      4. Click Add to include additional email addresses, click Add and Close to add the email address and also close the dialog box, or click Close to exit the dialog box.
      5. Click Done to return to the Profile Details tab.
    6. Click Save. The modified publishing profile appears activated on the Publishing Profiles page. Data that meets the defined criteria is exported to the specified FTP location when the profile is run.
      Running the OCLC publishing profiles (Publish bibliographic record (DataSync) to OCLC and Publish your Local Holdings Records (LHRs) to OCLC) may be done only once per day. If you attempt to run one of these profiles more than once a day, you will receive an error message.
      For information on monitoring a publishing export job, see Viewing Running Jobs.
      When publishing bibliographic records to OCLC, the maximum number of records per file that can be published is 90K. This complies with OCLC standards described in the OCLC documentation located at http://www.oclc.org/support/services/collection-manager/migration/dsc-migration.en.html. This same OCLC document also describes the FTP output file structure. If there are more than 200,000 records to be exported, multiple data files are created with up to 200,000 records in each file.

    Publishing Electronic Holdings to OCLC

    Synchronizing your libraries’ electronic holdings from Alma to WorldCat can be achieved using Alma’s publishing platform.
    Once you set up the publishing platform (according to the steps below), Alma will publish your electronic holdings to WorldCat on a scheduled basis resulting in synchronization of every change to your electronic holdings with WorldCat. A scheduled job for Publishing to OCLC - Holding Records is created.
    To publish electronic holdings to OCLC:
    1. Create the set of electronic holdings that you want to synchronize with WorldCat. See Adding Logical Sets for instructions.
    2. Create a general publishing profile. Refer to the procedure Publishing and Inventory Enrichment, and use the details provided in the following table to customize your profile configuration.
      Profile Details for OCLC Electronic Holdings
      Parameter Description
      Profile name Enter a name for the profile that distinguishes it from other profiles on the Publishing Profiles List page and identifies it for OCLC electronic holdings.
      Profile description Use the description to further identify the publishing profile for OCLC electronic holdings.
      Status Select Active.
      Scheduling Select the schedule that you prefer.
      Email Notifications Use this feature to send email notifications when the publishing job has completed.
      You can view the status/report of a completed job from the History tab on the Monitor Jobs page (Administration > Manage Jobs > Monitor Jobs).
      Content section
      Set name Click the search icon for this parameter to view the available sets for publishing and select the set that you created for electronic publishing in step 1.
      Publish on Select Bibliographic level.
      Output format Select MARC 21 Bibliographic.
      Publishing mode Select Full.
      Publishing Protocol section
      FTP, OAI, or Z39.50 Select the FTP check box.
      FTP configuration Select the FTP configuration that you created for OCLC (in Administration > General Configuration > Configuration Menu > External Systems section > S/FTP Definitions). Your FTP configuration should include the following configuration parameters:
      • FTP Server=ftp2.oclc.org
      • UserName=the one assigned to you by OCLC
      • Password=the one assigned to you by OCLC
      • Sub-directory=wckb/in/data
      Refer to for more information.
      Files Configuration section
      Physical format Select XML.
      Number of records in file Select One File. (All records published to OCLC should be in one file.)
      Use default file name Select No.
      File name Specify HOLDINGS_<registry_id>.xml-marc where <registry_id> is your WorldCat Registry ID (also known as your OCLC Institution ID) for your library. If you have questions regarding your WorldCat Registry ID, contact OCLC customer support (support@oclc.org).
      OCLC Electronic Publishing Profile - Profile Details
      Data Enrichment for OCLC Electronic Holdings
      Parameter Description
      Electronic Inventory Enrichment section
      Add Electronic Portfolio Information Select the check box for this parameter.
      Repeatable field 866
      Access URL subfield u
      Link Resolver Base URL Enter your link resolver base URL.
      Enter the base URL for the Primo service page redirect to the Alma Link Resolver using the following format and inserting your institution’s information where indicated:
      http://<primo server host:port>/openurl/<primo institution_code>/<primo view_code>?
      Collection Name subfield x
      Coverage Statement subfield a
      CZ Collection Identifier subfield t
      OCLC Electronic Publishing Profile - Data Enrichment
    3. Click Save.

    Transitioning to Alma Production from a Previous System that was used to Synchronize with OCLC WorldCat

    The purpose of this section is to provide instructions that will enable you to continue processing incremental changes to OCLC WorldCat (versus reloading your entire database) when you switch from a previous system to Alma production. To do this, you will need to:
    • Create the OCLC publishing profile using the one-time baseline option
    • Run the OCLC publishing profile while the one-time baseline option is set to create a starting point in your database from which Alma can continue with the incremental updates to OCLC.
      See the following procedure for instructions regarding how to configure the OCLC publishing profile using the one-time baseline option for establishing the starting point from which Alma can continue with your incremental updates to OCLC WorldCat.
      It is key that you run the special one-time-use publishing profile/job on your first day or very close to your first day in Alma production and before making changes to your cataloging records.
      Your bibliographic records with an OCLC-prefixed 035 field are automatically flagged during migration for bibliographic OCLC publishing. If your records need to be flagged differently:
    • Use Alma’s Repository Search to create a set that reflects your relevant OCLC records at that point in time.
    • Run the Synchronize Bib records with external catalog job with the Synchronize with External Catalog parameter in the TaskParameters: MmsTagSyncExternal section set to Publish bibliographic records or Publishing holdings only to mark/flag the set of records to be published to OCLC. This step may also be used to unmark a set of records to prevent them from being published.
      Synchronize with External Catalog Parameter
      See Running Manual Jobs on Defined Sets for more information.
      For marking individual records (versus a set of records), use the MD Editor and the Publish bib/Publish holdings only Tools options (Tools > Set Management Tags > Export to WorldCat). See Export to WorldCat in MD Editor – Tools Menu for more information.
    • Once your OCLC records have been flagged, use Alma’s Advanced Repository Search and Tag Sync External Catalog search parameter to verify the records that have been marked for OCLC processing.
      Tag Sync External Catalog Advanced Search Parameter
      Once you have addressed these workflow considerations, you are ready to configure your OCLC baseline publishing profile and run the publishing job using this profile.
    To configure and run the OCLC publishing profile for the transition to Alma production:
    1. Use the steps outlined in the procedure Publishing Print Holdings to OCLC to create your one-time-use OCLC publishing profile except use the Publishing Profile Details page settings described in the table below.
      Publishing Profile Details Page Parameters (for Transition Profile)
      Parameter Description
      Profile Details section:
      Profile name Modify the name to meet your requirements.
      Profile description Modify the description to further identify this profile.
      OCLC institution symbol Enter the institution/library code symbol previously agreed upon with OCLC (see step 1 in the configuration process outline above).
      Project ID Enter the synchronization project ID previously agreed upon with OCLC (see step 2 in the configuration process outline above).
      Publishing mode: Baseline Select this one-time-use option that is provided for institutions that are migrating from a different ILS where OCLC records have been maintained and exchanged with OCLC, and the goal is to continue the exchange of records with OCLC on the Alma system from where the other ILS left off (using the existing OCLC account that was used with the previous ILS).
      This option is intended for use – once – immediately after the database is migrated to Alma and before any OCLC records are changed in Alma. This option publishes the whole set of OCLC records to an Alma publishing index (an internal manifestation of the set in Alma specific to Baseline publishing to OCLC), but does not create any files on the FTP server used for OCLC publishing. Once the publishing job completes, Alma automatically sets the Publishing mode in the OCLC publishing profile to Incremental for the ongoing incremental publishing updates with OCLC.
      The scheduling and running of the Baseline publishing job should be incorporated into the process immediately following the Alma cutover to production.
      Submission Format section:
      FTP configuration From the drop-down list, select the name of the S/FTP connection that you have established/coordinated with OCLC. This is the FTP from which OCLC can retrieve records to be synchronized with the WorldCat records.
      Since the Baseline option that you select for Publishing mode does not create any files on the FTP server used for OCLC publishing and Alma automatically sets the Publishing mode in the OCLC publishing profile to Incremental after the Baseline publishing is completed, you can select the ongoing, incremental FTP configuration that you have established with OCLC.
      Subdirectory Enter a subdirectory of the path specified when creating the S/FTP connection. For example, if you specified Alma in the Sub-directory field during S/FTP connection configuration and you enter OCLC in this field, the data is exported to the Alma/OCLC directory.
      Status Select Active.
      Scheduling Select Not scheduled. You will manually initiate running this job.
      After you have completed your transition (Baseline) publishing job, you will need to change the scheduling option to your scheduling preference for ongoing, incremental publishing.
    2. After you have saved your profile settings, manually run the transition publishing job (Actions > Run) for Publish bibliographic record (DataSync) to OCLC or Publish your Local Holdings Records (LHRs) to OCLC (depending on which profile you chose to configure).
    3. Once your transition job has completed running, reconfigure the Scheduling parameter to set up your OCLC publishing profile for ongoing incremental publishing with OCLC WorldCat records.