2017-03-14 Meeting Agenda and Notes

Owned by Bill Branan
Jun 16, 2017
2 min read

When: 2017-03-14; 12pm ET

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

Moderator: Andrew Myers (WGBH)

Notetaker:

Attendees:

Agenda:

  1. Notetaker†

  2. Review action items†

    1. Write a ticket to propose guidelines for how to handle plugin configuration (Drew)
      1. carry forward
    2. Write a guideline to not do monkey patching.  Suggest if you need to do monkey patching you should refactor the component instead.
      1. https://github.com/projecthydra-labs/hydra_plugins_wg/issues/31
      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
    3. Be on the Hydra tech call on March 22 (everyone)
    4. Start filling out justifications for guidelines in PRs to be done by LDCX (Jenn)
    5. Turn Chris' observations on GA and config into actionable tickets (Chris)
    6. Put the google analytics plugin to the test as a topic for LDCX developers congress. (Drew)
    7. Put time on people's schedule for Thursday and or Friday afternoon for Geo Concerns and or Google analytic 2 hours per. (Drew)
      1. Done
    8. Formulate discussion topic for how to refactor the derivatives pipe line in hyrax & hydra-derivative (is already a topic for LDCX)
    9. Define the scope of the gem in the readme to include 'custom event tracking downloads and then rendering of that in a dashboard'
  3. Development update:
    1. Friday, March 17 @ 3pm - 5pm (CST)
    2. Stay tuned on Slack for link to Google Hangout.
  4. Review Roadmap†
  5. Next Meeting†
    1. When: 2017-21-14; 12pm ET

† - Standing agenda item


Action Items:

  1. Write a ticket to propose guidelines for how to handle plugin configuration (Andrew Myers)
  2. Start filling out justifications for guidelines in PRs to be done by LDCX (Jenn Colt)
  3. Turn Chris' observations on GA and config into actionable tickets (Chris Colvard (Deactivated))
  4. Put the google analytics plugin to the test as a topic for LDCX developers congress. (Andrew Myers)
  5. Come up with user stories (or better yet, actionable tickets) for refactoring derivative generation in Hyrax, that can be organized into a sprint during Hydra Dev Congress.
    1. Andrew Myers, Eliot Jordan, Matthew Barnett, Noah Botimer, Jenn Colt, cam156, Chris Colvard (Deactivated)
    2. When uploading, we need to map the uploaded file (or set of files) to a set of derivative generation processes.
    3. The set of derivative generation processes needs to be able to be configurable (i.e. added to, or removed from) by plugins, and also by the host application.
    4. When downloading derivatives, we need to be able to map a persisted record (in Fedora, Solr, or both) to the location of it's generated derivatives.
  6. Update README in https://github.com/projecthydra-labs/hyrax-google_analytics to define the scope of the gem to include 'custom event tracking downloads and then rendering of that in a dashboard' (Anyone)