[opal_migration_leads] Clarification about Alma's OCLC publishing profiles

[Matt Polcyn]

Good morning everyone –

Just to follow up yesterday’s OhioLINK Project Meeting wherein Ex Libris talked about the OCLC holdings publishing process wherein Alma sets your holdings in OCLC, rather than you setting your holdings in OCLC via Connexion or Record Manager ….

OPAL libraries should not to move forward with setting up the Alma Publishing Profile that makes this all work.  You should also refrain from running the baseline process described in the meeting; this process should only be done just before beginning setting holdings in Alma, rather than in OCLC directly.

As you’re contemplating the potential for this workflow, please keep in mind that there are a number of steps involved in this process, including establishing a Data Sync process with OCLC.  That process takes several weeks.  Because of this and potential for complicating existing OCLC holdings processes, e.g., existing Data Sync processes used by OPAL libraries, we’ll need time to sort out the implications and to establish best practices for those.

Over the coming months after go-live, we will be looking into this … and some of the other cataloging workflows that Alma supports.

If you have any questions or concerns, as always, please let us know.

Thanks!!

Matt


[A picture containing text, gauge, clipart  Description automatically generated]
Matt Polcyn
Director, Technology Services | OhioNet
570 Polaris Parkway, Suite 275 | Westerville, Ohio 43082
p: (614) 484-1061 | https://www.ohionet.org<https://www.ohionet.org/>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opal-libraries.org/pipermail/opal_migration_leads/attachments/20250502/f78addf0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3473 bytes
Desc: image001.png
URL: <http://lists.opal-libraries.org/pipermail/opal_migration_leads/attachments/20250502/f78addf0/attachment.png>