One small word of caution – for us non-developers, it’s super-important that to be really clear with all of these various loaders:

What type of file (what format of data)
Loading into which app
To create/update what type of record

There has already been some confusion about loading MARC Bibs into Inventory, when what should be loaded into Inventory would be Instance/Holdings/Item JSON. MARC Bibs will load into Source Record Storage and (shortly) surface as Instances in Inventory. That Instance will first be based on the old MARC-Instance mapping, but will soon be updated to a newer, more robust default mapping.

Thanks,
A-M

Ann-Marie Breaux

Vice President, Workflow Management Services

EBSCO Information Services

10 Estes Street

Ipswich, MA 01938

abreaux@ebsco.com

Mobile: +1-678-427-4875

From: data-migration@ole-lists.openlibraryfoundation.org <data-migration@ole-lists.openlibraryfoundation.org> On Behalf Of Dale Arntson
Sent: Monday, April 15, 2019 4:15 PM
To: data-migration@ole-lists.openlibraryfoundation.org
Subject: Re: FOLIO Data Migration Implementing Bulk-Download, Streaming and Bulk-Upload

CAUTION: External E-mail

Thanks for the links, Ingolf. The RAML is quite clear. I'll be reviewing it this week to see if it covers everything we need.

-dale

On 4/15/2019 11:32 AM, Ingolf Kuss wrote:

Dear Patty, dear group:

I want to bring this to your attention:

Julian Ladisch, a core team developer, followed the discussion of the data migration subgroup on March 25 and this is want he wants to make the group aware of:

The functionalities which have been described by Wayne on March 25, 2019 (in the DM meeting) (Bulk-Download, Streaming, Bulk-Upload) have all been implemented in the Raml-Module-Builder (RMB) :

https://github.com/folio-org/raml-module-builder/blame/v23.11.1/domain-models-runtime/src/main/java/org/folio/rest/persist/PostgresClient.java#L877-L984 ,

https://github.com/folio-org/raml-module-builder/blame/v23.11.1/domain-models-runtime/src/main/java/org/folio/rest/persist/PostgresClient.java#L1442-L1550

These can be made use of with very little effort (Streaming, Bulk Download) and little effort (Bulk Upload), respectively, in the respective modules. To accomplish this, it only needs adequate Tickets for specific (!) APIs. These Tickets can be implemented promptly upon adequate priorisation by the PO. (E.g., https://issues.folio.org/browse/MODUSERS-3 has not been prioritized highly since two years ago).

Julian also makes the remark, that using Jon's loader in SQL mode bypasses using the microservice APIs, which he considers "forbidden" in a multi-tenant environment for security reasons.

Best,

Ingolf

To unsubscribe from this list please go to http://archives.simplelists.com

To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=9w1trkFTrGuhr2ADjEVGxjLfyncmUAsy