Samvera Tech Call 2026-04-08

Samvera Community Wiki


Samvera Tech Call 2026-04-08


Meeting Logistics

  • Time: 9:00am PT / Noon ET

  • Zoom Meeting URL: https://iu.zoom.us/j/87635137325?pwd=YhVGftEpANzAwgk84swAyF53edj31x.1
    (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

  • Moderator: Daniel Pierce

  • Notetaker: LaRita Robinson

Agenda Items

(Meeting notes below)

 

Attendees

  • @LaRita Robinson

  • @Heather Greer Klein

  • @Tracy McCormick

  • @Sarah Proctor

  • @Daniel Pierce

  • @Bradley Watson

  • @Randy Kuehn

  • @Mark Bussey

  • @Rob Kaufman

  • @Nicholas Mark Homenda

  • @Heather Greer Klein

  • @Chris Colvard

  • @Randall Floyd

  • @Nic Don Stanton-Roark


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 XXXX-XX-XX"

      2. Click on ... in the top right corner, and select Make a copy.

      3. Popup will open for location. It should contain:

        1. Space: Samvera

        2. Parent page: (Verify value is current year)

      4. Select Make a 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.

      6. Click Publish


Meeting Notes

  1. Tracy: question on how Hyrax/Hyku can handle estimated dates in EDTF format. Rob said we store as text and do not normalize. Chris said they use edtf and edtf-humanize gem (in avalon) to make it readable. He can share more info which Tracy can pass along to Jessica. Rob said may be a welcome addition and questioned whether should be a hyrax or a hyku feature. Chris and Mark affirmed that it should be in Hyrax. Rob noted that getting closer to avalon is also a plus. Mark added that the humanize gem still requires normalization of the data to ensure edtf format. Tracy wonders how to deal with bulk ingestion… Mark added that it wouldn’t handle it,and they would still need to parse the data ahead of time.

  2. Rob: analytics discussion - issues regarding complexity & setup. Causing people problems. Had an interesting discussion with notch8 Nick around the 4 kinds of analytics: Usage of works - covered by hyrax. Aggregate - views for tenant, across multi tenancy. Usage of features. Usage across platform… what versions of various gems. Is there appetite to add additional provider (possibly new default)… Ahoy, natively private to repository, part of rails, etc. This would help ease setup significantly. Asking if anyone has experience or opinions. Daniel has heard of it and does not like the setup required with google analytics.. how to wire into the above 4.
    Rob said first two shouldn’t be too difficult with an adapter. Third is where Ahoy has a big advantage & could simplify this a lot. Last is the hard one (anonymized phone home statistics). Likely need to punt on item 4 and may need a separate solution. No objections, so Rob will pursue technical feasibility.

  3. Daniel: follow up on Hyrax 7405… GW doing test imports w/ Fedora 6 & performance problems. Dolcy tracked down to a malformed URI being used in requests that ends up doing root node request & returning too much in rdf gem. Daniel tracked it down to an ACL optimization. In that state it doesn’t have a proper identifier (needed to find object again fresh). Quick fix is to get rid of the optimization but needs a lower level investigation into Valkyrie. Rob wonders whether to modify the memoization would handle it… he will look into the change and try to see whether code comment gives any additional details. May have been a premature optimization… will try to figure this out. Daniel: Ideally should figure out where in RDF or valkyrie etc it isn’t getting processed the same as a fresh load. Maybe reach out to Trey.

  4. PR's - none noted?

  5. Chris: circle CI update… Heather got open source designation back on so we should not run out of credits and builds should be ok now.

  6. Moderator next week: @Rob Kaufman

  7. Notetaker next week: @Nicholas Mark Homenda