Child pages
  • Hydra Tech Call 2016-11-30
Skip to end of metadata
Go to start of metadata

Time: 9:00am PDT / Noon EDT

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

Moderator: Michael J. Giarlo

Notetaker: Thomas Scherz

Attendees:

Agenda

  1. Roll call by timezone per following order - ensure notetaker is present
    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
  2. Call for additional agenda items (moderator)
  3. Gem releases
    1. hydra-works (Cowles)  - Update is coming and this will include multiple dependencies.  So if you have any work you are thinking of merging in, now is the time.
  4. Check-in on large PRs requiring review (moderator)
    1. Reverse Collection membership (Cowles) - Depends on the next hydra-works.  Seeking someone to cut the hydra-works release.
  5. Soliciting review/comment on Sufia/CurationConcerns Consolidation Plan (Giarlo)
    1. Background - Document created by the  Architecture Working Group (Stroop and Giarlo) includes proposed Timeline and FAQs.
    2. Drop comments or reviews here.
      1. What does it means for the current gems?  (sufia and curation_concerns)  They will remain available for many months, at least, for a few more versions to be released and for current work to be wrapped up.
      2. What is the relationship with the Plugin Working Group?  - Looking to partnership on patterns of abstractions and geo-concerns integrations.
    3. Timeline begins now.
    4. Focus is now on pulling Sufia and CC together in the same branch currently living in the cc_subtree branch of Sufia. As soon as the codebases are consolidated, the work will move into the new Hyrax GitHub repo in the -labs organization, and the branch will be deleted in Sufia.
  6. Order in multi-valued metadata fields (Anna Headley)
    1. Major areas - Communicating with users.  Have you ever had to explain to users about ordering of meta-data fields?  Expectations around order meta-data fields?  
    2. UM had to deal with it related with Author ordering by separating them out into separate fields 
    3. UCSD had to introduce a formatted citation that was hand edited around the Author field.
    4. PSU is getting by a little longer by delaying going to RDF 2.0.  Still running into problems on import and migration.
    5. Esme discovered similar limited/odd ordering behaviors in Fedora 4.6 and 4.7.  It is his observation that this did change in Fedora. 
  7. Moderator/notetaker for next time: 
    1. Moderator: Adam Wead
    2. Notetaker: Colin Gross