Time/Place
Time: 9am - 3pm Central Daylight Time US (UTC-5)
Place:
Washington Boulevard Executive Center
4818 Washington Boulevard
St. Louis, MO 63108
Audio Conference:
Join Zoom Meeting
https://duraspace.zoom.us/j/5769796461
One tap mobile
+16699006833,,5769796461# US (San Jose)
+16468769923,,5769796461# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 876 9923 US (New York)
Meeting ID: 576 979 6461
Find your local number: https://zoom.us/u/afJIZ8XWA
Directions
TBD
Attendees
Absent
- Michael J. Giarlo (calling in)
- Mark Jordan (calling in)
Agenda/ Notes
Designing a Migration Path - collection of project resources Discussion. 'Ah Ha!' moments after reading. Any surprises? Survey distribution timeline (one month behind sched) and strategy Idea to deliver a webinar as project update and to kick off survey distribution. Draft survey preamble: https://docs.google.com/document/d/1vsg4NGJ5aDfwQfp63JG4jCgXtyAb37xnfq6K4_BUs5k/edit Distribution to lists: Samvera-Tech, Samvera-Community, Digital-Curation, Code4Lib, DLF, PASIG, Fedora-Community, Islandora-Community, Islandora-Dev. Personal solicitations for survey from advisory group members? Volunteers? Timeline for keeping survey open: Two weeks? With reminders during period. Schedule and draft text and assignments. Planning next steps: Secondary consultation with Samvera, Islandora and Fedora Communities after survey results come back. Advisory board members will receive a summary of anonymized survey results. We will speak to each advisory board member if there are gaps in the data set (e.g. things we thought we would see that we didn't) and surprises in the data set. Feedback will be documented and included in the final report. Action- provide timeline for setting up individual meetings with Advisory Board members Action - Determine timeline for next series of virtual meetings in May/June. Get it on our calendars. Final Report / Report out at OR in June 2019 Discussion:Time Topic Lead 9:00-9:15 Welcome, agenda review 9:15-10:15 David 10:15-10:30 Break 10:30 - 11:45 Erin 11:45 - 1:00 Lunch 1:00 - 2:30 Erin 2:30 - 3:00 David
Notes
Agenda review
Erin shared that a practicum student is starting on Monday and will be helping with the grant. Erin will send out a message introducing her.
Overview of documents
Broad overview of documents, AHA moments
David - Reached out to a number of institutions and did a brief survey of front-end data model perspective. What is the same, what is different, how difficult to do a migration based on the front-end framework. Islandora is probably the easiest - homogenous, core structure with solution packs, Islandora already has a migration framework. Some issues, some things to be rewritten, but Islandora will likely have the least trouble. Content will be okay, but custom front end will need to be required. Florida State University, National Library of Medicine, University of Wisconsin-Madison, UNC Chapel Hill, Michigan State University, Stanford University, Williams College, Amherst College
Este - UX/custom front ends are not necessarily critical to migration, but could be major areas of need for many institutions because that is what users and non-tech staff think of as the library interface.
Erin - is this something we need to call out as a priority for migration?
Scott - ORM - object relational mapping may be an important component to consider to allow for more easily developing an interface for the underlying repositories. Could be challenging to build out UI template because of so many data models. But an ORM could be a middle layer to help with editing.
Erin - brainstorm what the next steps are an include this issue of UX layer in the planning.
Tim - the barriers are not all technology barriers. Can be custom metadata, data models. We should at least write down the barriers. Could be to tell some folks that they are a DSpace shop, maybe best to move off of Fedora.
Erin - need to acknowledge these barriers exist to help with thinking about what happens in next phases of migration work.
Scott - what about service providers who could implement Fedora? Similar to DSpace?
Erin - There are about 25 service providers for DSpace. It is expensive, though, and there are a limit to people who are able to code Fedora. Sharing information with service providers would be valuable to let them know where things are heading with Fedora.
Scott - also work with Lyrasis, consider possibilities, formal encouragement to develop service provider relationships.
David - good to connect with list of schools that need migrations and the service providers in some capacity. Samvera sites still running three all very similar to custom implementations. Migration will involve a lot of custom work. Question - to what degree can we build on and create tools that will help with custom shops. OCFL/6 will be path with custom stuff as it will be easier than getting to 4 or 5.
Erin - need to be deliberate about where we focus our efforts - some institutions will still need to manage their own migrations.
DAvid - front end - Islandora is uniform. custom shops - so many variations can't really make a tool.
Andrew - slides on migrating 3-4 and there are different categories they present in Fedora trainings (see sample slides): content migration, front-end migration, functionality migration (authorization controls, disseminators).
Este - we are planning to migration content and then look at user interface migration second. Like the categories for migration.
Scott - Tools to help with the migration in terms of how to plan for front end, such as how to map Solr from 3-4
David - initial migration, get content over - fairly low barrier, and not that bad in terms of moving to a new version of Fedora. Maybe create a Fedora migration guide?
Erin - great idea. Bridge to Hyku just put out their recommendations. Metadata clean up could wait?
Scott - take data model now and same bitstreams and put in Fedora 6. Maybe later tear things up and expose more linked data but not yet. This isn't that difficult.
David - don't have to convert all XML to RDF. It is not a requirement.
Migration tools
David - there are three that exist - migration-utils, FedoraMigrate, Migrate_7x_claw (based on The Drupal Migrate framework). Can we leverage what is there/update?
Erin - how heavy a lift to make migration-utils compatible for 5.0. A good starting point for the basic content migration. Would need some updating in terms of documentation.
Scott - documentation is a core are for our future development. Google doing 'summer of documentation' "Google Season of Docs" - offering stipends of up to $6,000 for a 3 month documentation writer for technical documentation writers. Could be interesting for Fedora and Duraspace.
Erin - any feedback about the existing documentation about what should be addressed?
Scott - having documentation, and having it up to date. Having a good level of documentation is very helpful, it shows and makes it easy to develop and doing thing
Erin - helps to level the playing field.
Scott - writing good documentation is hard/a skill.
Erin - IMLS is focused on the US, documentation in English, should have documentation translated in other languages, and pursue funding.
David - need ongoing support for translation.
Este - could we start with the Fedora migration guide as a place to have multilingual support?
Tim - can we look at the survey to see what people need the most help with?
Erin - could we add content/metadata/ux migration into the survey?
Este - could we also mine Slack channels to see what kinds of questions come up?
Eri
