Child pages
  • Samvera Tech Call 2019-01-30

Versions Compared


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



  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. PSU Dev Sprint (Tom)
    3. add agenda item here
  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 2019-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: 2019
    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: 


Some code sitting between existing Valkyrie/AF which permit casting Valkyrie resources to AF resources

Switch out persistence methodmethods from AF to Valkyrie ones in order

There are PRs which are open now

Some additional PRs might be issued, or there might be some work focused around a Gem which has been the focus of others during the sprint

There are also those who have been increasing the efficiency of the tests

Objective is to merge these PRs on Friday

There will be follow-up sprints, please contact steve van tuyl or Tom Johnson


Link provided from Trey outlining some recommendations for using the Mapper interface

Drew: Is there a concrete scope for this sprint for non-technical stakeholders?

You as a Hyrax adopter will not see an immediate change, but the outcome is that we have next steps which are laid out for sprint groups in the future for moving Hyrax forward

Save call at the bottom of the Actor Stack might shift to a Valkyrie call

Adopters would see that as a straight refactor

If we release a G