2019-01-28 - Data Migration Subgroup Agenda and Notes
- Dale Arntson
Date
Attendees
- Dale Arntson
- Ingolf Kuss
- patty.wanninger
- Sharon Markus
- Ann-Marie Breaux (Deactivated)
- Uschi Klute
- Anne L. Highsmith
- Christopher Creswell
- Tod Olson
- Steve Bischof
- Alexander Krug
- Matthew Harrington
- Jon Miller
- Wayne Schneider
Meeting link
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 | Welcome and update | Dale | Notetaker: Jon Miller |
| 5 | PC | Dale | We presented our data loader document to the Product Council on January 10. Dale will report briefly on how it was received. |
| 30 | Data loader user stories | Patty W. | Patty has been working on some user stories for the data loader, and will talk about these at the meeting. Discussion to follow. |
| 15 | External ERMs | various | In SysOps last week, we discussed the need to integrate various external ERMs with Folio. It was also mentioned that some institutions may wish to migrate their external ERM data to Folio's ERM. In particular, the Coral ERM was mentioned as a system whose data some institutions may wish to migrate. Dale said that he would bring this issue up as a topic for our next meeting. |
1/28/2019 Data Migration Meeting Notes Patty Wanninger talked about needing “epic” for JIRA issues There is a JIRA Data Migrations page with related JIRAs collected/linked together UXPROD-850 is the epic for Migration Tools Patty added links to JIRAs in other projects to the epic Dale mentioned that we need to create “user stories” Patty said that developers use the stories Dale asked whether it’s up to the developers to determine which project a feature would fall under Ingolf Kuss asked if the issues are marked as Data Migration Patty said they are tagged with migration-load Patty said there is a Getting Started for Product Owner wiki that has documentation that explains how to enter issues Dale said that he didn’t think that JIRAs from other projects should be “shoe horned” in I think he was saying that we should create our own issues rather than linking to ones in other projects? Dale said that he thought that we should create “features” for each of the bullet points in the DataLoaderRequirements document Patty said that the bullet points would be features of the epic, not user stories yet Ingolf Kuss said user stories are written in collaboration with the developers Ann-Marie Breaux said that priorities are set at the feature level Ann-Marie said that no work happens until you create user stories, if you just have an epic and features it doesn’t There was a question about how to set priorities for the items and getting them queued up for developers to work on them Ann-Marie said that the dev teams are already designated for Q1 Patty asked a question about gaps in data mapping and showed a Draft Crosswalk document and mentioned that a staff-only flag was missing Dale said that the purpose of the data loader was to load the data from JSON files Dale said that the place to look for whether elements are missing is in the RAML/JSON schema files Ann-Marie said that the first step is to have a place to “park” the data Patty said that in the future the data may or may not be “surfaced” in the UI Patty said that she would write up the features Ann-Marie mentioned a queue and unranked features Dale mentioned that the data loader was taken to the PC and that they were amenable to it Dale said Sysops from two weeks ago discussed migrating ERM data which hadn’t been brought up in the data migration group previously, so, he wanted to bring it up Dale mentioned that he heard that TAMU was considering migrating to FOLIO ERM Ann Highsmith said that she would look into it, but, hadn’t heard about it Ingolf and Theodor said they are on the ERM group Ingolf said we need to determine what needs to be migrated Ingolf said that he would ask Martina about getting an overview of ERM Patty said that she would show us the user stories and documentation she is working on next week
|
Link to Acquisitions Interface Fields
Link to FOLIO Record Data Elements
Action Items
- Tod Olson Pull list of data elements and descriptions from JSON schema, focus on
purchase-orderandpo_lineschemas, send to Beltaine. - Tod Olson Contact User Management SIG (Maura Byrne) to find out more about Affiliation data upload plans
- Dale Arnston will contact Khalilah and Ann-Marie attend an upcoming Data Migration subgroup meeting to discuss questions about the User-Import Endpoint tool and the Data Import tool
- Tod Olson and Patty Wanninger to draft a Data Loaders Requirements document to for Data Migration group to discuss in 2 weeks (Dec 10)
Patty creates a Slack channel for Voyager resource access. She creates #migration-voyager, #migration-aleph, ... Slack channels.
Dale Arnston will talk with Patty about plans for discussing Data Loader user stories in a future meeting
Dale Arnston will follow up with Paula Sullenger and Jesse Koenneke to determine when the Data Loader Proposal can be presented to Product Council