[UXPROD-850] Migration Tools Created: 07/Jun/18 Updated: 20/Jan/21 |
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q1 2019 |
| Type: | Epic | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Ian Walls |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | library_dependent, migration-load, sysops_mgt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Name: | Migration Tools from Legacy ILS | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Score: | 44.13 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Start date (migrated): | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| End date: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Color: | ghx-label-1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Ability to migrate data. Will lean on import tools being built for other purposes when possible (e.g. batch bib/acq import) but will likely need special tools for importing things like circulation data. This implies tools created per supported legacy ILS system that may need to be created that export in a standard format that a high speed loader can easily process and load into FOLIO. User loading may be the exception except when needing to transfer user stats in some systems. Here is a link to the SysOps feature writeups: https://docs.google.com/spreadsheets/d/1Y52ltM_nVZsMM9dEVCkHAWuRZXjOykZfvoF-zLQ-YBg/edit#gid=0 See SYSOPS-004 for specifics on this item including some thoughts on how we should approach this feature (to be futher fleshed out by PO at a later date). |
| Comments |
| Comment by Anne L. Highsmith [ 11/Jun/18 ] |
|
I heard Harry comment on this ticket at the Data Migration subgroup meeting this morning, saying that he had omitted some of the detail from SYSOPS-004 on the SysOps and Data Migration spreadsheet because he wanted to focus more on the what rather than the how of the migration process, since the how needed to be worked out between SIG and developers. I’m wondering if that omission is really necessary. The “what” contained in SYSOPS-004 was worked out among a large group of librarians and system administrators, many of them members of SysOps SIG and the Data Migration Subgroup, in a meeting that was led by Wayne Schneider, a developer. Given that it seems to me that all of the relevant groups were represented when that detail was worked out. |
| Comment by Cate Boerema (Inactive) [ 12/Jun/18 ] |
|
Thanks for your comment, Anne L. Highsmith. Tagging Hkaplanian and Wayne Schneider for their thoughts. For reference, here is a link to the SysOps feature writeups: https://docs.google.com/spreadsheets/d/1Y52ltM_nVZsMM9dEVCkHAWuRZXjOykZfvoF-zLQ-YBg/edit#gid=0 See SYSOPS-004 for specifics on this item. |
| Comment by Hkaplanian [ 12/Jun/18 ] |
|
Thanks everyone. When EPICs are created in JIRA, the implementation details are typically defined by the developers at a lower level such as the feature or story. If Wayne is working on this, he will document that information while providing a level of detail that's ideal for the software developers working on those features. |
| Comment by Wayne Schneider [ 12/Jun/18 ] |
|
Thanks for the clarification, Harry. I was unfortunately not in the meeting yesterday, so didn't have the full context. It is true that we had a productive meeting at WOLFcon where we agreed on some broad principles of both the "what" and the "how." I'm am not sure whose role it is to turn that discussion into user stories that fit under this epic. |
| Comment by Cate Boerema (Inactive) [ 13/Jun/18 ] |
|
I think we probably need a (technical) PO for this project to write up the user stories and link them here. I am guessing Wayne has enough other things on his plate to take that on right now A big part of the justification for simplifying and prioritizing our epic list is to highlight that many important epics/projects are still lacking the staffing they need to move forward (both PO and development). In about a week we will have the results of this prioritization and can begin having conversations about where the resources will come from and be assigned. In the meantime, I added a link to the epic here to your document with further details on the How which will be reviewed and incorporated into designs and stories when we get a PO assigned. Thanks! |