...
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Welcome and Introductions, call for Note taker | Chris Manly | Wayne Schneider will take notes |
| 10 min | Subgroup convener(s) | Will we rotate? Share duties? Do we have someone willing to take on the roll full time? Dale Arntson will convene the next meeting, Ingolf Kuss will volunteer to be part of the rotation. | |
| 45 min | Defining the scope of our work | Chris Manly | This falls into two categories: The types of requirements that we need to define (things like time lines, performance characteristics, API quality, etc.) and subject areas for the data we need to migrate (things like "vendors", "MARC records" and so on). The things in the first category would apply to each of the things in the second category, but the specifics might vary. Let's see if we can rough out a draft definition for both of these categories. Charter: https://folio-org.atlassian.net/wiki/display/SYSOPS/Data+Migration+Subgroup Question (Dale Arntson): Is this group focused on practical needs of immediate migration, or high-level discussion of requirements? Piles of data:
Open system architecture question: what is the distinction between bibliographic metadata loading and inventory loading? Mechanisms for linking interdependent data (purchase order line items with instances, for example) as different parts of the system come online need to be defined. Libraries should be talking to their internal implementation groups to validate data migration requirements, we should also be going to SIGs to validate assumptions. Talk to system experts about data extraction – what data is hard to extract, what kinds of transformations are likely to be necessary. For reference to existing data formats, the API documentation is very valuable: http://dev.folio.org/doc/api/ |