Child pages
  • Samvera Tech Call 2020-05-27
Skip to end of metadata
Go to start of metadata

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

 Click to view telephone/H.323/SIP connection instructions

Meeting ID: 940 3021 4208

One tap mobile

+13017158592,,94030214208# US (Germantown)

+13126266799,,94030214208# US (Chicago)

Dial by your location +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 646 558 8656 US (New York) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) Meeting ID: 940 3021 4208

Find your local number: https://notredame.zoom.us/u/aPls29JbL

Join by SIP 94030214208@zoomcrc.com

Time: 9:00am PDT / Noon EDT

Moderator: Jeremy Friesen

Notetaker: Tom Johnson

Attendees:

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. Change in Zoom URL; or what options do we have available? Jeremy Friesen
    3. Giving local Hyrax apps Wings - Check-in Chris Colvard Lynette Rayle
    4. Samvera help follow-up
    5. Pull request review
  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

  1. Change in Zoom URL; or what options do we have available? Jeremy Friesen
    1. How can we end the scramble for Zoom meetings?
      1. Santa Barbara provided a link last week; ND this week
      2. Slack may not scale.
      3. Slack is more opaque and would create a barrier for discovery
      4. Could we just create a free Samvera account?
        1. Would limit meeting time, but that's okay for this meeting.
        2. Is it possible to make a scheduled free meeting, make it open to join without the meeting owner, etc...?
        3. Jeremy Friesen will give this a try with family and see what happens.
          1. As a follow-up, I have created a personal Zoom account. I created a meeting but cannot delegate to others to be host. It also will always require a password. I'm going to pivot away from that and see what other options might exist.
          2. I also looked at Google Chat, which allows for Rooms. However Rooms require invitations, which runs contrary to our goal.
          3. I’m hitting barriers, because our aspirational goal is “We’re going to meet at this street corner each week”. However, with the services most of them say “Street corners aren’t valid, they must be in a physical building and BTW who has those keys?”
  2. Giving local Hyrax apps Wings - Check-in Chris Colvard Lynette Rayle
    1. Current work on moving some apps to Hyrax 3.0.0 and use some of the Wings Valkyrie adapter code.
    2. Cornell is:
      1. moving their app to 2.7.2
      2. fixing deprecations
      3. and then moving to 3.0; upgrade to Rails 5.2; etc...
    3. IU is making this change for Avalon Bundle (the Avalon → Hyrax development project).
      1. There are a range of plugins that needed to be updated to `master`
      2. Porting works to Valkyrie and using the configurable YAML metadata
      3. Running the test suite is leading to some failures
      4. Running into issues with the actor stack
      5. had to use this branch: https://github.com/samvera/hyrax/pull/4335
      6. we talked a bit about Wings internals and the various approaches for porting applications
      7. chatter is happening in the #hyrax-valkyrie slack channel
      8. Notes are being kept here: https://docs.google.com/document/d/1ytiQOQykJtGaBuWgyihF3Z2JIyhcPXg0DyxapbK3NCQ/edit#
      9. Question: are we working from the document folks worked on at Solar Vortex (UCSD)?
        1. A: yes, that's the Dive Into Valkyrie doc? (yes)
      10. Aiming to create general purpose documentation, e.g. in Dive Into Valkyrie and the Hyrax Valkyrie Usage Guide
  3. Samvera help follow-up
    1. It appears that we've answered and engaged in all help requests
  4. Pull request review
  5. Moderator & notetaker for next time
    1. Moderator: Jeremy Friesen
    2. Notetaker: Thomas Scherz
  • No labels