Time/Place

• Time: 3:00pm Eastern Time US
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php

Attendees

• Andrew Woods
• Nick Ruest
• Michael J. Giarlo
• Joshua Westgard 
• Youn Noh
• Karen Estlund (present?)
• Esmé Cowles
• David Wilcox
• Jon Stroop
• Benjamin Armintor (present?)
• Mark Jordan
• David Chandek-Stark (present?)
• Elliot Metsger (present?)
• Aaron Birkland
• Justin Simpson
• A. Soroka
• Michael Durbin
• Unknown User (acoburn)
• Audrey Templeton
• Don Richards

Related

• Design - Import - Export

Agenda

1. Introduction and topic summary
   1. Establish common understanding of function of Import/Export
2. Use case discussion
3. Review initial requirements
   1. Two flavours of import/export effort; RDF and binaries vs BagIt Bags
4. Confirm commitments
   1. Stakeholders
      1. Uses cases
      2. Requirements
   2. Developers
   3. Testing and validation
   4. Documentation
5. Workplan and timelines
   1. Sprint scheduling

Minutes

1. Roll call of attendees (~16 persons were on the call)
2. Goals of this meeting: 
   1. Shared understanding of what we would like to achieve (specifically in 2 week sprint) – probably a subset of what falls into the scope of import/export
   2. Look at the calendar to plan when the feature sprint might be scheduled
3. Andrew Woods commented on two flavors of import/export:
   1. Raw RDF serialized in some way to disk, plus the binaries or files associated with the objects
   2. Bagit bags that could be imported/exported and round tripped into a Fedora repository
4. Andrew Woods is hosting this initial call; Nick Ruest will lead the effort/sprint going forward
5. Nick Ruest led a walk through of the use cases and requirements on the design page
   1. Use Case #1: Transfer between Fedora and external preservation systems
      1. there was general agreement that round-tripping was implied in 'transfer between' 
      2. discussion of whether content should be assumed to be in Bagit bags (often yes, but not universally so)
      3. after some discussion, suggestion was made to let the particulars be refined later 
   2. Use Case #2: Export the content of a single Fedora container and all its descendant resources
      1. the ability to define a subset of resources
      2. hypothetically one might wish to be able to configure the property that determines containment (other than LDP:contains)
   3. Use Case #3: Transfer between fedora instances or (more generally) from Fedora to an LDP instance
      1. this use case was intended to help flesh out whether the transfer was between the same repository
   4. Use Case #4: Import into a specified container
      1. the problem here could be that there could be very different ideas about what to do if there are conflicts
      2. lossless round tripping is probably not possible (creation date, for example), though the barriers to that are rooted in policy decisions that could be changed (making dates alterable, for example)
      3. issue of versioning: the versioning in Fedora 3 would allow a new version to be created if a resource already exists
      4. the issue of adding resources to an existing export was raised; an additional use case will be created.
   5. Use Case #5: Round-tripping resources in Fedora in support of backup/restore
   6. Use Case #6: Round-tripping resources in Fedora in support of Fedora repository version upgrades
6. Due to a lack of time, use cases 5-6 were not discussed in detail. It was agreed that a second planning meeting would be held in one week at the same time. Andrew Woods raised one final consideration going forward for the planning of this work: a development sprint around Bagit is planned for September at Penn State.  This sprint would be a good opportunity to fix bugs or add additional features to an initial implementation, if it is possible to carry forward the planning, scheduling, and completion of an initial development sprint in the interim.