A presentation given at Samvera Connect 2020 On-line described thus and Figgy is Princeton University Library’s staff-facing repository management application. This presentation will share screenshots, user stories, and technical overviews of all the forms, magic buttons, storage integrations, drag-and-drop targets, rake tasks, and directory watchers that Figgy provides to support the different workflows our users have for ingesting content. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
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
A lightning talk at Samvera Virtual Connect 2019 described thus and I'll present the many contexts in which pair programming can be beneficial in different ways, reasons to use pairing as part of the regular practice of your team, the basic mechanics of how pairing works, prompts for staying mindful of power dynamics while pairing, and ideas for introducing the practice to a team that has never really done it before.
A presentation given at Samvera Connect 2018 described thus and A project description of adding our first A/V materials to Princeton's repository management software, Figgy. I'll briefly describe the project history, the collections in question, and project management strategies. Will demo the resulting ingest workflow. A video recording of this session is available at the 'Related URL' below.
We will present our use case for and development of a GraphQL API in Figgy, our Valkyrie-based digital collections management application. We'll give a brief summary of GraphQL itself, demo an in-broswer query tool called graphiql, and show how we used the graphql gem to quickly develop and deploy a GraphQL API endpoint. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
I will use Natural Language Processing and Machine Learning techniques to analyze issue backlogs in applications from institutions throughout the community. I will apply a variety of techniques in an attempt to answer questions like, What kinds of open issues do we have in general as a community? Can I extract an interesting set of widely-desired features or widely-held use cases? Can I identify connections that might lead to collaboration across institutions? What solutions already exist that might advance open issues? Can I link open issues in one backlog to merged PRs in another repository? What have people been working on recently? Can we characterize the full set of issues that have been closed over the past year? What patterns of development do repositories follow? Can we describe the life cycle of repository development by aligning issues based on their creation / completion dates relative to the initial commit? These may or may not be the exact questions my talk will address, depending on the direction the project naturally takes. I will focus on applications in use or under development at institutions, as opposed to community-maintained engines and core gems. This talk will describe my process, results, and evaluate the success of the endeavor., and A presentation at Samvera Connect 2019 described thus