[UXPROD-3699] Records transmitted to FOLIO from GOBI should be seamlessly loaded Created: 02/Jun/22  Updated: 28/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD

Type: New Feature Priority: P3
Reporter: patty.wanninger Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-662 Automated FTP and Scheduling for batc... Draft
relates to UXPROD-185 Import Orders in MARC format Closed
Release: Not Scheduled
Development Team: Folijet
PO Rank: 0

 Description   

Currently, full MARC records provided by GOBI are sent to an FTP server, and the library must manually pick up the file and load it through a data import profile. The records should be sent directly to the Data Import API and run automatically.
In scope

Proposed solution/stories
Could be automated behind the scenes with a simple script as a sync service.



 Comments   
Comment by Khalilah Gambrell [ 09/Sep/22 ]

Hey Dennis Bridges , should this feature be assigned Tjet?

Comment by Dennis Bridges [ 09/Sep/22 ]

Khalilah Gambrell I think Ann-Marie Breaux may be able to clarify whether this has allredy been considered or not. If so, perhaps we would consider this a duplicate. If not we could assign it to Thunderjet and I will work on collecting some additional detail.

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

MARC records and the Order API don't mix. The MARC records that libraries are picking up from GOBI may be intended to:

  • Create MARC Bibs, Instances, Holdings, Items, Orders
  • Create MARC Bibs, Instances, Holdings only
  • Update MARC Bibs, Instances, Holdings, Items
  • Create MARC Bibs, Update Instances, Holdings, Items
  • Create MARC Bibs, Update Instances, Create Holdings, Items

It all depends on what stage of the order/purchase workflow the file is being generated, and what is or is not already in FOLIO. All of those above flows would require different Import job profiles. And currently the Order creation API is not set up to work with MARC Data, only XML data.

What would be helpful in the short term is being able to automate ftp pickup, assign a job profile, and run the import automatically. That cannot be done in FOLIO currently, though a library can use an external FTP scheduler to go check for new files and retrieve them on a regular basis. They could then script a process to upload that file and select a particular job profile. But those MARC files need to hit Data Import, not the Orders app.

We have a separate feature for automating/scheduling FTP, UXPROD-662 Draft , but so far it has not yet been ranked highly. I'll link it to this Jira. My inclination is to close this one as a duplicate to it.

Comment by Dennis Bridges [ 12/Sep/22 ]

Thanks Ann-Marie Breaux, I will defer to you on this one. Also, the scheduler seems like a logical alternative if this cannot be triggered by mod-gobi in something that might more closely resemble "Real-time". 

Comment by Lisa Sjögren [ 06/Oct/22 ]

What would be helpful in the short term is being able to automate ftp pickup, assign a job profile, and run the import automatically. That cannot be done in FOLIO currently, though a library can use an external FTP scheduler to go check for new files and retrieve them on a regular basis. They could then script a process to upload that file and select a particular job profile. But those MARC files need to hit Data Import, not the Orders app.

Ann-Marie Breaux Yes! Being able to automate the ftp pickup and DI jobs would be a great improvement for libraries using the Gobi-FOLIO API in combination with the "shelf ready" service.

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