Many institutions need to import, export, and migrate data in bulk, and the ability to do this easily should be a fundamental service offered by any repository. For Hyrax, there are a range of home-grown and community solutions focused on specific use cases but there are no easily reusable community solutions. That’s starting to change and we’d like to talk about our specific experience building ‘Bulkrax’ and ‘Zizia’, two bulk import-export engines for Hyrax. This talk will outline the current status of our two projects, covering the design and approach taken, alongside features such as OAI-PMH import, and CSV import and export. We'll also talk about where Bulkrax and Zizia are going in the near future. We’ll show how each can be adopted, configured, and extended to meet local use cases, and how these projects are meeting the requirements set out by 2018’s ‘Batch Import-Export Working Group’. We’ll also discuss how best to move forward as a community around this issue, This will mean developing not only software but also shared community practice for managing the flow of bulk metadata from legacy systems and digitization projects into Samvera repositories., and A presentation at Samvera Connect 2019 described thus
As most Hyrax adopters know, Hyrax offers a basic set of metadata properties that it assigns to each new work type. Most adopters will extend that set, to a greater or lesser degree, adding new properties, defining vocabularies and terms lists, and setting other constraints and requirements. Adding new metadata is a complicated process in Hyrax, and there are various ways in which developers have worked to streamline things (eg. scooby snacks, dog biscuits and archetypes). But before we even get to customising a Hyrax application, metadata librarians and developers must collaborate on specifying the metadata requirements. With no community machine-readable approach to defining those requirements, misunderstandings are common, and can be costly. With a machine-readable specification for metadata, metadata librarians could accurately specify requirements and developers could validate and codify those into applications. That’s where the Machine-readable Metadata Modeling Specification (M3) steps in. The specification is the output of the M3 Working Group and is nearing its version 1.0 release. This presentation will provide a walkthrough of the specification, show how to construct and validate a new M3 profile, and illustrate the benefits of M3 for both metadata specialists and developers. and A presentation at Samvera Connect 2019 described thus
Using agile for more accurate proposals - Aaron Collier New Tools for NU, A combined slide pack containing the lightning talks presented at Samvera Connect 2019. Deploying a custom Hyrax on Azure with Terraform and Kubernetes from a standing start - Julie Allinson Controlled Vocabulary Options in Hyrax - Julie Hardesty Scholarsphere is Dead, Long Live Scholarsphere! - Adam Wead Work Estimation Records, and Elixir, Broadway, Phoenix, and GraphQL - Michael B Klein Hyku Open Source Institutional Repository Development partnership awarded $1M Arcadia grant to improve open scholarship infrastructure - Brian Hole Showcasing & Connecting Women in Technology - Robin Ruggaber Iterating on a Hiring Process - Jeremy Friesen
Keyword:
Lightning talk, Samvera, and Connect 2019
Subject:
Samvera Community
Creator:
Klein, Michael B, Collier, Aaron, Wead, Adam, Ruggaber, Robin, Hardesty, Juliet L, Allinson, Julie, Friesen, Jeremy, and Hole, Brian