Time/Place
Time: 11:00am Eastern Time (US)
Please see calendar invite for Zoom link.
Attendees
- Andrew Woods
- David Wilcox
- Danny Bernstein
- Thomas Bernhart
- Jon Dunn
- Raman Ganguly
- Scott Prater
- Ben Pennell
- Peter Winckles
- Jennifer Gilbert
- Doron Shalvi
- Jared Whiklo
- Robin Lindley Ruggaber
Agenda
Open development questions
- To what extent should Fedora 6 support vanilla OCFL? i.e:
- Do we value Fedora being able to run on top of vanilla OCFL? - in a read-only fashion? in a read/write fashion?
- Do we value a post-Fedora OCFL that is not peppered with Fedora-specific system metadata?
Use cases
- As a systems integrator, I would like a simple GET/PUT HTTP server over OCFL
- As a Fedora 3 repository manager, I would like to export my content as vanilla OCFL
- As a repository manager, I would like to bring my vanilla OCFL into Fedora
- As a digital preservationist, I would like to keep the OCFL created by Fedora but stop using Fedora
Context
- In order for Fedora to manage repository content, Fedora-specific system metadata is required (caveat for vanilla OCFL)
- Although it is meaningful and self-describing, there is some stakeholder concern around including content in an OCFL object that is in addition to what the user provided
- Currently, Fedora segregates this system metadata into its own directory (".fcrepo/") within the OCFL object
What system metadata are we exactly talking about?
Structure and location of Fedora system metadata in an OCFL object
Notes
Action Items
- Type your task here, using "@" to assign to a user and "//" to select a due date