How can we include user experience [UX] best practices in Hydra's core development work? How can UX experts contribute effectively to the Hydra project? How can we ensure that decisions around elements that affect the user experience are based on good evidence? Through case studies and facilitated discussion, this panel will seek to demonstrate and explore how to better integrate end-user feedback into the Hydra development stream. Dave McCallum from the University of Oregon explores issues of accessibility and the user experience. Jenn Colt from Cornell University and Sonya Betz from the University of Alberta will facilitate an active discussion around building UX into Hydra development workflows, and will ask participants to suggest strategies for including real users and their feedback in design and development decisions. The second presentation is available at the 'Related URL' below. An audio recording of the session is available for download below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Hydra, and User experience
Subject:
Hydra Project
Creator:
Betz, Sonya, Colt, Jenn, and McCallum, David
Contributor:
Cornell University, University of Oregon, and University of Alberta
The Samvera Branch Renaming Working Group formed in August 2020 to create a recommendation, plan, and timeline for our community to stop using long-practiced "master/slave" coding jargon that perpetuates racist systems and language, and instead embrace and implement positive change, leading by example. This presentation will detail the work of this group, A presentation given at Samvera Connect 2020 On-line described thus, and the guiding morals and philosophy for undertaking this work, where and why we prioritized change while some communities are left uncertain how to proceed with similar work, the challenges we have discovered along the way, our immediate future plans, and the forward-to-better model that we hope this group’s deliverables put forth for the Samvera Community and others in the Open Source world. The 'Related URL' below links to a video recording of the session. The video has closed captioning.
Keyword:
Interest and Working Groups, Connect 2020, and Samvera
Subject:
Samvera Community
Creator:
Rayle, E Lynette, Dunn, Alexandra, Brittle, Collin, Lynch, Kate, Friesen, Jeremy, and Colvard, Chris
Contributor:
Ubiquity Press, University of California Santa Barbara, University of Notre Dame, Cornell University, Emory University, and Princeton University
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 and We will share our experience as we built the United States Department of Agriculture's Economics Statistics and Market Information System (USDA ESMIS) from Sufia 7.2 to Hyrax 2.1. A video recording of this session is available at the 'Related URL' below.
A presentation at Samvera Connect 2019, originally titled"Questioning Authority, Questioning authority is a Samvera developed gem that provides a standard way of accessing external authority controlled vocabularies. As part of the Mellon Foundation-funded Linked Data for Production (LD4P) project, this gem was expanded to include a module for general processing of authorities that provide linked data regardless of ontology. This module leverages the existing normalized data format of QA and expands it to include extended context allowing for more accurate selections. Also part of this work was the development of QaServer which is an engine from which you can build a standalone Rails app acting as a service point for submitting queries to QA. The QaServer includes a management UI to explore the availability of authorities and the performance of requests. We will look at recent enhancements to QA, the QaServer UI, a caching system for linked data authorities without an API, metadata entry using extended context, and how we’ve leveraged linked data in some of our user facing applications., and Connecting to Authorities through Linked Data", described thus
Keyword:
Linked data, Grants, Samvera, and Connect 2019
Subject:
Samvera Community
Creator:
Rayle, E Lynette and Eichmann, Dave
Contributor:
Andrew W Mellon Foundation, Cornell University, and University of Iowa
A workshop given at Samvera Connect 2018 described thus and Have you ever wondered when to use admin sets vs collections, what this new collection type is all about, or how many work types you should have? This workshop will focus on designing approaches for best practices on using admin sets and collections in structuring a repository in Hyrax. We will talk about the basic building blocks available in Hyrax from collecting items to controlling visibility to work types and files. Consideration will be given to various uses cases, from single-use case systems to complex multi-use case systems. There will be time for hands on design in groups of use cases brought by participants.
Keyword:
Workshop, Architecture, Connect 2018, Samvera, and Collection management
Subject:
Samvera Community
Creator:
Rayle, E Lynette and Rudder, Julie
Contributor:
University of North Carolina Chapel Hill and Cornell University
Flexible approaches to grouping things in the repository" and described thus, An introduction to the Hyrax 2.1 Collections which include collections extensions, once known as Display Sets. This implementation adds the ability to define collection types with various settings to meet the many use cases for collections from user collections to exhibits. We'll also look at how these play nicely with Admin Sets., and A presentation given at Connect 2017 advertiosed under the title "Collections Extensions and Admin Sets
Keyword:
Hyrax, Connect 2017, Samvera, and Collection management
Subject:
Samvera Community
Creator:
Rayle, E Lynette
Contributor:
Cornell University and Collection Extensions Working Groups
Want to move beyond a simple autocomplete field for controlled vocabularies? Want a more accurate selection process? We will look at a Hyrax demo app that uses questioning authority to search linked data authorities and extracts multiple predicate values from search results to provide additional context in a lookup table to help with the selection process from a controlled vocabulary. The presentation will include direct access to OCLC Fast, locally cached access to Library of Congress and GeoNames, as well as others. and A presentation given at Connect 2017 originally advertised as "Lookup with Context to select metadata values from a controlled vocabulary" and described thus