2018-06-11 - Data Migration Subgroup Agenda and Notes

• Volunteer for note taking. Ingolf volunteered.

MM Sig needs more contextual information to interpret legacy data elements

Notes:

Christie added new tabs for GAPS Instance/Holdings/Items to Inventory Spreadsheet . Added UChicago requirements. Cornell will add gaps. Others should also add their gaps. Christie has questions, how some of the data elements are being used at other institutions. Same gaps might show up in different columns at other institutions, while different gaps might show up in the same column. New Target Date for the Inventory Spreadsheet: July 2nd. Sharon and Charlotte will schedule a meeting prior to that date.

GAPS-Tabs should also be added to the other spreadsheets (Users, Loans, Requests). Deadlines for the other spreadsheets will be discussed on the (e-mail) list.

 Review action items in Action Items for Development

; only those related to the Data Migration Subgroup (SYSOPS-004 and SYSOPS-005).

Notes

Harry created UXPROD-Epics for some of the action items or linked them to existing Epics. He needs more specifications for those items for which he didn't create / add Epics.

SYSOPS-001 might have already been solved.

SYSOPS-002: LS-Tools. It might be solved with the help of another open source project, an ETL tool. Harry discussed with Chrstopher Spalding. Harry needs more specification about LS-Tools. Sharon will get in touch with the Cornell team who created LS Tools.

SYSOPS-003 : Harry quotes this as an example for a good specification. There is a link to a presentation. Cate created UXPROD-849 and there is already a discussion on the ticket. So, information goes back and forth from the SIG, other experts and the POs.

SYSOPS-004 : Cate created a ticket which should now be reviewed by the group.

SYSOPS-005 : Data model revisions / gap analysis. Some of this has just been addressed by Christie. We (the group) need to take this to the conveners of the other groups, as applicable. The the POs of the other SIGs can work on this after discussion in the other SIGs.

SYSOPS-006: UUIDs. There is an Epic for this, UXPROD-884. Harry says, the UUIDs really need to be there, it's a powerful thing to have, for example when one ties to external systems. Human readable identifiers can be added as additional identifiers. UUIDs will be displayed at first but will be replaced or supplemented by HR identifiers where needed. HR identifiers are needed as an alternative identification system. We should specify which HR identifiers we need, e.g. barcode in inventory record. Acquisition-, PO-IDs could have that need, too. HR identifiers will be added only where needed. Tod says, it comes out of the Discuss Thread where we need the HR identifiers. The main cases have been identified there. Not every record or object needs an HR identifier. Loan-IDs don't need to be HR.

SIG or Subgroup should examine, wheter SYSOPS-006 can be merged with SYSOPS-005, both subsumed as "Data model revisions".