Spike: Figure out relationship of Folijet batch loader and CoreTeam mod-data-loader

Get a better understanding of the upcoming Folijet batch loader work in the context of existing Core Team loader/import work

• A-M, Taras meet with Alfons Seelen (perhaps also Jakub) to discuss mod-data-loader
• Determine whether Folijet batch loader backend work will coordinate with or be different from mod-data-loader, to ensure that we avoid confusion or duplication of work
  Note: There is no existing ui for batch load/import, so any Folijet ui work will be new

Feedback from Jakub: As far as the architecture goes: the Core Team has built on batch import module called mod-data-loader [1]. Alfons Seelen is the current maintainer (I am CCing him and Julian) and just released a new version. I'd like to discuss what would be the aim for FOLIJET's modules and how would that impact mod-data-loader going forward, e.g we should try to coordinate the work to avoid potential duplication. E.g we have discussed with Alfons that mod-data-loader needs to be refactored to be production-ready (we discussed merging it with mod-inventory-storage OR extending the API bridge between the two), I could see a third option: FOLIJET's module supersede mod-data-loader.

[1] https://github.com/folio-org/mod-data-loader

Definition of done: Understand the current state and create a Confluence page with the information.