Time/Place

Time: 3:00pm ET

Audio Conference: 

Join from PC, Mac, Linux, iOS or Android: https://duraspace.zoom.us/j/8128353771

Or iPhone one-tap :
US: +16699006833,,8128353771# or +16468769923,,8128353771#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 876 9923
Canada: +1 647 558 0588
Australia: +61 (0) 2 8015 2088
United Kingdom: +44 (0) 20 3695 0088
Meeting ID: 812 835 3771
International numbers available: https://zoom.us/u/MO73B

Attendees

Agenda/ Notes 

TopicLead
Review pilot guidelines and answer any questionsDavid

Discuss UW Madison pilot details

  • What are the desired outcomes?
  • What are the timelines?
  • What is our communication plan?
David

Next steps

All


Notes

Objectives

  1. UW on F3.8 with custom frontend
    1. Exporting to Solr
    2. Viewing with Rails app
  2. UW Goal: simple migration
    1. Minimizing changes to data model
    2. Keeping datastreams as datastreams... minimal transformation
    3. Maintaining F3 URLs is not critical
  3. Fedora/DuraSpace goal: validating approach to F6... addressing real-world requirements
  4. "Validate Fedora 6 design against stakeholder requirements"
    1. Be able to reconstitute a Fedora object from OCFL on disk (i.e. rebuild from OCFL on disk, and/or spinning up F6 over a copy of Fedora-OCFL)

Responsibilities

  1. Development sprints:
    1. 2 in Fall of 2019
    2. 2 in first half of 2020

UW

  1. UW has management commitment to pilot participation
  2. Sample data
    1. Using akubra - can tar-up existing content
    2. ~0.5 million objects in production store
    3. Will provide a smaller dataset for initial testing
    4. Deadline: Aug 7
  3. Communication channels
    1. #fedora6-pilots Slack channel
    2. Mailing lists
    3. Weekly Fedora tech call - please join call as possible
    4. Direct email to Scott/Peter is welcomed
  4. Institutional requirements?
    1. Currently using Fedora in a reduced role
    2. No disseminators
    3. Mostly focused on preservation
    4. The direction of F6 appears to be designed for UW requirements
    5. Documentation of F3 → F6 migration process
      1. ..to facilitate a seamless migration when the time has come
  5. It would be valuable to have the migration experiences, tools, case studies communicated to the broader community

DuraSpace

  1. Reciprocal responsibilities to UW's set

Next steps

  1. Sample data - Aug 7
  2. Requirements - prior to first F6 sprint
    1. If there are such requirements
  3. 2019-02 Fedora Design Summary
  4. Will be attending weekly tech calls starting in Aug
  5. Will be keeping pilot partners up to date during sprints

Actions


  • No labels