Versions Compared

Old Version 1

changes.mady.by.user Rebekah Kati

Saved on

compared with

New Version Current

changes.mady.by.user Bradley Watson

Saved on

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: Daniel Pierce

      2. Notetaker: Chris Colvard

    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. Bradley Watson PRs:

    1. https://github.com/samvera/hyrax/pull/6866 Does this require remediation in either Fedora 4 or Fedora 6 implementations?

      1. For Fedora 4, compatibility is only with ActiveFedora, which pulls indexing predicates from the models themselves, and this change is only in YAMLs that feed Valkyrie.

      2. For Fedora 6, this would be necessary if we know of other institutions actively using Hyrax/Valkyrie/Fedora 6, but at the moment, it’s just Emory. Emory is in development processes that include rebuilding databases/repositories when necessary, so this won’t affect their practices.

    2. https://github.com/samvera/hyrax/pull/6884 This needs to addressed within Valkyrie first, and then possibly Hyrax. Changing this PR to draft.

  2. Implementing Flexible Metadata Schemas: should we refactor to a model by model basis? First the models, then the indexers (as far as PRs are concerned).

  3. Revised Rails Maintenance Policies: versions serviced for only 2 years. Hyrax needs to be upgraded to Rails 7 soon.

    1. Avalon is planning to upgrade all components used by it soon.

    2. Hyrax 5 should contain all of the Fedora 6 compliance code, not v6.

    3. Open question: should we move to Rails 7 within Hyrax 5 work?

      1. Past discussions identified it as Developer Congress work.

      2. May not be able to accomplish in parallel.

      3. Daniel: It needs to come in line with latest version of Rails.

      4. Will Sprockets have Rails 8 support? Unclear.

  4. 8/28 Moderator: Rob Kaufman