Hydra Tech Call 2016-04-13

Owned by Bill Branan
Jun 16, 2017
2 min read

Time: 9:00am PDT / Noon EDT

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

Moderator: Adam Wead

Notetaker:  Hector Correa

Attendees:

Lynette Rayle (Cornell)

Lakeisha Robinson (Yale)

cam156 (PSU)

Mark Bussey (DCE)

newmanld (Cincinnati)

Andrew Myers (WGBH)

(missed the name, sorry) (Virginia Tech)

Esmé Cowles (Princeton)

pbinkley (Alberta)

Michael Joseph Giarlo (Stanford)

Agenda:

  1. Call for additional agenda items
    1. none
  2. How should we prioritizing refactoring efforts? ( Andrew Myers)
    1. Topic discussed at LDCX around the opacity of the stack for new developers
    2. How can we make it clearer for new comers?
    3. The recent refactoring efforts done to merge Hydra Collections into Curation Concerns are a good example of what Andrew is talking about. Refactoring to make the code better/simpler without adding new functionality.
    4. Andrew asked if there are other candidate pieces of functionality to refactor. Nothing is slated for refactoring as of today.
    5. Mike and Esme agree that something should be done.
    6. Mike talked about the difficulty of achieving architectural correctness and developing a stack that we as a community can sustain.
    7. Andrew talked about the "intentional lack of architectural leadership" on the stack.
    8. The consensus was to try to schedule refactoring sessions at community events where a larger group of people can sit down and work together on refactoring pieces of functionality.
    9. Andrew will pitch refactoring sessions in the upcoming Hydra Developer Congress at Michigan  May 2016 Developer Congress Meeting Agenda
  3. Collection Survey follow-on points and streams of work ( Lynette Rayle)
    1. Lynette talked about the results of the Collections Survey https://groups.google.com/forum/#!topic/hydra-tech/uMIZWUHVoh8
    2. Four major themes: Discovery, Visibility, Sharing, and Types (types are the less well defined)
    3.  Collections are challenging because it's hard to decide what to inherit into works when works belong to more than one collection
    4. Mike and Lynette will discuss if there are any overlaps in the requirements of Collections for HyBox and the results of the survey
    5. Lynette pointed out that she named "policy collections" rather than "admin sets" because the later has different meanings to different people.
    6. There was consensus in the meeting that "policy sets" is a better name since it reflects the intention. Lynette will run this by the large community.
    7. The idea is that a work would be able to belong to a single "policy set" and that would prevent the issues inheriting from multiple collections.
    8. Linda agreed that the concepts discussed by Lynette are solid. She is mentioned that the next challenge would be to come up with a user interface that is clear to our users.
    9. There was a questions about the work that was done recently to merge Hydra Collections into CurationConcerns and a bit of new functionality that was added to them in the process. The new functionality matches with what Lynette was looking for.  

Next Call

  1. Date/Time: 2016-04-20 9:00am PDT / Noon EDT
  2. Moderator:  Andrew Myers
  3. Notetaker:  pbinkley