...
Attendees
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Role Call | Noah |
| |
10min | Discuss responsibility of migration sub-team for AT/Archon migration tools
| All From Brad: In |
i. Brad had placed statement "In 2015/16, the migration sub-team will also become responsible for supporting migration of Archon and Archivists' Toolkit data into ArchivesSpace. This work will involve assisting organizations that are migrating their AT or Archon data and indicating to ArchivesSpace developers how migration scripts might need to be revised. " in our charge. ii. Chris Fitzpatrick had also stated on the listserv that the maintenance of the tools was now being passed to the community. This had also been stated at the Hack-a-Thon recently. Noah stated that he believed this to be the case. iii. For this group, this might mean:1. Respond to people on the user list when questions arise about the migration tools. Phil and Terry have already done a great deal about this with individuals, doing test migrations for other repositories, etc. Need to be clear with people that this is volunteer service, that sub-team members are not employees of the project and are just helping out. If there are actual bugs in the scripts themselves, members of team could submit pull requests for fixes. Brian reported that no one but Nathan had worked on those reports. Terry Reese had reported that he had been working on tweaking the migration tool, but this is still a work in progress and not published. Meant to clean up the text at the end of the biographical/historical note. Looking at the AT Migration tool, there are currently 0 contributors. This version was uploaded a month ago and is made for 1.4. The new migration path for institutions that have not migrated yet is to make the migration into 1.4.2 and then update from there. If this is the new migration path, it was suggested that this should be noted in the documentation--Noah will look into this and update as needed. iv. Most listserv traffic has been about the Archon migration tool, Noah suggested that reports of this type be pushed to Chris Prom and Mike Gorzalski. Suggested that most of the problems in this regard is not caused by the tool itself, but by modeling differences between AT and Archon--may not require bug fixing as much as massaging/reinterpreting data. Matt suggested that some work could still be done to improve migration process (e.g., fields added by the tool that weren't in the original data), though. It may be that this group could be used to mediate feature requests, which could then be passed along to Terry for bug fixes.
|
10min | Discuss creating FAQ for AT/Archon Migration Tools | All | How would this differ from "official" migration guidelines at: http://www.archivesspace.org/migrations a. Need to review documentation for users on preparing data for migration, migration process, correcting errors found in process |
10min | Updates on progress with work plan items | All |
|
10min | Update on container management testing (pending any updates from Features Prioritization sub-team meeting) | Noah | Draft of migration / data cleanup guidelines for container management (Maureen and Patrick G.): https://docs.google.com/document/d/1aIKCpExEaIvc_miEX8Eick1Ix2dsS9ayDQz9YLsSnoI/edit?usp=sharing
Work on the container management plugin continues, but Maureen and Patrick G. have been working on documentation for cleanup needed for implementation. They are hoping to have a new draft ready for next week. This document will be very useful for planning for migration, but no one on the call had implemented yet and had experience with cleanup. It was asked if there was documentation available for how data is moved within the database during the migration process, but Brian stated that he was not aware of anything in Github. Noah was interrupted by a fire drill at 11:48 AM MST, which brought the call to a premature end. |