Hydra Tech Call 2017-03-01

Owned by Bill Branan
Jun 16, 2017

Time: 9:00am PDT / Noon EDT

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

Moderator:  Andrew Myers

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. Updates on last week's items
  4. Display Sets update – Requirements - Admin Sets vs. Display Sets vs. User Collections, List of required mockups for Collections, call for members for Collection Extensions UI/UX Design Working Group ( Lynette Rayle)

    1. Working group will continue discussing fine points.

    2. Asking for community review of above documents.  

    3. Call for members to join the next iteration of the UX recommendation process.

  5. Questioning Authority - linked data implementation (https://github.com/projecthydra-labs/questioning_authority/tree/linked_data_refactor) ( Lynette Rayle)
    1. Lynette completed a refactor of the linked data implementation in QA.  
    2. The refactor includes configurability specifications and class encapsulation.
    3. Posting to Hydra Tech
  6. (STANDING) Update on Sufia/CurationConcerns Consolidation Plan ( justin or Michael Joseph Giarlo)
    1. Moving forward to mint Sufia 7.3 to mint Hyrax 1.0.
    2. Might need to start thinking about documentation for migration.
  7. (STANDING) Sufia 7.3 Blockers ( Thomas Scherz, or Glen Horton)
    1. Josh Gum has a PR in on CC that will complete the final Sufia 7.3rc2 blocker.
    2. Looking to mint Sufia 7.3rc2 this week
  8. Updating RDF type on ActiveFedora::Base resources ( Adam Wead)
    1. AF issue: https://github.com/projecthydra/active_fedora/issues/1165
    2. affects PCDM use extension (https://github.com/duraspace/pcdm/blob/master/pcdm-ext/use.rdf) where you want to add or change types to a resource to identify its particular use.

    3. Making easier for Hydra:Work to edit RDF type after creation.

    4. Are there certain rdf:type values that we should not allow updating/removing?

    5. Should we allow changing the RDF:Type after creation?

    6. Next steps:  Explore how deep the problem is.  Maybe include tamsin johnson in the conversation.
  9. Cancelling next weeks Hydra Tech call due to Code4Lib attendance.
  10. Moderator/notetaker for next time:
    1. Moderator:   justin
    2. Notetaker:  cam156