Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties
Document status

Status
titleDRAFT

Area coveredCataloging, 3rd Party Integrations
Lead Author
Co-authors

Lauren Magnuson (Unlicensed), Micah Jeffries, Marcus Jun, Moon Kim, Elizabeth Rallos, Jeremy Hobbs

Background

In order for records to be exported from Connexion into the Network Zone (NZ), there must be an Integration Profile set up in the Network Zone instance.  Each institution then must add a Gateway Export in Connexion using the NZ credentials to enable export and overlay of records in the Network Zone.  

...

Optionally, an institution may choose to configure an OCLC Connexion Integration Profile in Alma that will enable the export of records from Connexion to their Institution Zone (IZ).

Policy Statement

This policy applies to the setup required for importing records into the Network Zone via Connexion.  This policy also outlines the system-wide settings for match, merge, normalization, and management tag settings used when importing and overlaying records from Connexion into the Alma Network Zone.

Best practice recommendations

Best practices for match, merge, normalization, and management tags forthcoming.

Procedures

See also: Ex Libris Documentation (general instructions, does not include required Network Zone configuration)

Permissions Needed:  

  • For Alma initial configuration, General Systems Administrator

  • To overlay NZ records from Connexion, operators must have the Cataloger role

OCLC Connexion Configuration (action required by each Connexion user at each institution)

Create an OCLC Gateway Export in Connexion (Tools > Options > Export > Create … > OCLC Gateway Export)

...

  • Close Connexion and reopen

Alma Configuration:  Network Zone Instance (no action required by individual institutions)

Each institution does NOT need to configure an Alma Integration Profile for Connexion in order to use Connexion to export and overlay records into the Network Zone.  Each institution ONLY needs to set credentials in Connexion as explained above   For reference, we are documenting the settings currently used in the NZ instance below.

...

  • Synchronize with External Catalog: Publish Bibliographic Records


Optional Alma Configuration: Institution Zone Instances (to enable export from Connexion into your Institution Zone - action optional by each institution)


In Metadata Editor (Alma > Resource Management > Cataloging > Open Metadata Editor)

...

  • Create password (whatever you want)

  • Click Save

Optional Connexion Configuration for Exporting to the Institution Zone (action optional by each institution's Connexion user)

If you have set up Institution Zone export in Alma, you will need to create an additional Gateway Export for exporting to your institution zone with the password you have set in your IZ Connexion Integration Profile.

...

  • Close Connexion and reopen


Action log


SectionPoint Person

Expected Completion Date

Last action takenNext action required

Articulate the need for the policy (background)

 

9/29/2016 - Luiz, Lauren, and Marcus at Northridge discovered that OCLC Connexion Integration Profiles in the NZ and each CSU IZ needs to be identical, necessitating the need for CSU-wide policies on components of the Connexion Integration Profile (merge, match, normalization, and management tags). Emailed Import Profiles / Normalization Task Force with links from Luiz for Orbis' merge and NZ normalization policies.


Import Profiles / Normalization Task Force will develop policies for standardizing all components of the Connexion Integration Profile.


Create a Policy Statement for recommended NZ match method

 



Create a Policy Statement for recommended NZ merge method


 



Create a Policy Statement for recommended NZ normalization

 



Create a Policy Statement for recommended management tags (e.g., publish bibs to OCLC)

 



Where applicable, identify and write up procedures in Alma


 




Tasks to be completed

  •  Type your task here, using "@" to assign to a user and "//" to select a due date