https://duraspace.zoom.us/my/vivo1

• Andrew Woods (DuraSpace)
• Julian Morley (Stanford)
• Rosy Metz (Emory) *
• Simeon Warner (Cornell)
• Andrew Hankinson (Bodleian Libraries)
• Neil Jefferies (Bodleian Libraries)

(* indicates the notetaker)

1. PR #362
   • Previous discussions: 2019.03.30 Editors, Issue #320
2. Agenda for Editors Meeting @ Stanford
   • Planning draft. Is this still relevant?
   • Update from Julian Preservation API meeting?
3. Working towards a 1.0 release
4. Updates from Open Repositories 2019
5. Potential topics for future conference presentations
   • Performance and scale
   • Implementations
   • Storage layout
   • Logical <--> Storage paths
   • Forward delta versioning
   • Walk-through of inventory.json
   • Namaste files
6. Bringing back closed issues/use-cases that are appropriate for future releases
7. Community calls: ensuring clarity of when they are happening, and who is hosting
8. OCFL branding artwork by @phochste
   • Bursting 1
   • Bursting 2
   • Bursting 3

1. OR review
   • Interest in uptake of OCFL
   • Red Box - Australia - Technical University of Sydney); Invenio - looking at it - V2 may be able to address their particular concerns. see issue #363; Archipelago - Neil looking into this (http://archipelago.nyc/).
   • OCFL may be added to the list of next generation repository technologies
   • DSpace is on the rise - perhaps we can have a conversation with Tim after DSpace 7 lands
   • Haplo is getting an uptick in adoption
2. PR #362
   • discussion about how deep we want to go in the recommendations we provide. We don't want to get too far into the weeds.
   • we came to agreement that the deposit directory should be at the root. then accessioning is the only a move operation.
3. Stanford Meeting
   • Preservation Meeting. Do we have a standard way of talking about the current digital preservation landscape, and do we have a way of improving interoperability. Transfers, Remote Audit, Discovery. Stanford has a hit list of folks that they will be reaching out to around a dozen other folks. Discussion about increasing diversity. What are we trying to do, and who should we be inviting for a proper kickoff.
   • Editors Meeting Agenda. We should start an agenda and populate with topics.
4. Bringing back closed issues/use-cases
   • We should bring these back
5. Potential topics for new presentations
   • Some new topics for presenting on
   • Rosy presenting to Northwestern
6. OCFL Community Calls
   • Let's check-in on the Monday of the week of the community calls to determine who is available to attend and help facilitate
7. Artwork!
   • We like the black and white one the most.

• Zimeon: troll through use cases and find closed ones that should have been deferred.
• Rosalyn: start an agenda
• Julian: take our thoughts back to Stanford for discussion
• Neil: clean up PR #362 based on the conversation
• Julian: consider what a guidance document of the OCFL stack (on the wiki) would look like