[UXPROD-211] Single MARC Record Integration with OCLC Created: 19/Feb/18  Updated: 06/Dec/23  Resolved: 11/May/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021

Type: Epic Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Mike Gorrell
Resolution: Done Votes: 0
Labels: library_dependent, oclc, post-v1, round_iv, sysops_mgt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UXPROD-976 Import individual MARC record from OC... Closed
is defined by UXPROD-2804 Import individual MARC record from OC... Closed
is defined by UXPROD-2912 Refinements to OCLC (and other target... Draft
Relates
relates to UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
Epic Name: Single MARC Record Integration with OCLC
Development Team: Thor
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: U of AL (MVP Oct 2020): R1
Score: 37.75
Start date (migrated):
End date:
Epic Color: ghx-label-9

 Description   

Import individual MARC record from external source (e.g. OCLC, LC, other bibliographic databases) to SRS, which will then serve as the basis for quickMARC, or order. Current plan is integrating with (only) Connexion, triggering import from Inventory, and populating the MARC record into SRS. This may not fit with Batch Importer, but it doesn't have any other home Epic for now.

Index Data working on a solution; work will likely be done in summer 2020



 Comments   
Comment by Cate Boerema (Inactive) [ 03/Mar/18 ]

Per Hkaplanian, as we integrate external services, we will add these, as we have already done for the EBSCO KB API. So nothing specific remaining for v1.

Actual integration with external services is covered in other feature/epics.

Comment by Cate Boerema (Inactive) [ 04/Jun/18 ]

VBar, is there overlap between this and edge apis? The thought here was that a PO and dev team would be assigned to this and would work with the SMEs to determine the top priority integrations and then make sure that we have the APIs needed to integrate. My understanding is that we should be able to leverage the apis used by the folio UI for external integrations, but I am sure there will be tuning needed and, in some cases, we'll need something purpose-made.

Comment by VBar [ 04/Jun/18 ]

Yes there are essentially all edge APIs. These would also include integrations that have not yet been identified. It is my strong recommendation that external systems do not integrate directly to Folio internal APIs (i.e. directly to Okapi) instead they should integrate to edge APIs.

Comment by Cate Boerema (Inactive) [ 09/Jul/18 ]

Marking this as a duplicate as each of the features it contained have now been given their own epics. They are all labeled with the external_sys_int label. See the full list here: : https://folio-org.atlassian.net/issues/?filter=10777

Comment by Ann-Marie Breaux (Inactive) [ 06/Apr/20 ]

Cate Boerema VBar Mike Gorrell Hkaplanian Since the only features and stories related to this Epic are OCLC-related, I'm going to rename it to Single record integration with OCLC.

Then if there's other integrations, we can figure out if they should be added as features under other existing Epics, or as new Epics.

Removed from the description field of this Epic: External system integrations (e.g. OPAC, ILL, Self Check). Each integration will likely need to be tackled individually. Each integration should be a feature within this epic. We will have the features prioritized and work through them according to priority.

Comment by Mike Gorrell [ 14/Jul/20 ]

Index Data (Thor) is planning to start this work in August and hope to have it completed in October of 2020.

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