Hydra Tech Call 2016-08-17
Time: 9:00am PDT / Noon EDT
Call-In Info: 1-641-715-3660, access code 651025
Moderator: @Steven Ng
Notetaker: @Jeremy Friesen
Attendees
@Esmé Cowles (Princeton)
@Steven Ng (Temple)
@Michael Joseph Giarlo (Stanford)
@tamsin woo (DPLA)
@cam156 (Penn State)
@Lakeisha Robinson (Yale)
@Anna Headley (CHF)
John Cline (Yale)
@Jeremy Friesen (Notre Dame)
Jennifer and Adam (Cornell)
@Jennifer Lindner (Independent)
@Trey Pendragon (Princeton)
Benjamin Armintor (Columbia)
Agenda
Roll call by timezone per following order (moderator)
folks outside North and South America
Eastern timezone
Central timezone
Mountain timezone
Pacific timezone
folks who were missed or who dialed in during roll call
Call for additional agenda items (moderator)
Reversing Collection membership to improve performance (again) (Esmé)
As discussed last week, linking from Objects to the Collections they are members of (using pcdm:memberOf) is much faster when the Collections have many members.
Unlike last week, Princeton is interested in moving forward with this change sooner rather than later in order to be able to begin ingesting data.
PR for discussion: https://github.com/projecthydra/curation_concerns/pull/901
Includes UI polish
Additional local changes
Princeton does Intend to use this branch in the Short Term if Hydra Community does not move forward
As written this requires a migration of data to reverse the directions
Princeton is proposing User Collections are part of blacklight favorites; The pull request addresses a "Library" Collection.
Conjecture that it will be faster linking from Object to Collection; There is no assumption that Princeton might reverse this
Cornell feels that having both directions is a good option
Esmé will be leveraging this pull request and experimenting with it
The underlying issue is being worked through in the Hydra Architecture Working Group
RDF.rb Ruby Version support (Tom)
rdf v2.1.0 drops Ruby 2.0 and 2.1 support (>= 2.2.2).
Plans for rdf v2.0.x maintenance
There are short term maintenance plans for Ruby 2.0 and Ruby 2.1 on prior branches.
Moderator/notetaker for next time:
Moderator: @Jeremy Friesen
Notetaker: @cam156