Versions Compared

Old Version 3

changes.mady.by.user Ben Pennell

Saved on

compared with

New Version Current

changes.mady.by.user Jeremy Friesen

Saved on

Key

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

...

...

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)

  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. Identify cause of sudden loss of ability to run fits.sh; there’s an old issue filed on Sidekiq regarding the $PATH getting overwritten. Somewhere there’s non-thread safe code that’s overwriting the environment. Once that blanking out happens, the fits.sh will fail. A work around is to hard-code the path to fits; but that doesn’t address other issues.

  2. Question regarding Matomo: See Slack thread. Some parts work of Matomo, but there are definitely a majority of failures. Without caching there are distinct performance issues regarding loading pages (30 seconds for initial page, 2 or so minutes for other pages).

    1. The caching was likely unintentionally dropped; it does make sense to cache things locally. The big push on the analytics PR likely did not work off of a large dataset, so there was no performance issues.

    2. There is need for overhauling the analytics dashboard.

    3. These concerns are something to bring up with Repository Managers.

  3. Usage of Matomo: seeing issues with the file analytics page; is only loading cached stuff (that is no events are being added when you switch over to Matomo); what is the intent of support with Matomo.

    1. There’s a need to discern what is the intent of the analytics; Rebekah Kati is looking at bringing this up to the Repository Managers.