May 23, 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

• Yamil Suarez
• Rosie LeFaive
• Paul Pound
• Jared Whiklo 🌟
• Danny Lamb
• Seth Shaw
• Andrija Sagic
• Minnie Rangel

Agenda

1. Features MAYHEM: https://github.com/Islandora-CLAW/islandora/pull/86
2. What do we need for CENTOS support?
3. ... (feel free to add agenda items)

Minutes

1. Crazy set of pulls to separate out into two sets of features. Tried to document it and it seemed to lock us in a bad way. So Danny took all the configuration from all the pulls and created the islandora_core_feature (which you must have) and the islandora_demo_feature which has additional functionality for an out of the box testing. With both you can do all the testing referenced in the new content modelling overhaul PRs.

   This could be the way we will handle our configuration. A core Islandora feature that you must install and the changes are maintained by the community, and then you will have your own feature on-top of it that does the additional changes necessary for your repository.

   If someone wants a turnkey repo, you would use the islandora_demo_feature. Probably copying it and making changes to your copy.

   More docs to be added around content-modelling (https://github.com/dannylamb/islandora/tree/content-modeling-overhaul)

   Running into Out of Memory Errors when running on PHP 5.6, using up all 1.5 GB of Ram.

2. What do we need for Centos support?

   Gemini DB table design is causing problems using MariaDB.

   Change to make 2 hashes out of the paths and make them unique. Also maybe using the Doctrine API to generate a clean table structure for both Ubuntu and Centos.

   You can have a unique constraint but not on such long varchar fields.

   Is there a very long field to store very long fields? Maybe move the URI fields to be text or blob so we won't hit a large size. DBAL has a text field, which we can.

   We are going to refactor to use a 512 hash of the URI for the unique field like Diego suggested https://gist.github.com/DiegoPino/825d33da1a376b72cf0b0c06ff66bed1

   Changes are all in https://github.com/Islandora-CLAW/Crayfish/blob/master/Gemini/src/UrlMapper/UrlMapper.php

3. Migration stuff

   Paul has built http://claw2.researchspaces.ca/ which is a port of Islandora 6 to CLAW!!

   Jared has built some plugins for pulling direct from a Fedora 3. https://github.com/whikloj/migrate_7x_claw