...
Attendees
Goals
- One thing that's on our minds at Chicago: the need to have loading APIs defined for all of the data we need to migrate far enough in advance for us to work our data conversion, test workflows, and give feedback on gaps.
We have a few that we can start working with, but we'll need time with all of them.
- define the types of data that needs to be migrated in order to work with the system (e.g. bibs, holdings, items, ... )
- acceptable load times
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Welcome and Introductions, call for Note taker | Chris Manly | |
| 10 min | Subgroup convener(s) | Will we rotate? Share duties? Do we have someone willing to take on the roll full time? | |
| 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. |