Samvera Tech Call 2020-12-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: @Chris Colvard (Deactivated)

Notetaker: @tamsin woo

Attendees:

• @Thomas Scherz (Cincinnati)

• @tamsin woo (UCSB)

• @Chris Colvard (Deactivated) (Ubiquity Press)

• @Brian Keese (Indiana)

• @Lynette Rayle  (Cornell)

Agenda

• Developers Congress Report

• FITS Configuration for apps using Hydra Derivatives (@tamsin woo)

  1. https://github.com/samvera/hyrax/issues/4571

• Add more agenda items here

Samvera help follow-up

Pull request review

Meeting Process

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. Agenda items above

   3. Samvera help follow-up

   4. Pull request review

3. Moderator & notetaker for next time
   
   

   1. Moderator: @Lynette Rayle

   2. Notetaker: @Chris Colvard (Deactivated)

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

• Developers Congress Report

  • @Chris Colvard (Deactivated) worked with a group adding Rails 6 support to core components.

    • Hydra Editor is the only remaining known non-Rails 6 core component.

    • Once Hydra Editor has support, there's a need to work on Hyrax support.

  • @Lynette Rayle worked in one of several small groups working on Hyrax valkyrie/wings

    • single value types in Valkyrie native models

    • performance improvements for wings

  • @tamsin woo merged https://github.com/samvera/hyrax/pull/4628 yesterday

    • contains some performance improvements for Wings

  • documentation overhaul for Hyrax

  • IIIF React media work

• FITS Configuration for apps using Hydra Derivatives (@tamsin woo)

  1. https://github.com/samvera/hyrax/issues/4571

  2. fits configuration can be a big pitfall; jobs can end up running for a long time (forever) and need to be manually

  3. the issue documents a fix

  4. where should this knowledge live other than a closed hyrax issue?

     1. maybe answer: Samvera.github.io documentation pages (consensus that we should put something here)

     2. maybe also the gem readme or other gem documentation (github wiki)

  5. ACTION: @tamsin woo will open a ticket on samvera.github.io

• fits in Hyrax's docker containers (@Brian Keese)

  • trying to get fits installed in Hyrax's container, should the workers be a different image than the application container?

  • Avalon historically has one image that works for the application and for the workers

  • Some discussion about pros and cons, issues with fits download location changing unannounced.

  • DECISION: keep it simple for now, just install fits to application image and take things from there.

• help follow-up: none.