A work in progress!
All times in Eastern Daylight time (EDT).
Day 1: Tuesday, April 23, 2019
| 11:00-11:05 AM EDT | Welcome and HousekeepingRyan Steans (Northwestern University) | All Audiences | |
Community Updates | |||
Samvera Steering Update Richard Green (Consultant to the University of Hull & Chair, Samvera Steering Group) Jon Dunn (Indiana University & Chair-Elect, Samvera Steering Group) | The Chair and Chair-Elect of the Samvera Steering Group will discuss the work of Steering in a year of change. This discussion will cover the recent changes in the structure of Steering and efforts to increase transparency, along with a brief discussion of topics and issues that Steering is working on this year with the Samvera Community. | All Audiences | |
Samvera Roadmap Council Update Jen Young (Northwestern University) | A brief update on the work the Roadmap Council has done and will do since being constituted in October 2018. | All Audiences | |
| Samvera Fundraising Working Group Update | An update on the activities of the Samvera Fundraising Working Group. | All Audiences | |
Samvera Marketing Working Group Update Chris Awre (University of Hull) | We wish to share the ongoing work of the Samvera Marketing WG following its initiation in 2018. The goal for this year is to raise awareness of Samvera amongst different audiences that Samvera works with, both within our organisations and with potential new members of the community. Ideas, as ever, of what sells Samvera for you are welcome! | All Audiences | |
Presentation #1 | |||
M3 and Hyrax: Bringing Flexible Metadata to the Samvera Community Randall Floyd (Indiana University) Julie Allinson (Co-Sector) Ned Henry (UC Santa Cruz) | If you’re a developer or metadata specialist involved in building or managing a Hyrax based application, you may have discovered that developer time is required just to add new fields to Work Types or alter the behavior of existing fields in Hyrax edit forms and views. There are currently no features within Hyrax that allow for easy configuration-based metadata, so changes are required in multiple places to the code to accommodate needs beyond the core profile provided. This presentation will provide a glimpse into collaborative work currently underway that could be used as a basis to solve this problem for the Samvera community. We will begin by summarizing some individual efforts to introduce "configurable metadata", such as Houndstooth, Scooby Snacks, Dog Biscuits, and Archetypes. We will then touch on the collaborative team that has emerged from those efforts - the Machine-readable Metadata Modeling Working Group, or M3 - which is currently working to develop a draft specification for a common format for metadata modeling. Finally we will provide an overview of how this specification could be used to develop a common feature to allow for more flexible and configurable metadata in Hyrax. | Developers, Metadata Specialists | |
Lightning Talks (Day 1) | 7-minutes each | ||
Rethinking metadata design and management Arwen Hutt (UC San Diego) Ruth Tillman (Penn State) | For metadata specialists, creating metadata profiles, system requirements, and accompanying documentation often feels like a game of whack-a-mole. Current practices and technologies also mean comparing your profiles with another institutions’ is an enormous hassle. To address this problem, developers and metadatists came together to create the machine-readable metadata modeling (M3) specification. This presentation will offer some history and use cases for the specification, an update on its current status, and where to learn more. | Metadata Specialists | |
Making Hyrax more inclusive through controlled vocabulary choice Julie Hardesty (Indiana University) | What if the Hyrax web application were to support and include, by default, controlled vocabularies from marginalized communities? Currently Hyrax supplies a default set of descriptive metadata fields for describing uploaded objects. This set of fields includes Keyword (a required field) and Subject (an optional field). Neither of these fields are controlled by a vocabulary of terms upon install. The Questioning Authority (QA) gem exists as an option to configure and apply controlled vocabularies for use with fields such as these in Hyrax. While QA can be configured to work with nearly any vocabulary, the current vocabularies offered through the gem when it is installed include LCSH/NAF/GFT/MPT/DGT, FAST, Geonames, MeSH, Agrovoc, DBPedia, NALT, and Getty (AAT, TGN, ULAN). These are widely used mainstream sources for topical subject and genre description but also tend to reflect the current dominant mainstream power structure in the United States (white, male, straight, able-bodied, middle-class, Christian, Anglo). Should we increase the list of vocabularies available, by default, in the QA gem? Should we go beyond that and enable vocabulary choices on the default Subject and Keyword Hyrax fields? This lightning talk will discuss these questions and consider vocabulary options that would provide more inclusive descriptive capabilities. | Developers, Repository or DAMS Managers, Metadata Specialists | |
Break |
Day 2: Wednesday, April 24, 2019
| 11:00-11:05 AM EDT | Welcome and Housekeeping Ryan Steans (Northwestern University) | All Audiences | |