Hydra Tech Call 2017-03-15

Owned by Bill Branan
Jun 16, 2017
3 min read

Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025 (or https://www.freeconferencecallhd.com/wp-content/themes/responsive/webrtc/webrtc.php?a=651025&n=6417153660&u=yournamehere)

Moderator:  justin (Stanford)

Notetaker:  cam156 (Penn State)

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. Do not show share tab if workflow disallows access grants ( justin)
    1. These are blockers for 7.3
    2. See https://github.com/projecthydra/sufia/pull/3138
      1. Do not allow access grants - Supress the tag
      2. Needs a reviewer
  5. Add child/parent work in Sufia master ( justin)
    1. See https://github.com/projecthydra/sufia/pull/3147
    2. Ajax request are breaking the optimistic locking
      1. submit everything on the same form
      2. Add this work to parent work - Could take a long time and was not locking
        1. remove the widget to add this work to a parent 
          1. got to the parent and add this children from there
        2. From the user stand point it makes sense to do it from the parent and the child, but in the short term let us disable it
        3. Schedule a talk during LDCX
    3. needs an approver
  6. (STANDING) Sufia 7.3 Blockers ( Thomas Scherz or  Glen Horton)
    1. There are now PRs in for all remaining blockers
    2. Need to merge the blocking PR
    3. Will release priori to LDCX bugs will be fixed in 7.3.1
  7. (STANDING) Update on Sufia/CurationConcerns Consolidation Plan ( justin or Michael Joseph Giarlo)
    1. Focus is on getting the Sufia 7.3.0 release out, at which point the focus will be on the Hyrax 1.0.0 release, so work can begin on the CC to Hyrax 2.0.0 path.
    2. Once 7.3.0 is cut then Hyrax 1.0 will be cut which is blocking some PR
    3. Work on CC and Hyrax upgrade path, thanks to Princeton
    4. Bugs from 7.3.0 will not get any push after there is an upgrade to hyrax
    5. How well defined it the process from Sufia 7.3.0 to Hyrax 1.0.0
      1. Pulm was upgraded from Curation Concerns - Added to the upgrade pathHyku was upgraded from Sufia 7 - Started documenting the upgrade path
  8. Display Sets update – Display Sets Requirements and Milestones (Lynette)
    1. documentation has been reworked to include milestones (still in progress)
    2. Like reviewers on Section Use Case milestone requirements - Are these the requirements and do they make sense for me?  Which milestones are required for your use? 
    3. Includes User Collections.
    4. being worked on by the Display Set working group -  Display Sets Working Group
  9. Validating pcdm:use of Files within FileSets (from FileSets Working Group) ( Andrew Myers)
    1. want to be able to set the use tag on files in a Fileset instead of the current hard coded set.
    2. How feasible is it to validate cardinality and optional/required of pcdm:use of Files within FileSet
      1. Having a required PCDM use (original_file) May have only one
      2. May have intermediate file (possibly more that one)
    3. Where would the validation go?  Looked at ActiveFedora for works but there is validation up and down the stack
      1. ActiveFedora should not have idea of PCDM
      2. No concrete example in ActiveFedora
      3. Need the ability to put the configuration reader somewhere that may be defined in the host application
      4. Put it in the Gem that affects the least amount of people.  Possibly put it in a hydra-pcdm or hydra-works
    4. Where should they go? ActiveFedora? Hydra-PCDM? Hydra-Works? Hyrax? Host application?
      1. What interface should they subscribe to?  What is the best pattern for validation?
        1. validate against PCDM rules in a config file
      2. AF validation rules are set up for association (validate!)
      3. For object validators use ActiveModel pattern (part of the bitstream of a file)
      4. Hydra:pcdm:File has no concept of metadata
      5. How do we validate the entire fileset after all the processing is done?
      6. Would not be the last step on the actor stack since you could get in a bad state
        1. we do not currently use transactions
        2. Object will need to know if they are valid or not and save them anyway
      7. Could push the validation to the UI to keep the user from sending data
        1. generally the form objects have validators so this makes sense
  10. Moderator/notetaker for next time:
    1. Moderator:  Steve Van Tuyl
    2. Notetaker:  pbinkley