Hydra Tech Call 2014-10-15

Owned by Bill Branan
Jun 16, 2017
3 min read

Date: 2014-10-15

Time: 8:30am PDT / 11:30am EDT

Call-In Info: 1-530-881-1400, access code 651025

Moderator: Adam Wead

Notetaker:  Matt Critchlow

Attendees:

       Patrick Feeley (Case Western)

       Thomas Scherz (University of Cincinnati)

       Glen Horton (University of Cincinnati)

Trey Terrell (Oregon State)

Tom Johnson (DPLA)

Mike Giarlo (PSU)

Adam Wead (PSU)

Hector Corea (PSU)

Esme Cowles (UCSD)

Matt Critchlow (UCSD)

Jim Coble (Duke)

Carolyn Cole (Penn State)

Jeremy Friesen (Notre Dame)

Joe Atzberger (Stanford)

Peter Binkley (University of Alberta)

Sharon Farnel (University of Alberta)


Agenda:

  1. Call for Agenda Items
  2. Reminder:  Hydra Developers - Making Progress Fall 2014
  3. Call for Hydra::Works Use Cases https://github.com/projecthydra-labs/hydra-works/blob/master/CONTRIBUTING.md#use-cases
    1. Use Case synthesis will begin 2014-10-22
      1. Winnowing out use cases (discussion will need to happen and documentation for deferred/rejected use cases)
      2. Following due date: Will migrate all use cases into Hydra Wiki
    2. Joe Atzberger reviewing existing published cases at Stanford
    3. Critchlow, Matthew reviewed use cases at UCSD, will have final use cases soon
    4. Use Case contributions from folks without iCLAs https://github.com/projecthydra-labs/hydra-works/issues/21 (Matt)
      1. Mike – Use Cases should live on the Wiki anyway
      2. Esme – Put them in Github issues is fine too, then they can be distributed into repo and/or Wiki
      3. For now: Either Github Issue or Hydra Wiki is fine
  4. Followup from Hydra Tech Call 2014-10-08
    1. How to Have Architectural Conversations (Jeremy)
      1. DataMapper pattern noted in Hydra Tech post.  Jeremy Friesen exploring and creating a straw-dog for review at PDX hackfest
      2. GH Issues pace of discussion is very positive
    2. Access Controls - Put this on the agenda for next week. Can't drag out too long because it's needed for the PSU beta pilot. 
      1. Overview of the proposed solutions - Which one of these should we pick? Rob, Esmé and David are working on use cases and examples.
        1. http://www.w3.org/wiki/WebAccessControl- Model that the w3c is working on, but it's not a standard.
          1. See: https://docs.google.com/document/d/1pLcfruVy594ydtfL5G_Ony8oN6JeEKhtAWr5a6pE6Vg
        2. vs. new predicates on repository objects- Simpler model proposed for UCSD.
      2. Updates: 
        1. Rob and David have created examples of WAC implementation. Esme has examples in his gist.
        2. Former user (Deleted) has reservations on WAC. Do others?
        3. justin is implementing Hydra Access Controls using WAC model and is close to an implementation. Uses RDF. Will post when ready for comment/review
          1. Enforcement is in Hydra, not in Fedora
        4. Former user (Deleted) - Fedora 4.x could have updated Roles module to enforce access control at the repository level.
        5. Former user (Deleted) - On Fedora call tomorrow. Will bring up issue and solicit opinions and engagement
    3. ActiveFedora update for using ActiveTriples 0.3.0
      1. tamsin woo - branch in place https://github.com/no-reply/active_fedora/tree/object-resource-refactor
        1. Current blocker is Identifiable. Hopes to get to it soon to resolve so AT doesn't leave behind AF
          1. Treating AF base objects as graphs
        2. Getting AT-related gems in on the DPLA side at the moment
      2. justin would be OK if AF7 uses 0.2, wants AF8 to be on master of AT 0.3+
      3. Jeremy Friesen - Are we shutting down feature upgrades/development for AF7?
        1. justin - No, anyone can work on it. Hydra stack is motivated on who wants to work on it.
        2. Adam Wead - Majority of work is on AF8, but be aware if you make updates to AF7 you may be encourage to port to AF8
        3. tamsin woo - If folks are concerned about AF7's future, should organize and discuss as a group. What do we want to have happen with it?
        4. Action Item: Jeremy Friesen will move this discussion to the Hydra-Tech, Hydra-Community, Hydra-Partners lists for further discussion
    4. New version of hydra-jetty containing https://github.com/fcrepo4/fcrepo4/pull/496
      1. Former user (Deleted) - the branch cbeer was working on is merged into master
      2. Adam Wead - will create new version based on master
      3. There is a hydra-jetty with Fedora3 and 4 if folks want to test their migrations

  5. RDF

    1. Rights/Works discussion are everything in the RDF context at the moment
    2. Still standing item going forward? Group: Yes, at bottom of agenda

  6. ActiveFedora and Fedora4 - where are we? (awead)

    1. PSU: moving forward with F4 migration at end of year. Requires AF compatibility. Sprint scheduled with DCE soon to finalize AF updates needed
      1. Hope to have a RC of AF8 to support F4 integration
      2. https://github.com/projecthydra/active_fedora/milestones/Fedora%204 (Review and provide feedback)
      3. tamsin woo - Communication on timeline of Sprint(s) would be very helpful for folks to participate. DPLA has interest in AF8+ looking as much like LDP as possible. Might have resources to support this Fall.
      4. Adam Wead - Will send email with communication details for Sprints to Hydra Tech/Community/Partners
  7. Next call: October 22
    1. Moderator:  Carolyn Cole
    2. Notetaker:  Thomas Scherz