Fedora Repository Usecase Review & Submission

[Robin Lindley Ruggaber]

All,

   A group of committed software engineers will meet on Feb 25th to design functionality for the next major release of Fedora Repository software. 

   What can we do to best support that effort and protect our investment in Fedora? The most urgent need is to review and update existing use cases,  and submit use cases for additional functionality before February 25, 2019. A simple template for new uses cases is also provided. Please add new use cases to the wiki or send them to David Wilcox or Andrew Woods.  

    At UVa, Fedora is a core element of our preservation infrastructure. We need the  next release of Fedora to afford transparent persistence and align with the Oxford Common Filesystems Layout (OCFL) to simplify migration.  What are your most critical use cases?

   As a co-chair of Fedora Steering, I want to thank everyone in advance for this work and to those of you who have committed resources for the design and implementation of the next major release. 

Sincerely,

Robin Ruggaber

Fedora Steering Co-Chair

Library IT

University of Virginia

[west...@umd.edu]

Thank you, Robin, for starting this ball rolling.  I have just spent some time reviewing the existing use-cases, and "liking" those that seemed important for us.  It soon became clear, however, that many of the use-cases there are germane to the API, others to the uderlying storage layer, and others are specific to applications that are built on top of Fedora and which may themselves have changed a lot in recent years.

Given that we now have the API as a starting point, would it make sense for us to start a new set of use-cases specific to the task of implementing the API over a different storage layer?  I wouldn't want to re-invent the wheel unneccessarily, but it feels like that might make it easier focus on the things that are up for discussion with the next major release.

Best,

Josh

[west...@umd.edu]

Or, another thought, would it be sufficient to create new use-cases in the same location but label them as "Fedora 5 -> 6 use-cases" or something like that?

[Robin Lindley Ruggaber]

Josh,

   I apologize for the delayed response. Yes, I agree that adding new cases makes the most since. Those were written long before the API was even a vision. I do appreciate your time and effort to come to this conclusion. I do think the simple template remains worthwhile to use.  I have renamed the old content list to 2012-2016 and added an area for 2019- people will need to use the label “fedora6usecase” for their page to aggregate correctly. I have also created a simple example.

Thanks again for this feedback!

Community,

Please submit your use cases for Fedora6 here.

Thanks to everyone in advance for this effort,

Robin

Robin Ruggaber

--
You received this message because you are subscribed to the Google Groups "Fedora Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fedora-communi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Wilcox]

Hi all,

I went through the list of 2012-2016 use cases and tagged most of them as either already completed or obsolete, and I moved a number of them that might still be relevant to the Fedora6 Use Cases section. This should make the list easier to review.

There is still time to submit use cases [1], so please do so if you have requirements for adopting the next version of Fedora. A number of use cases have already been submitted, so you are also invited to review and Like or comment on use cases that are relevant to your institution. 

Thanks for your engagement,

David 

[1] https://wiki.duraspace.org/display/FF/Use+Cases

--

David Wilcox
Fedora Product Manager
DuraSpace
dwi...@duraspace.org