Samvera Tech Call 2017-08-30

Owned by cam156
Last updated: Aug 30, 2017 by Lynette Rayle
2 min read

Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025

Moderator: Anna Headley

Notetaker: Michael Joseph Giarlo

Attendees:

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
    2. Hyrax 2.0.0 Release (Steve Van Tuyl)
      1. Michael Joseph Giarlo and Steve Van Tuyl have spent some time reviewing bug issues and Milestone 2.0 issues for Hyrax
        1. See the delightful issue evaluation spreadsheet
      2. It appears we may be ready for Hyrax 2.0 beta release...
      3. Path to include collections extensions in Hyrax 2.0 (Lynette Rayle)
        1. See the Plan to merge to master drafted by Lynette Rayle
        2. The above document details a number of potential merge points, and Lynette Rayle suggests merging at least the infrastructure piece back into master before cutting the beta1 release.
        3. If we merge the Collection Extensions work into master for the 2.0.0 series, will that complicate the upgrade path from CurationConcerns? Explored on the mailing lists and turned up no evidence of this.
        4. Time-sensitive points:
          1. Data Curation Experts would like the beta release cut soon, partly to get a client on the right footing and partly to use a stable release for Samvera Camp next week
          2. Collection Extensions folks would like their (sizable) feature branch merged sooner rather than later so it doesn't unnecessarily complicate the merge
        5. There is a shared sentiment that we not merge the Collection Extensions work into master until it is a coherent feature (which conflicts with the "just merge the infrastructure stuff in now, and do the rest later" idea)
        6. There are differing opinions on whether it is acceptable to merge the Collection Extensions work (a sizable feature) between the 2.0.0.beta1 and 2.0.0 final releases
        7. The "breaking change" in this Collection Extensions work is a change in database tables – easily dealt with via `rails db:migrate`
    3. Reversing the collection→collection relationship in hydra-pcdm (Chris Colvard (Deactivated) and Lynette Rayle)
      1. For the Collection Extensions community sprint
      2. https://github.com/samvera/hydra-pcdm/issues/243
      3. https://github.com/samvera/hydra-pcdm/pull/244
      4. This work allows inverting the relationship between collections, but does not require it. We will defer discussion of what we want the default behavior to be in Hyrax.
      5. Do folks have a use case for subcollections with hundreds of parents? Apparently not, at least among folks on the call.
    4. Feature tests always pass with have_content('GARBAGE_GARBAGE)  (Lynette Rayle)
      1. See #1592
      2. May also be playing a role in the flappy feature specs in Hyrax
  3. Moderator/notetaker for next time (moderator)
    1. Moderator: Jim Coble
    2. Notetaker: Esmé Cowles
  4. After call, this week's notetaker should create the agenda for the next call.

Notes