As a manager, one of the biggest challenges when starting any project (Hydra, or otherwise) is feeling comfortable that you’ve asked all the right questions before the first development hour is logged. But what are the right questions? And once you begin, how do you ensure that you, your developers and your stakeholders remain on the same page throughout the course of the engagement? This presentation will explore two processes that DCE employs to tackle these concerns, A partial audio recording of a presentation at Hydra Connect 2016 described thus, and the Scoping Phase and the Inception Deck. We'll explore how these to practices work to consolidate project expectations and fend-off wild assumptions, helping you to feel confident that when everyone says ‘circle,’ no one is picturing a square.
Using Sufia 7 as a reference model, what does the path for depositing a new item into a Hydra/PCDM based repository look like from an end-user, code, console, solr, and fedora perspective, A presentation given at Hydra Connect 2016 described thus, show the upload of new digital content via the Sufia UI and show each step of the data flow in the Browser, rails console, and Fedora. Walk through derivative generation and show the various PCDM relationships being built at each stage. Then add a new user collection, and walk through the same flows as a work is added to a collection, and what gems are in play, what does the data look like from a ruby developer perspective, what is persisted in Fedora and Solr - how does it all relate to PCDM? A video of this session is available at the 'Related URL' below.
Keyword:
Connect 2016, Hydra, Portland Common Data Model (PCDM), and Sufia
The Governance Working Group was chartered by Partners thus, A one-page summary of the discussion, documentation, and feedback to-date related to the various governance models under consideration. * Synthesis, This step will be shepherded by Steering, as the proposed model will also be assessed for legal, licensing, and MOU implications prior to further community review. * Proposal, Development of a draft governance proposal and incremental steps to implementation if appropriate * Community Input, Circulation of the final proposal for potential adoption at a Spring/Summer 2018 partner meeting, The Governance working group is a small group chartered by the community to help synthesize and formalize the various governance discussions and documents currently underway. The scope of the Samvera Governance Working Group’s deliverables will be, Circulation of the above to Partners, stakeholders, and the Steering group for review, comment, and change requests to the proposal * Legal Review, * Context, A revised governance proposal based on community, stakeholder, & legal feedback * Community Review, and A summary of the themes and issues that the community hopes to address by refining existing or adopting new governance practices and structures. Ideally identifies key differences and decision points between the models provided for evaluation and current model. This combined context and synthesis documents should be approximately 750-1500 words (1-3 pages) in length * Draft
Keyword:
Governance, Interest and Working Groups, and Samvera
University of Michigan, Data Curation Experts, Northwestern University, DuraSpace, Emory University, Princeton University, Indiana University, and Cornell University
A presentation given at Samvera Connect 2018 described thus, Despite widespread interest in Hyrax, Samvera’s new flagship repository solution, there is a dearth of documentation about how to run a production instance. We’ll cover the lessons we’ve learned from a year of building and hosting Hyrax, including our new project checklist, logging and monitoring practices, and data migration paths. DCE has been hosting a Hyrax based ETD repository for Emory University for 12 months. We've made a lot of discoveries and improvements since we launched. We'll be sharing our learnings and best practices for running Samvera Based repositories including, and * Infrastructure as code (esp. ansible for configuration management) * Monitoring using open-source and commercial tools (nagios, ok computer, splunk, pingdom, honeybadger) * Maintenance, Upgrades, and Testing A video recording of this session is available at the 'Related URL' below.
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
