[UXPROD-2402] API real time synchronization of FOLIO holdings to OCLC Created: 24/Apr/20  Updated: 10/May/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to REP-252 OCLC Holdings Synchronization Draft
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 18
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

API real-time synchronization of OCLC holdings from FOLIO to OCLC - an automaic process that bypasses query and export

Purpose:
Review if the existing solution build by University of Chicago (UC) working in OLE can be transformed and implemented as a FOLIO solution.
In the short term, UC would like to see a service that automatically sets holdings in OCLC when the criteria for a fully cataloged record is met and an OCLC number is present, e.g. when Instance status = Cataloging Complete or equivalent.

University of Chicago (UC) has a few workflows for setting holdings. The bulk of (UC) holdings are set automatically via the OCLC Metadata API:
https://www.oclc.org/developer/develop/web-services/worldcat-metadata-api/holdings-resource.en.html

This service runs in the background. This, however, is only currently designed for setting holdings where an OCLC number is already known.
For records that do not have an OCLC number, we have a workflow that identifies and exports fully cataloged records that have no OCLC number.

A different process for deleting holdings in OCLC is running too.

Documentation on current workflows: https://folio-org.atlassian.net/wiki/display/MM/Updating+%28Title-level%29+Holdings+in+OCLC



 Comments   
Comment by Cate Boerema (Inactive) [ 27/Jul/20 ]

Charlotte Whitt is there an epic this can be assigned to?

Comment by Charlotte Whitt [ 27/Jul/20 ]

Cate Boerema, yes: UXPROD-868 In Progress Bulk Edit

Comment by Ann-Marie Breaux (Inactive) [ 22/Sep/20 ]

renamed and added info to the top of the description based on a convo at today's OCLC single record import mtg

Comment by Lloyd Chittenden [ 16/Jun/21 ]

This has issues for a multi-tenant consortium.  We have many members each with their own OCLC holdings to maintain.  We also have members who are not in OCLC at all.  We would want the ability to limit this sync to records from a particular tenant on the server.

Comment by Jenn Colt [ 07/Oct/21 ]

cc Ann-Marie Breaux Khalilah Gambrell

Comment by Magda Zacharska [ 08/May/23 ]

Moving LC1 label from epic to defining features with Caitlin Stewart permission.

Comment by Khalilah Gambrell [ 09/May/23 ]

Hey Magda Zacharska. How does this feature tie into bulk-edit?

Comment by Magda Zacharska [ 10/May/23 ]

Khalilah Gambrell - I don't think it does. I'm removing it from the bulk edit epic.

Generated at Fri Feb 09 00:23:39 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.