2018-04-16 - Data Migration Subgroup Notes

Is it done? Is it clear? Does it provide the information the User SIG and the developers need to complete their data model? The User spreadsheet is here.

Discussion about User, UserId:

• Bulk user import requires an external system ID as a match point. Needed for ongoing maintenance of a user, updates from a central system. The FOLIO UserId won't be imported from the legacy system.
• The UUID will be generated outside of FOLIO . The use of UUIDs was reinforced earlier on. Going away from it would be a disruptive change.
• We want to have a more human readable user ID. Charlotte will take that to the developers. One can have two IDs in parallel.
• UUIDs are not user friendly, we need to have user-friendly integer ids, which can be communicated by phone (it happens often).
• => we defer this discussion (using UUIDs) to the other groups.

We will send the Spreadsheet to the User Management SIG (Chris Manly will take the sheet to this SIG, he is the Convener). We have identified gaps. The sheet needs to have a column "Questions of the User Management SIG" added.

Last week, we looked at the Alpha and Beta data models and how well they represented Chicago's data elements. This we we will be able to add Chalmers, and HBZ's data elements to the discussion. The Inventory spreadsheet is here.

We did a gap analysis for inventory.

New fields needed by hbz: accession number, inventory number, date of inventarization. Also needed in Sweden. Accession number and inventory number might be the same - see Ingolf's posts in the SysOps slack channel (today).

...

Dale: add repeatability, data type (integer, char, array, ...), length to the tables.

All: Add further columns to the Inventory mapping table. For further library systems that need to be mapped. Or complete your list of fields for your library system.