Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Notetaker: Bradley Watson

Attendees:


...

Meeting Process

Expand
titleModerator and Note Taker - click to see meeting process...
  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

      1. Recent Samvera PR list

  4. Post-meeting action (note taker)

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

      1. Open template agenda titled "Samvera Tech Call 2023-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: 2023

      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. 


...

Notes

  1. An update from Emory University’s Hyrax v5/Fedora based application:

    1. Rails logs weren’t being written to the expected production.log location. They were instead writing to /var/log/httpd/error_log. Our Middleware team was able to forward the log over to the expected location, but we’ve never seen that behavior before with Hyrax or Ruby on Rails installs.

    2. Derivatives are either not being created or not being delivered as expected. This may be a configuration issue.

  2. pg.Nurax and dev.Nurax are both down now, producing Solr errors.