-
Notifications
You must be signed in to change notification settings - Fork 14
2019.06.18 Editors Meeting
neilsjefferies edited this page Jun 19, 2019
·
10 revisions
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)
-
PR #362
- Previous discussions: 2019.03.30 Editors, Issue #320
- Agenda for Editors Meeting @ Stanford
- Planning draft. Is this still relevant?
- Update from Julian Preservation API meeting?
- Working towards a 1.0 release
- Updates from Open Repositories 2019
- 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
- Bringing back
closed
issues/use-cases that are appropriate for future releases - Community calls: ensuring clarity of when they are happening, and who is hosting
- OCFL branding artwork by @phochste
- 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
-
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.
- 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.
- Bringing back
closed
issues/use-cases- We should bring these back
- Potential topics for new presentations
- Some new topics for presenting on
- Rosy presenting to Northwestern
- 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
- 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