June 28, 2017

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

• Jared Whiklo
• Bryan Brown
• Marcus Barnes
• Rosie Le Faive
• Danny Lamb
• Yamil Suarez
• Martin Dow
• Adam Soroka

Agenda

1. New theme: Carapace
2. The future is back
3. API-X is using SNAPSHOT builds. https://github.com/Islandora-CLAW/Crayfish/pull/38 is ready for test.
4. Decouple modules from theme.
   1. The culprit: https://github.com/Islandora-CLAW/islandora_collection/blob/8.x-1.x/config/install/block.block.views_block__membership_view_block_1.yml
   2. The band-aid: https://github.com/Islandora-CLAW/CLAW/pull/672
5. Image object model
6. ... (feel free to add agenda items)

Minutes

1. Favenzio of FSU set up Carapace, a new theme for Islandora. It's been put on the Vagrant and on future.islandora.ca.
   1. Base theme (generic default that can ship with islandora) + subtheme (for extra features and stuff) - carapace + beautiful_carapace? We'll keep developing on carapace until we decide to break into theme + subtheme
   2. If you're interested in helping / chatting re theme, join the UI Interest group!
2. Sandbox! future.islandora.ca. it is NOT exactly the same as the Vagrant install... it includes some unmerged changes:
   1. OpenSeadragon: http://future.islandora.ca/node/7
   2. API-X: http://future.islandora.ca:8081/fcrepo/rest Also the sandbox is snapshotted, so go nuts and Danny can fix it if it gets too crazy.
3. Crayfish pull makes it possible to work with API-X - can anyone look and committer merge? (It's already running on Sandbox).
4. We all think this is BAD but need to come up with a solution. Distribution? Features? (Also, let's get that bandaid merged)
5. OpenSeadragon is installed on the sandbox, as a field formatter. It's currently the field formatter set up for the OBJ media field. That means that while you can upload jpg, gif, tiff, jp2 as obj, only tiffs (right now, not even jp2) will show up in the viewer.
   1. This means if you have a reusable media bundle, it'll display the same in all content types.
   2. How are we going to set up book viewer? (crickets)
   3. It seems like we need to treat different file types differently... a web image and a tiff shouldn't be in the same OBJ media bundle.
   4. Is there going to be an identifiable way to find out where the preservation master is, if it exists? We've had a convention that led to consistent access (/islandora/object/PID/datastream/TN) even though never formalized, can we try to carry this pseudo-API over? A restful API, like node/N/files/OBJ or something in the URL is do-able.
   5. If we're talking REST api's, we should do it right. We shouldn't publish things in our linked data side that are ddirectly UURI's from Drupal. They are (and should remain) internal identifiers, but some relationships still point there and shouldn't.
6. OpenSeadragon: will be transferred in Github to CLAW.