Samvera Tech Call 2017-12-13

How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

Time: 9:00am PDT / Noon EDT

Moderator: @justin

Notetaker: @Steve Van Tuyl

Attendees:

• @Michael Joseph Giarlo (Stanford)

• @Jim Coble (Duke)

• @James Griffin (Princeton University Library)

• @Steve Van Tuyl (oregon state university)

• @gregorio.luisramirez (oregon state university)

• @LaRita Robinson (Notre Dame)

• @cam156 (Penn State) 

• @Steven Ng (Temple)

• @Lynette Rayle (Cornell)

• @Brendan Quinn (Northwestern)

• @Chris Colvard (Deactivated) (Indiana University)

• add yourself here

Agenda

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. Welcome all newcomers!

2. Agenda (moderator)

   1. Call for new agenda items (moderator)

   2. active_fedora-noid is now noid-rails (@justin)

      1. https://github.com/samvera/noid-rails/pull/78

   3. versions for Valkyrie (@justin)

      1. https://github.com/samvera-labs/valkyrie/pull/312

   4. migration process for Collection Extensions - single process to migrate all collections (@Steve Van Tuyl, @Michael Joseph Giarlo, @Lynette Rayle)

      1. https://github.com/samvera/hyrax/issues/1596 - Migration Steps

   5. add agenda item here

3. Notetaker and moderator for next time

   1. Notes: @LaRita Robinson

   2. Moderate: @Steve Van Tuyl

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

Notes

1. active_fedora-noid is now noid-rails (@justin) - https://github.com/samvera/noid-rails/pull/78

   1. valkyrie sprints sorta forced this to be a thing

   2. next version of AF Noid will now be called Noid-Rails

   3. Shouldn't be any noticeable impact

2. versions for Valkyrie (@justin) - https://github.com/samvera-labs/valkyrie/pull/312

   1. spooky silence

   2. Proposal in that PR is for an api for versioning

   3. Comments:

      1. confusion: it seems like versioning is happening automatically if you upload a file to the storage adaptor with the same file name and attaching resource

         1. response: @justin agrees, this is whats happening - similar to git protocol

         2. concern that this may version when people don't want it to - @Trey Pendragon will leave some feedback

      2. go over some new issues in the repo - not sure taking notes on this makes a huge amount of sense... important things will be captured in valkyrie issues in github

3. migration process for Collection Extensions - single process to migrate all collections (@Steve Van Tuyl, @Michael Joseph Giarlo, @Lynette Rayle

   1. Process has been solidifying and have been testing it on Nurax

   2. Working on lazy migration but had concerns about performance and finding all the things that would need to be touched

   3. Plan at this point is to provide a small script that will update all of the collections

   4. Process:

      1. update gem

      2. db-migrate

      3. rake task to create new collection types

      4. additional script to update collections (run once when updating the code)

   5. @Lynette Rayle is updating instructions now

   6. Q: is it necessary to add collection types to permission templates

      1. A: there are a number of places where source type is used

      2. logic in the permission templates controller allows you to determine what the collection type is

      3. Valkyrie work may conflict, in a way, that suggests a need for a closer look at this approach

      4. @Lynette Rayle and @justin will discuss offline and come to a joint solution