2017-02-28 Meeting Agenda and Notes

When: 2017-02-28; 12pm ET

Where: Google Hangouts: https://hangouts.google.com/hangouts/_/event/cd3blc5al8lb5v97fc9a3847id0?hl=en&authuser=1

Moderator: Andrew Myers (WGBH)

Notetaker: Carolyn Cole

Attendees:

Agenda:

  1. Notetaker

  2. Review action items

    1. Write a ticket to propose guidelines for how to handle plugin configuration (Drew)
      1. Not done. Carry forward
    2. Comment on Drew's ticket with hyrax GA concerns (Chris)
      1. Chris Colvard (Deactivated)?
      2. Carried forward
    3. Bring up WG topics on hydra-tech call for inclusion in Hydra Dev Congress agenda (Drew)
      1. Done.
      2. Will not be voted on before the dev congress.  Need to consolidate topics for refactoring to include the plugins group.
        1. Added an agenda item prior to the developers congress to discuss consolidating the ideas.
    4. Update the charter with new sunset date (Carolyn)
      1. Done
    5. Announce via hydra-tech list with new sunset date (Carolyn)
      1. Done
    6. Start filling out justifications for guidelines in PRs to be done by LDCX (Jenn)
      1. Jenn Colt?
    7. Turn Chris' observations on GA and config into actionable tickets
      1. Chris Colvard (Deactivated)? Dupe of action item listed above, or not?
    8. Chris to cc: Kate & Greg re: time to pair up on Google Analytics
      1. Chris Colvard (Deactivated), Kate Lynch, Greg Kostin?
  3. Development update:
    1. GeoConcerns
      1. Started out going through the guidelines an creating tickets when completed the system will satisfy the guidelines
      2. Handling installation failures was started & How the plugin should be configurable.
        1. all tickets have been created and completed
      3. Derivatives pipelines - New integration points for paths
        1. Hyrax needs to allow for mapping a derivative type to a derivative file extension
        2. Need a class to do the mapping and calling you overriding class
          1. method inside a class that returns the class name of the class doing the mapping
            1. only available after you instantiate a FileSet object
            2. It was hard coded on the downloads controller.
            3. Builds the path that you are searching for derivatives
          2. May need to modify Hydra-derivatives to allow for new derivative Generators
          3. May also need to allow for easier configuration of hydra-derivatives
          4. Want a pipeline for derivatives generation that works like handlers
            1. Need to respond to a mime type and do multiple things
            2. Specify as many handlers as you want
            3. Need to be able to add and remove handlers from the plugin.
    2. Google Analytics
  4. Review Roadmap
  5. Next Meeting
    1. When: 2017-03-14; 12pm ET

- Standing agenda item


Action Items:

  1. Write a ticket to propose guidelines for how to handle plugin configuration (Drew)
  2. Write a guideline to not do monkey patching.  Suggest if you need to do monkey patching you should refactor the component instead.
  3. Comment on Drew's ticket with hyrax GA concerns (Chris)
    1. the GA plugin will need to do configuration as it is already using hyrax config
  4. Be on the Hydra tech call on March 22 (everyone)
  5. Start filling out justifications for guidelines in PRs to be done by LDCX (Jenn)
  6. Turn Chris' observations on GA and config into actionable tickets (Chris)
  7. Put the google analytics plugin to the test as a topic for LDCX developers congress. (Drew)
  8. Put time on people's schedule for Thursday and or Friday afternoon for Geo Concerns and or Google analytic 2 hours per. (Drew)
  9. Formulate discussion topic for how to refactor the derivatives pipe line in hyrax & hydra-derivative (is already a topic for LDCX)
  10. Define the scope of the gem in the readme to include 'custom event tracking downloads and then rendering of that in a dashboard'