...
Absent
- Michael J. Giarlo (calling in)
- Mark Jordan (calling in)
- Timothy Shearer
- Sayeed Choudhury
Agenda/ Notes
Designing a Migration Path - collection of project resources
| Advanced Tables - Table Plus | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
...
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?
...
Andrew - migrationutils reads Fedora 3 via API or what is on disk, and writes into Fedora via the API. Increasingly thinking of going from file system to file system. From tools he agrees, but there might be a higher level recommendation to write from disk to disk rather than API, which could be a new tool.
API documentation
David - summarizes API. Utility of API is already well known. You can migrate through the API but it is slow. REST, one object at a time. Have heard that the API ingest into 4 is so slow it is not useful for mass migration. Could take 6 months to move data. NLM projected at least six months.
...
Erin - a program institutions could apply for - very interesting idea beyond picking a few institutions to start with.
...
OCFL
David - helps with speed issues with migration and batch ingest.
...
Erin - expanding on the risks to the content in terms of the deprecated applications.
Survey
Tim: additional question: what most do you need help with? (UX, content migration, metadata, etc.)
...
Scott: helpful to get responses, even if we can't help with everything
Survey Timing and distribution
Erin: release in a week, keep open 2/3 weeks; send two reminders; first solicit personal contacts, then to open lists
...
Este: stress that we want more than one person at a given institution
Survey preamble
Should take 10 minutes
Andrew: and specify number of questions
...
(update preamble to same subject/title)
Survey distribution
Erin: send out by Wednesday?
...
- Where to publish survey results
- Link excel spreadsheet to the wiki/website
- Scott will check to see if we can deposit to UW IR
- We should mint a public PID (ARK, Handle, DOI, etc.)
- What should be included in the final report?
- Summary of this morning's discussion topics
- Clear indication of what is needed for a follow-on grant (docs, tooling, etc.)
- Recommendations, prioritized tasks to present to Fedora governance leading to concrete actions
- Not a SWOT analysis, but a statement of the risks involved in not migrating away from Fedora 3.x
- Clarity about what DuraSpace/Lyrasis should do vs. what other stakeholders should do
- This will help with communication with other groups/service providers
- Prioritization based on need and impact
- Description of where this fits in with other DuraSpace/Lyrasis priorities (e.g. OCFL)
- Consider SOAR (Strengths, Opportunities, Aspirations, Risks) analysis
- Confirmation that people in the community aren't alone, DuraSpace/Lyrasis is on top of things
- Beyond just migrating from 3.x to 6.x, thinking about future versions of Fedora
- Should we check in like this every few years?
- What problems are you facing, what do you need help with
- This helps us get beyond our current governance structure, which heavily favours institutions that are able to pay membership fees
- The results of this effort could be useful to other communities as well (e.g. DSpace)
- The process could be useful to share as well
- Dissemination
- Presentation accepted at OR
- The group will put a proposal into DLF
- Islandoracon, Samvera Connect, CNI
- Organize a webinar in the Fall
- Publish a paper in an open access journal (e.g. Code4Lib)
- Include in workshops and camps
- Couple messaging with release of Fedora 6
- Next Steps in the grant process
- This is a planning grant, implementation grants typically follow
- IMLS will put out a call for proposals in September
- Support for a second phase would probably fall into 2020
- What could a follow-on grant help fund in this timeline?
- Hard to know before we see the results
- Identify priorities in the report without assuming any grant funding, but indicate where funding would help accelerate these efforts
- We want to be working on migration tooling as soon as possible
- The grant could help fund migration guide, site visits, training
- Probably target $150K
- Revisit this once we have the results of the survey on the May 13 meeting
Actions
- David Wilcoxadd "What would help" question to the survey
- David Wilcox Add option name and email address fields to the end of the survey
- David Wilcox Send out survey to mailing lists on April 17
- All: Add 5 people to the list of contacts for personal survey invitations
- All: Draft proposals for DLF, Islandora Con, Samvera Connect, CNI