Samvera Tech Call 2020-09-02

How to connect: https://notredame.zoom.us/j/94030214208 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

Time: 9:00am PDT / Noon EDT

Moderator: @tamsin woo

Notetaker: @James Griffin

Attendees:

• @Jeremy Friesen (University of Notre Dame)

• @rkadel (Data Curation Experts)

• @Brickman, Nelson (Deactivated) (UC San Diego)

• @Chris Colvard (Deactivated) (Ubiquity Press)

• @Collin Brittle (Emory University)

• @Lynette Rayle (Cornell University)

Agenda

1. Roll call by timezone per following order - ensure notetaker is present (moderator)

   1. folks outside North and South America

   2. Eastern timezone

   3. Central timezone

   4. Mountain timezone

   5. Pacific timezone

   6. folks who were missed or who dialed in during roll call

   7. Remind everyone to sign in on agenda.

   8. Welcome all newcomers!

2. Agenda (moderator)

   1. Call for new agenda items (moderator)

   2. Hyrax Containers (@tamsin woo )

      1. Dev Environment:

         1. `git clone git@github.com:samvera/hyrax.git; cd hyrax; docker-compose build; docker-compose up`

      2. Published, reusable containers:

         1.  https://hub.docker.com/u/samveralabs

      3. Kubernetes/Helm

         1. fcrepo4 chart

         2. hyrax chart

         3. draft documentation: https://github.com/samvera/hyrax/commit/6d61df9557c4a066a16397f6ab07ed4a17e50d5d

   3. Samvera Connect presentation submissions

   4. Samvera Dev Congress update

   5. <add open agenda items here>

   6. Samvera help follow-up

      1. https://app.slack.com/client/T0F4TBPB9/C0F9JQJDQ/thread/C0F9JQJDQ-1599061557.031200

   7. Pull request review

      1. https://github.com/samvera/hyrax/pull/4493

3. Moderator & notetaker for next time

   1. Moderator:

   2. Notetaker:

4. After call, this week's notetaker should create the agenda for the next call:

   1. Open template agenda titled "Samvera Tech Call 2020-xx-xx"

   2. Click on ... in the top right corner, and select copy.

   3. Popup will open for location. It should contain: 

      1. Space: Samvera

      2. Parent page: 2020

   4. Select copy. New page should be created.

   5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.

5. PR Review

   1. Review issues:

   2. PR review coordinator for next time: 

Notes

• Containers for Hyrax

  • Tom has been providing updates on this work in the #dev Channel

  • There is now a docker-compose environment which Tom is using as a development system

  • Tom has also been exploring strategies for reusable containers

  • Quite a lot of progress for finalizing a Kubernetes environment and Helm in order to ensure that Hyrax can be deployed into a reference environment

    • PostgreSQL, Solr, and Redis would be deployed into this

  • Can this be used to provide a test environment?

    • There shouldn't be much additional labor needed in order to structure this as a test environment

  • Reusability

    • There is a single Dockerfile specifying a multi-stage build

      • First provisions a deployment directory, along with a base Hyrax setup

    • Second and third provide environments for Rails Engine development

      • Synchronization uses a local working copy for supporting development in the container

    • There is a separate plain Hyrax image useful as a base image for the developer's own Hyrax application

    • Hyrax Container is used for deployments using Helm

  • Tom is still working on this, and please welcomes individuals who might want to experiment with or test this using Kubernetes environment

    • Feedback for working with Kubernetes and Helm is definitely desired

• Samvera Connect Presentation Submissions

  • Presentation and lightning talk submissions can still be submitted

    • Everyone is encouraged to submit their proposals please!

  • Jeremy proposed to present a lightning talk discussing the structure and role of the Samvera Tech. Call

    • Guiding interested parties in how to contribute/get involved will be very helpful

    • There might be two lightning talks: the Samvera Tech. Call and a separate talk addressing getting involved

    • People may be more likely to attend lightning talks (as opposed to any call-to-action)

    • Specificity in the lightning talk is also preferred

• Samvera Dev. Congress Update

  • Is there an update from the group planning this?

  • Jeremy is on this group

    • Presently there is a Wiki Page: Developer Congress - November 16-18 2020

    • Want CfPs to first finalize for Samvera Connect

    • Dev. Congress is scheduled for Nov. 16-18th, and it will be all virtual

    • October 1st an e-mail announcement shall be issued

    • This will also be discussed during the next Partners Meeting

      • There will be a request for developer resources in order to try and ensure that enough organizations participate

  • How might others support Dev. Congress planning?

    • Please consider topics worth focusing upon

    • Perhaps Docker-related work? Ensuring that there is a collective understanding of the requirements for this at the Congress?

    • Any amount of pre-planning which we can address will only be better

      • Given that this is 3 days in length, it will only ensure that the time is used more efficiently

• Lyrasis Wiki

  • Requesting an account used to be possible with a main page where one could request an account

  • How would one do this now? This page needs to be inaccessible

    • It was recommended that one contact Richard Green with a request

• Samvera Help Follow-Up

  • Linda Sato had a question regarding AdminSetCreateService

    • https://samvera.slack.com/archives/C0F9JQJDQ/p1598896022011600 

    • Might anyone be available to respond to Linda who is familiar with the scope of this question?

    • It may be related to the database and/or Solr not being entirely clean while trying to debug this

  • Samvera-Tech Mailing List

    • Alice had general questions regarding how Samvera works

    • Answering some of the questions, following a request to the community to answer others might be the best approach

• Pull Request Review

  • https://github.com/samvera/hyrax/pull/4493

    • Authored by Jeremy, but a pull request against Lynette's PR

    • Adding human_readable_type into the Solr index requires that the anonymous class-building for Valkyrie/Hyrax support this

      • Do we need an anonymous class builder in the RSpec tests?

      • Resistance to adding a builder pattern; It is explicit regarding the dependencies if one must manually derive a child class from Hyrax::Work

      • For this PR, one needs to have an ActiveModel name, without the Class being an explicitly-named

    • Perhaps have a default for #human_readable_type also

    • It should be a reasonable assumption for the ecosystem that an ActiveModel#name be present for the object

      • With an alternate default, maybe `self.class.to_s` could suffice?

      • Agree that ActiveModel#name should be acceptable, the concern related to indexer dependencies

    • Proposed changes to the PR are welcome, but one approval was issued

      • PR was rebased and merged for Lynettes PR (4488)

    • Hyrax::Work is a Valkyrie model

      • Chris has been working off of GenericWork for a plugin

        • Is there a correlation between the GenericWork#name and the ActiveModel#name on Hyrax::Work?

        • ActiveModel#name uses a class-level method `.name`, uncertain if there is a mutator for this

        • Class method `.name` is a Ruby feature for all Classes

          • ActiveModel#name might use an override for this

          • ActiveModel#name returns an object, Hyrax::Name object in this case

          • Hence, to get a string, one needs to invoke `Hyrax::Name#name`, so `my_model.name.name`

          • There are also helper methods on `Hyrax::Name`, such as `#humanize`

    • What is the difference between `Hyrax::Name` and `ActiveModel::Name`? Are these compatible?

      • These should be compatible Class APIs

  • Merge is welcome from others

• Next Scheduled Call

  • Moderator: Jeremy

  • Notetaker: Tom

• Call concluded at 09:41 PDT/12:41 EDT