Archiving Research Data into Hydra through the Open Science Framework (OSF) - A look at initial work of Notre Dame and Johns Hopkins to archive research projects from the OSF into Fedora and Hydra repositories, and first implementation of a Fedora Research Object Model. This plugs into a service offering of the Center for for Open Science, OSF for Institutions (OSF4I). ND/JHU version will be initial support for OSF Fedora Archiving Add-on in the OSF as part of OSF4I offering. We hope to start discussion around next steps for other Hydra institutions to use this along with OSF4I to allow them support to archive research data from the OSF into their own Hydra/Fedora repository. An audio recording of the session is available for download below. and A presentation given at Hydra Connect 2016 described thus
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. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Archivematica, Workflow, Hydra, and Preservation
and we often need to make localized adjustment(s) to address either an underlying bug or to extend existing behavior. The code-base has places for configuration, but sometimes that might not be enough. Join me on a foray into how you can make the Ruby/Rails changes you need now and not make things (too much worse) for your future self and others. and The Samvera stack is deep
- Large ingestion of 4 gig tifs with derivates and preservation checks (10k works) in ~ 1 hour - 5k batch metadata updates ~5 minutes - Round trip spreadsheet update (5k records in 5 minutes) - Preservation dashboard / verification - Local authority creation and updates This presentation will discuss the process, what we learned, and how it relates to the Samvera community at large. and On St. Patrick's Day NU went live with our new digital collection repository and asset management tool prioritizing speed of ingestion and metadata updates. We reframed the problem by working with end-users to look closely at workflows and prioritize solutions rather than any specific technology. The resulting application ecosystem is extremely budget friendly and the architecture supports
Between 2018 and 2019, Jisc funded an effort to refresh the SWORD repository deposit protocol, with modern repository use cases in mind, especially around data repositories. As a result we produced a draft specification, extensively reviewed by a large number of the repositories community, including those from the Samvera and Fedora communities. In 2019, NII provided funding to produce a reference implementation, and we have been working to prove that the specification is implementable and viable. That work concluded in July 2020 with the release of a client library and a server library in Python. Now the SWORDv3 team is looking outward to the rest of the repositories community, looking to engage them in development for their platforms, and to enable novel integrations. This presentation will introduce the spec for those that are not familiar, and describe the technical and community-building work that is ongoing, and call for engagement by the Samvera technical community in working with SWORDv3. The YouTube 'Related URL' below links to a recording of the presentation with closed captioning. and A presentation at Samvera Connect 2020 On-line described thus
Keyword:
Samvera, SWORD, Protocol, Connect 2020, and Metadata
Ubiquity repositories, which are based on Hyku, are designed to be highly scalable, highly reliable and quick to deploy in the cloud. In this presentation we will outline the technical architecture we have implemented, along with the challenges faced. These include scalability, security, cost-efficiency, performance, reliability, resilience, portability, delivery pipelines for code deployment, error reporting, testing and localization. We will also discuss our approach ensuring we remain on the most recent stable branch of the platform and contributing our code back to the community. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Collaboration, Architecture, Samvera, API, Customization, Connect 2020, Hyrax, and Hyku
