Fedora, the flexible, extensible, open source repository platform for managing, preserving, and providing access to digital content, is a key component of most Samvera implementations. Fedora 4.x, the latest version of Fedora, has been in production since 2015, and since then the real-world experience of the community’s use cases has clarified Fedora’s role in supporting preservation and access in the context of large collections and performance at scale. This understanding led to an effort to formally specify the Fedora application programming interface (API) that provides a stable layer of abstraction between clients and repository instances. In this way, alternate back-end implementations suited for specific user cases can all expose the same core services to repository clients. This initiative will allow the Fedora project to adapt to technological change more easily over time while insulating clients from changes in the underlying implementation. This presentation will provide an overview of the the API specification effort, including current status, motivations, and benefits, with a particular focus on the relevance to Samvera. A brief survey of alternate implementations will provide context for the different use cases that will be enabled by the specification. This will be of interest to current and future Fedora implementers looking for an update on the current status and technical roadmap of the project. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
A presentation given at Connect 2017 described thus and In this presentation, we present Fedora 4’s performance in different use cases. These use cases are the most general use cases that were developed by the Fedora 4 performance team. We compare the performance between different versions of Fedora 4 and demonstrate the improvement between these versions. We will also describe the procedures of these performance experiments and demonstrate the software we use (Ansible, AWS, and JMeter). Our performance experiments are conducted in the AWS ecosystem, and we use an R graph tool to visualize the JMeter result. With the AWS grant, we can do many different performance experiments in many scales. Moreover, it is easy to repeat and verify the performance results using AWS. The Fedora 4 performance team wants to know more about the Samvera community’s interests related to the Fedora 4 performance. We plan to gather more use cases from the Samvera community, including middleware such as Solr, Camel, and Fuseki, etc. We can investigate, explore issues, and continue enhancing the future of Fedora 4.
Update on the recent work to implement standards-based import/export functionality for Fedora 4, working on importing and exporting Bags for migrating between Fedora repositories, and backing up to and restoring from preservation services such as APTrust, Archivematica, etc. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Fedora, Connect 2016, Hydra, Import/export, and Lightning talk
The Boston Public Library has long been a Fedora 3 Commons system and we are heavily invested in that backend. After waiting to see how Fedora 4 Commons develops and with some recent internal debate, our "next gen" repository solution is going in a different direction. This will be a (perhaps) controversial talk as to why and how we came to this conclusion. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
A presentation given at Hydra Connect 2016, described thus and In the UK, the Universities of York and Hull are looking at Archivematica's place in a research data pipeline. The two universities have slightly different use cases but share the desire to put research (and likely other) content through Archivematica on its way to the repository thus giving us a solid base for long-term preservation. We are both now in the third phase of a joint project to build proof-of-concepts to illustrate how Hydra and Archivematica can work together to manage and preserve research data. Since our project began, Jisc have launched an ambitious UK national research data shared service where a range of suppliers offer systems in different lots. Both Hydra / Fedora and Islandora / Fedora are part of the the ‘research repository’ lot of the service and the work of York and Hull has heavily informed the ‘preservation’ lot, with Archivematica one of the systems on offer. This presentation will describe the proof-of-concept work done by Hull and York, and will provide an overview of the new Jisc service.
Keyword:
Fedora, Connect 2016, Workflow, Hydra, and Archives
