At the Digital Collections and Archives (DCA) at Tufts University we have designed, built, and integrated our archival collection management system and repository’s administrative interface to facilitate ingesting archival objects into our Fedora based repository. This 24x7 session briefly explores the assumptions and functional requirements we have used to guide this development work. The DCA’s unique position as an archives that is one of the key stakeholders and users of the Tufts institutional repository has enabled us to meet this integration challenge. The session describes how the integration of our archival collection management system and our repository relies on the ability to flexibly move metadata from one system to another. and A lightning talk given at the Open Repositories conference in 2015 held in Indianapolis described thus
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, provide an update on progress to date, At the University of Alberta Libraries we are currently developing a Digital Asset Management System (‘Hydra North’, built on Hydra and Fedora 4) to bring all of our digital assets into one platform for discovery, access and preservation. The metadata underlying these repositories has been created according to many standards (DC, MODS, EAD, etc.) and varies in level of fullness and overall quality. We find ourselves at a ‘metadata crossroads’ as we attempt to bring this disparate metadata together. We see a solution in a move to RDF and the application of the principles of linked data. In this presentation we will discuss some of the initial questions we asked ourselves as we tried to fully grasp what the move to RDF and linked data would mean for our existing metadata, provide concrete examples of the thought processes and workflows involved in moving from existing non-RDF metadata to RDF, based on the principles of linked data, outline some of the decisions we made along the way, and why, and what the impact has been, and reflect on lessons learned and outline next steps.
Indiana University Bloomington Libraries is involved in two new projects to digitize and store content and related metadata. Each of these projects presents unique challenges. We want to use the same technology stack for both, however, so we are choosing Fedora as a storage mechanism, with Hydra-based Sufia as a repository front end. We will discuss our decision, show advantages of this Hydra/Fedora framework, and discuss advantages of moving to Fedora 4. We will also contrast this framework with the way we might have approached these projects in the past with previous versions of Fedora and before Sufia or Hydra were options. and A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus and Avalon Media System requires support for complex structure and modular descriptive metadata management. Use cases and examples will examine options for Avalon in Fedora such as the RDF data model in Fedora 4, static XML datastreams, and external data stores to determine which path best fits structural and descriptive metadata needs for time-based media.
Component Maintenance WG - James Griffin BrowseEverything IG - James Griffin Metadata IG - Anna Goslen Hyrax v3.0 Metadata Application Profile Documentation Review WG - Nora Egloff Repository Management IG - Moira Downey Infrastructure WG - Michael Klein Newspapers IG - Eben English Hyrax Maintenance WG - Tom Johnson Geo Predicates WG - John Huck The video recording of this segment is available at the 'Related URL' below. and Working and Interest Group Updates
Slides from an on-line workshop given at Samvera Connect 2020 On-line described thus and *Overview of the M3 schema *Requirements and Installation for Allinson Flex *Overview of Allinson Flex usage *Constraints and next steps discussion Allinson Flex brings on the fly user editable M3 metadata schemas to Hyrax and repositories built with similar components. We'll dive deep into what the M3 schema is and how it is structured, how Allinson Flex works today and what our plans for the future bring. Workshop will be divided into 2 parts. Part 1 will be a feature overview and discussion / dive into how M3 schemas are laid out. Part 2 will be a hands on installation and configuration of the Allinson Flex tools and a code dive into certain features.
A set of very brief (3 minute) presentations given at Samvera Connect 2020 On-line updating the Community on the work of some of its Interest and Working Groups. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Elixir, Phoenix, React, GraphQL, PostgreSQL, Elasticsearch, Amazon Web Services, Docker and Terraform. This presentation will focus on describing why we chose this path and the decisions and tradeoffs we've made along the way, along with a brief demonstration of our current state. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., Northwestern University Libraries has been building a "green field" digital repository application since June 2019, code-named "Meadow". Our goal in building Meadow is to provide an internal tool to ingest, modify and publish digital resources to an API that drives our user-facing digital collections frontend. Meadow's development roadmap has focused on complementing NUL's existing production workflows and implementing best practices in digital preservation in a cloud-based environment. Meadow is built with a several languages, tools, and frameworks including, and A presentation given at Samvera Connect 2020 On-line described thus
A presentation given at Samvera Connect 2020 On-line described thus and Princeton University Library’s digital projects and initiatives were seriously disrupted by COVID-19. Digitization of materials for projects and forthcoming exhibitions came to an unexpected halt at the same time as patrons and staff were separated from physical objects and library spaces. Necessity, however, provided an opportunity to reassess digital projects and how staff members interact with and contribute to our repository (Figgy). We focused on the creation of workflows and documentation for new contributors who would be working in the repository, helping them enhance existing digital objects with OCR, item level organization, structural metadata, page labeling, and IIIF display attributes. We describe how we were able to use Figgy and unexpectedly-available staff time to make more effective research tools and provide a better user experience for patrons and staff working with our digital collections. Such enhancements add immense value to our collections as well as to our applications, and the work can be done effectively by a wide range of staff from different departments with variable skill sets. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
one size would not fit all for our campus archives, library, and museum, and community needs above all. In this presentation, team members will talk about the past two years of experimentation, development, and conversation around how to connect our community to our cultural heritage collections through multiple integrations, both human and technological. At a high-level, we’ll discuss our technical architecture that uses legacy applications like ArchivesSpace, an aging Fedora repository, and a decades-old museum database together with the IIIF framework and open-source GatsbyJS. And perhaps more importantly, we’ll outline the cross-departmental team structure that has developers talking to museum curators, library cataloguers, archivists, and everyone in between. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., The University of Notre Dame has taken a modular approach to building a new digital collections platform-integrating existing applications and connecting the people that manage and use them across the library, archives, and art museum. We began with two assumptions, and A presentation given at Samvera Connect 2020 On-line described thus