January 24, 2018

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

• Daniel Lamb
• Jared Whiklo 🌠
• Seth Shaw
• Jonathan Green
• Rosie LeFaive
• Kim Pham
• Yamil Suarez
• Bryan Brown
• Natkeeran Kanthan

Agenda

1. Google Summer of Code
2. CLAW Lunch and Learn: Feb 23, 12:00-3:00 PM Eastern
3. Recent Activity
   1. https://github.com/Islandora-CLAW/CLAW/issues/777
   2. https://github.com/Islandora-CLAW/CLAW/issues/776
   3. https://github.com/Islandora-CLAW/CLAW/issues/775
   4. https://github.com/Islandora-CLAW/CLAW/issues/736
4. Still needs a tie break: https://github.com/Islandora-CLAW/islandora/pull/71
5. Need a merge https://github.com/Islandora-Devops/claw-playbook/pull/42
6. ... (feel free to add agenda items)

Minutes

1. Spent a couple days doing an application for Google Summer of Code, Google offers stipends to students and tries to lined up with an OSS project. Then the students would make a pitch for the project they might like to contribute to it, but we can also have multiple mentors if others are interested. Information on February 12.

   Danny created a list of possible projects - https://github.com/Islandora-CLAW/CLAW/wiki/Google-Summer-of-Code-Ideas-List

   If you have an idea of a project, then add it to the list so possible students could review the projects.

2. CLAW Lunch and Learn - Kim Pham

   Hosted in person at UTSC 12-1 is in-person lunch and 1-3 updates and talk about the work, Kim talk about what they are starting to work on.

   Information for registering for online and in-person is available here https://goo.gl/forms/4vfqyCFnaDrGEGWr2

3. Recent activity

   • Syn not installed in claw-playbook, Jared will open issue-736 PR and issue-777 PR for ansible-role-fcrepo-syn.
   • Centos order of operation will be selinux, php-repo-remi, webserver-app Drupal & JWT, openseadragon, tomcat 8, grok, then crayfish.
   • Eventually we could serve RPMs for those things we need to compile from source to avoid the lag.

4. Still need a tie-break test to move this along, there is work stacking up that was based off this (ie. https://github.com/Islandora-CLAW/islandora/pull/72) so we need to know if this is a code or configuration issue.

5. Danny live merged this, so 👍 for that.

6. Other business

   A suggestion based on IslandoraCon's HackDoc where Danny was teaching how to create new Content-Types and exporting the configuration into a new module that could be re-used.

   Some of that HackDoc knowledge/experience has been lost and the IR group are interested in having PDFs and CSVs binaries. Could we do a screencast about how to export the configuration files so people could watch them?

   There is this - https://github.com/Islandora-CLAW/CLAW/blob/master/docs/islandora/drupal-bundle-configurations.md

   A little out-of-date but there was also CLAW Porcus - https://github.com/Islandora-Labs/claw_porcus/tree/aee552d3504fab7ae560d2e468856be686c1a408

   We can do this, not sure how quickly it can be done.

   When will the next sprint be?

   Next sprint might be in March, trying to get derivatives done first and with Melissa away Danny has multiple things to work on.

   Focus could be on metadata and the tools we might need to develop around it.

   Metadata Interest Group is interested in this too. The community has settled around Bibframe because it seems to be the most generic and fits the general library models.

   • Example data - https://github.com/Islandora-Labs/claw_porcus/tree/aee552d3504fab7ae560d2e468856be686c1a408
   • Context module allows us to swap out view modes and edit modes based on user permissions.
   • How are the blank nodes going to end up looking. Individual statements.
   • LOC has a Bibframe editor - http://bibframe.org/tools/editor/#

   Bibframes use of blank nodes could eventually be a performance problem as we will have a bunch of fields and no one really knows how many fields are too many.