Hydra Tech Call 2015-08-05

Owned by Bill Branan
Jun 16, 2017
2 min read

Time: 9:00am PDT / Noon EDT

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

Moderator: Trey Terrell

Notetaker: Mike Giarlo

Attendees: 

  • Trey Terrell (Oregon State)
  • Mike Giarlo (Penn State)
  • Steven Ng (Temple)
  • Esme Cowles (UCSD)
  • Colin Gross (Michigan)
  • Drew Myers (WGBH)
  • Collin Brittle (Virginia Tech)
  • Carolyn Cole (Penn State)
  • Adam Wead (Penn State)
  • Corey Harper (NYU)
  • Chris Colvard (Indiana)
  • Peter Binkley (Alberta)
  • Julie Hardesty (Indiana)
  • Nikitas Tampakis (Princeton)

Agenda:

  1. Call for agenda items
    1. No new items
  2. PCDM hasRelatedFile
    1. Topic was framed and discussed on the hydra-tech list
    2. Desiderata
      1. The related file should go away when the file to which it's related is removed.
      2. The solution should be implementable in Fedora in relatively short order.
      3. The model shouldn't smell bad.
    3. Options
      1. Do not change the model.
        1. Variant: use iana:describes/describedBy to link related files to other files (recommendation from Hydra Metadata Working Group)
        2. This is the only option that satisfies the cascading deletion requirement automatically.
        3. hasRelatedFile feels like a modeling shortcut. Relationship is unspecified and indirect (through the parent object).
      2. Create a pcdm:Object to represent the "related file." This object is a child of the object containing the file to which it's related.
        1. This can cause related files to get orphaned (depends on application logic).
        2. Lots of nesting (complexity).
      3. Nested files.
        1. Parent object would have a direct container to hold related files.
        2. File can use iana:describes or powder:describes in its technical metadata to relate to the related file.
          1. Is this blurring the line between technical and descriptive metadata?
          2. If so, how much do we care about that in the context of finding a consensus solution to related files?
        3. Ticket already in place to make cascading deletions work in this scenario.
        4. Makes LDP Link headers important which introduces some complexity.
        5. ACTION: Esme will try to dig up a picture to help folks visualize this option (DONE)
    4. Consensus: the group on the call had a clear favorite in option iii.
      1. This was also preferred by the group that gathered in Portland in February, but at the time it was thought that Fedora would not allow the implementation. Since then, our understanding has changed.
      2. This needs more discussion since many PCDM stakeholders were not present on the call. See 2e!
    5. ACTION: Mike will send notes to Hydra, Fedora, and Islandora communities to continue the discussion. (DONE, sent to hydra-tech, fedora-tech, and islandora-dev earlier today)

  3. Next call

    1. Date: August 19, 2015
    2. Moderator: Carolyn Cole (Penn State)
    3. Notetaker: Nikitas Tampakis (Princeton)