FOLIO will have a bulk user import feature to support the migration from existing ILS systems, as well as to provide some mechanism to automatically import data from external systems like a Student Information System.
We have created a draft document to describe the workflow of an import and the contents of the user import file format. This document can be found here: https://docs.google.com/document/d/14S4YfB7g6L5lrdnebFJU1ioNqaRdcSTZZLUMrJlbpQY/edit?usp=sharing
On Slack I’ve recently asked some question regarding the automated import. I’m moving these questions here for discussion:
I’ve had some thinking about the configuration file we’ve discussed, which will configure how FOLIO behaves with the automated import. I don’t know what will be the distribution and installation method of FOLIO when actually released, but with the current Vagrant VM images it seems difficult to me to edit configuration files. I think it would be still a better way to create a configuration page for the user import in the Settings app, and you can setup the import there. What do you think?
I was also thinking about importing through an API call you’ve mentioned in the end. My proposed method works by polling the file system, so it’s basically a pull method. But actually an API based push import is not a bad idea either. From my past experience push can be more real-time and can avoid the creation of temporary files. Also with a good API design the caller can be notified instantly about issues. It’s also easier to support some kind of client application controlled transaction. However the SIS conversion script/tool have to be a little bit more complex and handle some of the additional tasks of the API calling. Which of the two import methods would support your needs better?