Skip to end of banner
Go to start of banner

2022-06-13 - Data Migration Subgroup Agenda and Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Attendees

Darsi Rueda   


Meeting Link

Link to Recordings

Discussion items

TimeItemWhoNotes


Jiras


Theodor opened a few Jiras

https://issues.folio.org/browse/SUP-75 
https://issues.folio.org/browse/MODINVSTOR-921 Create API endpoint to get the current maximum assigned HRID



Optimistic locking issue with upsert50

https://issues.folio.org/browse/MODINVSTOR-910 Optimistic locking keeps upsert in the batch mod-inventory-storage api from working because you need to know the record version # and update it with same in order to be able to update it.  Otherwise the record is “locked” to you.  Data import app should still work.

Ian is using Data Import app to migrate a small library.

Load vendor files with Data Import app, even if doing under the hood with apis, use "Data Import app endpoint"

Brooks: Should be a way to bypass the version check for batch updates/batch loads
Tod: Discussion on what the solution should be needs to happen.  Bypassing optimistic locking is one.  Partial load and an error report is another (so all other records load except the ones with version conflicts)
Jeremy: If batch fails, we post each record on its own so we can see which one failed.
Tod: if the apis could do that, it would be nice
Brooks: in PO group presentation, they had provided a way to bypass optimistic locking, but then didn’t implement it. The “solution” of looking up version number and updating your incoming record to match it is not feasible for 10K+ records

Tod: Would some small number of people be willing to write up the operational problem, and the obstacles we’re running into.
Ingolf: Is this a pain point that TC should review?
Tod: yes, but that’s more long-term.  Needs escalation now and a short-term solution

Jeffrey: Does the same as Jeremy, trying to post each record in a failed batch/doing the checks.  Does some of each depending on process.
Dale: Every institution creating their own workaround is waste of resources, solution should be in the apis.

Brooks: the apis seem to have been overlooked when considering optimistic locking. Works for Data Import because if a record hits the problem, code pulls it again, does its update, and reposts.

Tod: We don’t need to provide a solution, we need to say we have an operational problem. Is a problem for anyone migrating. Batch updates (dump, update externally, reload).


Orders migration10

Advice about amount of resources to allocate for loading orders, number of pods?  We only have one mod-orders/mod-orders-storage composite-orders.  Jeff gets ~400-500/hour.  Stanford getting 120/hour.

Question about finance data/budgets.  Working from spreadsheet to form json. For budgets, required field allocated is supposed to be used when posting the real budget allocation? Or need to use finance transaction endpoint when allocating budgets (Erin’s advice?). Duke allocates the $$ after the budget is created (a secondary step), with a financial transaction. Jeff sets allocation to 0 when creating the budgets. Julie then allocates money to them. Maybe ask on Acquisitions SIG channel #folio-acquisitions-sig





Action items

  •  
  • No labels