December 9, 2015

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join. Here is the info:

• Time: 1:00pm Eastern Daylight Time US (UTC-4)
• Dial-in Number: (641) 715-3570
  • Participant Code: 304589#
  • International numbers: Conference Call Information
  • Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  • Join the #islandora chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #islandora on irc.freenode.net

Attendees

• Nick Ruest
• Melissa Anez
• Jared Whiklo
• Diego Pino
• Mark Cooper
• Kim Pham
• Sunny Lee
• Nigel Banks ⭐

Agenda

1. Sprint updates
2. Drupal 8 Prospectus
3. Better replication techniques for Fedora / Drupal synchronization
4. ...feel free to add...

Minutes

• Sprint Update
  • Focused on Services API
  • Monday / Tuesday were used to discuss and create issues.
  • Danny created a example of a Transaction Service API we can work from.
• Sprint Questions
  • Diego - Transactions shouldn't return a new instance of Chullo for each function call. Lines 18-20 in the pull request. Everyone says cool.
  • Jared - Where should we setup silex? In Drupal as a Library? Somewhere else? Putting it inside of Drupal would require a wrapper so folks settled on having a separate virtual host configured in Apache.
  • Kim Pham - Will we be able to reuse code from Solution Packs? Likely not much other, then the lessons learned from previous work, along with some small portions of logic around derivatives.
• Drupal 8 Prospectus
  • Nick is working on the Drupal 8 prospectus and has made the document available for everyone so others can contribute. The goal is to have it ready for next week sometime.
• Replication / Sync Ideas
  • Diego - is looking for more input on his thoughts here: https://github.com/Islandora-CLAW/CLAW/issues/121
  • Everyone agrees more research is needed.
  • Nick / Jared - Perhaps we should build a test framework first before exploring algorithms so we can verify if potential algorithms work correctly.
    • Nick is a member of the performance group for F4, suggests we might be able to take advantage of some of the work being done here https://wiki.duraspace.org/display/FF/2015-11-30+Performance+-+Scale+Meeting, it's mostly jmeter work, so we could fork the repo and add concurrent requests to Drupal as well to attempt to break the sync system
    • Might need for funding for testing in Amazon, maybe just a few hundred dollars not much.
• Feature Ideas
  • Adopt Archivematica's Format Policy Registry
    • Might work like this: Drupal node with file -> File characterization service (something like FITS) -> PRONOM ID -> Informs the POLICY Registry about what to do -> Registry gives back unix commands that generate the derivative -> commands get passed on to a service that executes them -> generated file is added to node in Drupal.
    • Chaining Format Policy Registries?
    • Example command: https://fpr.archivematica.org/fpr/api/v2/fp-command/1628571b-c2cd-4822-afdb-53561400c7c4/?format=json