Versions Compared

Key

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

...

  1. Notetaker and moderator for next time
    1. Notes: Steve Van Tuyl
    2. Moderator: Steven Ng

2b. Update on Hyrax 2.0.0 release timeline (Michael J. Giarlo)

  • 2.0.0beta4 released
  • testing with nurax, repo managers group
  • release imminent

2c. "Hyralkyrizing Valkyrax is Samverific!" – Announcing plan for Hyrax/Valkyrie sprints (Michael J. Giarlo)

  • team assembled to build support in Valyrie that Hyrax would need
  • begins October 9th; 4 week sprint (non-consecutive)
  • ending week after connect
  • 5 institutions: indiana, oregon, stanford, princeton (and one more I missed)
  • targeting hyrax 3 ... next year

2d. Deprecate Namespacing (redis-namespace)? (Tom Johnson)

as per Tom's description

q. PR leaves the behavior but deprecates the config; more work needed on the branch - agreed

2e. Admin set to work relationship (Lynette Rayle) REF: #1461

  • read the issue ^^
  • impacts on collections proposal to make admin sets just another collection
  • proposing pcdm:memberOf
  • issue with this approach is that it makes retrieving just the admin set more difficult
  • Tom - reluctant to change the filtering, changing predicate a simpler fix
  • Lynette will do some more research

2f. Admin Sets vs. Collections use of participants has some inconsistencies (Lynette Rayle) REF: Impact of Participants on admin_set/collection and works

  • inconsistency is fine for now but flat it to revisit later if we move forward with making admin sets a type of collection

2g. QA 2.0 adds support for Rails 5.1 and drops support of Rails 4.2. Release now with no other updates or in a few weeks significant updates to linked data processing? (Lynette Rayle)

  • release now and then another release later
  • linked data work should not be backwards incompatible

2h. Updating browse-everything to Box API v2 (Michael B. Klein)

  • upgrading BE because box api v2 is much better, should not break anything